Dnia Środa, 3 Kwietnia 2013 21:33 Greg KH <gregkh@xxxxxxxxxxxxxxxxxxx> napisał(a) > On Wed, Apr 03, 2013 at 09:02:50PM +0200, Tomasz Miś wrote: > > Dnia Środa, 3 Kwietnia 2013 20:26 Greg KH napisał(a) > > > > > > A: No. > > > Q: Should I include quotations after my reply? > > > > > > http://daringfireball.net/2007/07/on_top > > > > > > On Wed, Apr 03, 2013 at 08:16:47PM +0200, Tomasz Miś wrote: > > > > Welcome. Yes You're right. However, I reported that at this point, > > > > because of the effects it causes. You can not see absolutely no > > > > negative side effects of network solutions. However, there are > > > > "effects" about which I wrote on the USB drive. > > > > > > I agree, but this is not a USB issue, it's a networking / udev issue, > > > there's nothing we can do here. > > > > > > > Established "symptoms" appear both in my kernels [pure vanilla sources > > > > + patch removes the message fail tsc ...] and the mainline kernels for > > > > Ubuntu. > > > > > > This works just fine for me here with a newer version of udev, perhaps > > > your distro needs to update to a more recent version? > > > > > > Again, there's nothing the USB developers can do here, sorry, > > > > > > good luck, > > > > > > greg k-h > > > > That's what I was beginning to suspect - udevd version. But why under > > the rc4 is ok?!?. I just wondered if this irresistible desire to > > remain by Canonical at the "old" udevd = and "not accept" by them > > systemd not rebound soon hiccup ... so I have version 175 udev. But... > > what could be changed between rc4 and rc5 that this effect was made - > > on the side of notifications about USB drives? > > The kernel change is commit 14134f6584212d585b310ce95428014b653dfaf6 if > you are curious. As to why that causes the change in udev, I do not > know, ask the udev and networking developers about this. > > Good luck, > > greg k-h Thank You for response. As for the changes in the kernel ... I follow up changes in git ;) ... but this time I can not even track down where to look. I thought that you show me more precisely the possible search area ;). I rather, try to look for any errors and try to remove them by myself - I submit it, if I can not do it myself - for example, errors in Realtek rts5139 driver [by the way the code of this driver still is "medium" and crashes ehci and sometimes usb-storage after about 1 hour of action]. There are also "mistakes" that I myself repair, but I do not submit it - eg eth driver: Intel: e1000e and IGB and from the 3.9.x kernel in Marvell`s driver ... but they "is revealed" only if the kernel is subjected to optimization [fairly deep] at the level of the compiler. I builds four versions of the kernel for the various machines including version i7 specially optimized for Intel processors [i3, i5 and i7] and Brazos [for newer AMD processors - from Athlon II X4] and publish the Ubuntu community - mainly in Poland. I asked Colleague which works with me on our project [NeteXt'73 - Ubuntu optymizator] to check how the kernel 3.9-rc5 is working [generic from Ubuntu ppa mailine] under Ubuntu 13.04 [under virtual machine] - there is udev in version 175 and libudev in version 198 ... unfortunately again "shows" udevd `errors`. https://dl.dropbox.com/u/72313101/screeny/udevd-fail.png Regards Tomasz Miś -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
