From: Greg KH <gregkh@linuxfoundation.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: problem on reboot: pcieport 0000:00:1c:0: pciehp: Slot(0): No link
Date: Wed, 27 Jul 2022 07:08:51 +0000 [thread overview]
Message-ID: <YuDkgw9SU1GmA3kS@kroah.com> (raw)
In-Reply-To: <94dbdb74-1de7-22e6-62d2-1fe460eb89d9@afaics.de>
On Mon, Jul 25, 2022 at 05:43:10PM +0200, Harald Dunkel wrote:
> Hi folks,
>
> setup:
> kernel 5.18.14 (built from git)
> Qnap TS-559 Pro II, 4*3.5 HDD + 1 SSD, /boot is on USB stick
> Intel(R) Atom(TM) CPU D525
> Debian Sid
>
> On a reboot after some runtime my Qnap TS-559 Pro II shuts down cleanly, but
> after the kernel and initrd are loaded again it writes an endless stream of
> messages to the console
>
> pcieport 0000:00:1c:0: pciehp: Slot(0): Card present
> pcieport 0000:00:1c:0: pciehp: Slot(0): No link
> pcieport 0000:00:1c:0: pciehp: Slot(0): Card present
> pcieport 0000:00:1c:0: pciehp: Slot(0): No link
> pcieport 0000:00:1c:0: pciehp: Slot(0): Card present
> pcieport 0000:00:1c:0: pciehp: Slot(0): No link
> pcieport 0000:00:1c:0: pciehp: Slot(0): Card present
> pcieport 0000:00:1c:0: pciehp: Slot(0): No link
> pcieport 0000:00:1c:0: pciehp: Slot(0): Card present
> pcieport 0000:00:1c:0: pciehp: Slot(0): No link
> pcieport 0000:00:1c:0: pciehp: Slot(0): Card present
> pcieport 0000:00:1c:0: pciehp: Slot(0): No link
>
> Appr. 2 lines per second. I get an emergency console to login, but it
> is garbled.
>
> If I wait a few minutes to let the qnap cool down it boots again.
Try posting on the linux-pci@vger.kernel.org list, that is the best for
this type of thing.
thanks,
greg k-h
next prev parent reply other threads:[~2022-07-27 7:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-25 15:43 problem on reboot: pcieport 0000:00:1c:0: pciehp: Slot(0): No link Harald Dunkel
2022-07-27 7:08 ` Greg KH [this message]
2022-07-31 17:11 ` Harald Dunkel
2022-07-31 17:23 ` Harald Dunkel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=YuDkgw9SU1GmA3kS@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=linux-hotplug@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).