Re: Spurious messages at the console
On Sat, May 11, 2024 at 08:57:24PM -0400, Paul M Foster wrote: [...] > Excellent advice. Thanks. > > Here's an oddity. The following commands are equivalent, according to the > dmesg(1) man page: > > dmesg -n 1 and dmesg -n emerg > > But according to every document I've viewed, "emerg" is code for 0, not 1. > If anyone can explain, I'd be interested. This is funny, yes. It seems intentional, though: https://sources.debian.org/src/util-linux/2.38.1-5/sys-utils/dmesg.c/#L1505 calls parse_level with a second arg of 0, which causes parse_level() https://sources.debian.org/src/util-linux/2.38.1-5/sys-utils/dmesg.c/#L348 to add an offset of 1. No idea what the thought behind this is. Perhaps backward-compat to some forgotten lore? Cheers -- t signature.asc Description: PGP signature
Re: Spurious messages at the console
On Sat, May 11, 2024 at 07:54:28AM +0200, to...@tuxteam.de wrote: > On Fri, May 10, 2024 at 05:30:44PM -0400, Paul M Foster wrote: > > Folks: > > > > I've installed Debian (latest) without X on a small form factor PC, and > > typically SSH into it, though I also have a keyboard and monitor > > temporarily connected to it. > > > > I'm getting spurious error messages in groups on the monitor connected to > > it. They look like: > > > > [76056.389126] pcieport :00:1c.0: PCIe Buss Error: severity=Corrected, > > type=Physical Layer, (Reciever ID) > > > > That's just one line. Others are related but different. These happen every > > few minutes, and only on the monitor, not where I'm SSHed in. > > I don't know exactly what this is doing (to my naïve eye it looks like > some part of the PCI bus is doing things the kernel doesn't expect but > thinks it can fix) but... > > > It would be neat to know what's going wrong, and if you can come up with a > > reason, I'd be interested. But I'm not really fixated on that. Instead, > > what I'm interested in is how to make them stop. > > ...for that try "dmesg -D" (see man dmesg). You can also try to mess > with the value of /proc/sys/kernel/printk, documented, e.g. here [1], > to set it permanently. > > Cheers > > [1] https://www.kernel.org/doc/html/latest/core-api/printk-basics.html > or, of course, locally. If you are in Debian, part of the linux-doc > package, in /usr/share/doc/linux-doc/html/core-api/printk-basics.html > Excellent advice. Thanks. Here's an oddity. The following commands are equivalent, according to the dmesg(1) man page: dmesg -n 1 and dmesg -n emerg But according to every document I've viewed, "emerg" is code for 0, not 1. If anyone can explain, I'd be interested. Paul -- Paul M. Foster Personal Blog: http://noferblatz.com Company Site: http://quillandmouse.com Software Projects: https://gitlab.com/paulmfoster
Re: Spurious messages at the console
On 2024-05-10, Paul M Foster wrote: > [76056.389126] pcieport :00:1c.0: PCIe Buss Error: severity=Corrected, > type=Physical Layer, (Reciever ID) Use lspci (from package pciutils) to find which device it is
Re: Spurious messages at the console
On Fri, May 10, 2024 at 05:30:44PM -0400, Paul M Foster wrote: > Folks: > > I've installed Debian (latest) without X on a small form factor PC, and > typically SSH into it, though I also have a keyboard and monitor > temporarily connected to it. > > I'm getting spurious error messages in groups on the monitor connected to > it. They look like: > > [76056.389126] pcieport :00:1c.0: PCIe Buss Error: severity=Corrected, > type=Physical Layer, (Reciever ID) > > That's just one line. Others are related but different. These happen every > few minutes, and only on the monitor, not where I'm SSHed in. I don't know exactly what this is doing (to my naïve eye it looks like some part of the PCI bus is doing things the kernel doesn't expect but thinks it can fix) but... > It would be neat to know what's going wrong, and if you can come up with a > reason, I'd be interested. But I'm not really fixated on that. Instead, > what I'm interested in is how to make them stop. ...for that try "dmesg -D" (see man dmesg). You can also try to mess with the value of /proc/sys/kernel/printk, documented, e.g. here [1], to set it permanently. Cheers [1] https://www.kernel.org/doc/html/latest/core-api/printk-basics.html or, of course, locally. If you are in Debian, part of the linux-doc package, in /usr/share/doc/linux-doc/html/core-api/printk-basics.html -- t signature.asc Description: PGP signature
Spurious messages at the console
Folks: I've installed Debian (latest) without X on a small form factor PC, and typically SSH into it, though I also have a keyboard and monitor temporarily connected to it. I'm getting spurious error messages in groups on the monitor connected to it. They look like: [76056.389126] pcieport :00:1c.0: PCIe Buss Error: severity=Corrected, type=Physical Layer, (Reciever ID) That's just one line. Others are related but different. These happen every few minutes, and only on the monitor, not where I'm SSHed in. It would be neat to know what's going wrong, and if you can come up with a reason, I'd be interested. But I'm not really fixated on that. Instead, what I'm interested in is how to make them stop. Any help would be appreciated. Paul -- Paul M. Foster Personal Blog: http://noferblatz.com Company Site: http://quillandmouse.com Software Projects: https://gitlab.com/paulmfoster
