Bug 599411 - WARNING: at fs/fs-writeback.c:589 writeback_inodes_wb+0x1d0/0x3ca()
Summary: WARNING: at fs/fs-writeback.c:589 writeback_inodes_wb+0x1d0/0x3ca()
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 14
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-06-03 07:49 UTC by Andreas Wallberg
Modified: 2011-08-30 18:33 UTC (History)
7 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2011-08-30 18:33:35 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Andreas Wallberg 2010-06-03 07:49:06 UTC
Description of problem:

Kernel oopses but never crashes. Seems related to filesystem interaction but I do not know at what level. I am running btrfs on / and /home in two LUKS/dm-crypt partitions

Version-Release number of selected component (if applicable):

This has been happening in the 2.6.34 kernel in Rawhide from version 2.6.34-2 to 2.6.34-11 (current).

How reproducible:

From what I can tell, it pretty much just happens during day-to-day activities. However, it has a tendency to occur frequently when resuming from suspend on my Thinkpad laptop. I have seven of these oopses in ABRT since 20th of May but think I had a few more before that as well.

Steps to Reproduce:

Resuming from suspend is the best bet.
  
Additional info:

This looks pretty similar to Bug 593669 in Bugzilla.

Comment 1 Bug Zapper 2010-07-30 11:47:55 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 14 development cycle.
Changing version to '14'.

More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 2 Josh Boyer 2011-08-30 18:33:35 UTC
Bug is a year old and has no usable information to help debug.  If you can recreate this on f15 or f16, please open a new bug.


Note You need to log in before you can comment on or make changes to this bug.