kernel BUG at fs/block_dev.c:765!
in [Kernel]
|
Prev: [PATCH] Kbuild: Add option to set -femit-struct-debug-baseonly
Next: [PATCH 1/5] drivers/regulator: Remove dead CONFIG_TWL4030_ALLOW_UNSUPPORTED
From: Markus Trippelsdorf on 14 Jul 2010 10:00 My machine just hanged (while browsing the web). After reboot I've found this in the logs: Jul 14 15:29:13 arch kernel: ------------[ cut here ]------------ Jul 14 15:29:13 arch kernel: kernel BUG at fs/block_dev.c:765! Jul 14 15:29:13 arch kernel: invalid opcode: 0000 [#1] SMP Jul 14 15:29:13 arch kernel: last sysfs file: /sys/devices/virtual/vc/vcsa9/uevent Jul 14 15:29:13 arch kernel: CPU 0 Jul 14 15:29:13 arch kernel: Pid: 10176, comm: mount Not tainted 2.6.35-rc5-00006-gc9cc066 #26 M4A78T-E/System Product Name Jul 14 15:29:13 arch kernel: RIP: 0010:[<ffffffff810f66bf>] [<ffffffff810f66bf>] __bd_abort_claiming+0x17/0x40 Jul 14 15:29:13 arch kernel: RSP: 0018:ffff8800c9109d18 EFLAGS: 00010207 Jul 14 15:29:13 arch kernel: RAX: 000000000000c3c3 RBX: ffff88012fb65380 RCX: 0000000000000002 Jul 14 15:29:13 arch kernel: RDX: 0000000000000003 RSI: ffffffff8182f060 RDI: ffff88012fb65380 Jul 14 15:29:13 arch kernel: RBP: ffff8800c9109d28 R08: ffff8800c9109b68 R09: ffffffff81877e68 Jul 14 15:29:13 arch kernel: R10: ffff8800c9109cb8 R11: 0000000000000010 R12: ffff88012fb65380 Jul 14 15:29:13 arch kernel: R13: 0000000000000001 R14: ffffffff8182f060 R15: 00000000ffffff85 Jul 14 15:29:13 arch kernel: FS: 00007fd86f721740(0000) GS:ffff880001a00000(0000) knlGS:0000000000000000 Jul 14 15:29:13 arch kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b Jul 14 15:29:13 arch kernel: CR2: 00007ffce705e000 CR3: 000000001051d000 CR4: 00000000000006f0 Jul 14 15:29:13 arch kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 Jul 14 15:29:13 arch kernel: DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400 Jul 14 15:29:13 arch kernel: Process mount (pid: 10176, threadinfo ffff8800c9108000, task ffff88012ef82c20) Jul 14 15:29:13 arch kernel: Stack: Jul 14 15:29:13 arch kernel: ffff8800c9109d28 ffffffffffffff85 ffff8800c9109d68 ffffffff810f7b64 Jul 14 15:29:13 arch kernel: <0> ffff8800c9109d98 0000000000000001 ffffffff8182f060 0000000000000001 Jul 14 15:29:13 arch kernel: <0> ffff8800cbfec000 ffffffff8182f060 ffff8800c9109de8 ffffffff810d3da2 Jul 14 15:29:13 arch kernel: Call Trace: Jul 14 15:29:13 arch kernel: [<ffffffff810f7b64>] open_bdev_exclusive+0xb3/0xc3 Jul 14 15:29:13 arch kernel: [<ffffffff810d3da2>] get_sb_bdev+0x47/0x178 Jul 14 15:29:13 arch kernel: [<ffffffff81131214>] ? ext4_fill_super+0x0/0x208d Jul 14 15:29:13 arch kernel: [<ffffffff8112e6b2>] ext4_get_sb+0x18/0x1a Jul 14 15:29:13 arch kernel: [<ffffffff810d40a7>] vfs_kern_mount+0x62/0xff Jul 14 15:29:13 arch kernel: [<ffffffff810d4313>] do_kern_mount+0x4d/0xef Jul 14 15:29:13 arch kernel: [<ffffffff810e86a5>] do_mount+0x6cb/0x744 Jul 14 15:29:13 arch kernel: [<ffffffff810e87f3>] sys_mount+0x8c/0xcd Jul 14 15:29:13 arch kernel: [<ffffffff8102b93b>] system_call_fastpath+0x16/0x1b Jul 14 15:29:13 arch kernel: Code: c7 c3 f4 ff ff ff 5e 5f 48 89 d8 5b 41 5c 41 5d 41 5e c9 c3 55 48 89 e5 53 48 83 ec 08 e8 0a 50 f3 ff 48 39 77 50 48 89 fb 74 02 <0f> 0b 48 c7 47 50 00 00 00 00 48 8d 7f 50 31 f6 e8 8b ad f7 ff Jul 14 15:29:13 arch kernel: RIP [<ffffffff810f66bf>] __bd_abort_claiming+0x17/0x40 Jul 14 15:29:13 arch kernel: RSP <ffff8800c9109d18> Jul 14 15:29:13 arch kernel: ---[ end trace e3e601b81dcec19b ]--- -- Markus -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
From: Markus Trippelsdorf on 23 Jul 2010 09:40 On Fri, Jul 23, 2010 at 01:47:36PM +0200, Rafael J. Wysocki wrote: > This message has been generated automatically as a part of a summary report > of recent regressions. > > The following bug entry is on the current list of known regressions > from 2.6.34. Please verify if it still should be listed and let the tracking team > know (either way). It happend again today: .... Jul 23 09:22:00 arch kernel: r8169 0000:02:05.0: eth0: link up Jul 23 09:22:00 arch kernel: r8169: WARNING! Changing of MTU on this NIC may lead to frame reception errors! Jul 23 13:41:43 arch kernel: ------------[ cut here ]------------ Jul 23 13:41:43 arch kernel: kernel BUG at fs/block_dev.c:765! Jul 23 13:41:43 arch kernel: invalid opcode: 0000 [#1] SMP Jul 23 13:41:43 arch kernel: last sysfs file: /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_max_freq Jul 23 13:41:43 arch kernel: CPU 1 Jul 23 13:41:43 arch kernel: Pid: 2616, comm: mount Not tainted 2.6.35-rc6-00012-g7e5a57e #32 M4A78T-E/System Product Name Jul 23 13:41:43 arch kernel: RIP: 0010:[<ffffffff810f66c7>] [<ffffffff810f66c7>] __bd_abort_claiming+0x17/0x40 Jul 23 13:41:43 arch kernel: RSP: 0018:ffff880035d07d18 EFLAGS: 00010207 Jul 23 13:41:43 arch kernel: RAX: 0000000000009292 RBX: ffff88011f8249c0 RCX: 0000000000000002 Jul 23 13:41:43 arch kernel: RDX: 0000000000000003 RSI: ffffffff8182f0a0 RDI: ffff88011f8249c0 Jul 23 13:41:43 arch kernel: RBP: ffff880035d07d28 R08: ffff880035d07b68 R09: ffffffff81877ea8 Jul 23 13:41:43 arch kernel: R10: ffff880035d07cb8 R11: 0000000000000010 R12: ffff88011f8249c0 Jul 23 13:41:43 arch kernel: R13: 0000000000000001 R14: ffffffff8182f0a0 R15: 00000000ffffff85 Jul 23 13:41:43 arch kernel: FS: 00007f727e6a8740(0000) GS:ffff880001a80000(0000) knlGS:0000000000000000 Jul 23 13:41:43 arch kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b Jul 23 13:41:43 arch kernel: CR2: 00007f99480f2000 CR3: 000000003c34d000 CR4: 00000000000006e0 Jul 23 13:41:43 arch kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 Jul 23 13:41:43 arch kernel: DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400 Jul 23 13:41:43 arch kernel: Process mount (pid: 2616, threadinfo ffff880035d06000, task ffff88011afe0000) Jul 23 13:41:43 arch kernel: Stack: Jul 23 13:41:43 arch kernel: ffff880035d07d28 ffffffffffffff85 ffff880035d07d68 ffffffff810f7b6c Jul 23 13:41:43 arch kernel: <0> ffff880035d07d98 0000000000000001 ffffffff8182f0a0 0000000000000001 Jul 23 13:41:43 arch kernel: <0> ffff88003c3c5000 ffffffff8182f0a0 ffff880035d07de8 ffffffff810d3daa Jul 23 13:41:43 arch kernel: Call Trace: Jul 23 13:41:43 arch kernel: [<ffffffff810f7b6c>] open_bdev_exclusive+0xb3/0xc3 Jul 23 13:41:43 arch kernel: [<ffffffff810d3daa>] get_sb_bdev+0x47/0x178 Jul 23 13:41:43 arch kernel: [<ffffffff8113121c>] ? ext4_fill_super+0x0/0x208d Jul 23 13:41:43 arch kernel: [<ffffffff8112e6ba>] ext4_get_sb+0x18/0x1a Jul 23 13:41:43 arch kernel: [<ffffffff810d40af>] vfs_kern_mount+0x62/0xff Jul 23 13:41:43 arch kernel: [<ffffffff810d431b>] do_kern_mount+0x4d/0xef Jul 23 13:41:43 arch kernel: [<ffffffff810e86ad>] do_mount+0x6cb/0x744 Jul 23 13:41:43 arch kernel: [<ffffffff810e87fb>] sys_mount+0x8c/0xcd Jul 23 13:41:43 arch kernel: [<ffffffff8102b93b>] system_call_fastpath+0x16/0x1b Jul 23 13:41:43 arch kernel: Code: c7 c3 f4 ff ff ff 5Jul 23 13:42:38 arch kernel: Linux version 2.6.35-rc6-00012-g7e5a57e (markus(a)arch.tripp.de) (gcc version 4.5.0 20100610 (prerelease) (GCC) ) #32 SMP Fri Jul 23 09:21:31 CEST 2010 Jul 23 13:42:38 arch kernel: Command line: BOOT_IMAGE=/usr/src/linux/arch/x86/boot/bzImage root=/dev/sdb2 fbcon=rotate:3 drm.edid_force_checksum=1 quiet Jul 23 13:42:38 arch kernel: BIOS-provided physical RAM map: -- Markus -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
From: Justin P. Mattock on 23 Jul 2010 09:50
On 07/23/2010 06:33 AM, Markus Trippelsdorf wrote: > On Fri, Jul 23, 2010 at 01:47:36PM +0200, Rafael J. Wysocki wrote: >> This message has been generated automatically as a part of a summary report >> of recent regressions. >> >> The following bug entry is on the current list of known regressions >> from 2.6.34. Please verify if it still should be listed and let the tracking team >> know (either way). > > It happend again today: > > ... > Jul 23 09:22:00 arch kernel: r8169 0000:02:05.0: eth0: link up > Jul 23 09:22:00 arch kernel: r8169: WARNING! Changing of MTU on this NIC may lead to frame reception errors! > Jul 23 13:41:43 arch kernel: ------------[ cut here ]------------ > Jul 23 13:41:43 arch kernel: kernel BUG at fs/block_dev.c:765! > Jul 23 13:41:43 arch kernel: invalid opcode: 0000 [#1] SMP > Jul 23 13:41:43 arch kernel: last sysfs file: /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_max_freq > Jul 23 13:41:43 arch kernel: CPU 1 > Jul 23 13:41:43 arch kernel: Pid: 2616, comm: mount Not tainted 2.6.35-rc6-00012-g7e5a57e #32 M4A78T-E/System Product Name > Jul 23 13:41:43 arch kernel: RIP: 0010:[<ffffffff810f66c7>] [<ffffffff810f66c7>] __bd_abort_claiming+0x17/0x40 > Jul 23 13:41:43 arch kernel: RSP: 0018:ffff880035d07d18 EFLAGS: 00010207 > Jul 23 13:41:43 arch kernel: RAX: 0000000000009292 RBX: ffff88011f8249c0 RCX: 0000000000000002 > Jul 23 13:41:43 arch kernel: RDX: 0000000000000003 RSI: ffffffff8182f0a0 RDI: ffff88011f8249c0 > Jul 23 13:41:43 arch kernel: RBP: ffff880035d07d28 R08: ffff880035d07b68 R09: ffffffff81877ea8 > Jul 23 13:41:43 arch kernel: R10: ffff880035d07cb8 R11: 0000000000000010 R12: ffff88011f8249c0 > Jul 23 13:41:43 arch kernel: R13: 0000000000000001 R14: ffffffff8182f0a0 R15: 00000000ffffff85 > Jul 23 13:41:43 arch kernel: FS: 00007f727e6a8740(0000) GS:ffff880001a80000(0000) knlGS:0000000000000000 > Jul 23 13:41:43 arch kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b > Jul 23 13:41:43 arch kernel: CR2: 00007f99480f2000 CR3: 000000003c34d000 CR4: 00000000000006e0 > Jul 23 13:41:43 arch kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 > Jul 23 13:41:43 arch kernel: DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400 > Jul 23 13:41:43 arch kernel: Process mount (pid: 2616, threadinfo ffff880035d06000, task ffff88011afe0000) > Jul 23 13:41:43 arch kernel: Stack: > Jul 23 13:41:43 arch kernel: ffff880035d07d28 ffffffffffffff85 ffff880035d07d68 ffffffff810f7b6c > Jul 23 13:41:43 arch kernel:<0> ffff880035d07d98 0000000000000001 ffffffff8182f0a0 0000000000000001 > Jul 23 13:41:43 arch kernel:<0> ffff88003c3c5000 ffffffff8182f0a0 ffff880035d07de8 ffffffff810d3daa > Jul 23 13:41:43 arch kernel: Call Trace: > Jul 23 13:41:43 arch kernel: [<ffffffff810f7b6c>] open_bdev_exclusive+0xb3/0xc3 > Jul 23 13:41:43 arch kernel: [<ffffffff810d3daa>] get_sb_bdev+0x47/0x178 > Jul 23 13:41:43 arch kernel: [<ffffffff8113121c>] ? ext4_fill_super+0x0/0x208d > Jul 23 13:41:43 arch kernel: [<ffffffff8112e6ba>] ext4_get_sb+0x18/0x1a > Jul 23 13:41:43 arch kernel: [<ffffffff810d40af>] vfs_kern_mount+0x62/0xff > Jul 23 13:41:43 arch kernel: [<ffffffff810d431b>] do_kern_mount+0x4d/0xef > Jul 23 13:41:43 arch kernel: [<ffffffff810e86ad>] do_mount+0x6cb/0x744 > Jul 23 13:41:43 arch kernel: [<ffffffff810e87fb>] sys_mount+0x8c/0xcd > Jul 23 13:41:43 arch kernel: [<ffffffff8102b93b>] system_call_fastpath+0x16/0x1b > Jul 23 13:41:43 arch kernel: Code: c7 c3 f4 ff ff ff 5Jul 23 13:42:38 arch kernel: Linux version 2.6.35-rc6-00012-g7e5a57e (markus(a)arch.tripp.de) (gcc version 4.5.0 20100610 (prerelease) (GCC) ) #32 SMP Fri Jul 23 09:21:31 CEST 2010 > Jul 23 13:42:38 arch kernel: Command line: BOOT_IMAGE=/usr/src/linux/arch/x86/boot/bzImage root=/dev/sdb2 fbcon=rotate:3 drm.edid_force_checksum=1 quiet > Jul 23 13:42:38 arch kernel: BIOS-provided physical RAM map: o.k. so im not going insane then... problem over here is the machine is responding as if nothing like that occurs. atheros has one of these as well(like I posted) how to reproduce such a beast of a bug... Justin P. Mattock -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ |