2.4.8-ac11 lockup when burning cds

2.4.8-ac11 lockup when burning cds

[Jörn Nettingsmeier]

hello *

i see hard lockups in 2.4.8-ac11 when i try to burn a cd.
after a few seconds into the burning (with cdrecord), the console
locks.
i cannot switch to other vc's or back to X.
no log entries survive. 
the box does not react to sysrq's.
i cannot ssh into it, but the hub showed continuing net traffic,
possibly from a download in the background, so there seemed to be
something still alive.
after a few minutes wait, i reset the machine.

system is:
* dual p3/600, 512m, mobo is asus p2b-ds
* a scsi disk and cdrom on scsi bus 0 with an adaptec aic7xxx
(onboard)
* an ide disk on ide channel 1 (master)
* an ide cdrecorder on ide channel 0 (master), running as a virtual
scsi device on scsi bus 2

sorry if this has been posted before, i'm not subscribed to lkml.
however, an archive search yielded nothing similar.

please keep me cc:ed on replies. thanks.

will try the latest ac patch now.

all the best,

jörn


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

Re: 2.4.8-ac11 lockup when burning cds

[Jörn Nettingsmeier]

Jörn Nettingsmeier wrote:
> 
> hello *
> 
> i see hard lockups in 2.4.8-ac11 when i try to burn a cd.

the problem is the same in 2.4.9-ac5.


regards,

jörn

Re: 2.4.8-ac11 lockup when burning cds

[Fred]

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?

 _________________________________________________ 
On Sunday 02 September 2001 08:23 am, Jörn Nettingsmeier wrote:
> Jörn Nettingsmeier wrote:
> > hello *
> >
> > i see hard lockups in 2.4.8-ac11 when i try to burn a cd.
>
> the problem is the same in 2.4.9-ac5.
>
>
> regards,
>
> jörn
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/

Re: 2.4.8-ac11 lockup when burning cds

[Jörn Nettingsmeier]

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/

Re: 2.4.8-ac11 lockup when burning cds

[Fred]

I have read quite a few messages about SMP machines locking up.
I believe that a few patches are available for these things, but you'd have 
to go back to the archive to find out more.

Fred

 _________________________________________________ 
On Monday 03 September 2001 09:25 am, Jörn Nettingsmeier wrote:
> 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...

Re: 2.4.8-ac11 lockup when burning cds

[Fred]

I think you two should compare notes
another SMP machine can't burn CD's?

see the messages below, the first is reposted from a different email
__________________________________________________
 _________________________________________________ 
