lnc0 in VmWare doesn't work
George V. Neville-Neil
gnn at neville-neil.com
Sat Aug 14 09:56:15 PDT 2004
At Sat, 14 Aug 2004 08:33:48 -0700 (PDT),
Vitaly Markitantov wrote:
>
> [1 <text/plain; us-ascii (7bit)>]
> --- Robert Watson <rwatson at freebsd.org> wrote:
>
> >
> > On Sat, 14 Aug 2004, Vitaly Markitantov wrote:
> >
> > > I'm running -CURRENT in VmWare virtual machine.
> > >
> > > Since about August 07 2004 lnc0 interface doesn't work
> > >
> > > I see just complains about:
> > >
> > > lnc0: Device timeout -- Resetting
> > > lnc0: Missed packet -- no receive buffer
> > >
> > > As workaround i use kernel from August 03 2004, which works perfectly
> > > with lnc.
> > >
> > > I attached verbose dmesg from todays kernel.
> >
> > I was chatting with George Neville-Neil about what sounds like an
> > identical problem last. Since you have both old and new kernels, could
> > you try comparing the lnc probe lines in dmesg in the "before" and "after"
> > scenarios, in particular looking for changes in interrupt assignment?
>
> I don't see in dmesg any critical changes in interrupt assigment.
> I provide both dmesg here.
I do note that the ACPI stuff is MPSAFE in one of the dmesg'd and
GIANT LOCKED in the other in the files you sent.
I can't get any files off of my system because without lnc0 it has no
network. I can only get in on the vmware console.
Later,
George
More information about the freebsd-current
mailing list