Marco Gatti wrote:
Linus Torvalds schrieb:
Was there a dmesg out there somewhere?
With 4G of RAM, you probably have some of it above the 4GB mark
(because of RAM remapping etc, and the PCI decode hole in the low
4GB). It does sound like this is a DMA problem, and your controller
cannot
Marco Gatti wrote:
Linus Torvalds schrieb:
Was there a dmesg out there somewhere?
With 4G of RAM, you probably have some of it above the 4GB mark
(because of RAM remapping etc, and the PCI decode hole in the low
4GB). It does sound like this is a DMA problem, and your controller
cannot
On Sat, 8 Dec 2007, Marco Gatti wrote:
>
> Today, I tested with different amounts of RAM:
>
> 2 GB: everything works fine
> 4 GB: same issue as described before with allocating block in system zone
>
> So what to do, in order to use more than 2 Gigs of RAM?
Was there a dmesg out there
Linus Torvalds schrieb:
But the disk errors are something else, doesn't ring a bell. Sounds like
IO corruption on the group descriptor block or something like that. Might
be worth testing to see if the problem goes away with less than 4GB of
RAM..
Today, I tested with different amounts
Linus Torvalds schrieb:
But the disk errors are something else, doesn't ring a bell. Sounds like
IO corruption on the group descriptor block or something like that. Might
be worth testing to see if the problem goes away with less than 4GB of
RAM..
Today, I tested with different amounts
On Sat, 8 Dec 2007, Marco Gatti wrote:
Today, I tested with different amounts of RAM:
2 GB: everything works fine
4 GB: same issue as described before with allocating block in system zone
So what to do, in order to use more than 2 Gigs of RAM?
Was there a dmesg out there somewhere?
Linus Torvalds schrieb:
But the disk errors are something else, doesn't ring a bell. Sounds like
IO corruption on the group descriptor block or something like that. Might
be worth testing to see if the problem goes away with less than 4GB of
RAM..
Thanks, I'll try this, to see if there's
Andrew Morton schrieb:
But the effect is under every circumstances described above that I got
after an unspecific time EXT3-fs errors. I tried to use different
partitions, one for root and data, got errors on both.
Dec 3 15:05:34 adira EXT3-fs error (device sdb4): ext3_new_block:
Allocating
On Thu, 6 Dec 2007, Andrew Morton wrote:
>
> http://bugs.gentoo.org/attachment.cgi?id=135761=view
>
> It disables PCI BARs during sizing. ISTR Linus opining that this was the
> wrong thing to do?
It looks ok now that it doesn't do it for host controllers. I guess we
could just apply it.
>
On Tue, 04 Dec 2007 21:54:57 +0100
Marco Gatti <[EMAIL PROTECTED]> wrote:
> Hello,
>
> I have a brand new Fujitsu-Siemens Celsius W360 pc with a FSC D2587-A1
> motherboard. It has a intel q35 chipset. In bios I have the sata
> controller in pure AHCI mode (legacy pata disabled). On windows
>
On Tue, 04 Dec 2007 21:54:57 +0100
Marco Gatti [EMAIL PROTECTED] wrote:
Hello,
I have a brand new Fujitsu-Siemens Celsius W360 pc with a FSC D2587-A1
motherboard. It has a intel q35 chipset. In bios I have the sata
controller in pure AHCI mode (legacy pata disabled). On windows
On Thu, 6 Dec 2007, Andrew Morton wrote:
http://bugs.gentoo.org/attachment.cgi?id=135761action=view
It disables PCI BARs during sizing. ISTR Linus opining that this was the
wrong thing to do?
It looks ok now that it doesn't do it for host controllers. I guess we
could just apply it.
Andrew Morton schrieb:
But the effect is under every circumstances described above that I got
after an unspecific time EXT3-fs errors. I tried to use different
partitions, one for root and data, got errors on both.
Dec 3 15:05:34 adira EXT3-fs error (device sdb4): ext3_new_block:
Allocating
Linus Torvalds schrieb:
But the disk errors are something else, doesn't ring a bell. Sounds like
IO corruption on the group descriptor block or something like that. Might
be worth testing to see if the problem goes away with less than 4GB of
RAM..
Thanks, I'll try this, to see if there's
14 matches
Mail list logo