On Tuesday 04 September 2001 04:17 pm, Gérard Roudier wrote:
> On 4 Sep 2001, C. Linus Hicks wrote:
> > I have been unsuccessful trying to burn a CD-R since upgrading my
> > computer and I'm not sure where to go with this. I decided to try here.
> > I suspect a problem with the SYM53C8xx driver, and I think there may
> > also be additional problems elsewhere. My old system worked. It was:
> >
> > RedHat 7.0 with 2.2.19 kernel
> > ASUS P2B-DS (440BX chipset) with 2 600MHz Intel processors
> > On-board Adaptec AIC-7890 with the new aic7xxx driver
> > Add-on Adaptec 2940 PCI adapter (narrow devices attached here)
> > Yamaha CRW6416S CD writer
> >
> > My new system:
> >
> > RedHat 7.1 with 2.4.8-ac11 kernel
> > Tyan Thunder HEsl S2567 (ServerWorks chipset) with 2 1000MHz Intel
> > processors
> > On-board LSI 53C1010-66 (running at 33MHz) dual channel SCSI
> > Add-on LSI21003 with 53C1010-33 (narrow devices here)
> > SYM53C8xx driver
> > Yamaha CRW2100S CD writer
> >
> > I looked for problem reports with the 2100S and didn't see any, rather
> > several reports that it worked okay. I updated the firmware to the
> > latest - 1.0N and it didn't help.
> >
> > I have tried several versions of cdrecord including the latest 1.11a05
> > with associated tools to no avail.
> >
> > When I try burning a CD, sometimes I get errors and sometimes it appears
> > to work. When I try to mount a CD-R that burned successfully in a
> > Toshiba DVD-ROM drive, I get errors like this:
> >
> > [root@lh2 /root]# mount /mnt/cdrom
> > mount: wrong fs type, bad option, bad superblock on /dev/cdrom,
> >        or too many mounted file systems
> > [root@lh2 /root]#
> >
> > And in /var/log/messages:
> >
> > Sep  4 16:31:18 LH2 kernel: sym53c1010-33-1:4: ERROR (0:18) (1-21-0)
> > (10/30) @ (script 8e8:110007c1).
> > Sep  4 16:31:18 LH2 kernel: sym53c1010-33-1: script cmd = 88080000
> > Sep  4 16:31:18 LH2 kernel: sym53c1010-33-1: regdump: da 10 c0 30 47 10
> > 04 0e 80 01 84 21 80 01 01 00 00 b0 d6 37 08 00 00 00.
> > Sep  4 16:31:18 LH2 kernel: sym53c1010-33-1: ctest4/sist original
> > 0x8/0x18  mod: 0x18/0x0
> > Sep  4 16:31:18 LH2 kernel: sym53c1010-33-1: restart (scsi reset).
> > Sep  4 16:31:18 LH2 kernel: sym53c1010-33-1: handling phase mismatch
> > from SCRIPTS.
> > Sep  4 16:31:18 LH2 kernel: sym53c1010-33-1: Downloading SCSI SCRIPTS.
> > Sep  4 16:31:20 LH2 kernel: sym53c1010-33-1-<4,*>: FAST-20 SCSI 20.0
> > MB/s (50.0 ns, offset 16)
> > Sep  4 16:31:20 LH2 kernel:  I/O error: dev 0b:00, sector 68
> > Sep  4 16:31:20 LH2 kernel: isofs_read_super: bread failed, dev=0b:00,
> > iso_blknum=17, block=17
> >
> > I tried replacing the LSI21003 with a 2940 and burned a CD-R. The
> > process went smoothly with no errors reported.
>
> The ERROR (0:18) thing indicates a SCSI GROSS ERROR problem. In other
> words, the controller is seing a severe transport error on the SCSI BUS.
> This is often due to a SCSI BUS problem. Decreasing the data throughput
> can make the problem less likely to happen, but this is obviously a poor
> workaround.
>
> Could you check the synchronous data parameters negotiated with the
> Adaptec. If speed is lower than 20 MB/s and/or offset is lower than 16,
> then we may well just be comparing oranges and apples.
>
> > I mounted the burned CD
> > in the Toshiba successfully and listed the contents. I did not think to
> > verify the CD with the mastered file. I then switched back to the
> > LSI21003 and tried to mount the burned CD-R. I got:
>
> Hmmm... If you just hot-switch the device then the breakage seems normal.
> Can I assume you didn't do so ?:)
>
> > [root@lh2 /root]# mount /mnt/cdrom
> > mount: Not a directory
> > [root@lh2 /root]#
> >
> > And in /var/log/messages:
> >
> > Sep  4 15:15:47 LH2 kernel: scsi : aborting command due to timeout : pid
> > 0, scsi1, channel 0, id 4, lun 0 Read (10) 00 00 00 00 1c 00 00 01 00
> > Sep  4 15:15:47 LH2 kernel: sym53c8xx_abort: pid=0 serial_number=149685
> > serial_number_at_timeout=149685
> > Sep  4 15:15:48 LH2 kernel: SCSI host 1 abort (pid 0) timed out -
> > resetting
> > Sep  4 15:15:48 LH2 kernel: SCSI bus is being reset for host 1 channel
> > 0.
> > Sep  4 15:15:48 LH2 kernel: sym53c8xx_reset: pid=0 reset_flags=2
> > serial_number=149685 serial_number_at_timeout=149685
> > Sep  4 15:15:48 LH2 kernel: sym53c1010-33-1: restart (scsi reset).
> > Sep  4 15:15:48 LH2 kernel: sym53c1010-33-1: handling phase mismatch
> > from SCRIPTS.
> > Sep  4 15:15:48 LH2 kernel: sym53c1010-33-1: Downloading SCSI SCRIPTS.
> > Sep  4 15:15:48 LH2 kernel: sym53c1010-33-1-<4,*>: FAST-20 SCSI 20.0
> > MB/s (50.0 ns, offset 16)
> > Sep  4 15:15:48 LH2 kernel: Device 0b:00 not ready.
> > Sep  4 15:15:48 LH2 kernel:  I/O error: dev 0b:00, sector 112
> > Sep  4 15:15:49 LH2 kernel: ISOFS: unable to read i-node block
> > Sep  4 15:15:49 LH2 kernel: Device 0b:00 not ready.
> > Sep  4 15:15:49 LH2 kernel:  I/O error: dev 0b:00, sector 128
> > Sep  4 15:15:49 LH2 kernel: ISOFS: unable to read i-node block
> >
> > Any help would be appreciated, and if anyone needs additional
> > information I will be glad to do what I can.
>
> I suggest you to define some lower data speed in the NVRAM and see if it
> makes differences. OTOH, if the Adaptec is using a different (assumed
> lower) speed you may give a try with the C1010-33 at the same speed.
> You may let me know the results.
>
> Regards,
>   Gérard.
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/

 _________________________________________________ 
On Monday 03 September 2001 01:14 pm, Jörn Nettingsmeier wrote:
> thanks for your help, fred.
> i will browse the archive again.
>
> and as soon as my new Xfree runs smoothly, i'll have a go at the
> kernel again.
>
> regards,
>
> jörn
>
> Fred wrote:
> > I have read quite a few messages about SMP machines locking up.
> > I believe that a few patches are available for these things, but you'd
> > have to go back to the archive to find out more.
> >
> > Fred
> >
> >  _________________________________________________
> >
> > On Monday 03 September 2001 09:25 am, Jörn Nettingsmeier wrote:
> > > 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...

2.4.9-ac9 ide-scsi oops [was Re: 2.4.8-ac11 lockup when burning cds]

[Jörn Nettingsmeier]

