From: Andre Costa <acosta@ar.microlink.com.br>
To: Linux kernel ML <linux-kernel@vger.kernel.org>
Subject: Re: [Fwd: SCSI-IDE crash in 2.4.21pre4]
Date: Mon, 10 Feb 2003 10:22:34 -0200 [thread overview]
Message-ID: <20030210102234.4588ff0d.acosta@ar.microlink.com.br> (raw)
In-Reply-To: <1044847348.3767.20.camel@h68-146-142-19.localdomain>
Hi Kim,
the probls you describe ("all sorts of SCSI timeout errors, SCSI comm
errors, etc") are experienced by me and other users of KT266-based mobos
as well, under the same circumstances (cdparanoia, SCSI-emul); see
thread "kernel 2.4.x + via-based kt266 mobo = IDE cdroms probls
(revisited)" here on LKML . Maybe the probl isn't restricted to SIS735
or KT266 after all...
Best,
Andre
On 09 Feb 2003 20:22:28 -0700
Kim Lux <lux@diesel-research.com> wrote:
> One more thing: a bunch of us cdparanoia users got together and
> compared notes. All the computers that are having the problem are
> running the SIS735 chipset. We suspect a kernel bug in that driver.
>
> Let me know if there is anything else we can do to help.
>
> BTW: I think that Linux rocks ! You kernel developers/ debuggers/
> supporters do an outstanding job.
>
> THANKS !
>
> Kim
>
>
>
> On Sat, 2003-02-08 at 23:31, Kim Lux wrote:
> > -----Forwarded Message-----
> >
> > > From: Kim Lux <lux@diesel-research.com>
> > > To: linux-kernel@verger.kernel.org
> > > Subject: SCSI-IDE crash in 2.4.21pre4
> > > Date: 08 Feb 2003 23:27:23 -0700
> > >
> > > One Line Summary:
> > >
> > > SCSI IDE emulation crashes RH8 computer running 2.4.21 pre4.
> > >
> > > Full Description of Problem:
> > >
> > > I've had this problem for months.
> > >
> > > If I run CDParanoia and try to rip CDs, it will work OK for a few
> > > minutes and then start crashing, giving all sorts of SCSI timeout
> > > errors, SCSI comm errors, etc. (Let me know if you want these;
> > > I'll get them.) I get the same or similar errors with KSCD as
> > > well. This is extremely frustrating.
> > >
> > > I get the error with all kernels, 2.4.18-18.8.0 through 2.4.21
> > > pre-4, although 2.4.21 freezes entirely and cannot be killed,
> > > whereas all kernels prior to this allow the process to be killed.
> > > For some reason the process survives a login and reboot with
> > > 2.4.21 pre 4, whereas it stops running with all previous kernels.
> > >
> > >
> > > I've tried 2 motherboards and 2 hd cables, with the same effect.
> > > The computer this occurs on is otherwise stable, with uptimes of
> > > several months at a time.
> > >
> > > I might have the links/permissions messed up in /dev from trying
> > > to fix this problem. I also disabled the CD automount command in
> > > .kde/autostart.
> > >
> > > I've been through the CDParanoia doc several times and have tried
> > > various kernels with various SCSI-IDE config setups. I know that
> > > ATAPI CDROM must be disabled to work with CDParanoia. I believe
> > > I've got that set up right as CD Paranoia finds (or used to find)
> > > the CDROM player. It does rip CDs, but will crash. I strongly
> > > believe this is a kernel problem and not a CDParanoia problem or a
> > > hardware problem.
> > >
> > > Keywords:
> > > 2.4.20
> > > 2.4.21-pre4
> > > SCSI-IDE Emulation
> > > CDParanoia
> > > KSCD
> > >
> > > Kernel Version:
> > > Linux version 2.4.20 (root@h68-146-142-19) (gcc version 3.2
> > > 20020903(Red Hat Linux 8.0 3.2-7)) #2 Mon Dec 2 11:09:28 MST 2002
> > >
> > >
> > > As I stated before, 2.4.21 becomes unstable on login; I cannot run
> > > it anymore as I can't kill the process.
> > >
> > > Output of Oops: don't have it. I got dmesg errors on boot, on
> > > /dev/hda. See dmesg output below.
> > >
> > > A small shell script that triggers the problem:
> > > > CDParanoia -svB or run KSCD.
> > >
> > > Environment: (see below) Running KDE. Everything stable
> > > otherwise.
--
Andre Oliveira da Costa
next prev parent reply other threads:[~2003-02-10 12:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-09 6:31 Kim Lux
2003-02-10 3:22 ` Kim Lux
2003-02-10 12:22 ` Andre Costa [this message]
2003-02-19 3:46 ` Bill Davidsen
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=20030210102234.4588ff0d.acosta@ar.microlink.com.br \
--to=acosta@ar.microlink.com.br \
--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®