Groups | Search | Server Info | Login | Register

Groups > comp.os.linux.hardware > #3611

Re: Intriguing issue

From "James H. Markowitz" <noone@nowhere.net>
Newsgroups comp.os.linux.hardware
Subject Re: Intriguing issue
Date 2023-01-13 15:03 +0000
Organization Aioe.org NNTP Server
Message-ID <tprrrc$55p$1@gioia.aioe.org> (permalink)
References <tphso5$8cv$1@gioia.aioe.org> <Qgq*2287y@news.chiark.greenend.org.uk> <op.1ymrmmlca3w0dxdave@hodgins.homeip.net> <tppmji$kk5$1@gioia.aioe.org> <op.1yomc3vaa3w0dxdave@hodgins.homeip.net>

Show all headers | View raw

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.

Back to comp.os.linux.hardware | Previous | Next — Previous in thread | Next in thread | Find similar

Thread

Intriguing issue "James H. Markowitz" <noone@nowhere.net> - 2023-01-09 20:17 +0000
  Re: Intriguing issue Marco Moock <mo01@posteo.de> - 2023-01-09 21:36 +0100
  Re: Intriguing issue mjb@signal11.invalid (Mike) - 2023-01-10 20:57 +0000
  Re: Intriguing issue Theo <theom+news@chiark.greenend.org.uk> - 2023-01-11 22:23 +0000
    Re: Intriguing issue "David W. Hodgins" <dwhodgins@nomail.afraid.org> - 2023-01-11 18:31 -0500
      Re: Intriguing issue "James H. Markowitz" <noone@nowhere.net> - 2023-01-12 19:21 +0000
        Re: Intriguing issue "David W. Hodgins" <dwhodgins@nomail.afraid.org> - 2023-01-12 18:32 -0500
          Re: Intriguing issue "James H. Markowitz" <noone@nowhere.net> - 2023-01-13 15:03 +0000
            Re: Intriguing issue "David W. Hodgins" <dwhodgins@nomail.afraid.org> - 2023-01-13 16:23 -0500
      Re: Intriguing issue Theo <theom+news@chiark.greenend.org.uk> - 2023-01-13 12:51 +0000
  Re: Intriguing issue "James H. Markowitz" <noone@nowhere.net> - 2023-01-14 20:04 +0000
    Re: Intriguing issue Henrik Carlqvist <Henrik.Carlqvist@deadspam.com> - 2023-01-15 09:17 +0000
      Re: Intriguing issue "James H. Markowitz" <noone@nowhere.net> - 2023-01-15 13:36 +0000
        Re: Intriguing issue Henrik Carlqvist <Henrik.Carlqvist@deadspam.com> - 2023-01-16 07:14 +0000
          Re: Intriguing issue Andrew <Doug@hyperspace.vogon.gov> - 2023-01-16 10:06 +0100
            Re: Intriguing issue Eric Pozharski <whynot@pozharski.name> - 2023-01-16 15:00 +0000
              Re: Intriguing issue John-Paul Stewart <jpstewart@personalprojects.net> - 2023-01-16 15:28 -0500
            Re: Intriguing issue "Carlos E.R." <robin_listas@es.invalid> - 2023-01-16 20:47 +0100
              Re: Intriguing issue "David W. Hodgins" <dwhodgins@nomail.afraid.org> - 2023-01-16 17:08 -0500
      Re: Intriguing issue "Carlos E. R." <robin_listas@es.invalid> - 2024-11-08 13:57 +0100

csiph-web