From: Bill Moseley <moseley@hank.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: Missing remove event
Date: Thu, 29 Dec 2005 06:50:21 +0000 [thread overview]
Message-ID: <20051229065021.GA24019@hank.org> (raw)
In-Reply-To: <20051229000359.GB15058@hank.org>
On Thu, Dec 29, 2005 at 04:46:47AM +0100, Kay Sievers wrote:
> What does:
> cat /proc/net/dev
Inter-| Receive | Transmit
face |bytes packets errs drop fifo frame compressed multicast|bytes packets errs drop fifo colls carrier compressed
lo: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
eth0: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
sit0: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
eth1: 58118 291 0 0 0 0 0 0 30980 340 0 0 0 0 0 0
> and:
> ls -l /sys/class/net
> show in that case?
drwxr-xr-x 3 root root 0 2005-12-28 22:22 eth0
drwxr-xr-x 4 root root 0 2005-12-28 22:24 eth1
drwxr-xr-x 3 root root 0 2005-12-28 22:22 lo
drwxr-xr-x 3 root root 0 2005-12-28 22:22 sit0
It's as if the card was not removed, it seems.
Perhaps a red herring, but as I mentioned, I'm not using ACPI[1]. For a
minute I thought the problem was related to not having the apm module
loaded -- because when I first posted apm was not loaded and card
ejects were not generating events. And just a minute ago apm was
loaded and card eject events where happening.
But after trying a few times it seems unrelated to having apm loaded
or not. Seems a bit random. Debugging is a bit slow, having to
reboot each time. So I don't have a huge sample size.
Dec 28 22:19:02 localhost kernel: eth1: hot unplug detected
Dec 28 22:19:02 localhost kernel: eth1: removing device
Dec 28 22:19:02 localhost kernel: eth1: islpci_close ()
Dec 28 22:19:02 localhost dhclient: receive_packet failed on eth1: Network is down
Dec 28 22:19:03 localhost default.hotplug[3337]: remove net
Dec 28 22:19:03 localhost net.agent[3337]: Invoking ifdown eth1
Dec 28 22:19:03 localhost default.hotplug[3356]: remove pci
> Does it work if you rmmod the network driver?
Well, I did a rmmod prism54 once today and rmmod hung -- rmmod was
eathing 95% CPU and I couldn't kill -9 it. Clearly getting in a
confused state.
[1] The reason I'm not using ACPI is because my wireless card doesn't
seem to work with acpi. With acpi enabled I get this when trying to
run the card:
ACPI: PCI interrupt 0000:06:00.0[A]: no GSI
eth1 could not install IRQ handler
prism54: probe of 0000:06:00.0 failed with -5
BTW -- I did flash the laptop's bios today, just to make sure it was
up to date. Just in case.
--
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
next prev parent reply other threads:[~2005-12-29 6:50 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 [this message]
2005-12-29 6:59 ` Bill Moseley
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=20051229065021.GA24019@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).