Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!

Bug 350310

Summary: sym53c8xx stops working in gentoo-sources-2.6.36-r5
Product: Gentoo Linux Reporter: Konstantin Agouros <elwood>
Component: [OLD] Core systemAssignee: Gentoo Kernel Bug Wranglers and Kernel Maintainers <kernel>
Status: RESOLVED TEST-REQUEST    
Severity: normal    
Priority: High    
Version: unspecified   
Hardware: AMD64   
OS: Linux   
Whiteboard:
Package list:
Runtime testing required: ---
Attachments: .config for the non working kernel

Description Konstantin Agouros 2011-01-01 19:02:25 UTC
With the boot of 2.6.35-r5 my scsi controller (a dawi control) stopped working. All I found, when the module was loaded was:
Jan  1 18:17:14 rumba kernel: [    9.523533] sym53c8xx 0000:00:0c.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
Jan  1 18:17:14 rumba kernel: [    9.524677] sym0: <875> rev 0x26 at pci 0000:00:0c.0 irq 17
Jan  1 18:17:14 rumba kernel: [    9.574370] sym0: No NVRAM, ID 7, Fast-20, SE, parity checking
Jan  1 18:17:14 rumba kernel: [    9.576012] sym0: SCSI BUS has been reset.
Jan  1 18:17:14 rumba kernel: [    9.646164] scsi1 : sym-2.2.3
 and a bit later:
Jan  1 18:17:14 rumba kernel: [   14.334884] scsi target1:0:6: FAST-20 WIDE SCSI 40.0 MB/s ST (50 ns, offset 16)
Jan  1 18:17:14 rumba kernel: [   14.335920] sym0: SCSI parity error detected: SCR1=1 DBC=11000004 SBCL=ae
Jan  1 18:17:14 rumba kernel: [   14.338990] scsi target1:0:6: FAST-20 SCSI 20.0 MB/s ST (50 ns, offset 16)

Problem does not occur in lower kernels.

Reproducible: Always

Steps to Reproduce:
1. Boot the kernel


Actual Results:  
scsi device (a tape drive) not working

Expected Results:  
scsi device (a tape drive) accessible
Comment 1 Konstantin Agouros 2011-01-01 19:03:28 UTC
Created attachment 258586 [details]
.config for the non working kernel

Of course here is the .config file
Comment 2 Mike Pagano gentoo-dev 2011-03-06 20:25:28 UTC
Please test with the latest 2.6.37 kernel
Comment 3 Mike Pagano gentoo-dev 2011-03-21 18:51:42 UTC
Reopen after testing with 2.6.38 and if you still have the same issue