[opensuse-kernel] KOTD 2.6.27.12-HEAD_20090122183653_0d7eb945-default
When booting 2.6.27.12-HEAD_20090122183653_0d7eb945-default x86_64 on my system the system freezes immediately with black screen. With both normal and safe settings. Nothing on the screen, nothing in the logs. 2.6.27.12- HEAD_20090120200141_5646759d works fine on that system. How to get useful information for a bug report in that case ? -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kernel+help@opensuse.org
On Friday 23 January 2009 19:39:14 Markus Koßmann wrote:
When booting 2.6.27.12-HEAD_20090122183653_0d7eb945-default x86_64 on my system the system freezes immediately with black screen. With both normal and safe settings. Nothing on the screen, nothing in the logs. 2.6.27.12- HEAD_20090120200141_5646759d works fine on that system. How to get useful information for a bug report in that case ?
Do you know if any earlier version of the available KOTD rpms is working for you? This would be helpful information .. since this would bring it down to hopefully only few changes which potential caused the regression. best regards, Daniel -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kernel+help@opensuse.org
Am Freitag, 23. Januar 2009 schrieb Daniel Gollub:
On Friday 23 January 2009 19:39:14 Markus Koßmann wrote:
When booting 2.6.27.12-HEAD_20090122183653_0d7eb945-default x86_64 on my system the system freezes immediately with black screen. With both normal and safe settings. Nothing on the screen, nothing in the logs. 2.6.27.12- HEAD_20090120200141_5646759d works fine on that system. How to get useful information for a bug report in that case ?
Do you know if any earlier version of the available KOTD rpms is working for you? This would be helpful information .. since this would bring it down to hopefully only few changes which potential caused the regression.
As I said : the previous version 2.6.27.12- HEAD_20090120200141_5646759d works fine -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kernel+help@opensuse.org
On Friday 23 January 2009 19:53:59 Markus Koßmann wrote:
Am Freitag, 23. Januar 2009 schrieb Daniel Gollub:
On Friday 23 January 2009 19:39:14 Markus Koßmann wrote:
When booting 2.6.27.12-HEAD_20090122183653_0d7eb945-default x86_64 on my system the system freezes immediately with black screen. With both normal and safe settings. Nothing on the screen, nothing in the logs. 2.6.27.12- HEAD_20090120200141_5646759d works fine on that system. How to get useful information for a bug report in that case ?
Do you know if any earlier version of the available KOTD rpms is working for you? This would be helpful information .. since this would bring it down to hopefully only few changes which potential caused the regression.
As I said : the previous version 2.6.27.12- HEAD_20090120200141_5646759d works fine
Oops, i have missed that - sorry. I guess this information is already very valuable in a bug report. Did you already try boot with vga=normal? best regards, Daniel -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kernel+help@opensuse.org
On Friday 23 January 2009 19:53:59 Markus Koßmann wrote:
Am Freitag, 23. Januar 2009 schrieb Daniel Gollub:
On Friday 23 January 2009 19:39:14 Markus Koßmann wrote:
When booting 2.6.27.12-HEAD_20090122183653_0d7eb945-default x86_64 on my system the system freezes immediately with black screen. With both normal and safe settings. Nothing on the screen, nothing in the logs. 2.6.27.12- HEAD_20090120200141_5646759d works fine on that system. How to get useful information for a bug report in that case ?
Do you know if any earlier version of the available KOTD rpms is working for you? This would be helpful information .. since this would bring it down to hopefully only few changes which potential caused the regression.
As I said : the previous version 2.6.27.12- HEAD_20090120200141_5646759d works fine
Wild guess - add to the kernel command-line "nohpet". Not quite sure if the highres=off in the failsafe already disables hpet. But there is also some hpet related patch between the two version - maybe worth a try. best regards, Daniel -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kernel+help@opensuse.org
Am Freitag, 23. Januar 2009 schrieb Daniel Gollub:
On Friday 23 January 2009 19:53:59 Markus Koßmann wrote:
Am Freitag, 23. Januar 2009 schrieb Daniel Gollub:
On Friday 23 January 2009 19:39:14 Markus Koßmann wrote:
When booting 2.6.27.12-HEAD_20090122183653_0d7eb945-default x86_64 on my system the system freezes immediately with black screen. With both normal and safe settings. Nothing on the screen, nothing in the logs. 2.6.27.12- HEAD_20090120200141_5646759d works fine on that system. How to get useful information for a bug report in that case ?
Do you know if any earlier version of the available KOTD rpms is working for you? This would be helpful information .. since this would bring it down to hopefully only few changes which potential caused the regression.
As I said : the previous version 2.6.27.12- HEAD_20090120200141_5646759d works fine
Wild guess - add to the kernel command-line "nohpet". Not quite sure if the highres=off in the failsafe already disables hpet. But there is also some hpet related patch between the two version - maybe worth a try.
I think you are right, the hpet change causes the trouble. With disabled
splash screen I see now messages from hpet:
hpet: increasing min_delta_ns to
On Friday 23 January 2009 21:17:38 Markus Koßmann wrote:
Am Freitag, 23. Januar 2009 schrieb Daniel Gollub:
On Friday 23 January 2009 19:53:59 Markus Koßmann wrote:
Am Freitag, 23. Januar 2009 schrieb Daniel Gollub:
On Friday 23 January 2009 19:39:14 Markus Koßmann wrote:
When booting 2.6.27.12-HEAD_20090122183653_0d7eb945-default x86_64 on my system the system freezes immediately with black screen. With both normal and safe settings. Nothing on the screen, nothing in the logs. 2.6.27.12- HEAD_20090120200141_5646759d works fine on that system. How to get useful information for a bug report in that case ?
Do you know if any earlier version of the available KOTD rpms is working for you? This would be helpful information .. since this would bring it down to hopefully only few changes which potential caused the regression.
As I said : the previous version 2.6.27.12- HEAD_20090120200141_5646759d works fine
Wild guess - add to the kernel command-line "nohpet". Not quite sure if the highres=off in the failsafe already disables hpet. But there is also some hpet related patch between the two version - maybe worth a try.
I think you are right, the hpet change causes the trouble. With disabled splash screen I see now messages from hpet: hpet: increasing min_delta_ns to
nsec The message is repeated after some other messages and the number becomes higher and higher with every repetition. Jeff, instead of bisecting, could you provide a kernel with hpet change backed out ? Or do the hpet messages allready prove that the hpet change is the cuplrit ?
Did you try if "nohpet" on the command line help? I have following changes in mind, which were between 5646759d...0d7eb945: 1c94d71a9bd77342bda0b3c5f51a08acd15a1473 - patches.arch/x86_64-hpet-64bit- timer.patch: allow 64-bit mode for HPET Timer0 (bnc#456700). (fix compilation on i386 and add hpet64 to kernel-parameters.txt) 2cd19d8a25b33f1ade697a7be2f1908ac08c2b51 - patches.arch/x86_64-hpet-64bit- timer.patch: allow 64-bit mode for HPET Timer0 (bnc#456700). best regards, Daniel -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kernel+help@opensuse.org
Am Freitag, 23. Januar 2009 schrieb Daniel Gollub:
On Friday 23 January 2009 21:17:38 Markus Koßmann wrote:
I think you are right, the hpet change causes the trouble. With disabled splash screen I see now messages from hpet: hpet: increasing min_delta_ns to
nsec The message is repeated after some other messages and the number becomes higher and higher with every repetition. Jeff, instead of bisecting, could you provide a kernel with hpet change backed out ? Or do the hpet messages allready prove that the hpet change is the cuplrit ? Did you try if "nohpet" on the command line help?
I'am writing this mail now from 2.6.27.12-HEAD_20090122183653_0d7eb945 booted with nohpet option -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kernel+help@opensuse.org
On Friday 23 January 2009 21:50:21 Markus Koßmann wrote:
Am Freitag, 23. Januar 2009 schrieb Daniel Gollub:
On Friday 23 January 2009 21:17:38 Markus Koßmann wrote:
I think you are right, the hpet change causes the trouble. With disabled splash screen I see now messages from hpet: hpet: increasing min_delta_ns to
nsec The message is repeated after some other messages and the number becomes higher and higher with every repetition. Jeff, instead of bisecting, could you provide a kernel with hpet change backed out ? Or do the hpet messages allready prove that the hpet change is the cuplrit ? Did you try if "nohpet" on the command line help?
I'am writing this mail now from 2.6.27.12-HEAD_20090122183653_0d7eb945 booted with nohpet option
Could create a bug on bugzilla.novell.com and mention the kernel parameter which work around the issue - as well as the two kernel version. I started a kernel build which backout the hpet64 patch .. as soon as i have uploaded i let you know where to find the package. best regards, Daniel -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kernel+help@opensuse.org
Am Freitag, 23. Januar 2009 schrieb Daniel Gollub:
On Friday 23 January 2009 21:50:21 Markus Koßmann wrote:
Am Freitag, 23. Januar 2009 schrieb Daniel Gollub:
On Friday 23 January 2009 21:17:38 Markus Koßmann wrote:
I think you are right, the hpet change causes the trouble. With disabled splash screen I see now messages from hpet: hpet: increasing min_delta_ns to
nsec The message is repeated after some other messages and the number becomes higher and higher with every repetition. Jeff, instead of bisecting, could you provide a kernel with hpet change backed out ? Or do the hpet messages allready prove that the hpet change is the cuplrit ? Did you try if "nohpet" on the command line help?
I'am writing this mail now from 2.6.27.12-HEAD_20090122183653_0d7eb945 booted with nohpet option
Could create a bug on bugzilla.novell.com and mention the kernel parameter which work around the issue - as well as the two kernel version.
I started a kernel build which backout the hpet64 patch .. as soon as i have uploaded i let you know where to find the package.
Opened #469017. I will do further testing tomorrow evening. -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kernel+help@opensuse.org
On Fri, 23 Jan 2009, Markus Koßmann wrote:
Opened #469017. I will do further testing tomorrow evening.
I think I have found a bug in patches.arch/x86_64-hpet-64bit-timer.patch. I will fix it and provide a kernel to test, probably today evening CET. Let's continue in bugzilla. -- Jiri Kosina SUSE Labs
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Markus Koßmann wrote:
When booting 2.6.27.12-HEAD_20090122183653_0d7eb945-default x86_64 on my system the system freezes immediately with black screen. With both normal and safe settings. Nothing on the screen, nothing in the logs. 2.6.27.12- HEAD_20090120200141_5646759d works fine on that system. How to get useful information for a bug report in that case ?
Ok, the broken one corresponds to: * Thu Jan 22 2009 jbenc@suse.cz - - patches.fixes/iwlwifi-fix-rs_get_rate-oops.patch: iwlwifi: fix rs_get_rate WARN_ON() (bnc#456002). - - Reordered wireless patches to group together patches touching the same driver. The working one corresponds to: * Tue Jan 20 2009 gregkh@suse.de - - clean up patch fuzz after 2.6.27.12 inclusion. Unfortunately there are 51 commits between those two releases. Fortunately, the process that cleans up old builds internally doesn't seem to be running right now. I'll start posting kernels externally for testing. I've posted a bunch of kernels at http://ftp.suse.com/pub/people/jeffm/suse/testpkgs/mkossmann/ Start by testing the one in that directory, and then follow the is_good/is_bad links until you're at the end and report the results. You should need to test, at maximum, 5 kernels. - -Jeff - -- Jeff Mahoney SUSE Labs -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iEYEARECAAYFAkl6G1AACgkQLPWxlyuTD7LVRwCglp2gudpMaclReYQpRfvc45Jw aLYAnicjAgDku2z29WAjR+hTZ8sc930p =JeIz -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kernel+help@opensuse.org
Le vendredi 23 janvier 2009, Jeff Mahoney a écrit :
Markus Koßmann wrote:
When booting 2.6.27.12-HEAD_20090122183653_0d7eb945-default x86_64 on my system the system freezes immediately with black screen. With both normal and safe settings. Nothing on the screen, nothing in the logs. 2.6.27.12- HEAD_20090120200141_5646759d works fine on that system. How to get useful information for a bug report in that case ?
Ok, the broken one corresponds to: * Thu Jan 22 2009 jbenc@suse.cz - patches.fixes/iwlwifi-fix-rs_get_rate-oops.patch: iwlwifi: fix rs_get_rate WARN_ON() (bnc#456002). - Reordered wireless patches to group together patches touching the same driver.
The working one corresponds to: * Tue Jan 20 2009 gregkh@suse.de - clean up patch fuzz after 2.6.27.12 inclusion.
Unfortunately there are 51 commits between those two releases. Fortunately, the process that cleans up old builds internally doesn't seem to be running right now. I'll start posting kernels externally for testing.
I've posted a bunch of kernels at http://ftp.suse.com/pub/people/jeffm/suse/testpkgs/mkossmann/
Start by testing the one in that directory, and then follow the is_good/is_bad links until you're at the end and report the results. You should need to test, at maximum, 5 kernels.
Wow, remote bisecting, I wouldn't have dared :D -- Jean Delvare Suse L3 -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kernel+help@opensuse.org
participants (5)
-
Daniel Gollub -
Jean Delvare -
Jeff Mahoney -
Jiri Kosina -
Markus Koßmann