On Wed, Apr 21, 2010 at 07:15:38AM +0200, Rafael J. Wysocki wrote:As upstream doesn't consider the first to be a kernel issue, I guess you should just list the second. On 10:57 Wed 21 Apr , Jerome Glisse wrote: OK, if the failure is due to userspace is doing Very Bad Things(tm), catching that seems reasonable. Nevertheless, even if it happened by luck, the result was (ostensibly) working programs that suddenly break once one "upgrades" to the latest kernel. If userspace can't be fixed before 2.6.34 is released, perhaps a less cryptic log message would be appropriate? -- Nick Bowler, Elliptic Technologies (http://www.elliptictech.com/) --
