Re: Recent MFC's causing trouble with network and mouse
- From: Gleb Smirnoff <glebius@xxxxxxxxxxx>
- Date: Tue, 31 Jan 2006 11:28:45 +0300
On Tue, Jan 31, 2006 at 02:27:58AM +0300, Andrew Pantyukhin wrote:
A> I upgraded my world and kernel from about a week's
A> old state to today's source and network (vge) and
A> mouse (ums) stopped working. vge0 has a formerly
A> usual trouble of link state going up and down, while
A> ums0 doesn't move or feel its buttons (tried moused
A> and xorg).
A>
A> Had a look at cvs, didn't see anything suspicious
A> about vge and ums in particular :-( This is about time
A> I learnt how to live with several kernels at hand...
Yes, vge(4) and ums(4) wasn't agressively edited recently,
so the breakage is somewhere else. Probably you need to
make a binary search to find the commit that caused the problem.
--
Totus tuus, Glebius.
GLEBIUS-RIPN GLEB-RIPE
_______________________________________________
freebsd-stable@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscribe@xxxxxxxxxxx"
- Follow-Ups:
- Re: Recent MFC's causing trouble with network and mouse
- From: Andrew Pantyukhin
- Re: Recent MFC's causing trouble with network and mouse
- References:
- Recent MFC's causing trouble with network and mouse
- From: Andrew Pantyukhin
- Recent MFC's causing trouble with network and mouse
- Prev by Date: Re: if_bge driver problem. - Upgrade to RELEASE :)
- Next by Date: Re: dc0: watchdog timeout and nve0: device timeout
- Previous by thread: Recent MFC's causing trouble with network and mouse
- Next by thread: Re: Recent MFC's causing trouble with network and mouse
- Index(es):