Correct modules for I2O-based raid are not loaded
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
grub (Ubuntu) |
Fix Released
|
High
|
Colin Watson | ||
Dapper |
Invalid
|
Undecided
|
Unassigned | ||
hw-detect (Ubuntu) |
Fix Released
|
Medium
|
Colin Watson | ||
Dapper |
Fix Released
|
Medium
|
Colin Watson | ||
linux-source-2.6.15 (Ubuntu) |
Fix Released
|
Medium
|
Unassigned | ||
Dapper |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Ubuntu 5.10 Preview experiences a system panic w/ I2O based raid controler at
kernel boot after controller is detected. Current controller that this is
experienced on is a Adaptec 2400a Hardware Raid (IDE). I do not have any other
I2O based controllers on which to test this.
5.4 did not experience this (we currently are using it), so this must be a
regression in the preview version.
Details for hw-detect dapper proposed update:
The installer offers a menu of disk drivers when disks are not automatically detected. This list fails to include the drivers from drivers/
The bug was addressed in hw-detect 1.33 (in edgy) by adding these directories to the list of directories to be searched for drivers to offer, and adding a guard in case either directory doesn't exist.
A proposed patch for dapper is linked here: https:/
You can reproduce this bug by removing the kernel module responsible for your disk from the running installer before it has a chance to load it (be quick!), and looking at the list of disks offered. Alternatively, it might be easier to boot in VMware with no disks attached.
I haven't yet thought of any regression possibilities here, but they ought to be limited to the path where no disks were automatically detected.
Related branches
Changed in udev: | |
assignee: | keybuk → nobody |
Changed in linux-source-2.6.15: | |
assignee: | nobody → ubuntu-kernel-team |
Changed in hw-detect: | |
assignee: | nobody → kamion |
Changed in linux-source-2.6.15: | |
status: | New → Fix Released |
Changed in grub: | |
status: | New → Invalid |
description: | updated |
Changed in hw-detect: | |
status: | Fix Released → Fix Committed |
Can't guarantee that this will get fixed for breezy, but since it's a regression I'm pushing it to P1 in the
hopes that it will get fixed.
Please could you send me the actual kernel panic? Taking a picture with a digital camera will suffice.
Thanks