On Fri, Jul 8, 2011 at 7:29 PM, Jeff Mahoney
On 07/08/2011 05:25 PM, Greg Freemyer wrote:
On Fri, Jul 8, 2011 at 4:29 PM, Jeff Mahoney
wrote: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 07/08/2011 02:18 PM, Greg Freemyer wrote:
All,
I just had a btrfs oops with a default 11,4 kernel.
I haven't even tried a update kernel yet since I wasn't sure anyone would care.
Unless advised otherwise, my plan is to try the same test with a Tumbleweed kernel and open a bugzilla if and only if I get the oops there too.
And the award for the most useless bug report goes to... ;)
Seriously, though, btrfs oops are tough to track because error handling is currently implemented by BUG_ON, so the details are important.
- -Jeff
Jeff,
As I understand it, the goal is to have btrfs be supported option instead of experimental in 12.1
If so, the Tumbleweed kernel seems to be about as bleeding edge as the factory one and thus a good place to test against.
If I'm wasting my time to create a opeSUSE bugzilla let me know and I'll work exclusively with a vanilla kernel and send my reports to kernel.org.
Nope, you're not wasting your time. We're definitely interested in bringing btrfs up to full speed. It's just that this report was "it crashed" and that's it. If you have an Oops, that'd definitely be helpful. The other issue is that some crashes would normally just be recoverable errors, but the error recovery code hasn't been written yet.
I opened bugzilla against the 2.6.39 tumbleweed kernel: https://bugzilla.novell.com/show_bug.cgi?id=705039 Hopefully there is enough info there to be useful. Note that this is the first time the oops actually locked my machine. Previously it just caused the test partitions to freeze up. Greg -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kernel+help@opensuse.org