Howdy,

I ran into a odd problem.  I'm not sure of the cause. I was trying to
get pictures off my deer trail cameras when I noticed it.  I don't know
if that is related or not.  This is the error.  Including a little over
a second's worth so you can see how fast it is generating these entries
in messages. 


root@fireball / # tail -f /var/log/messages
Jul 10 10:17:21 fireball kernel: ehci-pci 0000:00:12.2: port 3 resume
error -110
Jul 10 10:17:21 fireball kernel: ehci-pci 0000:00:12.2: port 3 resume
error -110
Jul 10 10:17:21 fireball kernel: ehci-pci 0000:00:12.2: port 3 resume
error -110
Jul 10 10:17:21 fireball kernel: ehci-pci 0000:00:12.2: port 3 resume
error -110
Jul 10 10:17:21 fireball kernel: ehci-pci 0000:00:12.2: port 3 resume
error -110
Jul 10 10:17:21 fireball kernel: ehci-pci 0000:00:12.2: port 3 resume
error -110
Jul 10 10:17:21 fireball kernel: ehci-pci 0000:00:12.2: port 3 resume
error -110
Jul 10 10:17:22 fireball kernel: ehci-pci 0000:00:12.2: port 3 resume
error -110
Jul 10 10:17:22 fireball kernel: ehci-pci 0000:00:12.2: port 3 resume
error -110
Jul 10 10:17:22 fireball kernel: ehci-pci 0000:00:12.2: port 3 resume
error -110
Jul 10 10:17:22 fireball kernel: ehci-pci 0000:00:12.2: port 3 resume
error -110
Jul 10 10:17:22 fireball kernel: ehci-pci 0000:00:12.2: port 3 resume
error -110
Jul 10 10:17:22 fireball kernel: ehci-pci 0000:00:12.2: port 3 resume
error -110
Jul 10 10:17:22 fireball kernel: ehci-pci 0000:00:12.2: port 3 resume
error -110
Jul 10 10:17:22 fireball kernel: ehci-pci 0000:00:12.2: port 3 resume
error -110
Jul 10 10:17:22 fireball kernel: ehci-pci 0000:00:12.2: port 3 resume
error -110
Jul 10 10:17:22 fireball kernel: ehci-pci 0000:00:12.2: port 3 resume
error -110
Jul 10 10:17:22 fireball kernel: ehci-pci 0000:00:12.2: port 3 resume
error -110
Jul 10 10:17:22 fireball kernel: ehci-pci 0000:00:12.2: port 3 resume
error -110
Jul 10 10:17:22 fireball kernel: ehci-pci 0000:00:12.2: port 3 resume
error -110
Jul 10 10:17:22 fireball kernel: ehci-pci 0000:00:12.2: port 3 resume
error -110
Jul 10 10:17:22 fireball kernel: ehci-pci 0000:00:12.2: port 3 resume
error -110
Jul 10 10:17:22 fireball kernel: ehci-pci 0000:00:12.2: port 3 resume
error -110
Jul 10 10:17:22 fireball kernel: ehci-pci 0000:00:12.2: port 3 resume
error -110
Jul 10 10:17:22 fireball kernel: ehci-pci 0000:00:12.2: port 3 resume
error -110
Jul 10 10:17:22 fireball kernel: ehci-pci 0000:00:12.2: port 3 resume
error -110
Jul 10 10:17:22 fireball kernel: ehci-pci 0000:00:12.2: port 3 resume
error -110
Jul 10 10:17:22 fireball kernel: ehci-pci 0000:00:12.2: port 3 resume
error -110
Jul 10 10:17:22 fireball kernel: ehci-pci 0000:00:12.2: port 3 resume
error -110
Jul 10 10:17:22 fireball kernel: ehci-pci 0000:00:12.2: port 3 resume
error -110
Jul 10 10:17:22 fireball kernel: ehci-pci 0000:00:12.2: port 3 resume
error -110
Jul 10 10:17:22 fireball kernel: ehci-pci 0000:00:12.2: port 3 resume
error -110
Jul 10 10:17:22 fireball kernel: ehci-pci 0000:00:12.2: port 3 resume
error -110
Jul 10 10:17:22 fireball kernel: ehci-pci 0000:00:12.2: port 3 resume
error -110
Jul 10 10:17:22 fireball kernel: ehci-pci 0000:00:12.2: port 3 resume
error -110
Jul 10 10:17:22 fireball kernel: ehci-pci 0000:00:12.2: port 3 resume
error -110
Jul 10 10:17:22 fireball kernel: ehci-pci 0000:00:12.2: port 3 resume
error -110
Jul 10 10:17:22 fireball kernel: ehci-pci 0000:00:12.2: port 3 resume
error -110
Jul 10 10:17:22 fireball kernel: ehci-pci 0000:00:12.2: port 3 resume
error -110
Jul 10 10:17:22 fireball kernel: ehci-pci 0000:00:12.2: port 3 resume
error -110
Jul 10 10:17:22 fireball kernel: ehci-pci 0000:00:12.2: port 3 resume
error -110
Jul 10 10:17:22 fireball kernel: ehci-pci 0000:00:12.2: port 3 resume
error -110
Jul 10 10:17:22 fireball kernel: ehci-pci 0000:00:12.2: port 3 resume
error -110
Jul 10 10:17:22 fireball kernel: ehci-pci 0000:00:12.2: port 3 resume
error -110
Jul 10 10:17:22 fireball kernel: ehci-pci 0000:00:12.2: port 3 resume
error -110
Jul 10 10:17:22 fireball kernel: ehci-pci 0000:00:12.2: port 3 resume
error -110
Jul 10 10:17:23 fireball kernel: ehci-pci 0000:00:12.2: port 3 resume
error -110
Jul 10 10:17:23 fireball kernel: ehci-pci 0000:00:12.2: port 3 resume
error -110


I did my usual updates the other day but not real sure how long this has
been going on but log rotate seems to have been busy. The only way I
found to stop it, stop the syslog service.  I did go to boot runlevel
and restart udev and other device related services.  As soon as syslog
starts up, it starts posting that error in messages.  Also, I'm using
the same kernel for several months with no problems. I'm on
5.14.15-gentoo with a uptime of over 4 months.  Based on log rotation,
I'd say this started about the time I did my updates in the last couple
days.  Give or take. Can't recall command to get last weeks worth of updates.  Brain freeze. 

I tried google and found nothing helpful.  Anyone have a idea what this
is all about?  Any clues?

Thanks.

Dale

:-)  :-) 

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Sunday, 10 July 2022 16:34:08 BST Dale wrote:

Howdy,

I ran into a odd problem. I'm not sure of the cause. I was trying to
get pictures off my deer trail cameras when I noticed it. I don't know
if that is related or not. This is the error. Including a little over
a second's worth so you can see how fast it is generating these entries
in messages.

root@fireball / # tail -f /var/log/messages
Jul 10 10:17:21 fireball kernel: ehci-pci 0000:00:12.2: port 3 resume
error -110

[snip ...]

I did my usual updates the other day but not real sure how long this has
been going on but log rotate seems to have been busy. The only way I
found to stop it, stop the syslog service. I did go to boot runlevel
and restart udev and other device related services. As soon as syslog
starts up, it starts posting that error in messages. Also, I'm using
the same kernel for several months with no problems. I'm on
5.14.15-gentoo with a uptime of over 4 months. Based on log rotation,
I'd say this started about the time I did my updates in the last couple
days. Give or take. Can't recall command to get last weeks worth of
updates. Brain freeze.

I tried google and found nothing helpful. Anyone have a idea what this
is all about? Any clues?

Thanks.

Dale

:-) :-)

dmesg ought to show a similar error. The kernel is trying to read whatever is hanging off your ehci-pci port 3 and it times out. The error message means "Timeout expired before the transfer completed". It could be a problematic device controller, or power demands of the device exceed what the MoBo supplies.

