Invalid opcode

Hi, I’m new to the forums. I’m fairly experienced with opensuse and usually pretty self sufficient. This morning, my pc was fine. I modified a spreadsheet and saved. About 15 minutes later, I came back to wake it from screensaver and it would not respond at all. After several minutes, i restarted the system and now it will not load the /root partition. I booted from the rescue cd and tried to run fsck on the partitions, but nothing is reported. I tried mounting varous partitions and all were successful with the exception of my root partition. When I try to mount that, it gives me a message “invalid opcode: 0000 #1] SMP” and about 4 lines after that, but the mount fails. If I try again, the command line becomes unresponsive and I cannot break out. I have no way to capture that from the rescue environment, but pulled the logs. I’m hoping there’s a way to recover without recreating the partition, but it is only my system partion, so not too painful. I’m hoping this is enough to help diagnose, but let me know if there is more information I can collect. Any help would be appreciated.

Jan 13 18:34:21 Rescue syslogd 1.4.1: restart.
Jan 13 18:34:21 Rescue ifup:     lo        
Jan 13 18:34:21 Rescue ifup-sysctl: sysctl utility missed, install procps
Jan 13 18:34:21 Rescue ifup:     lo        
Jan 13 18:34:21 Rescue ifup: IP address: 127.0.0.1/8  
Jan 13 18:34:21 Rescue ifup:  
Jan 13 18:34:21 Rescue ifup:     eth0      device: Realtek Semiconductor Co., Ltd. RTL8111/8168B
Jan 13 18:34:21 Rescue ifup:               No configuration found for eth0
Jan 13 18:34:26 Rescue kernel: klogd 1.4.1, log source = /proc/kmsg started.
Jan 13 18:35:33 Rescue kernel:   103.997401] Btrfs loaded
Jan 13 18:35:33 Rescue kernel:   103.998155] device fsid 57aef9ff-7023-4197-9319-91659fdc1f58 devid 1 transid 123446 /dev/sda7
Jan 13 18:35:33 Rescue kernel:   104.035104] btrfs: disk space caching is enabled
Jan 13 18:35:33 Rescue kernel:   104.657253] ------------ cut here ]------------
Jan 13 18:35:33 Rescue kernel:   104.657299] WARNING: at /home/abuild/rpmbuild/BUILD/kernel-default-3.1.0/linux-3.1/fs/btrfs/tree-log.c:1729 walk_down_log_tree+0x15a/0x3e0 [btrfs]()
Jan 13 18:35:33 Rescue kernel:   104.657307] Hardware name: System Product Name
Jan 13 18:35:33 Rescue kernel:   104.657311] Modules linked in: btrfs zlib_deflate nls_utf8 ppa arc4 ecb powernow_k8 mperf fan thermal nfs nfs_acl lockd fscache auth_rpcgss sunrpc nls_iso8859_1 nls_cp437 af_packet st usbhid usb_storage uas radeon ata_generic parport_pc ohci_hcd parport ttm drm_kms_helper button drm ehci_hcd wmi pata_atiixp xhci_hcd i2c_algo_bit ssb mmc_core usbcore sr_mod cdrom pcmcia pcmcia_core sg processor r8169 thermal_sys edd squashfs loop
Jan 13 18:35:33 Rescue kernel:   104.657389] Pid: 2751, comm: mount Not tainted 3.1.0-1.2-default #1
Jan 13 18:35:33 Rescue kernel:   104.657394] Call Trace:
Jan 13 18:35:33 Rescue kernel:   104.657421]  <ffffffff810042fa>] dump_trace+0x9a/0x270
Jan 13 18:35:33 Rescue kernel:   104.657435]  <ffffffff81523edb>] dump_stack+0x69/0x6f
Jan 13 18:35:33 Rescue kernel:   104.657449]  <ffffffff81051eab>] warn_slowpath_common+0x7b/0xc0
Jan 13 18:35:33 Rescue kernel:   104.657485]  <ffffffffa04709aa>] walk_down_log_tree+0x15a/0x3e0 [btrfs]
Jan 13 18:35:33 Rescue kernel:   104.657742]  <ffffffffa0470f57>] walk_log_tree+0xc7/0x1f0 [btrfs]
Jan 13 18:35:33 Rescue kernel:   104.657990]  <ffffffffa0474d2c>] btrfs_recover_log_trees+0x1ec/0x2d0 [btrfs]
Jan 13 18:35:33 Rescue kernel:   104.658244]  <ffffffffa0441c63>] open_ctree+0x13c3/0x1740 [btrfs]
Jan 13 18:35:33 Rescue kernel:   104.658357]  <ffffffffa04206d3>] btrfs_fill_super.isra.36+0x73/0x150 [btrfs]
Jan 13 18:35:33 Rescue kernel:   104.658395]  <ffffffffa0421ac9>] btrfs_mount+0x359/0x3e0 [btrfs]
Jan 13 18:35:33 Rescue kernel:   104.658424]  <ffffffff8114e185>] mount_fs+0x45/0x1d0
Jan 13 18:35:33 Rescue kernel:   104.658437]  <ffffffff81166736>] vfs_kern_mount+0x66/0xd0
Jan 13 18:35:33 Rescue kernel:   104.658448]  <ffffffff81167ac3>] do_kern_mount+0x53/0x120
Jan 13 18:35:33 Rescue kernel:   104.658458]  <ffffffff81169575>] do_mount+0x1a5/0x260
Jan 13 18:35:33 Rescue kernel:   104.658470]  <ffffffff81169a1a>] sys_mount+0x9a/0xf0
Jan 13 18:35:33 Rescue kernel:   104.658481]  <ffffffff81543e12>] system_call_fastpath+0x16/0x1b
Jan 13 18:35:33 Rescue kernel:   104.658495]  <00007f5e188f4daa>] 0x7f5e188f4da9
Jan 13 18:35:33 Rescue kernel:   104.658500] --- end trace b339d3701a74932f ]---
Jan 13 18:35:33 Rescue kernel:   104.658531] unable to find logical 20890721841152 len 4096
Jan 13 18:35:33 Rescue kernel:   104.658558] ------------ cut here ]------------
Jan 13 18:35:33 Rescue kernel:   104.658567] kernel BUG at /home/abuild/rpmbuild/BUILD/kernel-default-3.1.0/linux-3.1/fs/btrfs/volumes.c:2891!
Jan 13 18:35:33 Rescue kernel:   104.658578] invalid opcode: 0000 #1] SMP 
Jan 13 18:35:33 Rescue kernel:   104.658587] CPU 0 
Jan 13 18:35:33 Rescue kernel:   104.658590] Modules linked in: btrfs zlib_deflate nls_utf8 ppa arc4 ecb powernow_k8 mperf fan thermal nfs nfs_acl lockd fscache auth_rpcgss sunrpc nls_iso8859_1 nls_cp437 af_packet st usbhid usb_storage uas radeon ata_generic parport_pc ohci_hcd parport ttm drm_kms_helper button drm ehci_hcd wmi pata_atiixp xhci_hcd i2c_algo_bit ssb mmc_core usbcore sr_mod cdrom pcmcia pcmcia_core sg processor r8169 thermal_sys edd squashfs loop
Jan 13 18:35:33 Rescue kernel:   104.658681] 
Jan 13 18:35:33 Rescue kernel:   104.658687] Pid: 2751, comm: mount Tainted: G        W   3.1.0-1.2-default #1 System manufacturer System Product Name/M4A88T-M/USB3
Jan 13 18:35:33 Rescue kernel:   104.658704] RIP: 0010:<ffffffffa0465c58>]  <ffffffffa0465c58>] __btrfs_map_block+0x7c8/0x890 [btrfs]
Jan 13 18:35:33 Rescue kernel:   104.658743] RSP: 0018:ffff8802051a3678  EFLAGS: 00010292
Jan 13 18:35:33 Rescue kernel:   104.658751] RAX: 0000000000000044 RBX: 00001300000df000 RCX: 0000000000002ee5
Jan 13 18:35:33 Rescue kernel:   104.658760] RDX: 00000000000040fd RSI: 0000000000000046 RDI: 0000000000000246
Jan 13 18:35:33 Rescue kernel:   104.658769] RBP: 0000000000000001 R08: 0000000000000000 R09: 0000000000000000
Jan 13 18:35:33 Rescue kernel:   104.658777] R10: 0000000000000000 R11: 000000000000fffe R12: 0000000000000000
Jan 13 18:35:33 Rescue kernel:   104.658786] R13: 0000000000000008 R14: 0000000000000000 R15: ffff880204aa0100
Jan 13 18:35:33 Rescue kernel:   104.658795] FS:  00007f5e1942d7e0(0000) GS:ffff88021fc00000(0000) knlGS:0000000000000000
Jan 13 18:35:33 Rescue kernel:   104.658805] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Jan 13 18:35:33 Rescue kernel:   104.658812] CR2: 00007f46470a7000 CR3: 000000020502d000 CR4: 00000000000006f0
Jan 13 18:35:33 Rescue kernel:   104.658821] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
Jan 13 18:35:33 Rescue kernel:   104.658830] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Jan 13 18:35:33 Rescue kernel:   104.658839] Process mount (pid: 2751, threadinfo ffff8802051a2000, task ffff880211e3c440)
Jan 13 18:35:33 Rescue kernel:   104.658848] Stack:
Jan 13 18:35:33 Rescue kernel:   104.658852]  ffff880208f84cf8 ffffffffa045dfb1 0000000000000000 00001300000e0fff
Jan 13 18:35:33 Rescue kernel:   104.658866]  0000000000000050 ffff880204aa00f8 ffff8802051a3720 0000130000000000
Jan 13 18:35:33 Rescue kernel:   104.658879]  0000000000000000 0000000000000000 0000000000000000 0000000000000005
Jan 13 18:35:33 Rescue kernel:   104.658892] Call Trace:
Jan 13 18:35:33 Rescue kernel:   104.659125]  <ffffffffa0445fb9>] btrfs_merge_bio_hook+0x59/0x80 [btrfs]
Jan 13 18:35:33 Rescue kernel:   104.659262]  <ffffffffa045fd8c>] submit_extent_page.isra.31+0xec/0x240 [btrfs]
Jan 13 18:35:33 Rescue kernel:   104.659479]  <ffffffffa04603e5>] __extent_read_full_page+0x4c5/0x700 [btrfs]
Jan 13 18:35:33 Rescue kernel:   104.659698]  <ffffffffa04623db>] read_extent_buffer_pages+0x2bb/0x420 [btrfs]
Jan 13 18:35:33 Rescue kernel:   104.659919]  <ffffffffa043d730>] btree_read_extent_buffer_pages.isra.62+0x80/0xc0 [btrfs]
Jan 13 18:35:33 Rescue kernel:   104.660032]  <ffffffffa044049a>] btrfs_read_buffer+0x2a/0x40 [btrfs]
Jan 13 18:35:33 Rescue kernel:   104.660154]  <ffffffffa0473a46>] replay_one_buffer+0x46/0x360 [btrfs]
Jan 13 18:35:33 Rescue kernel:   104.660411]  <ffffffffa0470a5d>] walk_down_log_tree+0x20d/0x3e0 [btrfs]
Jan 13 18:35:33 Rescue kernel:   104.660661]  <ffffffffa0470f57>] walk_log_tree+0xc7/0x1f0 [btrfs]
Jan 13 18:35:33 Rescue kernel:   104.660911]  <ffffffffa0474d2c>] btrfs_recover_log_trees+0x1ec/0x2d0 [btrfs]
Jan 13 18:35:33 Rescue kernel:   104.661130]  <ffffffffa0441c63>] open_ctree+0x13c3/0x1740 [btrfs]
Jan 13 18:35:33 Rescue kernel:   104.661130]  <ffffffffa04206d3>] btrfs_fill_super.isra.36+0x73/0x150 [btrfs]
Jan 13 18:35:33 Rescue kernel:   104.661130]  <ffffffffa0421ac9>] btrfs_mount+0x359/0x3e0 [btrfs]
Jan 13 18:35:33 Rescue kernel:   104.661130]  <ffffffff8114e185>] mount_fs+0x45/0x1d0
Jan 13 18:35:34 Rescue kernel:   104.661130]  <ffffffff81166736>] vfs_kern_mount+0x66/0xd0
Jan 13 18:35:34 Rescue kernel:   104.661130]  <ffffffff81167ac3>] do_kern_mount+0x53/0x120
Jan 13 18:35:34 Rescue kernel:   104.661130]  <ffffffff81169575>] do_mount+0x1a5/0x260
Jan 13 18:35:34 Rescue kernel:   104.661130]  <ffffffff81169a1a>] sys_mount+0x9a/0xf0
Jan 13 18:35:34 Rescue kernel:   104.661130]  <ffffffff81543e12>] system_call_fastpath+0x16/0x1b
Jan 13 18:35:34 Rescue kernel:   104.661130]  <00007f5e188f4daa>] 0x7f5e188f4da9
Jan 13 18:35:34 Rescue kernel:   104.661130] Code: 47 8d 4c 31 ff c7 44 24 10 01 00 00 00 e9 cf fa ff ff 48 8b 44 24 30 48 89 de 48 c7 c7 70 36 49 a0 48 8b 10 31 c0 e8 a8 0b 0c e1 <0f> 0b 65 48 8b 04 25 80 b6 00 00 8b 80 d0 02 00 00 89 c2 c1 fa 
Jan 13 18:35:34 Rescue kernel:   104.661130] RIP  <ffffffffa0465c58>] __btrfs_map_block+0x7c8/0x890 [btrfs]
Jan 13 18:35:34 Rescue kernel:   104.661130]  RSP <ffff8802051a3678>
Jan 13 18:35:34 Rescue kernel:   104.661593] --- end trace b339d3701a749330 ]---

