nvidia geforce 4 440MX Using the nv driver
Twice now - X11 suddenly stops responding, or is extremely slow in responding. The mouse works just fine - so it's not a refresh issue, but the window manager/desktop (gnome) takes forever to respond to clicks.
Switching to a virtual console is instantaneous - but there is a delay in log in. But once logged in, the cli is snappy - but the problem persists in X11.
Anybody else seen this? Next time it happens I'll see if anything is in the x11 logs - if something hasn't already been reported related to this.
On Fri, 2004-04-23 at 10:41, Michael A. Peters wrote:
nvidia geforce 4 440MX Using the nv driver
Twice now - X11 suddenly stops responding, or is extremely slow in responding. The mouse works just fine - so it's not a refresh issue, but the window manager/desktop (gnome) takes forever to respond to clicks.
Switching to a virtual console is instantaneous - but there is a delay in log in. But once logged in, the cli is snappy - but the problem persists in X11.
Anybody else seen this? Next time it happens I'll see if anything is in the x11 logs - if something hasn't already been reported related to this.
Yeah, I am seeing pretty much the same thing, but it's not localized to X11. Some other random things are seeing "pauses", like setfiles. And I have an ATI Radeon, so at least it isn't a problem with one particular graphics card.
At first I thought the behavior was SELinux related, but it still happens when I boot with SELinux disabled. Haven't seen anything in any of the logs though. If I go back a couple of kernels, the problem seems to go away.
josh
On 23.04.2004 18:03, Josh Boyer wrote:
On Fri, 2004-04-23 at 10:41, Michael A. Peters wrote:
Twice now - X11 suddenly stops responding, or is extremely slow in responding. The mouse works just fine - so it's not a refresh issue, but the window manager/desktop (gnome) takes forever to respond to clicks.
Switching to a virtual console is instantaneous - but there is a delay in log in. But once logged in, the cli is snappy - but the problem persists in X11.
Yeah, I am seeing pretty much the same thing, but it's not localized to X11. Some other random things are seeing "pauses", like setfiles. And I have an ATI Radeon, so at least it isn't a problem with one particular graphics card.
At first I thought the behavior was SELinux related, but it still happens when I boot with SELinux disabled. Haven't seen anything in any of the logs though. If I go back a couple of kernels, the problem seems to go away.
I am seeing something like this too. The way it looks for me is as if the hard drive just stops responding - everything that wants disk access freezes, but everything else keeps working normally. Once in a while the disk would "unfreeze", I would see a lot of disk activity, and then another freeze (for a periods varying from a few seconds to couple of minutes).
These freezes always start when something very disk-intensive is running (slocate's updatedb, "setfiles check", etc). Quitting Mozilla sometimes helps get rid of them for a while, in other cases only a reboot makes them go away (until they come back a few hours later).
This is a major blocker, IMHO.
On Sun, 2004-04-25 at 03:25, Aleksey Nogin wrote:
On 23.04.2004 18:03, Josh Boyer wrote:
On Fri, 2004-04-23 at 10:41, Michael A. Peters wrote:
Twice now - X11 suddenly stops responding, or is extremely slow in responding. The mouse works just fine - so it's not a refresh issue, but the window manager/desktop (gnome) takes forever to respond to clicks.
Switching to a virtual console is instantaneous - but there is a delay in log in. But once logged in, the cli is snappy - but the problem persists in X11.
Yeah, I am seeing pretty much the same thing, but it's not localized to X11. Some other random things are seeing "pauses", like setfiles. And I have an ATI Radeon, so at least it isn't a problem with one particular graphics card.
At first I thought the behavior was SELinux related, but it still happens when I boot with SELinux disabled. Haven't seen anything in any of the logs though. If I go back a couple of kernels, the problem seems to go away.
I am seeing something like this too. The way it looks for me is as if the hard drive just stops responding - everything that wants disk access freezes, but everything else keeps working normally. Once in a while the disk would "unfreeze", I would see a lot of disk activity, and then another freeze (for a periods varying from a few seconds to couple of minutes).
These freezes always start when something very disk-intensive is running (slocate's updatedb, "setfiles check", etc). Quitting Mozilla sometimes helps get rid of them for a while, in other cases only a reboot makes them go away (until they come back a few hours later).
This is a major blocker, IMHO.
I had a similar problem in both Red Hat 9 and Fedora Core 1. Then, it disappeared with FC2, but came back recently, after a yum update (something like 1 or 2 weeks ago).
On Sun, 2004-04-25 at 04:58, Julien Olivier wrote:
I had a similar problem in both Red Hat 9 and Fedora Core 1. Then, it disappeared with FC2, but came back recently, after a yum update (something like 1 or 2 weeks ago).
When I boot with kernel 2.6.5-1.322, it doesn't seem to have the problem. Not sure about 2.6.5-1.326 or 2.6.5-1.327 yet, but 2.6.5-1.332 definitely has a problem.
I did a diff between 322 and 332, but it's pretty large. If I see anything that stands out (doubtful), I'll post it here.
josh
On Sun, 25 Apr 2004, Josh Boyer wrote:
On Sun, 2004-04-25 at 04:58, Julien Olivier wrote:
I had a similar problem in both Red Hat 9 and Fedora Core 1. Then, it disappeared with FC2, but came back recently, after a yum update (something like 1 or 2 weeks ago).
When I boot with kernel 2.6.5-1.322, it doesn't seem to have the problem. Not sure about 2.6.5-1.326 or 2.6.5-1.327 yet, but 2.6.5-1.332 definitely has a problem.
I did a diff between 322 and 332, but it's pretty large. If I see anything that stands out (doubtful), I'll post it here.
(I've answered the same in the test-list)
The last Arjan kernel that works in my Athlon laptop is 2.6.5-1.319. In a new P4 system, the last ones booted but with vsdo=0 in the boo params.
I've sticked to kernel-2.6.5-1.319 by now.
Pau
On Sun, 2004-04-25 at 03:25, Aleksey Nogin wrote:
I am seeing something like this too. The way it looks for me is as if the hard drive just stops responding - everything that wants disk access freezes, but everything else keeps working normally. Once in a while the disk would "unfreeze", I would see a lot of disk activity, and then another freeze (for a periods varying from a few seconds to couple of minutes).
I think we've got a handle on this. On a "low" memory box (128/256mb or so), it's easy to reproduce. updatedb cron.daily job never runs to completion for me.
It's the ext3 block reservation patch that's the culprit. (The details are pretty icky) There's been a number of fixes to that in the last few days, so hopefully we'll see resolution on it real soon.
Dave
On Wed, 2004-04-28 at 06:09, Dave Jones wrote:
On Sun, 2004-04-25 at 03:25, Aleksey Nogin wrote:
I am seeing something like this too. The way it looks for me is as if the hard drive just stops responding - everything that wants disk access freezes, but everything else keeps working normally. Once in a while the disk would "unfreeze", I would see a lot of disk activity, and then another freeze (for a periods varying from a few seconds to couple of minutes).
I think we've got a handle on this. On a "low" memory box (128/256mb or so), it's easy to reproduce.
Ah-hah - I experience the pauses and I got only 256MB. Been planning to buy more since I built this box january/03 - just never got around to it. Never really felt like I absolutely needed more.
On 28.04.2004 06:09, Dave Jones wrote:
I think we've got a handle on this. On a "low" memory box (128/256mb or so), it's easy to reproduce. updatedb cron.daily job never runs to completion for me.
I've got 512.
It's the ext3 block reservation patch that's the culprit. (The details are pretty icky) There's been a number of fixes to that in the last few days, so hopefully we'll see resolution on it real soon.
Could you please make the fixed packages available on people.redhat.com, once you have them? Thank you!
On Wed, 2004-04-28 at 08:09, Dave Jones wrote:
I think we've got a handle on this. On a "low" memory box (128/256mb or so), it's easy to reproduce. updatedb cron.daily job never runs to completion for me.
Yep, I have 256mb.
It's the ext3 block reservation patch that's the culprit. (The details are pretty icky) There's been a number of fixes to that in the last few days, so hopefully we'll see resolution on it real soon.
Glad you found it. Look at my diff between the two kernels was educational, but I still haven't reached the ext3 changes yet. But I guess that is why you guys get paid ;).
josh
On 28.04.2004 06:09, Dave Jones wrote:
It's the ext3 block reservation patch that's the culprit. (The details are pretty icky) There's been a number of fixes to that in the last few days, so hopefully we'll see resolution on it real soon.
Does -1.344 on http://people.redhat.com/~arjanv/2.6/RPMS.kernel/ have it fixed? Thank you!
On Fri, 2004-04-30 at 21:06, Aleksey Nogin wrote:
On 28.04.2004 06:09, Dave Jones wrote:
It's the ext3 block reservation patch that's the culprit. (The details are pretty icky) There's been a number of fixes to that in the last few days, so hopefully we'll see resolution on it real soon.
Does -1.344 on http://people.redhat.com/~arjanv/2.6/RPMS.kernel/ have it fixed? Thank you!
that should have it fixed yes.
-
Aleksey Nogin -
Arjan van de Ven -
Dave Jones -
Josh Boyer -
Julien Olivier -
Michael A. Peters -
Pau Aliagas