From: walt <wa1ter@hotmail.com>
To: linux-kernel@vger.kernel.org
Subject: 2.5.40 More on ppa.o (Zip Drive)
Date: Tue, 01 Oct 2002 22:24:11 -0700 [thread overview]
Message-ID: <3D9A82FB.1000300@hotmail.com> (raw)
I'm now up and running with 2.5.40, thank you! No obvious IDE
problems so far--but it's very early yet.
I applied Gert Vervoort's patch to ppa.c which allowed the
compile to finish, but there is still a problem.
When I do a modprobe (or insmod) ppa I get a segfault from
insmod. [version 2.4.19/Debian testing]
The wierd part is that ppa seems to get loaded in spite
of the segfault, and it actually seems to work. I've
tried only reading the Zip so far--considering the error
message I didn't try writing to it.
A partial listing of the messages I see when loading ppa:
bad: scheduling while atomic! [series of hex numbers]
Call trace: [another series of hex numbers]
[repeat the above two steps]
Unable to handle kernel paging request at ....
[more messages including Oops: 0004]
process insmod exited with preempt_count 1
Segmentation fault.
Unfortunately these errors only print out on a
virtual terminal, not on an xterm, so I have to
copy them by hand. I can copy them more completely
if it would help.
reply other threads:[~2002-10-01 22:26 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=3D9A82FB.1000300@hotmail.com \
--to=wa1ter@hotmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox