Skip to contentSkip to conversation

2.6.25 -- long standing bug with usb after resume with 4GB ram

DISCUSSION Pavel Machek 3 participants 4 messages Mar 13, 2008 x86

lore
Share & tools
lore
#0 lore raw

Hi!

There are problems with usb after suspend/resume... it works as long as memory is limited to 3G -- probably because iommu/agpgart/something is not used in such case.

rmmod/insmod of ehci_hcd & ohci_hcd fixes that.

For testing with 2.6.25, you'll need aperture_64.c patch that makes iommu as nosave (or it oopses).

Problem is also present in opensuse10.3.
Pavel

Signature · 2 lines
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
#1 lore raw
Quoted 10 lines · Pavel Machek

Hi!

There are problems with usb after suspend/resume... it works as long as memory is limited to 3G -- probably because iommu/agpgart/something is not used in such case.

rmmod/insmod of ehci_hcd & ohci_hcd fixes that.

For testing with 2.6.25, you'll need aperture_64.c patch that makes iommu as nosave (or it oopses).

Any chance to push that one upstream?

Rafael

#2 lore raw
In reply to Pavel Machek
Quoted 10 lines · Pavel Machek

Hi!

There are problems with usb after suspend/resume... it works as long as memory is limited to 3G -- probably because iommu/agpgart/something is not used in such case.

rmmod/insmod of ehci_hcd & ohci_hcd fixes that.

For testing with 2.6.25, you'll need aperture_64.c patch that makes iommu as nosave (or it oopses).

Any pointer to where this patch is?

Can it go into 2.6.25?

thanks,

greg k-h

#3 lore raw

Hi!

Quoted 4 lines
Quoted 4 lines

There are problems with usb after suspend/resume... it works as long as memory is limited to 3G -- probably because iommu/agpgart/something is not used in such case.

Quoted 8 lines
Quoted 4 lines

rmmod/insmod of ehci_hcd & ohci_hcd fixes that.

For testing with 2.6.25, you'll need aperture_64.c patch that makes iommu as nosave (or it oopses).

Any pointer to where this patch is?

Can it go into 2.6.25?

Here it is: Yes, I guess it could go into 2.6.25...
Pavel

arch/x86/kernel/aperture_64.c +2 -0
index 608152a..88747f3 100644
@@ -18,6 +18,7 @@ #include <linux/pci_ids.h>
 #include <linux/pci.h>
 #include <linux/bitops.h>
 #include <linux/ioport.h>
+#include <linux/suspend.h>
 #include <asm/e820.h>
 #include <asm/io.h>
 #include <asm/gart.h>
@@ -76,6 +77,7 @@ static u32 __init allocate_aperture(void
 	printk(KERN_INFO "Mapping aperture over %d KB of RAM @ %lx\n",
 			aper_size >> 10, __pa(p));
 	insert_aperture_resource((u32)__pa(p), aper_size);
+	register_nosave_region((u32)__pa(p) >> PAGE_SHIFT, (u32)__pa(p+aper_size) >> PAGE_SHIFT);
 
 	return (u32)__pa(p);
 }
Signature · 3 lines
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
pomozte zachranit klanovicky les:  http://www.ujezdskystrom.info/