public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Erick Staal <elstaal@xs4all.nl>
To: Marko van Dooren <Marko.vanDooren@student.kuleuven.ac.be>,
	linux-kernel@vger.kernel.org
Subject: Re: PROBLEM: Using Philips CDD3610 cd-writer crashes my system with every 2.4 kernel
Date: Fri, 24 Aug 2001 13:21:33 +0200	[thread overview]
Message-ID: <01082413213300.00959@andromeda> (raw)
In-Reply-To: <200108241045.f7OAjZ220280@urc1.cc.kuleuven.ac.be>
In-Reply-To: <200108241045.f7OAjZ220280@urc1.cc.kuleuven.ac.be>

Hi,

Basically I've encountered the same problem, but it went away after 2.4.6.

Machine: P II 300 Mhz, Adaptec 2940 SCSI adapter, 64 Mb memory, 1x Seagate 
ST34520W, 1x Seagate ST34520LW, 1x Philips CDD 3610, Toshiba XM-6201TA
OS: Redhat 7.1 with latest patches (except kernel)

Division over the buses as shown by cdrecord -scanbus

Scsibus0
           0.0.0           Seagate ST34520W
           0.2.0           Seagate ST34520LW
           0.5.0           Toshiba CD-ROM XM-6201TA
Scsibus1
           1.0.0           Philips CDD-3610 CD R/RW


and as stated everything fine after 2.4.6 (however 2.4.3-5 showed the same 
behaviour as your machine). The cd drive makes after 2.4.6 a strange churning 
sound when initializing cdrecord however. The cd's that were burned however 
were flawless (at least up to 2.4.9).
Further info: in the 2.4.3-2.4.5 kernels the devices which are above shown in 
scsibus0 were shown in scsibus1 and vice versa...

Sincerely, Erick

  reply	other threads:[~2001-08-24 11:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-24 10:45 PROBLEM: Using Philips CDD3610 cd-writer crashes my system with every 2.4 kernel Marko van Dooren
2001-08-24 11:21 ` Erick Staal [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-11-28 14:07 peter.kourzanov
2002-12-30 10:55 Marko van Dooren

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=01082413213300.00959@andromeda \
    --to=elstaal@xs4all.nl \
    --cc=Marko.vanDooren@student.kuleuven.ac.be \
    --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