https://bugzilla.novell.com/show_bug.cgi?id=439461 User meissner@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=439461#c1 Marcus Meissner changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |meissner@novell.com, seife@novell.com AssignedTo|bnc-team-screening@forge.provo.novell.com |trenn@novell.com --- Comment #1 from Marcus Meissner 2008-10-28 05:35:04 MDT --- Seife or Trenn most likely guilty ;) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=439461 User deckel@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=439461#c4 Christian Deckelmann changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|FIXED | --- Comment #4 from Christian Deckelmann 2008-10-29 13:13:20 MDT --- The new kernel doesn't work either. Well, in fact it works once, but at the second resume it seems I have to press some keys for progress. As soon as I press a key if moves forward to stop then again until I press a key. Looks like these key hits would generate an interrupt or something like that. At the third resume even that doesn't help. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=439461 User r2s2@gmx.de added comment https://bugzilla.novell.com/show_bug.cgi?id=439461#c6 Roland Schulz changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |r2s2@gmx.de --- Comment #6 from Roland Schulz 2008-10-30 10:14:55 MDT --- I also have the problem that s2ram works great with 2.6.25.16-0.1 but crashes after the update to 2.6.25.18. I reverted back to the .16 kernel and it works again. A bios update didn't help to make suspend work with .18. s2ram -n output wiht .18: Machine matched entry 387: sys_vendor = 'LENOVO' sys_product = '8897*' sys_version = '' bios_version = '' Fixes: 0x3 S3_BIOS S3_MODE This machine can be identified by: sys_vendor = "LENOVO" sys_product = "8897CTO" sys_version = "ThinkPad T61" bios_version = "7LETC4WW (2.24 )" It seems that bug 439353 is a duplicate of this bug not of the other bug which has been closed. This is without docking station. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=439461 User rjw@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=439461#c8 --- Comment #8 from Rafael Wysocki 2008-10-30 13:47:45 MDT --- Well, I would check the upstream -stable branch on which kernel-pae-2.6.25.18-0.2 is based (BTW, is "pae" reserved for 32-bit kernel? I hope it is). -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=439461 User pavel@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=439461#c10 --- Comment #10 from Pavel Machek 2008-10-30 14:19:19 MDT --- If pressing keys makes it continue, that sounds like nohz problem. Maybe "nohz=off highres=off" helps? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=439461 User deckel@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=439461#c12 --- Comment #12 from Christian Deckelmann 2008-10-30 16:33:51 MDT --- Pressing keys helped in my tests only once. At the next resume from StR it didn't help anymore. In my case it is a PAE kernel because YaST decided to install that kernel flavour as my system has a CPU which supports then NX functionalty. Or the equivalent on intel architecture. There are bugs against YaST where this behaviour is documented. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=439461 User deckel@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=439461#c14 Christian Deckelmann changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |meik.piepmeyer@web.de --- Comment #14 from Christian Deckelmann 2008-11-02 04:42:05 MDT --- *** Bug 440856 has been marked as a duplicate of this bug. *** https://bugzilla.novell.com/show_bug.cgi?id=440856 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=439461 User rjw@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=439461#c16 --- Comment #16 from Rafael Wysocki 2008-11-02 10:21:22 MDT --- It certainly would be helpful if someone having this problem could test the vanilla 2.6.25.18 kernel and see if it's reproducible with that one. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=439461 User meissner@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=439461#c18 --- Comment #18 from Marcus Meissner 2008-11-02 14:43:48 MDT --- Meik: can you please test vanilla 2.6.25.16 too? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=439461 Pavel Machek changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=439461 User pavel@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=439461#c21 --- Comment #21 from Pavel Machek 2008-11-03 02:10:58 MDT --- I went through 2.6.25.16->18 changelogs, and: This one could be it but then it would probably not be widespread: commit 8e023f85b670c9f6008df675b6b213025b3387b3 Author: Yinghai Lu Date: Fri Aug 22 17:40:05 2008 +0000 x86: work around MTRR mask setting commit 38cc1c3df77c1bb739a4766788eb9fa49f16ffdf upstream Joshua Hoblitt reported that only 3 GB of his 16 GB of RAM is usable. Booting with mtrr_show showed us the BIOS-initialized MTRR settings - which are all wrong. Timer/clockevents issues could also be it, and I believe I actually debugged something like that... but not in -stable: commit 22e4330618d27748cc69b62d3c96223bcefe6c6c Author: Thomas Gleixner Date: Sat Sep 6 03:06:08 2008 +0200 x86: HPET: read back compare register before reading counter commit 72d43d9bc9210d24d09202eaf219eac09e17b339 upstream After fixing the u32 thinko I sill had occasional hickups on ATI chipsets with small deltas. There seems to be a delay between writing the compare register and the transffer to the internal register which triggers the interrupt. Reading back the value makes sure, that it hit the internal match register befor we compare against the counter value. Signed-off-by: Thomas Gleixner Signed-off-by: Greg Kroah-Hartman commit 59ff733c6b6ef547bb09a9902020750dfbb2200f Author: Thomas Gleixner Date: Sat Sep 6 03:03:32 2008 +0200 x86: HPET fix moronic 32/64bit thinko commit f7676254f179eac6b5244a80195ec8ae0e9d4606 upstream We use the HPET only in 32bit mode because: 1) some HPETs are 32bit only 2) on i386 there is no way to read/write the HPET atomic 64bit wide The HPET code unification done by the "moron of the year" did not take into account that unsigned long is different on 32 and 64 bit. This thinko results in a possible endless loop in the clockevents code, when the return comparison fails due to the 64bit/332bit unawareness. unsigned long cnt = (u32) hpet_read() + delta can wrap over 32bit. but the final compare will fail and return -ETIME causing endless loops. Signed-off-by: Thomas Gleixner Signed-off-by: Greg Kroah-Hartman commit 9d29a18def727d9e0d5c656cfc86a278988b7926 Author: Thomas Gleixner Date: Sat Sep 6 03:01:45 2008 +0200 clockevents: broadcast fixup possible waiters commit 7300711e8c6824fcfbd42a126980ff50439d8dd0 upstream Until the C1E patches arrived there where no users of periodic broadcast before switching to oneshot mode. Now we need to trigger a possible waiter for a periodic broadcast when switching to oneshot mode. Otherwise we can starve them for ever. Signed-off-by: Thomas Gleixner Signed-off-by: Greg Kroah-Hartman commit 4f8e2bf785bd7e5ba9b93a7d5ad5c18ba409a199 Author: Thomas Gleixner Date: Wed Sep 3 21:37:24 2008 +0000 HPET: make minimum reprogramming delta useful commit 7cfb0435330364f90f274a26ecdc5f47f738498c upstream The minimum reprogramming delta was hardcoded in HPET ticks, which is stupid as it does not work with faster running HPETs. The C1E idle patches made this prominent on AMD/RS690 chipsets, where the HPET runs with 25MHz. Set it to 5us which seems to be a reasonable value and fixes the problems on the bug reporters machines. We have a further sanity check now in the clock events, which increases the delta when it is not sufficient. Signed-off-by: Thomas Gleixner Tested-by: Luiz Fernando N. Capitulino Tested-by: Dmitry Nezhevenko Signed-off-by: Ingo Molnar Signed-off-by: Greg Kroah-Hartman commit 19ab6cbbf02a7d4ca81ef44cc856ce11870e202b Author: Thomas Gleixner Date: Wed Sep 3 21:37:14 2008 +0000 clockevents: prevent endless loop lockup commit 1fb9b7d29d8e85ba3196eaa7ab871bf76fc98d36 upstream The C1E/HPET bug reports on AMDX2/RS690 systems where tracked down to a too small value of the HPET minumum delta for programming an event. The clockevents code needs to enforce an interrupt event on the clock event device in some cases. The enforcement code was stupid and naive, as it just added the minimum delta to the current time and tried to reprogram the device. When the minimum delta is too small, then this loops forever. Add a sanity check. Allow reprogramming to fail 3 times, then print a warning and double the minimum delta value to make sure, that this does not happen again. Use the same function for both tick-oneshot and tick-broadcast code. Signed-off-by: Thomas Gleixner Signed-off-by: Ingo Molnar Signed-off-by: Greg Kroah-Hartman commit ffa4da2a25bb4ac08f710ac99827baf48a8f8d57 Author: Thomas Gleixner Date: Wed Sep 3 21:37:08 2008 +0000 clockevents: prevent multiple init/shutdown commit 9c17bcda991000351cb2373f78be7e4b1c44caa3 upstream While chasing the C1E/HPET bugreports I went through the clock events code inch by inch and found that the broadcast device can be initialized and shutdown multiple times. Multiple shutdowns are not critical, but useless waste of time. Multiple initializations are simply broken. Another CPU might have the device in use already after the first initialization and the second init could just render it unusable again. Signed-off-by: Thomas Gleixner Signed-off-by: Ingo Molnar Signed-off-by: Greg Kroah-Hartman commit e73068458bf253c2e738cd55080c3a54c61037ef Author: Thomas Gleixner Date: Wed Sep 3 21:37:03 2008 +0000 clockevents: enforce reprogram in oneshot setup commit 7205656ab48da29a95d7f55e43a81db755d3cb3a upstream In tick_oneshot_setup we program the device to the given next_event, but we do not check the return value. We need to make sure that the device is programmed enforced so the interrupt handler engine starts working. Split out the reprogramming function from tick_program_event() and call it with the device, which was handed in to tick_setup_oneshot(). Set the force argument, so the devices is firing an interrupt. Signed-off-by: Thomas Gleixner Signed-off-by: Ingo Molnar Signed-off-by: Greg Kroah-Hartman commit fbbece349081a689d5687d9ebc769a847fdf423a Author: Thomas Gleixner Date: Wed Sep 3 21:36:57 2008 +0000 clockevents: prevent endless loop in periodic broadcast handler commit d4496b39559c6d43f83e4c08b899984f8b8089b5 upstream The reprogramming of the periodic broadcast handler was broken, when the first programming returned -ETIME. The clockevents code stores the new expiry value in the clock events device next_event field only when the programming time has not been elapsed yet. The loop in question calculates the new expiry value from the next_event value and therefor never increases. Signed-off-by: Thomas Gleixner Signed-off-by: Ingo Molnar Signed-off-by: Greg Kroah-Hartman commit 6141266c43db890ada7df589358b8553de2e6322 Author: Venkatesh Pallipadi Date: Wed Sep 3 21:36:50 2008 +0000 clockevents: prevent clockevent event_handler ending up handler_noop commit 7c1e76897492d92b6a1c2d6892494d39ded9680c upstream There is a ordering related problem with clockevents code, due to which clockevents_register_device() called after tickless/highres switch will not work. The new clockevent ends up with clockevents_handle_noop as event handler, resulting in no timer activity. The problematic path seems to be * old device already has hrtimer_interrupt as the event_handler * new clockevent device registers with a higher rating * tick_check_new_device() is called * clockevents_exchange_device() gets called * old->event_handler is set to clockevents_handle_noop * tick_setup_device() is called for the new device * which sets new->event_handler using the old->event_handler which is noop. Change the ordering so that new device inherits the proper handler. This does not have any issue in normal case as most likely all the clockevent devices are setup before the highres switch. But, can potentially be affecting some corner case where HPET force detect happens after the highres switch. This was a problem with HPET in MSI mode code that we have been experimenting with. Signed-off-by: Venkatesh Pallipadi Signed-off-by: Shaohua Li Signed-off-by: Thomas Gleixner Signed-off-by: Ingo Molnar Signed-off-by: Greg Kroah-Hartman ..and of course, EC is always suspect: commit dc317ed0f9cb83f616b95ae6abdba44832c60f39 Author: Zhao Yakui Date: Tue Sep 23 13:38:13 2008 +0800 ACPI: Avoid bogus EC timeout when EC is in Polling mode commit 9d699ed92a459cb408e2577e8bbeabc8ec3989e1 upstream When EC is in Polling mode, OS will check the EC status continually by using the following source code: clear_bit(EC_FLAGS_WAIT_GPE, &ec->flags); while (time_before(jiffies, delay)) { if (acpi_ec_check_status(ec, event)) return 0; msleep(1); } But msleep is realized by the function of schedule_timeout. At the same time although one process is already waken up by some events, it won't be scheduled immediately. So maybe there exists the following phenomena: a. The current jiffies is already after the predefined jiffies. But before timeout happens, OS has no chance to check the EC status again. b. If preemptible schedule is enabled, maybe preempt schedule will happen before checking loop. When the process is resumed again, maybe timeout already happens, which means that OS has no chance to check the EC status. In such case maybe EC status is already what OS expects when timeout happens. But OS has no chance to check the EC status and regards it as AE_TIME. So it will be more appropriate that OS will try to check the EC status again when timeout happens. If the EC status is what we expect, it won't be regarded as timeout. Only when the EC status is not what we expect, it will be regarded as timeout, which means that EC controller can't give a response in time. http://bugzilla.kernel.org/show_bug.cgi?id=9823 http://bugzilla.kernel.org/show_bug.cgi?id=11141 Signed-off-by: Zhao Yakui Signed-off-by: Zhang Rui Signed-off-by: Andi Kleen Signed-off-by: Greg Kroah-Hartman ..actually, can you try 2.6.27 kernel and/or opensuse11.1 beta? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=439461 User meik.piepmeyer@web.de added comment https://bugzilla.novell.com/show_bug.cgi?id=439461#c23 --- Comment #23 from Meik Piepmeyer 2008-11-03 04:01:51 MDT --- vanilla 2.6.25.17 works, too. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=439461 User meik.piepmeyer@web.de added comment https://bugzilla.novell.com/show_bug.cgi?id=439461#c25 --- Comment #25 from Meik Piepmeyer 2008-11-03 05:34:10 MDT --- Should be possible, but I am not familar with patching the kernel, reverting commits etc. If you'd give me so advice, I'll try with that. By the way, would'd it be clever trying out the commits as listed by Pavel first? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=439461 User rjw@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=439461#c27 Rafael Wysocki changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|pavel@novell.com |rjw@novell.com --- Comment #27 from Rafael Wysocki 2008-11-05 05:49:25 MST --- Sorry for the delay, I got distracted by some other urgencies. I'd like you to binary search the patches applied to the -stable kernel after 2.6.25.17 and before 2.6.25.18. I'll attach the instructions to the next comment. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=439461 User meik.piepmeyer@web.de added comment https://bugzilla.novell.com/show_bug.cgi?id=439461#c29 --- Comment #29 from Meik Piepmeyer 2008-11-05 12:34:09 MST --- Here is the output: ffa4da2a25bb4ac08f710ac99827baf48a8f8d57 is first bad commit commit ffa4da2a25bb4ac08f710ac99827baf48a8f8d57 Author: Thomas Gleixner Date: Wed Sep 3 21:37:08 2008 +0000 clockevents: prevent multiple init/shutdown commit 9c17bcda991000351cb2373f78be7e4b1c44caa3 upstream While chasing the C1E/HPET bugreports I went through the clock events code inch by inch and found that the broadcast device can be initialized and shutdown multiple times. Multiple shutdowns are not critical, but useless waste of time. Multiple initializations are simply broken. Another CPU might have the device in use already after the first initialization and the second init could just render it unusable again. Signed-off-by: Thomas Gleixner Signed-off-by: Ingo Molnar Signed-off-by: Greg Kroah-Hartman :040000 040000 6bb2c37ac2a45ce8f97a37094949575a63750e5c eda80c4051ed1fb945a997732253385a7c9982bf M kernel -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=439461 User meik.piepmeyer@web.de added comment https://bugzilla.novell.com/show_bug.cgi?id=439461#c31 --- Comment #31 from Meik Piepmeyer 2008-11-11 18:53:34 MST --- Any progress on this? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=439461 User rjw@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=439461#c33 --- Comment #33 from Rafael Wysocki 2008-11-15 06:27:59 MST --- We're not ignoring it, but we haven't put any new comments here just yet. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=439461 User deckel@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=439461#c35 Christian Deckelmann changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |oneukum@novell.com --- Comment #35 from Christian Deckelmann 2008-11-16 08:27:38 MST --- JFYI: The workaround from Tejun works for me. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=439461 User rjw@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=439461#c37 --- Comment #37 from Rafael Wysocki 2008-11-16 09:25:14 MST --- (In reply to comment #36 from Tejun Heo)

