Hi Gabriel,
I tried your patch, but as you expected it didn't fix the problem. I ran it
twice, once with my kernel as I got it from MontaVista, and once with the
atomic_set() function using regular stw (as it is in the offical sources, I
believe).
In both cases I got the de_put messages in a few minutes, and once I got the
dentry BUG().
I think Eli might have had better luck, but I'm not sure how long he was
running the test.
Regards,
Brian
Patch follows, it includes my previous patch. I don't think that it will
solve your problem, unless you happen to use a preemptible kernel.
While I was at it, I removed the useless stwcx. in transfer_to_handler.
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
No luck here. I checked the patched kernel running Brian's test after an
hour and it had frozen up, with one de_put message.
Eli
----- Original Message -----
From: "Brian Kuschak" <redacted>
To: "'Gabriel Paubert'" <redacted>
Cc: "'Dan Malek'" <redacted>; "Eli Chen" <redacted>;
[off-list ref]
Sent: Friday, May 11, 2001 5:44 PM
Subject: RE: dcache BUG()
Hi Gabriel,
I tried your patch, but as you expected it didn't fix the problem. I ran
it
twice, once with my kernel as I got it from MontaVista, and once with the
atomic_set() function using regular stw (as it is in the offical sources,
I
believe).
In both cases I got the de_put messages in a few minutes, and once I got
the
dentry BUG().
I think Eli might have had better luck, but I'm not sure how long he was
running the test.
Regards,
Brian
quoted
Patch follows, it includes my previous patch. I don't think that it will
solve your problem, unless you happen to use a preemptible kernel.
While I was at it, I removed the useless stwcx. in transfer_to_handler.
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
On Fri, 11 May 2001, Eli Chen wrote:
No luck here. I checked the patched kernel running Brian's test after an
hour and it had frozen up, with one de_put message.
Do you have a stack trace or something similar ?
Does my patch increase the time to failure ?
I've not yet got anything better than these messages without any context
(stack trace, etc). I'd prefer to have them with symbols, but even with
only register contents it would be better than nothing.
I'm currently thinking of ways to catch the occurrences of the problem.
The difficuly is that brute force debugging likely won't work on what
looks like a subtle timing problem. So I need a non-invasive check, and
that's far from trivial.
Along with the stack trace, please include as many details as possible on
your system.
Regards,
Gabriel.
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/