Jens Axboe wrote:
On Thu, Oct 18 2007, Jeff Garzik wrote:
Ingo Molnar wrote:
* Jens Axboe <[email protected]> wrote:
--- a/drivers/scsi/scsi_lib.c
+++ b/drivers/scsi/scsi_lib.c
@@ -39,7 +39,7 @@
* (unless chaining is used). Should ideally fit inside a single page,
to
* avoid a higher order allocation.
*/
-#define SCSI_MAX_SG_SEGMENTS 128
+#define SCSI_MAX_SG_SEGMENTS 129
this one finally made the trick and it's booting fine now, without any
crashes!
Alas, this didn't help me here. I did manage to capture the error messages
this time, and in the two machines I'm actively testing on, sata_mv is the
driver that's dying in both cases. Machine A additionally has sata_nv,
which is working. Machine B additionally has ata_piix, which is working.
So in both cases, its sata_mv that is throwing SError complaints:
Theory - ata_sg_is_last() isn't returning true for the last entry. Can
you double check that it correcly marks the last entry in mv_fill_sg()?
Alternatively, just try this patch.
Will check in a few minutes, after my current test: I noticed that
sg_tablesize in sata_mv is not LIBATA_MAX_PRD. This is expected
behavior, but I wonder if that difference -- most notably being smaller
than SCSI_MAX_SG_SEGMENTS -- would trigger any latent bugs.
Anyway, we will both have answers momentarily...
Jeff
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
