Bug 120251 - Continuous stream of "lost x rtc interrupts"
Summary: Continuous stream of "lost x rtc interrupts"
Status: RESOLVED OBSOLETE
Alias: None
Product: Platform Specific/Hardware
Classification: Unclassified
Component: x86-64 (show other bugs)
Hardware: All Linux
: P1 normal
Assignee: platform_x86_64@kernel-bugs.osdl.org
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-06-14 13:05 UTC by Rogério Brito
Modified: 2020-11-10 21:35 UTC (History)
1 user (show)

See Also:
Kernel Version: 4.6
Subsystem:
Regression: No
Bisected commit-id:


Attachments
dmesg log of kernel 4.6 showing lots of "lost x rtc interrupts" (113.72 KB, text/x-log)
2016-06-14 13:05 UTC, Rogério Brito
Details
output of acpidump (99.93 KB, text/plain)
2016-06-14 13:07 UTC, Rogério Brito
Details
output of running dmidecode (8.49 KB, text/plain)
2016-06-14 13:08 UTC, Rogério Brito
Details
output of lspci -vvxx (22.83 KB, text/plain)
2016-06-14 13:09 UTC, Rogério Brito
Details
output of lsusb (665 bytes, text/plain)
2016-06-14 13:09 UTC, Rogério Brito
Details
contents of /proc/cmdline (101 bytes, text/plain)
2016-06-14 13:10 UTC, Rogério Brito
Details
contents of /proc/cpuinfo (3.77 KB, text/plain)
2016-06-14 13:10 UTC, Rogério Brito
Details
contents of /proc/interrupts (2.39 KB, text/plain)
2016-06-14 13:11 UTC, Rogério Brito
Details
contents of /proc/iomem (1.98 KB, text/plain)
2016-06-14 13:11 UTC, Rogério Brito
Details
contents of /proc/ioports (1.57 KB, text/plain)
2016-06-14 13:12 UTC, Rogério Brito
Details

Description Rogério Brito 2016-06-14 13:05:33 UTC
Created attachment 219881 [details]
dmesg log of kernel 4.6 showing lots of "lost x rtc interrupts"

Hi.

First of all, I don't know if I selected the appropriate components here in bugzilla and I would appreciate it if anyone could correct me with my choice.

Now, to the actual report.

I have a desktop computer that has recently started to present a lot of messages of "lost xxx rtc interrupts" with recent-ish kernel versions (say, >= 4.5).

I'm using a Debian-compiled kernel (with all of my userspace being Debian testing) and the motherboard of this computer is a semi-generic one sold here in Brazil for which I don't believe there is any BIOS update (numerous Google searches gave me no apparent relevant results).

I can include here any data that the developers want me to and I can test patches to fix whatever (possible) quirk my computer may have.


Thanks,

Rogério Brito.
Comment 1 Rogério Brito 2016-06-14 13:07:01 UTC
I'm including here on bugzilla some other logs that I think (in my ignorance) that may offer some extra context.
Comment 2 Rogério Brito 2016-06-14 13:07:41 UTC
Created attachment 219891 [details]
output of acpidump
Comment 3 Rogério Brito 2016-06-14 13:08:12 UTC
Created attachment 219901 [details]
output of running dmidecode
Comment 4 Rogério Brito 2016-06-14 13:09:07 UTC
Created attachment 219911 [details]
output of lspci -vvxx
Comment 5 Rogério Brito 2016-06-14 13:09:32 UTC
Created attachment 219921 [details]
output of lsusb
Comment 6 Rogério Brito 2016-06-14 13:10:30 UTC
Created attachment 219931 [details]
contents of /proc/cmdline
Comment 7 Rogério Brito 2016-06-14 13:10:54 UTC
Created attachment 219941 [details]
contents of /proc/cpuinfo
Comment 8 Rogério Brito 2016-06-14 13:11:24 UTC
Created attachment 219951 [details]
contents of /proc/interrupts
Comment 9 Rogério Brito 2016-06-14 13:11:54 UTC
Created attachment 219961 [details]
contents of /proc/iomem
Comment 10 Rogério Brito 2016-06-14 13:12:20 UTC
Created attachment 219971 [details]
contents of /proc/ioports
Comment 11 Rogério Brito 2016-06-24 23:14:01 UTC
Is there anything else that I should provide?

Notice that I have the irqpoll option passed on my command line. Without it, I get some very strange behavior on my system, which I can describe in more detail (I don't remember them off the top of my head---I would have to boot without that option and see some strange things).

Thanks in advance,

Rogério Brito.
Comment 12 Rogério Brito 2020-11-10 21:35:55 UTC
Hi.

I'm closing this bug. The reason is not that the bug is fixed (it may, or it may not have been), but I don't have that computer anymore.

Thanks for all the help,

Rogério Brito.

Note You need to log in before you can comment on or make changes to this bug.