Bug#691902: Unable to shutdown Debian Wheezy via normal means
Hi Joachim, yes I did but it didn't help. Although I have to say I also have a usb mouse and keyboard connected to the USB port. I'm unable to unplug it because the pc is in a datacenter. On 15/12/2014 6:45, Joachim Fahrner wrote: Hi Maarten, did you try uninstalling acpi-support-base? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#691902: Unable to shutdown Debian Wheezy via normal means
Dear, I have the same problem on my debian wheezy system. Tried with various kernels from kernel.org (3.12.15, 3.14.26, 3.18) all reboot the system instead of shutdown. The only way to shutdown the system is via halt -fp Motherboard is Gigabyte GA-990FXA-UD5 with AMD FX(tm)-6200 Six-Core Processor Any news on this issue? KR, Maarten -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#691902: Unable to shutdown Debian Wheezy via normal means
Another accidental discovery: I have started to use a USB mouse recently, and when I leave the mouse plugged in when shutting down, the problem reoccurs. When I click "Shutdown," then unplug the mouse, power down completes successfully. (Always assuming that I run only Debian between power on and power down.) Another observation: With the USB mouse plugged in, Ubuntu 14.04 runs into the same issue. So, Ubuntu will power down OK, whether or not I ran a mix of Debian and Ubuntu since last power on. It will, however, fail to power down when I leave the USB mouse plugged in. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#691902: Unable to shutdown Debian Wheezy via normal means
Hmmm... The problem is apparently only partially resolved. This is a triple-boot computer, which has Ubuntu 10.04, Ubuntu 14.04, and Debian 7 installed. If I boot either of the Ubuntu systems, then reboot and start Debian, power down from Debian will fail. If I run only Debian after power on, then power down from Debian is OK. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#691902: Unable to shutdown Debian Wheezy via normal means
I encounter this issue as well. acpi-support acpi-support-base pcmciautils powertop task-laptop Of these packages, only "acpi-support-base" was installed on my system. After I removed it, the problem was solved. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#691902: Unable to shutdown Debian Wheezy via normal means
Am Samstag, den 31.05.2014, 11:33 +0200 schrieb Jochen Fahrner: > some more info on this. I installed kernel 3.12 and 3.14 from wheezy > backports, and both don't have this shutdown problem. > > Maybe it has something to do with acpi. If I boot kernel 3.2 with acpi=off, > system is halted on shutdown and I can manually power off. I have to correct: newer kernels also have this problem, but not on _every_ shutdown. After some googling, I found many hints that laptop-mode-tools can be the cause of this reboots. I don't have laptop-mode-tools installed, but since my Lenovo Ideacentre is not a laptop, I removed some other laptop related packages: acpi-support acpi-support-base pcmciautils powertop task-laptop That seems to solve the problem. Shutdown was working fine now for several times with kernel 3.2. Ubuntu kernels also don't have this problem, but I cannot use Ubuntu kernels because the kernel header package dependencies are not compatible with Debian, and I need them because of virtualbox kernel modules. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#691902: Unable to shutdown Debian Wheezy via normal means
Hi, some more info on this. I installed kernel 3.12 and 3.14 from wheezy backports, and both don't have this shutdown problem. Maybe it has something to do with acpi. If I boot kernel 3.2 with acpi=off, system is halted on shutdown and I can manually power off. Jochen -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#691902: Unable to shutdown Debian Wheezy via normal means
One more observation that may help: When I boot from grub directly into single user mode, and then do "shutdown -h now", it is correctly powering off. When I boot into multi user mode, then switch to single user mode via "init 1", then do "shutdown -h now", it is rebooting. Jochen -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#691902: Unable to shutdown Debian Wheezy via normal means
Hi, I just switched from Ubuntu to Debian 7.5 (Gnome 3) and have the same issue. Kernel is 3.2.0-4-amd64 #1 SMP Debian 3.2.57-3+deb7u1 x86_64 GNU/Linux. I was working with Ubuntu for several years and never had such a problem with any kernel. I was using Ubuntu 12.04 with LTS enablement stack, so I got many different version of the kernel, starting at 3.2 and ending with 3.11. After upgrade to Ubuntu 14.04 I used kernel 3.13.0 and also had no problem. So, maybe this is not an issue with the kernel, but with something else in Debians shutdown procedure? Maybe the setting of RTC in shutdown procedure? (I think Ubuntu does not set it on shutdown) Jochen -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#691902: Unable to shutdown Debian Wheezy via normal means
Package: src:linux Followup-For: Bug #691902 Dear Maintainer, I am unable to shutdown the computer by any means other then pressing the power button. I tried poweroff, shutdown -h -p, shutdown from KDE, etc. I tried kernel 2.6.32-5-amd64 and that works, i.e., it shuts down correctly. I also tried to comment the (halt -p -f ) command in K12halt at runlevel 0 and then do a halt. In this situation it restarts after shutdown as well. When I halt the system before running: K03network-manager K03nslcd K03postgresql K03slapd K03spamassassin K03virtualbox-ose K04sendsigs K05rsyslog K06umountnfs.sh K07nfs-common K07rpcbind K08hwclock.sh K08networking K09umountfs 10mdadm-raid K10umountroot K11mdadm-waitidle the PC powers off correctly. I tried some kernel paramters like acpi=noirq, acpi=force to no avail. Any help or workaround would be greatly appreciated Cheers Michael -- Package-specific info: ** Version: Linux version 3.2.0-4-amd64 (debian-ker...@lists.debian.org) (gcc version 4.6.3 (Debian 4.6.3-14) ) #1 SMP Debian 3.2.46-1 ** Command line: BOOT_IMAGE=/vmlinuz-3.2.0-4-amd64 root=UUID=ff63dec0-9e54-497f-a57a-ad4ee06a7b98 ro acpi=noirq quiet splash ** Tainted: PO (4097) * Proprietary module has been loaded. * Out-of-tree module has been loaded. ** Kernel log: [6.162796] EDAC amd64: DRAM ECC enabled. [6.162802] EDAC amd64: K8 revE or earlier detected (node 1). [6.162870] EDAC amd64: CS0: Registered Double data rate SDRAM [6.162873] EDAC amd64: CS2: Registered Double data rate SDRAM [6.162913] EDAC MC1: Giving out device to 'amd64_edac' 'K8': DEV :00:19.2 [6.163497] EDAC PCI0: Giving out device to module 'amd64_edac' controller 'EDAC PCI controller': DEV ':00:18.2' (POLLED) [6.171224] ACPI: resource :00:07.2 [io 0xcc00-0xcc1f] conflicts with ACPI region ECIO [io 0xcc00-0xcc1f] [6.171228] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver [6.200461] fglrx: module license 'Proprietary. (C) 2002 - ATI Technologies, Starnberg, GERMANY' taints kernel. [6.200469] Disabling lock debugging due to kernel taint [6.470779] AMD768 RNG detected [6.487937] [fglrx] Maximum main memory to use for locked dma buffers: 8830 MBytes. [6.488437] [fglrx] vendor: 1002 device: 94cc count: 1 [6.489094] [fglrx] ioport: bar 4, base 0xb000, size: 0x100 [6.489147] pci :04:00.0: PCI->APIC IRQ transform: INT A -> IRQ 28 [6.489157] pci :04:00.0: setting latency timer to 64 [6.489616] [fglrx] Kernel PAT support is enabled [6.489651] [fglrx] module loaded - fglrx 8.97.2 [Nov 16 2012] with 1 minors [6.496798] powernow-k8: Power state transitions not supported [6.496807] powernow-k8: Power state transitions not supported [6.517563] parport_pc 00:0a: reported by Plug and Play ACPI [6.517688] parport0: PC-style at 0x378 (0x778), irq 7 [PCSPP,TRISTATE,EPP] [6.556089] ACPI: resource amd756_smbus [io 0x10e0-0x10ef] conflicts with ACPI region PMIO [io 0x1000-0x10fe] [6.556094] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver [6.612377] parport_pc :02:02.0: PCI->APIC IRQ transform: INT A -> IRQ 26 [6.612384] PCI parallel port detected: 1409:7268, I/O at 0x8c00(0x8480), IRQ 26 [6.612414] parport1: PC-style at 0x8c00 (0x8480), irq 26 [PCSPP,TRISTATE] [6.736515] psmouse serio1: logips2pp: Detected unknown Logitech mouse model 127 [7.140491] snd_hda_intel :04:00.1: PCI->APIC IRQ transform: INT B -> IRQ 28 [7.140576] snd_hda_intel :04:00.1: setting latency timer to 64 [7.287432] input: ImExPS/2 Logitech Explorer Mouse as /devices/platform/i8042/serio1/input/input4 [ 10.168023] hda-intel: azx_get_response timeout, switching to polling mode: last cmd=0x000f0001 [ 10.185655] HDMI status: Codec=0 Pin=3 Presence_Detect=0 ELD_Valid=0 [ 10.185814] input: HDA ATI HDMI HDMI/DP,pcm=3 as /devices/pci:00/:00:0b.0/:03:03.0/:04:00.1/sound/card0/input5 [ 11.574752] Adding 979960k swap on /dev/sdb2. Priority:-1 extents:1 across:979960k [ 11.63] Adding 979960k swap on /dev/sdc2. Priority:-2 extents:1 across:979960k [ 12.210687] EXT3-fs (md1): using internal journal [ 12.326219] loop: module loaded [ 12.584849] vboxdrv: Found 2 processor cores. [ 12.585026] vboxdrv: fAsync=0 offMin=0x5c0 offMax=0x1a1c [ 12.585176] vboxdrv: TSC mode is 'asynchronous', kernel timer mode is 'normal'. [ 12.585179] vboxdrv: Successfully loaded version 4.2.16 (interface 0x001a0005). [ 14.849437] kjournald starting. Commit interval 5 seconds [ 14.877552] EXT3-fs (md0): using internal journal [ 14.877560] EXT3-fs (md0): mounted filesystem with ordered data mode [ 14.921990] kjournald starting. Commit interval 5 seconds [ 14.956090] EXT3-fs (md2): using internal journal [ 14.956094] EXT3-fs (md2): mounted filesystem with ordered data mode [ 14.981408
Bug#691902: Unable to shutdown Debian Wheezy via normal means
On Wed, 2012-10-31 at 09:19 +0200, Janne Boman wrote: > Package: linux-image-3.2.0-3-amd64 > Severity: Important > > Dear maintainters, > I'm unable to shutdown my system via normal means. The system > completes the shutdown process, all hardware lights are off, but then > somehow it restarts. > > Selecting "Shutdown" from Gnome, issuing "shutdown -h now", "poweroff" > or "halt" from command line all result in the same behavior: shutdown > followed by a restart. > The only way to shutdown my system is to issue "halt -pf" or to press > the power button in the Grub menu. > I'm using a fairly stock wheezy install. > > The reason I'm filing this against linux-image-3.2.0.3-amd64: shutdown > works when I install the default amd64 kernel from squeeze! > > I tried to use reportbug for this, but I get no confirmation mail... Perhaps some problem with the system mail configuration on your computer? > Please advice what additional info to provide, I'm happy to help :) Please use 'reportbug -N 691902' to provide extra information, but when asked whether to 'Submit this report', choose 'Save it in a temporary file and quit' (q). Then send the contents of that file using your usual mail program. Ben. -- Ben Hutchings I'm always amazed by the number of people who take up solipsism because they heard someone else explain it. - E*Borg on alt.fan.pratchett signature.asc Description: This is a digitally signed message part
Bug#691902: Unable to shutdown Debian Wheezy via normal means
Package: linux-image-3.2.0-3-amd64 Severity: Important Dear maintainters, I'm unable to shutdown my system via normal means. The system completes the shutdown process, all hardware lights are off, but then somehow it restarts. Selecting "Shutdown" from Gnome, issuing "shutdown -h now", "poweroff" or "halt" from command line all result in the same behavior: shutdown followed by a restart. The only way to shutdown my system is to issue "halt -pf" or to press the power button in the Grub menu. I'm using a fairly stock wheezy install. The reason I'm filing this against linux-image-3.2.0.3-amd64: shutdown works when I install the default amd64 kernel from squeeze! I tried to use reportbug for this, but I get no confirmation mail... Please advice what additional info to provide, I'm happy to help :) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
