vmware + aic7xxx + 2.4.19-4gb-smp = kernel panic

vmware + aic7xxx + 2.4.19-4gb-smp = kernel panic

[Lee Leahu]

my hardware is this:

2 pentium III 1.13 gb processors
tyan motharboard w/ via chipset
1.5 gb ram

adaptec 2490 scsi card.
plextor cd re-writer 8/2/20

sound blaster live card

-----------------------------------------------------------

problem description:

when i have vmware up and running w2k server,
and i burn a cd from bash (as root) using cdrecord,
i am getting a kernel panic.

also to note,  the emu10k1 sound driver is loaded with xmms playing mp3s.


----------------------------------------------------------

additional kernel info:

i was able to save this data because i configured the kernel to use the serial port as its console,
and i had tail -f /var/log/messages running on the serial port console



Nov 27 12:38:36 zadio kernel: sr0: CDROM (ioctl) reports ILLEGAL REQUEST.
Nov 27 12:38:36 zadio kernel:  I/O error: dev 0b:00, sector 64
Nov 27 12:38:37 zadio last message repeated 4 times
Nov 27 12:38:37 zadio kernel: sr0: CDROM (ioctl) reports ILLEGAL REQUEST.
Nov 27 12:38:37 zadio kernel:  I/O error: dev 0b:00, sector 64
Nov 27 12:38:37 zadio last message repeated 4 times
Nov 27 12:38:38 zadio kernel: sr0: CDROM (ioctl) reports ILLEGAL REQUEST.
Nov 27 12:38:38 zadio kernel:  I/O error: dev 0b:00, sector 64
Nov 27 12:38:38 zadio last message repeated 4 times
Nov 27 12:38:38 zadio kernel: sr0: CDROM (ioctl) reports ILLEGAL REQUEST.
Nov 27 12:38:38 zadio kernel:  I/O error: dev 0b:00, sector 64
Nov 27 12:38:39 zadio last message repeated 4 times
Nov 27 12:38:39 zadio kernel: sr0: CDROM (ioctl) reports ILLEGAL REQUEST.
Nov 27 12:39:15 zadio kernel: scsi0:0:4:0: Attempting to queue an ABORT message
Nov 27 12:39:15 zadio kernel: scsi0: Dumping Card State while idle, at SEQADDR 0x15c
Nov 27 12:39:15 zadio kernel: ACCUM = 0x2, SINDEX = 0x20, DINDEX = 0xc0, ARG_2 = 0x0
Nov 27 12:39:15 zadio kernel: HCNT = 0x0 SCBPTR = 0x0
Nov 27 12:39:15 zadio kernel: SCSISEQ = 0x12, SBLKCTL = 0x0
Nov 27 12:39:15 zadio kernel:  DFCNTRL = 0x4, DFSTATUS = 0x6d
Nov 27 12:39:15 zadio kernel: LASTPHASE = 0x1, SCSISIGI = 0xb6, SXFRCTL0 = 0x88
Nov 27 12:39:15 zadio kernel: SSTAT0 = 0x7, SSTAT1 = 0x13
Nov 27 12:39:15 zadio kernel: STACK == 0x186, 0x156, 0x0, 0x35
Nov 27 12:39:15 zadio kernel: SCB count = 4
Nov 27 12:39:15 zadio kernel: Kernel NEXTQSCB = 3
Nov 27 12:39:15 zadio kernel: Card NEXTQSCB = 3
Nov 27 12:39:15 zadio kernel: QINFIFO entries: 
Nov 27 12:39:15 zadio kernel: Waiting Queue entries: 
Nov 27 12:39:15 zadio kernel: Disconnected Queue entries: 
Nov 27 12:39:15 zadio kernel: QOUTFIFO entries: 
Nov 27 12:39:15 zadio kernel: Sequencer Free SCB List: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 
Nov 27 12:39:15 zadio kernel: Sequencer SCB Info: 0(c 0x40, s 0x47, l 0, t 0x2) 1(c 0x0, s 0xff, l 255, t 0xff) 2(c 0x0, s 0xff, l 255, t 0xff) 3(c 0x0, s 0xff, l 255, t 0xff) 4(c 0x0, s 0xff, l 255, t 0xff) 5(c 0x0, s 0xff, l 255, t 0xff) 6(c 0x0, s 0xff, l 255, t 0xff) 7(c 0x0, s 0xff, l 255, t 0xff) 8(c 0x0, s 0xff, l 255, t 0xff) 9(c 0x0, s 0xff, l 255, t 0xff) 10(c 0x0, s 0xff, l 255, t 0xff) 11(c 0x0, s 0xff, l 255, t 0xff) 12(c 0x0, s 0xff, l 255, t 0xff) 13(c 0x0, s 0xff, l 255, t 0xff) 14(c 0x0, s 0xff, l 255, t 0xff) 15(c 0x0, s 0xff, l 255, t 0xff) 
Nov 27 12:39:15 zadio kernel: Pending list: 2(c 0x40, s 0x47, l 0)
Nov 27 12:39:15 zadio kernel: Kernel Free SCB list: 1 0 
Nov 27 12:39:15 zadio kernel: Untagged Q(4): 2 
Nov 27 12:39:15 zadio kernel: DevQ(0:4:0): 0 waiting
Nov 27 12:39:15 zadio kernel: (scsi0:A:4:0): Queuing a recovery SCB
Nov 27 12:39:15 zadio kernel: scsi0:0:4:0: Device is disconnected, re-queuing SCB
Nov 27 12:39:15 zadio kernel: scsi0: brkadrint, Scratch or SCB Memory Parity Error at seqaddr = 0x15c
Nov 27 12:39:15 zadio kernel: scsi0: Dumping Card State while idle, at SEQADDR 0x15c
Nov 27 12:39:15 zadio kernel: ACCUM = 0x2, SINDEX = 0x20, DINDEX = 0xc0, ARG_2 = 0x0
Nov 27 12:39:15 zadio kernel: HCNT = 0x0 SCBPTR = 0x0
Nov 27 12:39:15 zadio kernel: SCSISEQ = 0x12, SBLKCTL = 0x0
Nov 27 12:39:15 zadio kernel:  DFCNTRL = 0x4, DFSTATUS = 0x6d
Nov 27 12:39:15 zadio kernel: LASTPHASE = 0x1, SCSISIGI = 0xb6, SXFRCTL0 = 0x88
Nov 27 12:39:15 zadio kernel: SSTAT0 = 0x7, SSTAT1 = 0x13
Nov 27 12:39:15 zadio kernel: STACK == 0x186, 0x156, 0x0, 0x35
Nov 27 12:39:15 zadio kernel: SCB count = 4
Nov 27 12:39:15 zadio kernel: Kernel NEXTQSCB = 3
Nov 27 12:39:15 zadio kernel: Card NEXTQSCB = 2
Nov 27 12:39:15 zadio kernel: QINFIFO entries: 2 
Nov 27 12:39:15 zadio kernel: Waiting Queue entries: 
Nov 27 12:39:15 zadio kernel: Disconnected Queue entries: 
Nov 27 12:39:15 zadio kernel: QOUTFIFO entries: 
Nov 27 12:39:15 zadio kernel: Sequencer Free SCB List: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 
Nov 27 12:39:15 zadio kernel: Sequencer SCB Info: 0(c 0x40, s 0x47, l 0, t 0x2) 1(c 0x0, s 0xff, l 255, t 0xff) 2(c 0x0, s 0xff, l 255, t 0xff) 3(c 0x0, s 0xff, l 255, t 0xff) 4(c 0x0, s 0xff, l 255, t 0xff) 5(c 0x0, s 0xff, l 255, t 0xff) 6(c 0x0, s 0xff, l 255, t 0xff) 7(c 0x0, s 0xff, l 255, t 0xff) 8(c 0x0, s 0xff, l 255, t 0xff) 9(c 0x0, s 0xff, l 255, t 0xff) 10(c 0x0, s 0xff, l 255, t 0xff) 11(c 0x0, s 0xff, l 255, t 0xff) 12(c 0x0, s 0xff, l 255, t 0xff) 13(c 0x0, s 0xff, l 255, t 0xff) 14(c 0x0, s 0xff, l 255, t 0xff) 15(c 0x0, s 0xff, l 255, t 0xff) 
Nov 27 12:39:15 zadio kernel: Pending list: 2(c 0x54, s 0x47, l 0)
Nov 27 12:39:15 zadio kernel: Kernel Free SCB list: 1 0 
Nov 27 12:39:15 zadio kernel: Untagged Q(4): 2 
Nov 27 12:39:15 zadio kernel: DevQ(0:4:0): 0 waiting
Nov 27 12:39:15 zadio kernel: Recovery SCB completes
Nov 27 12:39:15 zadio kernel: Recovery code sleeping
Nov 27 12:39:15 zadio kernel: Recovery code awake
Nov 27 12:39:15 zadio kernel: aic7xxx_abort returns 0x2002
Kernel panic: Loop 1