Could be a brtfs bug, but run memtest on your RAM first.

On 01/13/2012 08:46 PM, ken yap wrote:
>
> Could be a brtfs bug, but run memtest on your RAM first.

A memory test is a good idea, but it is likely that you have a brtfs problem. If
there were a proper fsck for that fs, you could probably recover. When you
reinstall, do not select btfrs for /. It is not ready for prime time.

On 01/14/2012 03:56 AM, Larry Finger wrote:
> do not select btfrs for /. It is not ready for prime time.

i would go further and say: do not select btrfs for any partition on
your daily driver/production machine/only computer/any computer you
depend on…

but, if you have a secondary ‘sandbox’ machine used only for software
testing then that is the place to install and test btrfs…

light reading on the subject: http://tinyurl.com/dxbftdf


DD http://tinyurl.com/DD-Caveat
openSUSE®, the “German Engineered Automobiles” of operating systems!

On 2012-01-14 03:26, EagleSB wrote:

> I tried mounting varous
> partitions and all were successful with the exception of my root
> partition. When I try to mount that, it gives me a message “invalid
> opcode: 0000 #1] SMP
” and about 4 lines after that, but the mount
> fails.

If I read that correctly, it means the cpu found a “0000” when it expected
and instruction, and halted. That would be a corrupted program or an error
in the programmer, or rather, the compiler.

