From: Jan Ciger <jan.ciger@epfl.ch>
To: frode <frode@freenix.no>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.17 oops, again ("kernel BUG at page_alloc.c:76!")
Date: Thu, 17 Jan 2002 18:02:08 +0100 [thread overview]
Message-ID: <m16RFvW-02103HC@ligsg2.epfl.ch> (raw)
In-Reply-To: <3C46FC88.2050906@freenix.no>
In-Reply-To: <3C46FC88.2050906@freenix.no>
Hello,
I have these strange spurious interrupts with 2.4.17 + low latency patch
too on PII 450 with 256 MB RAM. No oopses yet, but when I try to burn CD's,
my PS/2 mouse starts to act funny (jumps all over the screen under XFree) and
the burner usually burns garbage (=unreadable CD's). Seems like some IRQ
conflict to me, but according to /proc/interrupts, there is none. BTW,
enabling or disabling the low latency patch via /proc makes no difference.
I can send more info if needed.
Jan
On Thursday 17 January 2002 17:32, frode wrote:
> I got this oops yesterday, on a 2.4.17 kernel on a k7 750 with 384mb ram
> and 160mb swap. It took down XFree but I could still run programs on the
> VT, so I attach the output of 'dmesg | ksymoops', 'free', 'lspci' and
> 'lsmod'. If anyone's interested, I can mail the .config file as well.
>
> I've had a lot of oopses on 2.4.17 lately; see for example
> http://www.uwsg.iu.edu/hypermail/linux/kernel/0201.1/1628.html.
>
> The kernel is tainted because of the nvidia NVdriver module v2313.
> (but even without it loaded I recall getting oopses).
>
> I tried running MemTest86 for about 35 minutes with no errors reported.
>
> By the way, during bootup, i get a "spurious 8259A interrupt: IRQ7."
> kernel message. Sometimes after all services have been started, other times
> just before the initscripts are finished starting everything. It doesn't
> seem to have any effect.. my printer seems to work fine (if lpt1 is related
> to IRQ7..?)
>
> - Frode
prev parent reply other threads:[~2002-01-17 17:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-17 16:32 2.4.17 oops, again ("kernel BUG at page_alloc.c:76!") frode
2002-01-17 17:02 ` Jan Ciger [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=m16RFvW-02103HC@ligsg2.epfl.ch \
--to=jan.ciger@epfl.ch \
--cc=frode@freenix.no \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox