From: Michal Piotrowski <michal.k.k.piotrowski@gmail.com>
To: Andrey Borzenkov <arvidjaar@mail.ru>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>,
michal.k.k.piotrowski@gmail.com, linux-kernel@vger.kernel.org,
Pavel Machek <pavel@ucw.cz>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [possible regression] 2.6.22 reiserfs/libata sporadically hangs on resume from hibernation
Date: Sun, 01 Jul 2007 01:33:14 +0200 [thread overview]
Message-ID: <4686E83A.4040301@googlemail.com> (raw)
In-Reply-To: <200707010134.30843.arvidjaar@mail.ru>
Andrey Borzenkov pisze:
> On Sunday 01 July 2007, Rafael J. Wysocki wrote:
>> On Saturday, 30 June 2007 06:59, Andrey Borzenkov wrote:
>>> Since 2.6.18 I do not have suspend to RAM; now I am starting to lose
>>> suspend to disk :)
>>>
>>> Environment - vanilla kernel (2.6.22-rc6 currently + squashfs + single
>>> pata_ali patch to switch off DMA on CD-ROM), single root on reiserfs,
>>> libata with pata_ali driver.
>>>
>>> Until 2.6.22-rc I never had problems with hibernation. With 2.6.22-rc
>>> system hung at least once in every rcX. Up to rc6 those lockups were
>>> absolutely silent (black screen without reaction to any key). In rc6 I
>>> just got something different. After resume I got on screem:
>>>
>>> swsusp: Marking nosave pages: 000000000009f000-0000000000100000
>>> swsusp: Basic memory bitmaps created
>>> swsusp: Basic memory bitmaps freed
>>>
>>> After that it just sits there doing nothing. Ther was brief sound of HDD
>>> but I suspect it was related more to power-on. System was responding to
>>> power-on button press:
>>>
>>> ACPI Error (event-0305): No installed handler for fixed event [00000002
>>> 20070125]
>>>
>>> And SysRq was functioning.
>> That probably means that there's a deadlock somewhere in there.
>>
>>> Unfortunately I do not have serial console so I
>>> copy manually stacks from several last screens of output; I have tried to
>>> make a photo but right now my kbluetooth is refusing to work at all so I
>>> cannot transfer them :( (but I suspect quality would be too bad anyway)
>>>
>>> laptop_mode D
>>> io_schedule+0xe/0x20
>> Looks suspicious to me. Can you identify what line of code this points to?
>>
>
> If you could explain how to ...
gdb vmlinux
(gdb) l *io_schedule+0xe
Regards,
Michal
--
LOG
http://www.stardust.webpages.pl/log/
next prev parent reply other threads:[~2007-06-30 23:33 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-30 4:59 [possible regression] 2.6.22 reiserfs/libata sporadically hangs on resume from hibernation Andrey Borzenkov
2007-06-30 20:37 ` Rafael J. Wysocki
2007-06-30 21:34 ` Andrey Borzenkov
2007-06-30 23:33 ` Michal Piotrowski [this message]
2007-07-01 10:09 ` Rafael J. Wysocki
2007-07-15 18:56 ` Andrey Borzenkov
2007-09-02 11:29 ` Andrey Borzenkov
2007-09-02 14:49 ` Kasper Sandberg
2007-06-30 23:03 ` Pavel Machek
2007-09-09 14:00 ` Andrey Borzenkov
2007-09-09 17:07 ` Rafael J. Wysocki
2007-09-09 17:40 ` Andrey Borzenkov
2007-11-21 17:12 ` Andrey Borzenkov
2007-11-21 19:47 ` Rafael J. Wysocki
2008-03-13 4:08 ` Andrey Borzenkov
2008-03-13 20:46 ` Rafael J. Wysocki
2008-03-16 19:04 ` Andrey Borzenkov
2008-03-16 19:25 ` Rafael J. Wysocki
2008-03-17 4:00 ` Andrey Borzenkov
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=4686E83A.4040301@googlemail.com \
--to=michal.k.k.piotrowski@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=arvidjaar@mail.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=rjw@sisk.pl \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.