** Changed in: fedora
Importance: Unknown => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/203537
Title:
Hardy -- Suspend RUINS FILESYSTEM
To manage notifications about this bug go to:
ht
** Changed in: fedora
Status: Confirmed => Won't Fix
--
Hardy -- Suspend RUINS FILESYSTEM
https://bugs.launchpad.net/bugs/203537
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu
There is a workaround (iommu=soft) and this problem has been fixed in later
kernels. Due to the version
span between those kernels and hardy, backporting a patch would be too risky.
Users who need the
hardware iommu for performance should upgrade to get a later kernel.
** Changed in: linux (Ub
** Changed in: linux (Ubuntu Hardy)
Assignee: (unassigned) => Jim Lieb (lieb)
Status: Triaged => In Progress
--
Hardy -- Suspend RUINS FILESYSTEM
https://bugs.launchpad.net/bugs/203537
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to U
Thanks everyone for testing Intrepid. ichudov, since you are the
original bug reporter and can confirm this is resolved for you with
Intrepid I'm marking this fixed released for the Intrepid release and
will approve the Hardy nomination. Thanks.
** Changed in: linux (Ubuntu)
Status: Triag
I confirm this, I suspend several times a day on Intrepid
i
On Thu, Nov 20, 2008 at 02:57:54PM -, arturj wrote:
> I am now running a fresh installation of Ubuntu 8.10 (final release) and
> was brave enough (due to some hints in the internet which state that the
> bug should have been resolved
I am now running a fresh installation of Ubuntu 8.10 (final release) and
was brave enough (due to some hints in the internet which state that the
bug should have been resolved) to test it. So I suspended the system and
tried to resume without iommu=soft optoin. I have NO Grub-17 error any
more. I d
Just wondering if this bug is still there with the latest kernel in
hardy (2.6.24-21). I noticed that in the changes for this new kernel it
fixes Bug #257293
(https://bugs.launchpad.net/ubuntu/+source/linux/+bug/257293), which
seems very similar to this one. Has anyone tested this? Without the
iomm
I have the same issue as everyone else here. Motherboard is an Asus M2N-
MX SE+ with an AMD Athlon64 X2 5000+, not overclocked.
I downloaded and installed the current 8.10 beta. When suspended, the
system still hung on resume, but after hitting reset, I got the GRUB
menu and booted just fine, rath
I booted from Intrepid Ibex 8.10 Alpha5 Live-CD and did a "dmesg". All
"AGP" and "IOMMU" relevant messages seem to be the same as with 8.04. I
have done no suspend testing, since it needs nvidia binary drivers
installed on my system to resume.
grep "AGP" dmesg-intrepid
[0.004000] No AGP bridge
The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the
upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would
appreciate it if you could please test this newer 2.6.27 Ubuntu kernel.
There are one of two ways you should be able to test:
1) If you are comfortable
Same issue here, also with amd64 and nvidia-glx-new running hardy.
After hibernating, system locked and then grub error 17... my first
partition became unmountable
Fortunately I was very lucky and was able to recover the partition
with
e2fsck dev/sda1
without even a file in Lost+found
Just want to add that the hibernate->ruined filesystem bug is also a
problem on my
CPU AMD 64 X2 Dual Core Processor 5200+
MB M2A-VM HDMI
GPU ATI RADEON HD3870 (restricted drivers)
Ubuntu 8.04 (hardy) (64bit)
2.6.24-19-generic
everything up-to-date via update-manager as of 2008-06-24
--
Hard
Interesting... with iommu=soft, suspend/hibernate/resume works, but it
seems to confuse the graphics card driver. My laptop has a Nvidia
GeForce Go 7600 (256MB), and before suspending, adjusting brightness
with nvclock works just fine. After resuming, the display is at maximum
brightness and nvc
Hello,
beside iommu=soft which I proposed and tested successfully I also
already had tested:
- iommu=noagp NO success
- iommu=noaperture SUCCESS (seems similar to =soft according to dmesg output)
- iommu=memaper1,2,3 NO success
Still I agree, that this should be considered as a "workaround" as A
Let me preface this by saying, I am no expert, I just did some googling,
and I am most likely getting the info wrong.
BUT, from what I found, it looks like the kernel thinks that the IOMMU
is setup wrong in the BIOS so it makes some changes at startup. I think
that is what the "Using GART IOMMU" a
I can confirm that too iommu=soft fixes this bug
--
Hardy -- Suspend RUINS FILESYSTEM
https://bugs.launchpad.net/bugs/203537
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https:
I can confirm that the 'iommu=soft' option fixes this. I'm running hardy
on a Vostro 1000 with 4gb of RAM.
Thanks arturj!! You made my ubuntu usable again (I had to tune2fs -c 0
my filesystems due to the frequent boots so hibernate is really
welcome).
--
Hardy -- Suspend RUINS FILESYSTEM
https:/
I am the original submitter of this bug. For months, I avoided
hibernating on this laptop.
After seeing messages about IOMMU=soft, I verified that I also have
messages about IOMMU in my dmesg.
I then added iommu=soft to kopt setting in /boot/grub/menu.lst and reran
update-grub.
After this I rebo
Some more details:
Prior to enabling the "iommu=soft" kernel option, this is what dmesg shows in
regards to IOMMU:
/var/log$ zgrep IOMMU dmesg.1.gz
[ 22.839979] Please enable the IOMMU option in the BIOS setup
[ 23.667358] PCI-DMA: using GART IOMMU.
[ 23.667365] PCI-DMA: Reserving 64MB of
YES! arturj, THANK YOU.
I can confirm that the kernel option "iommu=soft" fixes this problem. I
can now suspend/hibernate/resume just fine. All 4GB of my RAM seem to
be available. I'm using 64-bit Hardy on an Everex XT5000T with 2 hard
drives, 100GB and 250GB, no problem. Now that this is wor
Hello,
reading in different forums I get more and more the idea that the IOMMU
implementation in the GART driver is to blame.
To get back all your memory you can try the kernel option "iommu=soft"
which forces a software emulated IOMMU to take over instead the AMD64
hardware IOMMU. Different peo
Hello,
I can confirm this "fix".
Adding mem=3G to boot options "fixes" the bug.
Now I want my 1GB of missing Ram back!! ;)
Regards oliver
--
Hardy -- Suspend RUINS FILESYSTEM
https://bugs.launchpad.net/bugs/203537
You received this bug notification because you are a member of Ubuntu
Bugs, which
Hello again,
in some other forums I found this:
"> iommu problem? Try it with mem=3G.
YES! :-) How did you know?
Even mem=4G did the trick."
Problem: even with "mem=4GB" option, the kernel only sees 3GB of useable
RAM. IOMMU seens to cause problems.
dmesg W/O mem= option:
[17180642.907074] Ch
just wanted to add that i also have 2x2GB and a 500GB HD connected via
SATA to a SB600 south-bridge.
--
Hardy -- Suspend RUINS FILESYSTEM
https://bugs.launchpad.net/bugs/203537
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-b
APPENDIX:
Hello again,
some further informations regarding my hardware:
Mainboard Asus M2A-VM with ATI 690G and ATI SB600 Chipsets. SB600 provides the
SATA interface
AMD64x2 CPU
2x2GB of RAM
My old system not only had a 200GB SATA disk but also only 2x512MB of
RAM (and everythin was OK under HA
Hallo,
same here on my AMD 650G chipset Mobo.
I was running a SATA1 HD with 200GB and no problem (nvidia-glx-new
grafix driver). After moving (fresh install of hardy) to a SATA2 HD with
500GB and 32MB of cache my filesystem gets totaly corrupted by Suspend-
to-RAM. Resuming first gives me some er
** Changed in: fedora
Status: Unknown => Confirmed
--
Hardy -- Suspend RUINS FILESYSTEM
https://bugs.launchpad.net/bugs/203537
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.c
** Bug watch added: Red Hat Bugzilla #451404
https://bugzilla.redhat.com/show_bug.cgi?id=451404
** Also affects: fedora via
https://bugzilla.redhat.com/show_bug.cgi?id=451404
Importance: Unknown
Status: Unknown
--
Hardy -- Suspend RUINS FILESYSTEM
https://bugs.launchpad.net/bugs/
Hello,
same here on my AMD 780G chipset system.
I just bought a Gigabyte GA-MA78GM-S2H board with a AMD X2 4850e cpu and MDT
2x2048-800-CL-KIT AMD Edition memory.
Happens on a fully updated backports & proposed system and on a fresh
setup system too.
I was able to grep (alias write down on pape
Exactt, sorry to hear you have joined the club. Just for completeness, I
also experienced the bug with amd64 and nvidia-glx-new.
--
Hardy -- Suspend RUINS FILESYSTEM
https://bugs.launchpad.net/bugs/203537
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscri
this bug left my system partition as well as the data partition as a bunch of
files and directories in lost+found. this is a disaster!
for completeness and hopefully a fast bug fix i want to mention that i was
using 2.6.24-38(?, the latest from proposed) kernel and that the system
suspended and
i just wanted to try if suspend2ram works. i really didn't expect my
filesystem to vanish. this is really critical! could it be related
to nvidia? i am/was running latest hardy amd64 with nvidia-glx-new
drivers installed. ended up with grub error 17 as well...
--
Hardy -- Suspend RUINS FILESY
** Summary changed:
- Hardy -- pm-suspend RUINS PARTITION TABLE
+ Hardy -- Suspend RUINS FILESYSTEM
--
Hardy -- Suspend RUINS FILESYSTEM
https://bugs.launchpad.net/bugs/203537
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-b
34 matches
Mail list logo
