Sometimes, when I boot, the PC makes a kernel panic, and Caps Lock and Scroll Lock LEDs are blinking

Bug #694993 reported by Joaquin
26
This bug affects 4 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

Sometimes, when I boot, the PC makes a kernel panic, and Caps Lock and Scroll Lock LEDs are blinking
Other times, the PC boots perfectly, but after 30 minutes more or less, the PC hangs, with the blinking LEDs

I think that it's a security bug, because it can be used to install something without super user permission
What do you think?

ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: ubuntu-desktop (not installed)
ProcVersionSignature: Ubuntu 2.6.37-11.25-generic-pae 2.6.37-rc7
Uname: Linux 2.6.37-11-generic-pae i686
NonfreeKernelModules: nvidia
Architecture: i386
Date: Tue Dec 28 12:45:02 2010
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
ProcEnviron:
 LANGUAGE=es_ES:es:en_GB:en
 PATH=(custom, no user)
 LANG=es_ES.UTF-8
 LC_MESSAGES=es_ES.utf8
 SHELL=/bin/bash
SourcePackage: ubuntu-meta
---
Architecture: i386
DistroRelease: Ubuntu 11.04
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
NonfreeKernelModules: nvidia
Package: linux (not installed)
ProcEnviron:
 LANGUAGE=es_ES:es:en_GB:en
 PATH=(custom, no user)
 LANG=es_ES.UTF-8
 LC_MESSAGES=es_ES.utf8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.37-11.25-generic-pae 2.6.37-rc7
Regression: Yes
Tags: natty
Uname: Linux 2.6.37-11-generic-pae i686
UserGroups: adm admin cdrom dialout fuse lpadmin plugdev sambashare

Revision history for this message
Dave Gilbert (ubuntu-treblig) wrote :

Hi,
  On one of the times that the PC boots OK, can you please run

apport-collect 694993

as soon as possible; that will collect a load of information about your machine and add it to this report. You could also try booting into 'recovery mode' and see if there is any more information on the screen when it panics.

It doesn't sound like a security issue to me.

Dave

affects: ubuntu-meta (Ubuntu) → linux (Ubuntu)
Revision history for this message
Joaquin (jknvv13) wrote : Re: [Bug 694993] Re: Sometimes, when I boot, the PC makes a kernel panic, and Caps Lock and Scroll Lock LEDs are blinking