> Jan 13 18:35:33 Rescue kernel: 104.657253] ------------ cut here ]------------

Send that to Bugzilla.

Besides that, btfrs is experimental. Don’t use it if you need your computer.


Cheers / Saludos,

Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)

Am 14.01.2012 03:56, schrieb Larry Finger:
> On 01/13/2012 08:46 PM, ken yap wrote:
>>
>> Could be a brtfs bug, but run memtest on your RAM first.
>
> A memory test is a good idea, but it is likely that you have a brtfs
> problem. If there were a proper fsck for that fs, you could probably
> recover. When you reinstall, do not select btfrs for /. It is not ready
> for prime time.
There is some repair tool available in the mean time
https://btrfs.wiki.kernel.org/articles/p/r/o/Problem_FAQ_68af.html
(I can’t mount my filesystem, and I get a kernel oops!)


PC: oS 11.4 (dual boot 12.1) 64 bit | Intel Core i7-2600@3.40GHz | KDE
4.6.0 | GeForce GT 420 | 16GB Ram
Eee PC 1201n: oS 11.4 64 bit | Intel Atom 330@1.60GHz | KDE 4.7.4 |
nVidia ION | 3GB Ram

Thank you all for your replies. I usually run ext3, but I was under the impression that btrfs was good in suse 12.1. I’ll run the memtest, but since i can successfully run the memory hog Windows without a problem, I didn’t think that’d turn anything up. Probably worth a try anyway. I’ll give the repair tool a try if it’ll work under my old 11.3 partition. I suspect that won’t be an issue. Sounds like i need to start rebuiling my file systems

On 01/14/2012 04:26 PM, EagleSB wrote:
> since i can successfully run the memory hog Windows without a problem, I
> didn’t think that’d turn anything up.

memtest may not show anything…but there are many examples of RAM
which Windows uses but which causes Linux to barf!

the reason is the large differences in the way the two systems use RAM:

Windows strives to empty RAM as fast as it can, at every opportunity
(like, when an application is halted all the RAM in use by that app is
freed)–with the underlying idea that the more RAM unused the better.

Linux keeps RAM is pretty much full all the time (like, when an app is
closed all of its RAM is likely to stay in use, until some other system
need pops up to need it…because, stuff in RAM is faster to get than
stuff on the disk, so if the user (or script or what ever) relaunches
the app in 30 seconds, BAM it is there!–with the underlying idea that
unused RAM is wasted ram…

so, Windows might go for years and never get to that almost full point
of RAM, hit that bad spot and barf.


DD http://tinyurl.com/DD-Caveat
openSUSE®, the “German Engineered Automobiles” of operating systems!

Great info on windows vs linux. Thanks. I did run the mem test and everything checked out without errors. I ran the btrfs-zero-log utility and that appears to have resolved the problem. Thank you @martin_helm. I’m back up and running. One more question as I prepare to reformat my partitions for ext4. I’d prefer not to have to install all my packages from scratch. Can I just tar/gzip the entire partition (including hidden files and directories), reformat it and restore? It is not the boot partition. I assume this would retain all the permissions, etc.

On 01/14/2012 11:56 AM, EagleSB wrote:
>
> Great info on windows vs linux. Thanks. I did run the mem test and
> everything checked out without errors. I ran the btrfs-zero-log utility
> and that appears to have resolved the problem. Thank you @martin_helm.
> I’m back up and running. One more question as I prepare to reformat my
> partitions for ext4. I’d prefer not to have to install all my packages
> from scratch. Can I just tar/gzip the entire partition (including
> hidden files and directories), reformat it and restore? It is not the
> boot partition. I assume this would retain all the permissions, etc.

Yes, running tar on the mount point will save everything and produce a file that
will restore the files exactly. When you use the j option (bzip2 compression),
it is as small as possible.

On 2012-01-14 18:56, EagleSB wrote:
> I ran the btrfs-zero-log utility
> and that appears to have resolved the problem.

Don’t forget that you have to do a report in Bugzilla.


Cheers / Saludos,

Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)

I’ll be happy to do so, but I’m not sure how. Can you provide guidance on submitting the report?

On 2012-01-14 22:56, EagleSB wrote:
>
> I’ll be happy to do so, but I’m not sure how. Can you provide guidance
> on submitting the report?

No, the wiki is down, till Monday or later. There is a page there that
explains the process.

Ah, I found it: <http://en.opensuse.org/Bugzilla>


Cheers / Saludos,

Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)

Thanks again for all your help.

Bug 741472 Submitted

On 2012-01-15 17:46, EagleSB wrote:
>
> Thanks again for all your help.
>
> Bug 741472 Submitted

Thanks.


Cheers / Saludos,

Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)