lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1211746106.6188.57.camel@localhost.localdomain>
Date:	Sun, 25 May 2008 22:08:26 +0200
From:	Patrick <ragamuffin@...acomm.ch>
To:	Pavel Machek <pavel@....cz>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: SB600 AHCI: Hard Disk Corruption

> iommu problem? Try it with mem=3G.

YES! :-) How did you know?

Even mem=4G did the trick. I should have tried that out long time back
(!), since it also used to make the fglrx driver problems I was dealing
with go away. These are solved now though, by a recent bios update
(Version 1705 2008/04/21). The fglrx driver used to work once but
stopped to work after an upgrade one day. Now with the new bios, the
current 
(ubuntu 8.04) version is working.

So now, using mem=4G, after successfully suspending once, my
ahci-scsi-libata-[sda] disk is still working. The error messages I
mentioned dissapeared from the kernel messages. Some other, usb driver
error messages, that used show up after resume have disappeared as well.

Anyway: using mem=4G is definitely no option! I get only 3G of usable
memory!!! *

So how are we going to get this fixed???

Should the IOMMU be reinitialized after resume? Or should the bios do it
but doesn't? ** On the m2a-vm, the "GART" seems to be used as iommu,
so... :-) ???

I put some kernel message logs here:
http://zefir.freesitespace.net/dmesg/
One log without mem=4G will also be there shortly, where you will see
the messages concerning the iommu (which seems to be unused right now).

Greets

*
> I suspect all you need is to burn one dimm.. or send it to me so that
> I can reproduce it ;-).
;-) ...looking back - all the trouble the 4G caused me till now, I
would have saved lots of time mounting only one 2G dimm in the first
place, even if the system was a little slower, but be it...

> Boot it from cd ;-).
I'm impatient...

** Seems, the SB600 is not to blame - alas sorry for the subject.

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