From: Ben Collins <bcollins@debian.org>
To: Tillmann Steinbrecher <t-st@t-st.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: PROBLEM: 2.6.3 + external firewire dvd writer - frequent freezes
Date: Mon, 23 Feb 2004 14:04:32 -0500 [thread overview]
Message-ID: <20040223190432.GD388@phunnypharm.org> (raw)
In-Reply-To: <4038B244.2020209@t-st.org>
On Sun, Feb 22, 2004 at 02:44:36PM +0100, Tillmann Steinbrecher wrote:
> Hi,
>
> I'm using an external FireWire DVD writer (Plextor 708 in case w/Oxford
> 911 chipset). This was working fine until kernel 2.6.2.
>
> Since I upgraded to 2.6.3, it frequently happens that the system totally
> freezes when trying to write a DVD. It's really a hard crash, no mouse
> movement, no ping on the network. Reset required.
>
> It doesn't happen each time I try to burn a DVD, but in about 20% the
> cases. So basically the writer is unusable with 2.6.3.
>
> I searched the web and archives for the problem, but didn't find any
> results, except for one guy describing the same problem, also with
> 2.6.3, also on this mailing list here:
> http://www.ussg.iu.edu/hypermail/linux/kernel/0402.2/0950.html
>
> However he didn't get any replies.
>
> Please CC: me for replies, or if anybody needs .config, lspci, or other
> info. The firewire controller is a Texas Instruments TSB43AB22/A.
Can you enable spinlock debug so we can see if this is a race condition
somewhere?
--
Debian - http://www.debian.org/
Linux 1394 - http://www.linux1394.org/
Subversion - http://subversion.tigris.org/
WatchGuard - http://www.watchguard.com/
next prev parent reply other threads:[~2004-02-23 19:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-22 13:44 PROBLEM: 2.6.3 + external firewire dvd writer - frequent freezes Tillmann Steinbrecher
2004-02-23 19:04 ` Ben Collins [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-02-24 15:48 Tillmann Steinbrecher
2004-02-24 15:33 ` 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=20040223190432.GD388@phunnypharm.org \
--to=bcollins@debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=t-st@t-st.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