Re: Should I make a tracking bug in fedora for problem reported upstream?

2011-08-29 Thread Adam Williamson
On Sun, 2011-08-28 at 09:43 -0500, Bruno Wolff III wrote: I have reported https://bugzilla.kernel.org/show_bug.cgi?id=41862 for an issue with 3.1 kernels crashing, typically on the order of hours after booting. Based on some names in the traceback, I suspect this is MD raid or luks related.

Should I make a tracking bug in fedora for problem reported upstream?

2011-08-28 Thread Bruno Wolff III
I have reported https://bugzilla.kernel.org/show_bug.cgi?id=41862 for an issue with 3.1 kernels crashing, typically on the order of hours after booting. Based on some names in the traceback, I suspect this is MD raid or luks related. I reported this upstream, since that seems to be a better place

Re: Should I make a tracking bug in fedora for problem reported upstream?

2011-08-28 Thread Matej Cepl
Dne 28.8.2011 16:43, Bruno Wolff III napsal(a): I reported this upstream, since that seems to be a better place to get attention for development kernel bugs, than Fedora's tracker. However, if this should be considered a beta blocker, then I should probably also make a Fedora bug entry so that

RE: Should I make a tracking bug in fedora for problem reported upstream?

2011-08-28 Thread John Dulaney
From: br...@wolff.to To: test@lists.fedoraproject.org Subject: Should I make a tracking bug in fedora for problem reported upstream? I have reported https://bugzilla.kernel.org/show_bug.cgi?id=41862 for an issue with 3.1 kernels crashing, typically on the order of hours after booting.