On Fri, 2 Jun 2006 13:29:18 +1200
"Keith Chew" <[email protected]> wrote:
> Hi
>
> I recently started a thread called "IO APIC IRQ assignment" to find a
> way to separate the IRQs assignments for the USB and BT878 chip. In
> the meantime, our workaround was to tweak the PCI latency to make the
> 2 devices work nicely on the same IRQ, but last night, 1 of the 10 PCs
> under test crashed.
>
> I apologise in advance for posting the same console stack trace again,
> but I figured this problem needed a new topic as it is not related to
> IO APIC IRQ Assignment topic. If anyone can guide us to where to look
> for the problem, it will be much appreciated. We have 5 x PCs running
> 2.6.14.2 kernel, and 5 x PCs running 2.6.16.18. This crash happened on
> the 2.6.14.2 kernel.
>
> ===================================
> Unable to handle kernel paging request at virtual address 23232327
> printing eip:
> c014b569
> *pde = 00000000
> Oops: 0002 [#1]
> Modules linked in: ipt_LOG ipt_state iptable_filter ip_tables ip_conntrack_tf
> ip_conntrack_proto_sctp ip_conntrack_irc ip_conntrack_ftp ip_conntrack_amanda
> _conntrack rt2570 zd1211 autofs4 video button battery ac uhci_hcd bt878 tuner
> audio bttv video_buf i2c_algo_bit v4l2_common btcx_risc tveeprom videodev i2c
> 01 i2c_core snd_intel8x0 snd_ac97_codec snd_ac97_bus snd_pcm_oss snd_mixer_os
> nd_pcm snd_timer snd soundcore snd_page_alloc e100 mii dm_snapshot dm_zero dm
> rror ext3 jbd dm_mod
> CPU: 0
> EIP: 0060:[<c014b569>] Not tainted VLI
> EFLAGS: 00010046 (2.6.14.2)
> EIP is at activate_page+0x59/0xd0
> eax: 23232323 ebx: c1400160 ecx: c1400178 edx: 23232323
> esi: c03b7300 edi: c03b73e0 ebp: 00000001 esp: d3769ae4
> ds: 007b es: 007b ss: 0068
> Process mencoder (pid: 23017, threadinfo=d3768000 task=d615d030)
> Stack: d3769b7c 00000000 c1400160 00000040 c1000000 c014b613 c1400160 c0150b1
> c7fe9d68 0000000f 00000001 b771d000 00000001 00000000 00000001 e5d26ee
> f724124c f7241200 c0150cbe f7241200 b775a000 00000000 00000001 0000000
> Call Trace:
> [<c014b613>] mark_page_accessed+0x33/0x40
> [<c0150b13>] __follow_page+0x153/0x160
> [<c0150cbe>] get_user_pages+0x11e/0x380
> [<f896e348>] videobuf_dma_init_user+0x118/0x190 [video_buf]
> [<f896eac7>] videobuf_iolock+0x77/0x110 [video_buf]
> [<f89a0909>] bttv_prepare_buffer+0x179/0x1c0 [bttv]
> [<f89a2b9c>] bttv_do_ioctl+0xbdc/0x1850 [bttv]
> [<c035d2eb>] _read_unlock+0xb/0x10
> [<f8a553c4>] zd1205_xmit_frame+0x94/0x4a0 [zd1211]
> [<c035d2ab>] _spin_lock+0xb/0x10
> [<c0300c73>] qdisc_restart+0x23/0x200
> [<c035d2cb>] _spin_unlock+0xb/0x10
> [<c02f0312>] dev_queue_xmit+0x2a2/0x330
> [<f8cae3c3>] tcp_in_window+0x303/0x510 [ip_conntrack]
> [<c035d1bf>] _spin_lock_irqsave+0xf/0x20
> [<c0124d28>] __mod_timer+0xa8/0xd0
> [<c035d3cb>] _write_unlock_bh+0xb/0x20
> [<f8cad773>] __ip_ct_refresh_acct+0x73/0xc0 [ip_conntrack]
> [<f8caeaa3>] tcp_packet+0x1a3/0x580 [ip_conntrack]
> [<c02ea2e1>] __alloc_skb+0x61/0x150
> [<c026b0e8>] dma_pool_alloc+0x98/0x180
> [<c0117597>] activate_task+0x67/0x80
> [<c0117688>] try_to_wake_up+0x88/0xd0
> [<c01176ed>] wake_up_process+0x1d/0x20
> [<c035d31b>] _spin_unlock_irq+0xb/0x10
> [<f8a466f3>] uhci_alloc_qh+0x23/0x60 [uhci_hcd]
> [<c0117597>] activate_task+0x67/0x80
> [<c0117688>] try_to_wake_up+0x88/0xd0
> [<c0131b7f>] autoremove_wake_function+0x2f/0x60
> [<c0118021>] __wake_up_common+0x41/0x80
> [<c01e4756>] copy_from_user+0x66/0xa0
> [<f897b427>] video_usercopy+0xf7/0x180 [videodev]
> [<c0117688>] try_to_wake_up+0x88/0xd0
> [<c0118021>] __wake_up_common+0x41/0x80
> [<c011809e>] __wake_up+0x3e/0x60
> [<f89a384f>] bttv_ioctl+0x3f/0x70 [bttv]
> [<f89a1fc0>] bttv_do_ioctl+0x0/0x1850 [bttv]
> [<c0177b48>] do_ioctl+0x58/0x80
> [<c0177cd5>] vfs_ioctl+0x65/0x1f0
> [<c01e46d6>] copy_to_user+0x66/0x80
> [<c0177ee8>] sys_ioctl+0x88/0xa0
> [<c01031af>] sysenter_past_esp+0x54/0x75
We've certianly screwed around with the mmapping of IO space and such
things in recent months, and iirc 2.6.14 was somewhat in the middle of it
all.
Are you seeing the above problem on 2.6.16.x?
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
