* Re: Linux 2.6.22-rc4 [not found] <alpine.LFD.0.98.0706042040350.23741@woody.linux-foundation.org> @ 2007-06-05 18:54 ` Michal Piotrowski [not found] ` <4665B169.2030803@googlemail.com> 1 sibling, 0 replies; 14+ messages in thread From: Michal Piotrowski @ 2007-06-05 18:54 UTC (permalink / raw) To: Linus Torvalds; +Cc: linux-pm, Linux Kernel Mailing List, Pavel Machek Linus Torvalds pisze: > So -rc4 is out there now, hopefully shrinking the regression list further. > It is too stable for me. aio_dio_bugs ok aiostress ok bash_shared_mapping ok cpu_hotplug ok fio ok fsx ok interbench ok iozone ok isic ok linus_stress ok the latest ltp ok this looks harmless [ 116.733327] PM: suspend-to-disk mode set to 'shutdown' [ 116.738849] swsusp: Basic memory bitmaps created [ 116.745353] Stopping tasks ... WARNING: at /home/devel/linux-git/kernel/lockdep.c:2414 check_flags() [ 116.754921] [<c0404fbf>] show_trace_log_lvl+0x1a/0x2f [ 116.754937] [<c0405bd6>] show_trace+0x12/0x14 [ 116.754947] [<c0405c5d>] dump_stack+0x16/0x18 [ 116.754957] [<c043c3e5>] check_flags+0x95/0x143 [ 116.754967] [<c043f158>] lock_acquire+0x29/0x82 [ 116.754977] [<c06313a7>] _spin_lock+0x35/0x42 [ 116.754990] [<c044894a>] refrigerator+0x14/0xc6 [ 116.755002] [<c042d4b3>] get_signal_to_deliver+0x33/0x397 [ 116.755016] [<c0403597>] do_notify_resume+0x94/0x6ed [ 116.755029] [<c0404099>] work_notifysig+0x13/0x1a [ 116.755044] ======================= [ 116.755052] irq event stamp: 69 [ 116.755060] hardirqs last enabled at (69): [<c04040f9>] syscall_exit_work+0x11/0x26 [ 116.755084] hardirqs last disabled at (68): [<c0403fdd>] syscall_exit+0x9/0x1a [ 116.755109] softirqs last enabled at (0): [<c042150c>] copy_process+0x4dd/0x1286 [ 116.755139] softirqs last disabled at (0): [<00000000>] 0x0 [ 116.945776] done. http://www.stardust.webpages.pl/files/tbf/bitis-gabonica/2.6.22-rc4/git-dmesg http://www.stardust.webpages.pl/files/tbf/bitis-gabonica/2.6.22-rc4/git-config Regards, Michal -- "Najbardziej brakowało mi twojego milczenia." -- Andrzej Sapkowski "Coś więcej" ^ permalink raw reply [flat|nested] 14+ messages in thread
[parent not found: <4665B169.2030803@googlemail.com>]
* Re: Linux 2.6.22-rc4 [not found] ` <4665B169.2030803@googlemail.com> @ 2007-06-05 19:26 ` Linus Torvalds 2007-06-05 19:37 ` Ingo Molnar 2007-06-07 14:46 ` Jan Engelhardt 0 siblings, 2 replies; 14+ messages in thread From: Linus Torvalds @ 2007-06-05 19:26 UTC (permalink / raw) To: Michal Piotrowski, Ingo Molnar Cc: linux-pm, Linux Kernel Mailing List, Pavel Machek On Tue, 5 Jun 2007, Michal Piotrowski wrote: > > It is too stable for me. I wish all our testers were you ;) > this looks harmless > > [ 116.733327] PM: suspend-to-disk mode set to 'shutdown' > [ 116.738849] swsusp: Basic memory bitmaps created > [ 116.745353] Stopping tasks ... WARNING: at /home/devel/linux-git/kernel/lockdep.c:2414 check_flags() > [ 116.754921] [<c0404fbf>] show_trace_log_lvl+0x1a/0x2f > [ 116.754937] [<c0405bd6>] show_trace+0x12/0x14 > [ 116.754947] [<c0405c5d>] dump_stack+0x16/0x18 > [ 116.754957] [<c043c3e5>] check_flags+0x95/0x143 > [ 116.754967] [<c043f158>] lock_acquire+0x29/0x82 > [ 116.754977] [<c06313a7>] _spin_lock+0x35/0x42 > [ 116.754990] [<c044894a>] refrigerator+0x14/0xc6 > [ 116.755002] [<c042d4b3>] get_signal_to_deliver+0x33/0x397 > [ 116.755016] [<c0403597>] do_notify_resume+0x94/0x6ed > [ 116.755029] [<c0404099>] work_notifysig+0x13/0x1a > [ 116.755044] ======================= > [ 116.755052] irq event stamp: 69 > [ 116.755060] hardirqs last enabled at (69): [<c04040f9>] syscall_exit_work+0x11/0x26 > [ 116.755084] hardirqs last disabled at (68): [<c0403fdd>] syscall_exit+0x9/0x1a > [ 116.755109] softirqs last enabled at (0): [<c042150c>] copy_process+0x4dd/0x1286 > [ 116.755139] softirqs last disabled at (0): [<00000000>] 0x0 > [ 116.945776] done. > > http://www.stardust.webpages.pl/files/tbf/bitis-gabonica/2.6.22-rc4/git-dmesg > http://www.stardust.webpages.pl/files/tbf/bitis-gabonica/2.6.22-rc4/git-config Well, it's harmless in the sense that "yeah, the system still works", but it does seem to be a real bug. We have hardware interrupts disabled when we _think_ we should have them on, so our irq tracking is off. Ingo, do you see what's up? It looks like we got a signal to a process that just got created, is the setup stuff for "tsk->hardirqs_enabled" perhaps off a bit? Linus ^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: Linux 2.6.22-rc4 2007-06-05 19:26 ` Linus Torvalds @ 2007-06-05 19:37 ` Ingo Molnar 2007-06-05 19:50 ` Linus Torvalds ` (2 more replies) 2007-06-07 14:46 ` Jan Engelhardt 1 sibling, 3 replies; 14+ messages in thread From: Ingo Molnar @ 2007-06-05 19:37 UTC (permalink / raw) To: Linus Torvalds Cc: Peter Zijlstra, Linux Kernel Mailing List, Pavel Machek, linux-pm, Michal Piotrowski * Linus Torvalds <torvalds@linux-foundation.org> wrote: > > this looks harmless > > > > [ 116.733327] PM: suspend-to-disk mode set to 'shutdown' [ > > 116.738849] swsusp: Basic memory bitmaps created [ 116.745353] > > Stopping tasks ... WARNING: at > > /home/devel/linux-git/kernel/lockdep.c:2414 check_flags() > > [ 116.755052] irq event stamp: 69 > > [ 116.755060] hardirqs last enabled at (69): [<c04040f9>] syscall_exit_work+0x11/0x26 > > [ 116.755084] hardirqs last disabled at (68): [<c0403fdd>] syscall_exit+0x9/0x1a > > [ 116.755109] softirqs last enabled at (0): [<c042150c>] copy_process+0x4dd/0x1286 > > [ 116.755139] softirqs last disabled at (0): [<00000000>] 0x0 > > [ 116.945776] done. > Well, it's harmless in the sense that "yeah, the system still works", > but it does seem to be a real bug. We have hardware interrupts > disabled when we _think_ we should have them on, so our irq tracking > is off. > > Ingo, do you see what's up? It looks like we got a signal to a process > that just got created, is the setup stuff for "tsk->hardirqs_enabled" > perhaps off a bit? hm. I cannot see the source of the bug at the moment, but here's my analysis so far: the last event that irqtrace got was #69, and that was a 'hardirqs on' in syscall_exit_work. After that we did a 'hardirqs off' without properly tracking that via irqtrace. Next time we got an irqtrace event (event 70) the assert caught up with us and turned off lockdep and backed out of that function. This was in: > [ 116.754957] [<c043c3e5>] check_flags+0x95/0x143 > [ 116.754967] [<c043f158>] lock_acquire+0x29/0x82 > [ 116.754977] [<c06313a7>] _spin_lock+0x35/0x42 > [ 116.754990] [<c044894a>] refrigerator+0x14/0xc6 > [ 116.755002] [<c042d4b3>] get_signal_to_deliver+0x33/0x397 > [ 116.755016] [<c0403597>] do_notify_resume+0x94/0x6ed > [ 116.755029] [<c0404099>] work_notifysig+0x13/0x1a isnt the refrigerator() suspend related? Perhaps suspend disables irqs somewhere that we forgot to track? a new thread gets its hardirqs_enabled this way: #ifdef __ARCH_WANT_INTERRUPTS_ON_CTXSW p->hardirqs_enabled = 1; #else p->hardirqs_enabled = 0; #endif on i386 __ARCH_WANT_INTERRUPTS_ON_CTXSW is off so it starts with 0. We set this up in copy_process() so there's no chance this task can run without this initialized. Ingo ^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: Linux 2.6.22-rc4 2007-06-05 19:37 ` Ingo Molnar @ 2007-06-05 19:50 ` Linus Torvalds 2007-06-05 20:16 ` Pavel Machek 2007-06-05 20:19 ` Pavel Machek [not found] ` <20070605201954.GB4424@elf.ucw.cz> 2 siblings, 1 reply; 14+ messages in thread From: Linus Torvalds @ 2007-06-05 19:50 UTC (permalink / raw) To: Ingo Molnar Cc: Peter Zijlstra, Linux Kernel Mailing List, Pavel Machek, linux-pm, Michal Piotrowski On Tue, 5 Jun 2007, Ingo Molnar wrote: > > isnt the refrigerator() suspend related? Perhaps suspend disables irqs > somewhere that we forgot to track? There _is_ something strange there. For that whole sequence to trigger, the current task has to have the TIF_FREEZE bit set, but I don't see why it would be during shutdown. Linus ^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: Linux 2.6.22-rc4 2007-06-05 19:50 ` Linus Torvalds @ 2007-06-05 20:16 ` Pavel Machek 0 siblings, 0 replies; 14+ messages in thread From: Pavel Machek @ 2007-06-05 20:16 UTC (permalink / raw) To: Linus Torvalds Cc: Michal Piotrowski, Linux Kernel Mailing List, Ingo Molnar, linux-pm, Peter Zijlstra Hi! > > isnt the refrigerator() suspend related? Perhaps suspend disables irqs > > somewhere that we forgot to track? > > There _is_ something strange there. For that whole sequence to trigger, > the current task has to have the TIF_FREEZE bit set, but I don't see why > it would be during shutdown. [ 116.733327] PM: suspend-to-disk mode set to 'shutdown' [ 116.738849] swsusp: Basic memory bitmaps created [ 116.745353] Stopping tasks ... WARNING: at /home/devel/linux-git/kernel/lockdep.c:2414 check_flags() [ 116.754921] [<c0404fbf>] show_trace_log_lvl+0x1a/0x2f [ 116.754937] [<c0405bd6>] show_trace+0x12/0x14 No, he's not shutting down, he's trying to snapshot his machine. 'shutdown' will be done at end of hibernation, _way_ after this. Pavel -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html ^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: Linux 2.6.22-rc4 2007-06-05 19:37 ` Ingo Molnar 2007-06-05 19:50 ` Linus Torvalds @ 2007-06-05 20:19 ` Pavel Machek [not found] ` <20070605201954.GB4424@elf.ucw.cz> 2 siblings, 0 replies; 14+ messages in thread From: Pavel Machek @ 2007-06-05 20:19 UTC (permalink / raw) To: Ingo Molnar Cc: Michal Piotrowski, Linux Kernel Mailing List, linux-pm, Linus Torvalds, Peter Zijlstra Hi! > > > [ 116.733327] PM: suspend-to-disk mode set to 'shutdown' [ > > > 116.738849] swsusp: Basic memory bitmaps created [ 116.745353] > > > Stopping tasks ... WARNING: at > > > /home/devel/linux-git/kernel/lockdep.c:2414 check_flags() > > > > [ 116.755052] irq event stamp: 69 > > > [ 116.755060] hardirqs last enabled at (69): [<c04040f9>] syscall_exit_work+0x11/0x26 > > > [ 116.755084] hardirqs last disabled at (68): [<c0403fdd>] syscall_exit+0x9/0x1a > > > [ 116.755109] softirqs last enabled at (0): [<c042150c>] copy_process+0x4dd/0x1286 > > > [ 116.755139] softirqs last disabled at (0): [<00000000>] 0x0 > > > [ 116.945776] done. > > > Well, it's harmless in the sense that "yeah, the system still works", > > but it does seem to be a real bug. We have hardware interrupts > > disabled when we _think_ we should have them on, so our irq tracking > > is off. > > > > Ingo, do you see what's up? It looks like we got a signal to a process > > that just got created, is the setup stuff for "tsk->hardirqs_enabled" > > perhaps off a bit? > > hm. I cannot see the source of the bug at the moment, but here's my > analysis so far: > > the last event that irqtrace got was #69, and that was a 'hardirqs on' > in syscall_exit_work. After that we did a 'hardirqs off' without > properly tracking that via irqtrace. Next time we got an irqtrace event > (event 70) the assert caught up with us and turned off lockdep and > backed out of that function. This was in: > > > [ 116.754957] [<c043c3e5>] check_flags+0x95/0x143 > > [ 116.754967] [<c043f158>] lock_acquire+0x29/0x82 > > [ 116.754977] [<c06313a7>] _spin_lock+0x35/0x42 > > [ 116.754990] [<c044894a>] refrigerator+0x14/0xc6 > > [ 116.755002] [<c042d4b3>] get_signal_to_deliver+0x33/0x397 > > [ 116.755016] [<c0403597>] do_notify_resume+0x94/0x6ed > > [ 116.755029] [<c0404099>] work_notifysig+0x13/0x1a > > isnt the refrigerator() suspend related? Perhaps suspend disables irqs > somewhere that we forgot to track? refrigerator is suspend related, but I do not think it does any interrupt magic. We do magic later in hibernation process. This is in kernel/power/process.c, we have spinlock_irqsave there, but that's pretty much it AFAICT. Pavel -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html ^ permalink raw reply [flat|nested] 14+ messages in thread
[parent not found: <20070605201954.GB4424@elf.ucw.cz>]
* Re: Linux 2.6.22-rc4 [not found] ` <20070605201954.GB4424@elf.ucw.cz> @ 2007-06-05 22:01 ` Rafael J. Wysocki 0 siblings, 0 replies; 14+ messages in thread From: Rafael J. Wysocki @ 2007-06-05 22:01 UTC (permalink / raw) To: Pavel Machek Cc: Peter Zijlstra, Linux Kernel Mailing List, Ingo Molnar, Linus Torvalds, linux-pm, Michal Piotrowski On Tuesday, 5 June 2007 22:19, Pavel Machek wrote: > Hi! > > > > > [ 116.733327] PM: suspend-to-disk mode set to 'shutdown' [ > > > > 116.738849] swsusp: Basic memory bitmaps created [ 116.745353] > > > > Stopping tasks ... WARNING: at > > > > /home/devel/linux-git/kernel/lockdep.c:2414 check_flags() > > > > > > [ 116.755052] irq event stamp: 69 > > > > [ 116.755060] hardirqs last enabled at (69): [<c04040f9>] syscall_exit_work+0x11/0x26 > > > > [ 116.755084] hardirqs last disabled at (68): [<c0403fdd>] syscall_exit+0x9/0x1a > > > > [ 116.755109] softirqs last enabled at (0): [<c042150c>] copy_process+0x4dd/0x1286 > > > > [ 116.755139] softirqs last disabled at (0): [<00000000>] 0x0 > > > > [ 116.945776] done. > > > > > Well, it's harmless in the sense that "yeah, the system still works", > > > but it does seem to be a real bug. We have hardware interrupts > > > disabled when we _think_ we should have them on, so our irq tracking > > > is off. > > > > > > Ingo, do you see what's up? It looks like we got a signal to a process > > > that just got created, is the setup stuff for "tsk->hardirqs_enabled" > > > perhaps off a bit? > > > > hm. I cannot see the source of the bug at the moment, but here's my > > analysis so far: > > > > the last event that irqtrace got was #69, and that was a 'hardirqs on' > > in syscall_exit_work. After that we did a 'hardirqs off' without > > properly tracking that via irqtrace. Next time we got an irqtrace event > > (event 70) the assert caught up with us and turned off lockdep and > > backed out of that function. This was in: > > > > > [ 116.754957] [<c043c3e5>] check_flags+0x95/0x143 > > > [ 116.754967] [<c043f158>] lock_acquire+0x29/0x82 > > > [ 116.754977] [<c06313a7>] _spin_lock+0x35/0x42 > > > [ 116.754990] [<c044894a>] refrigerator+0x14/0xc6 > > > [ 116.755002] [<c042d4b3>] get_signal_to_deliver+0x33/0x397 > > > [ 116.755016] [<c0403597>] do_notify_resume+0x94/0x6ed > > > [ 116.755029] [<c0404099>] work_notifysig+0x13/0x1a > > > > isnt the refrigerator() suspend related? Perhaps suspend disables irqs > > somewhere that we forgot to track? > > refrigerator is suspend related, but I do not think it does any > interrupt magic. We do magic later in hibernation process. > > This is in kernel/power/process.c, we have spinlock_irqsave there, but > that's pretty much it AFAICT. That's correct. We don't manipulate IRQs directly in the freezer. Greetings, Rafael -- "Premature optimization is the root of all evil." - Donald Knuth ^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: Linux 2.6.22-rc4 2007-06-05 19:26 ` Linus Torvalds 2007-06-05 19:37 ` Ingo Molnar @ 2007-06-07 14:46 ` Jan Engelhardt 2007-06-07 15:24 ` Gene Heskett [not found] ` <200706071124.30128.gene.heskett@gmail.com> 1 sibling, 2 replies; 14+ messages in thread From: Jan Engelhardt @ 2007-06-07 14:46 UTC (permalink / raw) To: Linus Torvalds Cc: Michal Piotrowski, Linux Kernel Mailing List, Pavel Machek, Ingo Molnar, linux-pm On Jun 5 2007 12:26, Linus Torvalds wrote: >On Tue, 5 Jun 2007, Michal Piotrowski wrote: >> >> It is too stable for me. > >I wish all our testers were you ;) It [2.6.22-rc4] did not die on me so far, unlike that stock FC7 kernel (same config but without fc patches). Jan -- ^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: Linux 2.6.22-rc4 2007-06-07 14:46 ` Jan Engelhardt @ 2007-06-07 15:24 ` Gene Heskett [not found] ` <200706071124.30128.gene.heskett@gmail.com> 1 sibling, 0 replies; 14+ messages in thread From: Gene Heskett @ 2007-06-07 15:24 UTC (permalink / raw) To: Jan Engelhardt Cc: Michal Piotrowski, Linux Kernel Mailing List, Pavel Machek, Ingo Molnar, Linus Torvalds, linux-pm On Thursday 07 June 2007, Jan Engelhardt wrote: >On Jun 5 2007 12:26, Linus Torvalds wrote: >>On Tue, 5 Jun 2007, Michal Piotrowski wrote: >>> It is too stable for me. >> >>I wish all our testers were you ;) > >It [2.6.22-rc4] did not die on me so far, unlike that stock FC7 kernel >(same config but without fc patches). > > > > Jan Oh its stable allright, but why do I have to turn the monitor off by hand when I leave. None of that is working, not even the screen blanker. -- Cheers, Gene "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) I'm not an Iranian!! I voted for Dianne Feinstein!! ^ permalink raw reply [flat|nested] 14+ messages in thread
[parent not found: <200706071124.30128.gene.heskett@gmail.com>]
* Re: Linux 2.6.22-rc4 [not found] ` <200706071124.30128.gene.heskett@gmail.com> @ 2007-06-07 15:38 ` Jan Engelhardt 2007-06-07 16:06 ` Gene Heskett 0 siblings, 1 reply; 14+ messages in thread From: Jan Engelhardt @ 2007-06-07 15:38 UTC (permalink / raw) To: Gene Heskett Cc: Michal Piotrowski, Linux Kernel Mailing List, Pavel Machek, Ingo Molnar, Linus Torvalds, linux-pm On Jun 7 2007 11:24, Gene Heskett wrote: >>>> It is too stable for me. >>> >>>I wish all our testers were you ;) >> >>It [2.6.22-rc4] did not die on me so far, unlike that stock FC7 kernel >>(same config but without fc patches). >> >Oh its stable allright, but why do I have to turn the monitor off by hand when >I leave. None of that is working, not even the screen blanker. VC or X? Jan -- ^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: Linux 2.6.22-rc4 2007-06-07 15:38 ` Jan Engelhardt @ 2007-06-07 16:06 ` Gene Heskett 2007-06-07 16:54 ` Jan Engelhardt 0 siblings, 1 reply; 14+ messages in thread From: Gene Heskett @ 2007-06-07 16:06 UTC (permalink / raw) To: Jan Engelhardt Cc: Michal Piotrowski, Linux Kernel Mailing List, Pavel Machek, Ingo Molnar, Linus Torvalds, linux-pm On Thursday 07 June 2007, Jan Engelhardt wrote: >On Jun 7 2007 11:24, Gene Heskett wrote: >>>>> It is too stable for me. >>>> >>>>I wish all our testers were you ;) >>> >>>It [2.6.22-rc4] did not die on me so far, unlike that stock FC7 kernel >>>(same config but without fc patches). >> >>Oh its stable allright, but why do I have to turn the monitor off by hand >> when I leave. None of that is working, not even the screen blanker. > >VC or X? > > > Jan Regular X, fc6 box, amd xp2800. Using NVIDIA's latest driver, and it works when booted to a 2.6.21 era kernel. Just about up to date, seems I have to do the kde stuffs one or two pieces at a time as yumex isn't handling the deps well otherwise. -- Cheers, Gene "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) The inherent vice of capitalism is the unequal sharing of blessings; the inherent virtue of socialism is the equal sharing of misery. -- Churchill ^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: Linux 2.6.22-rc4 2007-06-07 16:06 ` Gene Heskett @ 2007-06-07 16:54 ` Jan Engelhardt 2007-06-07 20:21 ` Gene Heskett [not found] ` <200706071621.00687.gene.heskett@gmail.com> 0 siblings, 2 replies; 14+ messages in thread From: Jan Engelhardt @ 2007-06-07 16:54 UTC (permalink / raw) To: Gene Heskett Cc: Michal Piotrowski, Linux Kernel Mailing List, Pavel Machek, Ingo Molnar, Linus Torvalds, linux-pm On Jun 7 2007 12:06, Gene Heskett wrote: > >On Thursday 07 June 2007, Jan Engelhardt wrote: >>On Jun 7 2007 11:24, Gene Heskett wrote: >>>>>> It is too stable for me. >>>>> >>>>>I wish all our testers were you ;) >>>> >>>>It [2.6.22-rc4] did not die on me so far, unlike that stock FC7 kernel >>>>(same config but without fc patches). >>> >>>Oh its stable allright, but why do I have to turn the monitor off by hand >>> when I leave. None of that is working, not even the screen blanker. >> >>VC or X? > >Regular X Most likely an X incompatibility then? > fc6 box, amd xp2800. Using NVIDIA's latest driver, and it works >when booted to a 2.6.21 era kernel. Well, NVIDIA is your first stop then. What about nv? Jan -- ^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: Linux 2.6.22-rc4 2007-06-07 16:54 ` Jan Engelhardt @ 2007-06-07 20:21 ` Gene Heskett [not found] ` <200706071621.00687.gene.heskett@gmail.com> 1 sibling, 0 replies; 14+ messages in thread From: Gene Heskett @ 2007-06-07 20:21 UTC (permalink / raw) To: Jan Engelhardt Cc: Michal Piotrowski, Linux Kernel Mailing List, Pavel Machek, Ingo Molnar, Linus Torvalds, linux-pm On Thursday 07 June 2007, Jan Engelhardt wrote: >On Jun 7 2007 12:06, Gene Heskett wrote: >>On Thursday 07 June 2007, Jan Engelhardt wrote: >>>On Jun 7 2007 11:24, Gene Heskett wrote: >>>>>>> It is too stable for me. >>>>>> >>>>>>I wish all our testers were you ;) >>>>> >>>>>It [2.6.22-rc4] did not die on me so far, unlike that stock FC7 kernel >>>>>(same config but without fc patches). >>>> >>>>Oh its stable allright, but why do I have to turn the monitor off by hand >>>> when I leave. None of that is working, not even the screen blanker. >>> >>>VC or X? >> >>Regular X > >Most likely an X incompatibility then? > >> fc6 box, amd xp2800. Using NVIDIA's latest driver, and it works >>when booted to a 2.6.21 era kernel. > >Well, NVIDIA is your first stop then. What about nv? > > > > Jan Don't know Jan. nv, the last time I tried that bucket of molasses in january, couldn't drive this card at more than 800x600, and I am used to double that both ways. The last time I booted to nv, it took me a week to get all the crap fixed that it overwrote trying to fit the default screens I use while trying to make them fit in an 800x600 window. I run 1600x1200, on either an ati card (but the radeon driver quit supporting the r280 chipset according to boot messages, the main reason I bought this nvidia card) or on an older nvidia card that nv was quite happy with. That card went belly up and took the motherboard with it 2 years ago though. Did you miss the comment that it works with a 2.6.21ish kernel? Everything else being equal. I will boot to one of them later tonight and test it to make sure its not some update to kde though, and let the list know. -- Cheers, Gene "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) Vote anarchist. ^ permalink raw reply [flat|nested] 14+ messages in thread
[parent not found: <200706071621.00687.gene.heskett@gmail.com>]
* Re: Linux 2.6.22-rc4 [not found] ` <200706071621.00687.gene.heskett@gmail.com> @ 2007-06-07 21:14 ` Pavel Machek 0 siblings, 0 replies; 14+ messages in thread From: Pavel Machek @ 2007-06-07 21:14 UTC (permalink / raw) To: Gene Heskett Cc: Michal Piotrowski, Linux Kernel Mailing List, Jan Engelhardt, Ingo Molnar, Linus Torvalds, linux-pm Hi! > Don't know Jan. nv, the last time I tried that bucket of molasses in january, > couldn't drive this card at more than 800x600, and I am used to double that > both ways. > > The last time I booted to nv, it took me a week to get all the crap fixed that > it overwrote trying to fit the default screens I use while trying to make > them fit in an 800x600 window. > > I run 1600x1200, on either an ati card (but the radeon driver quit supporting > the r280 chipset according to boot messages, the main reason I bought this > nvidia card) or on an older nvidia card that nv was quite happy with. That > card went belly up and took the motherboard with it 2 years ago though. > > Did you miss the comment that it works with a 2.6.21ish kernel? Everything > else being equal. I will boot to one of them later tonight and test it to > make sure its not some update to kde though, and let the list know. Well, your kernel is tainted with nvidia crap we are not allowed to debug. Issue is screen blanking. "It worked before" or not is not really interesting, sorry. Pavel -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html ^ permalink raw reply [flat|nested] 14+ messages in thread
end of thread, other threads:[~2007-06-07 21:14 UTC | newest]
Thread overview: 14+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <alpine.LFD.0.98.0706042040350.23741@woody.linux-foundation.org>
2007-06-05 18:54 ` Linux 2.6.22-rc4 Michal Piotrowski
[not found] ` <4665B169.2030803@googlemail.com>
2007-06-05 19:26 ` Linus Torvalds
2007-06-05 19:37 ` Ingo Molnar
2007-06-05 19:50 ` Linus Torvalds
2007-06-05 20:16 ` Pavel Machek
2007-06-05 20:19 ` Pavel Machek
[not found] ` <20070605201954.GB4424@elf.ucw.cz>
2007-06-05 22:01 ` Rafael J. Wysocki
2007-06-07 14:46 ` Jan Engelhardt
2007-06-07 15:24 ` Gene Heskett
[not found] ` <200706071124.30128.gene.heskett@gmail.com>
2007-06-07 15:38 ` Jan Engelhardt
2007-06-07 16:06 ` Gene Heskett
2007-06-07 16:54 ` Jan Engelhardt
2007-06-07 20:21 ` Gene Heskett
[not found] ` <200706071621.00687.gene.heskett@gmail.com>
2007-06-07 21:14 ` Pavel Machek
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox