Bug#744193: linux-image-3.13-1-amd64: fails to shut down: handle_exit: unexpected exit_int_info ...
Hi Thorsten, On Wed, Apr 30, 2014 at 02:08:04PM +0200, Thorsten Glaser wrote: > On Mon, 14 Apr 2014, Ben Hutchings wrote: > > > Do you mean that when there is a VM that won't shutdown cleanly, > > rebooting the host consistently works but power-off consistently fails? > > After quite some more test runs (although I admit not trying > without the nvidia nonfree module), I can confirm that this is > indeed the case. Whenever my MirBSD VM (without ACPI) is still > running, shutting down consistently fails¹, and Alt-SysRq-O > produces lots of the error messages on the console. > > ① Although I wonder why the normal init script stop messages > are not shown on /dev/tty1, either… Assuming the hardware is still available, is this something you still can reproduce with recent kernels? If not I would be inclinded to close the bug. Regards, Salvatore
Bug#744193: linux-image-3.13-1-amd64: fails to shut down: handle_exit: unexpected exit_int_info ...
On Mon, 14 Apr 2014, Ben Hutchings wrote: Do you mean that when there is a VM that won't shutdown cleanly, rebooting the host consistently works but power-off consistently fails? After quite some more test runs (although I admit not trying without the nvidia nonfree module), I can confirm that this is indeed the case. Whenever my MirBSD VM (without ACPI) is still running, shutting down consistently fails¹, and Alt-SysRq-O produces lots of the error messages on the console. ① Although I wonder why the normal init script stop messages are not shown on /dev/tty1, either… bye, //mirabilos -- tarent solutions GmbH Rochusstraße 2-4, D-53123 Bonn • http://www.tarent.de/ Tel: +49 228 54881-393 • Fax: +49 228 54881-235 HRB 5168 (AG Bonn) • USt-ID (VAT): DE122264941 Geschäftsführer: Dr. Stefan Barth, Kai Ebenrett, Boris Esser, Alexander Steeg -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#744193: linux-image-3.13-1-amd64: fails to shut down: handle_exit: unexpected exit_int_info ...
On Mon, 14 Apr 2014, Ben Hutchings wrote: Do you mean that when there is a VM that won't shutdown cleanly, rebooting the host consistently works but power-off consistently fails? Sorry, no. I meant: without a VM that will not respond to ACPI shutdown events, “sudo poweroff” works. I’ll test a bit in the next few days as to the consistency of this behaviour. bye, //mirabilos -- tarent solutions GmbH Rochusstraße 2-4, D-53123 Bonn • http://www.tarent.de/ Tel: +49 228 54881-393 • Fax: +49 228 54881-235 HRB 5168 (AG Bonn) • USt-ID (VAT): DE122264941 Geschäftsführer: Dr. Stefan Barth, Kai Ebenrett, Boris Esser, Alexander Steeg -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#744193: linux-image-3.13-1-amd64: fails to shut down: handle_exit: unexpected exit_int_info ...
On Fri, 11 Apr 2014, Ben Hutchings wrote: I typed “sudo poweroff” as usual on Debian… the system switched to the text console and mostly hung. Is this reproducible when not using the nvidia module? Hrm. I’d have to try, but first a quick shot… [.xxx] handle_exit: unexpected exit_int_info 0x8028 exit_code 0x78 This repeated over and over. I eventuall pulled external power. The system previously had been running for 2 days and a bit, with the same kernel image version. [...] That error message comes from AMD support code in KVM. I don't know why it would appear when trying to power-off. … I still had a VM running in kvm/libvirt, which would not respond to normal ACPI shutdown commands. Maybe this is the cause of this issue? bye, //mirabilos -- tarent solutions GmbH Rochusstraße 2-4, D-53123 Bonn • http://www.tarent.de/ Tel: +49 228 54881-393 • Fax: +49 228 54881-235 HRB 5168 (AG Bonn) • USt-ID (VAT): DE122264941 Geschäftsführer: Dr. Stefan Barth, Kai Ebenrett, Boris Esser, Alexander Steeg -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#744193: linux-image-3.13-1-amd64: fails to shut down: handle_exit: unexpected exit_int_info ...
On Mon, 14 Apr 2014, Thorsten Glaser wrote: … I still had a VM running in kvm/libvirt, which would not respond to normal ACPI shutdown commands. Maybe this is the cause of this issue? FWIW, I was able to reboot without a VM “hanging”, just fine. bye, //mirabilos -- tarent solutions GmbH Rochusstraße 2-4, D-53123 Bonn • http://www.tarent.de/ Tel: +49 228 54881-393 • Fax: +49 228 54881-235 HRB 5168 (AG Bonn) • USt-ID (VAT): DE122264941 Geschäftsführer: Dr. Stefan Barth, Kai Ebenrett, Boris Esser, Alexander Steeg -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#744193: linux-image-3.13-1-amd64: fails to shut down: handle_exit: unexpected exit_int_info ...
On Mon, 2014-04-14 at 10:34 +0200, Thorsten Glaser wrote: On Mon, 14 Apr 2014, Thorsten Glaser wrote: … I still had a VM running in kvm/libvirt, which would not respond to normal ACPI shutdown commands. Maybe this is the cause of this issue? FWIW, I was able to reboot without a VM “hanging”, just fine. Do you mean that when there is a VM that won't shutdown cleanly, rebooting the host consistently works but power-off consistently fails? Ben. -- Ben Hutchings I say we take off; nuke the site from orbit. It's the only way to be sure. signature.asc Description: This is a digitally signed message part
Bug#744193: linux-image-3.13-1-amd64: fails to shut down: handle_exit: unexpected exit_int_info ...
Package: src:linux Version: 3.13.7-1 Severity: normal Hi *, I had to reboot to cleanse my system of running KDE, dbus, etc. again (since KDEPIM didn’t want to “see” new incoming eMails… this used to work better in KDE 3… but offtopic for here), and since reboots heal problems anyway, and since living in Debian sid has lots of library updates under the hood… anyway, I wanted to reboot. I typed “sudo poweroff” as usual on Debian… the system switched to the text console and mostly hung. I tried a few SysRq keys such as ‘w’, ‘l’, ‘e’, ‘f’, ‘m’, ‘t’… but “This SysRq operation is disabled.” – why? (Should I open a separate bugreport for this? This cannot be!) With Alt-SysRq-S+U+S+O I at least got the system off, right? No. After the Sync, Umount, Sync, which worked fine, the Off only made the kernel print the following line in an endless loop, præfixed by the time in brackets (which did change, just fine): [.xxx] handle_exit: unexpected exit_int_info 0x8028 exit_code 0x78 This repeated over and over. I eventuall pulled external power. The system previously had been running for 2 days and a bit, with the same kernel image version. -- Package-specific info: ** Version: Linux version 3.13-1-amd64 (debian-ker...@lists.debian.org) (gcc version 4.8.2 (Debian 4.8.2-16) ) #1 SMP Debian 3.13.7-1 (2014-03-25) ** Command line: BOOT_IMAGE=/boot/vmlinuz-3.13-1-amd64 root=/dev/mapper/vg--tglase-lv--tglase ro rootdelay=5 ** Tainted: PO (4097) * Proprietary module has been loaded. * Out-of-tree module has been loaded. ** Kernel log: [7.316208] disk 0, wo:0, o:1, dev:sda2 [7.316209] disk 1, wo:0, o:1, dev:sdb2 [7.331080] md1: unknown partition table [7.343563] device-mapper: uevent: version 1.0.3 [7.343659] device-mapper: ioctl: 4.27.0-ioctl (2013-10-30) initialised: dm-de...@redhat.com [7.346120] random: lvm urandom read with 77 bits of entropy available [7.357361] bio: create slab bio-1 at 1 [7.501644] PM: Starting manual resume from disk [7.501714] PM: Hibernation image partition 8:17 present [7.501715] PM: Looking for hibernation image. [7.501865] PM: Image not found (code -22) [7.501866] PM: Hibernation image not present or could not be loaded. [7.527331] EXT4-fs (dm-0): orphan cleanup on readonly fs [7.691454] random: nonblocking pool is initialized [7.827108] EXT4-fs (dm-0): 13 orphan inodes deleted [7.827168] EXT4-fs (dm-0): recovery complete [8.132412] EXT4-fs (dm-0): mounted filesystem with ordered data mode. Opts: (null) [ 10.340879] systemd-udevd[402]: starting version 204 [ 11.664792] wmi: Mapper loaded [ 11.684061] input: Power Button as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input4 [ 11.684137] ACPI: Power Button [PWRB] [ 11.684223] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input5 [ 11.684298] ACPI: Power Button [PWRF] [ 11.685584] ACPI: processor limited to max C-state 1 [ 11.841457] parport_pc 00:05: reported by Plug and Play ACPI [ 11.841583] parport0: PC-style at 0x378 (0x778), irq 7 [PCSPP,TRISTATE] [ 11.991571] acpi-cpufreq: overriding BIOS provided _PSD data [ 12.177759] ACPI Warning: 0x0b00-0x0b07 SystemIO conflicts with Region \SOR1 1 (20131115/utaddress-251) [ 12.177954] ACPI Warning: 0x0b00-0x0b07 SystemIO conflicts with Region \SMRG 2 (20131115/utaddress-251) [ 12.178141] ACPI Warning: 0x0b00-0x0b07 SystemIO conflicts with Region \_SB_.PCI0.SBRG.ASOC.SMRG 3 (20131115/utaddress-251) [ 12.178328] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver [ 12.200474] EDAC MC: Ver: 3.0.0 [ 12.201694] MCE: In-kernel MCE decoding enabled. [ 12.202815] AMD64 EDAC driver v3.4.0 [ 12.202922] EDAC amd64: DRAM ECC disabled. [ 12.202997] EDAC amd64: ECC disabled in the BIOS or no ECC capability, module will not load. [ 12.202997] Either enable ECC checking or force module loading by setting 'ecc_enable_override'. [ 12.202997] (Note that use of the override may cause unknown side effects.) [ 12.418358] input: PC Speaker as /devices/platform/pcspkr/input/input6 [ 12.484617] sp5100_tco: SP5100/SB800 TCO WatchDog Timer Driver v0.05 [ 12.484781] sp5100_tco: PCI Revision ID: 0x3c [ 12.484868] sp5100_tco: failed to find MMIO address, giving up. [ 12.665554] kvm: Nested Virtualization enabled [ 12.665619] kvm: Nested Paging enabled [ 12.776817] input: HDA ATI SB Front Headphone as /devices/pci:00/:00:14.2/sound/card0/input15 [ 12.776995] input: HDA ATI SB Line Out Side as /devices/pci:00/:00:14.2/sound/card0/input14 [ 12.777129] input: HDA ATI SB Line Out CLFE as /devices/pci:00/:00:14.2/sound/card0/input13 [ 12.777262] input: HDA ATI SB Line Out Surround as /devices/pci:00/:00:14.2/sound/card0/input12 [ 12.777395] input: HDA ATI SB Line Out Front as
Bug#744193: linux-image-3.13-1-amd64: fails to shut down: handle_exit: unexpected exit_int_info ...
Control: tag -1 moreinfo On Fri, 2014-04-11 at 11:03 +0200, Thorsten Glaser wrote: Package: src:linux Version: 3.13.7-1 Severity: normal Hi *, I had to reboot to cleanse my system of running KDE, dbus, etc. again (since KDEPIM didn’t want to “see” new incoming eMails… this used to work better in KDE 3… but offtopic for here), and since reboots heal problems anyway, and since living in Debian sid has lots of library updates under the hood… anyway, I wanted to reboot. I typed “sudo poweroff” as usual on Debian… the system switched to the text console and mostly hung. Is this reproducible when not using the nvidia module? I tried a few SysRq keys such as ‘w’, ‘l’, ‘e’, ‘f’, ‘m’, ‘t’… but “This SysRq operation is disabled.” – why? (Should I open a separate bugreport for this? This cannot be!) This is controlled by sysctl kernel.sysrq. No bug report is required. With Alt-SysRq-S+U+S+O I at least got the system off, right? No. After the Sync, Umount, Sync, which worked fine, the Off only made the kernel print the following line in an endless loop, præfixed by the time in brackets (which did change, just fine): [.xxx] handle_exit: unexpected exit_int_info 0x8028 exit_code 0x78 This repeated over and over. I eventuall pulled external power. The system previously had been running for 2 days and a bit, with the same kernel image version. [...] That error message comes from AMD support code in KVM. I don't know why it would appear when trying to power-off. Ben. -- Ben Hutchings I'm not a reverse psychological virus. Please don't copy me into your sig. signature.asc Description: This is a digitally signed message part
