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
Created attachment 258586 [details] .config for the non working kernel Of course here is the .config file
Please test with the latest 2.6.37 kernel
Reopen after testing with 2.6.38 and if you still have the same issue