All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Eli Chen" <eli@routefree.com>
To: "Brian Kuschak" <brian.kuschak@skystream.com>,
	"'Gabriel Paubert'" <paubert@iram.es>
Cc: "'Dan Malek'" <dan@mvista.com>, <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: dcache BUG()
Date: Fri, 11 May 2001 17:57:43 -0700	[thread overview]
Message-ID: <07ab01c0da7e$8d645070$4b00000a@foolio1> (raw)
In-Reply-To: B25E2E5A003CD311B61E00902778AF2A02044682@SERVER1


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" <brian.kuschak@skystream.com>
To: "'Gabriel Paubert'" <paubert@iram.es>
Cc: "'Dan Malek'" <dan@mvista.com>; "Eli Chen" <eli@routefree.com>;
<linuxppc-embedded@lists.linuxppc.org>
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
>
>
>
> > 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/

  reply	other threads:[~2001-05-12  0:57 UTC|newest]

Thread overview: 57+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-12  0:44 dcache BUG() Brian Kuschak
2001-05-12  0:57 ` Eli Chen [this message]
2001-05-14  9:28   ` Gabriel Paubert
  -- strict thread matches above, loose matches on Subject: below --
2001-05-10 21:20 Brian Kuschak
2001-05-10 21:26 ` Dan Malek
2001-05-09 16:40 Brian Kuschak
2001-05-09 18:31 ` Dan Malek
2001-05-09 19:18 ` Gabriel Paubert
2001-05-10 18:39   ` Frank Rowand
2001-05-10 18:49     ` Gabriel Paubert
2001-05-10 19:10       ` Frank Rowand
2001-05-11  4:23         ` Paul Mielke
2001-05-11 10:09         ` Gabriel Paubert
2001-05-10 20:56       ` Dan Malek
2001-05-10 23:14         ` Cort Dougan
2001-05-11 11:01           ` Gabriel Paubert
2001-05-11 10:57         ` Gabriel Paubert
2001-05-11 18:49           ` Dan Malek
2001-05-08 17:43 Brian Kuschak
2001-05-09 11:06 ` Gabriel Paubert
2001-05-08 15:43 Brian Kuschak
2001-05-08  3:36 Brian Kuschak
2001-05-08  1:53 Brian Kuschak
2001-05-08  2:03 ` Dan Malek
2001-05-08 11:59 ` Gabriel Paubert
2001-05-08  0:40 Brian Kuschak
2001-05-07 23:01 Brian Kuschak
2001-05-07 22:19 Brian Kuschak
2001-05-07 22:35 ` Cort Dougan
2001-05-07 22:43 ` Eli Chen
2001-05-07 19:04 Eli Chen
2001-05-07 21:04 ` Dan Malek
2001-05-07 21:17 ` Dan Malek
2001-05-07 21:30   ` Tom Rini
2001-05-07 23:03     ` Dan Malek
2001-05-07 21:47   ` Eli Chen
2001-05-07 23:01     ` Dan Malek
2001-05-07 23:06     ` Gabriel Paubert
2001-05-07 23:15       ` Dan Malek
2001-05-07 23:28         ` Gabriel Paubert
2001-05-07 23:35         ` Eli Chen
2001-05-07 23:36           ` Dan Malek
2001-05-08  0:16             ` Eli Chen
2001-05-08  0:41               ` Dan Malek
2001-05-08  1:14                 ` Eli Chen
2001-05-08  1:11                   ` Dan Malek
2001-05-08 18:01                     ` David Blythe
2001-05-08 20:27                       ` Dan Malek
2001-05-08 21:34                         ` David Blythe
2001-05-08 21:49                           ` Dan Malek
2001-05-08 22:34                             ` Ira Weiny
2001-05-08 22:53                               ` Dan Malek
2001-05-08  1:37             ` Gabriel Paubert
2001-05-08  1:44               ` Dan Malek
2001-05-07 23:40           ` Gabriel Paubert
2001-05-07 17:21 Brian Kuschak
2001-05-07 20:58 ` Dan Malek

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='07ab01c0da7e$8d645070$4b00000a@foolio1' \
    --to=eli@routefree.com \
    --cc=brian.kuschak@skystream.com \
    --cc=dan@mvista.com \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    --cc=paubert@iram.es \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.