-- 
+----------------------------------+---------------------------------+
| Lee Leahu                        | voice -> 708-444-2690           |
| Internet Technology Specialist   | fax -> 708-444-2697             |
| RICIS, Inc.                      | email -> lee@ricis.com          |
+----------------------------------+---------------------------------+
| I cannot conceive that anybody will require multiplications at the |
| rate of 40,000 or even 4,000 per hour ...                          |
|		-- F. H. Wales (1936)                                |
+--------------------------------------------------------------------+

Re: vmware + aic7xxx + 2.4.19-4gb-smp = kernel panic

[Petr Vandrovec]

On 27 Nov 02 at 12:58, Lee Leahu wrote:
> 
> my hardware is this:
> 
> 2 pentium III 1.13 gb processors
> tyan motharboard w/ via chipset
> 1.5 gb ram
> 
> adaptec 2490 scsi card.
> plextor cd re-writer 8/2/20
> 
> sound blaster live card
> 
> -----------------------------------------------------------
> 
> problem description:
> 
> when i have vmware up and running w2k server,
> and i burn a cd from bash (as root) using cdrecord,
> i am getting a kernel panic.
> 
> also to note,  the emu10k1 sound driver is loaded with xmms playing mp3s.

How is your virtual machine configured? Do you use
/dev/sg* for generic access to your SCSI, or
/dev/sr* for accessing your CD drive from virtual machine? 

In that case, try disconnecting this hardware from guest before
using cdrecord. It is quite possible that your cdwriter gets mad
if you are recording and at same time Windows try to detect whether
you changed medium inside writer...

Not that aic7xxx driver should panic due to that, but...
                                                Best regards,
                                                    Petr Vandrovec
                                                    vandrove@vc.cvut.cz
                                                    

Re: vmware + aic7xxx + 2.4.19-4gb-smp = kernel panic

[Doug Ledford]

On Wed, Nov 27, 2002 at 08:19:50PM +0100, Petr Vandrovec wrote:
> Not that aic7xxx driver should panic due to that, but...

I've sent a note under separate cover to Justin about this particular 
panic.  I've seen it once before and I relayed some more details to him.  
For example, on my machine, I was using the stock Red Hat kernels.  The 
i386 BOOT kernel worked fine, the i686 kernel panic'ed just like this.  
You might try recompiling the kernel as an i386 kernel without a bunch of 
optimizations and see if that changes things.

-- 
  Doug Ledford <dledford@redhat.com>     919-754-3700 x44233
         Red Hat, Inc. 
         1801 Varsity Dr.
         Raleigh, NC 27606