On 04/10/2013 18:09, Dale wrote: > Sometime last night while I was sleeping, my network sort of hiccuped. > If I went to a Konsole, I could ping google so it appears the network > was working on the lower level but not one browser that was left open > would work. It also didn't/couldn't download new emails. When I > restarted the browser, it worked. This is the case for both Seaminkey > and Firefox. If it was just one, I'd think browser issue but not two of > them at the same time. This is a example of what is in my messages file: > > Sep 29 03:10:15 localhost kernel: [382175.585718] ohci_hcd 0000:00:12.1: > urb ffff88034092b0c0 path 1 ep1in 93120000 cc 9 --> status -121 > Sep 29 03:10:17 localhost kernel: [382177.582033] ohci_hcd 0000:00:12.1: > urb ffff8803f06a9d40 path 1 ep1in 92120000 cc 9 --> status -121 > Sep 29 03:10:19 localhost kernel: [382179.586285] ohci_hcd 0000:00:12.1: > urb ffff8803f06a9680 path 1 ep1in 93120000 cc 9 --> status -121 > Sep 29 03:10:21 localhost kernel: [382181.582602] ohci_hcd 0000:00:12.1: > urb ffff8803f06a9680 path 1 ep1in 92120000 cc 9 --> status -121 > Sep 29 03:10:23 localhost kernel: [382183.586879] ohci_hcd 0000:00:12.1: > urb ffff8803f06a9680 path 1 ep1in 93120000 cc 9 --> status -121
What I read from your description is that Seamonkey and Firefox hiccuped and everything else either works or was not tested. Assuming that those browsers share lots of common code - see where I'm going with this? The entries in your messages file may or may not be relevant, and if they are relevant it will be as a side effect. OHCI is a USB 1.1 implementation, I can't imagine why you have it loaded. Surely you do not have USB 1 only hardware? USB2 deals with that nicely. It is possible that you have a shit storm of USB weirdness going on and this in locking up the desktop. Try disabling USB stuff you don't need and see what gives. > > I did a google search but obviously not direct hits so I had to adjust > things until I got some hits. I removed for example the time stamp and > lots of other unigue things to my system. The closest hit I got was > three years ago and it's not the same even allowing for the stuff that > will change. So, google was no help. > > I did a update last night. It updated the kernel sources but I haven't > touched it yet. It updated the virtual for udev and nvidia-drivers > which I am using at the moment. The only one I see that could possibly > affect this is the udev one but I don't think it is likely since it is a > virtual and the actual dev package didn't change. > > By the way, I use checkrestart after updates. If needed, I go to boot > runlevel and restart whatever else is needed to get a clean output. I > did rmmod nvidia and modprobe nvidia last night. I'm hoping this driver > will not cause my kicker thingy to lock up like the last dozen or so > has. :/ > > Keep in mind, the network worked in a Konsole. It appears to me it was > KDE and/or things running inside of KDE and a regular user that had > issues. I only checked my Seamonkey and Firefox and they did not work > until they was restarted. My grand fix was to log out and log back in > again. > > I just checked again, I am still getting the errors above even tho the > browsers are working. The error above may not be related to this. Sort > of confusing at the moment. > > Kernel problem? KDE problem? Some USB error? Something else? Thoughts? > > Dale > > :-) :-) > > P. S. This is what I get while restarting my network service: > > Oct 4 10:27:13 localhost kernel: [839575.429674] ohci_hcd 0000:00:12.1: > urb ffff8802f06dc240 path 1 ep1in 93120000 cc 9 --> status -121 > Oct 4 10:27:15 localhost kernel: [839577.425964] ohci_hcd 0000:00:12.1: > urb ffff8802f06dc240 path 1 ep1in 92120000 cc 9 --> status -121 > Oct 4 10:27:17 localhost kernel: [839579.430267] ohci_hcd 0000:00:12.1: > urb ffff8802f06dc6c0 path 1 ep1in 93120000 cc 9 --> status -121 > Oct 4 10:27:17 localhost sshd[8316]: Received signal 15; terminating. > Oct 4 10:27:17 localhost kernel: [839580.289194] r8169 0000:03:00.0 > eth0: link down > Oct 4 10:27:17 localhost kernel: [839580.289204] r8169 0000:03:00.0 > eth0: link down > Oct 4 10:27:17 localhost kernel: [839580.289256] IPv6: > ADDRCONF(NETDEV_UP): eth0: link is not ready > Oct 4 10:27:18 localhost sshd[8692]: Server listening on 0.0.0.0 port 22. > Oct 4 10:27:18 localhost sshd[8692]: Server listening on :: port 22. > Oct 4 10:27:19 localhost kernel: [839581.426532] ohci_hcd 0000:00:12.1: > urb ffff88042086ac00 path 1 ep1in 92120000 cc 9 --> status -121 > Oct 4 10:27:19 localhost kernel: [839582.327590] r8169 0000:03:00.0 > eth0: link up > Oct 4 10:27:19 localhost kernel: [839582.327599] IPv6: > ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready > Oct 4 10:27:21 localhost kernel: [839583.430811] ohci_hcd 0000:00:12.1: > urb ffff8802f06dc6c0 path 1 ep1in 93120000 cc 9 --> status -121 > Oct 4 10:27:22 localhost kernel: [839584.527264] r8169 0000:03:00.0 > eth0: link down > Oct 4 10:27:23 localhost kernel: [839585.427127] ohci_hcd 0000:00:12.1: > urb ffff880410612900 path 1 ep1in 92120000 cc 9 --> status -121 > Oct 4 10:27:23 localhost kernel: [839586.105999] r8169 0000:03:00.0 > eth0: link up > Oct 4 10:27:25 localhost kernel: [839587.431380] ohci_hcd 0000:00:12.1: > urb ffff880410612900 path 1 ep1in 93120000 cc 9 --> status -121 > Oct 4 10:27:27 localhost kernel: [839589.427672] ohci_hcd 0000:00:12.1: > urb ffff880410612900 path 1 ep1in 92120000 cc 9 --> status -121 > > I'm thinking the error is not related to network since on e of them is > while the network was down. I'm glad that logrotate is working well. O_O > -- Alan McKinnon alan.mckin...@gmail.com
