From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Borislav Petkov <bp@alien8.de>
Cc: linux-serial@vger.kernel.org, Jiri Slaby <jirislaby@kernel.org>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: serial 00:06: Runtime PM usage count underflow!
Date: Sat, 16 Nov 2024 18:19:36 +0100 [thread overview]
Message-ID: <2024111656-try-flatten-b215@gregkh> (raw)
In-Reply-To: <20241116170727.GCZzjRT5WGcOMKFDYq@fat_crate.local>
On Sat, Nov 16, 2024 at 06:07:27PM +0100, Borislav Petkov wrote:
> Hi folks,
>
> got a box here which says:
>
> [ 4.654361] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
> [ 4.660820] 00:06: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A
> [ 4.668313] printk: legacy console [ttyS0] disabled
> [ 4.676903] serial 00:06: Runtime PM usage count underflow!
> [ 4.677175] serial 00:06: disabled
> [ 4.677264] serial 00:06: unable to assign resources
> [ 4.677356] serial 00:06: probe with driver serial failed with error -16
> [ 4.677923] printk: legacy console [ttyS0] disabled
>
> Any suggestions?
Look in the bios, that seems to be the "old" pnp serial device? Does it
really have a serial port on the board? Is it enabled properly?
That is odd, what's the chance that someone didn't enable it in acpi
somehow?
> I'd like to use the serial cable to catch dmesg but somehow the driver doesn't
> like the chip...
It should be the bog-standard 16550 PNP device, check the resource
settings somewhere? Sorry I can't think of anything else at the
moment...
greg k-h
next prev parent reply other threads:[~2024-11-16 17:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-16 17:07 serial 00:06: Runtime PM usage count underflow! Borislav Petkov
2024-11-16 17:19 ` Greg Kroah-Hartman [this message]
2024-11-16 17:58 ` Borislav Petkov
2024-11-18 14:14 ` Ilpo Järvinen
2024-12-10 15:17 ` Borislav Petkov
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=2024111656-try-flatten-b215@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=bp@alien8.de \
--cc=jirislaby@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@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).