Date: Sat, 14 Aug 2004 09:55:11 -0700 From: "George V. Neville-Neil" <gnn@neville-neil.com> To: Vitaly Markitantov <ua_vitaly@yahoo.com> Cc: current@freebsd.org Subject: Re: lnc0 in VmWare doesn't work Message-ID: <m2wu01d5hs.wl@minion.local.neville-neil.com> In-Reply-To: <20040814153348.20497.qmail@web13425.mail.yahoo.com> References: <Pine.NEB.3.96L.1040814103541.99198B-100000@fledge.watson.org> <20040814153348.20497.qmail@web13425.mail.yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
At Sat, 14 Aug 2004 08:33:48 -0700 (PDT), Vitaly Markitantov wrote: > > [1 <text/plain; us-ascii (7bit)>] > --- Robert Watson <rwatson@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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?m2wu01d5hs.wl>