Bug#650119: linux-image-3.1.0-1-amd64: fails to boot on HP DL380 g4
Hello ?
When I am not wrong some stable kernels are taken from the list at kernel.org
cause they were buggy ... only few are left.
I had trouble with 3.1.2 and still with 3.1.5 (both stable), cause they dont boot
and hang themselves up with:
FATAL: Could not load /lib/modules/3.1.x/modules.dep: No such file or directory
Installation was done correctly.
Greetings
Val.
2011/12/15 Ben Hutchings
<ben@decadent.org.uk>
-------- Forwarded Message --------
From: Peter Verschoor <peter.j.verschoor@gmail.com>
To: Ben Hutchings <ben@decadent.org.uk>
Subject: Re: Bug#650119: linux-image-3.1.0-1-amd64: fails to boot on HP DL380 g4
Date: Sun, 27 Nov 2011 18:44:12 -0700
Ben:
Now comes the head-scratching part. When I modify the grub boot
command line to send output to my laptop through the serial port it
boots correctly!
[ 0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-3.1.0-1-amd64
root=UUID=155d483d-563c-4c25-b9f2-bf0b61e14041 ro console=ttyS0,9600
console=tty0
and the cciss IRQ gets rerouted to 19.
The output appears on both my laptop and the main console screen. I can
capture the output on the laptop and the kernel captures it in /var/log.
If I boot it with this command line it will lock up every time.
Command line: BOOT_IMAGE=/boot/vmlinuz-3.1.0-1-amd64
root=UUID=155d483d-563c-4c25-b9f2-bf0b61e14041 ro
The attached file CAPTURE.TXT was created on an old IBM laptop running
Win2k using Hyperterm and sneaker-netted to the Proliant using a USB
stick. That means that at least the front USB port is working.
Let me study the HP manuals tomorrow and see what I can do with the
Integrated Lights-Out module. I've never used it on these machines but
have used Sun's LOM on my sparc servers many times.
Pete
Meanwhile ..............
On Sun, Nov 27, 2011 at 11:34 AM, Ben Hutchings <ben@decadent.org.uk>
wrote:
> On Sun, 2011-11-27 at 07:44 -0700, Peter Verschoor wrote:
>> Ben:
>>
>> I found your email this AM. I removed the init scripts for
>> vmware and virtual box so the kernel is no longer tainted. I then
>> rebooted and used the grub editor to remove the pci=noioapicreroute
>> switch. I can then scroll back through the boot messages and find
the
>> two following lines.
>> [ 1.200100] cciss 0000:04:03.0 unable to get irq 19 for cciss0
>> [ 1.200207] cciss:probe of 0000:04:03.0 failed with error -1
>> It eventually drops into a BusyBox shell where I can reboot Irq 19
us
>> used by one of the USB ports.
> [...]
>
> I (and the upstream developers) will need to see what was logged
before
> those lines as well.
>
> Ben.
>
> --
> Ben Hutchings
> The two most common things in the universe are hydrogen and stupidity.
>
Reply to: