[Bug 716582] New: "invalid opcode" messages in syslog when using btrfs
https://bugzilla.novell.com/show_bug.cgi?id=716582 https://bugzilla.novell.com/show_bug.cgi?id=716582#c0 Summary: "invalid opcode" messages in syslog when using btrfs Classification: openSUSE Product: openSUSE 12.1 Version: Milestone 5 Platform: i586 OS/Version: SuSE Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers@forge.provo.novell.com ReportedBy: osl2008@googlemail.com QAContact: qa@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux i686; rv:5.0) Gecko/20100101 Firefox/5.0 Using 12.1 M5 on elderly P4 machine, 512M RAM, and working the file IO hard with searching, sorting etc. Every so often I get blocks like this from syslogd: Message from syslogd@linux-d8t5 at Sep 8 10:02:16 ... kernel:[ 2231.615921] ------------[ cut here ]------------ Message from syslogd@linux-d8t5 at Sep 8 10:02:17 ... kernel:[ 2231.615940] invalid opcode: 0000 [#1] SMP Message from syslogd@linux-d8t5 at Sep 8 10:02:17 ... kernel:[ 2231.616019] Process btrfs-endio-wri (pid: 220, ti=dfb8c000 task=dcd08430 task.ti=dfb8c000) Message from syslogd@linux-d8t5 at Sep 8 10:02:17 ... kernel:[ 2231.616019] Stack: Message from syslogd@linux-d8t5 at Sep 8 10:02:17 ... kernel:[ 2231.616019] Call Trace: Message from syslogd@linux-d8t5 at Sep 8 10:02:17 ... kernel:[ 2231.616019] Code: 24 8b 54 24 14 89 4c 24 04 e8 96 f0 02 00 8d 95 86 00 00 00 89 f8 8b 4c 24 78 e8 05 ed 02 00 e9 78 ff ff ff b8 f4 ff ff ff eb bc <0f> 0b 8b 4c 24 74 8b 41 09 8b 51 0d 89 44 24 0c 89 54 24 10 8b Message from syslogd@linux-d8t5 at Sep 8 10:02:17 ... kernel:[ 2231.616019] EIP: [<e12914b7>] alloc_reserved_file_extent+0x217/0x250 [btrfs] SS:ESP 0068:dfb8dd64 I am not sure how serious this is but since btrfs is new I think it worth reporting. Reproducible: Sometimes Steps to Reproduce: 1. Install 12.1 M5 on Pentium 4 machine 2. Exercise the file IO 3. Actual Results: Nasty looking syslogd messages at ? random intervals (~ 1 per hour) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=716582 https://bugzilla.novell.com/show_bug.cgi?id=716582#c1 --- Comment #1 from richard meek <osl2008@googlemail.com> 2011-09-08 09:53:47 UTC --- The machine crashed following the above (hard lock-up, no ssh access either). On re-boot I noticed the following, may be relevant? The btrfs set-up was done by YaST in the installation, using defaults (apart from the selection of btrfs itself) Sep 8 10:37:33 linux-d8t5 kernel: [ 41.604165] btrfs: free space inode generation (0) did not match free space cache generation (310) Sep 8 10:37:33 linux-d8t5 kernel: [ 41.604170] btrfs: failed to load free space cache for block group 1103101952 Sep 8 10:37:33 linux-d8t5 kernel: [ 41.604185] btrfs: free space inode generation (0) did not match free space cache generation (343) Sep 8 10:37:33 linux-d8t5 kernel: [ 41.604189] btrfs: failed to load free space cache for block group 5398069248 Let me know if other log-files are useful, but I will attach the standard y2log anyway. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=716582 https://bugzilla.novell.com/show_bug.cgi?id=716582#c2 --- Comment #2 from richard meek <osl2008@googlemail.com> 2011-09-08 09:56:23 UTC --- Created an attachment (id=449741) --> (http://bugzilla.novell.com/attachment.cgi?id=449741) y2log generated by save_y2logs -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=716582 https://bugzilla.novell.com/show_bug.cgi?id=716582#c3 David Sterba <dsterba@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |osl2008@googlemail.com AssignedTo|kernel-maintainers@forge.pr |dsterba@suse.com |ovo.novell.com | --- Comment #3 from David Sterba <dsterba@suse.com> 2011-10-14 19:03:16 CEST --- Thanks for the report. Can you please attach the messages from syslog? The initial report does not contain all messages (just some fragments interleaved with other terminal output). (In reply to comment #0)
Using 12.1 M5 on elderly P4 machine, 512M RAM, and working the file IO hard with searching, sorting etc.
This not a widely tested hardware with btrfs :)
I am not sure how serious this is but since btrfs is new I think it worth reporting.
It's not that new, but it's still experimental (backups etc).
Nasty looking syslogd messages at ? random intervals (~ 1 per hour)
I'd like to seem, plus the kernel version which you're running (I can see there is 3.1-rc7 on Beta1) or any preceeding message in syslog like "btrfs update block group failed for" (can be found in function alloc_reserved_file_extent mentioned in your report) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=716582 https://bugzilla.novell.com/show_bug.cgi?id=716582#c4 --- Comment #4 from richard meek <osl2008@googlemail.com> 2011-10-15 15:06:00 UTC --- I have no access to the machine until Wednesday but will upload whatever I can find then. As you say, an elderly P4 machine is maybe not widely tested hardware with btrfs - but this machine is one of a bunch that I use for pre-release openSuSE tests. These errors just might affect others too so worth a brief examination. And btrfs is new to me, and seems very different from ext3 / ext4 etc. More next week! -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=716582 https://bugzilla.novell.com/show_bug.cgi?id=716582#c5 --- Comment #5 from richard meek <osl2008@googlemail.com> 2011-10-24 11:26:08 UTC --- Sorry for the delay - I now have the hardware again but it is not booting. I will try again when I get the chance but I won't be in the office much this week. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=716582 https://bugzilla.novell.com/show_bug.cgi?id=716582#c6 --- Comment #6 from David Sterba <dsterba@suse.com> 2011-11-23 15:03:30 CET --- I'm still interested in this bug and would like to see more from the crash if you're able to get it. If you can access shell afther the crash, the full stacktraces should be somewhere in /var/log/messages (you pulled out the yast logs, so I guess getting 'messages' will be possible too). Is the maichine not able to boot due to btrfs? Booting from livecd just to get the logs should work too. Thanks. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=716582 https://bugzilla.novell.com/show_bug.cgi?id=716582#c7 --- Comment #7 from richard meek <osl2008@googlemail.com> 2011-11-23 15:13:00 UTC --- Machine now upgraded to 12.1 Gold Master, no errors installing but I used ext4. I have an old HDD that I can put in and try again with M5 or is 12.1 GM more appropriate? Please advise before I re-do the installation. Actually, I am not too sure I still have the M5 files, I may need to use GM anyway. Is that any use? I will have a ferret around to see what - if anything - I still have from pre-release. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=716582 https://bugzilla.novell.com/show_bug.cgi?id=716582#c8 David Sterba <dsterba@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |RESOLVED InfoProvider|osl2008@googlemail.com | Resolution| |FIXED --- Comment #8 from David Sterba <dsterba@suse.com> 2011-12-21 13:47:35 CET --- Sorry for the delay, from what you wrote it's not straightforward to get to the machine to gather logs so I tried to analyze from the bits you've posted here. There were many fixes upstream in the area where you noticed the crash and will be part of upcomming opensuse kernel. So I hope the issue is fixed, there were no similar reports. Closing. Thanks. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com