Dropping -pae- from the subject as it also happens on the default kernel. Also, the bisection result doesn't seem to agree with my hacky workaround of unloading ehci_hcd before suspend.

Hm, why exactly do you think it doesn't agree? Perhaps ehci_hcd is only necessary to trigger the issue. Have you tried with the bisected commit reverted? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=439461 User rjw@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=439461#c39 --- Comment #39 from Rafael Wysocki 2008-11-16 11:25:40 MST --- Well, no. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=439461 User rjw@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=439461#c41 Rafael Wysocki changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO Info Provider| |teheo@novell.com --- Comment #41 from Rafael Wysocki 2008-11-17 15:51:24 MST --- Does reverting the bisected patch help? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=439461 User teheo@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=439461#c43 --- Comment #43 from Tejun Heo 2008-11-18 23:24:34 MST --- Confirmed with SUSE kernel with the commit reverted too. http://htj.dyndns.org/export/testing/sl110-x86_64-bug439461_dbg0/kernel-defa... http://htj.dyndns.org/export/testing/sl110-x86_64-bug439461_dbg0/0001-revert... The commit couldn't be reverted by "patch -R -p1" so I did some manual editing. I'm not entirely sure it's correct tho. Anyways, with the above patch applied, resume works fine. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=439461 User rjw@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=439461#c45 --- Comment #45 from Rafael Wysocki 2008-11-23 05:36:56 MST --- Well, this is a regression in -stable and -stable regressions are (fortunately) rare, so it really is exceptional. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=439461 User pbaudis@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=439461#c47 --- Comment #47 from Petr Baudis 2008-11-23 06:12:50 MST --- Do you have some timeline of the update release, so that users can decide whether to wait further or roll their own solution? This bug really is super-annoying. :-( -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=439461 User rjw@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=439461#c51 Rafael Wysocki changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |m.koller@surfeu.at --- Comment #51 from Rafael Wysocki 2008-11-25 08:38:19 MST --- *** Bug 443279 has been marked as a duplicate of this bug. *** https://bugzilla.novell.com/show_bug.cgi?id=443279 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=439461 Rafael Wysocki changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|rjw@novell.com |gregkh@novell.com Status|NEEDINFO |NEW Info Provider|gregkh@novell.com | -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=439461 User gregkh@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=439461#c59 Greg Kroah-Hartman changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|gregkh@novell.com |fseidel@novell.com --- Comment #59 from Greg Kroah-Hartman 2009-01-08 17:01:08 MST --- Frank was going to check this in... -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=439461 User gregkh@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=439461#c63 Greg Kroah-Hartman changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED --- Comment #63 from Greg Kroah-Hartman 2009-01-14 09:07:21 MST --- The patch has been availble in our kernel-of-the-day package, right? And also, a 11.0 kernel update is already in the works, to be pushed out to all users soon, which will have this fix in it. Sorry, we just forgot to close this bug out. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=439461 User gregkh@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=439461#c65 Greg Kroah-Hartman changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution| |FIXED --- Comment #65 from Greg Kroah-Hartman 2009-01-14 15:22:16 MST --- Sorry, but no, that's not the way we use bugzilla. Otherwise we would have to go back and do major amounts of "close this bug" type work when we do releases. We close bugs when the fix is checked into our kernel tree, and it is publicly available, which this fix is, in the kernel-of-the-day package. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=439461 User swamp@suse.com added comment https://bugzilla.novell.com/show_bug.cgi?id=439461#c67 Swamp Script User changed: What |Removed |Added ---------------------------------------------------------------------------- Status Whiteboard| |maint:released:11.0:21569 --- Comment #67 from Swamp Script User 2009-01-20 04:58:13 MST --- Update released for: kernel-debug, kernel-default, kernel-docs, kernel-kdump, kernel-pae, kernel-ppc64, kernel-ps3, kernel-rt, kernel-rt_debug, kernel-source, kernel-syms, kernel-vanilla, kernel-xen Products: openSUSE 11.0 (debug, i386, ppc, x86_64) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.