I've seen the same on USB 3.0 sticks which failed soon after, so you may want to back up your data in the first instance.
-----BEGIN PGP SIGNATURE-----

iQIzBAABCAAdFiEEXqhvaVh2ERicA8Ceseqq9sKVZxkFAmLK/w8ACgkQseqq9sKV ZxnOBRAAro1ISY7Oz9wZgHa0cabFU7W0gX1a+6zH+DqG7E/+eSr2QFBxDqzsG9J+ zIcsENWRfPu1C129EdJ5k/CLcw8GoZElIT+2Nc8YDG1BgB4AOfEQqCUsn4TATLfA i1NCNpODMHWsHTkDRzVYosTMLYqJFAOct4UWQICZpP9iZuQ8N3Nv0It2b4/EgcFs TrAlogcQNY5Oe41xBu8ZLHrdhD4L4tpreky4QDFiPz9VTvN59/w2cTu5NulHYcJf 0WRb9V/x1GQyn429zcFPV0QiZgRFGeSlbA1/kKrFmdEOZriwJFoAiG5WAMYTnZWU ew+kQeHUQM2AW31ut7ZIzng3J2mpnTgaeiZ/SQ4VY7uB/I9akkoGEoz13DdcvYoc oQgO+wgNq17pXacMZ1my6yJ5zPUxnEaWnt4fzgP/M+iXDqtZ+RgaUkUiPlaJfgi3 3wrAD7DKjLEUf14YivzGVxKBUmOc5TIOTzVhhFgkz7+qeaZVu8wmjzM5ZuCpnQqU 3ZYNPk95UCxzHx6kBAF5Qo+0pVZwefzPW+sWASMoLGXEDSoMJnBmcyVlZnSdCGow W7UrncgEaW8WhBk8XM99viVeucqm/h088kfjZm/sFLZPov9aRBLiFThMWqVonQDY EbfD9mvm+g8Ik33NXYwUSz2xQJUixx4zgdFNKuAAEwVNHwCqq90=
=8OHf
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Sunday, 10 July 2022 18:13:24 BST Dale wrote:

Michael wrote:

On Sunday, 10 July 2022 16:34:08 BST Dale wrote:

Howdy,

I ran into a odd problem. I'm not sure of the cause. I was trying to
get pictures off my deer trail cameras when I noticed it. I don't know
if that is related or not. This is the error. Including a little over
a second's worth so you can see how fast it is generating these entries
in messages.


root@fireball / # tail -f /var/log/messages
Jul 10 10:17:21 fireball kernel: ehci-pci 0000:00:12.2: port 3 resume
error -110

[snip ...]

I did my usual updates the other day but not real sure how long this has >> been going on but log rotate seems to have been busy. The only way I
found to stop it, stop the syslog service. I did go to boot runlevel
and restart udev and other device related services. As soon as syslog
starts up, it starts posting that error in messages. Also, I'm using
the same kernel for several months with no problems. I'm on
5.14.15-gentoo with a uptime of over 4 months. Based on log rotation,
I'd say this started about the time I did my updates in the last couple
days. Give or take. Can't recall command to get last weeks worth of
updates. Brain freeze.

I tried google and found nothing helpful. Anyone have a idea what this
is all about? Any clues?

Thanks.

Dale

:-) :-)

dmesg ought to show a similar error. The kernel is trying to read
whatever is hanging off your ehci-pci port 3 and it times out. The error message means "Timeout expired before the transfer completed". It could
be a problematic device controller, or power demands of the device exceed what the MoBo supplies.

I've seen the same on USB 3.0 sticks which failed soon after, so you may want to back up your data in the first instance.

I found this info:

00:12.2 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB EHCI Controller

Right now, I don't have a lot of USB in use. Mouse, UPS and a card
reader, which I just unplugged with no change. This is my USB devices now:

root@fireball / # lsusb
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 002: ID 046d:c077 Logitech, Inc. Mouse
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 007: ID 0764:0501 Cyber Power System, Inc. CP1500 AVR UPS
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 009 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 008 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
Bus 008 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
root@fireball / #

Is there anyway to figure out which part is causing this? I hope it
isn't my UPS. I got a spare rodent if it is that. Oh, any way to stop
it from filling dmesg? It's spitting it out pretty fast. o_O

Thoughts?

Dale

:-) :-)

Does lsusb shed some light to the port which causes the interruptions? Otherwise can you unplug devices and plug them in one at a time?
-----BEGIN PGP SIGNATURE-----

iQIzBAABCAAdFiEEXqhvaVh2ERicA8Ceseqq9sKVZxkFAmLLDrYACgkQseqq9sKV ZxkQYhAAh2NKw+xa7vjSEm/hW3E3f4aNQBe/0Tz+Lah3LwQinxQ3H1sPGYJrU1+/ 3Hy2PB3m3IcmCiduVmulEdc4z4ryFfWy0ve00eu4ja3EpplGwXHvI4QxxLNmMJhy XmvR27NdHygb8oB2oJrxgyjmliPzPZJKxQC/HWgVI4NS0H3oQSeMji76lSNgcRzZ CZrPJNl1AzS3uKS4c4tBMmLR3V2d09V1Y4x1kiufI9rnY0bVNj6/I/vjC8vbiEDM 262M/p6+qgJyLXXCsI49xZIm2rqRBlfiNxFZ63GKyse3+XE+c0NTHTGWkU2iqIqN jept3cJDmmTndR7e6rNJGYM7YaeIwycjUCoXOoYuLuyX1gs2ycIPW6dawUAj+7gr beGoWyuiJGmX8tbmO9LwVa9a8kpFf++DyX3kNyRz5GRNGNyM6mO+13DyYrjoAHdC ANE9CdwrelXOZRgweUj3cSD8fuGx7/mb4hzwzDDNu2E4dSzf42Vrw0mXCWCwfVhG Qy9YU17MudMZBWYGgXtrd3K/l9KQ3WbzPvDN3YV5MBvGGevCpixmJogm10RePg/4 Lp/8vVPGmZwuszK8dE6DFBiGOnMnAt2ssZJoaPTkhafD2z1xut3EAdwaIdoWocWP myHUI06ao2lNTejyTMgZSVpTT9+nRk/kPgTVxd8bjt0d5n0/CSw=
=Ew9Y
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Sunday, 10 July 2022 18:39:02 BST Michael wrote:

Does lsusb shed some light to the port which causes the interruptions? Otherwise can you unplug devices and plug them in one at a time?

Oops, I meant to say, 'lsusb -t' or check usbview, or in your Plasma check System > Info Center > Devices > EHCI Host Controller and/or USB Devices. -----BEGIN PGP SIGNATURE-----

iQIzBAABCAAdFiEEXqhvaVh2ERicA8Ceseqq9sKVZxkFAmLLEQIACgkQseqq9sKV ZxmiihAAh3bbGqJFUAZG+rCOlCUaMXtzr66FrhEjeZg6bBgXzP3j9UXwjstFd/KN C3Z2RiR+QYdVnwooeLWzL+RObMHrv3eS2EVSSb2NwqMKU/xaP3n4eaktvsOgjkK9 rpZHRkLfMjfFZPHBXzSuQV5/9lWO0Npun+0LcVW5hsDDCDq1dPg7jlGBpsZaNVre R/EvE+rl6t8Pvc/3BkmCBqwgtU8jZIxZfOIGzLbwkuawlPq7WQVPfg7IbgYRDQb/ 06f48YY8Kur593ri5BKfBLZ53X8D6jhyhzsMmv/9WDlJpZSESRquOoFMGTG0gBui zdAepT5mF4DfePT2pToLuFmTWYU+NcHXJ0MW7ropepFgDHJnKECtOqvp6ATEcS1i /OJi5Ug6K4LL0KxmPkacpbBt48m6HpAqhEnrVAe36iR9tVt3UK+3BkpdJjcaGZZS FQGLIjFQ1r7WKlFx5zvlrETg1dSIP3rdAxrNL6uYvUdCs+zmkwz/bHI9vt6ZGVn6 QVeLppec+HkpueUsGg5SQoSKnY50zIik7+Qi7iaphXh0I0G8OezxnnSpH8OtiFEV RYMALRRTSKdIHtQ5DRsw6YKfr0vQROu7MQxJiGeUVxqx83kwWtW3/qOji+Ot5PDf z6b4V4j2egDvsJhmAqOAaKaK2C0IMPGkrylX8l3nc2Bcfyw8Mx8=
=RGzU
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Michael wrote:

On Sunday, 10 July 2022 16:34:08 BST Dale wrote:

Howdy,

I ran into a odd problem. I'm not sure of the cause. I was trying to
get pictures off my deer trail cameras when I noticed it. I don't know
if that is related or not. This is the error. Including a little over
a second's worth so you can see how fast it is generating these entries
in messages.


root@fireball / # tail -f /var/log/messages
Jul 10 10:17:21 fireball kernel: ehci-pci 0000:00:12.2: port 3 resume
error -110

[snip ...]

I did my usual updates the other day but not real sure how long this has
been going on but log rotate seems to have been busy. The only way I
found to stop it, stop the syslog service. I did go to boot runlevel
and restart udev and other device related services. As soon as syslog
starts up, it starts posting that error in messages. Also, I'm using
the same kernel for several months with no problems. I'm on
5.14.15-gentoo with a uptime of over 4 months. Based on log rotation,
I'd say this started about the time I did my updates in the last couple
days. Give or take. Can't recall command to get last weeks worth of
updates. Brain freeze.

I tried google and found nothing helpful. Anyone have a idea what this
is all about? Any clues?

Thanks.

Dale

:-) :-)

dmesg ought to show a similar error. The kernel is trying to read whatever is
hanging off your ehci-pci port 3 and it times out. The error message means "Timeout expired before the transfer completed". It could be a problematic device controller, or power demands of the device exceed what the MoBo supplies.

I've seen the same on USB 3.0 sticks which failed soon after, so you may want to back up your data in the first instance.

I found this info:


00:12.2 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB EHCI Controller


Right now, I don't have a lot of USB in use.  Mouse, UPS and a card
reader, which I just unplugged with no change.  This is my USB devices now:


root@fireball / # lsusb
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 002: ID 046d:c077 Logitech, Inc. Mouse
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 007: ID 0764:0501 Cyber Power System, Inc. CP1500 AVR UPS
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 009 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 008 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
Bus 008 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
root@fireball / #


Is there anyway to figure out which part is causing this?  I hope it
isn't my UPS.  I got a spare rodent if it is that.  Oh, any way to stop
it from filling dmesg?  It's spitting it out pretty fast. o_O

Thoughts?

Dale

:-)  :-) 

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Michael wrote:

On Sunday, 10 July 2022 18:39:02 BST Michael wrote:

Does lsusb shed some light to the port which causes the interruptions?
Otherwise can you unplug devices and plug them in one at a time?

Oops, I meant to say, 'lsusb -t' or check usbview, or in your Plasma check System > Info Center > Devices > EHCI Host Controller and/or USB Devices.

Well, I didn't know if it would help or not but I rebooted.  I
remembered I built a new kernel a while back and wanted to test it
anyway.  Of course, that kernel had some issues and I had to revert back
to old kernel.  Anyway, after rebooting, it isn't doing it.  At least it isn't doing it right now.  It may start up again if I do something to
trigger it again.  Maybe it was a update that went sideways and I'm good
for a long time.  Who knows.  At least the smoke didn't get out and
break something.  ;-)

If it starts up again shortly, I'll post again.  At least this should
rule out my UPS and mouse.  Very good thing on the UPS. 

Thanks much.

Dale

:-)  :-) 

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)