2.6.9-rc2-mm3: swsusp horribly slow on AMD64

2.6.9-rc2-mm3: swsusp horribly slow on AMD64

[Rafael J. Wysocki]

Pavel,

I've just tried to suspend my box and I must admit I've given up after 30 
minutes (sic!) of waiting when there were only 12% of pages written to disk.  
Apparently, swsusp slows down to an unacceptable level after saying "PM: 
Writing image to disk".

The box is an Athlon 64-based notebook.  The .config is available at:
http://www.sisk.pl/kernel/040925/2.6.9-rc2-mm3.config
and the output of dmesg is available at:
http://www.sisk.pl/kernel/040925/2.6.9-rc2-mm3-dmesg.log

Greets,
RJW

-- 
- Would you tell me, please, which way I ought to go from here?
- That depends a good deal on where you want to get to.
		-- Lewis Carroll "Alice's Adventures in Wonderland"

Re: 2.6.9-rc2-mm3: swsusp horribly slow on AMD64

[Stefan Seyfried]

Rafael J. Wysocki wrote:
> Pavel,
> 
> I've just tried to suspend my box and I must admit I've given up after 30 
> minutes (sic!) of waiting when there were only 12% of pages written to disk.  
> Apparently, swsusp slows down to an unacceptable level after saying "PM: 
> Writing image to disk".

is this reproducible? can you get sysrq-t / sysrq-p while it is slow
writing to disk?
I have seen this, too but i cannot nail it down to some specific
pattern, it just "sometimes" is slow. Sysrq-p shows me it's almost
always in "pccardd" (where it shouldn't be during suspend, iiuc).
Unfortunately Pavel does not see this so we have to convince him that
this is really a problem ;-)
So if you can reproduce this, it would be a step in the right direction.

    Stefan

Re: 2.6.9-rc2-mm3: swsusp horribly slow on AMD64

[Rafael J. Wysocki]

On Saturday 25 of September 2004 23:33, Stefan Seyfried wrote:
> Rafael J. Wysocki wrote:
> > Pavel,
> > 
> > I've just tried to suspend my box and I must admit I've given up after 30 
> > minutes (sic!) of waiting when there were only 12% of pages written to 
disk.  
> > Apparently, swsusp slows down to an unacceptable level after saying "PM: 
> > Writing image to disk".
> 
> is this reproducible?

Yes, it is.  100% of the time, AFAICT, though I've tried it for only a couple 
of times.

> can you get sysrq-t / sysrq-p while it is slow 
> writing to disk?

Well, I'll try, but sysrq didn't work for me at all on 2.6.9-rc2-mm1, so I'm 
not sure if I really can.

> I have seen this, too but i cannot nail it down to some specific
> pattern, it just "sometimes" is slow. Sysrq-p shows me it's almost
> always in "pccardd" (where it shouldn't be during suspend, iiuc).
> Unfortunately Pavel does not see this so we have to convince him that
> this is really a problem ;-)
> So if you can reproduce this, it would be a step in the right direction.

It seems that I can. ;-)

Could it be possible to printk time along with the percentage info (for 
debugging purposes only, of course)?

Greets,
RJW

-- 
- Would you tell me, please, which way I ought to go from here?
- That depends a good deal on where you want to get to.
		-- Lewis Carroll "Alice's Adventures in Wonderland"

Re: 2.6.9-rc2-mm3: swsusp horribly slow on AMD64

[Pavel Machek]

Hi!

> > I have seen this, too but i cannot nail it down to some specific
> > pattern, it just "sometimes" is slow. Sysrq-p shows me it's almost
> > always in "pccardd" (where it shouldn't be during suspend, iiuc).
> > Unfortunately Pavel does not see this so we have to convince him that
> > this is really a problem ;-)
> > So if you can reproduce this, it would be a step in the right direction.
> 
> It seems that I can. ;-)
> 
> Could it be possible to printk time along with the percentage info (for 
> debugging purposes only, of course)?

Sure, feel free to printk("%d", jiffies/HZ).
								Pavel

-- 
People were complaining that M$ turns users into beta-testers...
...jr ghea gurz vagb qrirybcref, naq gurl frrz gb yvxr vg gung jnl!

Re: 2.6.9-rc2-mm3: swsusp horribly slow on AMD64

[Rafael J. Wysocki]

On Sunday 26 of September 2004 12:02, Rafael J. Wysocki wrote:
> On Saturday 25 of September 2004 23:33, Stefan Seyfried wrote:
> > Rafael J. Wysocki wrote:
> > > Pavel,
> > > 
> > > I've just tried to suspend my box and I must admit I've given up after 
30 
> > > minutes (sic!) of waiting when there were only 12% of pages written to 
> disk.  
> > > Apparently, swsusp slows down to an unacceptable level after saying "PM: 
> > > Writing image to disk".
> > 
> > is this reproducible?
> 
> Yes, it is.  100% of the time, AFAICT, though I've tried it for only a 
couple 
> of times.

I can confirm that it's 100% reproducible.

> > can you get sysrq-t / sysrq-p while it is slow 
> > writing to disk?
> 
> Well, I'll try, but sysrq didn't work for me at all on 2.6.9-rc2-mm1, so I'm 
> not sure if I really can.

As I suspected, the damn sysrq doesn't work (/proc/sysrq-trigger does, so it 
_is_ compiled in, sigh).

I'm only able to get swsusp output from the serial console:

Stopping tasks: ==============================|
Freeing memory... done (18812 pages freed)
PM: Attempting to suspend to disk.
PM: snapshotting memory.
swsusp: critical section:
..<7>[nosave pfn 0x588]......................................swsusp: Need to 
copy 11017 pages
suspend: (pages needed: 11017 + 512 free: 119862)
..<7>[nosave pfn 0x588]......................................swsusp: critical 
section/: done (11145 pages copied)
PM: writing image.

and it slows down _here_:

PCI: Setting latency timer of device 0000:00:02.0 to 64
PCI: Setting latency timer of device 0000:00:02.1 to 64
PCI: Setting latency timer of device 0000:00:02.2 to 64
ACPI: PCI interrupt 0000:00:06.0[A] -> GSI 5 (level, low) -> IRQ 5
PCI: Setting latency timer of device 0000:00:06.0 to 64
ACPI: PCI interrupt 0000:02:00.0[A] -> GSI 11 (level, low) -> IRQ 11
ACPI: PCI interrupt 0000:02:01.2[C] -> GSI 11 (level, low) -> IRQ 11
 swsusp: Version: 132617
 swsusp: Num Pages: 130880
 swsusp: UTS Sys: Linux
 swsusp: UTS Node: albercik
 swsusp: UTS Release: 2.6.9-rc2-mm3
 swsusp: UTS Version: #1 Fri Sep 24 11:52:15 CEST 2004
 swsusp: UTS Machine: x86_64
 swsusp: UTS Domain:
 swsusp: CPUs: 1
 swsusp: Image: 11145 Pages
 swsusp: Pagedir: 0 Pages
Writing data to swap (11145 pages)...   0%

Here I have to press the red button unless I want to wait for a couple of 
hours.  I'll send you more info when there's more.

Greets,
RJW

-- 
- Would you tell me, please, which way I ought to go from here?
- That depends a good deal on where you want to get to.
		-- Lewis Carroll "Alice's Adventures in Wonderland"

Re: 2.6.9-rc2-mm3: swsusp horribly slow on AMD64

[Pavel Machek]

Hi!

> > Well, I'll try, but sysrq didn't work for me at all on 2.6.9-rc2-mm1, so I'm 
> > not sure if I really can.
> 
> As I suspected, the damn sysrq doesn't work (/proc/sysrq-trigger does, so it 
> _is_ compiled in, sigh).

Map sysrq to some other key; sysrq is hard to press on notebooks.
				Pavel
-- 
64 bytes from 195.113.31.123: icmp_seq=28 ttl=51 time=448769.1 ms         

Re: 2.6.9-rc2-mm3: swsusp horribly slow on AMD64

[Rafael J. Wysocki]

On Sunday 26 of September 2004 13:45, Rafael J. Wysocki wrote:
[-- snip --]
>  swsusp: Image: 11145 Pages
>  swsusp: Pagedir: 0 Pages
> Writing data to swap (11145 pages)...   0%
> 
> Here I have to press the red button unless I want to wait for a couple of 
> hours.  I'll send you more info when there's more.

I figured out that the slowdown occurs in device_resume(), so I put a printk() 
in dpm_resume(), like this:

--- drivers/base/power/resume.c 2004-09-26 16:44:09.000000000 +0200
+++ drivers/base/power/resume.c.rjw     2004-09-26 16:43:57.000000000 +0200
@@ -34,6 +34,7 @@
        while(!list_empty(&dpm_off)) {
                struct list_head * entry = dpm_off.next;
                struct device * dev = to_device(entry);
+               printk("%ld\n",  jiffies/HZ);
                list_del_init(entry);

                if (!dev->power.prev_state)

>From it, I have got the following results:

PM: writing image.
4294807
[ ... ]
4294807
PCI: Setting latency timer of device 0000:00:02.0 to 64
4294813
PCI: Setting latency timer of device 0000:00:02.1 to 64
4294817
PCI: Setting latency timer of device 0000:00:02.2 to 64
4294821
ACPI: PCI interrupt 0000:00:06.0[A] -> GSI 5 (level, low) -> IRQ 5
PCI: Setting latency timer of device 0000:00:06.0 to 64
4294822
[ ... ]
4294822
ACPI: PCI interrupt 0000:02:00.0[A] -> GSI 11 (level, low) -> IRQ 11
4294822
4294825
4294828
ACPI: PCI interrupt 0000:02:01.2[C] -> GSI 11 (level, low) -> IRQ 11
4294828
[ ... ]
4294828
4294829
[ ... ]
4294829

As you can see, the difference between the first and the last timestamp is 22.  
However, if I make the same change in 2.6.9-rc2-mm1, I get:

PM: writing image.
4294761
[ ... ]
4294761
PCI: Setting latency timer of device 0000:00:02.0 to 64
4294761
PCI: Setting latency timer of device 0000:00:02.1 to 64
4294761
PCI: Setting latency timer of device 0000:00:02.2 to 64
4294761
ACPI: PCI interrupt 0000:00:06.0[A] -> GSI 5 (level, low) -> IRQ 5
PCI: Setting latency timer of device 0000:00:06.0 to 64
4294762
[ ... ]
4294762
ACPI: PCI interrupt 0000:02:00.0[A] -> GSI 11 (level, low) -> IRQ 11
4294762
4294762
4294762
ACPI: PCI interrupt 0000:02:01.2[C] -> GSI 11 (level, low) -> IRQ 11
4294762
[ ... ]
4294762

so the difference between the first and the last timestamp is 1 (ie 22 times 
less).

Now, I have no idea about what may be responsible for such a slowdown, but I 
suspect that it's related to PCI.  I really don't know what to look for, so 
if you can give me any hint, please do.

Greets,
RJW

-- 
- Would you tell me, please, which way I ought to go from here?
- That depends a good deal on where you want to get to.
		-- Lewis Carroll "Alice's Adventures in Wonderland"

Re: 2.6.9-rc2-mm3: swsusp horribly slow on AMD64

[Pavel Machek]

Hi!

> [-- snip --]
> >  swsusp: Image: 11145 Pages
> >  swsusp: Pagedir: 0 Pages
> > Writing data to swap (11145 pages)...   0%
> > 
> > Here I have to press the red button unless I want to wait for a couple of 
> > hours.  I'll send you more info when there's more.
> 
> I figured out that the slowdown occurs in device_resume(), so I put a printk() 
> in dpm_resume(), like this:

When you hit "writing data to swap", device_resume should be no longer
happening.

Try to unload all modules etc, see if it goes away. If not, fix sysrq
to work for you, and look at backtrace.
								Pavel
-- 
People were complaining that M$ turns users into beta-testers...
...jr ghea gurz vagb qrirybcref, naq gurl frrz gb yvxr vg gung jnl!

Re: 2.6.9-rc2-mm3: swsusp horribly slow on AMD64

[Rafael J. Wysocki]

On Sunday 26 of September 2004 20:34, Pavel Machek wrote:
> Hi!
> 
> > [-- snip --]
> > >  swsusp: Image: 11145 Pages
> > >  swsusp: Pagedir: 0 Pages
> > > Writing data to swap (11145 pages)...   0%
> > > 
> > > Here I have to press the red button unless I want to wait for a couple 
of 
> > > hours.  I'll send you more info when there's more.
> > 
> > I figured out that the slowdown occurs in device_resume(), so I put a 
printk() 
> > in dpm_resume(), like this:
> 
> When you hit "writing data to swap", device_resume should be no longer
> happening.

It isn't.  Still, device_resume() is called explicitly by swsusp_write() and 
IMO what happens is that the resume() function of one of the drivers does 
something that causes the system to slow down, which affects the writing 
operation (please note that the clock seems to be unaffected, though).  I'll 
try to narrow it.

> Try to unload all modules etc, see if it goes away.

I guess it will, but I'll check.

> If not, fix sysrq  to work for you, and look at backtrace.

This would be more time-consuming. :-)

Greets,
RJW

-- 
- Would you tell me, please, which way I ought to go from here?
- That depends a good deal on where you want to get to.
		-- Lewis Carroll "Alice's Adventures in Wonderland"

Re: 2.6.9-rc2-mm3: swsusp horribly slow on AMD64

[Stefan Seyfried]

[-- Attachment #1: Type: text/plain, Size: 760 bytes --]

Rafael J. Wysocki wrote:

>>Try to unload all modules etc, see if it goes away.
> 
> I guess it will, but I'll check.

please try attached patch first. The comments should explain it pretty
well. It seems to have helped me: without it, sysrq-p during writing
(even if not that slow) almost always was in pccardd, now it is idling
in swapper task.
Maybe i am totally wrong but you may give it a shot.

>>If not, fix sysrq  to work for you, and look at backtrace.
> 
> This would be more time-consuming. :-)

maybe you just press wrong keys? On my Dell D600, although SysRQ is in
blue on PrtSc, no Fn-Key is needed but only ALT-PrtSc.
-- 
Stefan Seyfried, QA / R&D Team Mobile Devices, SUSE LINUX AG Nürnberg.

"Any ideas, John?"
"Well, surrounding them's out."

[-- Attachment #2: swsusp-disable-irqs-before-writing-image.diff --]
[-- Type: text/x-patch, Size: 1780 bytes --]

Only in kernel/power/: .built-in.o.cmd
Only in kernel/power/: .console.o.cmd
Only in kernel/power/: .disk.o.cmd
Only in kernel/power/: .main.o.cmd
Only in kernel/power/: .pm.o.cmd
Only in kernel/power/: .poweroff.o.cmd
Only in kernel/power/: .process.o.cmd
Only in kernel/power/: .swsusp.o.cmd
Only in kernel/power/: built-in.o
Only in kernel/power/: console.o
diff -up ../linux-2.6.8-14/kernel/power/disk.c kernel/power/disk.c
--- ../linux-2.6.8-14/kernel/power/disk.c	2004-09-23 02:22:50.000000000 +0200
+++ kernel/power/disk.c	2004-09-26 22:41:14.735864464 +0200
@@ -182,6 +182,13 @@ int pm_suspend_disk(void)
 		goto Done;
 
 	if (in_suspend) {
+		/*
+		 * during swsusp_suspend, the machine basically suspends,
+		 * does the atomic copy and then resumes again. This is
+		 * why we have to disable irqs again or there may be trouble.
+		 */
+		local_irq_disable();
+
 		pr_debug("PM: writing image.\n");
 
 		/*
Only in kernel/power/: disk.o
Only in kernel/power/: main.o
Only in kernel/power/: pm.o
Only in kernel/power/: poweroff.o
Only in kernel/power/: process.o
diff -up ../linux-2.6.8-14/kernel/power/swsusp.c kernel/power/swsusp.c
--- ../linux-2.6.8-14/kernel/power/swsusp.c	2004-09-23 02:22:51.000000000 +0200
+++ kernel/power/swsusp.c	2004-09-26 22:45:24.027966304 +0200
@@ -853,7 +853,10 @@ int swsusp_suspend(void)
 	local_irq_disable();
 	save_processor_state();
 	error = swsusp_arch_suspend();
-	/* Restore control flow magically appears here */
+	/* Restore control flow magically appears here during resume.
+	 * During suspend, this is not the end! We still have to write
+	 * the image to disk and power off.
+	 */
 	restore_processor_state();
 	restore_highmem();
 	local_irq_enable();
Only in kernel/power/: swsusp.c-orig
Only in kernel/power/: swsusp.o

Re: 2.6.9-rc2-mm3: swsusp horribly slow on AMD64

[Rafael J. Wysocki]

On Sunday 26 of September 2004 22:48, Stefan Seyfried wrote:
> Rafael J. Wysocki wrote:
> 
> >>Try to unload all modules etc, see if it goes away.
> > 
> > I guess it will, but I'll check.
> 
> please try attached patch first. The comments should explain it pretty
> well. It seems to have helped me: without it, sysrq-p during writing
> (even if not that slow) almost always was in pccardd, now it is idling
> in swapper task.
> Maybe i am totally wrong but you may give it a shot.

Does not help, sorry. :-(

> >>If not, fix sysrq  to work for you, and look at backtrace.
> > 
> > This would be more time-consuming. :-)
> 
> maybe you just press wrong keys? On my Dell D600, although SysRQ is in
> blue on PrtSc, no Fn-Key is needed but only ALT-PrtSc.

It is possible, but I have two x86-64 boxes, one of which is a regular PC with 
no Fn-Key whatsoever, and it doesn't work on both, apparently.

Greets,
RJW

-- 
- Would you tell me, please, which way I ought to go from here?
- That depends a good deal on where you want to get to.
		-- Lewis Carroll "Alice's Adventures in Wonderland"

Re: 2.6.9-rc2-mm3: swsusp horribly slow on AMD64

[Pavel Machek]

Hi!

> > I guess it will, but I'll check.
> 
> please try attached patch first. The comments should explain it pretty
> well. It seems to have helped me: without it, sysrq-p during writing
> (even if not that slow) almost always was in pccardd, now it is idling
> in swapper task.
> Maybe i am totally wrong but you may give it a shot.

I do not think it is right, interrupts may be needed for writing
image.
									Pavel
-- 
People were complaining that M$ turns users into beta-testers...
...jr ghea gurz vagb qrirybcref, naq gurl frrz gb yvxr vg gung jnl!

Re: 2.6.9-rc2-mm3: swsusp horribly slow on AMD64

[Pavel Machek]

Hi!

> I've just tried to suspend my box and I must admit I've given up after 30 
> minutes (sic!) of waiting when there were only 12% of pages written to disk.  
> Apparently, swsusp slows down to an unacceptable level after saying "PM: 
> Writing image to disk".
> 
> The box is an Athlon 64-based notebook.  The .config is available at:
> http://www.sisk.pl/kernel/040925/2.6.9-rc2-mm3.config
> and the output of dmesg is available at:
> http://www.sisk.pl/kernel/040925/2.6.9-rc2-mm3-dmesg.log

We have seen something similar after hdparm was used on specific
machines. Are you using hdparm?
							Pavel
-- 
People were complaining that M$ turns users into beta-testers...
...jr ghea gurz vagb qrirybcref, naq gurl frrz gb yvxr vg gung jnl!

Re: 2.6.9-rc2-mm3: swsusp horribly slow on AMD64

[Rafael J. Wysocki]

On Sunday 26 of September 2004 01:40, Pavel Machek wrote:
> Hi!
> 
> > I've just tried to suspend my box and I must admit I've given up after 30 
> > minutes (sic!) of waiting when there were only 12% of pages written to 
disk.  
> > Apparently, swsusp slows down to an unacceptable level after saying "PM: 
> > Writing image to disk".
> > 
> > The box is an Athlon 64-based notebook.  The .config is available at:
> > http://www.sisk.pl/kernel/040925/2.6.9-rc2-mm3.config
> > and the output of dmesg is available at:
> > http://www.sisk.pl/kernel/040925/2.6.9-rc2-mm3-dmesg.log
> 
> We have seen something similar after hdparm was used on specific
> machines. Are you using hdparm?

Not explicitly, but it's used by SuSE initscripts to set IDE DMA, AFAICS.  
However, the problem did not occur on 2.6.9-rc2-mm1 with the same 
initscripts.

Greets,
RJW

-- 
- Would you tell me, please, which way I ought to go from here?
- That depends a good deal on where you want to get to.
		-- Lewis Carroll "Alice's Adventures in Wonderland"

Re: 2.6.9-rc2-mm3: swsusp horribly slow on AMD64

[Pavel Machek]

Hi!

> > > I've just tried to suspend my box and I must admit I've given up after 30 
> > > minutes (sic!) of waiting when there were only 12% of pages written to 
> disk.  
> > > Apparently, swsusp slows down to an unacceptable level after saying "PM: 
> > > Writing image to disk".
> > > 
> > > The box is an Athlon 64-based notebook.  The .config is available at:
> > > http://www.sisk.pl/kernel/040925/2.6.9-rc2-mm3.config
> > > and the output of dmesg is available at:
> > > http://www.sisk.pl/kernel/040925/2.6.9-rc2-mm3-dmesg.log
> > 
> > We have seen something similar after hdparm was used on specific
> > machines. Are you using hdparm?
> 
> Not explicitly, but it's used by SuSE initscripts to set IDE DMA, AFAICS.  
> However, the problem did not occur on 2.6.9-rc2-mm1 with the same 
> initscripts.

Okay, so try what happens without the initscripts and try to locate
change that breaks it...
								Pavel
-- 
People were complaining that M$ turns users into beta-testers...
...jr ghea gurz vagb qrirybcref, naq gurl frrz gb yvxr vg gung jnl!

Re: 2.6.9-rc2-mm3: swsusp horribly slow on AMD64

[Rafael J. Wysocki]

On Sunday 26 of September 2004 12:09, Pavel Machek wrote:
> Hi!
> 
> > > > I've just tried to suspend my box and I must admit I've given up after 
30 
> > > > minutes (sic!) of waiting when there were only 12% of pages written to 
> > disk.  
> > > > Apparently, swsusp slows down to an unacceptable level after saying 
"PM: 
> > > > Writing image to disk".
> > > > 
> > > > The box is an Athlon 64-based notebook.  The .config is available at:
> > > > http://www.sisk.pl/kernel/040925/2.6.9-rc2-mm3.config
> > > > and the output of dmesg is available at:
> > > > http://www.sisk.pl/kernel/040925/2.6.9-rc2-mm3-dmesg.log
> > > 
> > > We have seen something similar after hdparm was used on specific
> > > machines. Are you using hdparm?
> > 
> > Not explicitly, but it's used by SuSE initscripts to set IDE DMA, AFAICS.  
> > However, the problem did not occur on 2.6.9-rc2-mm1 with the same 
> > initscripts.
> 
> Okay, so try what happens without the initscripts

I turned the stuff off but of course it didn't change anything. :-)

> and try to locate change that breaks it...

Well, I'm a bit confused:

--- linux-2.6.9-rc2-mm1/kernel/power/swsusp.c   2004-09-16 14:06:56.000000000 
+0200
+++ linux-2.6.9-rc2-mm3/kernel/power/swsusp.c   2004-09-24 11:35:18.000000000 
+0200
@@ -862,8 +862,8 @@
        error = swsusp_arch_suspend();
        /* Restore control flow magically appears here */
        restore_processor_state();
-       local_irq_enable();
        restore_highmem();
+       local_irq_enable();
        return error;
 }

What else should I look for?

Greets,
RJW

-- 
- Would you tell me, please, which way I ought to go from here?
- That depends a good deal on where you want to get to.
		-- Lewis Carroll "Alice's Adventures in Wonderland"

Re: 2.6.9-rc2-mm3: swsusp horribly slow on AMD64

[Pavel Machek]

Hi!

> > > Not explicitly, but it's used by SuSE initscripts to set IDE DMA, AFAICS.  
> > > However, the problem did not occur on 2.6.9-rc2-mm1 with the same 
> > > initscripts.
> > 
> > Okay, so try what happens without the initscripts
> 
> I turned the stuff off but of course it didn't change anything. :-)
> 
> > and try to locate change that breaks it...
> 
> Well, I'm a bit confused:

That's very simple bugfix. Some code outside swsusp is doing this.
Is it still slow with init=/bin/bash? If no, locate module that
causes slowdown. We've seen pcmcia support behaving strange.

				Pavel
-- 
64 bytes from 195.113.31.123: icmp_seq=28 ttl=51 time=448769.1 ms         

Re: 2.6.9-rc2-mm3: swsusp horribly slow on AMD64 (update)

[Rafael J. Wysocki]

[-- Attachment #1: Type: text/plain, Size: 6471 bytes --]

On Sunday 26 of September 2004 15:20, Pavel Machek wrote:
> Hi!
> 
> > > > Not explicitly, but it's used by SuSE initscripts to set IDE DMA, 
AFAICS.  
> > > > However, the problem did not occur on 2.6.9-rc2-mm1 with the same 
> > > > initscripts.
> > > 
> > > Okay, so try what happens without the initscripts
> > 
> > I turned the stuff off but of course it didn't change anything. :-)
> > 
> > > and try to locate change that breaks it...
> > 
> > Well, I'm a bit confused:
> 
> That's very simple bugfix. Some code outside swsusp is doing this.

You are right, but I don't think it's a module.  Read on. ;-)

> Is it still slow with init=/bin/bash? If no, locate module that
> causes slowdown. We've seen pcmcia support behaving strange.

I did some tests on 2.6.9-rc2-mm4, just to make sure that the problem hasn't 
been fixed "magically".  Apparently, it hasn't.

First, I rebooted the machine, unloaded all modules except for ipv6 (it seems 
to be always used) and tried to suspend it.  It successfully suspended and 
resumed.

Then, I loaded ohci_hcd and ehci_hcd (usbhid and evdev got loaded 
automatically) and tried to suspend it again.  It successfully suspended and 
resumed.

Next, I loaded sk98lin and restarted networking (/etc/init.d/network restart), 
so af_packet got loaded automatically.  I tried to suspend the box and, 
again, everything went OK.

Next, after the box had woken up, I loaded parport and parport_pc and 
successfully suspended the box and resumed.

Next, I loaded lp and usbserial, and the box successfully suspended with these 
modules, but I got a familiar double fault on resume (trace attached).  So, I 
tried to recreate the conditions: I rebooted the box, unloaded all modules, 
loaded only the modules that had been present previosly (ie usbserial lp 
ohci_hcd parport_pc parport af_packet sk98lin ehci_hcd evdev usbhid ipv6) and 
tried to suspend the box.  It seemed to go just fine:

Stopping tasks: ============================|
Freeing memory... done (19488 pages freed)
PM: Attempting to suspend to disk.
PM: snapshotting memory.
swsusp: critical section:
..<7>[nosave pfn 0x586].....................................swsusp: Need to 
copy 10721 pages
suspend: (pages needed: 10721 + 512 free: 120158)
..<7>[nosave pfn 0x586]......................................swsusp: critical 
section/: done (10849 pages copied)
PM: writing image.
PCI: Setting latency timer of device 0000:00:02.0 to 64
PCI: Setting latency timer of device 0000:00:02.1 to 64
PCI: Setting latency timer of device 0000:00:02.2 to 64
ACPI: PCI interrupt 0000:00:06.0[A] -> GSI 5 (level, low) -> IRQ 5
PCI: Setting latency timer of device 0000:00:06.0 to 64
ACPI: PCI interrupt 0000:02:00.0[A] -> GSI 11 (level, low) -> IRQ 11
ACPI: PCI interrupt 0000:02:01.0[A] -> GSI 9 (level, low) -> IRQ 9
ACPI: PCI interrupt 0000:02:01.1[B] -> GSI 11 (level, low) -> IRQ 11
ACPI: PCI interrupt 0000:02:01.2[C] -> GSI 11 (level, low) -> IRQ 11
 swsusp: Version: 132617
 swsusp: Num Pages: 130880
 swsusp: UTS Sys: Linux
 swsusp: UTS Node: albercik
 swsusp: UTS Release: 2.6.9-rc2-mm4
 swsusp: UTS Version: #14 Mon Sep 27 19:59:28 CEST 2004
 swsusp: UTS Machine: x86_64
 swsusp: UTS Domain:
 swsusp: CPUs: 1
 swsusp: Image: 10849 Pages
 swsusp: Pagedir: 0 Pages
Writing data to swap (10849 pages)...  84%

but the system slowed down here, after writing 84% pages to the swap, so I 
pressed Alt+sysrq+p:

<6>SysRq : Show Regs

Modules linked in: usbserial lp af_packet sk98lin evdev parport_pc parport 
usbhid ehci_hcd ohci_hcd ipv6
Pid: 1035, comm: kjournald Tainted: G   M  2.6.9-rc2-mm4
RIP: 0010:[<ffffffff80117b1b>] <ffffffff80117b1b>{sched_clock+11}
RSP: 0018:000001001d7a3d90  EFLAGS: 00000206
RAX: 00000085835f7fdd RBX: 000001001bd854d8 RCX: 00000000fffee984
RDX: 0000008500000000 RSI: 0000000000000000 RDI: 000001001fda8130
RBP: 000001001bd854d8 R08: 000001001d7a2000 R09: 000001001c9ca9e0
R10: 0000000000000000 R11: 0000000000000000 R12: 000001001bd854d8
R13: 000001001bd854d8 R14: 000001001bd854d8 R15: 000001001bd854d8
FS:  0000002a9588d700(0000) GS:ffffffff805582c0(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 000000008005003b
CR2: 0000000000415cbf CR3: 0000000000101000 CR4: 00000000000006e0

Call Trace:<ffffffff803a695c>{schedule+204} 
<ffffffff801634f7>{refrigerator+743}
       <ffffffff80236d12>{kjournald+1042} 
<ffffffff8015be70>{autoremove_wake_function+0}
       <ffffffff8015be70>{autoremove_wake_function+0} 
<ffffffff802370d0>{commit_timeout+0}
       <ffffffff80111843>{child_rip+8} <ffffffff80236900>{kjournald+0}
       <ffffffff8011183b>{child_rip+0}

Now, can you tell me, please, what the chances of hitting schedule() this way 
should be?  Not great, I think.  Still, I pressed Alt+sysrq+p for several 
times after I'd got the above trace and it always hit schedule() (all the 
traces were very similar to this one).

I've investigated this a bit more and it turns out that when I press 
Alt+sysrq+p after such a slowdown, I almost always hit schedule().  Slowdowns 
usually happen sooner or later after swsusp has been started, and the more 
modules are in memory at that time, the sooner the system slows down.  When 
all modules are present, it slows down right after printing "PM: writing 
image.".

My theory is that something really bad is going on in the scheduler after 
swsusp has been started and the "slowdowns" occur because the processor 
spends _a_ _lot_ of time in schedule().

I have verified that the problem was introduced between 2.6.9-rc2-mm1 and 
2.6.9-rc2-mm2, but I haven't identified the change that might have caused it, 
yet.  I've verified that it's not caused by any of the following patches:

cleanup-move-call-to-update_process_times.patch
cleanup-timeh-timesh-timexh-and-jiffiesh.patch

I can also say with a great deal of certainty that it's not caused by any 
changes to PCI and/or ACPI.  Moreover, I replaced the scheduler in 
2.6.9-rc2-mm2 with the Con's staircase scheduler and it made the symptoms 
even worse.  That is, with the staircase scheduler, the system always "slows 
down" before it writes all pages to the swap and if all modules are present 
when the system is suspended, the "slowdown" is much more "visible".  Of 
course, I can do some more tests/measurements if necessary.

Greets,
RJW

-- 
- Would you tell me, please, which way I ought to go from here?
- That depends a good deal on where you want to get to.
		-- Lewis Carroll "Alice's Adventures in Wonderland"

[-- Attachment #2: swsusp-double_fault.log --]
[-- Type: text/x-log, Size: 3784 bytes --]

Relocating pagedir not necessary
Reading image data (9659 pages): 100% 9659 done.
Stopping tasks: ===|
Freeing memory... done (0 pages freed)
PM: Restoring saved image.
<0>double fault: 0000 [1]
CPU 0
Modules linked in: usbserial lp ohci_hcd parport_pc parport af_packet sk98lin ehci_hcd evdev usbhid ipv6
Pid: 17009, comm: hibernate.sh Tainted: G   M  2.6.9-rc2-mm4
RIP: 0010:[<ffffffff8012518d>] <ffffffff8012518d>{do_page_fault+1485}
RSP: 0000:000001001fe00008  EFLAGS: 00010002
RAX: 000000001fce8740 RBX: 0000000000000001 RCX: 000ffffffffff000
RDX: 000000001fce8000 RSI: 0000010000000000 RDI: 000001001fe000e8
RBP: 000001001fce8740 R08: 0000000000000000 R09: 000001001fe27e54
R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000000
R13: 0000000000000000 R14: 000001001fe000e8 R15: 000001001b09e200
FS:  0000000000000000(0000) GS:ffffffff805582c0(0000) knlGS:0000000000000000
CS:  0010 DS: 0018 ES: 0018 CR0: 0000000080050033
CR2: 000001001fdffff8 CR3: 0000000000101000 CR4: 00000000000006e0
Process hibernate.sh (pid: 17009, threadinfo 000001001c6d8000, task 000001001ad16530)
Stack: 000001001fe01000 0000000000000060 000001001ad16530 0000ffff0000001a
       fffefffefffefffe fffefffe00030001 fffefffefffefffe fffefffefffefffe
       fffefffefffefffe fffefffefffefffe
Call Trace:<ffffffff8011168d>{error_exit+0} <ffffffff8012518d>{do_page_fault+1485}
       <ffffffff80282d47>{acpi_os_allocate+12} <ffffffff8011168d>{error_exit+0}
       <ffffffff8012518d>{do_page_fault+1485} <ffffffff8011168d>{error_exit+0}
       <ffffffff8012518d>{do_page_fault+1485} <ffffffff80282d47>{acpi_os_allocate+12}
       <ffffffff8011168d>{error_exit+0} <ffffffff8012518d>{do_page_fault+1485}
       <ffffffff80282d47>{acpi_os_allocate+12} <ffffffff80282d47>{acpi_os_allocate+12}
       <ffffffff8011168d>{error_exit+0} <ffffffff8012518d>{do_page_fault+1485}
       <ffffffff80282d47>{acpi_os_allocate+12} <ffffffff8011168d>{error_exit+0}
       <ffffffff8012518d>{do_page_fault+1485} <ffffffff80282d47>{acpi_os_allocate+12}
       <ffffffff8011168d>{error_exit+0} <ffffffff8012518d>{do_page_fault+1485}
       <ffffffff8011168d>{error_exit+0} <ffffffff8012518d>{do_page_fault+1485}
       <ffffffff80282d47>{acpi_os_allocate+12} <ffffffff8011168d>{error_exit+0}
       <ffffffff8012518d>{do_page_fault+1485} <ffffffff80282d47>{acpi_os_allocate+12}
       <ffffffff8011168d>{error_exit+0} <ffffffff8012518d>{do_page_fault+1485}
       <ffffffff80282d47>{acpi_os_allocate+12} <ffffffff8011168d>{error_exit+0}
       <ffffffff8012518d>{do_page_fault+1485} <ffffffff80282d47>{acpi_os_allocate+12}
       <ffffffff8011168d>{error_exit+0} <ffffffff8012518d>{do_page_fault+1485}
       <ffffffff80282d47>{acpi_os_allocate+12} <ffffffff8011168d>{error_exit+0}
       <ffffffff8012518d>{do_page_fault+1485} <ffffffff8011168d>{error_exit+0}
       <ffffffff8012518d>{do_page_fault+1485} <ffffffff80282d47>{acpi_os_allocate+12}
       <ffffffff8011168d>{error_exit+0} <ffffffff8012518d>{do_page_fault+1485}
       <ffffffff80282d47>{acpi_os_allocate+12} <ffffffff80282d47>{acpi_os_allocate+12}
       <ffffffff8011168d>{error_exit+0} <ffffffff8012518d>{do_page_fault+1485}
       <ffffffff80282d47>{acpi_os_allocate+12} <ffffffff8011168d>{error_exit+0}
       <ffffffff8012518d>{do_page_fault+1485} <ffffffff80282d47>{acpi_os_allocate+12}
       <ffffffff8011168d>{error_exit+0} <ffffffff8012518d>{do_page_fault+1485}
       <ffffffff8011168d>{error_exit+0} <ffffffff8012518d>{do_page_fault+1485}
       <ffffffff80282d47>{acpi_os_allocate+12} <ffffffff8011168d>{error_exit+0}
       <ffffffff8012518d>{do_page_fault+1485} <ffffffff80282d47>{acpi_os_allocate+12}


Code: f6 04 06 81 0f 84 52 fc ff ff 48 8b 05 e2 f9 3a 00 48 89 c2
RIP <ffffffff8012518d>{do_page_fault+1485} RSP <000001001fe00008>

Re: 2.6.9-rc2-mm3: swsusp horribly slow on AMD64 (update)

[Narayan Desai]

[-- Attachment #1: Type: text/plain, Size: 333 bytes --]

As another data point, I am having a similar performance problem with
swsusp on a thinkpad t41p running
2.6.9rc2-mm4. CONFIG_NOHIGHMEM=Y. The strange thing is that there
isn't any performance problem with 2.6.9-rc1-mm4. There are no
substantive changes between the kernel configs. A .config is attached,
in case it will help.
 -nld


[-- Attachment #2: kernel config --]
[-- Type: text/plain, Size: 32095 bytes --]

#
# Automatically generated make config: don't edit
# Linux kernel version: 2.6.9-rc1-mm4
# Thu Sep  9 09:54:58 2004
#
CONFIG_X86=y
CONFIG_MMU=y
CONFIG_UID16=y
CONFIG_GENERIC_ISA_DMA=y

#
# Code maturity level options
#
CONFIG_EXPERIMENTAL=y
CONFIG_CLEAN_COMPILE=y
CONFIG_BROKEN_ON_SMP=y

#
# General setup
#
CONFIG_SWAP=y
CONFIG_SYSVIPC=y
CONFIG_POSIX_MQUEUE=y
CONFIG_BSD_PROCESS_ACCT=y
# CONFIG_BSD_PROCESS_ACCT_V3 is not set
CONFIG_SYSCTL=y
# CONFIG_AUDIT is not set
CONFIG_KERNEL_EVENTS=y
CONFIG_LOG_BUF_SHIFT=14
CONFIG_HOTPLUG=y
CONFIG_IKCONFIG=y
CONFIG_IKCONFIG_PROC=y
# CONFIG_EMBEDDED is not set
CONFIG_KALLSYMS=y
# CONFIG_KALLSYMS_ALL is not set
# CONFIG_KALLSYMS_EXTRA_PASS is not set
CONFIG_FUTEX=y
CONFIG_EPOLL=y
CONFIG_IOSCHED_NOOP=y
CONFIG_IOSCHED_AS=y
CONFIG_IOSCHED_DEADLINE=y
CONFIG_IOSCHED_CFQ=y
# CONFIG_CC_OPTIMIZE_FOR_SIZE is not set
CONFIG_LOCALVERSION=""
CONFIG_SHMEM=y
# CONFIG_TINY_SHMEM is not set

#
# Loadable module support
#
CONFIG_MODULES=y
CONFIG_MODULE_UNLOAD=y
CONFIG_MODULE_FORCE_UNLOAD=y
CONFIG_OBSOLETE_MODPARM=y
# CONFIG_MODVERSIONS is not set
CONFIG_KMOD=y

#
# Processor type and features
#
CONFIG_X86_PC=y
# CONFIG_X86_ELAN is not set
# CONFIG_X86_VOYAGER is not set
# CONFIG_X86_NUMAQ is not set
# CONFIG_X86_SUMMIT is not set
# CONFIG_X86_BIGSMP is not set
# CONFIG_X86_VISWS is not set
# CONFIG_X86_GENERICARCH is not set
# CONFIG_X86_ES7000 is not set
# CONFIG_M386 is not set
# CONFIG_M486 is not set
# CONFIG_M586 is not set
# CONFIG_M586TSC is not set
# CONFIG_M586MMX is not set
# CONFIG_M686 is not set
# CONFIG_MPENTIUMII is not set
# CONFIG_MPENTIUMIII is not set
CONFIG_MPENTIUMM=y
# CONFIG_MPENTIUM4 is not set
# CONFIG_MK6 is not set
# CONFIG_MK7 is not set
# CONFIG_MK8 is not set
# CONFIG_MCRUSOE is not set
# CONFIG_MWINCHIPC6 is not set
# CONFIG_MWINCHIP2 is not set
# CONFIG_MWINCHIP3D is not set
# CONFIG_MCYRIXIII is not set
# CONFIG_MVIAC3_2 is not set
# CONFIG_X86_GENERIC is not set
CONFIG_X86_CMPXCHG=y
CONFIG_X86_XADD=y
CONFIG_X86_L1_CACHE_SHIFT=6
CONFIG_RWSEM_XCHGADD_ALGORITHM=y
CONFIG_X86_WP_WORKS_OK=y
CONFIG_X86_INVLPG=y
CONFIG_X86_BSWAP=y
CONFIG_X86_POPAD_OK=y
CONFIG_X86_GOOD_APIC=y
CONFIG_X86_INTEL_USERCOPY=y
CONFIG_X86_USE_PPRO_CHECKSUM=y
CONFIG_HPET_TIMER=y
CONFIG_HPET_EMULATE_RTC=y
# CONFIG_SMP is not set
# CONFIG_PREEMPT is not set
# CONFIG_X86_UP_APIC is not set
CONFIG_X86_TSC=y
CONFIG_X86_MCE=y
# CONFIG_X86_MCE_NONFATAL is not set
# CONFIG_TOSHIBA is not set
# CONFIG_I8K is not set
CONFIG_MICROCODE=m
CONFIG_X86_MSR=m
CONFIG_X86_CPUID=m

#
# Firmware Drivers
#
# CONFIG_EDD is not set
CONFIG_NOHIGHMEM=y
# CONFIG_HIGHMEM4G is not set
# CONFIG_HIGHMEM64G is not set
# CONFIG_MATH_EMULATION is not set
CONFIG_MTRR=y
# CONFIG_EFI is not set
# CONFIG_REGPARM is not set

#
# Performance-monitoring counters support
#
# CONFIG_PERFCTR is not set
# CONFIG_KEXEC is not set

#
# Power management options (ACPI, APM)
#
CONFIG_PM=y
CONFIG_PM_DEBUG=y
CONFIG_SOFTWARE_SUSPEND=y
CONFIG_PM_STD_PARTITION="/dev/hda5"

#
# ACPI (Advanced Configuration and Power Interface) Support
#
CONFIG_ACPI=y
CONFIG_ACPI_BOOT=y
CONFIG_ACPI_INTERPRETER=y
CONFIG_ACPI_SLEEP=y
CONFIG_ACPI_SLEEP_PROC_FS=y
CONFIG_ACPI_AC=m
CONFIG_ACPI_BATTERY=m
CONFIG_ACPI_BUTTON=m
CONFIG_ACPI_FAN=m
CONFIG_ACPI_PROCESSOR=m
CONFIG_ACPI_THERMAL=m
# CONFIG_ACPI_ASUS is not set
# CONFIG_ACPI_TOSHIBA is not set
CONFIG_ACPI_BLACKLIST_YEAR=0
# CONFIG_ACPI_DEBUG is not set
CONFIG_ACPI_BUS=y
CONFIG_ACPI_EC=y
CONFIG_ACPI_POWER=y
CONFIG_ACPI_PCI=y
CONFIG_ACPI_SYSTEM=y
# CONFIG_X86_PM_TIMER is not set

#
# APM (Advanced Power Management) BIOS Support
#
CONFIG_APM=y
# CONFIG_APM_IGNORE_USER_SUSPEND is not set
# CONFIG_APM_DO_ENABLE is not set
CONFIG_APM_CPU_IDLE=y
# CONFIG_APM_DISPLAY_BLANK is not set
# CONFIG_APM_RTC_IS_GMT is not set
CONFIG_APM_ALLOW_INTS=y
# CONFIG_APM_REAL_MODE_POWER_OFF is not set

#
# CPU Frequency scaling
#
CONFIG_CPU_FREQ=y
# CONFIG_CPU_FREQ_PROC_INTF is not set
# CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE is not set
CONFIG_CPU_FREQ_DEFAULT_GOV_USERSPACE=y
CONFIG_CPU_FREQ_GOV_PERFORMANCE=y
CONFIG_CPU_FREQ_GOV_POWERSAVE=y
CONFIG_CPU_FREQ_GOV_USERSPACE=y
CONFIG_CPU_FREQ_GOV_ONDEMAND=m
# CONFIG_CPU_FREQ_24_API is not set
CONFIG_CPU_FREQ_TABLE=y

#
# CPUFreq processor drivers
#
# CONFIG_X86_ACPI_CPUFREQ is not set
# CONFIG_X86_POWERNOW_K6 is not set
# CONFIG_X86_POWERNOW_K7 is not set
# CONFIG_X86_POWERNOW_K8 is not set
# CONFIG_X86_GX_SUSPMOD is not set
CONFIG_X86_SPEEDSTEP_CENTRINO=y
CONFIG_X86_SPEEDSTEP_CENTRINO_TABLE=y
# CONFIG_X86_SPEEDSTEP_ICH is not set
# CONFIG_X86_SPEEDSTEP_SMI is not set
# CONFIG_X86_P4_CLOCKMOD is not set
# CONFIG_X86_CPUFREQ_NFORCE2 is not set
# CONFIG_X86_LONGRUN is not set
# CONFIG_X86_LONGHAUL is not set

#
# Bus options (PCI, PCMCIA, EISA, MCA, ISA)
#
CONFIG_PCI=y
# CONFIG_PCI_GOBIOS is not set
# CONFIG_PCI_GOMMCONFIG is not set
# CONFIG_PCI_GODIRECT is not set
CONFIG_PCI_GOANY=y
CONFIG_PCI_BIOS=y
CONFIG_PCI_DIRECT=y
CONFIG_PCI_MMCONFIG=y
# CONFIG_PCI_LEGACY_PROC is not set
CONFIG_PCI_NAMES=y
# CONFIG_ISA is not set
# CONFIG_MCA is not set
# CONFIG_SCx200 is not set

#
# PCMCIA/CardBus support
#
# CONFIG_PCMCIA is not set

#
# PCI Hotplug Support
#
# CONFIG_HOTPLUG_PCI is not set

#
# Executable file formats
#
CONFIG_BINFMT_ELF=y
CONFIG_BINFMT_AOUT=m
CONFIG_BINFMT_MISC=m

#
# Device Drivers
#

#
# Generic Driver Options
#
CONFIG_STANDALONE=y
CONFIG_PREVENT_FIRMWARE_BUILD=y
CONFIG_FW_LOADER=m
# CONFIG_DEBUG_DRIVER is not set

#
# Memory Technology Devices (MTD)
#
# CONFIG_MTD is not set

#
# Parallel port support
#
CONFIG_PARPORT=m
CONFIG_PARPORT_PC=m
CONFIG_PARPORT_PC_CML1=m
# CONFIG_PARPORT_SERIAL is not set
CONFIG_PARPORT_PC_FIFO=y
CONFIG_PARPORT_PC_SUPERIO=y
# CONFIG_PARPORT_OTHER is not set
CONFIG_PARPORT_1284=y

#
# Plug and Play support
#

#
# Block devices
#
CONFIG_BLK_DEV_FD=y
# CONFIG_PARIDE is not set
# CONFIG_BLK_CPQ_DA is not set
# CONFIG_BLK_CPQ_CISS_DA is not set
# CONFIG_BLK_DEV_DAC960 is not set
# CONFIG_BLK_DEV_UMEM is not set
CONFIG_BLK_DEV_LOOP=y
CONFIG_BLK_DEV_CRYPTOLOOP=m
CONFIG_BLK_DEV_NBD=m
# CONFIG_BLK_DEV_SX8 is not set
# CONFIG_BLK_DEV_UB is not set
CONFIG_BLK_DEV_RAM=y
CONFIG_BLK_DEV_RAM_SIZE=4096
CONFIG_BLK_DEV_INITRD=y
# CONFIG_LBD is not set
# CONFIG_CDROM_PKTCDVD is not set

#
# ATA/ATAPI/MFM/RLL support
#
CONFIG_IDE=y
CONFIG_BLK_DEV_IDE=y

#
# Please see Documentation/ide.txt for help/info on IDE drives
#
# CONFIG_BLK_DEV_IDE_SATA is not set
# CONFIG_BLK_DEV_HD_IDE is not set
CONFIG_BLK_DEV_IDEDISK=y
# CONFIG_IDEDISK_MULTI_MODE is not set
CONFIG_BLK_DEV_IDECD=m
CONFIG_BLK_DEV_IDETAPE=m
CONFIG_BLK_DEV_IDEFLOPPY=m
CONFIG_BLK_DEV_IDESCSI=m
# CONFIG_IDE_TASK_IOCTL is not set
# CONFIG_IDE_TASKFILE_IO is not set

#
# IDE chipset support/bugfixes
#
CONFIG_IDE_GENERIC=y
# CONFIG_BLK_DEV_CMD640 is not set
CONFIG_BLK_DEV_IDEPCI=y
CONFIG_IDEPCI_SHARE_IRQ=y
# CONFIG_BLK_DEV_OFFBOARD is not set
# CONFIG_BLK_DEV_GENERIC is not set
# CONFIG_BLK_DEV_OPTI621 is not set
# CONFIG_BLK_DEV_RZ1000 is not set
CONFIG_BLK_DEV_IDEDMA_PCI=y
# CONFIG_BLK_DEV_IDEDMA_FORCED is not set
CONFIG_IDEDMA_PCI_AUTO=y
# CONFIG_IDEDMA_ONLYDISK is not set
CONFIG_BLK_DEV_ADMA=y
# CONFIG_BLK_DEV_AEC62XX is not set
# CONFIG_BLK_DEV_ALI15X3 is not set
# CONFIG_BLK_DEV_AMD74XX is not set
# CONFIG_BLK_DEV_ATIIXP is not set
# CONFIG_BLK_DEV_CMD64X is not set
# CONFIG_BLK_DEV_TRIFLEX is not set
# CONFIG_BLK_DEV_CY82C693 is not set
# CONFIG_BLK_DEV_CS5520 is not set
# CONFIG_BLK_DEV_CS5530 is not set
# CONFIG_BLK_DEV_HPT34X is not set
# CONFIG_BLK_DEV_HPT366 is not set
# CONFIG_BLK_DEV_SC1200 is not set
CONFIG_BLK_DEV_PIIX=y
# CONFIG_BLK_DEV_IT8212 is not set
# CONFIG_BLK_DEV_NS87415 is not set
# CONFIG_BLK_DEV_PDC202XX_OLD is not set
# CONFIG_BLK_DEV_PDC202XX_NEW is not set
# CONFIG_BLK_DEV_SVWKS is not set
# CONFIG_BLK_DEV_SIIMAGE is not set
# CONFIG_BLK_DEV_SIS5513 is not set
# CONFIG_BLK_DEV_SLC90E66 is not set
# CONFIG_BLK_DEV_TRM290 is not set
# CONFIG_BLK_DEV_VIA82CXXX is not set
# CONFIG_IDE_ARM is not set
CONFIG_BLK_DEV_IDEDMA=y
# CONFIG_IDEDMA_IVB is not set
CONFIG_IDEDMA_AUTO=y
# CONFIG_BLK_DEV_HD is not set

#
# SCSI device support
#
CONFIG_SCSI=m
CONFIG_SCSI_PROC_FS=y

#
# SCSI support type (disk, tape, CD-ROM)
#
CONFIG_BLK_DEV_SD=m
# CONFIG_CHR_DEV_ST is not set
# CONFIG_CHR_DEV_OSST is not set
CONFIG_BLK_DEV_SR=m
# CONFIG_BLK_DEV_SR_VENDOR is not set
CONFIG_CHR_DEV_SG=m

#
# Some SCSI devices (e.g. CD jukebox) support multiple LUNs
#
CONFIG_SCSI_MULTI_LUN=y
# CONFIG_SCSI_CONSTANTS is not set
# CONFIG_SCSI_LOGGING is not set

#
# SCSI Transport Attributes
#
CONFIG_SCSI_SPI_ATTRS=m
# CONFIG_SCSI_FC_ATTRS is not set

#
# SCSI low-level drivers
#
# CONFIG_BLK_DEV_3W_XXXX_RAID is not set
# CONFIG_SCSI_3W_9XXX is not set
# CONFIG_SCSI_ACARD is not set
# CONFIG_SCSI_AACRAID is not set
# CONFIG_SCSI_AIC7XXX is not set
# CONFIG_SCSI_AIC7XXX_OLD is not set
# CONFIG_SCSI_AIC79XX is not set
# CONFIG_SCSI_DPT_I2O is not set
# CONFIG_MEGARAID_NEWGEN is not set
# CONFIG_MEGARAID_LEGACY is not set
# CONFIG_SCSI_SATA is not set
# CONFIG_SCSI_BUSLOGIC is not set
# CONFIG_SCSI_DMX3191D is not set
# CONFIG_SCSI_EATA is not set
# CONFIG_SCSI_EATA_PIO is not set
# CONFIG_SCSI_FUTURE_DOMAIN is not set
# CONFIG_SCSI_GDTH is not set
# CONFIG_SCSI_IPS is not set
# CONFIG_SCSI_INIA100 is not set
# CONFIG_SCSI_PPA is not set
# CONFIG_SCSI_IMM is not set
# CONFIG_SCSI_SYM53C8XX_2 is not set
# CONFIG_SCSI_IPR is not set
# CONFIG_SCSI_QLOGIC_ISP is not set
# CONFIG_SCSI_QLOGIC_FC is not set
# CONFIG_SCSI_QLOGIC_1280 is not set
CONFIG_SCSI_QLA2XXX=m
# CONFIG_SCSI_QLA21XX is not set
# CONFIG_SCSI_QLA22XX is not set
# CONFIG_SCSI_QLA2300 is not set
# CONFIG_SCSI_QLA2322 is not set
# CONFIG_SCSI_QLA6312 is not set
# CONFIG_SCSI_QLA6322 is not set
# CONFIG_SCSI_DC395x is not set
# CONFIG_SCSI_DC390T is not set
# CONFIG_SCSI_NSP32 is not set
# CONFIG_SCSI_DEBUG is not set

#
# Multi-device support (RAID and LVM)
#
CONFIG_MD=y
CONFIG_BLK_DEV_MD=m
CONFIG_MD_LINEAR=m
CONFIG_MD_RAID0=m
CONFIG_MD_RAID1=m
# CONFIG_MD_RAID10 is not set
CONFIG_MD_RAID5=m
# CONFIG_MD_RAID6 is not set
CONFIG_MD_MULTIPATH=m
# CONFIG_BLK_DEV_DM is not set

#
# Fusion MPT device support
#
# CONFIG_FUSION is not set

#
# IEEE 1394 (FireWire) support
#
# CONFIG_IEEE1394 is not set

#
# I2O device support
#
CONFIG_I2O=m
# CONFIG_I2O_CONFIG is not set
CONFIG_I2O_BLOCK=m
CONFIG_I2O_SCSI=m
CONFIG_I2O_PROC=m

#
# Networking support
#
CONFIG_NET=y

#
# Networking options
#
CONFIG_PACKET=y
# CONFIG_PACKET_MMAP is not set
CONFIG_NETLINK_DEV=m
CONFIG_UNIX=y
# CONFIG_NET_KEY is not set
CONFIG_INET=y
CONFIG_IP_MULTICAST=y
# CONFIG_IP_ADVANCED_ROUTER is not set
# CONFIG_IP_PNP is not set
CONFIG_NET_IPIP=m
CONFIG_NET_IPGRE=m
# CONFIG_NET_IPGRE_BROADCAST is not set
# CONFIG_IP_MROUTE is not set
# CONFIG_ARPD is not set
CONFIG_SYN_COOKIES=y
# CONFIG_INET_AH is not set
# CONFIG_INET_ESP is not set
# CONFIG_INET_IPCOMP is not set
CONFIG_INET_TUNNEL=m

#
# IP: Virtual Server Configuration
#
# CONFIG_IP_VS is not set
CONFIG_IPV6=m
CONFIG_IPV6_PRIVACY=y
CONFIG_INET6_AH=m
CONFIG_INET6_ESP=m
CONFIG_INET6_IPCOMP=m
CONFIG_INET6_TUNNEL=m
CONFIG_IPV6_TUNNEL=m
CONFIG_NETFILTER=y
# CONFIG_NETFILTER_DEBUG is not set

#
# IP: Netfilter Configuration
#
CONFIG_IP_NF_CONNTRACK=m
# CONFIG_IP_NF_CT_ACCT is not set
CONFIG_IP_NF_CT_PROTO_SCTP=m
CONFIG_IP_NF_FTP=m
CONFIG_IP_NF_IRC=m
CONFIG_IP_NF_TFTP=m
CONFIG_IP_NF_AMANDA=m
CONFIG_IP_NF_QUEUE=m
CONFIG_IP_NF_IPTABLES=m
CONFIG_IP_NF_MATCH_LIMIT=m
CONFIG_IP_NF_MATCH_IPRANGE=m
CONFIG_IP_NF_MATCH_MAC=m
CONFIG_IP_NF_MATCH_PKTTYPE=m
CONFIG_IP_NF_MATCH_MARK=m
CONFIG_IP_NF_MATCH_MULTIPORT=m
CONFIG_IP_NF_MATCH_TOS=m
# CONFIG_IP_NF_MATCH_RECENT is not set
CONFIG_IP_NF_MATCH_ECN=m
CONFIG_IP_NF_MATCH_DSCP=m
# CONFIG_IP_NF_MATCH_AH_ESP is not set
CONFIG_IP_NF_MATCH_LENGTH=m
CONFIG_IP_NF_MATCH_TTL=m
CONFIG_IP_NF_MATCH_TCPMSS=m
CONFIG_IP_NF_MATCH_HELPER=m
CONFIG_IP_NF_MATCH_STATE=m
CONFIG_IP_NF_MATCH_CONNTRACK=m
CONFIG_IP_NF_MATCH_OWNER=m
# CONFIG_IP_NF_MATCH_ADDRTYPE is not set
# CONFIG_IP_NF_MATCH_REALM is not set
# CONFIG_IP_NF_MATCH_SCTP is not set
CONFIG_IP_NF_FILTER=m
CONFIG_IP_NF_TARGET_REJECT=m
CONFIG_IP_NF_TARGET_LOG=m
# CONFIG_IP_NF_TARGET_ULOG is not set
CONFIG_IP_NF_TARGET_TCPMSS=m
CONFIG_IP_NF_NAT=m
CONFIG_IP_NF_NAT_NEEDED=y
CONFIG_IP_NF_TARGET_MASQUERADE=m
CONFIG_IP_NF_TARGET_REDIRECT=m
# CONFIG_IP_NF_TARGET_NETMAP is not set
# CONFIG_IP_NF_TARGET_SAME is not set
# CONFIG_IP_NF_NAT_LOCAL is not set
CONFIG_IP_NF_NAT_SNMP_BASIC=m
CONFIG_IP_NF_NAT_IRC=m
CONFIG_IP_NF_NAT_FTP=m
CONFIG_IP_NF_NAT_TFTP=m
CONFIG_IP_NF_NAT_AMANDA=m
CONFIG_IP_NF_MANGLE=m
CONFIG_IP_NF_TARGET_TOS=m
CONFIG_IP_NF_TARGET_ECN=m
CONFIG_IP_NF_TARGET_DSCP=m
CONFIG_IP_NF_TARGET_MARK=m
# CONFIG_IP_NF_TARGET_CLASSIFY is not set
# CONFIG_IP_NF_RAW is not set
CONFIG_IP_NF_ARPTABLES=m
CONFIG_IP_NF_ARPFILTER=m
# CONFIG_IP_NF_ARP_MANGLE is not set
CONFIG_IP_NF_COMPAT_IPCHAINS=m
CONFIG_IP_NF_COMPAT_IPFWADM=m

#
# IPv6: Netfilter Configuration
#
# CONFIG_IP6_NF_QUEUE is not set
# CONFIG_IP6_NF_IPTABLES is not set
CONFIG_XFRM=y
CONFIG_XFRM_USER=m

#
# SCTP Configuration (EXPERIMENTAL)
#
# CONFIG_IP_SCTP is not set
# CONFIG_ATM is not set
# CONFIG_BRIDGE is not set
# CONFIG_VLAN_8021Q is not set
# CONFIG_DECNET is not set
# CONFIG_LLC2 is not set
# CONFIG_IPX is not set
# CONFIG_ATALK is not set
# CONFIG_X25 is not set
# CONFIG_LAPB is not set
# CONFIG_NET_DIVERT is not set
# CONFIG_ECONET is not set
# CONFIG_WAN_ROUTER is not set
# CONFIG_NET_HW_FLOWCONTROL is not set

#
# QoS and/or fair queueing
#
# CONFIG_NET_SCHED is not set
# CONFIG_NET_CLS_ROUTE is not set

#
# Network testing
#
CONFIG_NET_PKTGEN=m
# CONFIG_KGDBOE is not set
# CONFIG_NETPOLL is not set
# CONFIG_NETPOLL_RX is not set
# CONFIG_NETPOLL_TRAP is not set
# CONFIG_NET_POLL_CONTROLLER is not set
# CONFIG_HAMRADIO is not set
# CONFIG_IRDA is not set
CONFIG_BT=m
CONFIG_BT_L2CAP=m
CONFIG_BT_SCO=m
CONFIG_BT_RFCOMM=m
CONFIG_BT_RFCOMM_TTY=y
CONFIG_BT_BNEP=m
CONFIG_BT_BNEP_MC_FILTER=y
CONFIG_BT_BNEP_PROTO_FILTER=y
# CONFIG_BT_HIDP is not set

#
# Bluetooth device drivers
#
CONFIG_BT_HCIUSB=m
CONFIG_BT_HCIUSB_SCO=y
CONFIG_BT_HCIUART=m
CONFIG_BT_HCIUART_H4=y
CONFIG_BT_HCIUART_BCSP=y
CONFIG_BT_HCIUART_BCSP_TXCRC=y
CONFIG_BT_HCIBCM203X=m
CONFIG_BT_HCIBFUSB=m
CONFIG_BT_HCIVHCI=m
CONFIG_NETDEVICES=y
CONFIG_DUMMY=m
CONFIG_BONDING=m
CONFIG_EQUALIZER=m
CONFIG_TUN=m
# CONFIG_ETHERTAP is not set

#
# ARCnet devices
#
# CONFIG_ARCNET is not set

#
# Ethernet (10 or 100Mbit)
#
CONFIG_NET_ETHERNET=y
CONFIG_MII=m
CONFIG_HAPPYMEAL=m
CONFIG_SUNGEM=m
CONFIG_NET_VENDOR_3COM=y
CONFIG_VORTEX=m
# CONFIG_TYPHOON is not set

#
# Tulip family network device support
#
# CONFIG_NET_TULIP is not set
CONFIG_HP100=m
CONFIG_NET_PCI=y
CONFIG_PCNET32=m
# CONFIG_AMD8111_ETH is not set
CONFIG_ADAPTEC_STARFIRE=m
# CONFIG_ADAPTEC_STARFIRE_NAPI is not set
# CONFIG_B44 is not set
# CONFIG_FORCEDETH is not set
# CONFIG_DGRS is not set
CONFIG_EEPRO100=m
# CONFIG_EEPRO100_PIO is not set
CONFIG_E100=m
# CONFIG_E100_NAPI is not set
CONFIG_FEALNX=m
CONFIG_NATSEMI=m
CONFIG_NE2K_PCI=m
CONFIG_8139CP=m
CONFIG_8139TOO=m
CONFIG_8139TOO_PIO=y
CONFIG_8139TOO_TUNE_TWISTER=y
CONFIG_8139TOO_8129=y
# CONFIG_8139_OLD_RX_RESET is not set
CONFIG_SIS900=m
CONFIG_EPIC100=m
CONFIG_SUNDANCE=m
# CONFIG_SUNDANCE_MMIO is not set
CONFIG_TLAN=m
CONFIG_VIA_RHINE=m
# CONFIG_VIA_RHINE_MMIO is not set
# CONFIG_VIA_VELOCITY is not set

#
# Ethernet (1000 Mbit)
#
# CONFIG_ACENIC is not set
CONFIG_DL2K=m
CONFIG_E1000=m
# CONFIG_E1000_NAPI is not set
# CONFIG_NS83820 is not set
# CONFIG_HAMACHI is not set
# CONFIG_YELLOWFIN is not set
# CONFIG_R8169 is not set
# CONFIG_SK98LIN is not set
# CONFIG_TIGON3 is not set

#
# Ethernet (10000 Mbit)
#
# CONFIG_IXGB is not set
# CONFIG_S2IO is not set

#
# Token Ring devices
#
# CONFIG_TR is not set

#
# Wireless LAN (non-hamradio)
#
CONFIG_NET_RADIO=y

#
# Obsolete Wireless cards support (pre-802.11)
#
CONFIG_STRIP=m

#
# Wireless 802.11b ISA/PCI cards support
#
CONFIG_HERMES=m
CONFIG_PLX_HERMES=m
CONFIG_TMD_HERMES=m
CONFIG_PCI_HERMES=m
CONFIG_ATMEL=m
CONFIG_PCI_ATMEL=m

#
# Prism GT/Duette 802.11(a/b/g) PCI/Cardbus support
#
CONFIG_PRISM54=m
CONFIG_NET_WIRELESS=y

#
# Wan interfaces
#
# CONFIG_WAN is not set
# CONFIG_FDDI is not set
# CONFIG_HIPPI is not set
# CONFIG_PLIP is not set
# CONFIG_PPP is not set
# CONFIG_SLIP is not set
# CONFIG_NET_FC is not set
# CONFIG_SHAPER is not set
# CONFIG_NETCONSOLE is not set

#
# ISDN subsystem
#
# CONFIG_ISDN is not set

#
# Telephony Support
#
# CONFIG_PHONE is not set

#
# Input device support
#
CONFIG_INPUT=y

#
# Userland interfaces
#
CONFIG_INPUT_MOUSEDEV=y
CONFIG_INPUT_MOUSEDEV_PSAUX=y
CONFIG_INPUT_MOUSEDEV_SCREEN_X=1400
CONFIG_INPUT_MOUSEDEV_SCREEN_Y=1050
CONFIG_INPUT_JOYDEV=m
# CONFIG_INPUT_TSDEV is not set
CONFIG_INPUT_EVDEV=m
# CONFIG_INPUT_EVBUG is not set

#
# Input I/O drivers
#
# CONFIG_GAMEPORT is not set
CONFIG_SOUND_GAMEPORT=y
CONFIG_SERIO=y
CONFIG_SERIO_I8042=y
CONFIG_SERIO_SERPORT=y
# CONFIG_SERIO_CT82C710 is not set
# CONFIG_SERIO_PARKBD is not set
# CONFIG_SERIO_PCIPS2 is not set
# CONFIG_SERIO_RAW is not set

#
# Input Device Drivers
#
CONFIG_INPUT_KEYBOARD=y
CONFIG_KEYBOARD_ATKBD=y
# CONFIG_KEYBOARD_SUNKBD is not set
# CONFIG_KEYBOARD_LKKBD is not set
# CONFIG_KEYBOARD_XTKBD is not set
# CONFIG_KEYBOARD_NEWTON is not set
CONFIG_INPUT_MOUSE=y
CONFIG_MOUSE_PS2=y
# CONFIG_MOUSE_SERIAL is not set
# CONFIG_MOUSE_VSXXXAA is not set
# CONFIG_INPUT_JOYSTICK is not set
# CONFIG_INPUT_TOUCHSCREEN is not set
# CONFIG_INPUT_MISC is not set

#
# Character devices
#
CONFIG_VT=y
CONFIG_VT_CONSOLE=y
CONFIG_HW_CONSOLE=y
# CONFIG_SERIAL_NONSTANDARD is not set

#
# Serial drivers
#
CONFIG_SERIAL_8250=y
CONFIG_SERIAL_8250_CONSOLE=y
CONFIG_SERIAL_8250_ACPI=y
CONFIG_SERIAL_8250_NR_UARTS=4
# CONFIG_SERIAL_8250_EXTENDED is not set

#
# Non-8250 serial port support
#
CONFIG_SERIAL_CORE=y
CONFIG_SERIAL_CORE_CONSOLE=y
CONFIG_UNIX98_PTYS=y
CONFIG_LEGACY_PTYS=y
CONFIG_LEGACY_PTY_COUNT=256
# CONFIG_PRINTER is not set
# CONFIG_PPDEV is not set
# CONFIG_TIPAR is not set

#
# IPMI
#
# CONFIG_IPMI_HANDLER is not set

#
# Watchdog Cards
#
# CONFIG_WATCHDOG is not set
# CONFIG_HW_RANDOM is not set
CONFIG_NVRAM=m
CONFIG_RTC=y
# CONFIG_DTLK is not set
# CONFIG_R3964 is not set
# CONFIG_APPLICOM is not set
# CONFIG_SONYPI is not set

#
# Ftape, the floppy tape device driver
#
# CONFIG_FTAPE is not set
CONFIG_AGP=y
# CONFIG_AGP_ALI is not set
# CONFIG_AGP_ATI is not set
# CONFIG_AGP_AMD is not set
# CONFIG_AGP_AMD64 is not set
CONFIG_AGP_INTEL=m
CONFIG_AGP_INTEL_MCH=m
# CONFIG_AGP_NVIDIA is not set
# CONFIG_AGP_SIS is not set
# CONFIG_AGP_SWORKS is not set
# CONFIG_AGP_VIA is not set
# CONFIG_AGP_EFFICEON is not set
CONFIG_DRM=y
# CONFIG_DRM_TDFX is not set
# CONFIG_DRM_R128 is not set
CONFIG_DRM_RADEON=m
# CONFIG_DRM_I810 is not set
# CONFIG_DRM_I830 is not set
# CONFIG_DRM_I915 is not set
# CONFIG_DRM_MGA is not set
# CONFIG_DRM_SIS is not set
# CONFIG_MWAVE is not set
# CONFIG_RAW_DRIVER is not set
CONFIG_HPET=y
# CONFIG_HPET_RTC_IRQ is not set
CONFIG_HPET_MMAP=y
CONFIG_HANGCHECK_TIMER=m

#
# I2C support
#
CONFIG_I2C=y
CONFIG_I2C_CHARDEV=m

#
# I2C Algorithms
#
CONFIG_I2C_ALGOBIT=y
CONFIG_I2C_ALGOPCF=m
CONFIG_I2C_ALGOPCA=m

#
# I2C Hardware Bus support
#
# CONFIG_I2C_ALI1535 is not set
# CONFIG_I2C_ALI1563 is not set
# CONFIG_I2C_ALI15X3 is not set
# CONFIG_I2C_AMD756 is not set
# CONFIG_I2C_AMD8111 is not set
# CONFIG_I2C_I801 is not set
# CONFIG_I2C_I810 is not set
CONFIG_I2C_ISA=m
# CONFIG_I2C_NFORCE2 is not set
CONFIG_I2C_PARPORT=m
# CONFIG_I2C_PARPORT_LIGHT is not set
# CONFIG_I2C_PIIX4 is not set
# CONFIG_I2C_PROSAVAGE is not set
# CONFIG_I2C_SAVAGE4 is not set
# CONFIG_SCx200_ACB is not set
# CONFIG_I2C_SIS5595 is not set
# CONFIG_I2C_SIS630 is not set
# CONFIG_I2C_SIS96X is not set
# CONFIG_I2C_VIA is not set
# CONFIG_I2C_VIAPRO is not set
# CONFIG_I2C_VOODOO3 is not set
CONFIG_I2C_PCA_ISA=m

#
# Hardware Sensors Chip support
#
CONFIG_I2C_SENSOR=m
# CONFIG_SENSORS_ADM1021 is not set
# CONFIG_SENSORS_ADM1025 is not set
# CONFIG_SENSORS_ADM1031 is not set
# CONFIG_SENSORS_ASB100 is not set
# CONFIG_SENSORS_DS1621 is not set
# CONFIG_SENSORS_FSCHER is not set
# CONFIG_SENSORS_GL518SM is not set
# CONFIG_SENSORS_IT87 is not set
# CONFIG_SENSORS_LM75 is not set
# CONFIG_SENSORS_LM77 is not set
# CONFIG_SENSORS_LM78 is not set
# CONFIG_SENSORS_LM80 is not set
# CONFIG_SENSORS_LM83 is not set
# CONFIG_SENSORS_LM85 is not set
# CONFIG_SENSORS_LM90 is not set
# CONFIG_SENSORS_MAX1619 is not set
CONFIG_SENSORS_SMSC47M1=m
# CONFIG_SENSORS_VIA686A is not set
# CONFIG_SENSORS_W83781D is not set
# CONFIG_SENSORS_W83L785TS is not set
# CONFIG_SENSORS_W83627HF is not set

#
# Other I2C Chip support
#
# CONFIG_SENSORS_EEPROM is not set
# CONFIG_SENSORS_PCF8574 is not set
# CONFIG_SENSORS_PCF8591 is not set
# CONFIG_SENSORS_RTC8564 is not set
# CONFIG_I2C_DEBUG_CORE is not set
# CONFIG_I2C_DEBUG_ALGO is not set
# CONFIG_I2C_DEBUG_BUS is not set
# CONFIG_I2C_DEBUG_CHIP is not set

#
# Dallas's 1-wire bus
#
# CONFIG_W1 is not set

#
# Misc devices
#
# CONFIG_IBM_ASM is not set

#
# Multimedia devices
#
CONFIG_VIDEO_DEV=m

#
# Video For Linux
#

#
# Video Adapters
#
CONFIG_VIDEO_BT848=m
CONFIG_VIDEO_BWQCAM=m
CONFIG_VIDEO_CQCAM=m
CONFIG_VIDEO_W9966=m
CONFIG_VIDEO_CPIA=m
CONFIG_VIDEO_CPIA_PP=m
CONFIG_VIDEO_CPIA_USB=m
# CONFIG_VIDEO_SAA5246A is not set
CONFIG_VIDEO_SAA5249=m
CONFIG_TUNER_3036=m
CONFIG_VIDEO_STRADIS=m
CONFIG_VIDEO_ZORAN=m
CONFIG_VIDEO_ZORAN_BUZ=m
CONFIG_VIDEO_ZORAN_DC10=m
# CONFIG_VIDEO_ZORAN_DC30 is not set
CONFIG_VIDEO_ZORAN_LML33=m
# CONFIG_VIDEO_ZORAN_LML33R10 is not set
# CONFIG_VIDEO_SAA7134 is not set
# CONFIG_VIDEO_MXB is not set
# CONFIG_VIDEO_DPC is not set
# CONFIG_VIDEO_HEXIUM_ORION is not set
# CONFIG_VIDEO_HEXIUM_GEMINI is not set
# CONFIG_VIDEO_CX88 is not set
# CONFIG_VIDEO_OVCAMCHIP is not set

#
# Radio Adapters
#
CONFIG_RADIO_GEMTEK_PCI=m
CONFIG_RADIO_MAXIRADIO=m
CONFIG_RADIO_MAESTRO=m

#
# Digital Video Broadcasting Devices
#
# CONFIG_DVB is not set
CONFIG_VIDEO_TUNER=m
CONFIG_VIDEO_BUF=m
CONFIG_VIDEO_BTCX=m
CONFIG_VIDEO_IR=m

#
# Graphics support
#
CONFIG_FB=y
CONFIG_FB_MODE_HELPERS=y
# CONFIG_FB_CIRRUS is not set
# CONFIG_FB_PM2 is not set
# CONFIG_FB_CYBER2000 is not set
# CONFIG_FB_ASILIANT is not set
# CONFIG_FB_IMSTT is not set
# CONFIG_FB_VGA16 is not set
# CONFIG_FB_VESA is not set
CONFIG_VIDEO_SELECT=y
# CONFIG_FB_HGA is not set
# CONFIG_FB_RIVA is not set
# CONFIG_FB_I810 is not set
# CONFIG_FB_MATROX is not set
# CONFIG_FB_RADEON_OLD is not set
CONFIG_FB_RADEON=y
CONFIG_FB_RADEON_I2C=y
CONFIG_FB_RADEON_DEBUG=y
# CONFIG_FB_ATY128 is not set
# CONFIG_FB_ATY is not set
# CONFIG_FB_SIS is not set
# CONFIG_FB_NEOMAGIC is not set
# CONFIG_FB_KYRO is not set
# CONFIG_FB_3DFX is not set
# CONFIG_FB_VOODOO1 is not set
# CONFIG_FB_TRIDENT is not set
# CONFIG_FB_VIRTUAL is not set

#
# Console display driver support
#
CONFIG_VGA_CONSOLE=y
CONFIG_DUMMY_CONSOLE=y
CONFIG_FRAMEBUFFER_CONSOLE=y
# CONFIG_FONTS is not set
CONFIG_FONT_8x8=y
CONFIG_FONT_8x16=y

#
# Logo configuration
#
CONFIG_LOGO=y
CONFIG_LOGO_LINUX_MONO=y
CONFIG_LOGO_LINUX_VGA16=y
CONFIG_LOGO_LINUX_CLUT224=y

#
# Sound
#
CONFIG_SOUND=m

#
# Advanced Linux Sound Architecture
#
CONFIG_SND=m
CONFIG_SND_TIMER=m
CONFIG_SND_PCM=m
CONFIG_SND_HWDEP=m
CONFIG_SND_RAWMIDI=m
CONFIG_SND_SEQUENCER=m
CONFIG_SND_SEQ_DUMMY=m
CONFIG_SND_OSSEMUL=y
CONFIG_SND_MIXER_OSS=m
CONFIG_SND_PCM_OSS=m
CONFIG_SND_SEQUENCER_OSS=y
CONFIG_SND_RTCTIMER=m
CONFIG_SND_VERBOSE_PRINTK=y
# CONFIG_SND_DEBUG is not set

#
# Generic devices
#
CONFIG_SND_MPU401_UART=m
CONFIG_SND_OPL3_LIB=m
CONFIG_SND_DUMMY=m
CONFIG_SND_VIRMIDI=m
CONFIG_SND_MTPAV=m
CONFIG_SND_SERIAL_U16550=m
CONFIG_SND_MPU401=m

#
# PCI devices
#
CONFIG_SND_AC97_CODEC=m
# CONFIG_SND_ALI5451 is not set
# CONFIG_SND_ATIIXP is not set
# CONFIG_SND_ATIIXP_MODEM is not set
# CONFIG_SND_AU8810 is not set
# CONFIG_SND_AU8820 is not set
# CONFIG_SND_AU8830 is not set
# CONFIG_SND_AZT3328 is not set
# CONFIG_SND_BT87X is not set
# CONFIG_SND_CS46XX is not set
# CONFIG_SND_CS4281 is not set
# CONFIG_SND_EMU10K1 is not set
# CONFIG_SND_KORG1212 is not set
# CONFIG_SND_MIXART is not set
# CONFIG_SND_NM256 is not set
# CONFIG_SND_RME32 is not set
# CONFIG_SND_RME96 is not set
# CONFIG_SND_RME9652 is not set
# CONFIG_SND_HDSP is not set
# CONFIG_SND_TRIDENT is not set
CONFIG_SND_YMFPCI=m
# CONFIG_SND_ALS4000 is not set
# CONFIG_SND_CMIPCI is not set
# CONFIG_SND_ENS1370 is not set
# CONFIG_SND_ENS1371 is not set
# CONFIG_SND_ES1938 is not set
# CONFIG_SND_ES1968 is not set
# CONFIG_SND_MAESTRO3 is not set
# CONFIG_SND_FM801 is not set
# CONFIG_SND_ICE1712 is not set
# CONFIG_SND_ICE1724 is not set
CONFIG_SND_INTEL8X0=m
CONFIG_SND_INTEL8X0M=m
# CONFIG_SND_SONICVIBES is not set
# CONFIG_SND_VIA82XX is not set
# CONFIG_SND_VX222 is not set

#
# ALSA USB devices
#
CONFIG_SND_USB_AUDIO=m
# CONFIG_SND_USB_USX2Y is not set

#
# Open Sound System
#
# CONFIG_SOUND_PRIME is not set

#
# USB support
#
CONFIG_USB=m
# CONFIG_USB_DEBUG is not set

#
# Miscellaneous USB options
#
CONFIG_USB_DEVICEFS=y
CONFIG_USB_BANDWIDTH=y
# CONFIG_USB_DYNAMIC_MINORS is not set
CONFIG_USB_SUSPEND=y
# CONFIG_USB_OTG is not set

#
# USB Host Controller Drivers
#
CONFIG_USB_EHCI_HCD=m
# CONFIG_USB_EHCI_SPLIT_ISO is not set
# CONFIG_USB_EHCI_ROOT_HUB_TT is not set
CONFIG_USB_OHCI_HCD=m
CONFIG_USB_UHCI_HCD=m

#
# USB Device Class drivers
#
# CONFIG_USB_AUDIO is not set

#
# USB Bluetooth TTY can only be used with disabled Bluetooth subsystem
#
# CONFIG_USB_MIDI is not set
# CONFIG_USB_ACM is not set
# CONFIG_USB_PRINTER is not set
CONFIG_USB_STORAGE=m
# CONFIG_USB_STORAGE_DEBUG is not set
# CONFIG_USB_STORAGE_RW_DETECT is not set
# CONFIG_USB_STORAGE_DATAFAB is not set
# CONFIG_USB_STORAGE_FREECOM is not set
# CONFIG_USB_STORAGE_ISD200 is not set
# CONFIG_USB_STORAGE_DPCM is not set
# CONFIG_USB_STORAGE_HP8200e is not set
# CONFIG_USB_STORAGE_SDDR09 is not set
# CONFIG_USB_STORAGE_SDDR55 is not set
# CONFIG_USB_STORAGE_JUMPSHOT is not set

#
# USB Human Interface Devices (HID)
#
CONFIG_USB_HID=m
CONFIG_USB_HIDINPUT=y
# CONFIG_HID_FF is not set
CONFIG_USB_HIDDEV=y

#
# USB HID Boot Protocol drivers
#
CONFIG_USB_KBD=m
CONFIG_USB_MOUSE=m
# CONFIG_USB_AIPTEK is not set
# CONFIG_USB_WACOM is not set
# CONFIG_USB_KBTAB is not set
# CONFIG_USB_POWERMATE is not set
# CONFIG_USB_MTOUCH is not set
# CONFIG_USB_EGALAX is not set
# CONFIG_USB_XPAD is not set
# CONFIG_USB_ATI_REMOTE is not set

#
# USB Imaging devices
#
CONFIG_USB_MDC800=m
CONFIG_USB_MICROTEK=m
CONFIG_USB_HPUSBSCSI=m

#
# USB Multimedia devices
#
# CONFIG_USB_DABUSB is not set
# CONFIG_USB_VICAM is not set
# CONFIG_USB_DSBR is not set
# CONFIG_USB_IBMCAM is not set
# CONFIG_USB_KONICAWC is not set
# CONFIG_USB_OV511 is not set
# CONFIG_USB_SE401 is not set
# CONFIG_USB_SN9C102 is not set
# CONFIG_USB_STV680 is not set

#
# USB Network adaptors
#
# CONFIG_USB_CATC is not set
# CONFIG_USB_KAWETH is not set
# CONFIG_USB_PEGASUS is not set
# CONFIG_USB_RTL8150 is not set
# CONFIG_USB_USBNET is not set

#
# USB port drivers
#
# CONFIG_USB_USS720 is not set

#
# USB Serial Converter support
#
# CONFIG_USB_SERIAL is not set

#
# USB Miscellaneous drivers
#
# CONFIG_USB_EMI62 is not set
# CONFIG_USB_EMI26 is not set
# CONFIG_USB_TIGL is not set
# CONFIG_USB_AUERSWALD is not set
# CONFIG_USB_RIO500 is not set
# CONFIG_USB_LEGOTOWER is not set
# CONFIG_USB_LCD is not set
# CONFIG_USB_LED is not set
# CONFIG_USB_CYTHERM is not set
# CONFIG_USB_PHIDGETSERVO is not set
# CONFIG_USB_TEST is not set

#
# USB Gadget Support
#
# CONFIG_USB_GADGET is not set

#
# File systems
#
# CONFIG_EXT2_FS is not set
CONFIG_EXT3_FS=y
CONFIG_EXT3_FS_XATTR=y
CONFIG_EXT3_FS_POSIX_ACL=y
CONFIG_EXT3_FS_SECURITY=y
CONFIG_JBD=y
# CONFIG_JBD_DEBUG is not set
CONFIG_FS_MBCACHE=y
# CONFIG_REISER4_FS is not set
# CONFIG_REISERFS_FS is not set
# CONFIG_JFS_FS is not set
CONFIG_FS_POSIX_ACL=y
# CONFIG_XFS_FS is not set
CONFIG_MINIX_FS=m
CONFIG_ROMFS_FS=m
CONFIG_QUOTA=y
CONFIG_QFMT_V1=m
CONFIG_QFMT_V2=m
CONFIG_QUOTACTL=y
CONFIG_AUTOFS_FS=m
CONFIG_AUTOFS4_FS=m

#
# Caches
#
# CONFIG_CACHEFS is not set

#
# CD-ROM/DVD Filesystems
#
CONFIG_ISO9660_FS=m
CONFIG_JOLIET=y
CONFIG_ZISOFS=y
CONFIG_ZISOFS_FS=m
CONFIG_UDF_FS=m
CONFIG_UDF_NLS=y

#
# DOS/FAT/NT Filesystems
#
CONFIG_FAT_FS=m
CONFIG_MSDOS_FS=m
CONFIG_VFAT_FS=m
CONFIG_FAT_DEFAULT_CODEPAGE=437
CONFIG_FAT_DEFAULT_IOCHARSET="iso8859-1"
CONFIG_NTFS_FS=m
# CONFIG_NTFS_DEBUG is not set
# CONFIG_NTFS_RW is not set

#
# Pseudo filesystems
#
CONFIG_PROC_FS=y
CONFIG_PROC_KCORE=y
CONFIG_SYSFS=y
# CONFIG_DEVFS_FS is not set
# CONFIG_DEVPTS_FS_XATTR is not set
CONFIG_TMPFS=y
# CONFIG_HUGETLBFS is not set
# CONFIG_HUGETLB_PAGE is not set
CONFIG_RAMFS=y

#
# Miscellaneous filesystems
#
# CONFIG_ADFS_FS is not set
# CONFIG_AFFS_FS is not set
# CONFIG_HFS_FS is not set
# CONFIG_HFSPLUS_FS is not set
# CONFIG_BEFS_FS is not set
# CONFIG_BFS_FS is not set
# CONFIG_EFS_FS is not set
CONFIG_CRAMFS=m
# CONFIG_VXFS_FS is not set
# CONFIG_HPFS_FS is not set
# CONFIG_QNX4FS_FS is not set
# CONFIG_SYSV_FS is not set
# CONFIG_UFS_FS is not set

#
# Network File Systems
#
CONFIG_NFS_FS=y
CONFIG_NFS_V3=y
# CONFIG_NFS_V4 is not set
# CONFIG_NFS_DIRECTIO is not set
CONFIG_NFSD=m
CONFIG_NFSD_V3=y
# CONFIG_NFSD_V4 is not set
# CONFIG_NFSD_TCP is not set
CONFIG_LOCKD=y
CONFIG_LOCKD_V4=y
CONFIG_EXPORTFS=m
CONFIG_SUNRPC=y
CONFIG_SUNRPC_GSS=m
# CONFIG_RPCSEC_GSS_KRB5 is not set
CONFIG_RPCSEC_GSS_SPKM3=m
CONFIG_SMB_FS=m
# CONFIG_SMB_NLS_DEFAULT is not set
CONFIG_CIFS=m
# CONFIG_CIFS_STATS is not set
CONFIG_CIFS_XATTR=y
# CONFIG_CIFS_POSIX is not set
# CONFIG_NCP_FS is not set
# CONFIG_CODA_FS is not set
# CONFIG_AFS_FS is not set

#
# Partition Types
#
# CONFIG_PARTITION_ADVANCED is not set
CONFIG_MSDOS_PARTITION=y

#
# Native Language Support
#
CONFIG_NLS=y
CONFIG_NLS_DEFAULT="cp437"
CONFIG_NLS_CODEPAGE_437=m
CONFIG_NLS_CODEPAGE_737=m
CONFIG_NLS_CODEPAGE_775=m
CONFIG_NLS_CODEPAGE_850=m
CONFIG_NLS_CODEPAGE_852=m
CONFIG_NLS_CODEPAGE_855=m
CONFIG_NLS_CODEPAGE_857=m
CONFIG_NLS_CODEPAGE_860=m
CONFIG_NLS_CODEPAGE_861=m
CONFIG_NLS_CODEPAGE_862=m
CONFIG_NLS_CODEPAGE_863=m
CONFIG_NLS_CODEPAGE_864=m
CONFIG_NLS_CODEPAGE_865=m
CONFIG_NLS_CODEPAGE_866=m
CONFIG_NLS_CODEPAGE_869=m
CONFIG_NLS_CODEPAGE_936=m
CONFIG_NLS_CODEPAGE_950=m
CONFIG_NLS_CODEPAGE_932=m
CONFIG_NLS_CODEPAGE_949=m
CONFIG_NLS_CODEPAGE_874=m
CONFIG_NLS_ISO8859_8=m
CONFIG_NLS_CODEPAGE_1250=m
CONFIG_NLS_CODEPAGE_1251=m
# CONFIG_NLS_ASCII is not set
CONFIG_NLS_ISO8859_1=m
CONFIG_NLS_ISO8859_2=m
CONFIG_NLS_ISO8859_3=m
CONFIG_NLS_ISO8859_4=m
CONFIG_NLS_ISO8859_5=m
CONFIG_NLS_ISO8859_6=m
CONFIG_NLS_ISO8859_7=m
CONFIG_NLS_ISO8859_9=m
CONFIG_NLS_ISO8859_13=m
CONFIG_NLS_ISO8859_14=m
CONFIG_NLS_ISO8859_15=m
CONFIG_NLS_KOI8_R=m
CONFIG_NLS_KOI8_U=m
CONFIG_NLS_UTF8=m

#
# Profiling support
#
# CONFIG_PROFILING is not set

#
# Kernel hacking
#
CONFIG_DEBUG_KERNEL=y
CONFIG_MAGIC_SYSRQ=y
# CONFIG_DEBUG_SLAB is not set
# CONFIG_DEBUG_SPINLOCK is not set
# CONFIG_DEBUG_SPINLOCK_SLEEP is not set
# CONFIG_DEBUG_INFO is not set
# CONFIG_FRAME_POINTER is not set
CONFIG_EARLY_PRINTK=y
# CONFIG_DEBUG_STACKOVERFLOW is not set
# CONFIG_KPROBES is not set
# CONFIG_DEBUG_STACK_USAGE is not set
# CONFIG_DEBUG_PAGEALLOC is not set
# CONFIG_4KSTACKS is not set
# CONFIG_SCHEDSTATS is not set
# CONFIG_KGDB is not set

#
# Security options
#
# CONFIG_KEYS is not set
# CONFIG_SECURITY is not set

#
# Cryptographic options
#
CONFIG_CRYPTO=y
CONFIG_CRYPTO_HMAC=y
CONFIG_CRYPTO_NULL=m
CONFIG_CRYPTO_MD4=m
CONFIG_CRYPTO_MD5=m
CONFIG_CRYPTO_SHA1=m
CONFIG_CRYPTO_SHA256=m
CONFIG_CRYPTO_SHA512=m
CONFIG_CRYPTO_WHIRLPOOL=m
CONFIG_CRYPTO_DES=m
CONFIG_CRYPTO_BLOWFISH=m
CONFIG_CRYPTO_TWOFISH=m
CONFIG_CRYPTO_SERPENT=m
CONFIG_CRYPTO_AES_586=m
CONFIG_CRYPTO_CAST5=m
CONFIG_CRYPTO_CAST6=m
CONFIG_CRYPTO_TEA=m
CONFIG_CRYPTO_ARC4=m
CONFIG_CRYPTO_KHAZAD=m
CONFIG_CRYPTO_DEFLATE=m
CONFIG_CRYPTO_MICHAEL_MIC=m
# CONFIG_CRYPTO_CRC32C is not set
# CONFIG_CRYPTO_TEST is not set

#
# Library routines
#
CONFIG_CRC_CCITT=y
CONFIG_CRC32=m
# CONFIG_LIBCRC32C is not set
CONFIG_ZLIB_INFLATE=m
CONFIG_ZLIB_DEFLATE=m
CONFIG_X86_BIOS_REBOOT=y
CONFIG_PC=y

2.6.9-rc2-mm[2-4]: zaphod-scheduler.patch makes swsusp incredibly slow (was: Re: 2.6.9-rc2-mm3: swsusp horribly slow on AMD64)

[Rafael J. Wysocki]

Hi,

I have verified that the odd symptoms described previously in this thread 
result from the zaphod-scheduler.patch.

To show this, I took the 2.6.9-rc2-mm2 kernel, reverted the 
zaphod-scheduler.patch and applied the following changes to swsusp.c:

--- a/kernel/power/swsusp.c	2004-09-29 21:45:15.000000000 +0200
+++ b/kernel/power/swsusp.c	2004-09-29 22:08:33.971404368 +0200
@@ -295,18 +295,20 @@
 	int error = 0;
 	int i;
 	unsigned int mod = nr_copy_pages / 100;
+	unsigned long start_time =  jiffies;
 
 	if (!mod)
 		mod = 1;
 
-	printk( "Writing data to swap (%d pages)...     ", nr_copy_pages );
+	printk( "Writing data to swap (%d pages)...                ", 
nr_copy_pages );
 	for (i = 0; i < nr_copy_pages && !error; i++) {
 		if (!(i%mod))
-			printk( "\b\b\b\b%3d%%", i / mod );
+			printk( "\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b%3d%%, time: %3ld",
+					i / mod, (jiffies - start_time)/HZ);
 		error = write_page((pagedir_nosave+i)->address,
 					  &((pagedir_nosave+i)->swap_address));
 	}
-	printk("\b\b\b\bdone\n");
+	printk(" ... done\n");
 	return error;
 }
 
Then, I obtained the following result:

Stopping tasks: ===============================|
Freeing memory... done (17507 pages freed)
PM: Attempting to suspend to disk.
PM: snapshotting memory.
swsusp: critical section:
..<7>[nosave pfn 0x582].............................................swsusp: 
Need to copy 10738 pages
suspend: (pages needed: 10738 + 512 free: 120141)
..<7>[nosave pfn 0x582].............................................swsusp: 
critical section/: done (10866 pages copied)
PM: writing image.
PCI: Setting latency timer of device 0000:00:02.0 to 64
PCI: Setting latency timer of device 0000:00:02.1 to 64
PCI: Setting latency timer of device 0000:00:02.2 to 64
ACPI: PCI interrupt 0000:00:06.0[A] -> GSI 5 (level, low) -> IRQ 5
PCI: Setting latency timer of device 0000:00:06.0 to 64
ACPI: PCI interrupt 0000:02:00.0[A] -> GSI 11 (level, low) -> IRQ 11
ACPI: PCI interrupt 0000:02:01.2[C] -> GSI 11 (level, low) -> IRQ 11
 swsusp: Version: 132617
 swsusp: Num Pages: 130880
 swsusp: UTS Sys: Linux
 swsusp: UTS Node: albercik
 swsusp: UTS Release: 2.6.9-rc2-mm2
 swsusp: UTS Version: #4 Wed Sep 29 22:09:48 CEST 2004
 swsusp: UTS Machine: x86_64
 swsusp: UTS Domain:
 swsusp: CPUs: 1
 swsusp: Image: 10866 Pages
 swsusp: Pagedir: 0 Pages
Writing data to swap (10866 pages)... 100%, time:   2 ... done
Writing pagedir (85 pages)
S|
Powering off system
Shutdown: hdc
acpi_power_off called

which is OK, IMO.  However, for the vanilla 2.6.9-rc2-mm2 (with the same 
changes to swsusp.c), I get:

[-- snip --]
 swsusp: Version: 132617
 swsusp: Num Pages: 130880
 swsusp: UTS Sys: Linux
 swsusp: UTS Node: albercik
 swsusp: UTS Release: 2.6.9-rc2-mm2
 swsusp: UTS Version: #2 Wed Sep 29 23:12:00 CEST 2004
 swsusp: UTS Machine: x86_64
 swsusp: UTS Domain:
 swsusp: CPUs: 1
 swsusp: Image: 11115 Pages
 swsusp: Pagedir: 0 Pages
Writing data to swap (11115 pages)...   6%, time: 738<6>SysRq : Resetting

which should give you an idea what kind of a slowdown I was talking about 
earlier.

Well, zaphod-scheduler.patch is a big patch and I know to little to be able to 
figure out what's wrong with it so it causes the observed symptoms to appear.  
If you can, please help me fix this.

Greets,
RJW

-- 
- Would you tell me, please, which way I ought to go from here?
- That depends a good deal on where you want to get to.
		-- Lewis Carroll "Alice's Adventures in Wonderland"

Re: 2.6.9-rc2-mm[2-4]: zaphod-scheduler.patch makes swsusp incredibly slow (was: Re: 2.6.9-rc2-mm3: swsusp horribly slow on AMD64)

[Pavel Machek]

Hi!

> I have verified that the odd symptoms described previously in this thread 
> result from the zaphod-scheduler.patch.
> 
> To show this, I took the 2.6.9-rc2-mm2 kernel, reverted the 
> zaphod-scheduler.patch and applied the following changes to
> swsusp.c:

Hmm, similar behaviour was observed when we had missing unplug in
-suse kernels (IIRC; Andrea debugged it, he might know more).
								Pavel

-- 
People were complaining that M$ turns users into beta-testers...
...jr ghea gurz vagb qrirybcref, naq gurl frrz gb yvxr vg gung jnl!

Re: 2.6.9-rc2-mm3: swsusp horribly slow on AMD64

[Stefan Seyfried]

Rafael J. Wysocki wrote:
> On Sunday 26 of September 2004 12:09, Pavel Machek wrote:

>>>>We have seen something similar after hdparm was used on specific
>>>>machines. Are you using hdparm?

Pavel, i am pretty sure the issue with hdparm and 32-bit disk access was
just a symptom, not the cause. Rafael, please try the patch i posted in
the other mail, i believe this is the right thing to do.

>>>Not explicitly, but it's used by SuSE initscripts to set IDE DMA, AFAICS.  
>>>However, the problem did not occur on 2.6.9-rc2-mm1 with the same 
>>>initscripts.
>>
>>Okay, so try what happens without the initscripts
> 
> I turned the stuff off but of course it didn't change anything. :-)

That's what i expected.

>>and try to locate change that breaks it...

> Well, I'm a bit confused:
> 
> --- linux-2.6.9-rc2-mm1/kernel/power/swsusp.c   2004-09-16 14:06:56.000000000 
> +0200
> +++ linux-2.6.9-rc2-mm3/kernel/power/swsusp.c   2004-09-24 11:35:18.000000000 
> +0200
> @@ -862,8 +862,8 @@
>         error = swsusp_arch_suspend();
>         /* Restore control flow magically appears here */
>         restore_processor_state();
> -       local_irq_enable();
>         restore_highmem();
> +       local_irq_enable();
>         return error;
>  }

without this one is needed or highmem will break "sometimes". Was really
nasty. You did have highmem-resume problems, didn't you?

    Stefan

Re: 2.6.9-rc2-mm3: swsusp horribly slow on AMD64

[Rafael J. Wysocki]

[-- Attachment #1: Type: text/plain, Size: 2791 bytes --]

On Sunday 26 of September 2004 23:00, Stefan Seyfried wrote:
> Rafael J. Wysocki wrote:
> > On Sunday 26 of September 2004 12:09, Pavel Machek wrote:
> 
> >>>>We have seen something similar after hdparm was used on specific
> >>>>machines. Are you using hdparm?
> 
> Pavel, i am pretty sure the issue with hdparm and 32-bit disk access was
> just a symptom, not the cause. Rafael, please try the patch i posted in
> the other mail, i believe this is the right thing to do.

In summary:

1) The patch does not fix the problem. :-(

2) In the meantime, I've made the following change to pci-driver.c:

--- pci-driver.c	2004-09-26 23:35:32.701574416 +0200
+++ pci-driver.c.rjw	2004-09-26 23:35:18.441742240 +0200
@@ -328,6 +328,7 @@
  */
 static void pci_default_resume(struct pci_dev *pci_dev)
 {
+	printk("pci_default_resume (0x%04x, 0x%04x): %ld\n", pci_dev->vendor, 
pci_dev->device, jiffies/HZ);
 	/* restore the PCI config space */
 	pci_restore_state(pci_dev, pci_dev->saved_config_space);
 	/* if the device was enabled before suspend, reenable */
@@ -343,6 +344,7 @@
 	struct pci_dev * pci_dev = to_pci_dev(dev);
 	struct pci_driver * drv = pci_dev->driver;
 
+	printk("pci_device_resume (0x%04x, 0x%04x): %ld\n", pci_dev->vendor, 
pci_dev->device, jiffies/HZ);
 	if (drv && drv->resume)
 		drv->resume(pci_dev);
 	else

in order to identify the offending device.  I'm now almost sure that the 
NVidia chipset is to blame but I don't know which part of it exactly.

I've got two logs (attached), one of which is taken from the system with all 
modules loaded (swsusp.log), and the other comes from the system with no 
modules except for ipv6 (swsusp-nomod.log).  As you can see from the first 
log, the system with all modules loaded slows down significantly after 
pci_device_resume() is called for the device having vendor id = 0x10de 
(NVidia) and device id = 0x00d7 (no idea).  The system without modules is 
capable of writing 80-83% of pages to the swap _before_ slows down too and I 
have to wait for 1/2 h for the remaining ~20%.

I'm afraid I can't get any more info until I sort out the sysrq problem.

[-- snip --]

> >         /* Restore control flow magically appears here */
> >         restore_processor_state();
> > -       local_irq_enable();
> >         restore_highmem();
> > +       local_irq_enable();
> >         return error;
> >  }
> 
> without this one is needed or highmem will break "sometimes". Was really
> nasty. You did have highmem-resume problems, didn't you?

Yup, probably.  I only need to apply it to 2.6.9-rc2-mm1 to confirm that it 
fixes what I've seen.

Greets,
RJW

-- 
- Would you tell me, please, which way I ought to go from here?
- That depends a good deal on where you want to get to.
		-- Lewis Carroll "Alice's Adventures in Wonderland"

[-- Attachment #2: swsusp.log --]
[-- Type: text/x-log, Size: 2971 bytes --]

Stopping tasks: ==============================|
Freeing memory... done (17085 pages freed)
PM: Attempting to suspend to disk.
PM: snapshotting memory.
swsusp: critical section:
..<7>[nosave pfn 0x588]....................................swsusp: Need to copy 10916 pages
suspend: (pages needed: 10916 + 512 free: 119963)
..<7>[nosave pfn 0x588]....................................swsusp: critical section/: done (11044 pages copied)
PM: writing image.
pci_device_resume (0x10de, 0x00d1): 4294786
pci_default_resume (0x10de, 0x00d1): 4294786
pci_device_resume (0x10de, 0x00d0): 4294786
pci_default_resume (0x10de, 0x00d0): 4294786
pci_device_resume (0x10de, 0x00d4): 4294786
pci_default_resume (0x10de, 0x00d4): 4294786
pci_device_resume (0x10de, 0x00d7): 4294786
PCI: Setting latency timer of device 0000:00:02.0 to 64
pci_device_resume (0x10de, 0x00d7): 4294792
PCI: Setting latency timer of device 0000:00:02.1 to 64
pci_device_resume (0x10de, 0x00d8): 4294798
PCI: Setting latency timer of device 0000:00:02.2 to 64
pci_device_resume (0x10de, 0x00da): 4294801
ACPI: PCI interrupt 0000:00:06.0[A] -> GSI 5 (level, low) -> IRQ 5
PCI: Setting latency timer of device 0000:00:06.0 to 64
pci_device_resume (0x10de, 0x00d9): 4294803
pci_default_resume (0x10de, 0x00d9): 4294803
pci_device_resume (0x10de, 0x00d5): 4294803
pci_default_resume (0x10de, 0x00d5): 4294803
pci_device_resume (0x10de, 0x00dd): 4294803
pci_default_resume (0x10de, 0x00dd): 4294803
pci_device_resume (0x10de, 0x00d2): 4294803
pci_default_resume (0x10de, 0x00d2): 4294803
pci_device_resume (0x1022, 0x1100): 4294803
pci_default_resume (0x1022, 0x1100): 4294803
pci_device_resume (0x1022, 0x1101): 4294803
pci_default_resume (0x1022, 0x1101): 4294803
pci_device_resume (0x1022, 0x1102): 4294803
pci_default_resume (0x1022, 0x1102): 4294803
pci_device_resume (0x1022, 0x1103): 4294803
pci_default_resume (0x1022, 0x1103): 4294803
pci_device_resume (0x11ab, 0x4320): 4294803
pci_default_resume (0x11ab, 0x4320): 4294803
ACPI: PCI interrupt 0000:02:00.0[A] -> GSI 11 (level, low) -> IRQ 11
pci_device_resume (0x1180, 0x0476): 4294803
pci_device_resume (0x1180, 0x0476): 4294806
pci_device_resume (0x1180, 0x0552): 4294809
ACPI: PCI interrupt 0000:02:01.2[C] -> GSI 11 (level, low) -> IRQ 11
pci_device_resume (0x1180, 0x0576): 4294809
pci_default_resume (0x1180, 0x0576): 4294809
pci_device_resume (0x1180, 0x0592): 4294809
pci_default_resume (0x1180, 0x0592): 4294809
pci_device_resume (0x14e4, 0x4320): 4294809
pci_default_resume (0x14e4, 0x4320): 4294809
pci_device_resume (0x10de, 0x031b): 4294809
pci_default_resume (0x10de, 0x031b): 4294809
 swsusp: Version: 132617
 swsusp: Num Pages: 130880
 swsusp: UTS Sys: Linux
 swsusp: UTS Node: albercik
 swsusp: UTS Release: 2.6.9-rc2-mm3
 swsusp: UTS Version: #4 Sun Sep 26 22:20:12 CEST 2004
 swsusp: UTS Machine: x86_64
 swsusp: UTS Domain:
 swsusp: CPUs: 1
 swsusp: Image: 11044 Pages
 swsusp: Pagedir: 0 Pages
Writing data to swap (11044 pages)...   0%


[-- Attachment #3: swsusp-nomod.log --]
[-- Type: text/x-log, Size: 3249 bytes --]

Stopping tasks: ===========================|
Freeing memory... done (18713 pages freed)
PM: Attempting to suspend to disk.
PM: snapshotting memory.
swsusp: critical section:
..<7>[nosave pfn 0x588]...................................swsusp: Need to copy 10285 pages
suspend: (pages needed: 10285 + 512 free: 120594)
..<7>[nosave pfn 0x588]...................................swsusp: critical section/: done (10413 pages copied)
PM: writing image.
pci_device_resume (0x10de, 0x00d1): 4295657
pci_default_resume (0x10de, 0x00d1): 4295657
pci_device_resume (0x10de, 0x00d0): 4295657
pci_default_resume (0x10de, 0x00d0): 4295657
pci_device_resume (0x10de, 0x00d4): 4295657
pci_default_resume (0x10de, 0x00d4): 4295657
pci_device_resume (0x10de, 0x00d7): 4295657
pci_default_resume (0x10de, 0x00d7): 4295657
pci_device_resume (0x10de, 0x00d7): 4295657
pci_default_resume (0x10de, 0x00d7): 4295657
pci_device_resume (0x10de, 0x00d8): 4295657
pci_default_resume (0x10de, 0x00d8): 4295657
pci_device_resume (0x10de, 0x00da): 4295657
pci_default_resume (0x10de, 0x00da): 4295657
ACPI: PCI interrupt 0000:00:06.0[A] -> GSI 5 (level, low) -> IRQ 5
PCI: Setting latency timer of device 0000:00:06.0 to 64
pci_device_resume (0x10de, 0x00d9): 4295657
pci_default_resume (0x10de, 0x00d9): 4295657
pci_device_resume (0x10de, 0x00d5): 4295657
pci_default_resume (0x10de, 0x00d5): 4295657
pci_device_resume (0x10de, 0x00dd): 4295657
pci_default_resume (0x10de, 0x00dd): 4295657
pci_device_resume (0x10de, 0x00d2): 4295657
pci_default_resume (0x10de, 0x00d2): 4295657
pci_device_resume (0x1022, 0x1100): 4295657
pci_default_resume (0x1022, 0x1100): 4295657
pci_device_resume (0x1022, 0x1101): 4295657
pci_default_resume (0x1022, 0x1101): 4295657
pci_device_resume (0x1022, 0x1102): 4295657
pci_default_resume (0x1022, 0x1102): 4295657
pci_device_resume (0x1022, 0x1103): 4295657
pci_default_resume (0x1022, 0x1103): 4295657
pci_device_resume (0x11ab, 0x4320): 4295657
pci_default_resume (0x11ab, 0x4320): 4295657
ACPI: PCI interrupt 0000:02:00.0[A] -> GSI 11 (level, low) -> IRQ 11
pci_device_resume (0x1180, 0x0476): 4295657
pci_default_resume (0x1180, 0x0476): 4295657
ACPI: PCI interrupt 0000:02:01.0[A] -> GSI 9 (level, low) -> IRQ 9
pci_device_resume (0x1180, 0x0476): 4295657
pci_default_resume (0x1180, 0x0476): 4295657
ACPI: PCI interrupt 0000:02:01.1[B] -> GSI 11 (level, low) -> IRQ 11
pci_device_resume (0x1180, 0x0552): 4295657
pci_default_resume (0x1180, 0x0552): 4295657
ACPI: PCI interrupt 0000:02:01.2[C] -> GSI 11 (level, low) -> IRQ 11
pci_device_resume (0x1180, 0x0576): 4295657
pci_default_resume (0x1180, 0x0576): 4295657
pci_device_resume (0x1180, 0x0592): 4295657
pci_default_resume (0x1180, 0x0592): 4295657
pci_device_resume (0x14e4, 0x4320): 4295657
pci_default_resume (0x14e4, 0x4320): 4295657
pci_device_resume (0x10de, 0x031b): 4295657
pci_default_resume (0x10de, 0x031b): 4295657
 swsusp: Version: 132617
 swsusp: Num Pages: 130880
 swsusp: UTS Sys: Linux
 swsusp: UTS Node: albercik
 swsusp: UTS Release: 2.6.9-rc2-mm3
 swsusp: UTS Version: #4 Sun Sep 26 22:20:12 CEST 2004
 swsusp: UTS Machine: x86_64
 swsusp: UTS Domain:
 swsusp: CPUs: 1
 swsusp: Image: 10413 Pages
 swsusp: Pagedir: 0 Pages
Writing data to swap (10413 pages)...  81%

Re: 2.6.9-rc2-mm3: swsusp horribly slow on AMD64

[Pavel Machek]

Hi!

> --- pci-driver.c	2004-09-26 23:35:32.701574416 +0200
> +++ pci-driver.c.rjw	2004-09-26 23:35:18.441742240 +0200
> @@ -328,6 +328,7 @@
>   */
>  static void pci_default_resume(struct pci_dev *pci_dev)
>  {
> +	printk("pci_default_resume (0x%04x, 0x%04x): %ld\n", pci_dev->vendor, 
> pci_dev->device, jiffies/HZ);
>  	/* restore the PCI config space */
>  	pci_restore_state(pci_dev, pci_dev->saved_config_space);
>  	/* if the device was enabled before suspend, reenable */
> @@ -343,6 +344,7 @@
>  	struct pci_dev * pci_dev = to_pci_dev(dev);
>  	struct pci_driver * drv = pci_dev->driver;
>  
> +	printk("pci_device_resume (0x%04x, 0x%04x): %ld\n", pci_dev->vendor, 
> pci_dev->device, jiffies/HZ);
>  	if (drv && drv->resume)
>  		drv->resume(pci_dev);
>  	else
> 
> in order to identify the offending device.  I'm now almost sure that the 
> NVidia chipset is to blame but I don't know which part of it exactly.
> 
> I've got two logs (attached), one of which is taken from the system with all 
> modules loaded (swsusp.log), and the other comes from the system with no 
> modules except for ipv6 (swsusp-nomod.log).  As you can see from the first 
> log, the system with all modules loaded slows down significantly after 
> pci_device_resume() is called for the device having vendor id = 0x10de 
> (NVidia) and device id = 0x00d7 (no idea).  The system without modules is 

lspci, and take a look?

> capable of writing 80-83% of pages to the swap _before_ slows down too and I 
> have to wait for 1/2 h for the remaining ~20%.

Strange, *very* strange.

> I'm afraid I can't get any more info until I sort out the sysrq
> problem.

This should remap magic key to both-shifts-both-alts-key. Worked for
me once...
								Pavel

--- clean-mm/drivers/char/keyboard.c	2004-09-26 01:34:24.000000000 +0200
+++ linux-mm/drivers/char/keyboard.c	2004-09-26 01:42:24.000000000 +0200
@@ -1079,6 +1079,23 @@
 		sysrq_down = down;
 		return;
 	}
+	if (test_bit(KEY_LEFTALT, key_down) &&
+	    test_bit(KEY_RIGHTALT, key_down) &&
+	    test_bit(KEY_LEFTSHIFT, key_down) &&
+	    test_bit(KEY_RIGHTSHIFT, key_down) &&
+		down && !rep) {
+		handle_sysrq(kbd_sysrq_xlate[keycode], regs, tty);
+#ifdef CONFIG_KGDB_SYSRQ
+                sysrq_down = 0;        /* in case we miss the "up" event */
+#endif
+		return;
+	}
+
+	if (down)
+		set_bit(keycode, key_down);
+	else
+		clear_bit(keycode, key_down);
+
 	if (sysrq_down && down && !rep) {
 		handle_sysrq(kbd_sysrq_xlate[keycode], regs, tty);
 #ifdef CONFIG_KGDB_SYSRQ
@@ -1114,11 +1131,6 @@
 		raw_mode = 1;
 	}
 
-	if (down)
-		set_bit(keycode, key_down);
-	else
-		clear_bit(keycode, key_down);
-
 	if (rep && (!vc_kbd_mode(kbd, VC_REPEAT) || (tty && 
 		(!L_ECHO(tty) && tty->driver->chars_in_buffer(tty))))) {
 		/*

-- 
People were complaining that M$ turns users into beta-testers...
...jr ghea gurz vagb qrirybcref, naq gurl frrz gb yvxr vg gung jnl!

Re: 2.6.9-rc2-mm3: swsusp horribly slow on AMD64

[Rafael J. Wysocki]

Hi,

On Monday 27 of September 2004 00:33, Pavel Machek wrote:
[-- snip --]
> > I've got two logs (attached), one of which is taken from the system with 
all 
> > modules loaded (swsusp.log), and the other comes from the system with no 
> > modules except for ipv6 (swsusp-nomod.log).  As you can see from the first 
> > log, the system with all modules loaded slows down significantly after 
> > pci_device_resume() is called for the device having vendor id = 0x10de 
> > (NVidia) and device id = 0x00d7 (no idea).  The system without modules is 
> 
> lspci, and take a look?

albercik:~ # lspci -n
[ ... ]
0000:00:02.0 Class 0c03: 10de:00d7 (rev a5)
0000:00:02.1 Class 0c03: 10de:00d7 (rev a5)
0000:00:02.2 Class 0c03: 10de:00d8 (rev a2)
[ ... ]

albercik:~ # lspci
[ ... ]
0000:00:02.0 USB Controller: nVidia Corporation nForce3 USB 1.1 (rev a5)
0000:00:02.1 USB Controller: nVidia Corporation nForce3 USB 1.1 (rev a5)
0000:00:02.2 USB Controller: nVidia Corporation nForce3 USB 2.0 (rev a2)
[ ... ]

So, it's the USB 1.1 controller (OHCI).

> > capable of writing 80-83% of pages to the swap _before_ slows down too and 
I 
> > have to wait for 1/2 h for the remaining ~20%.
> 
> Strange, *very* strange.

Yes, it is.

> > I'm afraid I can't get any more info until I sort out the sysrq
> > problem.
> 
> This should remap magic key to both-shifts-both-alts-key. Worked for
> me once...

Thanks a lot, but it turned out to be much simpler: sysrq was disabled by an 
initscript (shame on me, shame, shame).  I'll get the traces as soon as I can 
get something to attach to the serial console.  In the meantime, I'll try to 
look at the USB stuff.

Greets,
RJW

-- 
- Would you tell me, please, which way I ought to go from here?
- That depends a good deal on where you want to get to.
		-- Lewis Carroll "Alice's Adventures in Wonderland"