[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <m1odmi4gx5.fsf@ebiederm.dsl.xmission.com>
Date: Sat, 24 Mar 2007 12:47:50 -0600
From: ebiederm@...ssion.com (Eric W. Biederman)
To: Thomas Meyer <thomas@...3r.de>
Cc: Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [3/5] 2.6.21-rc4: known regressions (v2)
Thomas Meyer <thomas@...3r.de> writes:
> Eric W. Biederman schrieb:
>> Thomas Meyer <thomas@...3r.de> writes:
>>
>>
>>> Adrian Bunk schrieb:
>>>
>>>> Subject : second suspend to disk in a row results in an oops (libata?)
>>>> References : http://lkml.org/lkml/2007/3/17/43
>>>> Submitter : Thomas Meyer <thomas@...3r.de>
>>>> Status : unknown
>>>>
>>>>
>>> The problem is identified: http://lkml.org/lkml/2007/3/22/150
>>>
>>
>> Given the description above I'm a little confused. Doesn't this
>> happen every time now?
>>
> With current git head the oops happens in the second suspend to disk
> attempt in a row.
Odd. I would have thought the oops happened in the first resume, not
the second.
Hmm. It may have something to do with the ``managed'' driver
aspect of this as well..
>> Or was this happening only the second time before I started my msi
>> fixes...
>>
> So i think, that the current git head already contains your msi fixes.
Yes it does.
> I don't know if this already happend before your msi changes, but i can
> test 2.6.20 if you like to?
Sure. A data point if you boot with nomsi or have a kernel compiled
without msi support would be interesting as well.
As the problem case may not show up without msi support in the picture.
Eric
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists