* Rolf Eike Beer (eike-kernel@xxxxxxxxx) [060718 08:46]:
> Andreas Barth wrote:
>
> > [please Cc me, I'm currently not subscribed.]
>
> > I have noticed that one of my boxes stopped to boot correctly after
> > adding more memory (in total 6 GB) and loading an adjusted kernel for
> > that. After some testing around, we noticed that it is enough for the
> > kernel to boot correctly if we limit the kernel to use 4GB of memory.
> >
> > If the kernel has 6GB, I directly get error messages like:
> > SCSI device sda: 143299800 512-byte hdwr sectors (73369 MB)
> > sda: Write Protect is off
> > sda: got wrong page
> > sda: assuming drive cache: write through
> > SCSI device sda: 143299800 512-byte hdwr sectors (73369 MB)
> > sda: Write Protect is off
> > sda: got wrong page
>
> This is from sd.c::sd_read_cache_type
>
> > Any hints for me how I can use the full 6 GB of memory (and/or what I
> > should try out to find the bug)?
>
> Please change the printk in sd.c around 1482 that is
>
> printk(KERN_ERR "%s: got wrong page\n", diskname);
>
> to
>
> printk(KERN_ERR "%s: got wrong page (expect: 0x%x, got 0x%x)\n",
> diskname, modepage, buffer[offset]);
With this patch, it returns now:
SCSI device sda: 143299800 512-byte hdwr sectors (73369 MB)
sda: Write Protect is off
sda: got wrong page (expect: 0x8, got 0x0)
sda: assuming drive cache: write through
SCSI device sda: 143299800 512-byte hdwr sectors (73369 MB)
sda: Write Protect is off
sda: got wrong page (expect: 0x8, got 0x0)
(Full log with your and this patch:
--- a/drivers/scsi/gdth.c
+++ b/drivers/scsi/gdth.c
@@ -1543,7 +1543,7 @@ static int __init gdth_init_pci(gdth_pci
if (prot_ver < 0x2b) /* FW < x.43: no 64-bit DMA support */
ha->dma64_support = 0;
else
- ha->dma64_support = 1;
+ ha->dma64_support = 0;
}
return 1;
put at http://neualius.turmzimmer.net/~aba/6G/kernel-20060807.log .
If you rather want your patch alone, please tell me.)
Cheers,
Andi
--
http://home.arcor.de/andreas-barth/
-
: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
