From: Tillmann Steinbrecher <t-st@t-st.org>
To: linux-kernel@vger.kernel.org, bcollins@debian.org
Subject: [PROBLEM] Firewire-related crashes in 2.6.4
Date: Tue, 16 Mar 2004 13:08:40 +0100 [thread overview]
Message-ID: <1079438920.2947.10.camel@paranoia.pallasnet.de> (raw)
Hi,
although not as unstable as in 2.6.3, the usage of my external FireWire
drive (Plextor 708A DVD burner with Oxford 911 FireWire interface) is
still causing freezes. This time the freezes occur randomly when reading
files from the drive, or when trying to rip a video DVD. It's a hard
crash - no mouse movement, no ping on the network. It is not always
reproducible, but occurs frequently.
Here's a screenshot of the resulting kernel panic (sorry for the .jpg, I
couldn't paste it as text, for obvious reasons):
http://www.t-st.org/panic.jpg
Here's my kernel .config:
http://www.t-st.org/kconf.txt
And here lspci:
http://www.t-st.org/lspci.txt
The system was running fine with identical config under 2.6.0, 2.6.1,
2.6.2. Under 2.6.3 crashes of the same kind occured when trying to burn
DVDs. Under 2.6.4 this problem was fixed, but the new crash-on-read
problem described here showed up.
I also have another problem with FireWire, which is probably unrelated -
this problem was also present in earlier 2.6 kernel releases:
Sometimes it happens that after I mount a DVD with data on it, I get
read errors. Unmounting and remounting the DVD solves this problem, it
can be read without problems after that. The error message on the
console is:
Buffer I/O error on device sr0, logical block 2204373
attempt to access beyond end of device
src: rw=0, want=8817500, limit=8640640
Buffer I/O error on device sr0, logical block 2204374
Please CC: me replies, since I'm not subscribed.
best regards,
Tillmann
next reply other threads:[~2004-03-16 11:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-16 12:08 Tillmann Steinbrecher [this message]
2004-03-16 12:59 ` Ben Collins
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=1079438920.2947.10.camel@paranoia.pallasnet.de \
--to=t-st@t-st.org \
--cc=bcollins@debian.org \
--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
all inboxes | Powered by JetHome®