L A Walsh wrote:
Will this be included/fixed in 2.6.8?
How serious is the problem? The system doesn't seem to panic or
indicate backup
failures.
Setting up a CVS tree to get a patch for a "stable-series" kernel
seems a bit
unstable. I'm not sure what I'd pull in besides the fix or even if
I'd pull
down a coherent/stable CVS image if I downloaded in the middle of when
some
other patch was being checked in. Maybe I'm sounding like a wimp, but
the idea
of pulling in freshly checked in CVS code for use on a 'stable'
machine is
bordering on my discomfort zone. :-)
-l
FWIW I am getting this error. I assumed it was my NVIDIA binary drivers
causing it. However, there are lots of weird allocator issues popping
up right now [so it seems]. I have checked my FS several times, and it
does not seem to be a problem. It only happens when I have large
blocks of memory sucked into some process, which would lead me to
believe that there is some amount of memory pressure leading up to
them. The pagebuf_get is a note, but it does not seem to be an error.
AFAICT the XFS folks tend to "dead-lock instead of corrupt" [which is
standard fare in the Linux kernel]. So you will have your own mileage
I am sure. If it is a production machine, and 2.6.6 ran fine, unless
you need something specific I would back-rev and wait.
All that being said, I have not tried to Use The Source(tm). So all I
have is speculation.
js
|