From: Steven Walter <srwalter@yahoo.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Odd __alloc_pages failure in 2.4.9
Date: Sat, 25 Aug 2001 12:37:36 -0500 [thread overview]
Message-ID: <20010825123736.A709@hapablap.dyn.dhs.org> (raw)
In-Reply-To: <20010825113344.A528@hapablap.dyn.dhs.org>
In-Reply-To: <20010825113344.A528@hapablap.dyn.dhs.org>; from srwalter@yahoo.com on Sat, Aug 25, 2001 at 11:33:44AM -0500
Hmm... I just recompiled with gcc 2.95.3, and now it works. The kernel
had been compiled with gcc 3.0; guess its a compiler bug.
I'll look into this more and see if I can't file a formal gcc bugreport.
On Sat, Aug 25, 2001 at 11:33:44AM -0500, Steven Walter wrote:
> Running kernel 2.4.9, if I start xcdroast 0.98alpha9 as an ordinary
> user, the system seems to freeze indefinitely.
>
> If I start it as root, however, the system only freeze for 2-3 seconds.
> After this time, if I check dmesg, I get a slew of __alloc_pages
> failures, even 0-order failures.
>
> Being unable to diagnose the complete lockup in the user case any
> better, I assume that this is what's happening there, too, only
> indefinitely.
>
> The system is an AMD Thunderbird 900MHz with 2 IDE CD-ROM drives, both
> use ide-scsi. One is a burner, the other is a DVD-ROM drive.
>
> I'll try and get a backtrace of whats happening during the lockup later
> when I can hook up my serial console.
> --
> -Steven
> In a time of universal deceit, telling the truth is a revolutionary act.
> -- George Orwell
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
--
-Steven
In a time of universal deceit, telling the truth is a revolutionary act.
-- George Orwell
prev parent reply other threads:[~2001-08-25 17:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-25 16:33 Odd __alloc_pages failure in 2.4.9 Steven Walter
2001-08-25 17:37 ` Steven Walter [this message]
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=20010825123736.A709@hapablap.dyn.dhs.org \
--to=srwalter@yahoo.com \
--cc=linux-kernel@vger.kernel.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 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.