Herbert Xu wrote:
> > > > > My laptop hangs when I try to log in to X with the current git
> > > > > kernel (commit 2a397e82c7db18019e408f953dd58dc1963a328c). It runs
> > > > > fine with 2.6.23. At boot time kdm starts normally, but hangs with
> > > > > the caps lock LED blinking immediately after
Andrew Morton wrote:
> > My laptop hangs when I try to log in to X with the current git kernel
> > (commit 2a397e82c7db18019e408f953dd58dc1963a328c). It runs fine with
> > 2.6.23. At boot time kdm starts normally, but hangs with the caps lock
> > LED blinking immediately after I press Enter after
Andrew Morton wrote:
My laptop hangs when I try to log in to X with the current git kernel
(commit 2a397e82c7db18019e408f953dd58dc1963a328c). It runs fine with
2.6.23. At boot time kdm starts normally, but hangs with the caps lock
LED blinking immediately after I press Enter after typing
Herbert Xu wrote:
My laptop hangs when I try to log in to X with the current git
kernel (commit 2a397e82c7db18019e408f953dd58dc1963a328c). It runs
fine with 2.6.23. At boot time kdm starts normally, but hangs with
the caps lock LED blinking immediately after I press Enter after
Marcus Better wrote:
> NO_HZ. I will try without it...
Nope, still the same result.
Marcus
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.htm
My laptop hangs when I try to log in to X with the current git kernel
(commit 2a397e82c7db18019e408f953dd58dc1963a328c). It runs fine with
2.6.23. At boot time kdm starts normally, but hangs with the caps lock LED
blinking immediately after I press Enter after typing the password.
I can log in
My laptop hangs when I try to log in to X with the current git kernel
(commit 2a397e82c7db18019e408f953dd58dc1963a328c). It runs fine with
2.6.23. At boot time kdm starts normally, but hangs with the caps lock LED
blinking immediately after I press Enter after typing the password.
I can log in
Marcus Better wrote:
NO_HZ. I will try without it...
Nope, still the same result.
Marcus
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ
Lennert Buytenhek wrote:
> Does that mean that the Debian ARM people have their heads so far
> up their collective asses that they think that every form of change
> is bad and are unable to accept that some forms of change might be
> for the better?
Well, I am not one of the Debian ARM people,
Krzysztof Halasa wrote:
> Lennert Buytenhek <[EMAIL PROTECTED]> writes:
>> There _is_ an ARM BE version of Debian.
>>
>> It's not an official port, but it's not maintained any worse than
>> the 'official' LE ARM Debian port is.
> Hmm... That changes a bit. Perhaps we should forget about
> that LE
Krzysztof Halasa wrote:
Lennert Buytenhek [EMAIL PROTECTED] writes:
There _is_ an ARM BE version of Debian.
It's not an official port, but it's not maintained any worse than
the 'official' LE ARM Debian port is.
Hmm... That changes a bit. Perhaps we should forget about
that LE thing then,
Lennert Buytenhek wrote:
Does that mean that the Debian ARM people have their heads so far
up their collective asses that they think that every form of change
is bad and are unable to accept that some forms of change might be
for the better?
Well, I am not one of the Debian ARM people, just a
> > s2ram -f -a3 -m: Works!
>
> Thanks. Should we consider this regression resolved?
Yes, as far as I am concerned...
Marcus
pgpC8jlaPgo64.pgp
Description: PGP signature
> Have you tried other combinations?
>
> s2ram -m -p -f
> s2ram -s -p -f
Yes, I tried these slightly different combinations:
s2ram -f -a3 -s: Works! The screen becomes green but is restored quickly. It
prints the following messages:
Allocated buffer at 0x11000 (base is 0x0)
ES: 0x1100 EBX:
Have you tried other combinations?
s2ram -m -p -f
s2ram -s -p -f
Yes, I tried these slightly different combinations:
s2ram -f -a3 -s: Works! The screen becomes green but is restored quickly. It
prints the following messages:
Allocated buffer at 0x11000 (base is 0x0)
ES: 0x1100 EBX: 0x
s2ram -f -a3 -m: Works!
Thanks. Should we consider this regression resolved?
Yes, as far as I am concerned...
Marcus
pgpC8jlaPgo64.pgp
Description: PGP signature
> Just for clarification, do you suspend from VESA framebuffer console or
> from VGA text console?
From VESA console.
Marcus
pgpVFqTnb6hcb.pgp
Description: PGP signature
Just for clarification, do you suspend from VESA framebuffer console or
from VGA text console?
From VESA console.
Marcus
pgpVFqTnb6hcb.pgp
Description: PGP signature
Antonino A. Daplas wrote:
> A screen with blinking green blocks implies that your display is in text
> mode, not in graphics mode.
Yes, it happens when I suspend from text mode.
> If the above does not work, also try
>
> acpi_sleep=s3_bios,s3_mode
Will try, but I'm using "s2ram -f -a3" which
Antonino A. Daplas wrote:
A screen with blinking green blocks implies that your display is in text
mode, not in graphics mode.
Yes, it happens when I suspend from text mode.
If the above does not work, also try
acpi_sleep=s3_bios,s3_mode
Will try, but I'm using s2ram -f -a3 which should
Eric W. Biederman wrote:
> >> Patch : http://lkml.org/lkml/2007/3/24/136
> Marcus any chance I could see an oops?
I didn't see anything, it froze with the yellow "Linux!" sign. Any idea how to
get a oops?
> Or you could try the patch I
> previously posted when debugging this with
Adrian Bunk wrote:
> > > Does setting CONFIG_PCI_MSI=n make any difference?
> >
> > Yes, it does. The hanging resume problem went away.
>
> Thanks for testing.
>
> If you enable it again, does the patch from [1] also fix it?
Yes, it appears to fix it.
Marcus
pgpnnyS0pETwQ.pgp
Description: PGP
er : Thomas Meyer <[EMAIL PROTECTED]>
> Frédéric Riss <[EMAIL PROTECTED]>
> Marcus Better <[EMAIL PROTECTED]>
> Handled-By : Eric W. Biederman <[EMAIL PROTECTED]>
> Patch : http://lkml.org/lkml/2007/3/24/136
> Status : patch
[EMAIL PROTECTED]
Frédéric Riss [EMAIL PROTECTED]
Marcus Better [EMAIL PROTECTED]
Handled-By : Eric W. Biederman [EMAIL PROTECTED]
Patch : http://lkml.org/lkml/2007/3/24/136
Status : patch was suggested
For the sake of completeness, my bisection resulted
Adrian Bunk wrote:
Does setting CONFIG_PCI_MSI=n make any difference?
Yes, it does. The hanging resume problem went away.
Thanks for testing.
If you enable it again, does the patch from [1] also fix it?
Yes, it appears to fix it.
Marcus
pgpnnyS0pETwQ.pgp
Description: PGP signature
Eric W. Biederman wrote:
Patch : http://lkml.org/lkml/2007/3/24/136
Marcus any chance I could see an oops?
I didn't see anything, it froze with the yellow Linux! sign. Any idea how to
get a oops?
Or you could try the patch I
previously posted when debugging this with Thomas.
Do
Adrian Bunk wrote:
> > > Subject: ThinkPad R60: suspend to disk broken
> Does setting CONFIG_PCI_MSI=n make any difference?
Yes, it does. The hanging resume problem went away.
(The display corruption and the instant resume were not affected.)
Marcus
-
To unsubscribe from this list: send
Pavel Machek wrote:
>> > Subject: ThinkPad R60: suspend to disk broken
>> > References : http://lkml.org/lkml/2007/3/23/74
>> input, so I suspended to RAM again. This time the resume failed, it hung
>> after printing "Linux!" in yellow at the top of the screen.
> Yellow Linux! is my
Adrian Bunk wrote:
> Subject: ThinkPad R60: suspend to disk broken
> References : http://lkml.org/lkml/2007/3/23/74
> Submitter : Marcus Better <[EMAIL PROTECTED]>
> Status : submitter tries to bisect
I just tried -rc5. Now suspend to disk seems to work. I think the XF
Adrian Bunk wrote:
Subject: ThinkPad R60: suspend to disk broken
References : http://lkml.org/lkml/2007/3/23/74
Submitter : Marcus Better [EMAIL PROTECTED]
Status : submitter tries to bisect
I just tried -rc5. Now suspend to disk seems to work. I think the XFS
workqueue patch fixed
Pavel Machek wrote:
Subject: ThinkPad R60: suspend to disk broken
References : http://lkml.org/lkml/2007/3/23/74
input, so I suspended to RAM again. This time the resume failed, it hung
after printing Linux! in yellow at the top of the screen.
Yellow Linux! is my debugging trick.
Adrian Bunk wrote:
Subject: ThinkPad R60: suspend to disk broken
Does setting CONFIG_PCI_MSI=n make any difference?
Yes, it does. The hanging resume problem went away.
(The display corruption and the instant resume were not affected.)
Marcus
-
To unsubscribe from this list: send the
> Do you use the microcode driver?
No.
I'm in the middle of bisecting. Strange enough the symptoms change as I go.
Some commits manage to suspend to RAM, but hang at resume.
Marcus
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL
Marcus Better wrote:
> The XFS workqueue patch [1] fixes my problem [2].
> [1] http://permalink.gmane.org/gmane.linux.kernel/507616
> [2] http://permalink.gmane.org/gmane.linux.kernel/505570
Unfortunately it only fixed suspend to RAM. Suspend to disk still hangs
at "snaps
Marcus Better wrote:
The XFS workqueue patch [1] fixes my problem [2].
[1] http://permalink.gmane.org/gmane.linux.kernel/507616
[2] http://permalink.gmane.org/gmane.linux.kernel/505570
Unfortunately it only fixed suspend to RAM. Suspend to disk still hangs
at snapshotting system. Will try
Do you use the microcode driver?
No.
I'm in the middle of bisecting. Strange enough the symptoms change as I go.
Some commits manage to suspend to RAM, but hang at resume.
Marcus
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL
Thomas Gleixner wrote:
> You said, that the breakage came between 2.6.20 and rc2. Can you bisect
> it ?
The XFS workqueue patch [1] fixes my problem [2].
Marcus
[1] http://permalink.gmane.org/gmane.linux.kernel/507616
[2] http://permalink.gmane.org/gmane.linux.kernel/505570
pgpv6EWLbYBMj.pgp
Thomas Gleixner wrote:
You said, that the breakage came between 2.6.20 and rc2. Can you bisect
it ?
The XFS workqueue patch [1] fixes my problem [2].
Marcus
[1] http://permalink.gmane.org/gmane.linux.kernel/507616
[2] http://permalink.gmane.org/gmane.linux.kernel/505570
pgpv6EWLbYBMj.pgp
Thomas Gleixner wrote:
> I finally found a dual core box, which survives suspend/resume without
> crashing in the middle of nowhere. Sigh, I never figured out from the
> code and the bug reports what's going on.
>
> The observed hangs are caused by a stale state transition of the clock
> event
Thomas Gleixner wrote:
I finally found a dual core box, which survives suspend/resume without
crashing in the middle of nowhere. Sigh, I never figured out from the
code and the bug reports what's going on.
The observed hangs are caused by a stale state transition of the clock
event
Marcus Better wrote:
> suspend (to RAM and disk) broke on my Thinkpad R60 (Core 2 Duo laptop)
> somewhere between 2.6.20 and 2.6.21-rc3
I just tried -rc4, and it's still broken.
Marcus
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a m
Hi,
suspend (to RAM and disk) broke on my Thinkpad R60 (Core 2 Duo laptop)
somewhere between 2.6.20 and 2.6.21-rc3 (commit
8ce5e3e45e01ffab38a9f03900181132b9068543), but most likely before -rc2. In
contrast to previous reports I saw on the list, it actually hangs at
suspend, not resume.
On
Hi,
suspend (to RAM and disk) broke on my Thinkpad R60 (Core 2 Duo laptop)
somewhere between 2.6.20 and 2.6.21-rc3 (commit
8ce5e3e45e01ffab38a9f03900181132b9068543), but most likely before -rc2. In
contrast to previous reports I saw on the list, it actually hangs at
suspend, not resume.
On
Marcus Better wrote:
suspend (to RAM and disk) broke on my Thinkpad R60 (Core 2 Duo laptop)
somewhere between 2.6.20 and 2.6.21-rc3
I just tried -rc4, and it's still broken.
Marcus
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL
44 matches
Mail list logo
