Most recent kernel where this bug did not occur: Distribution: Ubuntu 6.06 Hardware Environment: Via K8n800 Unichrome Pro (Acer aspire laptop) Software Environment: Problem Description: In the dmesg I see this: [drm] Initialized via 2.7.4 20051116 on minor 0 irq 22: nobody cared (try booting with the "irqpoll" option) [<c013c2da>] __report_bad_irq+0x2a/0x90 [<c013baad>] handle_IRQ_event+0x3d/0x70 [<c013c3e7>] note_interrupt+0x87/0xe0 [<c013bbb0>] __do_IRQ+0xd0/0x100 [<c01055c9>] do_IRQ+0x19/0x30 [<c010392e>] common_interrupt+0x1a/0x20 [<c0100d2b>] default_idle+0x2b/0x60 [<c0100dc1>] cpu_idle+0x41/0x60 [<c0352845>] start_kernel+0x175/0x190 [<c0352390>] unknown_bootoption+0x0/0x1e0 handlers: [<f8b32030>] (via_driver_irq_handler+0x0/0x1d0 [via]) Disabling IRQ #22 If I try to boot with "irqpoll" the system won't work well. Steps to reproduce:
I've tried the latest kernel 2.6.17.3 but the error still remain: Linux agpgart interface v0.101 (c) Dave Jones [drm] Initialized drm 1.0.1 20051102 ACPI: PCI Interrupt 0000:01:00.0[A] -> GSI 16 (level, low) -> IRQ 22 [drm] Initialized via 2.7.4 20051116 on minor 0 irq 22: nobody cared (try booting with the "irqpoll" option) <c013b5b4> __report_bad_irq+0x24/0x90 <c013b6b3> note_interrupt+0x93/0x270 <c013aead> handle_IRQ_event+0x3d/0x70 <c013afb0> __do_IRQ+0xd0/0x100 <c0105579> do_IRQ+0x19/0x30 <c0103806> common_interrupt+0x1a/0x20 <c014b704> __handle_mm_fault+0x1b4/0x9e0 <c01133f0> do_page_fault+0x0/0x690 <c01133f0> do_page_fault+0x0/0x690 <c0113523> do_page_fault+0x133/0x690 <c01133f0> do_page_fault+0x0/0x690 <c01038cf> error_code+0x4f/0x54 handlers: [<f8b224b0>] (via_driver_irq_handler+0x0/0x1e0 [via]) Disabling IRQ #22
Dave, any idea? IRQ routing borkage?
Pleaswe test with latest kernel. If the problem is still there, please attach: /var/log/messages and dmesg, output of /proc/interrups, and lspci -vv Thanks.
Subject: Re: VIA Unichrome / Pro prolems I think the problem is still there. I've tried the latest kernel.. but the machine locked itself... :-( I think the problem of no 3d is related to some bug in DRI, because, when I disabled DRI in my xorg.conf: ... Section "Module" Load "i2c" Load "bitmap" Load "ddc" #Load "dri" Load "extmod" Load "freetype" Load "glx" Load "int10" Load "vbe" EndSection ... i have no more IRQ problems from kernel. Now, the 3d isn't working, but the machine won't lock no more... I will wait for the bug to be resolved... but If I have to buy a new laptop... It won't be powered by VIA video card.... Best Regards 2007/6/22, bugme-daemon@bugzilla.kernel.org <bugme-daemon@bugzilla.kernel.org>: > http://bugzilla.kernel.org/show_bug.cgi?id=6790 > > > protasnb@gmail.com changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > CC| |protasnb@gmail.com > > > > > ------- Comment #3 from protasnb@gmail.com 2007-06-21 16:32 ------- > Pleaswe test with latest kernel. > If the problem is still there, please attach: /var/log/messages and dmesg, > output of /proc/interrups, and lspci -vv > Thanks. > > > -- > Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email > ------- You are receiving this mail because: ------- > You reported the bug, or are watching the reporter. >
I see similar problem with kernel 2.6.23-rc7. Most recent kernel where this bug did not occur: Distribution: Debian 4.0 Hardware Environment: VIA K8N800 (on laptop Clevo model D4J, product code: D410J) Software Environment: xorg X server 7.1.1 Problem Description: When the X server starts, the following error message appears in dmesg: [drm:via_mem_alloc] *ERROR* Attempt to allocate from uninitialized memory manager. irq 16: nobody cared (try booting with the "irqpoll" option) [<c01052ca>] show_trace_log_lvl+0x1a/0x30 [<c0105e62>] show_trace+0x12/0x20 [<c0105e85>] dump_stack+0x15/0x20 [<c0152f07>] __report_bad_irq+0x27/0x90 [<c01531c7>] note_interrupt+0x257/0x290 [<c015386c>] handle_fasteoi_irq+0xac/0xe0 [<c010649a>] do_IRQ+0x4a/0xa0 [<c0104cee>] common_interrupt+0x2e/0x34 [<c02fab2b>] schedule+0x29b/0x490 [<c0102410>] cpu_idle+0x70/0x80 [<c02fa5b0>] rest_init+0x60/0x70 [<c03d8b6f>] start_kernel+0x22f/0x280 [<00000000>] 0x0 ======================= handlers: [<f8c9f470>] (via_driver_irq_handler+0x0/0x1d0 [via]) Disabling IRQ #16
Created attachment 12944 [details] K8M800 /var/log/messages
Created attachment 12945 [details] K8M800 lspci -vv
Created attachment 12946 [details] K8M800 lspci -v -n
Created attachment 12947 [details] K8M800 cat /proc/interrupts
Created attachment 12948 [details] K8M800 /var/log/Xorg.0.log
Created attachment 12954 [details] dmesg of 2.6.23-rc8 dmesg of linux kernel 2.6.23-rc8. The drm kernel module was loaded with debug=1 parameter. The kernel was compiled with CONFIG_PRINTK_TIME=y.
See also http://bugzilla.kernel.org/show_bug.cgi?id=8641
This appears to be IRQ assignment problem. CCing to Len, take a look. Maybe this needs to be re-assigned to ACPI?
Workaround: Using the openChrome X11 driver does not tirgger this bug ( http://www.openchrome.org/ ). See also http://lkml.org/lkml/2008/3/16/10 for a bit detailed description.
Great information, thanks. Will this also apply in the bug mentioned in #12?
I think the workaround in comment #14 also applies to the problem in bug #8641. (Maybe bug #6790 and #8641 are DUPs?)
*** Bug 8641 has been marked as a duplicate of this bug. ***
(In reply to comment #14) > Workaround: > > Using the openChrome X11 driver does not tirgger this bug ( > http://www.openchrome.org/ ). See also http://lkml.org/lkml/2008/3/16/10 for > a > bit detailed description. > Openchrome doesn't exhibit the bug because it disables the IRQ by default on K8M800.
Closing as stale