[CentOS] centos 5.1 kernel dump

Tue Jan 8 18:53:50 UTC 2008
Ross S. W. Walker <rwalker at medallion.com>

Jerry Geis wrote:
> 
> Below is a kernel dump that I just got. This is a fresh new 
> install of centos 5.1 on NVIDIA
> gigabyte MB-GA-M61P-S3. nothing extra has been added.
> 
> I have not tried the irqpoll but I am surprised to get this.
> 
> Also the machine keeps running just hod this show on the console...
> 
> Any ideas???
> 
> Jerry
> 
> Jan  8 05:20:00 localhost kernel: irq 169: nobody cared (try 
> booting with the "irqpoll" option)
> Jan  8 05:20:00 localhost kernel: 
> Jan  8 05:20:00 localhost kernel: Call Trace:
> Jan  8 05:20:00 localhost kernel:  <IRQ>  
> [<ffffffff800b5d77>] __report_bad_irq+0x30/0x7d
> Jan  8 05:20:00 localhost kernel:  [<ffffffff800b5faa>] 
> note_interrupt+0x1e6/0x227
> Jan  8 05:20:00 localhost kernel:  [<ffffffff800b54bc>] 
> __do_IRQ+0xc7/0x105
> Jan  8 05:20:00 localhost kernel:  [<ffffffff8006a3bd>] 
> do_IRQ+0xe7/0xf5
> Jan  8 05:20:00 localhost kernel:  [<ffffffff8005b615>] 
> ret_from_intr+0x0/0xa
> Jan  8 05:20:00 localhost kernel:  [<ffffffff80011cba>] 
> __do_softirq+0x53/0xd5
> Jan  8 05:20:00 localhost kernel:  [<ffffffff801515dd>] 
> end_msi_irq_wo_maskbit+0x9/0x16
> Jan  8 05:20:00 localhost kernel:  [<ffffffff8005c2fc>] 
> call_softirq+0x1c/0x28
> Jan  8 05:20:00 localhost kernel:  [<ffffffff8006a53a>] 
> do_softirq+0x2c/0x85
> Jan  8 05:20:00 localhost kernel:  [<ffffffff8006a3c2>] 
> do_IRQ+0xec/0xf5
> Jan  8 05:20:00 localhost kernel:  [<ffffffff8005b615>] 
> ret_from_intr+0x0/0xa
> Jan  8 05:20:00 localhost kernel:  <EOI>  
> [<ffffffff8000cb74>] bit_waitqueue+0x3c/0xb4
> Jan  8 05:20:00 localhost kernel:  [<ffffffff8002ce23>] 
> wake_up_bit+0x11/0x22
> Jan  8 05:20:00 localhost kernel:  [<ffffffff880328ef>] 
> :jbd:do_get_write_access+0x137/0x527
> Jan  8 05:20:01 localhost kernel:  [<ffffffff800192e9>] 
> __getblk+0x25/0x22c
> Jan  8 05:20:01 localhost kernel:  [<ffffffff88032d01>] 
> :jbd:journal_get_write_access+0x22/0x33
> Jan  8 05:20:01 localhost kernel:  [<ffffffff8804dc75>] 
> :ext3:ext3_reserve_inode_write+0x38/0x90
> Jan  8 05:20:01 localhost kernel:  [<ffffffff8804dcee>] 
> :ext3:ext3_mark_inode_dirty+0x21/0x3c
> Jan  8 05:20:01 localhost kernel:  [<ffffffff88050b14>] 
> :ext3:ext3_dirty_inode+0x63/0x7b
> Jan  8 05:20:01 localhost kernel:  [<ffffffff8001349c>] 
> __mark_inode_dirty+0x29/0x16e
> Jan  8 05:20:01 localhost kernel:  [<ffffffff8804b5f5>] 
> :ext3:ext3_new_blocks+0x567/0x693
> Jan  8 05:20:01 localhost kernel:  [<ffffffff80025273>] 
> __bread+0x6/0x81
> Jan  8 05:20:01 localhost kernel:  [<ffffffff8804e46b>] 
> :ext3:ext3_get_blocks_handle+0x43a/0x9f1
> Jan  8 05:20:01 localhost kernel:  [<ffffffff88032ca8>] 
> :jbd:do_get_write_access+0x4f0/0x527
> Jan  8 05:20:01 localhost kernel:  [<ffffffff8804ed42>] 
> :ext3:ext3_get_block+0xbe/0xe3
> Jan  8 05:20:01 localhost kernel:  [<ffffffff8000e1b3>] 
> __block_prepare_write+0x1b6/0x4a0
> Jan  8 05:20:01 localhost kernel:  [<ffffffff8804ec84>] 
> :ext3:ext3_get_block+0x0/0xe3
> Jan  8 05:20:01 localhost kernel:  [<ffffffff8003c1d4>] 
> block_prepare_write+0x1a/0x25
> Jan  8 05:20:01 localhost kernel:  [<ffffffff88050260>] 
> :ext3:ext3_prepare_write+0xaf/0x17b
> Jan  8 05:20:01 localhost kernel:  [<ffffffff8000f9cb>] 
> generic_file_buffered_write+0x25a/0x6d8
> Jan  8 05:20:01 localhost kernel:  [<ffffffff8000cca5>] 
> file_read_actor+0xb9/0x154
> Jan  8 05:20:01 localhost kernel:  [<ffffffff8000ddd9>] 
> current_fs_time+0x3b/0x40
> Jan  8 05:20:01 localhost kernel:  [<ffffffff8000cbec>] 
> file_read_actor+0x0/0x154
> Jan  8 05:20:01 localhost kernel:  [<ffffffff80015dc6>] 
> __generic_file_aio_write_nolock+0x36c/0x3b8
> Jan  8 05:20:01 localhost kernel:  [<ffffffff8002134b>] 
> generic_file_aio_write+0x65/0xc1
> Jan  8 05:20:01 localhost kernel:  [<ffffffff8804c192>] 
> :ext3:ext3_file_write+0x16/0x91
> Jan  8 05:20:01 localhost kernel:  [<ffffffff80017958>] 
> do_sync_write+0xc7/0x104
> Jan  8 05:20:01 localhost kernel:  [<ffffffff8009b492>] 
> autoremove_wake_function+0x0/0x2e
> Jan  8 05:20:01 localhost kernel:  [<ffffffff8000cbec>] 
> file_read_actor+0x0/0x154
> Jan  8 05:20:01 localhost kernel:  [<ffffffff800161d8>] 
> vfs_write+0xce/0x174
> Jan  8 05:20:01 localhost kernel:  [<ffffffff80016a8d>] 
> sys_write+0x2d/0x6e
> Jan  8 05:20:01 localhost kernel:  [<ffffffff80016aa5>] 
> sys_write+0x45/0x6e
> Jan  8 05:20:01 localhost kernel:  [<ffffffff8005b28d>] 
> tracesys+0xd5/0xe0
> Jan  8 05:20:01 localhost kernel: 
> Jan  8 05:20:01 localhost kernel: handlers:
> Jan  8 05:20:01 localhost kernel: [<ffffffff801dadc4>] 
> (usb_hcd_irq+0x0/0x55)
> Jan  8 05:20:01 localhost kernel: Disabling IRQ #169

You may want to try disabling ACPI irq routing with the
kernel option acpi=noirq. It may be that the SATA
controller's irq was re-routed, but the ACPI message
wasn't properly intercepted.

With the ACPI irq routing disabled it will default to
the older method of irq polling I believe.

-Ross

______________________________________________________________________
This e-mail, and any attachments thereto, is intended only for use by
the addressee(s) named herein and may contain legally privileged
and/or confidential information. If you are not the intended recipient
of this e-mail, you are hereby notified that any dissemination,
distribution or copying of this e-mail, and any attachments thereto,
is strictly prohibited. If you have received this e-mail in error,
please immediately notify the sender and permanently delete the
original and any copy or printout thereof.