https://bugzilla.novell.com/show_bug.cgi?id=435314 Michal Seben changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mseben@novell.com AssignedTo|bnc-team-screening@forge.provo.novell.com |kernel-maintainers@forge.provo.novell.com -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=435314 User michael.csj@gmail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=435314#c2 --- Comment #2 from Michael Cheah 2008-10-15 12:00:33 MDT --- I'm sorry that I'm afraid I will be unable to test it within the next two weeks. This is my primary computer and I do need to use it now since i should be doing and submitting my final assigments soon. The bug is reproducible on my laptop with latest kernel + nVidia binary driver + 4GB ram. It actually happened to me twice. Once more after I reinstalled the whole system. However, it might not be a nVidia-specific bug. (There is one reply in Ubuntu lauchpad which says it happen on machine with Ati graphic card as well) Or perhaps both nVidia and ATI driver have this bug. I'm unable to test it in VirtualBox since the bug require 4GB ram to reproduce anyway. For the moment being I think a warning should be issues to all openSUSE user running a similar hardware specification as me. Thank you. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=435314 User michael.csj@gmail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=435314#c4 Michael Cheah changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|michael.csj@gmail.com | --- Comment #4 from Michael Cheah 2008-10-18 05:03:32 MDT --- Somehow I found time to reproduce the bug again today. The result is THIS BUG HAPPENS EVEN WITH ONLY THE nv DRIVER LOADED.I ran three round of tests today. And the last one reproduce the bug. Test 1: 1) I compiled the latest nvidia binary driver (177.80). 2) Restarted my laptop and at the Grub Startup Screen I passed mem=4G to the kernel. 3) The nvidia driver was loaded automatically. I logged in using root. Opened the terminal and umount my /home directory and Drive C to prevent data corruption in these two partitions. 4) I launched suspend to RAM from the SUSE Menu. The laptop entered standby and woke up fine. No data corruption. Test 2: 1) I modified xorg.conf to use the nv driver. Restarted the computer, and at the Grub Startup Screen I passed mem=4G to the kernel. 2) The nv driver was loaded automatically. I ran lsmod and checked the nvidia module was not present. 4) Like Test 1, I umount-ed my partitions. 3) I launch suspend to RAM from the SUSE Menu. The laptop entered standby successfully, but the display did not came back alive when I tried to wake it up. The keyboard was responsive though. So I pressed CTRL + ALT + SHIFT + PG DOWN (KDE hotkey for shutdown). 4) The laptop shutdown fine and upon reboot there was no data corruption as well. Test 3: 1) I repeated the procedure for Test 2, except that I did not pass mem=4G to the kernel. 2) The laptop entered standby successfully and the keyboard was responsive upon wakeup. Pressing CTRL + ALT + SHIFT + PG DOWN has no effect though. I had to force shutdown the laptop using the power button. 3) Upon reboot, Grub showed "Error 17". My root partition was corrupted and running fsck did not recover the problem. I have reinstalled openSUSE before posting this bug report. So, in conclusion passing mem=4G prevents the disk corruption after standby/wakeup cycle but it reduced my visible RAM from 3.75GB to 2.89GB. Without passing mem=4G to the kernel even nv driver could cause disk corruption. Sorry for the report-like format. I guess I've done too many lab reports this semester. ;-) Thank you. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=435314 User pavel@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=435314#c5 Pavel Machek changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |rjw@novell.com --- Comment #5 from Pavel Machek 2008-10-21 02:50:05 MDT --- It should be possible to work around this by using iommu=soft (and full memory). Can you confirm that? If so it is the "we don't save the iommu/agpgart state around suspend" problem... -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=435314 Pavel Machek changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|Major Disk Corruption after suspend to RAM |Major Disk Corruption after suspend to RAM on | |4GB system -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=435314 User rjw@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=435314#c7 --- Comment #7 from Rafael Wysocki 2008-10-22 16:49:18 MDT --- This problem should be fixed in the last mainline kernel as well as in the kernels at ftp://ftp.suse.com/pub/projects/kernel/kotd/HEAD/ . It should be fixed in openSUSE 11.1 too. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=435314 User rjw@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=435314#c9 --- Comment #9 from Rafael Wysocki 2008-10-25 04:06:47 MDT --- Yes, the GART IOMMU is safe wrt suspend/resume in 2.6.26 and later kernels, while the openSUSE 11.1 kernel will be based on 2.6.27. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.