Opened 11 years ago

Closed 11 years ago

#1668 closed bug (fixed)

Booting fails with nforce driver

Reported by: ekdahl Owned by: axeld
Priority: normal Milestone: R1
Component: Drivers/Network Version: R1/pre-alpha1
Keywords: Cc: nielx
Blocked By: Blocking:
Has a Patch: no Platform: x86

Description

Just tried the nforce network driver and booting fails. I've attached a couple of pictures showing the output.

Image is built with gcc 4 and I have this motherboard: http://global.msi.com.tw/index.php?func=proddesc&prod_no=257 (nForce 430 Chipset)

Attachments (3)

nforce_bt.jpg (441.4 KB) - added by ekdahl 11 years ago.
nforce.jpg (442.1 KB) - added by ekdahl 11 years ago.
nforce_bt.2.jpg (259.2 KB) - added by anevilyak 11 years ago.

Download all attachments as: .zip

Change History (9)

Changed 11 years ago by ekdahl

Attachment: nforce_bt.jpg added

Changed 11 years ago by ekdahl

Attachment: nforce.jpg added

comment:1 Changed 11 years ago by nielx

Cc: nielx added

comment:2 Changed 11 years ago by anevilyak

Mine KDLs as well, with an ASUS A8N-SLI motherboard (nForce4). Working on getting a good shot of the trace now.

Changed 11 years ago by anevilyak

Attachment: nforce_bt.2.jpg added

comment:3 Changed 11 years ago by axeld

Thanks! In ekdahl's back trace, the important lines were missing, but anevilyak's were very useful. Should be fixed in hrev23135, please retry.

comment:4 Changed 11 years ago by ekdahl

It works fine now! I successfully pinged google.com. Thank you!

comment:5 Changed 11 years ago by anevilyak

Works here as well, though sockets do seem to sometimes go dead after a while, i.e. my first try at wgetting Firefox from bebits went dead around 70% and Vision's network threads randomly go dead as well, but...it boots, DHCPs, etc.

Incidentally, this doesn't seem to kill networking as a whole, a new app started still manages to successfully create and use connections.

comment:6 in reply to:  5 Changed 11 years ago by axeld

Resolution: fixed
Status: newclosed

Thanks for the update! The network problems are most likely problems of the stack itself, and not network driver related. I've seen similar problems with various drivers over here (they just happen to disappear when I try to find out why :-)).

Note: See TracTickets for help on using tickets.