Hi everyone, [snip][snip] I've done that poking around and found something that to me looks interesting. Before plugging in a usb stick, I changed udev's log_priority to "debug" (using udevcontrol). Attached is the snippet from /var/log/messages that shows all the diagnostics emitted by udev when the stick was plugged in. (This is with 2.6.26-rc5-git5). You will see that there are several instances of a message about udev unsuccesfully waiting for a file ioerr_cnt to appear deep down in the guts of /sys. Eventually, it does appear, but only after 21 seconds have elapsed. On 2.6.25.6, the file appears almost as soon as udev starts looking for it. The log extract showing this is also attached as is an extract from the kernel log for 2.6.26-rc5-git5. By the way, the main udev-rules file that is installed is the one for slackware that comes with the udev package from kernel.org. So the file these tests were run with are that from udev-122, which I upgraded to earlier this evening (more in hope than expectation :-) -- Beauty is in the eye of the beerholder.
| Greg Kroah-Hartman | [PATCH 006/196] Chinese: add translation of oops-tracing.txt |
| Andrew Morton | Re: -mm merge plans for 2.6.23 -- sys_fallocate |
| Eric W. Biederman | [PATCH] nfs lockd reclaimer: Convert to kthread API |
| James Bottomley | Re: Integration of SCST in the mainstream Linux kernel |
git: | |
| David Miller | [GIT]: Networking |
| Gerrit Renker | [PATCH 03/37] dccp: List management for new feature negotiation |
| David Miller | Re: [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
