From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Pavel Machek <pavel@suse.cz>
Cc: Soeren Sonnenburg <kernel@nn7.de>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.26-rc7: BUG at kernel/power/snapshot.c:493
Date: Fri, 11 Jul 2008 22:47:44 +0200 [thread overview]
Message-ID: <200807112247.44530.rjw@sisk.pl> (raw)
In-Reply-To: <20080711204023.GE6843@elf.ucw.cz>
On Friday, 11 of July 2008, Pavel Machek wrote:
> On Fri 2008-07-11 22:33:52, Rafael J. Wysocki wrote:
> > On Friday, 11 of July 2008, Pavel Machek wrote:
> > > Hi!
> > >
> > > > > > Anyone else seeing this? Happened after resuming from s2both (from
> > > > > > disk)...
> > > > >
> > > > > At what point exactly did it happen?
> > > >
> > > > I am attaching the full dmesg.
> > >
> > > Something is seriously wrong here.
> > >
> > > > usbcore: registered new interface driver usbhid
> > > > usbhid: v2.6:USB HID core driver
> > > > TCP cubic registered
> > > > NET: Registered protocol family 10
> > > > lo: Disabled Privacy Extensions
> > > > Mobile IPv6
> > > > NET: Registered protocol family 17
> > > > NET: Registered protocol family 15
> > > > Using IPI No-Shortcut mode
> > > > RAMDISK: ext2 filesystem found at block 0
> > > > RAMDISK: Loading 2000KiB [1 disk] into ram disk... |\b/\b-\b\\b|\b/\b-\b\\b|\b/\b-\b\\b|\b/\b-\b\\b|\b/\b-\b\\b|\b/\b-\b\\b|\b/\b-\b\\b|\b/\b-\b\\b|\b/\b-\b\\b|\b/\b-\b\\b|\b/\b-\b\\b|\b/\b-\b\\b|\b/\b-\b\\b|\b/\b-\b\\b|\b/\b-\b\\b|\b/\b-\b\\b|\b/\b-\b\\b|\b/\b-\b\\b|\b/\b-\b\\b|\b/\b-\b\\b|\b/\b-\b\\b|\b/\b-\b\\b|\b/\b-\b\\b|\b/\b-\b\\b|\b/\b-\b\\b|\b/\b-\b\\b|\b/\b-\b\\b|\b/\b-\b\\b|\b/\b-\b\\b|\b/\b-\b\\b|\b/\b-\b\\b|\bdone.
>
> (1)
> > > > EXT2-fs warning: checktime reached, running e2fsck is recommended
> (2)
> > > > VFS: Mounted root (ext2 filesystem).
> > > > ------------[ cut here ]------------
> > > > kernel BUG at kernel/power/snapshot.c:493!
> > > > invalid opcode: 0000 [#1] PREEMPT SMP
> > > > Modules linked in:
> > >
> > > This is _after_ we mounted filesystems... we should not be resuming at
> > > this point.
> >
> > This is an initrd, isn't it?
>
> Does not look like so: it mounted some filesystem at (1), and
> checktime is reached. I thought initrd is read-only RAM disk -- it
> should not reach check time, no?
Yes, it will reach the check time if it's ext2 (which is the case).
Thanks,
Rafael
next prev parent reply other threads:[~2008-07-11 20:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-27 16:43 2.6.26-rc7: BUG at kernel/power/snapshot.c:493 Soeren Sonnenburg
2008-06-27 17:07 ` Rafael J. Wysocki
2008-06-27 18:14 ` Soeren Sonnenburg
2008-06-27 19:35 ` Rafael J. Wysocki
2008-07-11 19:54 ` Pavel Machek
2008-07-11 20:33 ` Rafael J. Wysocki
2008-07-11 20:40 ` Pavel Machek
2008-07-11 20:47 ` Rafael J. Wysocki [this message]
2008-07-09 13:08 ` Martin Michlmayr
2008-07-09 21:00 ` Rafael J. Wysocki
2008-07-11 15:38 ` Martin Michlmayr
2008-07-11 19:05 ` Rafael J. Wysocki
2008-07-15 12:44 ` Martin Michlmayr
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=200807112247.44530.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=kernel@nn7.de \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@suse.cz \
/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