dtl1_cs causes kernel panic when plugged in (intrepid ibex alpha 4)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: linux-image-
This is related to bug 217659.
This bug report is being opened at the request of Leann Ogasawara (see last comment in bug 217659).
I have done the same testing now for feisty, gutsy, hardy, intrepid alpha4, and intrepid pre-alpha5.
Kernel panics have started to appear since hardy release for dtl1_cs module.
user@user-laptop:~$ apt-cache policy linux-image-
linux-image-
Installed: 2.6.26-5.15
Candidate: 2.6.26-5.17
Version table:
2.6.26-5.17 0
500 http://
*** 2.6.26-5.15 0
100 /var/lib/
user@user-laptop:~$ lsb_release -rd
Description: Ubuntu intrepid (development branch)
Release: 8.10
COM2 (ttyS1) is disabled in bios.
See attached kernel crash for 2.6.26-5-generic
Interrupt list:
user@user-laptop:~$ cat /proc/interrupts
CPU0
0: 45282 XT-PIC-XT timer
1: 8 XT-PIC-XT i8042
2: 0 XT-PIC-XT cascade
3: 3 XT-PIC-XT
4: 376 XT-PIC-XT serial
5: 3 XT-PIC-XT
6: 2 XT-PIC-XT
7: 3 XT-PIC-XT parport0
8: 0 XT-PIC-XT rtc0
9: 381 XT-PIC-XT acpi
10: 3 XT-PIC-XT
11: 1217 XT-PIC-XT uhci_hcd:usb1, uhci_hcd:usb2, uhci_hcd:usb3, yenta, yenta, Intel 82801CA-ICH3, eth0
12: 149 XT-PIC-XT i8042
14: 8560 XT-PIC-XT ata_piix
15: 5559 XT-PIC-XT ata_piix
NMI: 0 Non-maskable interrupts
LOC: 0 Local timer interrupts
RES: 0 Rescheduling interrupts
CAL: 0 function call interrupts
TLB: 0 TLB shootdowns
TRM: 0 Thermal event interrupts
SPU: 0 Spurious interrupts
ERR: 0
MIS: 0
Hi Quinn,
We'll actually continue to use your original bug report to track this bug. I'm sorry if it wasn't clear in my other message but you only need to open a new bug report for bugs which appear in 2.6.27 and not in 2.6.26 or previous kernels. Ie 2.6.27 regressions. If a report already exist for the bug in question, please continue to use that existing bug report and post 2.6.27 comment updates there. Sorry again for the confusion. I'll go ahead and mark this as a duplicate of your original bug report. Thanks.