netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Garzik <jeff@garzik.org>
To: Chris Holvenstot <cholvenstot@comcast.net>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	netdev <netdev@vger.kernel.org>
Subject: Re: Network failure with 2.6.23-git14
Date: Fri, 19 Oct 2007 12:28:34 -0400	[thread overview]
Message-ID: <4718DB32.5000404@garzik.org> (raw)
In-Reply-To: <1192790946.6416.4.camel@localhost>

Chris Holvenstot wrote:
> I built 2.6.23-git14 this morning - when booted I can not access the
> network via my Ethernet connection.  Fallback to 2.6.23-git11 works OK.
> One interesting message during boot:

> [   37.325760] forcedeth: Reverse Engineered nForce ethernet driver.
> [   37.843618] forcedeth 0000:00:0a.0: ifname eth0, PHY OUI 0x5043 @ 1,
> addr 00:19:db:6d:3f:1b
> [   37.843623] forcedeth 0000:00:0a.0: highdma csum timirq gbit lnktim
> desc-v3

> [   46.414433] sysfs: duplicate filename 'eth1' can not be created
> [   46.414438] WARNING: at fs/sysfs/dir.c:424 sysfs_add_one()
> [   46.414445]  [<c01ba80f>] sysfs_add_one+0x9f/0xe0
> [   46.414456]  [<c01bb5c6>] sysfs_create_link+0x86/0x110
> [   46.414462]  [<c025608a>] device_rename+0x17a/0x1e0
> [   46.414467]  [<c0130190>] run_timer_softirq+0x30/0x180
> [   46.414472]  [<c0287a60>] dev_change_name+0xb0/0x200
> [   46.414476]  [<c0159a62>] filemap_fault+0x1f2/0x400
> [   46.414478]  [<c012c895>] __do_softirq+0x75/0xf0
> [   46.414484]  [<c027a260>] sock_ioctl+0x0/0x230
> [   46.414487]  [<c028809c>] dev_ioctl+0x25c/0x520
> [   46.414489]  [<c01646eb>] __do_fault+0x1ab/0x380
> [   46.414494]  [<c0165d28>] handle_mm_fault+0xf8/0x610
> [   46.414499]  [<c027a260>] sock_ioctl+0x0/0x230
> [   46.414502]  [<c018343b>] do_ioctl+0x2b/0x90
> [   46.414506]  [<c01834fc>] vfs_ioctl+0x5c/0x290
> [   46.414510]  [<c0183798>] sys_ioctl+0x68/0x80
> [   46.414513]  [<c01041de>] sysenter_past_esp+0x5f/0x85
> [   46.414520]  =======================
> [   46.414523] net eth1: device_rename: sysfs_create_symlink failed


What are your network devices?  Is your problem with eth0, forcedeth, or 
as this traceback implies, eth1?

What is eth1?  (driver, bus, ...)

Can you bisect?

	Jeff




       reply	other threads:[~2007-10-19 16:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1192790946.6416.4.camel@localhost>
2007-10-19 16:28 ` Jeff Garzik [this message]
2007-10-19 18:28   ` Network failure with 2.6.23-git14 Chris Holvenstot

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4718DB32.5000404@garzik.org \
    --to=jeff@garzik.org \
    --cc=cholvenstot@comcast.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).