On Tue, Feb 22, 2011 at 09:06:44PM -0500, Daniel Kahn Gillmor wrote:
> On 02/22/2011 08:14 PM, Ben Hutchings wrote:
> > This bug report was made against Debian's package of Linux 2.6.37:
> [...]
> > I don't see any changes to this driver between 2.6.37-rc4 (the first
> > version we built as '2.6.37-trunk-686') and 2.6.37, so I think Daniel
> > just had good luck with the earlier versions.
>
> I was running 2.6.37-1~experimental.1, fwiw, since 2011-01-09. I don't
> think that was based off of rc4, because i was running
> 2.6.37~rc5-1~experimental.3 before that since 2010-12-16.
>
> so the dates are:
>
> 2010-12-16: start running 2.6.37~rc5-1~experimental.3
> 2011-01-09: start running 2.6.37-1~experimental.1
> 2011-02-17: start running 2.6.37-1
>
> I run this machine every day, connect it to multiple wired networks, and
> have a usage pattern of suspend-to-ram at least twice a day. I never
> saw this problem until i was running 2.6.37-1.
>
> I don't think i was simply lucky with the previous versions.
Does this still occur with more recent kernels, e.g. 3.0?
Cheers,
Moritz
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110729152021.GA24903@pisco.westfalen.local
