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): > > [xxxx.xxx] handle_exit: unexpected exit_int_info 0x80000028 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
