On Fri, 2009-08-21 at 17:03 +0000, BAILEY, SCOTT (EDS Server Management & Virtualization) wrote: > Ben, > > I have good news and bad news. > > Good news: No ugly trace during device discovery. > Bad news: First QLA1040 still fails to initialize, and the other two > work fine. So there are two separate bugs here, and I seem to have fixed the easy one. > Console output from this boot attempt is attached. > > Thanks for your assistance. I should be able to turn around patches > more quickly in the future, but I will be on vacation next week so I > won't be able to test anything then. No patch this time, as I think the issue may be outside the kernel itself. I would like you to get a debug log from udev: 1. For one boot, add "break" to the kernel command line. This will give you an interactive shell before driver modules are loaded. 2. At the shell prompt, enter "sed -i s/err/debug/ /etc/udev/udev.conf". Note that this does not modify the file on your normal filesystem. 3. Enter "exit" to continue booting. There should be a flood of debug messages from udev; please attach them to your reply. Ben. -- Ben Hutchings If at first you don't succeed, you're doing about average.
Attachment:
signature.asc
Description: This is a digitally signed message part