From: Christian Kujau <evil@g-house.de>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: parport_pc Oops with 2.6.0-test3
Date: Mon, 18 Aug 2003 13:20:05 +0200 [thread overview]
Message-ID: <3F40B665.2010407@g-house.de> (raw)
hi,
as the subject might presume, the parport_pc modules oopses when it's
unloaded. so on every shutdown i see an Oops on the console, which get
logged to syslog then:
http://christian.go4more.de/parport/parport_pc-init6.txt
yes, the kernel is tainted with the nvidia module, i try to reprodduce
later on without nvidia.
upon manual "rmmod parport_pc", this exits with a seg-fault, the log shows:
http://christian.go4more.de/parport/parport_pc-rmmod.txt
This is with vanilla 2.6.0-test3, i386, Debian unstable (glibc
2.3.2-2, kernel compiled with gcc (GCC) 3.3.2 20030812 (Debian prerelease).
more info available, of course.
Thanks,
Christian.
PS: i have 2.6.0-test3 (and previous versions) running now for
days/weeks und X11, normal use, sometimes under load, some quirks, but
*no* crashes! Thank you!
--
BOFH excuse #333:
A plumber is needed, the network drain is clogged
next reply other threads:[~2003-08-18 11:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-18 11:20 Christian Kujau [this message]
2003-08-19 22:01 ` parport_pc Oops with 2.6.0-test3 Christian Kujau
2003-08-24 10:00 ` Andrew Morton
2003-08-24 14:34 ` Christian
2003-08-25 4:53 ` Christian Kujau
2003-08-25 3:37 ` Andrew Morton
-- strict thread matches above, loose matches on Subject: below --
2003-08-16 8:38 increased verbosity in dmesg Gene Heskett
2003-08-16 10:48 ` Martin Schlemmer
2003-08-16 15:07 ` Gene Heskett
2003-08-26 0:17 ` parport_pc Oops with 2.6.0-test3 Christian Kujau
2003-08-26 8:38 ` Andrew Morton
2003-08-26 23:03 ` Christian
2003-08-28 2:41 ` Christian Kujau
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=3F40B665.2010407@g-house.de \
--to=evil@g-house.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