I've burnt install-x86-minimal-20091103.iso on dvd. Then gentoo kernel without any options has been booted successfully. After issuing reboot command the system starts to shutdown but hangs after the following message appears: Remounting remaining filesystems read only [ok] Reproducible: Always Steps to Reproduce: 1. burn minimal install cd on dvd 2. boot from it 3. wait until system starts 4. type "reboot -f" Actual Results: sd 2:0:0:0: [sda] Synchronizing SCSI cache Restarting system. machine restart do_IRQ: 0.108 No irq handler for vector (irq -1) do_IRQ: 0.110 No irq handler for vector (irq -1) do_IRQ: 0.110 No irq handler for vector (irq -1) do_IRQ: 0.110 No irq handler for vector (irq -1) do_IRQ: 0.110 No irq handler for vector (irq -1) do_IRQ: 0.110 No irq handler for vector (irq -1) do_IRQ: 0.110 No irq handler for vector (irq -1) do_IRQ: 0.110 No irq handler for vector (irq -1) do_IRQ: 0.110 No irq handler for vector (irq -1) do_IRQ: 0.110 No irq handler for vector (irq -1) and the system hangs Expected Results: the system is rebooted
Created attachment 209560 [details] uname and lspci output
This sounds like a kernel issue.
(In reply to comment #2) > This sounds like a kernel issue. > You are right. install-x86-minimal-20091013.iso has the same issue.
That message basically means that the hardware sent vector 0x110 to cpu0 but it couldn't be handled. That's quite weird. Did you upgrade your BIOS recently? Can you trace the last kernel version, if any, which could reboot successfully? Also, give us a full copy of your dmesg before trying to reboot.
(In reply to comment #4) > That message basically means that the hardware sent vector 0x110 to cpu0 but it > couldn't be handled. That's quite weird. > > Did you upgrade your BIOS recently? > Can you trace the last kernel version, if any, which could reboot successfully? > Also, give us a full copy of your dmesg before trying to reboot. > No, I didn't upgrade my BIOS recently. Booting up Ubuntu 9.04 (kernel 2.6.28) and Ubuntu 9.10 (kernel 2.6.31) is OK. I'll provide copy of my dmesg in an hour.
Created attachment 209886 [details] dmesg output
Even tho I don't have your kernel config and I can't see if you have MSI enabled, judging by this line in your dmesg "r8169 0000:02:00.0: no MSI. Back to INTx." I guess that you don't. You may be getting MSIs that can't be interpreted correctly because you miss CONFIG_PCI_MSI. Try booting with the "nomsi" parameter and see if you get any changes in your dmesg.
I've booted with nomsi, but there are no major differences in dmesg.
Created attachment 211844 [details] dmesg with nomsi
(In reply to comment #8) > I've booted with nomsi, but there are no major differences in dmesg. > Hmmm, so when you try to reboot with the nomsi kernel you still get the "do_IRQ: 0.108 No irq handler for vector (irq -1)" messages and the hang? Try switching between the different options of the "PCI access mode" kernel configuration and also attach the kernel .config that you use. Thanks!
(In reply to comment #10) > (In reply to comment #8) > > I've booted with nomsi, but there are no major differences in dmesg. > > > > Hmmm, so when you try to reboot with the nomsi kernel you still get the > "do_IRQ: 0.108 No irq handler for vector (irq -1)" messages and the hang? > > Try switching between the different options of the "PCI access mode" kernel > configuration and also attach the kernel .config that you use. > > Thanks! > George, I use install-x86-minimal-20091013.iso This problem occurs with already built kernel which is used by the minimal cd. So I'm not able to change kernel build options.
Does this still happen with the latest installcd version?
RESOLVED NEEDINFO
