Bug#691902: [squeeze-wheezy regression] Unable to shutdown via normal means
tags 691902 + upstream forwarded 691902 https://bugzilla.kernel.org/show_bug.cgi?id=44261 quit Janne Boman wrote: You might want to take a look at the changes between 13 and 14, because 3.2.13-1 is shutting down properly :) Thanks again for testing so quickly. Let's take this upstream. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#691902: [squeeze-wheezy regression] Unable to shutdown via normal means
Hi, did it the lazy way and installed linux-image-3.2.0-2-amd64 3.2.13-1 followed by 3.2.14-1 from the snapshots. You might want to take a look at the changes between 13 and 14, because 3.2.13-1 is shutting down properly :) Methods tried: - selecting shutdown from Gnome - issuing shutdown -h 0 happy hunting ;) On Sat, Nov 3, 2012 at 8:07 PM, Jonathan Nieder jrnie...@gmail.com wrote: found 691902 linux/3.6.4-1~experimental.1 quit Janne Boman wrote: acpidump dmesg attached 3.6 from experimental did not work... Thanks for checking so quickly. By did not work, you mean that after booting that kernel, shutting down caused the computer to reboot, right? Please test the pre-compiled 3.2.13-1 and 3.2.14-1 packages from http://snapshot.debian.org/package/linux-2.6/, or if you prefer, please test the attached patch against a 3.7-rc3 or newer kernel, for example by using the following directions: 0. prerequisites apt-get install git build-essential 1. get the kernel history, if you don't already have it git clone \ git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git 2. configure, build, test cd linux git fetch origin git checkout origin/master cp /boot/config-3.6-trunk-amd64 .config; # stock configuration scripts/config --disable DEBUG_INFO make localmodconfig; # optional: minimize configuration make deb-pkg; # optionally with -jnum for parallel build dpkg -i ../name of package; # as root shut down, unplug, remove battery, wait a few seconds restore power, boot shutdown -h now Hopefully it reproduces the bug, so 3. try the patch cd linux git revert 41c7f7424259 :wq make deb-pkg; # maybe with -j4 dpkg -i ../name of package; # as root ... power down completely, test it ... Hope that helps, Jonathan
Bug#691902: [squeeze-wheezy regression] Unable to shutdown via normal means
found 691902 linux-2.6/3.2.14-1 quit Janne Boman wrote: did it the lazy way and installed linux-image-3.2.0-2-amd64 3.2.13-1 followed by 3.2.14-1 from the snapshots. You might want to take a look at the changes between 13 and 14, because 3.2.13-1 is shutting down properly :) \o/ Let's take this upstream. I'll send instructions after breakfast. Ciao, Jonathan -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#691902: [squeeze-wheezy regression] Unable to shutdown via normal means
tags 691902 - moreinfo quit Janne Boman wrote: just installed wheezy (managed to get netinst cd working) Same restart issue persists. I attached the output from reportbug --template linux-image-$(uname -r), for this latest installation also. Methods that I tried for shutdown: - From Gnome - From terminal: shutdown -h now, halt, poweroff Lovely, thanks. Please attach full acpidump and dmesg output. If you get a chance to try 3.6.y from experimental, that would also be very useful. If we're lucky then d8e725f356fd ACPI: Ignore invalid _PSS entries, but use valid ones which is included in that version will fix this. Jonathan -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#691902: [squeeze-wheezy regression] Unable to shutdown via normal means
found 691902 linux/3.6.4-1~experimental.1 quit Janne Boman wrote: acpidump dmesg attached 3.6 from experimental did not work... Thanks for checking so quickly. By did not work, you mean that after booting that kernel, shutting down caused the computer to reboot, right? Please test the pre-compiled 3.2.13-1 and 3.2.14-1 packages from http://snapshot.debian.org/package/linux-2.6/, or if you prefer, please test the attached patch against a 3.7-rc3 or newer kernel, for example by using the following directions: 0. prerequisites apt-get install git build-essential 1. get the kernel history, if you don't already have it git clone \ git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git 2. configure, build, test cd linux git fetch origin git checkout origin/master cp /boot/config-3.6-trunk-amd64 .config; # stock configuration scripts/config --disable DEBUG_INFO make localmodconfig; # optional: minimize configuration make deb-pkg; # optionally with -jnum for parallel build dpkg -i ../name of package; # as root shut down, unplug, remove battery, wait a few seconds restore power, boot shutdown -h now Hopefully it reproduces the bug, so 3. try the patch cd linux git revert 41c7f7424259 :wq make deb-pkg; # maybe with -j4 dpkg -i ../name of package; # as root ... power down completely, test it ... Hope that helps, Jonathan From: Jonathan Nieder jrnie...@gmail.com Date: Sat, 3 Nov 2012 10:58:20 -0700 Subject: Revert rtc: Disable the alarm in the hardware (v2) This reverts commit 41c7f7424259ff11009449f87c95656f69f9b186, which should tell us whether Alessandro will want to know about these shutdown failures. Not signed off, only for testing. --- drivers/rtc/interface.c | 15 ++- 1 file changed, 2 insertions(+), 13 deletions(-) diff --git a/drivers/rtc/interface.c b/drivers/rtc/interface.c index 9592b936b71b..c11596b9ba4e 100644 --- a/drivers/rtc/interface.c +++ b/drivers/rtc/interface.c @@ -782,14 +782,6 @@ static int rtc_timer_enqueue(struct rtc_device *rtc, struct rtc_timer *timer) return 0; } -static void rtc_alarm_disable(struct rtc_device *rtc) -{ - if (!rtc-ops || !rtc-ops-alarm_irq_enable) - return; - - rtc-ops-alarm_irq_enable(rtc-dev.parent, false); -} - /** * rtc_timer_remove - Removes a rtc_timer from the rtc_device timerqueue * @rtc rtc device @@ -811,10 +803,8 @@ static void rtc_timer_remove(struct rtc_device *rtc, struct rtc_timer *timer) struct rtc_wkalrm alarm; int err; next = timerqueue_getnext(rtc-timerqueue); - if (!next) { - rtc_alarm_disable(rtc); + if (!next) return; - } alarm.time = rtc_ktime_to_tm(next-expires); alarm.enabled = 1; err = __rtc_set_alarm(rtc, alarm); @@ -877,8 +867,7 @@ again: err = __rtc_set_alarm(rtc, alarm); if (err == -ETIME) goto again; - } else - rtc_alarm_disable(rtc); + } mutex_unlock(rtc-ops_lock); } -- 1.8.0
Bug#691902: [squeeze-wheezy regression] Unable to shutdown via normal means
Janne Boman wrote: Got hit by this on the way... http://forums.debian.net/viewtopic.php?f=17t=60881 [Invalid release file: No entry for main/binary-amd64/Packages] Testing halted until this is resolved Yech. Is that reproducible? If so, please file an installation report (i.e., a bug report against the installation-report package) and include X-Debbugs-Cc: jrnie...@gmail.com in the header so I get a copy. It doesn't seem to be listed at http://www.debian.org/devel/debian-installer/errata so I don't think it's a known problem. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#691902: [squeeze-wheezy regression] Unable to shutdown via normal means
I'll try to find time between work and home :) my updates might take a while but I really would like to get these resolved. On Nov 2, 2012 8:47 AM, Jonathan Nieder jrnie...@gmail.com wrote: Janne Boman wrote: Got hit by this on the way... http://forums.debian.net/viewtopic.php?f=17t=60881 [Invalid release file: No entry for main/binary-amd64/Packages] Testing halted until this is resolved Yech. Is that reproducible? If so, please file an installation report (i.e., a bug report against the installation-report package) and include X-Debbugs-Cc: jrnie...@gmail.com in the header so I get a copy. It doesn't seem to be listed at http://www.debian.org/devel/debian-installer/errata so I don't think it's a known problem.
Bug#691902: [squeeze-wheezy regression] Unable to shutdown via normal means
Hi, just installed wheezy (managed to get netinst cd working) Same restart issue persists. I attached the output from reportbug --template linux-image-$(uname -r), for this latest installation also. Methods that I tried for shutdown: - From Gnome - From terminal: shutdown -h now, halt, poweroff BR -Janne On Fri, Nov 2, 2012 at 9:07 AM, Janne Boman janne.m.bo...@gmail.com wrote: I'll try to find time between work and home :) my updates might take a while but I really would like to get these resolved. On Nov 2, 2012 8:47 AM, Jonathan Nieder jrnie...@gmail.com wrote: Janne Boman wrote: Got hit by this on the way... http://forums.debian.net/viewtopic.php?f=17t=60881 [Invalid release file: No entry for main/binary-amd64/Packages] Testing halted until this is resolved Yech. Is that reproducible? If so, please file an installation report (i.e., a bug report against the installation-report package) and include X-Debbugs-Cc: jrnie...@gmail.com in the header so I get a copy. It doesn't seem to be listed at http://www.debian.org/devel/debian-installer/errata so I don't think it's a known problem. output_2 Description: Binary data
Bug#691902: [squeeze-wheezy regression] Unable to shutdown via normal means
Hi sorry but I have a problem I cannot remember if I installed the nvidia binary driver (installer from Nvidia site) or nvidia from nonfree repo... I have a spare hard drive that I can swap in and install wheezy, would that be ok? That way we would be testing stock wheezy against this hardware BR -Janne On Wed, Oct 31, 2012 at 10:00 PM, Jonathan Nieder jrnie...@gmail.com wrote: Janne Boman wrote: ouput attached. Thanks. Can you reproduce this using nouveau instead of nvidia? (Testing this would require disabling uvesafb temporarily.) If it works with nouveau, we can pass this on to the maintainers of the nvidia proprietary driver. If it fails with nouveau, too, that will help us bring this up with linux-kernel upstream. So either result is progress. Hope that helps, Jonathan -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#691902: [squeeze-wheezy regression] Unable to shutdown via normal means
Janne Boman wrote: I have a spare hard drive that I can swap in and install wheezy, would that be ok? That way we would be testing stock wheezy against this hardware That would be great. If you have time for it, don't forget to file an installation report: http://www.debian.org/releases/wheezy/amd64/apas04.html Thanks, Jonathan -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#691902: [squeeze-wheezy regression] Unable to shutdown via normal means
Ok, I'm going with this image: debian-wheezy-DI-b3-amd64-CD-1.iso (http://cdimage.debian.org/cdimage/wheezy_di_beta3/amd64/iso-cd/) On Thu, Nov 1, 2012 at 10:44 AM, Jonathan Nieder jrnie...@gmail.com wrote: That would be great. If you have time for it, don't forget to file an installation report: http://www.debian.org/releases/wheezy/amd64/apas04.html Thanks, Jonathan -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#691902: [squeeze-wheezy regression] Unable to shutdown via normal means
Got hit by this on the way... http://forums.debian.net/viewtopic.php?f=17t=60881 Testing halted until this is resolved On Nov 1, 2012 11:04 AM, Janne Boman janne.m.bo...@gmail.com wrote: Ok, I'm going with this image: debian-wheezy-DI-b3-amd64-CD-1.iso (http://cdimage.debian.org/cdimage/wheezy_di_beta3/amd64/iso-cd/) On Thu, Nov 1, 2012 at 10:44 AM, Jonathan Nieder jrnie...@gmail.com wrote: That would be great. If you have time for it, don't forget to file an installation report: http://www.debian.org/releases/wheezy/amd64/apas04.html Thanks, Jonathan
Bug#691902: [squeeze-wheezy regression] Unable to shutdown via normal means
reassign 691902 src:linux 3.2.23-1 quit Hi Janne, Janne Boman wrote: 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! Thanks for reporting it. Please attach output from reportbug --template linux-image-$(uname -r), which will tell us a little more about your setup. Hope that helps, Jonathan -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#691902: [squeeze-wheezy regression] Unable to shutdown via normal means
Hi, ouput attached. On Wed, Oct 31, 2012 at 8:54 PM, Jonathan Nieder jrnie...@gmail.com wrote: reassign 691902 src:linux 3.2.23-1 quit Hi Janne, Janne Boman wrote: 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! Thanks for reporting it. Please attach output from reportbug --template linux-image-$(uname -r), which will tell us a little more about your setup. Hope that helps, Jonathan output Description: Binary data
Bug#691902: [squeeze-wheezy regression] Unable to shutdown via normal means
Janne Boman wrote: ouput attached. Thanks. Can you reproduce this using nouveau instead of nvidia? (Testing this would require disabling uvesafb temporarily.) If it works with nouveau, we can pass this on to the maintainers of the nvidia proprietary driver. If it fails with nouveau, too, that will help us bring this up with linux-kernel upstream. So either result is progress. Hope that helps, Jonathan -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org