Re: bug report question

2023-09-07 Thread Dan Purgert
On Sep 07, 2023, duh_gently...@simplelogin.com wrote:
> Thank you for your advice!

No problem.

> 
> lspci says:
> 00:01.3 PCI bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models
> 00h-0fh) PCIe GPP Bridge

Okay so it's the root PCI bridge on the motherboard.  Are there any
BIOS/UEFI updates available?

> 
> The only 2 PCIe devices I have are my video card and my m.2 drive. I have
> had different kernel versions as I have had this problem for at least 6
> months (debian testing)... so I can't really say when it all started.

What kernel are you running right now?


-- 
|_|O|_|
|_|_|O| Github: https://github.com/dpurgert
|O|O|O| PGP: DDAB 23FB 19FA 7D85 1CC1  E067 6D65 70E5 4CE7 2860


signature.asc
Description: PGP signature


Re: bug report question

2023-09-07 Thread duh_gently889

Thank you for your advice!

lspci says:
00:01.3 PCI bridge: Advanced Micro Devices, Inc. [AMD] Family 17h 
(Models 00h-0fh) PCIe GPP Bridge


The only 2 PCIe devices I have are my video card and my m.2 drive. I 
have had different kernel versions as I have had this problem for at 
least 6 months (debian testing)... so I can't really say when it all 
started.


But for me, at least a half-solution would be to stop these errors being 
logged, so that I can shut down the computer properly. When the root 
file system is full, many programs stop working, and even after a 
reboot, the user interface will not start.


On 07/09/2023 12.24, Dan Purgert - dan at djph.net wrote:

On Sep 07, 2023, duh_gently...@simplelogin.com wrote:

Hello,

I'd like to submit a bug, but I'm not quite sure which package it
should be.
I could not find anything similar in the bugtracker.

The problem occurs every 10-20 times. After the system has been suspended
and then resumed, the following message is written to kern.log and syslog:

2023-09-07T09:43:21.264297+02:00 host kernel: [527584.040221] pcieport
:00:01.3: PME: Spurious native interrupt!
[...]

I accept that the message may indicate a valid problem, but having so many
log messages is not OK either. Currently, when this happens, I am
forced to manually delete the log file and reboot.

At first glance, it seems to be hardware related. What device is plugged
into that PCIe slot (or is it the PCIe Root)?


In no particular order:

   - Check for a BIOS/UEFI update
   - Check with an older kernel
   - Check for an updated kernel module / driver
   - Reboot and revert to the previously working kernel revision / patch








Re: bug report question

2023-09-07 Thread Dan Purgert
On Sep 07, 2023, duh_gently...@simplelogin.com wrote:
> Hello,
> 
> I'd like to submit a bug, but I'm not quite sure which package it
> should be.
> I could not find anything similar in the bugtracker.
> 
> The problem occurs every 10-20 times. After the system has been suspended
> and then resumed, the following message is written to kern.log and syslog:
> 
> 2023-09-07T09:43:21.264297+02:00 host kernel: [527584.040221] pcieport
> :00:01.3: PME: Spurious native interrupt!
> [...]
> 
> I accept that the message may indicate a valid problem, but having so many
> log messages is not OK either. Currently, when this happens, I am
> forced to manually delete the log file and reboot.

At first glance, it seems to be hardware related. What device is plugged
into that PCIe slot (or is it the PCIe Root)?


In no particular order:

  - Check for a BIOS/UEFI update
  - Check with an older kernel
  - Check for an updated kernel module / driver
  - Reboot and revert to the previously working kernel revision / patch



-- 
|_|O|_|
|_|_|O| Github: https://github.com/dpurgert
|O|O|O| PGP: DDAB 23FB 19FA 7D85 1CC1  E067 6D65 70E5 4CE7 2860


signature.asc
Description: PGP signature


bug report question

2023-09-07 Thread duh_gently889

Hello,

I'd like to submit a bug, but I'm not quite sure which package it should 
be. I could not find anything similar in the bugtracker.


The problem occurs every 10-20 times. After the system has been 
suspended and then resumed, the following message is written to kern.log 
and syslog:


2023-09-07T09:43:21.264297+02:00 host kernel: [527584.040221] pcieport 
:00:01.3: PME: Spurious native interrupt!
2023-09-07T09:43:21.264297+02:00 host kernel: [527584.040225] pcieport 
:00:01.3: PME: Spurious native interrupt!
2023-09-07T09:43:21.264298+02:00 host kernel: [527584.040229] pcieport 
:00:01.3: PME: Spurious native interrupt!
2023-09-07T09:43:21.264298+02:00 host kernel: [527584.040233] pcieport 
:00:01.3: PME: Spurious native interrupt!
2023-09-07T09:43:21.264299+02:00 host kernel: [527584.040237] pcieport 
:00:01.3: PME: Spurious native interrupt!
2023-09-07T09:43:21.264299+02:00 host kernel: [527584.040241] pcieport 
:00:01.3: PME: Spurious native interrupt!
2023-09-07T09:43:21.264300+02:00 host kernel: [527584.040244] pcieport 
:00:01.3: PME: Spurious native interrupt!
2023-09-07T09:43:21.264301+02:00 host kernel: [527584.040248] pcieport 
:00:01.3: PME: Spurious native interrupt!
2023-09-07T09:43:21.264301+02:00 host kernel: [527584.040252] pcieport 
:00:01.3: PME: Spurious native interrupt!


There are so many of them that within 10 minutes the log files are 
several GiB in size, filling the root filesystem and rendering the OS 
unusable.


I accept that the message may indicate a valid problem, but having so 
many log messages is not OK either. Currently, when this happens, I am 
forced to manually delete the log file and reboot.


Best regards,
Peter



Bug Report Question

2023-06-19 Thread Christopher Quinn

Hello Debian Team,

I have a bug to report and have not done that before, thus, I need some 
assistance. My bug isn't with a specific package. If so, I am not sure 
which one. Below I will describe the issue.



I use a Lenovo T560 with a Lenovo dock. It is the one that Lenovo made 
for this specific laptop. If I have it off of the dock and am using it, 
there is not an issue. However, if I have it locked or in hibernation 
mode, and place it on the dock while it is in one of those states, the 
computer locks up and I have to do a manual restart using the power 
button. The first time I thought it might have just been a fluke but it 
has happened every time. I have ran Debian 10 and Debian 11 on this 
laptop and it did not do that. That is why I think it might be a bug.



Thank you,

Chris