Date: Tue, 17 Oct 2006 20:31:39 -0700 From: "Jack Vogel" <jfvogel@gmail.com> To: "Balgansuren Batsukh" <balgaa@micom.mn> Cc: freebsd-stable@freebsd.org Subject: Re: Fw: em0 problem Message-ID: <2a41acea0610172031n1058ca06o2792268dc068f479@mail.gmail.com> In-Reply-To: <00b101c6f1d0$f18f74c0$287ffe7a@JACK> References: <00b101c6f1d0$f18f74c0$287ffe7a@JACK>
next in thread | previous in thread | raw e-mail | index | archive | help
One can't do anything with this kind of information, think about
it as one that has to fix the issue, we need:
- exact model numbers on the system or mb
- pciconf -l so we can see the real version of the adapter
- What exactly was the driver version that last worked, and
what is the version you are having this problem with?
- what is the system doing when this occurs, are there special
things, like using NFS, that are notable?
Thanks for the help,
Jack
On 10/17/06, Balgansuren Batsukh <balgaa@micom.mn> wrote:
> Hello,
>
> I get UP/DOWN message since updated new driver little bi longer:
>
>
> Oct 16 21:14:28 gk kernel: em0: link state changed to DOWN
> Oct 16 21:14:43 gk kernel: em0: link state changed to UP
> Oct 16 21:16:25 gk kernel: em0: link state changed to DOWN
> Oct 16 21:16:40 gk kernel: em0: link state changed to UP
> Oct 16 21:19:28 gk kernel: em0: link state changed to DOWN
> Oct 16 21:19:43 gk kernel: em0: link state changed to UP
> Oct 17 10:00:04 gk su: balgaa to root on /dev/ttyp0
> Oct 17 12:26:18 gk su: balgaa to root on /dev/ttyp0
> Oct 17 13:44:16 gk kernel: em0: link state changed to DOWN
> Oct 17 14:32:29 gk login: ROOT LOGIN (root) ON ttyv0
> Oct 17 14:33:30 gk kernel: em0: link state changed to UP
> Oct 17 14:33:46 gk kernel: em0: link state changed to DOWN
> Oct 17 14:34:00 gk kernel: em0: link state changed to UP
> Oct 17 14:36:25 gk su: balgaa to root on /dev/ttyp0
> Oct 17 14:37:05 gk kernel: em0: link state changed to DOWN
> Oct 17 14:37:40 gk kernel: em0: link state changed to UP
> Oct 17 17:40:26 gk su: balgaa to root on /dev/ttyp0
>
> Is there anyway to do something?
>
> Regards,
> Balgaa
>
> ----- Original Message -----
> From: "Balgansuren Batsukh" <balgaa@micom.mn>
> To: <freebsd-stable@freebsd.org>
> Sent: Saturday, October 14, 2006 11:16 PM
> Subject: Re: em0 problem
>
>
> > Hello Scott,
> >
> > I found below email:
> > =============
> > Mike,
> >
> > I have a new patch that I hope addresses the actual bug, instead of
> > shuffling the timing. Would you be willing to test it? I can't
> > guarantee that it's safe for production use yet, though. It seems
> > to work, but it might set your dog on fire too.
> >
> > Scott
> > =============
> >
> > Is it possible test your new patch?
> >
> > Regards,
> > Balgaa
> >
> > ----- Original Message -----
> > From: "Scott Long" <scottl@samsco.org>
> > To: "Mike Tancsa" <mike@sentex.net>
> > Cc: "Balgansuren Batsukh" <balgaa@micom.mn>; <freebsd-stable@freebsd.org>
> > Sent: Saturday, October 14, 2006 10:32 PM
> > Subject: Re: em0 problem
> >
> >
> >> Mike Tancsa wrote:
> >>> At 08:09 AM 10/14/2006, Balgansuren Batsukh wrote:
> >>>> Hello,
> >>>>
> >>>> I installed FreeBSD-6.1 on my home PC. After sometime frequently get
> >>>> em0 UP/DOWN message.
> >>>
> >>> There is a patch you can try that might help you at
> >>>
> >>> http://lists.freebsd.org/pipermail/freebsd-stable/2006-October/029224.html
> >>>
> >>> ---Mike
> >>>
> >>
> >> This patch isn't applicable to 6.1, just 6.2-PRE.
> >>
> >> Scott
> >>
> >>
> >>
> >
> > _______________________________________________
> > freebsd-stable@freebsd.org mailing list
> > http://lists.freebsd.org/mailman/listinfo/freebsd-stable
> > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org"
> >
> >
>
> _______________________________________________
> freebsd-stable@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org"
>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?2a41acea0610172031n1058ca06o2792268dc068f479>