WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] 3c59x module errors, scsi timeouts

On Fri, 2005-10-21 at 13:59 -0400, Ted Kaczmarek wrote:
> On Fri, 2005-10-21 at 10:26 -0700, Nivedita Singhvi wrote:
> > Ted Kaczmarek wrote:
> > > On Fri, 2005-10-21 at 12:21 -0400, Ted Kaczmarek wrote:
> > > 
> > >>Also noticed lots of scsi timeouts as well. I rebooted in stock FC4
> > >>kernel and do not see any problems with scsi or the 3c59x.
> > >>
> > >>
> > >>Did not see any of these issues with stock FC4 kernel.
> > >>
> > >>
> > >>
> > >>Regards,
> > >>Ted
> > > 
> > > 
> > > Just built from pristine source and see the same issue.
> > > 
> > > Regards,
> > > Ted
> > 
> > Ted, stupid question but did you mean mainline Linux?
> > i.e, is it a Xen issue?
> > 
> > thanks,
> > Nivedita
> 
> Timer ISR/1: Time went backwards: delta=-216859625 cpu_delta=3196141
> shadow=10003318252 off=999877946 processed=11220055766
> cpu_processed=11000000000
>  0: 11220055766
>  1: 11000000000
> SCSI subsystem initialized
> ACPI: PCI Interrupt 0000:00:0d.0[A] -> GSI 16 (level, low) -> IRQ 16
> ACPI: PCI Interrupt 0000:00:0d.1[B] -> GSI 17 (level, low) -> IRQ 17
> scsi0 : Adaptec AIC7XXX EISA/VLB/PCI SCSI HBA DRIVER, Rev 6.2.36
>         <Adaptec aic7899 Ultra160 SCSI adapter>
>         aic7899: Ultra160 Wide Channel A, SCSI Id=7, 32/253 SCBs
> 
> 
> 
> 
> I missed that, didn't scroll up enough in the log files.
> 
> This did not start until after the 2.6.12.5 patch was correctly applied
> from what I can tell. 
> 
> I need to try this as a monolithic kernel as well still.
> 
> 
> 
> ACPI: PCI Interrupt 0000:00:0d.0[A] -> GSI 16 (level, low) -> IRQ 16
> ACPI: PCI Interrupt 0000:00:0d.1[B] -> GSI 17 (level, low) -> IRQ 17
> scsi0 : Adaptec AIC7XXX EISA/VLB/PCI SCSI HBA DRIVER, Rev 6.2.36
>         <Adaptec aic7899 Ultra160 SCSI adapter>
>         aic7899: Ultra160 Wide Channel A, SCSI Id=7, 32/253 SCBs
> 
> (scsi0:A:0:0): parity error detected in DT Data-in phase. SEQADDR(0x1a6)
> SCSIRATE(0x0)
>         Unexpected non-DT Data Phase
> scsi0:0:0:0: Attempting to queue an ABORT message
> CDB: 0x12 0x0 0x0 0x0 0x24 0x0
> 
> 
> ACPI: PCI Interrupt 0000:00:0f.0[A] -> GSI 18 (level, low) -> IRQ 18
> 3c59x: Donald Becker and others. www.scyld.com/network/vortex.html
> 0000:00:0f.0: 3Com PCI 3c980C Python-T at 0x1c00. Vers LK1.1.19
>  ***INVALID CHECKSUM 00c7*** <3>*** EEPROM MAC address is invalid.
> 3c59x: vortex_probe1 fails.  Returns -22
> 3c59x: probe of 0000:00:0f.0 failed with error -22
> ACPI: PCI Interrupt 0000:00:10.0[A] -> GSI 19 (level, low) -> IRQ 19
> 0000:00:10.0: 3Com PCI 3c980C Python-T at 0x1c80. Vers LK1.1.19
>  ***INVALID CHECKSUM 00c8*** <3>*** EEPROM MAC address is invalid.
> 3c59x: vortex_probe1 fails.  Returns -22
> 3c59x: probe of 0000:00:10.0 failed with error -22
> Intel(R) PRO/1000 Network Driver - version 6.0.54-k2-NAPI
> Copyright (c) 1999-2004 Intel Corporation.
> ACPI: PCI Interrupt 0000:00:0c.0[A] -> GSI 16 (level, low) -> IRQ 16
> e1000: eth0: e1000_probe: Intel(R) PRO/1000 Network Connection
> ACPI: PCI Interrupt 0000:00:0a.0[A] -> GSI 18 (level, low) -> IRQ 18
> 
> [root@inyoureyes xen]# cat /proc/interrupts
>            CPU0       CPU1
>   1:          8          0        Phys-irq  i8042
>   9:          0          0        Phys-irq  acpi
>  14:      21794          0        Phys-irq  ide0
>  16:       7480          0        Phys-irq  aic7xxx, peth0
>  17:      18046          0        Phys-irq  aic7xxx
>  18:          0          0        Phys-irq  EMU10K1
>  19:         98          0        Phys-irq  ohci_hcd:usb1
> 256:      94140          0     Dynamic-irq  timer0
> 257:       3037          0     Dynamic-irq  resched0
> 258:         14          0     Dynamic-irq  callfunc0
> 259:          0       3919     Dynamic-irq  resched1
> 260:          0       2632     Dynamic-irq  callfunc1
> 261:          0      15144     Dynamic-irq  timer1
> 262:       7327          0     Dynamic-irq  xenbus
> 263:        381          0     Dynamic-irq  console
> 264:          0          0     Dynamic-irq  net-be-dbg
> 265:       1359          0     Dynamic-irq  blkif-backend
> 266:          2          0     Dynamic-irq  blkif-backend
> 267:       1355          0     Dynamic-irq  blkif-backend
> 268:          2          0     Dynamic-irq  blkif-backend
> 269:         31          0     Dynamic-irq  vif2.1
> 270:       1354          0     Dynamic-irq  blkif-backend
> 271:          2          0     Dynamic-irq  blkif-backend
> 272:       3510          0     Dynamic-irq  blkif-backend
> 273:         49          0     Dynamic-irq  blkif-backend
> 274:         28          0     Dynamic-irq  vif4.1
> 275:        818          0     Dynamic-irq  blkif-backend
> 276:          1          0     Dynamic-irq  blkif-backend
> 277:        734          0     Dynamic-irq  blkif-backend
> 278:          2          0     Dynamic-irq  blkif-backend
> 279:         40          0     Dynamic-irq  vif6.1
> 280:        607          0     Dynamic-irq  blkif-backend
> 281:          2          0     Dynamic-irq  blkif-backend
> 282:         10          0     Dynamic-irq  vif7.1
> 283:        603          0     Dynamic-irq  blkif-backend
> 284:          2          0     Dynamic-irq  blkif-backend
> 285:         15          0     Dynamic-irq  vif8.1
> 286:        796          0     Dynamic-irq  blkif-backend
> 287:          2          0     Dynamic-irq  blkif-backend
> 288:        795          0     Dynamic-irq  blkif-backend
> 289:          3          0     Dynamic-irq  blkif-backend
> 290:         41          0     Dynamic-irq  vif10.1
> NMI:          0          0
> LOC:          0          0
> ERR:          0
> MIS:          0
>    
> 
> This above is with an e1000 for eth0.
> 
> Ted
> 
Changeset 7468:17a9f111fa93 does not have this problem.

Regards,
Ted


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

<Prev in Thread] Current Thread [Next in Thread>