Jörn Nettingsmeier wrote:
> 
> Jörn Nettingsmeier wrote:
> >
> > hello *
> >
> > i see hard lockups in 2.4.8-ac11 when i try to burn a cd.
> 
> the problem is the same in 2.4.9-ac5.
> 
> regards,
> 
> jörn

with kernel 2.4.9-ac9, the problem remains the same, but i have
finally been able to capture an oops message. "capture" here means
copying the whole shit from the log console and typing it back in
again at ten past midnight, so excuse minor inaccuracies...


the syslog messages just before the oops were:

hda timeout waiting for DMA
ide_dmaproc: chipset supported ide_dma_timeout func only: 14
hda status timeout: status=0xd0 {busy}
hda: drive not ready for command
hda: ATAPI reset complete
hda: irq timeout: status=0xd0 {busy}

and now, the oops:


<oops>
ksymoops 2.4.0 on i686 2.4.9-ac9  
 
Warning (compare_maps): mismatch on symbol usb_devfs_handle  ,
usbcore says e2a53320,
/lib/modules/2.4.9-ac9/kernel/drivers/usb/usbcore.o says e2a52e40. 
Ignoring /lib/modules/2.4.9-ac9/kernel/drivers/usb/usbcore.o entry
Oops: 0002
CPU: 0
EIP: 0010: [<c01f3ea3>]
Using defaults from ksymoops -t elf32-i386 -a i386
EFLAGS: 00010002
eax: 00000000   ebx: d6bac740   ecx: 00000000   edx: d6bac740
esi: 00000000   edi: 00000000   ebp: cf590000   esp: c02e7eb4
ds: 0018   es: 0018   ss: 0018
Process swapper (pid: 0, stackpage=c02c7000)
Stack: d6bac740 c0371560 000000d0 c0371520 00000000 d6bac749
dfffa7c0 c0371560
       c01c3c12 00000000 c189ad60 c0371560 c189ad60 c01f4088
000000d0 c01c481a
       c0371560 c0297862 000000d0 c189ad60 c01c466c 00000000
c0351b60 00000282
Call trace: [<c01c3c12>] [<c01f4088>] [<c01c481a>] [<c01c466c>]
[<c011f895>]
            [<c011f90c>] [<c011c030>] [<c011bf0d>] [<c011bcaf>]
[<c01088cb>]
[<c01051b0>]
            [<c0105180>] [<c0105180>] [<c01051b0>] [<c01051dd>]
[<c0105242>]
[<c0105000>]
            [<c0105043>]
Code: c7 80 78 01 00 00 00 00 07 00 83 7c 24 10 00 0f 84 66 01 00
 
>>EIP; c01f3ea3 <idescsi_end_request+6b/250>   <=====
Trace; c01c3c12 <ide_error+11e/164>
Trace; c01f4088 <idescsi_pc_intr+0/230>
Trace; c01c481a <ide_timer_expiry+1ae/20c>
Trace; c01c466c <ide_timer_expiry+0/20c>
Trace; c011f895 <timer_bh+259/2b0>
Trace; c011f90c <do_timer+20/50>
Trace; c011c030 <bh_action+4c/88>
Trace; c011bf0d <tasklet_hi_action+61/90>
Trace; c011bcaf <do_softirq+6f/cc>
Trace; c01088cb <do_IRQ+db/ec>
Trace; c01051b0 <default_idle+0/34>
Trace; c0105180 <init+134/154>
Trace; c0105180 <init+134/154>
Trace; c01051b0 <default_idle+0/34>
Trace; c01051dd <default_idle+2d/34>
Trace; c0105242 <cpu_idle+3e/54>
Trace; c0105000 <_stext+0/0>
Trace; c0105043 <rest_init+43/44>
Code;  c01f3ea3 <idescsi_end_request+6b/250>
00000000 <_EIP>:
Code;  c01f3ea3 <idescsi_end_request+6b/250>   <=====
   0:   c7 80 78 01 00 00 00      movl   $0x70000,0x178(%eax)  
<=====
Code;  c01f3eaa <idescsi_end_request+72/250>
   7:   00 07 00
Code;  c01f3ead <idescsi_end_request+75/250>
   a:   83 7c 24 10 00            cmpl   $0x0,0x10(%esp,1)
Code;  c01f3eb2 <idescsi_end_request+7a/250>
   f:   0f 84 66 01 00 00         je     17b <_EIP+0x17b> c01f401e
<idescsi_end_request+1e6/250>
 
 <0>Kernel panic: Aiee, killing Interrupt handler !
 
2 warnings issued.  Results may not be reliable.

</oops>

here's my system config again:
dual p3/600, 512mb ram, 
asus p2b-ds mobo w/ onboard aic7xxx scsi, pci scsi controller
symbios (disabled, module *not* loaded when the oops occured), one
scsi cdrom and one 4gig scsi hd connected to the adaptec onboard,
one disk hdc connected to onboard IDE #1 (master), and the offending
cd burner hda, connected to onboard IDE #0 (master), and running in
scsi-emulation mode.

hope the oops will be useful to someone...

please keep me cc:ed on replies.

all the best,

jörn


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