From: Jens Benecke <usenet@jensbenecke.de>
To: linux-kernel@vger.kernel.org
Subject: 2.4.22rc2 repeated crashes / Oops / IRQ problems
Date: Tue, 12 Aug 2003 20:46:42 +0200 [thread overview]
Message-ID: <bhbcma$eh$1@sea.gmane.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1015 bytes --]
Hi,
I posted this earlier but it didn't get accepted (it seems). So I'll try
again. I tried "noapic" which results in "CPU0 APIC error (40)" or
something like that.
.config is attached, the rest is below. Please advise me on how to corner
this problem.
Marcelo Tosatti wrote:
> Here goes release candidate 2.
> It contains yet another bunch of important fixes, detailed below.
> Nice weekend for all of you!
I'm having problems. had them with -pre10 as well, posted here, but they
somehow didn't appear in the list.
Here's the short story: No network (3c509) because the card gets IRQ 22 (or
something) and doesn't like it, no USB, no firewire, no X11 (yeah, should
have recompiled the NVIDIA drivers, duh), and a total crash on shutdown-
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/
reply other threads:[~2003-08-12 18:46 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='bhbcma$eh$1@sea.gmane.org' \
--to=usenet@jensbenecke.de \
--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