CAPS LOCK LED STARTS BLINKING AND THE NOTEBOOK CRASH (KDE?) (PCI: Bus #04 (-#07) is hidden behind transparent bridge #03 )

Which version of Ubuntu are you using?

Ubuntu 7.04

----- Messaggio originale -----
Da: William Grant <email address hidden>
A: <email address hidden>
Inviato: Mercoledì 1 agosto 2007, 1:13:41
Oggetto: [Bug 129500] Re: CAPS LOCK LED STARTS BLINKING AND THE NOTEBOOK CRASH

Which version of Ubuntu are you using?

--
CAPS LOCK LED STARTS BLINKING AND THE NOTEBOOK CRASH
https://bugs.launchpad.net/bugs/129500
You received this bug notification because you are a direct subscriber
of the bug.

      ___________________________________
L'email della prossima generazione? Puoi averla con la nuova Yahoo! Mail: http://it.docs.yahoo.com/nowyoucan.html

Thank you for taking the time to report this bug and helping to make Ubuntu better.

Well, it is not easy because the blinking CAPS LOCK indicate that the kernel stop on one of the CPU core.
Unless you have Dual Core, it pretty means that nothing can be done after.

Please include the following additional information (before kernel crash of course), if you have not already done so (please pay attention to lspci's additional options), as required by the Ubuntu Kernel Team:
1. Please include the output of the command "uname -a" in your next response. It should be one, long line of text which includes the exact kernel version you're running, as well as the CPU architecture.
2. Please run the command "dmesg > dmesg.log" and attach the resulting file "dmesg.log" to this bug report.
3. Please run the command "sudo lspci -vvnn > lspci-vvnn.log" and attach the resulting file "lspci-vvnn.log" to this bug report.

For your reference, the full description of procedures for kernel-related bug reports is available at [WWW] http://wiki.ubuntu.com/KernelTeamBugPolicies.

What program were you using when this happens, doing what?
Does this happens often?

Thanks in advance!

This are the output request

uname -a
"Linux portatile 2.6.20-16-generic #2 SMP Thu Jun 7 19:00:28 UTC 2007 x86_64 GNU/Linux
"

dmesg.log and lspci-vvnn.log files are attached

TKS for HELPS

----- Messaggio originale -----
Da: Paul Dufresne <email address hidden>
A: <email address hidden>
Inviato: Giovedì 2 agosto 2007, 20:35:37
Oggetto: [Bug 129500] Re: CAPS LOCK LED STARTS BLINKING AND THE NOTEBOOK CRASH

Thank you for taking the time to report this bug and helping to make
Ubuntu better.

Well, it is not easy because the blinking CAPS LOCK indicate that the kernel stop on one of the CPU core.
Unless you have Dual Core, it pretty means that nothing can be done after.

Please include the following additional information (before kernel crash of course), if you have not already done so (please pay attention to lspci's additional options), as required by the Ubuntu Kernel Team:
1. Please include the output of the command "uname -a" in your next response. It should be one, long line of text which includes the exact kernel version you're running, as well as the CPU architecture.
2. Please run the command "dmesg > dmesg.log" and attach the resulting file "dmesg.log" to this bug report.
3. Please run the command "sudo lspci -vvnn > lspci-vvnn.log" and attach the resulting file "lspci-vvnn.log" to this bug report.

For your reference, the full description of procedures for kernel-
related bug reports is available at [WWW]
http://wiki.ubuntu.com/KernelTeamBugPolicies.

What program were you using when this happens, doing what?
Does this happens often?

Thanks in advance!

** Changed in: linux-source-2.6.20 (Ubuntu)
     Assignee: (unassigned) => Paul Dufresne
       Status: New => Incomplete

--
CAPS LOCK LED STARTS BLINKING AND THE NOTEBOOK CRASH
https://bugs.launchpad.net/bugs/129500
You received this bug notification because you are a direct subscriber
of the bug.

      ___________________________________
L'email della prossima generazione? Puoi averla con la nuova Yahoo! Mail: http://it.docs.yahoo.com/nowyoucan.html

Please use the web interface for which a link is added by the bug manager at the end of emails notice send (end of this email) rather than replying
to the email.

>dmesg.log and lspci-vvnn.log files are attached
I did not see them with the email you sent me, anyway, I would have requested you to reattach them using the web interface.
Scroll down on the bug's web page, and use the link 'Add a comment/attachment'.

I also note you have ignored my other two questions:
What program were you using when this happens, doing what?
Does this happens often?

Even with these files there is almost nothing we can do, because all we know is that Linux die, but without clue to where.
And it is not much your fault, because you cannot find why before it happens, and you cannot do actions to find why after it happens.
But if it happens on something like inserting a card or something similar, going to console with CTRL-ALT-F1 then inserting the card
should let you see some text explaining why it die on the screen. (Normally you return to graphics mode with ALT-F7 but after kernel die,
obviously you will not be able to do so).

I hope I am placing this in the correct place:

Hello, I've also had the same problem as bennyatc, only my notebook is an HP Pavilion zv6000. Here is my info:

Linux EPHNetworks 2.6.20-16-generic #2 SMP Thu Aug 30 23:16:15 UTC 2007 x86_64 GNU/Linux

I've encountered this problem while using Konsole and xemacs. Note that I run xemacs from the command line, so Konsole is open then, too.

Frequency of the problem is inconsistent. Over the last 3 or 4 days it has occurred about 6 times or so. It occurs while I am typing, most frequently when I am using arrow keys or backspace, although it happened one time after I hit the "p" key.

Please note that I run a dual boot setup and run Linux from a Seagate 500GB Free Agent Desktop external HD, and have changed the settings of /sys/block/sda/device/scsi_disk*/allow_restart to 1 in order to alleviate I/O problems with the HD where it remounts my partitions as read only.

Seems similar to http://ubuntuforums.org/showthread.php?t=289361 (ohci1394 causing flood of "APIC error on CPU0: 40(40)" )

Thank you very much, added the module to the blacklist, I'll see if that helps.

I added the module to the blacklist, but I got the same crash a bit later, and was still getting those messages in dmesg. I booted onto Windows, and flashed my BIOS, awaiting results of that. The BUG message that I saw during boot and that was in the dmesg:
[ 49.521295] ..MP-BIOS bug: 8254 timer not connected to IO-APIC
is now gone. So perhaps, for me, that solved the problem IAW the link you sent me to earlier. If you are interested, I have attached my new dmesg to this reply.

Thank you for the help.

I have had none of the APIC error on CPU0: 40(40) messages in my dmesg log since my last posting. However, I did continue to get the crashes more and more frequently (the blinking caps lock light). I had installed kdm, and was running the kde desktop sometime before all this happened. One day, after I decided to run GNOME, and I did not have the problems. However, due to a problem, that I am not sure about, I could not reconfigure GDM to be my default desktop manager (there are numerous postings about this, such as http://ircarchive.info/kubuntu/2007/3/18/124.html ), where I get the invoke-rc.d: initscript gdm, action "reload" failed. message, and even if I double checked that sudo dpkg --configure kdm or gdm was good. Anyhow, I no longer get the crashes, so I believe the issue for me, with the blinking caps lock light where my computer freezes, was associated with the KDE desktop somehow. Since I had complete freezes, and it could not log the error in dmesg, I have no idea where the crash was coming from. Since I reinstalled Ubuntu, and have not reinstalled KDE, I have had no problems whatsoever with either the CPU0: 40(40) flood or the blinking caps lock crash. Please note that both bennyatc and I have AMD64 Athlon CPU's, and we both have ATI Radeon Mobility Video cards (although his is a X700 and mine is a Xpress 200M). I'm sorry I cannot give more specific information as to what exact program was causing the crashes.

Thank you very much for the assistance you have provided thus far. Since I reinstalled, everything is quite stable. I just wanted to give some feedback on what could be causing the bug.

Sorry for not responding earlier.

Well, there is something else that both of you have in their dmesg.log files:
[ 47.128417] PCI: Bus #04 (-#07) is hidden behind transparent bridge #03 (-#04) (try 'pci=assign-busses')

bennyatc, are you still there?
Any news? Maybe you did upgrade to 7.10 (Gutsy) now?

I am running Gutsy on a dual-core machine, and I am having the same problem.

My Caps Lock and Scroll Lock both started blinking and the system froze, while I was ripping a DVD (just direct dump of the data). The emergency key combinations (Alt-Sysrq-*) did nothing. Since I'm on a dual-core machine, does having both of the lights blinking mean that the kernel has frozen on both cores? I think I once got all three lights blinking, but I'm not entirely sure.

This may also be related to a problem I am having with the Quit box in Gnome. Whenever I go to System > Quit... , the X session freezes. If I go to a text terminal and run Top, I can see that Init is the top process. When I switched back to X, I could see just the filled-in outline of the Quit box. Clicking where the Shut Down button should be does shut down the computer.

The only extra kernel module I am running is the Nvidia new driver from Restricted Drivers Manager. The motherboard is an Asus P5K Premium. If there is anything I can try to help to get rid of this problem, I am willing to try. I am now going to add the noapic and nolapic arguments to GRUB for next boot.

>does having both of the lights blinking mean that the kernel has frozen on both cores?
Well, I am not an expert at kernel, more a bug triager trying to make sure bug have enough info to ideally fix the bug, or at least knowing what to ask for better investigation. So, I thought that they were all blinking, bug I may be wrong.

I would prefer to consider your bug a different one until proved the same. So please, open a new bug.
It should be on the package linux-source-2.6.22 since you are using Gutsy. Please add a comment here with the number of the newly created bug, something like "I have open bug #9999" (this is automatically changed in a link).

Indicate in it if this have happen once, or happen sometimes. If sometimes, how often.
Please read a bit https://wiki.ubuntu.com/KernelTeamBugPolicies to know how to report bug on kernel.

I have opened bug #180507 under Paul's advice, because I am using a different kernel and because it now appears to me to have a different cause.

I am closing this bug report because I have no feedback from bennyatc or Eric Haslehurst
We don't have a oops trace.
And if they was to give answer I would ask them to try to boot with kernel option: pci=assign-busses
And see if they can post /var/log/kernel.log.
To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

I am using Ubuntu 7.10 with 2.6.22-14-generic kernel. I believe I can reliably reproduce this error.

Whenever I use the cisco VPN client software, shortly after logging in to my PIX the gnome terminal halts and the caps lock light blinks. There is no recovery from this other than a hard shutdown.

What files would you like me to provide?

I am currently running Ubuntu on an X61 C2D 2.2ghz 2GB.

Thanks.

Thank you for taking the time, 3rods, to report this bug and helping to make Ubuntu better.

Please open a new bug, indicating the bug number of this one in it.
The hard part is to get the crash info. KernelTeamBugPolicie suggest:
"If the bug report involves a crash, it is hoped that a kernel backtrace (aka OOPS, kernel panic) is available. If the machine does not completely lockup from the crash, the backtrace should be available in the dmesg output. If the crash completely locks the system, try rebooting to a known working kernel and see if any backtrace was logged to /var/log/kern.log.0 . Please attach this file if anything was captured. If all else fails, supply a digital photo of the screen to capture the crash."
In your case, you could also try VPN not from gnome-terminal, but from console (Ctrl-Alt-F1).
console shows kernel info, and hopefully crash info.

Include the following additional information (pay attention to lspci's additional options), as required by the Ubuntu Kernel Team:
1. Please include the output of the command "uname -a" in your next response. It should be one, long line of text which includes the exact kernel version you're running, as well as the CPU architecture.
2. Please run the command "dmesg > dmesg.log" after a fresh boot and attach the resulting file "dmesg.log" to this bug report.
3. Please run the command "sudo lspci -vvnn > lspci-vvnn.log" and attach the resulting file "lspci-vvnn.log" to this bug report.

For your reference, the full description of procedures for kernel-related bug reports is available at [WWW] http://wiki.ubuntu.com/KernelTeamBugPolicies.

Thanks in advance!

I've got the same issue on two machines: one HP tx1000 notebook, and another custom built desktop. Both are running 64 bit versions of Ubuntu 8.10. This issue forces me to use Windows to vpn into work :(.