The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Soeren Sonnenburg <kernel@nn7.de>
To: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: 2.6.26-rc7: BUG at kernel/power/snapshot.c:493
Date: Fri, 27 Jun 2008 18:43:05 +0200	[thread overview]
Message-ID: <1214584985.22228.15.camel@localhost> (raw)

Dear all,

Anyone else seeing this? Happened after resuming from s2both (from
disk)...

VFS: Mounted root (ext2 filesystem).
------------[ cut here ]------------
kernel BUG at kernel/power/snapshot.c:493!
invalid opcode: 0000 [#1] PREEMPT SMP 
Modules linked in:

Pid: 568, comm: linuxrc Not tainted (2.6.26-rc7-sonne #35)
EIP: 0060:[<c0157f99>] EFLAGS: 00010282 CPU: 0
EIP is at memory_bm_set_bit+0x29/0x30
EAX: fffffff2 EBX: f7165f1c ECX: 00000000 EDX: 03000200
ESI: f7115000 EDI: b7f2a008 EBP: f7165f28 ESP: f7165f18
 DS: 007b ES: 007b FS: 00d8 GS: 0000 SS: 0068
Process linuxrc (pid: 568, ti=f7164000 task=f7b65f80 task.ti=f7164000)
Stack: f7165f1c 00000013 f7117000 00000002 f7165f5c c0158e9b bf96e5ec c02dd570 
       00001000 c05fa980 00000008 00000008 00000000 00000000 f7000200 c05fa980 
       b7f2a008 f7165f70 c015b3af f7000200 b7f2a008 00001000 f7165f90 c0185e28 
Call Trace:
 [<c0158e9b>] ? snapshot_write_next+0xcb/0x7a0
 [<c02dd570>] ? write_chan+0x0/0x380
 [<c015b3af>] ? snapshot_write+0x1f/0x70
 [<c0185e28>] ? vfs_write+0x98/0x120
 [<c015b390>] ? snapshot_write+0x0/0x70
 [<c0185f6d>] ? sys_write+0x3d/0x70
 [<c010333a>] ? syscall_call+0x7/0xb
 =======================
Code: 00 00 55 89 e5 53 83 ec 0c 8d 4d f8 8d 5d f4 89 1c 24 e8 4b ff ff ff 85 c0
EIP: [<c0157f99>] memory_bm_set_bit+0x29/0x30 SS:ESP 0068:f7165f18
---[ end trace 70a926e889075b3c ]---


Soeren

             reply	other threads:[~2008-06-27 16:43 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-27 16:43 Soeren Sonnenburg [this message]
2008-06-27 17:07 ` 2.6.26-rc7: BUG at kernel/power/snapshot.c:493 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
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=1214584985.22228.15.camel@localhost \
    --to=kernel@nn7.de \
    --cc=linux-kernel@vger.kernel.org \
    /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