mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Jörn Nettingsmeier" <nettings@folkwang-hochschule.de>
To: Fred <fred@arkansaswebs.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.8-ac11 lockup when burning cds
Date: Mon, 03 Sep 2001 16:25:28 +0200	[thread overview]
Message-ID: <3B9392D8.BC963F23@folkwang-hochschule.de> (raw)
In-Reply-To: <3B922604.A8E3EB5F@folkwang-hochschule.de> <3B9232D8.143FC76D@folkwang-hochschule.de> <01090216434100.01174@bits.linuxball>

Fred wrote:
> 
> burning on 2.4.9-ac5 works fine for me with
> amd 500
> 12x ide cdrw
> 256MB ram
> ali mainboard
> 
> what's your hardware config?

#cdrecord -scanbus
Cdrecord 1.9 (i686-suse-linux) Copyright (C) 1995-2000 Jörg
Schilling
Linux sg driver version: 3.1.20
Using libscg version 'schily-0.1'
scsibus0:
        0,0,0     0) 'IBM     ' 'DCAS-34330W     ' 'S65A' Disk
        0,2,0     2) 'TOSHIBA ' 'CD-ROM XM-6201TA' '1037' Removable
CD-ROM
scsibus2:
        2,0,0   200) 'PHILIPS ' 'CDD3610 CD-R/RW ' '2.02' Removable
CD-ROM

there is another pci scsi adaptor (a symbios) for my scanner, but i
only load the module on demand, and it wasn't loaded when the lockup
occured.

i see you are running UP, perhaps it's a SMP related problem ?

will try playing with some debug options and linus' release...



-- 
Jörn Nettingsmeier     
home://Kurfürstenstr.49.45138.Essen.Germany      
phone://+49.201.491621
http://spunk.dnsalias.org
http://www.linuxdj.com/audio/lad/

  reply	other threads:[~2001-09-03 14:25 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-02 12:28 Jörn Nettingsmeier
2001-09-02 13:23 ` Jörn Nettingsmeier
2001-09-02 21:43   ` Fred
2001-09-03 14:25     ` Jörn Nettingsmeier [this message]
2001-09-03 17:40       ` Fred
     [not found]         ` <3B93C884.DA5CBE3D@folkwang-hochschule.de>
2001-09-04 23:00           ` Fred
2001-09-07 22:00   ` 2.4.9-ac9 ide-scsi oops [was Re: 2.4.8-ac11 lockup when burning cds] Jörn Nettingsmeier

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=3B9392D8.BC963F23@folkwang-hochschule.de \
    --to=nettings@folkwang-hochschule.de \
    --cc=fred@arkansaswebs.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

all inboxes | Powered by JetHome®