Bug 12241

Latest working kernel version: Long term bug
Earliest failing kernel version: At least 2.6.27
Distribution: Gentoo
Hardware/Software: 768 MB RAM, 1 GB swap partition, reiserfs filesystems

Problem Description:
The problem occured in my fourth attempt in quick succession to suspend
to disk. The first three did not succeed due to insufficient free swap. I then closed a few running programs to free some extra memory and did a fourth suspend to disk attempt that provoked the BUG with trace below.

This is at least the third time I've seen this, but as I reported earlier at [1] I did not capture the OOPS properly. I'm pretty sure it is a bug from at least 2.6.27, but it could have been there for years as far as I'm concerned since suspend to disk works well under most cirsumstances and I haven't been using it that much earlier.

I'm running into this bug when my computer has had an uptime of weeks, so it is not exactly easy to reproduce. I have tried upon a fresh bootup to provoke the crash without luck, but I haven't tried really hard and I'd say it is realiably reproducable if I put the right effort into it.

The key to reproduce it seems to be allocating sufficient memory for suspend to disk to fail due to insufficient swap space, do multiple attempts in succession and then free a bit of memory and attempt again. I'm not sure whether the multiple attempts in succession are really required, but I believe that I've been doing that each time the BUG has showned its ugly face.

The OOPS looks like this, the full details can be seen in the pictures I'm attaching. I'd gladly type in the text from the pictures if anyone finds it useful and requests it.

kernel BUG at fs/inode.c:1153!ks ...
invalid opcode 0000 [#1] PREEMPT

EIP is at iput
Pid: 2515, comm: bash Tainted: G         W (2.6.28-rc6-00007-ged31348 #137)
Call Trace:
  __blkdev_put
  swsusp_write
  hibernate
  state_store
  state_store
  state_store
  kobj_attr_store
  sysfs_write_file
  sysfs_write_file
  vfs_write
  sys_write
  sysenter_do_call
  down_write
Code: ......
EIP: [<...>] iput
---[ end trace ........................... ]---

About the following:
Tainted: G         W

I checked my logs and could not find any warning backtraces in them so I'm not sure why W is there.

[1] http://lkml.org/lkml/2008/11/20/146