From: Robert Hancock <hancockr@shaw.ca>
To: Jacek Luczak <difrost.kernel@gmail.com>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>,
Zdenek Kabelac <zdenek.kabelac@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Suspend to memory is freezing my machine
Date: Sun, 04 May 2008 11:36:56 -0600 [thread overview]
Message-ID: <481DF438.30307@shaw.ca> (raw)
In-Reply-To: <fa.plXIUcQIe19WMbpH4aKYo6JX1RQ@ifi.uio.no>
Jacek Luczak wrote:
> Rafael J. Wysocki pisze:
>> On Sunday, 4 of May 2008, Zdenek Kabelac wrote:
>>> Hello
>> Hi,
>>
>>> With recent 2.6.25 & 2.6.26-rc1 git (around 1 week) I get occasionally
>>> complete freeze of my T61 during suspend. (dual core, 2GB).
>> How reproducible is this?
>>
>>> I'm running kernel with no_console_suspend - but all I can see is
>>> blinking cursor on an empty screen - thus even when I run kernel with
>>> most debug options turned on, I can't pass more details so far. I run
>>> suspend with with SD card in - so maybe some update in the MMC driver
>>> might be responsible for this ?
>>>
>>> Also - I think that option no_console_suspend doens't work correctly -
>>> as many times with suspend I do not see any log message on my console
>>> screen. However sometimes the log is shown.
>> It would be helpful if you could verify if:
>>
>> (1) The problem occurs without no_console_suspend.
>> (2) The problem occurs without the SD card.
>>
>
> Hi Rafael,
>
> same problem here, although I was able to resume system (it's basically Intel
> machine) , but it was unusable - I was able to switch between terminals and see
> output from kernel. So there was:
> - Disabling irq #19;
> - some kind of lock spinning on disk:
> IDE interface: Intel Corporation 82801GBM/GHM (ICH7 Family) Serial ATA Storage
> Controller IDE (rev 02)
> but I can't provide more output of that lock now - no sign in logs.
>
> I've made some successful suspend/resume all without sound card active without
> problem. Those appear with sound card active, but I must take closer look - will
> send info later.
Can you post your dmesg and /proc/interrupts output from normal bootup ?
next parent reply other threads:[~2008-05-04 17:37 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.4esVkXHbwOL+Pzatd+lYSGawfns@ifi.uio.no>
[not found] ` <fa.zsdi5UBi6URzBaRSfFXIc6F7kHk@ifi.uio.no>
[not found] ` <fa.plXIUcQIe19WMbpH4aKYo6JX1RQ@ifi.uio.no>
2008-05-04 17:36 ` Robert Hancock [this message]
2008-05-04 17:42 ` Suspend to memory is freezing my machine Jacek Luczak
2008-05-04 18:01 ` Robert Hancock
2008-05-04 18:52 ` Jacek Luczak
2008-05-04 19:44 ` Jacek Luczak
2008-05-04 21:06 ` Robert Hancock
2008-05-07 20:29 ` Jacek Luczak
2008-05-04 7:37 Zdenek Kabelac
2008-05-04 10:40 ` Rafael J. Wysocki
2008-05-04 12:32 ` Jacek Luczak
2008-05-04 21:02 ` Zdenek Kabelac
2008-05-22 9:40 ` Zdenek Kabelac
2008-05-24 21:01 ` Rafael J. Wysocki
2008-05-25 8:56 ` Zdenek Kabelac
2008-05-25 8:59 ` Zdenek Kabelac
2008-05-25 12:24 ` Rafael J. Wysocki
2008-05-27 6:44 ` Zdenek Kabelac
2008-06-03 8:10 ` Zdenek Kabelac
2008-05-05 14:10 ` Pavel Machek
2008-05-06 9:15 ` Zdenek Kabelac
2008-05-07 14:33 ` Andrea Arcangeli
2008-05-07 14:43 ` Zdenek Kabelac
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=481DF438.30307@shaw.ca \
--to=hancockr@shaw.ca \
--cc=difrost.kernel@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rjw@sisk.pl \
--cc=zdenek.kabelac@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox