[lkml]   [2006]   [Dec]   [4]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: 2.6.19-rc6-mm2
On Wednesday November 29, wrote:
> On Tue, 28 Nov 2006, Andrew Morton wrote:
> >
> >
> md-change-lifetime-rules-for-md-devices.patch gives me the following early
> during boot (first WARNING() inside __mutex_lock_slowpath(), then BUG at
> __mutex_lock_slowpath(), just after that slab corruption).
> When I revert md-change-lifetime-rules-for-md-devices.patch, everything
> seems to go fine (this machine does use neither LVM nor RAID, but the
> kernel has DM compiled in).
> Config is at
> WARNING at kernel/mutex.c:132 __mutex_lock_common()
> [<c0103d70>] dump_trace+0x68/0x1b5
> [<c0103ed5>] show_trace_log_lvl+0x18/0x2c
> [<c010445b>] show_trace+0xf/0x11
> [<c01044cd>] dump_stack+0x12/0x14
> [<c036e6ba>] __mutex_lock_slowpath+0xa1/0x213
> [<c0197c7d>] create_dir+0x24/0x1ba
> [<c0198317>] sysfs_create_dir+0x45/0x5f
> [<c01ed1fb>] kobject_add+0xce/0x185
> [<c01ed3c3>] kobject_register+0x19/0x30
> [<c02e10c6>] md_probe+0x11a/0x124

Very odd.

md_probe is registering a kobject presenting md specific stuff and
that creates a directory called 'md' inside the block device. e.g.
The inode for /sys/block/md0 appear to be non-existent at this point,
which as you are seeing poisoned memory where the inode should be.
This shouldn't happen and I cannot reproduce it.

I notice it says:
> 090: 6b 6b 6b 6b 6a 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b
> Single bit error detected. Probably bad RAM.
> Run memtest86+ or a similar memory test tool.

Have you tried running memtest86 ??

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2006-12-05 02:35    [W:0.165 / U:3.432 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site