[gutsy] aha1542 causes kernel panic
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Won't Fix
|
Undecided
|
Unassigned | ||
linux-source-2.6.22 (Ubuntu) |
Won't Fix
|
Medium
|
Unassigned |
Bug Description
Binary package hint: linux-image-
Using scanimage -L with adaptec 1542CF ISA card and a Umax 610S SCSI scanner. Sane-find-scanner or scanimage -L causes a kernel panic as follows:
Bad Segment list supplied to AHA1542.c (1,0)
0:C0008000 5
<ptr C04B000 00 00 00 00 00 00 00 00 02 00 08 12 00 00 00 00 00
00 <0> Kernel Panic - not syncing:Foooooooood fight!
Googling around a bit suggests that this might be a regression in the aha1542 kernel driver as it seems to have appeared at irregualr intervals from late 2.4.x kernels, been fixed but then reappeared in 2.6.x kernels.
I've not seen this before on this machine, but then I last ran breezy on it so perhaps the module was still ok then.
Scanner/card/etc all seems ok on dual boot Windows XP.
Regards,
Craig
Changed in linux-source-2.6.22: | |
importance: | Undecided → Medium |
Changed in linux-source-2.6.22: | |
assignee: | brian-murray → ubuntu-kernel-team |
status: | Incomplete → Triaged |
Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't fix it, because your description doesn't yet have enough information. /wiki.ubuntu. com/KernelTeamB ugPolicies . Thanks in advance!
Please include as attachments the following additional information, 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' after reproducing the issue 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 https:/