Bug 31742 - got a "kernel BUG at fs/dcache.c:440!"
Summary: got a "kernel BUG at fs/dcache.c:440!"
Status: RESOLVED OBSOLETE
Alias: None
Product: File System
Classification: Unclassified
Component: ext4 (show other bugs)
Hardware: x86-64 Linux
: P1 normal
Assignee: fs_ext4@kernel-bugs.osdl.org
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-03-23 15:14 UTC by Mathias Rüdiger
Modified: 2012-08-20 15:14 UTC (History)
2 users (show)

See Also:
Kernel Version: 2.6.38
Subsystem:
Regression: No
Bisected commit-id:


Attachments
Picture of the Message (131.51 KB, image/jpeg)
2011-03-23 15:15 UTC, Mathias Rüdiger
Details
Python script used (1.03 KB, text/plain)
2011-03-23 15:18 UTC, Mathias Rüdiger
Details
kernel config (2.6.38+) (74.03 KB, text/plain)
2011-03-23 15:20 UTC, Mathias Rüdiger
Details

Description Mathias Rüdiger 2011-03-23 15:14:29 UTC
While traversing /usr with a python script, i got a message saying "kernel BUG". Its the first time i got something like this in the last 12 years using linux, so i guessed, i should report it. The message is attached as a jpeg.

so long
Mathias
Comment 1 Mathias Rüdiger 2011-03-23 15:15:41 UTC
Created attachment 51752 [details]
Picture of the Message
Comment 2 Mathias Rüdiger 2011-03-23 15:18:02 UTC
Created attachment 51762 [details]
Python script used
Comment 3 Mathias Rüdiger 2011-03-23 15:20:22 UTC
Created attachment 51772 [details]
kernel config (2.6.38+)
Comment 4 Theodore Tso 2011-03-23 19:31:19 UTC
Can you replicate the problem, or was this a once-off?

Can you say more about your hardware configuration?  Was this on an SMP machine?

Looking at the stack trace, this looks more like a VFS level issue than something within ext4. 

-- Ted
Comment 5 Mathias Rüdiger 2011-03-23 23:45:49 UTC
Yes i can replicate the problem. Start the script, wait a second and off you go.

I am using a Thinkpad X61 Tablet (http://www.thinkwiki.org/wiki/Category:X61_Tablet) with Intels L7300. Its a SMP machine. 

I also thought that fs/dcache.c isn't ext4 specific, but i didn't know where to put the bugreport.


Mathias
Comment 6 Mathias Rüdiger 2011-03-24 08:51:46 UTC
Just checked the script on my other machine. The error didn't occurred there.

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