Bug 12796 - via driver (?) fails to handle interrupt
Summary: via driver (?) fails to handle interrupt
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Drivers
Classification: Unclassified
Component: Video(DRI - non Intel) (show other bugs)
Hardware: All Linux
: P1 low
Assignee: drivers_video-dri
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-03-01 14:24 UTC by Vincent Zweije
Modified: 2012-06-16 13:15 UTC (History)
2 users (show)

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


Attachments

Description Vincent Zweije 2009-03-01 14:24:34 UTC
Latest working kernel version:
Earliest failing kernel version: 2.6.16 or earlier
Distribution: Debian
Hardware Environment: VIA K8M800/K8N800/K8N800A [S3 UniChrome Pro]
Software Environment: debian testing: xserver-xorg-video-via-1:0.2.2-6, libdrm2-2.3.1-2
Problem Description:
Package: xserver-xorg-video-via
Version: 1:0.1.33.2-3
Severity: minor

When starting the X server, the kernel spits out the following message:

Mar  1 22:43:42 arrow kernel: [   35.229770] [drm] Initialized drm 1.1.0 20060810
Mar  1 22:43:42 arrow kernel: [   35.255792] pci 0000:01:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
Mar  1 22:43:42 arrow kernel: [   35.255949] [drm] Initialized via 2.11.1 20070202 on minor 0
Mar  1 22:43:42 arrow kernel: [   35.293414] agpgart-amd64 0000:00:00.0: AGP 3.0 bridge
Mar  1 22:43:42 arrow kernel: [   35.293431] agpgart: Xorg tried to set rate=x12. Setting to AGP3 x8 mode.
Mar  1 22:43:42 arrow kernel: [   35.293439] agpgart-amd64 0000:00:00.0: putting AGP V3 device into 8x mode
Mar  1 22:43:42 arrow kernel: [   35.293503] pci 0000:01:00.0: putting AGP V3 device into 8x mode
Mar  1 22:43:43 arrow kernel: [   35.772229] irq 16: nobody cared (try booting with the "irqpoll" option)
Mar  1 22:43:43 arrow kernel: [   35.772237] Pid: 2517, comm: debtorrent-clie Not tainted 2.6.28.7 #1
Mar  1 22:43:43 arrow kernel: [   35.772240] Call Trace:
Mar  1 22:43:43 arrow kernel: [   35.772248]  [<c0159fb7>] __report_bad_irq+0x24/0x69
Mar  1 22:43:43 arrow kernel: [   35.772252]  [<c0159fbe>] __report_bad_irq+0x2b/0x69
Mar  1 22:43:43 arrow kernel: [   35.772255]  [<c015a0e7>] note_interrupt+0xeb/0x140
Mar  1 22:43:43 arrow kernel: [   35.772259]  [<c015a625>] handle_fasteoi_irq+0x89/0xae
Mar  1 22:43:43 arrow kernel: [   35.772263]  [<c0105bd7>] do_IRQ+0x67/0x7c
Mar  1 22:43:43 arrow kernel: [   35.772266]  [<c010450b>] common_interrupt+0x23/0x28
Mar  1 22:43:43 arrow kernel: [   35.772268] handlers:
Mar  1 22:43:43 arrow kernel: [   35.772270] [<dca465dc>] (via_driver_irq_handler+0x0/0x148 [via])
Mar  1 22:43:43 arrow kernel: [   35.772280] Disabling IRQ #16

However, the X server works well (so far), hence the low severity.

There is an open bug in the debian bug tracking system on this, with more info:

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=388453

I originally attributed this to the X server, but my knowledge is limited in these areas. The debian maintainer of bug 388453 asked me to reproduce this with the latest kernel, so here it is.

Steps to reproduce:
Comment 1 Jonathan Nieder 2011-08-05 16:37:37 UTC
(In reply to comment #0)

> irq 16: nobody cared (try booting with the "irqpoll" option)

Hmm, as always that is of course worrisome.  Nothing seems to have happened under driver/gpu/drm/via recently, unfortunately.

Vincent: Does the same thing happen with v3.0 or more recent snapshots?

Others: Any hints for debugging this (e.g., kernel command line parameters to get more information about IRQ handling)?
Comment 2 Anonymous Emailer 2012-06-16 13:15:06 UTC
Reply-To: vincent@zweije.nl

On Wed, May 30, 2012 at 02:20:06PM +0000,
bugzilla-daemon@bugzilla.kernel.org wrote:

||  https://bugzilla.kernel.org/show_bug.cgi?id=12796

||  > irq 16: nobody cared (try booting with the "irqpoll" option)
||  
||  Hmm, as always that is of course worrisome.  Nothing seems to have happened
||  under driver/gpu/drm/via recently, unfortunately.
||  
||  Vincent: Does the same thing happen with v3.0 or more recent snapshots?

Just checked: problem seems to be gone in linux-3.2.
-- 
Vincent Zweije <vincent@zweije.nl>   | "If you're flamed in a group you
<http://www.xs4all.nl/~zweije/>      | don't read, does anybody get burnt?"
[Xhost should be taken out and shot] |            -- Paul Tomblin on a.s.r.

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