Anybody have any idea as to why it is exactly 50 minutes?
What id it that may be so special about 50 minutes?
Mon Jan 9 12:28:08 2023] usb 2-1.4: reset high-speed USB device
number 7 using ehci-pci
I am guessing that there is some hardware issue with this device.
Mon Jan 9 12:28:08 2023] usb 2-1.4: reset high-speed USB device number 7 using ehci-pci
I am guessing that there is some hardware issue with this device. The
thing is, that kind of diagnostic is logged by the kernel exactly every
50 minutes. Let me emphasize this: exactly every 3,000 seconds. Not
3,001, or 2,999, but 3,000.
Anybody have any idea as to why it is exactly 50 minutes? What id
it that may be so special about 50 minutes?
James H. Markowitz <noone@nowhere.net> wrote:
Mon Jan 9 12:28:08 2023] usb 2-1.4: reset high-speed USB device
number 7 using ehci-pci
I am guessing that there is some hardware issue with this device. The
thing is, that kind of diagnostic is logged by the kernel exactly every
50 minutes. Let me emphasize this: exactly every 3,000 seconds. Not
3,001, or 2,999, but 3,000.
Anybody have any idea as to why it is exactly 50 minutes? What id
it that may be so special about 50 minutes?
It could be some kind of communication difficulty, which could be a hardware issue or noisy cabling or something else. Do you have any electrical appliances which might kick in on a 50 minute frequency? If there was a nearby motor or something and you had a bad USB cable, that might cause enough to disrupt communication.
Try changing the cable?
I tried on a different system with a different cable and at a
different location, and the same diagnostic keeps getting logged, with
the same frequency. I'll try disabling ehci_pci.
From
https://access.redhat.com/solutions/194273
"This error indicates that USB 2.0 may not function on your system, or may function only at USB 1.1 speeds."
See https://bbs.archlinux.org/viewtopic.php?id=89688 for disabling ehci-pci.
On Thu, 12 Jan 2023 14:21:23 -0500, James H. Markowitz
<noone@nowhere.net> wrote:
I tried on a different system with a different cable and at a
different location, and the same diagnostic keeps getting logged, with
the same frequency. I'll try disabling ehci_pci.
If that doesn't resolve the issue, try disabling pci power management
instead as the power management may be affecting the usb controller. To
do so add the kernel boot parameter's "pcie_port_pm=off pcie_aspm=off".
On Thu, 12 Jan 2023 18:32:53 -0500, David W. Hodgins wrote:
On Thu, 12 Jan 2023 14:21:23 -0500, James H. Markowitz
<noone@nowhere.net> wrote:
I tried on a different system with a different cable and at a
different location, and the same diagnostic keeps getting logged, with
the same frequency. I'll try disabling ehci_pci.
If that doesn't resolve the issue, try disabling pci power management
instead as the power management may be affecting the usb controller. To
do so add the kernel boot parameter's "pcie_port_pm=off pcie_aspm=off".
Not only did it not solve anything, but it created major
problems, for I forgot I have a wireless keyboard/mouse combo that relies
on it. Fortunately, I could access the system over ssh and re-enable ehci_pci.
At this point I am satisfied (well, not quite satisfied, but you
know what I mean) that the drive itself is dodgy.
I have an external USB hard drive connected to a Linux system.
When I invoke dmesg -T I get diagnostics like the following:
Mon Jan 9 12:28:08 2023] usb 2-1.4: reset high-speed USB device number 7 using ehci-pci
I am guessing that there is some hardware issue with this device. The
thing is, that kind of diagnostic is logged by the kernel exactly every
50 minutes. Let me emphasize this: exactly every 3,000 seconds. Not
3,001, or 2,999, but 3,000.
Anybody have any idea as to why it is exactly 50 minutes? What id
it that may be so special about 50 minutes?
I have tried with three more systems, and the diagnostic keeps
reappearing in two of them - with the same clockwork 50 minutes
frequency - but not at all in the third one - at least it has not for a
few days now. Interestingly, this last system is the oldest one of the
lot. They are all running exactly the same Linux version.
On Sat, 14 Jan 2023 20:04:09 +0000, James H. Markowitz wrote:
I have tried with three more systems, and the diagnostic keeps
reappearing in two of them - with the same clockwork 50 minutes
frequency - but not at all in the third one - at least it has not for a
few days now. Interestingly, this last system is the oldest one of the
lot. They are all running exactly the same Linux version.
Could it be that the third, oldest system only has USB1.1 and lacks
USB2?
Is the ehci_pci module loaded also on that system?
lsmod | grep hc xhci_pci 20480 0 xhci_pci_renesas
16384 1 xhci_pci ehci_pci 16384 0 xhci_hcd
286720 1 xhci_pci ehci_hcd 65536 1 ehci_pci
regards Henrik
This is what I get in that particular system:
smod | grep hci ohci_pci 16384 0 ohci_hcd
49152 1 ohci_pci ehci_pci 16384 0 ehci_hcd
65536 1 ehci_pci
In the others, in which the diagnostic does appear, the ohci lines are absent.
On Sun, 15 Jan 2023 13:36:01 +0000, James H. Markowitz wrote:
This is what I get in that particular system:
smod | grep hci ohci_pci 16384 0 ohci_hcd
49152 1 ohci_pci ehci_pci 16384 0 ehci_hcd
65536 1 ehci_pci
In the others, in which the diagnostic does appear, the ohci lines are
absent.
The fact that you have both ohci and ehci lines on the older system means that it has both USB1.1 (Open Host Controller Interface) and USB2
(Enhanced Host Controller Interface) controllers.
Could it be that you connected the external USB hard drive to a USB1.1
port?
regards Henrik
Henrik Carlqvist wrote:
On Sun, 15 Jan 2023 13:36:01 +0000, James H. Markowitz wrote:
*SKIP*In the others, in which the diagnostic does appear, the ohci lines
are absent.
*SKIP*Could it be that you connected the external USB hard drive to a
USB1.1 port?
The USB2 specs were released in April 2000, how long would it have
taken before motherboards with 1.x were no longer being sold?
Henrik Carlqvist wrote:
On Sun, 15 Jan 2023 13:36:01 +0000, James H. Markowitz wrote:
This is what I get in that particular system:
smod | grep hci ohci_pci 16384 0 ohci_hcd
49152 1 ohci_pci ehci_pci 16384 0 ehci_hcd >>> 65536 1 ehci_pci
In the others, in which the diagnostic does appear, the ohci lines are
absent.
The fact that you have both ohci and ehci lines on the older system means
that it has both USB1.1 (Open Host Controller Interface) and USB2
(Enhanced Host Controller Interface) controllers.
Could it be that you connected the external USB hard drive to a USB1.1
port?
Just as an aside: were there such systems?
with <tq342s$f6$1@gioia.aioe.org> Andrew wrote:
Henrik Carlqvist wrote:
On Sun, 15 Jan 2023 13:36:01 +0000, James H. Markowitz wrote:
*SKIP*
*SKIP*In the others, in which the diagnostic does appear, the ohci lines
are absent.
*SKIP*Could it be that you connected the external USB hard drive to a
USB1.1 port?
The USB2 specs were released in April 2000, how long would it have
taken before motherboards with 1.x were no longer being sold?
About a decade, apprently
% lsusb -t
/: Bus 07.Port 1: Dev 1, Class=root_hub, Driver=ohci_hcd/2p, 12M
/: Bus 06.Port 1: Dev 1, Class=root_hub, Driver=ohci_hcd/3p, 12M
/: Bus 05.Port 1: Dev 1, Class=root_hub, Driver=ohci_hcd/3p, 12M
/: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=ohci_hcd/3p, 12M
|__ Port 1: Dev 3, If 0, Class=HID, Driver=usbhid, 1.5M
|__ Port 1: Dev 3, If 1, Class=HID, Driver=usbhid, 1.5M
/: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=ohci_hcd/3p, 12M
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ehci_hcd/6p, 480M
|__ Port 2: Dev 2, If 0, Class=stor., Driver=usb-storage, 480M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci_hcd/6p, 480M
|__ Port 1: Dev 2, If 0, Class=hub, Driver=hub/4p, 480M
When I've comprehended what that means I was shocked. I repeat,
SHOCKED.
The fact that you have both ohci and ehci lines on the older system means >>> that it has both USB1.1 (Open Host Controller Interface) and USB2
(Enhanced Host Controller Interface) controllers.
Could it be that you connected the external USB hard drive to a USB1.1
port?
Just as an aside: were there such systems?
Certainly, I have one. I had to add usb 2 with a card.
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 300 |
Nodes: | 16 (2 / 14) |
Uptime: | 19:53:43 |
Calls: | 6,707 |
Calls today: | 1 |
Files: | 12,239 |
Messages: | 5,351,628 |