I have submitted my dmesg to to the email address. I have recently updated to -current which appears to have solved the issue, im guessing the PR you pointed to was the culprit.
Ill test it more thoroughly and report back if anything else is wrong. On 11/6/07, Chris Kuethe <[EMAIL PROTECTED]> wrote: > On 11/6/07, Chris Harper <[EMAIL PROTECTED]> wrote: > > ... > > nfe0 at pci0 dev 17 function 0 "NVIDIA MCP55 LAN" rev 0xa2: apic 4 int > > 5 (irq 5), address 04:4b:80:80:80:03 > > eephy0 at nfe0 phy 1: Marvell 88E1116 Gigabit PHY, rev. 1 > > nfe1 at pci0 dev 18 function 0 "NVIDIA MCP55 LAN" rev 0xa2: apic 4 int > > 5 (irq 5), address 04:4b:80:80:80:04 > > eephy1 at nfe1 phy 2: Marvell 88E1116 Gigabit PHY, rev. 1 > > http://marc.info/?l=openbsd-cvs&m=119158015415363&w=2 > > It's possible that this may fix your problem. you might be able to get > away with just downloading a new kernel and booting that. it may be > possible to ifconfig the interface up to see if it auto-negotiates > properly. running for any length of time with mismatched kernel and > userland is usually a recipe for pain though. > > It's kind of surprising to see an intel cpu with an nvidia chipset. if > you don't mind and haven't already done so, you might want to mail > this in to "[EMAIL PROTECTED]". we often go trolling through the dmesg > archives for odd hardware combinations, new devices, and testers for > risky changes... > > CK > > -- > GDB has a 'break' feature; why doesn't it have 'fix' too?
