Re: port-i386/35109 ("fxp0: device timeout" (after recent MPACPI changes?))

[Matthew Mondor <mm_lists%pulsar-zone.net@localhost>]

The following reply was made to PR port-i386/35109; it has been noted by GNATS.

From: Matthew Mondor <mm_lists%pulsar-zone.net@localhost>
To: gnats-bugs%NetBSD.org@localhost
Cc: 
Subject: Re: port-i386/35109 ("fxp0: device timeout" (after recent MPACPI
 changes?))
Date: Wed, 11 Nov 2009 09:44:56 -0500

 On Wed, 11 Nov 2009 14:24:04 +0000 (UTC)
 joerg%NetBSD.org@localhost wrote:
 
 > Synopsis: "fxp0: device timeout" (after recent MPACPI changes?)
 > 
 > State-Changed-From-To: feedback->closed
 > State-Changed-By: joerg%NetBSD.org@localhost
 > State-Changed-When: Wed, 11 Nov 2009 14:24:03 +0000
 > State-Changed-Why:
 > Consider feedback timed out. A lot of this has changed and without
 > testing it is impossible to determine if the problem is still
 > relevant.
 
 Interestingly I did get "fxp0: device timeout" with fxp0 stopping to
 work anymore until a reboot, but that was happening about 15-30 seconds
 after a resume from sleep on an IBM Thinkpad T22.  Not currently using
 that laptop anymore (and I'd have to change the HD to use it again), I'm
 however unlikely to test this with a recent -current any time soon.
 
 Thanks,
 -- 
 Matt