linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bill Moseley <moseley@hank.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: Missing remove event
Date: Thu, 29 Dec 2005 06:59:07 +0000	[thread overview]
Message-ID: <20051229065906.GB24019@hank.org> (raw)
In-Reply-To: <20051229000359.GB15058@hank.org>

On Thu, Dec 29, 2005 at 04:46:47AM +0100, Kay Sievers wrote:
> Does it work if you rmmod the network driver?

I just tried this again, and it didn't hang, but I couldn't bring the
card back up:

Removing the card from the slot did nothing, but then a rmmod prism54
results in what seems like a normal remove:

Dec 28 22:45:33 localhost kernel: eth1: removing device
Dec 28 22:45:33 localhost kernel: eth1: islpci_close ()
Dec 28 22:45:33 localhost dhclient: receive_packet failed on eth1: Network is down
Dec 28 22:45:33 localhost default.hotplug[2926]: remove net
Dec 28 22:45:33 localhost kernel: Unloaded prism54 driver
Dec 28 22:45:33 localhost net.agent[2926]: Invoking ifdown eth1

Then plugging the card back in nothing happens.  Manually running
modprobe prism54 goes through much of the same logging, but the
lights never come on on the wireless card:

Dec 28 22:46:21 localhost moseley: before insert

Then the manual "modeprobe prism54":

Dec 28 22:46:43 localhost kernel: Loaded prism54 driver, version 1.2
Dec 28 22:46:43 localhost kernel: PCI: cache line size of 32 is not supported by device 0000:06:00.0
Dec 28 22:46:43 localhost default.hotplug[2953]: add net
Dec 28 22:46:43 localhost net.ifup[2965]: Invoking ifup eth1=hotplug
Dec 28 22:46:44 localhost dhclient: Internet Software Consortium DHCP Client 2.0pl5
Dec 28 22:46:44 localhost dhclient: Copyright 1995, 1996, 1997, 1998, 1999 The Internet Software Consortium.
Dec 28 22:46:44 localhost dhclient: All rights reserved.
Dec 28 22:46:44 localhost dhclient: 
Dec 28 22:46:44 localhost dhclient: Please contribute if you find this software useful.
Dec 28 22:46:44 localhost dhclient: For info, please visit http://www.isc.org/dhcp-contrib.html
Dec 28 22:46:44 localhost dhclient: 
Dec 28 22:46:44 localhost dhclient: sit0: unknown hardware address type 776
Dec 28 22:46:44 localhost kernel: eth1: islpci_open()
Dec 28 22:46:44 localhost kernel: eth1: resetting device...
Dec 28 22:46:44 localhost kernel: eth1: uploading firmware...
Dec 28 22:46:44 localhost default.hotplug[2985]: add firmware
Dec 28 22:46:44 localhost default.hotplug[2996]: remove firmware
Dec 28 22:46:44 localhost kernel: eth1: firmware uploaded done, now triggering reset...
Dec 28 22:46:45 localhost kernel: eth1: device soft reset timed out
Dec 28 22:46:45 localhost kernel: eth1: timeout waiting for mgmt response 1000, triggering device
Dec 28 22:46:46 localhost kernel: eth1: timeout waiting for mgmt response
Dec 28 22:46:46 localhost kernel: eth1: timeout waiting for mgmt response 1000, triggering device
Dec 28 22:46:47 localhost kernel: eth1: timeout waiting for mgmt response
Dec 28 22:46:47 localhost kernel: eth1: timeout waiting for mgmt response 1000, triggering device
Dec 28 22:46:48 localhost kernel: eth1: timeout waiting for mgmt response
Dec 28 22:46:48 localhost kernel: eth1: timeout waiting for mgmt response 1000, triggering device
Dec 28 22:46:49 localhost kernel: eth1: timeout waiting for mgmt response
Dec 28 22:46:49 localhost kernel: eth1: mgmt tx queue is still full
Dec 28 22:46:49 localhost last message repeated 14 times
Dec 28 22:46:49 localhost kernel: eth1: mgt_commit has failed. Restart the device 
Dec 28 22:46:50 localhost dhclient: sit0: unknown hardware address type 776
Dec 28 22:46:50 localhost dhclient: Listening on LPF/eth1/00:30:b4:00:00:00
Dec 28 22:46:50 localhost dhclient: Sending on   LPF/eth1/00:30:b4:00:00:00




-- 
Bill Moseley
moseley@hank.org



-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_idv37&alloc_id\x16865&op=click
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

  parent reply	other threads:[~2005-12-29  6:59 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-29  0:03 Missing remove event Bill Moseley
2005-12-29  3:46 ` Kay Sievers
2005-12-29  6:50 ` Bill Moseley
2005-12-29  6:59 ` Bill Moseley [this message]
2005-12-30 20:40 ` Bill Moseley
2005-12-30 20:52 ` Kay Sievers
2005-12-30 22:12 ` Bill Moseley
2005-12-30 22:33 ` Kay Sievers

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=20051229065906.GB24019@hank.org \
    --to=moseley@hank.org \
    --cc=linux-hotplug@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).