Your message dated Sat, 1 May 2010 22:01:28 +0200 with message-id <20100501200128.ga15...@galadriel.inutil.org> and subject line Re: [linux-image-2.6.26-1-amd64] report_bad_irq (while in screensaver) has caused the Debian Bug report #518046, regarding [linux-image-2.6.26-1-amd64] report_bad_irq (while in screensaver) to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 518046: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=518046 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Package: linux-image-2.6.26-1-amd64 Version: 2.6.26-13 Severity: normal --- Please enter the report below this line. --- recently, ever time i get back to the computer which is in screensaver mode and i get this error in the /var/log/messages : kernel: [12466.291495] Pid: 0, comm: swapper Tainted: P 2.6.26-1- amd64 #1 kernel: [12466.291495] kernel: [12466.291495] Call Trace: kernel: [12466.291495] <IRQ> [<ffffffff8026c6c3>] __report_bad_irq+0x30/0x72 kernel: [12466.291495] [<ffffffff8026c902>] note_interrupt+0x1fd/0x23b kernel: [12466.291495] [<ffffffff8026d18b>] handle_fasteoi_irq+0xa5/0xc8 kernel: [12466.291495] [<ffffffff8020f5e4>] do_IRQ+0x6d/0xd9 kernel: [12466.291495] [<ffffffff8020c46d>] ret_from_intr+0x0/0x19 kernel: [12466.291495] <EOI> [<ffffffffa006e26d>] :processor:acpi_idle_enter_bm+0x2b3/0x327 kernel: [12466.291495] [<ffffffff803aa0e4>] cpuidle_idle_call+0x7a/0xb2 kernel: [12466.291495] [<ffffffff803aa06a>] cpuidle_idle_call+0x0/0xb2 kernel: [12466.291495] [<ffffffff8020ac79>] cpu_idle+0x89/0xb3 kernel: [12466.291495] system seems functional but maybe i am missing something ? --- System information. --- Architecture: amd64 Kernel: Linux 2.6.26-1-amd64 Debian Release: 5.0 500 unstable www.debian-multimedia.org 500 unstable snapshots.ekiga.net 500 unstable mirror.isoc.org.il 500 stable security.debian.org 1 experimental mirror.isoc.org.il --- Package information. --- Depends (Version) | Installed =====================================-+-============= module-init-tools | 3.4-1 initramfs-tools (>= 0.55) | 0.93 OR yaird (>= 0.0.13) | OR linux-initramfs-tool | --- Output from package bug script ---
--- End Message ---
--- Begin Message ---On Thu, Feb 25, 2010 at 07:02:43PM +0100, Moritz Muehlenhoff wrote: > tags 518046 moreinfo > thanks > > On Tue, Mar 03, 2009 at 10:05:15PM +0200, Nadav Kavalerchik wrote: > > Package: linux-image-2.6.26-1-amd64 > > Version: 2.6.26-13 > > Severity: normal > > > > --- Please enter the report below this line. --- > > recently, ever time i get back to the computer which is in screensaver mode > > and i get this error in the /var/log/messages : > > > > kernel: [12466.291495] Pid: 0, comm: swapper Tainted: P 2.6.26-1- > > amd64 #1 > > kernel: [12466.291495] > > kernel: [12466.291495] Call Trace: > > kernel: [12466.291495] <IRQ> [<ffffffff8026c6c3>] > > __report_bad_irq+0x30/0x72 > > kernel: [12466.291495] [<ffffffff8026c902>] note_interrupt+0x1fd/0x23b > > kernel: [12466.291495] [<ffffffff8026d18b>] handle_fasteoi_irq+0xa5/0xc8 > > kernel: [12466.291495] [<ffffffff8020f5e4>] do_IRQ+0x6d/0xd9 > > kernel: [12466.291495] [<ffffffff8020c46d>] ret_from_intr+0x0/0x19 > > kernel: [12466.291495] <EOI> [<ffffffffa006e26d>] > > :processor:acpi_idle_enter_bm+0x2b3/0x327 > > kernel: [12466.291495] [<ffffffff803aa0e4>] cpuidle_idle_call+0x7a/0xb2 > > kernel: [12466.291495] [<ffffffff803aa06a>] cpuidle_idle_call+0x0/0xb2 > > kernel: [12466.291495] [<ffffffff8020ac79>] cpu_idle+0x89/0xb3 > > kernel: [12466.291495] > > > > system seems functional but maybe i am missing something ? > > Does this also occur without the closed source kernel module loaded? > > Can you try with a current kernel? No further feedback, closing the bug. If this can be reproduced with current kernels, please reopen this bug. Cheers, Moritz
--- End Message ---
