[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <200807112247.44530.rjw@sisk.pl>
Date: Fri, 11 Jul 2008 22:47:44 +0200
From: "Rafael J. Wysocki" <rjw@...k.pl>
To: Pavel Machek <pavel@...e.cz>
Cc: Soeren Sonnenburg <kernel@....de>,
Linux Kernel <linux-kernel@...r.kernel.org>
Subject: Re: 2.6.26-rc7: BUG at kernel/power/snapshot.c:493
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... |./.-.\.|./.-.\.|./.-.\.|./.-.\.|./.-.\.|./.-.\.|./.-.\.|./.-.\.|./.-.\.|./.-.\.|./.-.\.|./.-.\.|./.-.\.|./.-.\.|./.-.\.|./.-.\.|./.-.\.|./.-.\.|./.-.\.|./.-.\.|./.-.\.|./.-.\.|./.-.\.|./.-.\.|./.-.\.|./.-.\.|./.-.\.|./.-.\.|./.-.\.|./.-.\.|./.-.\.|.done.
>
> (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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists