kernel BUG at /build/buildd/linux-ec2-2.6.32/fs/ext4/inode.c:1852!

Bug #586530 reported by brenden
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux-ec2 (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

There is a report for this same issue on the kernel bugzilla, including a patch at: https://bugzilla.kernel.org/show_bug.cgi?id=15231

This bug manifests in the affected partition becoming locked/inaccessible.

I have not yet tested the patch in the bug report above, but I'm working on it. System log is as follows:

Ubuntu 10.04 LTS domU-12-31-38-06-F4-02 tty1

domU-12-31-38-06-F4-02 login: [ 134.802484] ------------[ cut here ]------------

[ 134.802502] kernel BUG at /build/buildd/linux-ec2-2.6.32/fs/ext4/inode.c:1852!

[ 134.802508] invalid opcode: 0000 [#1] SMP

[ 134.802514] last sysfs file: /sys/kernel/uevent_seqnum

[ 134.802517] CPU 0

[ 134.802520] Modules linked in: ipv6

[ 134.802526] Pid: 1099, comm: ruby Not tainted 2.6.32-305-ec2 #9-Ubuntu

[ 134.802530] RIP: e030:[<ffffffff811cb6dc>] [<ffffffff811cb6dc>] T.1072+0x20c/0x210

[ 134.802542] RSP: e02b:ffff8801c59d5b38 EFLAGS: 00010297

[ 134.802546] RAX: 0000000000000018 RBX: ffff8801b4b5d0e0 RCX: 0000000000000154

[ 134.802550] RDX: 0000000000000019 RSI: 0000000000000018 RDI: 0000000000000153

[ 134.802554] RBP: ffff8801c59d5b88 R08: 0000000000000000 R09: 0000000000000000

[ 134.802558] R10: 0000000000000000 R11: 0000000000000000 R12: ffff8801b4b5d3a8

[ 134.802562] R13: ffff8801b4b5d0e0 R14: ffff8801b4b5d040 R15: 0000000000000018

[ 134.802571] FS: 00007fb608570710(0000) GS:ffff88000183c000(0000) knlGS:0000000000000000

[ 134.802575] CS: e033 DS: 0000 ES: 0000 CR0: 0000000080050033

[ 134.802579] CR2: 00007fb607246000 CR3: 00000001cd643000 CR4: 0000000000002660

[ 134.802583] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000

[ 134.802587] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000000

[ 134.802592] Process ruby (pid: 1099, threadinfo ffff8801c59d4000, task ffff8801c9daa280)

[ 134.802596] Stack:

[ 134.802599] ffff880100000000 ffff8801dc014400 0000000000000000 0000000000001d48

[ 134.802605] <0> ffff880008f4c8e8 ffff880199d4c130 ffffffffffff0000 ffff8801b4b5d0e0

[ 134.802613] <0> 0000000000001d48 0000000000000000 ffff8801c59d5bb8 ffffffff811cdcb0

[ 134.802621] Call Trace:

[ 134.802627] [<ffffffff811cdcb0>] ext4_da_get_block_prep+0xc0/0x100

[ 134.802633] [<ffffffff8111987c>] __block_prepare_write+0x1ac/0x580

[ 134.802638] [<ffffffff811cdbf0>] ? ext4_da_get_block_prep+0x0/0x100

[ 134.802644] [<ffffffff810ada09>] ? find_get_page+0x19/0xa0

[ 134.802648] [<ffffffff81119ddf>] block_write_begin+0x5f/0x100

[ 134.802653] [<ffffffff811d01ad>] ext4_da_write_begin+0x12d/0x260

[ 134.802658] [<ffffffff811cdbf0>] ? ext4_da_get_block_prep+0x0/0x100

[ 134.802663] [<ffffffff811ca6cf>] ext4_page_mkwrite+0x12f/0x190

[ 134.802668] [<ffffffff810cb285>] __do_fault+0xb5/0x680

[ 134.802672] [<ffffffff810cd160>] handle_mm_fault+0x260/0x4f0

[ 134.802678] [<ffffffff814a5fd7>] do_page_fault+0x147/0x390

[ 134.802683] [<ffffffff814a3e18>] page_fault+0x28/0x30

[ 134.802686] Code: 48 83 c4 28 31 c0 5b 41 5c 41 5d 41 5e 41 5f c9 c3 66 0f 1f 44 00 00 48 83 c4 28 b8 e4 ff ff ff 5b 41 5c 41 5d 41 5e 41 5f c9 c3 <0f> 0b eb fe 55 48 89 e5 48 83 ec 40 85 f6 48 89 5d d8 4c 89 65

[ 134.802742] RIP [<ffffffff811cb6dc>] T.1072+0x20c/0x210

[ 134.802747] RSP <ffff8801c59d5b38>

[ 134.802811] ---[ end trace 1f2cf7670a0a024e ]---

Tags: ec2-images
Revision history for this message
brenden (brenden) wrote :

Oh nice, I can't replace the kernel on EC2.

Scott Moser (smoser)
tags: added: ec2-images
Revision history for this message
brenden (brenden) wrote :

I should mention that I resolved this issue by NOT using EC2.

Revision history for this message
Stefan Bader (smb) wrote :

I am closing this for now as invalid for two reasons: first both the upstream bug report and this one seem to be stalled and second, since this was reported, there was a big set of stable updates that went into 2.6.32.y and then into the ec2 kernels as well. So the chances are quite high that this just does not happen anymore. Please feel free to re-open should I be wrong.

Changed in linux-ec2 (Ubuntu):
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.