Messages in this thread | | | Date | Thu, 11 Mar 2004 22:35:05 +0100 (CET) | From | Guennadi Liakhovetski <> | Subject | RE: sym53c8xx_2 driver and tekram dc-390u2w kernel-2.6.x |
| |
On Fri, 27 Feb 2004, Brad Cramer wrote:
> I installed a debian kernel image (kernel_image-2.4.24-1-k7) to tell if this > was just a problem with the driver or because of the upgrade to kernel 2.6.x > I the sym53c8xx and sym53c8xx_2 drivers are modules and this is what I got.
...
> bigdaddy:~# mount /var > reiserfs: found format "3.6" with standard journal > reiserfs: checking transaction log (device sd(8,2)) ... > for (sd(8,2)) > SCSI disk error : host 0 channel 0 id 0 lun 0 return code = 8000002 > Current sd08:02: sense key Aborted Command > Additional sense indicates Scsi parity error > I/O error: dev 08:02, sector 65680 > sd(8,2):reiserfs: journal-837: IO error during journal replay > sd(8,2):Replay Failure, unable to mount > sd(8,2):sh-2022: reiserfs_read_super: unable to initialize journal space > mount: wrong fs type, bad option, bad superblock on /dev/sda2, > or too many mounted file systems
Ok, still hoping to attract the help from some more experienced in SCSI and more knowledgable about this specific driver, here's one more thing I can suggest - can you enable debugging through the respective /proc-files (see, e.g., drivers/scsi/sym53c8xx_2/Documentation.txt in 2.4). I guess, useful would be tiny,result,queue. Possibly, for both drivers, but be prepared - for the working one it'll produce lots of output, I guess...
Thanks Guennadi --- Guennadi Liakhovetski
- 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/
| |