Ok, but how can I send the text when a kernel panic shows anything, in
recovery mode?
(And, sorry for my english, but I'm spanish)
El 28/12/2010 13:41, "Dave Gilbert" <email address hidden> escribió:
> Hi,
> On one of the times that the PC boots OK, can you please run
>
> apport-collect 694993
>
> as soon as possible; that will collect a load of information about your
> machine and add it to this report. You could also try booting into
> 'recovery mode' and see if there is any more information on the screen
> when it panics.
>
> It doesn't sound like a security issue to me.
>
> Dave
>
>
> ** Package changed: ubuntu-meta (Ubuntu) => linux (Ubuntu)
>
> --
> You received this bug notification because you are a direct subscriber
> of the bug.
> https://bugs.launchpad.net/bugs/694993
>
> Title:
> Sometimes, when I boot, the PC makes a kernel panic, and Caps Lock and
Scroll Lock LEDs are blinking
>
> Status in “linux” package in Ubuntu:
> New
>
> Bug description:
> Sometimes, when I boot, the PC makes a kernel panic, and Caps Lock and
Scroll Lock LEDs are blinking
> Other times, the PC boots perfectly, but after 30 minutes more or less,
the PC hangs, with the blinking LEDs
>
> I think that it's a security bug, because it can be used to install
something without super user permission
> What do you think?
>
> ProblemType: Bug
> DistroRelease: Ubuntu 11.04
> Package: ubuntu-desktop (not installed)
> ProcVersionSignature: Ubuntu 2.6.37-11.25-generic-pae 2.6.37-rc7
> Uname: Linux 2.6.37-11-generic-pae i686
> NonfreeKernelModules: nvidia
> Architecture: i386
> Date: Tue Dec 28 12:45:02 2010
> InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386
(20101007)
> ProcEnviron:
> LANGUAGE=es_ES:es:en_GB:en
> PATH=(custom, no user)
> LANG=es_ES.UTF-8
> LC_MESSAGES=es_ES.utf8
> SHELL=/bin/bash
> SourcePackage: ubuntu-meta
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/694993/+subscribe

Revision history for this message
Dave Gilbert (ubuntu-treblig) wrote :

> Ok, but how can I send the text when a kernel panic shows anything, in
> recovery mode?
> (And, sorry for my english, but I'm spanish)

If you have a camera then attach a picture of it.

Dave

Joaquin (jknvv13)
tags: added: apport-collected
description: updated
Revision history for this message
jolo (joop-loep) wrote :
Download full text (3.4 KiB)

I can confirm this bug with natty-desktop-i386.iso 01/05/2011
Checksum OK
DVD-RW burned with K3b "Verify written data" OK
Check disc for defects: No errors found
Inspite of the regularly Kernel panic in Live sessons, I was able to install Natty on two different PC's and one laptop

To capture the some of the kernel panics, I followed these instructions https://wiki.kubuntu.org/Kernel/Netconsole
I also added as boot option: panic=20

This is the kernel panic, captured from my ThinkPad R61i 8932GM laptop

[ 5887.663623] EXT4-fs (sda10): re-mounted. Opts: (null)
[ 5887.791037] md: stopping all md devices.
[ 5888.786178] sd 2:0:0:0: [sda] Synchronizing SCSI cache
[ 5888.822865] r852 0000:15:00.5: PCI INT C disabled
[ 5888.825375] ehci_hcd 0000:00:1d.7: PCI INT D disabled
[ 5888.828041] ehci_hcd 0000:00:1a.7: PCI INT C disabled
[ 5888.830253] Restarting system.
[ 5889.978958] irq 18: nobody cared (try booting with the "irqpoll" option)
[ 5889.980008] Pid: 1811, comm: reboot Not tainted 2.6.37-11-generic #25-Ubuntu
[ 5889.980008] Call Trace:
[ 5889.980008] [<c05f93ae>] ? printk+0x30/0x32
[ 5889.980008] [<c01b306c>] __report_bad_irq.clone.2+0x2c/0x90
[ 5889.980008] [<c01b1cbc>] ? handle_IRQ_event+0x4c/0x160
[ 5889.980008] [<c01b33ba>] note_interrupt+0x15a/0x1a0
[ 5889.980008] [<c01b4014>] handle_fasteoi_irq+0xb4/0xe0
[ 5889.980008] [<c01b3f60>] ? handle_fasteoi_irq+0x0/0xe0
[ 5889.980008] <IRQ> [<c0602a69>] ? do_IRQ+0x49/0xc0
[ 5889.980008] [<c0156e1c>] ? irq_exit+0x3c/0x80
[ 5889.980008] [<c0602b3b>] ? smp_apic_timer_interrupt+0x5b/0x8a
[ 5889.980008] [<c0156bf0>] ? __do_softirq+0x0/0x180
[ 5889.980008] [<c0103770>] ? common_interrupt+0x30/0x38
[ 5889.980008] [<c0156bf0>] ? __do_softirq+0x0/0x180
[ 5889.980008] [<c0156c35>] ? __do_softirq+0x45/0x180
[ 5889.980008] [<c0156bf0>] ? __do_softirq+0x0/0x180
[ 5889.980008] <IRQ> [<c0156e4d>] ? irq_exit+0x6d/0x80
[ 5889.980008] [<c0602b3b>] ? smp_apic_timer_interrupt+0x5b/0x8a
[ 5889.980008] [<c015007e>] ? _call_console_drivers+0x4e/0x90
[ 5889.980008] [<c05fc2d9>] ? apic_timer_interrupt+0x31/0x38
[ 5889.980008] [<c015007b>] ? _call_console_drivers+0x4b/0x90
[ 5889.980008] [<c015086d>] ? vprintk+0x16d/0x3f0
[ 5889.980008] [<c042649a>] ? sysdev_shutdown+0x6a/0xc0
[ 5889.980008] [<c05f93ae>] ? printk+0x30/0x32
[ 5889.980008] [<c0164234>] ? kernel_restart+0x44/0x60
[ 5889.980008] [<c01643cd>] ? sys_reboot+0x15d/0x1d0
[ 5889.980008] [<c01415c4>] ? enqueue_entity+0x184/0x210
[ 5889.980008] [<c014197a>] ? enqueue_task_fair+0x4a/0x50
[ 5889.980008] [<c0138842>] ? resched_task+0x22/0x70
[ 5889.980008] [<c01388f5>] ? check_preempt_curr+0x65/0x90
[ 5889.980008] [<c0149f93>] ? try_to_wake_up+0x223/0x3c0
[ 5889.980008] [<c05fb976>] ? _raw_spin_unlock_bh+0x16/0x20
[ 5889.980008] [<c0245390>] ? bdi_queue_work+0x60/0xd0
[ 5889.980008] [<c0245703>] ? __bdi_start_writeback+0x83/0x140
[ 5889.980008] [<c0229305>] ? iterate_supers+0xa5/0xb0
[ 5889.980008] [<c024a430>] ? sync_one_sb+0x0/0x30
[ 5889.980008] [<c05fbe54>] ? syscall_call+0x7/0xb
[ 5889.980008] handlers:
[ 5889.980008] [<c0498630>] (usb_hcd_irq+0x0/0x80)
[ 5889.980008] [<f8075b20>] (sdhci_irq+0x0/0x1a8 [sdhci])
[ 5889.980008] [...

Read more...

jolo (joop-loep)
Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
Dave Gilbert (ubuntu-treblig) wrote :

Hi Jolo,
  Can you file a separate bug for your crash; kernel bugs don't normally get merged like that without knowing it's exactly the same hardware and oops and cricumstances.

Dave

Changed in linux (Ubuntu):
status: Confirmed → New
Revision history for this message
jolo (joop-loep) wrote :

Hi Dave Gilbert,

The reason to report the random kernel panics here, is because I did experience this on two different PC's and laptop. But I was only able to capture kernel panics from my laptop. The kernel panics on the two PC's, I was only able to watch them in Recovery Mode. If I compare the kernel panics in Recovery Mode, my 2 PC's and laptop have in common at least these 5 lines. They occur during boot time, with Caps Lock and/or Scroll Lock LEDs blinking.

[<c047830e>] ata_bmdma_Port_intr+0x2e/0x100
[<c0476870>] ? ata_bmdma_error_handler+0x0/0x120
[<c0478b2d>] ata_bmdma_interrupt+0xcd/0x1d0
[<c01b1cec>] handle_IRQ_event+0x4c/0160
<IRQ> [<c0602cc9>] ? do_IRQ+0x49/0xc0

Do you still think, a separate bug report is required?

Revision history for this message
Jeremy Foshee (jeremyfoshee) wrote :

Hi Joaquin,

If you could also please test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

    [This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

tags: added: needs-upstream-testing
tags: added: kj-triage
Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status: Incomplete → Expired
Changed in linux (Ubuntu):
status: Expired → Incomplete
Changed in linux (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.