Another one, with the process running on a btrfs chroot instead of tmpfs:
[12350.410412] [ cut here ]
[12350.420001] kernel BUG at /home/kernel-ppa/COD/linux/fs/btrfs/inode.c:1759!
[12350.420001] invalid opcode: [#1] SMP
[12350.420001] last sysfs file:
/sys/devices/pc
On 31/01/11 14:11, cwillu wrote:
> There's a bunch of places it could be (any ret = foo
> followed by a break will exit with that ret rather
> than oops).
Ahh, thanks for that, I plead being a sysadmin rather than
a programmer.. ;-)
--
Chris Samuel : http://www.csamuel.org/ : Melbourne, VI
On Sun, Jan 30, 2011 at 8:57 PM, Chris Samuel wrote:
> On 31/01/11 12:33, cwillu wrote:
>
>> [33159.490003] kernel BUG at
>> /home/kernel-ppa/COD/linux/fs/btrfs/inode.c:1629!
>
> It looks like this happens when btrfs_drop_extents() returns
> an error, and in the code the only time that seems to h
On 31/01/11 12:33, cwillu wrote:
> [33159.490003] kernel BUG at /home/kernel-ppa/COD/linux/fs/btrfs/inode.c:1629!
It looks like this happens when btrfs_drop_extents() returns
an error, and in the code the only time that seems to happen
without already calling BUG_ON() is if it runs out of memory
And again, without the USB devices.
This time was under a vanilla 2.6.38rc2 build, rootfs is a 4-drive
btrfs raid10 connected internally via sata, and no other drives in the
picture.
The btrfs drives are sda5, sdb1, sdc1 and sdd1; sda1 is /boot, sda2
is swap, sda3 is a 4gb ext4 with a small inst
On Tue, Jan 18, 2011 at 4:28 PM, cwillu wrote:
> While untar'ing an image to an sd card via a reader, I got the
> following bug. The system also has a btrfs root, and a whole swath of
> processes went into uninterruptable sleep. I was able to poke around
> via ssh and sysrq, and already had netc
While untar'ing an image to an sd card via a reader, I got the
following bug. The system also has a btrfs root, and a whole swath of
processes went into uninterruptable sleep. I was able to poke around
via ssh and sysrq, and already had netconsole set up to capture the
bug.
Root fs is on /dev/sd
