Date: Thu, 19 Oct 2006 00:29:14 -0700 From: John-Mark Gurney <gurney_j@resnet.uoregon.edu> To: Yuriy Tsibizov <Yuriy.Tsibizov@gfk.ru> Cc: current@freebsd.org Subject: Re: ASUS U5F hangs during pci bus probe Message-ID: <20061019072914.GP23971@funkthat.com> In-Reply-To: <78664C02FF341B4FAC63E561846E3BCC01F8C1@ex.hhp.local> References: <78664C02FF341B4FAC63E561846E3BCC01F8B9@ex.hhp.local> <78664C02FF341B4FAC63E561846E3BCC01F8C1@ex.hhp.local>
next in thread | previous in thread | raw e-mail | index | archive | help
Yuriy Tsibizov wrote this message on Thu, Oct 19, 2006 at 10:48 +0400:
> > > > This is likely due to invalid VPD data on your system... Add a:
> > > > printf("reading vpd...\n");
> > > >
> > > > to just before the comment:
> > > > /* init vpd reader */
> > > >
> > > > if this is the last thing you see printed then it is due
> > to the new
> > > > VPD code... I have identified on problem w/ the code, and
> > > have posted
> > > > the patch to cvs-all, if you are interested in testing
> > it, I'll send
> > > > you a copy, though your problem could be different, and we
> > > > need do some
> > > > debugging to find out what it is...
> >
> > Yes, it keeps running in "for (; !end;)" loop forever. I'll
> > have access
> > to this notebook till friday evening.
>
> Just checked it today morning - it cannot start Ethernet adapter after
> last reboot...
> It lists it in POST message, but
> 1) don't start PXE firmware
> 2) can't see it with pre-installed Windows (It show unknown Ethernet,
> with vendor 10ec dev 8129 subsys 812911ec revision 01). It's PCI express
> network card, according to POST message.
> 3) link is active
>
> I have two more noteboks (same model), but don't want to kill their
> Ethernet adapters.
So, are you saying that after using the fixed patch, booting into
FreeBSD (getting to login), that the Windows no longer attached to the
on board ethernet adapter? Considering that this patch doesn't even
touch the read-write data, I can't imagine it breaking something, unless
the driver and other code can't handle the VPD registers being touched...
But if that's the case, then the Windows driver needs to be fixed since
there are no guaranties what the VPD registers will be...
--
John-Mark Gurney Voice: +1 415 225 5579
"All that I will do, has been done, All that I have, has not."
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20061019072914.GP23971>