https://bugzilla.novell.com/show_bug.cgi?id=826481
https://bugzilla.novell.com/show_bug.cgi?id=826481#c13
Jeff Mahoney changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |NEEDINFO
CC| |jeffm@suse.com
InfoProvider| |rlk@alum.mit.edu
--- Comment #13 from Jeff Mahoney 2013-07-16 12:05:38 EDT ---
The upstream kernel doesn't get any patches that we don't carry. It's a rare
thing for us to /revert/ an upstream change in one of our releases that isn't
also reverted in a -stable update.
The QA that goes into openSUSE is mostly by our users during the beta cycles.
We try to minimize the number of patches we apply on top of the official Linux
release we use as a base. "Our users" includes SUSE developers, but our core
responsibility is to develop and maintain our enterprise products since that's
what keeps the lights on in the offices. We try to eat our own dog food as much
as possible, but most of the openSUSE bugs tend to be with end-user consumer
hardware that may not be available to testers and/or developers.
Since 3.10 works for you, we'd like to track down what the real fix is and
incorporate it into the 12.3 release, but without access to the hardware or
detailed logs describing the problem, it's basically impossible for us to do
that without help from bug reporters. From the information you've provided, we
only know that it /is/ crashing. It could be any driver on your system.
Another way to narrow it down without bisecting it, would be to gradually
unload drivers and try to reproduce the problem. Once you can suspend
successfully, report the driver that made the difference, and we can look at
the changes to it between 3.4 and 3.7 to identify a potential failure.
--
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.