From: Shawn Starr <spstarr@sh0n.net>
To: Mike Galbraith <mikeg@wen-online.de>
Cc: <shawn@rhua.org>, Marcelo Tosatti <marcelo@conectiva.com.br>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
Linus Torvalds <torvalds@transmeta.com>,
lkm <linux-kernel@vger.kernel.org>
Subject: Re: [ANOMALIES]: 2.4.2 - __alloc_pages: failed - Causes more then just msgs
Date: Tue, 27 Feb 2001 16:52:09 -0500 (EST) [thread overview]
Message-ID: <Pine.LNX.4.30.0102271651290.7968-100000@coredump.sh0n.net> (raw)
In-Reply-To: <Pine.LNX.4.33.0102271104320.927-100000@mikeg.weiden.de>
When added with BUG(); it will hang /dev/dsp.
I'm not sure if it did without it. I'll be restarting with the removed
BUG(); soon.
On Tue, 27 Feb 2001, Mike Galbraith wrote:
> On Mon, 26 Feb 2001, Shawn Starr wrote:
>
> > It may not be an important message but what does happen is /dev/dsp becomes
> > hung and no sound works after the fault. So something is definately wrong.
>
> Do you mean it hangs without the BUG() inserted, or only after the oops?
>
> -Mike
>
>
>
next prev parent reply other threads:[~2001-02-27 21:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.33.0102250725180.1864-100000@mikeg.weiden.de>
2001-02-25 6:35 ` [ANOMALIES]: 2.4.2 - __alloc_pages: failed - Patch failed Shawn Starr
2001-02-25 8:03 ` Mike Galbraith
2001-02-25 23:13 ` Shawn Starr
2001-02-26 3:42 ` Marcelo Tosatti
2001-02-26 9:26 ` Alan Cox
2001-02-26 10:24 ` Marcelo Tosatti
2001-02-27 2:19 ` [ANOMALIES]: 2.4.2 - __alloc_pages: failed - Causes more then just msgs Shawn Starr
2001-02-27 10:08 ` Mike Galbraith
2001-02-27 21:52 ` Shawn Starr [this message]
2001-02-28 5:25 ` Mike Galbraith
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=Pine.LNX.4.30.0102271651290.7968-100000@coredump.sh0n.net \
--to=spstarr@sh0n.net \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
--cc=mikeg@wen-online.de \
--cc=shawn@rhua.org \
--cc=torvalds@transmeta.com \
/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).