From: "Michel Dänzer" <michel@daenzer.net>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Colin LEROY <colin@colino.net>,
Linux/PPC Development <linuxppc-dev@lists.linuxppc.org>
Subject: Re: PREEMPT problems
Date: Wed, 07 Apr 2004 01:28:39 +0200 [thread overview]
Message-ID: <1081294118.2722.43.camel@thor.asgaard.local> (raw)
In-Reply-To: <1081212676.1426.166.camel@gaston>
On Tue, 2004-04-06 at 02:51, Benjamin Herrenschmidt wrote:
> > Sure enough, -rc2-ben0 is now behaving just as badly as -rc3-ben0.
> > Probably just fluctuation.
> >
> > > I also added a WARN_ON(), do you see it triggered in dmesg ?
>
> Still can't reproduce any problem here. You are using xfs right ?
Yes. Colin, what about you?
> Maybe it's a filesystem issue... or some driver (USB device ?)
The only USB device I'm using regularly is a mouse.
> that you are using that is allergic to preempt ?
I don't think I'm using anything exotic... do you think ALSA could cause
such problems? The filesystem seems more likely to me, but what do I
know.
> It would be useful if you could spot one of those stuck processes
> and get a backtrace from it. For that, use P<pid> in xmon to get the
> ksp then b<ksp value> to get a backtrace.
I'm back to a non-preempt kernel for the time being, but I'll try to do
that if I ever feel adventurous again, and provided I find out how to
get into xmon.
--
Earthling Michel Dänzer | Debian (powerpc), X and DRI developer
Libre software enthusiast | http://svcs.affero.net/rm.php?r=daenzer
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2004-04-06 23:28 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-01 14:32 PREEMPT problems Colin LEROY
2004-04-02 0:29 ` Benjamin Herrenschmidt
2004-04-02 0:56 ` Benjamin Herrenschmidt
2004-04-02 16:00 ` Michel Dänzer
2004-04-02 16:43 ` Michel Dänzer
2004-04-03 3:06 ` Benjamin Herrenschmidt
2004-04-03 12:56 ` Michel Dänzer
2004-04-04 2:20 ` Benjamin Herrenschmidt
2004-04-06 0:51 ` Benjamin Herrenschmidt
2004-04-06 23:28 ` Michel Dänzer [this message]
2004-04-06 23:33 ` Benjamin Herrenschmidt
2004-04-02 9:57 ` Wolfram Quester
2004-04-19 14:26 ` ppc4xx_find_bridges( ) hangs kernel on Xilinx ML300 (PCI) Mike Wellington
2004-04-19 19:48 ` Mike Wellington
2004-04-19 20:48 ` Peter Ryser
2004-04-19 20:54 ` Mike Wellington
2004-04-19 20:58 ` PCI - i *thought* the edk2 was what I was using! Mike Wellington
2004-04-19 22:05 ` Peter Ryser
2004-04-19 22:13 ` did you give me the right ml300_edk*.zip link? Mike Wellington
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=1081294118.2722.43.camel@thor.asgaard.local \
--to=michel@daenzer.net \
--cc=benh@kernel.crashing.org \
--cc=colin@colino.net \
--cc=linuxppc-dev@lists.linuxppc.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).