Leonidas Spyropoulos
2011-Oct-22 20:23 UTC
Kernel BUG unable to handle kernel NULL pointer dereference
Hello, I got a kernel bug error, my guess from BTRFS. Here is the report, Oct 22 20:44:43 localhost kernel: [25554.947970] BUG: unable to handle kernel NULL pointer dereference at 0000000000000030 Oct 22 20:44:43 localhost kernel: [25554.948002] IP: [<ffffffffa01ab027>] btrfs_print_leaf+0x37/0x880 [btrfs] Oct 22 20:44:43 localhost kernel: [25554.948037] PGD bfa44067 PUD bfa43067 PMD 0 Oct 22 20:44:43 localhost kernel: [25554.948052] Oops: 0000 [#1] PREEMPT SMP Oct 22 20:44:43 localhost kernel: [25554.948066] CPU 1 Oct 22 20:44:43 localhost kernel: [25554.948072] Modules linked in: nls_cp437 vfat fat ipv6 loop fuse hid_apple usbhid hid uvcvideo videodev media v4l2_compat_ioctl32 adt7475 hwmon_vid evdev nouveau snd_emu10k1 snd_rawmidi snd_intel8x0 ttm drm_kms_helper sg snd_ac97_codec snd_seq_device firewire_ohci drm snd_util_mem ac97_bus snd_pcm snd_hwdep edac_core k8temp psmouse firewire_core emu10k1_gp snd_timer edac_mce_amd pcspkr snd i2c_algo_bit gameport mxm_wmi wmi crc_itu_t serio_raw soundcore video snd_page_alloc fan i2c_nforce2 thermal i2c_core floppy processor button uas usb_storage forcedeth btrfs zlib_deflate crc32c libcrc32c ext4 jbd2 crc16 ext3 jbd mbcache ohci_hcd ehci_hcd usbcore sr_mod sd_mod cdrom sata_nv pata_amd libata scsi_mod Oct 22 20:44:43 localhost kernel: [25554.948321] Oct 22 20:44:43 localhost kernel: [25554.948327] Pid: 4834, comm: firefox Not tainted 3.0-ARCH #1 /LP UT NF4 Expert Oct 22 20:44:43 localhost kernel: [25554.948522] RIP: 0010:[<ffffffffa01ab027>] [<ffffffffa01ab027>] btrfs_print_leaf+0x37/0x880 [btrfs] Oct 22 20:44:43 localhost kernel: [25554.948547] RSP: 0018:ffff8800b341fb38 EFLAGS: 00010282 Oct 22 20:44:43 localhost kernel: [25554.948557] RAX: 00000000ffffffe4 RBX: 0000000000000000 RCX: ffff8800b341ffd8 Oct 22 20:44:43 localhost kernel: [25554.948570] RDX: ffff8800b341e000 RSI: 0000000000000000 RDI: ffff880135075000 Oct 22 20:44:43 localhost kernel: [25554.948582] RBP: ffff8800b341fbc8 R08: ffffffffffffffff R09: 0000000000000000 Oct 22 20:44:43 localhost kernel: [25554.948595] R10: 00000000ffffffe4 R11: 0000000000000000 R12: 0000000000000005 Oct 22 20:44:43 localhost kernel: [25554.948607] R13: 0000000005114000 R14: 00000000ffffffe4 R15: 0000000000001000 Oct 22 20:44:43 localhost kernel: [25554.948621] FS: 00007f1c5a2f4720(0000) GS:ffff88013fd00000(0000) knlGS:00000000f68227f0 Oct 22 20:44:43 localhost kernel: [25554.948634] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Oct 22 20:44:43 localhost kernel: [25554.948645] CR2: 0000000000000030 CR3: 00000000bfa41000 CR4: 00000000000006e0 Oct 22 20:44:43 localhost kernel: [25554.948658] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 Oct 22 20:44:43 localhost kernel: [25554.948670] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400 Oct 22 20:44:43 localhost kernel: [25554.948683] Process firefox (pid: 4834, threadinfo ffff8800b341e000, task ffff88012d817300) Oct 22 20:44:43 localhost kernel: [25554.948701] Stack: Oct 22 20:44:43 localhost kernel: [25554.948708] 0000000000002000 0000000000001000 ffff8800b341fc70 0000000005114000 Oct 22 20:44:43 localhost kernel: [25554.948730] 0000000000000282 ffffffff81142c03 ffff880135075000 0000000000000090 Oct 22 20:44:43 localhost kernel: [25554.948755] 0000000000000090 0000805037106510 a800000000051140 0000000000001000 Oct 22 20:44:43 localhost kernel: [25554.948777] Call Trace: Oct 22 20:44:43 localhost kernel: [25554.948787] [<ffffffff81142c03>] ? kmem_cache_alloc+0x133/0x160 Oct 22 20:44:43 localhost kernel: [25554.948807] [<ffffffffa01a32df>] __btrfs_free_extent+0x61f/0x6d0 [btrfs] Oct 22 20:44:43 localhost kernel: [25554.948827] [<ffffffffa01a5b6d>] ? run_clustered_refs+0x11d/0x830 [btrfs] Oct 22 20:44:43 localhost kernel: [25554.948847] [<ffffffffa01a5dd9>] run_clustered_refs+0x389/0x830 [btrfs] Oct 22 20:44:43 localhost kernel: [25554.948867] [<ffffffffa01a6348>] btrfs_run_delayed_refs+0xc8/0x220 [btrfs] Oct 22 20:44:43 localhost kernel: [25554.948881] [<ffffffff813f29ce>] ? mutex_unlock+0xe/0x10 Oct 22 20:44:43 localhost kernel: [25554.948900] [<ffffffffa01b8381>] btrfs_commit_transaction+0x81/0x8a0 [btrfs] Oct 22 20:44:43 localhost kernel: [25554.948915] [<ffffffff8107f790>] ? abort_exclusive_wait+0xb0/0xb0 Oct 22 20:44:43 localhost kernel: [25554.948928] [<ffffffff8116e6be>] ? dput+0x10e/0x1a0 Oct 22 20:44:43 localhost kernel: [25554.948948] [<ffffffffa01c6ac4>] btrfs_sync_file+0x194/0x1e0 [btrfs] Oct 22 20:44:43 localhost kernel: [25554.948961] [<ffffffff8118321f>] vfs_fsync_range+0x5f/0xa0 Oct 22 20:44:43 localhost kernel: [25554.948973] [<ffffffff811832cc>] vfs_fsync+0x1c/0x20 Oct 22 20:44:43 localhost kernel: [25554.948984] [<ffffffff811835e3>] sys_fsync+0x33/0x50 Oct 22 20:44:43 localhost kernel: [25554.948995] [<ffffffff813f4c42>] system_call_fastpath+0x16/0x1b Oct 22 20:44:43 localhost kernel: [25554.949008] Code: 89 5d d8 4c 89 65 e0 4c 89 6d e8 4c 89 75 f0 4c 89 7d f8 66 66 66 66 90 65 48 8b 0c 25 48 cd 00 00 48 8d 91 28 e0 ff ff 48 89 f3 Oct 22 20:44:43 localhost kernel: [25554.949269] RIP [<ffffffffa01ab027>] btrfs_print_leaf+0x37/0x880 [btrfs] Oct 22 20:44:43 localhost kernel: [25554.949292] RSP <ffff8800b341fb38> Oct 22 20:44:43 localhost kernel: [25554.949300] CR2: 0000000000000030 Oct 22 20:44:43 localhost kernel: [25554.957960] ---[ end trace e3b54094ec35959e ]--- Anyone stumble upon it? After this a couple of BUG dumps followed, check this pastebin http://paste.pocoo.org/show/496620/ I am a on a Arch system with BTRFS root filesystem $ pacman -Si linux Repository : core Name : linux Version : 3.0.7-1 URL : http://www.kernel.org/ Licenses : GPL2 Groups : base Provides : kernel26 Depends On : coreutils linux-firmware module-init-tools>=3.16 mkinitcpio>=0.7 Optional Deps : crda: to set the correct wireless channels of your country Conflicts With : kernel26 Replaces : kernel26 Download Size : 38639.75 K Installed Size : 57060.00 K Packager : Tobias Powalowski <tpowa@archlinux.org> Architecture : x86_64 Build Date : Wed 19 Oct 2011 09:31:33 AM BST MD5 Sum : 1fa49419794d5b4c04fdd0b275f6649b Description : The Linux Kernel and modules btrfs-tools : Btrfs v0.19-85-gd4bb086 I am on an SSD drive. My mounts are like: /dev/sda2 on / type btrfs (rw,noatime,ssd) /dev/sda3 on /home type btrfs (rw,noatime,ssd) Regards Leonidas -- Caution: breathing may be hazardous to your health. -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Mitch Harder
2011-Oct-23 15:37 UTC
Re: Kernel BUG unable to handle kernel NULL pointer dereference
On Sat, Oct 22, 2011 at 3:23 PM, Leonidas Spyropoulos <artafinde@gmail.com> wrote:> Hello, I got a kernel bug error, my guess from BTRFS. > > Here is the report, > Oct 22 20:44:43 localhost kernel: [25554.947970] BUG: unable to handle > kernel NULL pointer dereference at 0000000000000030 > Oct 22 20:44:43 localhost kernel: [25554.948002] IP: > [<ffffffffa01ab027>] btrfs_print_leaf+0x37/0x880 [btrfs]A patch was submitted by Sergei Trofimovich to address the issue with handling a NULL pointer in btrfs_print_leaf. http://www.mail-archive.com/linux-btrfs@vger.kernel.org/msg12021.html Unfortunately, this usually only crops up when btrfs runs into corruptions that it can''t handle. So you very likely still have problems even if the btrfs_print_leaf issue isn''t addressed. -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Leonidas Spyropoulos
2011-Oct-23 18:24 UTC
Re: Kernel BUG unable to handle kernel NULL pointer dereference
On Sun, Oct 23, 2011 at 4:37 PM, Mitch Harder <mitch.harder@sabayonlinux.org> wrote:> On Sat, Oct 22, 2011 at 3:23 PM, Leonidas Spyropoulos > <artafinde@gmail.com> wrote: >> Hello, I got a kernel bug error, my guess from BTRFS. >> >> Here is the report, >> Oct 22 20:44:43 localhost kernel: [25554.947970] BUG: unable to handle >> kernel NULL pointer dereference at 0000000000000030 >> Oct 22 20:44:43 localhost kernel: [25554.948002] IP: >> [<ffffffffa01ab027>] btrfs_print_leaf+0x37/0x880 [btrfs] > > A patch was submitted by Sergei Trofimovich to address the issue with > handling a NULL pointer in btrfs_print_leaf. > > http://www.mail-archive.com/linux-btrfs@vger.kernel.org/msg12021.html > > Unfortunately, this usually only crops up when btrfs runs into > corruptions that it can''t handle. So you very likely still have > problems even if the btrfs_print_leaf issue isn''t addressed. >So from what I understand btrfs_print_leaf function is called only when something is wrong and want to print out debug information, correct? How can I track down the real problem? Any suggestions? -- Caution: breathing may be hazardous to your health. -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
David Sterba
2011-Oct-24 11:22 UTC
Re: Kernel BUG unable to handle kernel NULL pointer dereference
On Sun, Oct 23, 2011 at 07:24:42PM +0100, Leonidas Spyropoulos wrote:> On Sun, Oct 23, 2011 at 4:37 PM, Mitch Harder > <mitch.harder@sabayonlinux.org> wrote: > > A patch was submitted by Sergei Trofimovich to address the issue with > > handling a NULL pointer in btrfs_print_leaf. > > > > http://www.mail-archive.com/linux-btrfs@vger.kernel.org/msg12021.htmlafaik the patch should be enqueued for 3.2> How can I track down the real problem? Any suggestions?The preceding function in the stack was __btrfs_free_extent, there are 3 instances of btrfs_print_leaf() in that function, 2 of them relevant: 4470 printk(KERN_ERR "umm, got %d back from search" 4471 ", was looking for %llu\n", ret, 4472 (unsigned long long)bytenr); 4494 #ifdef BTRFS_COMPAT_EXTENT_TREE_V0 ... 4511 printk(KERN_ERR "umm, got %d back from search" 4512 ", was looking for %llu\n", ret, 4513 (unsigned long long)bytenr); 4514 btrfs_print_leaf(extent_root, path->nodes[0]); ... #endif and the third one without a pre-message 4481 btrfs_print_leaf(extent_root, path->nodes[0]); 4482 WARN_ON(1); 4483 printk(KERN_ERR "btrfs unable to find ref byte nr %llu " 4484 "parent %llu root %llu owner %llu offset %llu\n", 4485 (unsigned long long)bytenr, 4486 (unsigned long long)parent, 4487 (unsigned long long)root_objectid, 4488 (unsigned long long)owner_objectid, 4489 (unsigned long long)owner_offset); your original report does not contain any messages before the BUG listing, so I''m not sure which one it is. Supposed it''s the 3rd, it''s resulting from an error returned by 4429 ret = lookup_extent_backref(trans, extent_root, path, &iref, 4430 bytenr, num_bytes, parent, 4431 root_objectid, owner_objectid, 4432 owner_offset); ret != 0 -> print leaf etc, a missing backref could be the problem here. Are you able to trigger the BUG() repeatedly? david -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Leonidas Spyropoulos
2011-Oct-24 11:33 UTC
Re: Kernel BUG unable to handle kernel NULL pointer dereference
On Mon, Oct 24, 2011 at 12:22 PM, David Sterba <dsterba@suse.cz> wrote:> On Sun, Oct 23, 2011 at 07:24:42PM +0100, Leonidas Spyropoulos wrote: >> On Sun, Oct 23, 2011 at 4:37 PM, Mitch Harder >> <mitch.harder@sabayonlinux.org> wrote: >> > A patch was submitted by Sergei Trofimovich to address the issue with >> > handling a NULL pointer in btrfs_print_leaf. >> > >> > http://www.mail-archive.com/linux-btrfs@vger.kernel.org/msg12021.html > > afaik the patch should be enqueued for 3.2 > >> How can I track down the real problem? Any suggestions? > > The preceding function in the stack was __btrfs_free_extent, there are 3 > instances of btrfs_print_leaf() in that function, 2 of them relevant: > > 4470 printk(KERN_ERR "umm, got %d back from search" > 4471 ", was looking for %llu\n", ret, > 4472 (unsigned long long)bytenr); > > > 4494 #ifdef BTRFS_COMPAT_EXTENT_TREE_V0 > ... > 4511 printk(KERN_ERR "umm, got %d back from search" > 4512 ", was looking for %llu\n", ret, > 4513 (unsigned long long)bytenr); > 4514 btrfs_print_leaf(extent_root, path->nodes[0]); > ... > #endif > > and the third one without a pre-message > > 4481 btrfs_print_leaf(extent_root, path->nodes[0]); > 4482 WARN_ON(1); > 4483 printk(KERN_ERR "btrfs unable to find ref byte nr %llu " > 4484 "parent %llu root %llu owner %llu offset %llu\n", > 4485 (unsigned long long)bytenr, > 4486 (unsigned long long)parent, > 4487 (unsigned long long)root_objectid, > 4488 (unsigned long long)owner_objectid, > 4489 (unsigned long long)owner_offset); > > > your original report does not contain any messages before the BUG > listing, so I''m not sure which one it is.I got the whole log somwehre lying arround, let me find it and give a pastbin link Here is it, it''s big and contains usless information.. http://paste.pocoo.org/show/497299/> > Supposed it''s the 3rd, it''s resulting from an error returned by > > 4429 ret = lookup_extent_backref(trans, extent_root, path, &iref, > 4430 bytenr, num_bytes, parent, > 4431 root_objectid, owner_objectid, > 4432 owner_offset); > > ret != 0 -> print leaf etc, a missing backref could be the problem here. > > Are you able to trigger the BUG() repeatedly?No I cannot reproduce it intentionally, it was quite random, while playing something in the SMPlayer - think it was a movie. The movie kept playing, and I can start programs (that was on the memory I assume), couldn''t access the FS at all. ls failed for example. So I just hard-reboot and hoped all was alright. So far I didn''t see any problems after that.> > > david >Thanks for checking it Regards Leonidas -- Caution: breathing may be hazardous to your health. -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
David Sterba
2011-Oct-24 11:51 UTC
Re: Kernel BUG unable to handle kernel NULL pointer dereference
On Mon, Oct 24, 2011 at 12:33:05PM +0100, Leonidas Spyropoulos wrote:> Here is it, it''s big and contains usless information.. > > http://paste.pocoo.org/show/497299/not all that useless ... I saw another BUG earlier than the one you''ve reported: [31653.267742] ------------[ cut here ]------------ [31653.267764] kernel BUG at fs/btrfs/extent-tree.c:5510! [31653.267773] invalid opcode: 0000 [#1] PREEMPT SMP [31653.267785] CPU 1 [31653.267790] Modules linked in: vboxdrv ipv6 loop fuse adt7475 hwmon_vid nouveau evdev uvcvideo hid_apple ttm videodev drm_kms_helper media v4l2_compat_ioctl32 drm snd_emu10k1 i2c_algo_bit mxm_wmi wmi pcspkr snd_rawmidi snd_seq_device firewire_ohci emu10k1_gp edac_core psmouse snd_util_mem edac_mce_amd k8temp firewire_core gameport snd_hwdep video serio_raw crc_itu_t sg snd_intel8x0 snd_ac97_codec usbhid ac97_bus snd_pcm snd_timer hid snd floppy i2c_nforce2 thermal processor fan button soundcore i2c_core snd_page_alloc forcedeth btrfs zlib_deflate crc32c libcrc32c ext4 jbd2 crc16 ext3 jbd mbcache ohci_hcd ehci_hcd usbcore sr_mod sd_mod cdrom sata_nv pata_amd libata scsi_mod [31653.267989] [31653.267995] Pid: 726, comm: btrfs-transacti Not tainted 3.0-ARCH #1 /LP UT NF4 Expert [31653.268011] RIP: 0010:[<ffffffffa01a6263>] [<ffffffffa01a6263>] run_clustered_refs+0x813/0x830 [btrfs] [31653.268045] RSP: 0018:ffff88013469bc70 EFLAGS: 00010286 [31653.268286] RAX: 00000000ffffffe4 RBX: ffff88012e406900 RCX: ffff8801378a6100 [31653.268296] RDX: ffff88011513a0f0 RSI: 0000000000000000 RDI: 0000000000000000 [31653.268306] RBP: ffff88013469bd50 R08: ffffffffffffffff R09: 0000000000000000 [31653.268315] R10: ffff8801346f9800 R11: ffff88013735d3f0 R12: ffff8800a9bc7f00 [31653.268325] R13: ffff88007b1d7e40 R14: ffff88011bd1e4b0 R15: 0000000000000000 [31653.268341] FS: 00007f8dcc527880(0000) GS:ffff88013fd00000(0000) knlGS:00000000f67567f0 [31653.268367] CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b [31653.268380] CR2: 00007f9059631550 CR3: 00000000a499c000 CR4: 00000000000006e0 [31653.268394] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 [31653.268409] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400 [31653.268424] Process btrfs-transacti (pid: 726, threadinfo ffff88013469a000, task ffff880136c140b0) [31653.268443] Stack: [31653.268449] 0000000000000000 0000000000000000 ffff880100000001 0000000000000000 [31653.268473] 0000000000000c2e 00000000a01dc529 0000000000000000 0000000000000002 [31653.268495] 0000000000000b9f 0000000000000c04 0000000000000000 ffff88013469bd90 [31653.268515] Call Trace: [31653.268531] [<ffffffffa01a6348>] btrfs_run_delayed_refs+0xc8/0x220 [btrfs] [31653.268549] [<ffffffffa019421a>] ? btrfs_free_path+0x2a/0x40 [btrfs] [31653.268568] [<ffffffffa01b86c3>] btrfs_commit_transaction+0x3c3/0x8a0 [btrfs] [31653.268581] [<ffffffff8107f790>] ? abort_exclusive_wait+0xb0/0xb0 [31653.268598] [<ffffffffa01b13ed>] transaction_kthread+0x26d/0x290 [btrfs] [31653.268617] [<ffffffffa01b1180>] ? btrfs_congested_fn+0xd0/0xd0 [btrfs] [31653.268627] [<ffffffff8107ee3c>] kthread+0x8c/0xa0 [31653.268638] [<ffffffff813f5d64>] kernel_thread_helper+0x4/0x10 [31653.268647] [<ffffffff8107edb0>] ? kthread_worker_fn+0x190/0x190 [31653.268657] [<ffffffff813f5d60>] ? gs_change+0x13/0x13 [31653.268673] Code: e0 e9 12 f9 ff ff 0f 0b 80 fa b2 0f 84 bc f9 ff ff 0f 0b be 95 00 00 00 48 c7 c7 37 d0 20 a0 e8 54 65 eb e0 e9 04 f9 ff ff 0f 0b <0f> 0b 0f 0b 0f 0b 0f 0b 0f 0b 0f 0b 0f 0b 66 66 66 66 66 66 2e [31653.268928] RIP [<ffffffffa01a6263>] run_clustered_refs+0x813/0x830 [btrfs] [31653.268956] RSP <ffff88013469bc70> [31653.284196] ---[ end trace d5d8ee7634d1c36e ]--- and it looks related to the print_leaf bug later (eg. mentiones same functions in the stacktrace and happens during commit). And judging from the rest of BUG''s in the paste, the filesystem is in a bad shape. Some BUG_ON''s seem to be triggered by ENOSPC (RAX containing 0xfff..e4). david -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Leonidas Spyropoulos
2011-Oct-24 12:10 UTC
Re: Kernel BUG unable to handle kernel NULL pointer dereference
On Mon, Oct 24, 2011 at 12:51 PM, David Sterba <dsterba@suse.cz> wrote:> On Mon, Oct 24, 2011 at 12:33:05PM +0100, Leonidas Spyropoulos wrote: >> Here is it, it''s big and contains usless information.. >> >> http://paste.pocoo.org/show/497299/ > > not all that useless ... I saw another BUG earlier than the one you''ve > reported: > > [31653.267742] ------------[ cut here ]------------ > [31653.267764] kernel BUG at fs/btrfs/extent-tree.c:5510! > [31653.267773] invalid opcode: 0000 [#1] PREEMPT SMP > [31653.267785] CPU 1 > [31653.267790] Modules linked in: vboxdrv ipv6 loop fuse adt7475 hwmon_vid nouveau evdev uvcvideo hid_apple ttm videodev drm_kms_helper media v4l2_compat_ioctl32 drm snd_emu10k1 i2c_algo_bit mxm_wmi wmi pcspkr snd_rawmidi snd_seq_device firewire_ohci emu10k1_gp edac_core psmouse snd_util_mem edac_mce_amd k8temp firewire_core gameport snd_hwdep video serio_raw crc_itu_t sg snd_intel8x0 snd_ac97_codec usbhid ac97_bus snd_pcm snd_timer hid snd floppy i2c_nforce2 thermal processor fan button soundcore i2c_core snd_page_alloc forcedeth btrfs zlib_deflate crc32c libcrc32c ext4 jbd2 crc16 ext3 jbd mbcache ohci_hcd ehci_hcd usbcore sr_mod sd_mod cdrom sata_nv pata_amd libata scsi_mod > [31653.267989] > [31653.267995] Pid: 726, comm: btrfs-transacti Not tainted 3.0-ARCH #1 /LP UT NF4 Expert > [31653.268011] RIP: 0010:[<ffffffffa01a6263>] [<ffffffffa01a6263>] run_clustered_refs+0x813/0x830 [btrfs] > [31653.268045] RSP: 0018:ffff88013469bc70 EFLAGS: 00010286 > [31653.268286] RAX: 00000000ffffffe4 RBX: ffff88012e406900 RCX: ffff8801378a6100 > [31653.268296] RDX: ffff88011513a0f0 RSI: 0000000000000000 RDI: 0000000000000000 > [31653.268306] RBP: ffff88013469bd50 R08: ffffffffffffffff R09: 0000000000000000 > [31653.268315] R10: ffff8801346f9800 R11: ffff88013735d3f0 R12: ffff8800a9bc7f00 > [31653.268325] R13: ffff88007b1d7e40 R14: ffff88011bd1e4b0 R15: 0000000000000000 > [31653.268341] FS: 00007f8dcc527880(0000) GS:ffff88013fd00000(0000) knlGS:00000000f67567f0 > [31653.268367] CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b > [31653.268380] CR2: 00007f9059631550 CR3: 00000000a499c000 CR4: 00000000000006e0 > [31653.268394] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 > [31653.268409] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400 > [31653.268424] Process btrfs-transacti (pid: 726, threadinfo ffff88013469a000, task ffff880136c140b0) > [31653.268443] Stack: > [31653.268449] 0000000000000000 0000000000000000 ffff880100000001 0000000000000000 > [31653.268473] 0000000000000c2e 00000000a01dc529 0000000000000000 0000000000000002 > [31653.268495] 0000000000000b9f 0000000000000c04 0000000000000000 ffff88013469bd90 > [31653.268515] Call Trace: > [31653.268531] [<ffffffffa01a6348>] btrfs_run_delayed_refs+0xc8/0x220 [btrfs] > [31653.268549] [<ffffffffa019421a>] ? btrfs_free_path+0x2a/0x40 [btrfs] > [31653.268568] [<ffffffffa01b86c3>] btrfs_commit_transaction+0x3c3/0x8a0 [btrfs] > [31653.268581] [<ffffffff8107f790>] ? abort_exclusive_wait+0xb0/0xb0 > [31653.268598] [<ffffffffa01b13ed>] transaction_kthread+0x26d/0x290 [btrfs] > [31653.268617] [<ffffffffa01b1180>] ? btrfs_congested_fn+0xd0/0xd0 [btrfs] > [31653.268627] [<ffffffff8107ee3c>] kthread+0x8c/0xa0 > [31653.268638] [<ffffffff813f5d64>] kernel_thread_helper+0x4/0x10 > [31653.268647] [<ffffffff8107edb0>] ? kthread_worker_fn+0x190/0x190 > [31653.268657] [<ffffffff813f5d60>] ? gs_change+0x13/0x13 > [31653.268673] Code: e0 e9 12 f9 ff ff 0f 0b 80 fa b2 0f 84 bc f9 ff ff 0f 0b be 95 00 00 00 48 c7 c7 37 d0 20 a0 e8 54 65 eb e0 e9 04 f9 ff ff 0f 0b <0f> 0b 0f 0b 0f 0b 0f 0b 0f 0b 0f 0b 0f 0b 66 66 66 66 66 66 2e > [31653.268928] RIP [<ffffffffa01a6263>] run_clustered_refs+0x813/0x830 [btrfs] > [31653.268956] RSP <ffff88013469bc70> > [31653.284196] ---[ end trace d5d8ee7634d1c36e ]--- > > and it looks related to the print_leaf bug later (eg. mentiones same functions > in the stacktrace and happens during commit). > > And judging from the rest of BUG''s in the paste, the filesystem is in a bad > shape. Some BUG_ON''s seem to be triggered by ENOSPC (RAX containing 0xfff..e4). > > > david >I am doing a backup of my current data as I write this mail (hopefully it will finish without IO errors). Will it help if I print the btrfs tree and post it somewhere? I mean, since the system is funcionable, it could be useful to track down the bug, no? Regards Leonidas -- Caution: breathing may be hazardous to your health. -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Leonidas Spyropoulos
2011-Oct-26 12:22 UTC
Re: Kernel BUG unable to handle kernel NULL pointer dereference
On Mon, Oct 24, 2011 at 1:10 PM, Leonidas Spyropoulos <artafinde@gmail.com> wrote:> On Mon, Oct 24, 2011 at 12:51 PM, David Sterba <dsterba@suse.cz> wrote: >> On Mon, Oct 24, 2011 at 12:33:05PM +0100, Leonidas Spyropoulos wrote: >>> Here is it, it''s big and contains usless information.. >>> >>> http://paste.pocoo.org/show/497299/ >> >> not all that useless ... I saw another BUG earlier than the one you''ve >> reported: >> >> [31653.267742] ------------[ cut here ]------------ >> [31653.267764] kernel BUG at fs/btrfs/extent-tree.c:5510! >> [31653.267773] invalid opcode: 0000 [#1] PREEMPT SMP >> [31653.267785] CPU 1 >> [31653.267790] Modules linked in: vboxdrv ipv6 loop fuse adt7475 hwmon_vid nouveau evdev uvcvideo hid_apple ttm videodev drm_kms_helper media v4l2_compat_ioctl32 drm snd_emu10k1 i2c_algo_bit mxm_wmi wmi pcspkr snd_rawmidi snd_seq_device firewire_ohci emu10k1_gp edac_core psmouse snd_util_mem edac_mce_amd k8temp firewire_core gameport snd_hwdep video serio_raw crc_itu_t sg snd_intel8x0 snd_ac97_codec usbhid ac97_bus snd_pcm snd_timer hid snd floppy i2c_nforce2 thermal processor fan button soundcore i2c_core snd_page_alloc forcedeth btrfs zlib_deflate crc32c libcrc32c ext4 jbd2 crc16 ext3 jbd mbcache ohci_hcd ehci_hcd usbcore sr_mod sd_mod cdrom sata_nv pata_amd libata scsi_mod >> [31653.267989] >> [31653.267995] Pid: 726, comm: btrfs-transacti Not tainted 3.0-ARCH #1 /LP UT NF4 Expert >> [31653.268011] RIP: 0010:[<ffffffffa01a6263>] [<ffffffffa01a6263>] run_clustered_refs+0x813/0x830 [btrfs] >> [31653.268045] RSP: 0018:ffff88013469bc70 EFLAGS: 00010286 >> [31653.268286] RAX: 00000000ffffffe4 RBX: ffff88012e406900 RCX: ffff8801378a6100 >> [31653.268296] RDX: ffff88011513a0f0 RSI: 0000000000000000 RDI: 0000000000000000 >> [31653.268306] RBP: ffff88013469bd50 R08: ffffffffffffffff R09: 0000000000000000 >> [31653.268315] R10: ffff8801346f9800 R11: ffff88013735d3f0 R12: ffff8800a9bc7f00 >> [31653.268325] R13: ffff88007b1d7e40 R14: ffff88011bd1e4b0 R15: 0000000000000000 >> [31653.268341] FS: 00007f8dcc527880(0000) GS:ffff88013fd00000(0000) knlGS:00000000f67567f0 >> [31653.268367] CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b >> [31653.268380] CR2: 00007f9059631550 CR3: 00000000a499c000 CR4: 00000000000006e0 >> [31653.268394] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 >> [31653.268409] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400 >> [31653.268424] Process btrfs-transacti (pid: 726, threadinfo ffff88013469a000, task ffff880136c140b0) >> [31653.268443] Stack: >> [31653.268449] 0000000000000000 0000000000000000 ffff880100000001 0000000000000000 >> [31653.268473] 0000000000000c2e 00000000a01dc529 0000000000000000 0000000000000002 >> [31653.268495] 0000000000000b9f 0000000000000c04 0000000000000000 ffff88013469bd90 >> [31653.268515] Call Trace: >> [31653.268531] [<ffffffffa01a6348>] btrfs_run_delayed_refs+0xc8/0x220 [btrfs] >> [31653.268549] [<ffffffffa019421a>] ? btrfs_free_path+0x2a/0x40 [btrfs] >> [31653.268568] [<ffffffffa01b86c3>] btrfs_commit_transaction+0x3c3/0x8a0 [btrfs] >> [31653.268581] [<ffffffff8107f790>] ? abort_exclusive_wait+0xb0/0xb0 >> [31653.268598] [<ffffffffa01b13ed>] transaction_kthread+0x26d/0x290 [btrfs] >> [31653.268617] [<ffffffffa01b1180>] ? btrfs_congested_fn+0xd0/0xd0 [btrfs] >> [31653.268627] [<ffffffff8107ee3c>] kthread+0x8c/0xa0 >> [31653.268638] [<ffffffff813f5d64>] kernel_thread_helper+0x4/0x10 >> [31653.268647] [<ffffffff8107edb0>] ? kthread_worker_fn+0x190/0x190 >> [31653.268657] [<ffffffff813f5d60>] ? gs_change+0x13/0x13 >> [31653.268673] Code: e0 e9 12 f9 ff ff 0f 0b 80 fa b2 0f 84 bc f9 ff ff 0f 0b be 95 00 00 00 48 c7 c7 37 d0 20 a0 e8 54 65 eb e0 e9 04 f9 ff ff 0f 0b <0f> 0b 0f 0b 0f 0b 0f 0b 0f 0b 0f 0b 0f 0b 66 66 66 66 66 66 2e >> [31653.268928] RIP [<ffffffffa01a6263>] run_clustered_refs+0x813/0x830 [btrfs] >> [31653.268956] RSP <ffff88013469bc70> >> [31653.284196] ---[ end trace d5d8ee7634d1c36e ]--- >> >> and it looks related to the print_leaf bug later (eg. mentiones same functions >> in the stacktrace and happens during commit). >> >> And judging from the rest of BUG''s in the paste, the filesystem is in a bad >> shape. Some BUG_ON''s seem to be triggered by ENOSPC (RAX containing 0xfff..e4). >> >> >> david >> > > I am doing a backup of my current data as I write this mail (hopefully > it will finish without IO errors). > Will it help if I print the btrfs tree and post it somewhere? > > I mean, since the system is funcionable, it could be useful to track > down the bug, no? > > Regards > Leonidas > > > > -- > Caution: breathing may be hazardous to your health. >Update: I umount the /home partition and rin the btrfsck tool on the device The output is: http://paste.pocoo.org/show/498415/ Using btrfs-tools from darksatanic git repo branch integration-20111012 I think I will be going for recreation of the partition. Hopefully my / is ok. Need to do the check with a LiveCD. -- Caution: breathing may be hazardous to your health. -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html