Re: 2.6.21-rc1: known regressions (part 2)
- From: "Michael S. Tsirkin" <mst@xxxxxxxxxxxxxx>
- Date: Mon, 5 Mar 2007 10:42:57 +0200
Quoting Pavel Machek <pavel@xxxxxx>:
Subject: Re: 2.6.21-rc1: known regressions (part 2)
Hi!
* Jens Axboe <jens.axboe@xxxxxxxxxx> wrote:
f3ccb06f3b8e0cf42b579db21f3ca7f17fcc3f38 works for me, [...]
update: f3ccb06f3b8e0cf42b579db21f3ca7f17fcc3f38 works for me too, and
01363220f5d23ef68276db8974e46a502e43d01d is broken. I too will attempt
to bisect this.
Strange; on my x60, suspend to ram works okay.
(Resume is very slow, because disks are not spinned up properly; and
there's something wrong with timers; console beeps take way too long).
dmesg attached.
That's with
commit 7b965e0884cee430ffe5dc81cdb117b9316b0549
tree 754dce6432258e0a8c3a758e13a34eb3a1d22ee1
parent 5a39e8c6d655b4fe8305ef8cc2d9bbe782bfee5f
author Trond Myklebust <Trond.Myklebust@xxxxxxxxxx> Wed, 28 Feb 2007
20:13:55 -0800
committer Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxxxxxxxx> Thu, 01
Mar 2007 14:53:39 -0800
[PATCH] VM: invalidate_inode_pages2_range() should not exit early
Fix invalidate_inode_pages2_range() so that it does not
immediately exit
just because a single page in the specified range could not be
removed.
Signed-off-by: Trond Myklebust <Trond.Myklebust@xxxxxxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
Signed-off-by: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
Pavel, I tried with your .config, and indeed the system came back to life after
2-3 minutes after I press Fn/F4, indeed the issue seems to be with the disk.
It could be that the same takes place with my original .config - maybe
I just wasn't patient enough. I'll need to re-test that.
However, I noticed that, after resume, when the system is presumably functional,
if I try to suspend to ram again, this second suspend hangs, displaying
the following on screen:
[ 17.170000] ACPI: PCI Interrupt 0000:02:00.0[A] -> GSI 16 (level, low) -> IRQ 20
[ 17.170000] PCI: Setting latency timer of device 0000:02:00.0 to 64
[ 17.250000] e1000: 0000:02:00.0: e1000_probe: (PCI Express:2.5Gb/s:Width x1) 00:16:41:5
4:6c:47
[ 17.330000] e1000: eth0: e1000_probe: Intel(R) PRO/1000 Network Connection
the crescent LED starts blinking and does not seem to stop for at lest 10 min,
I've run out of patience after that. It could be that it's just very slow again.
Pavel, did you try suspend to RAM after a successfull resume from RAM?
Under 2.6.20, the system suspends/resumes to memory within about 20 sec
any number of times.
--
MST
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
- Follow-Ups:
- Re: [linux-pm] 2.6.21-rc1: known regressions (part 2)
- From: Pavel Machek
- SATA resume slowness, e1000 MSI warning
- From: Ingo Molnar
- Re: [linux-pm] 2.6.21-rc1: known regressions (part 2)
- References:
- Re: 2.6.21-rc1: known regressions (part 2)
- From: Ingo Molnar
- Re: 2.6.21-rc1: known regressions (part 2)
- From: Pavel Machek
- Re: 2.6.21-rc1: known regressions (part 2)
- Prev by Date: Re: [PATCH -mm 1/5] Blackfin: blackfin architecture patch update
- Next by Date: Re: [patch] KVM: T60 resume fix
- Previous by thread: Re: 2.6.21-rc1: known regressions (part 2)
- Next by thread: SATA resume slowness, e1000 MSI warning
- Index(es):
Relevant Pages
|
