Re: LOR on em in HEAD ( was Re: em driver regression

From: Jack Vogel <jfvogel_at_gmail.com>
Date: Fri, 9 Apr 2010 14:11:54 -0700
Don't know, but I would just ignore it, I think its a false warning anyway.

Jack


On Fri, Apr 9, 2010 at 2:05 PM, Mike Tancsa <mike_at_sentex.net> wrote:

> At 04:13 PM 4/9/2010, Pyun YongHyeon wrote:
>
>> On Fri, Apr 09, 2010 at 12:09:24PM -0700, Jack Vogel wrote:
>> > Someone else also pointed this out. I'm dubious about its claim.
>>
>> I can't reproduce the LOR with latest em(4)(r206429).
>>
>
>
> I still get it for some reason
>
>  1st 0xc5dc7610 em1:rx(1) (em1:rx(1)) _at_
> /usr/HEAD/src/sys/modules/em/../../dev/e1000/if_em.c:4087
>  2nd 0xc0f7df0c udp (udp) _at_ /usr/HEAD/src/sys/netinet/udp_usrreq.c:454
> KDB: stack backtrace:
> db_trace_self_wrapper(c0cb4313,c5b72a64,c08e4305,c08d467b,c0cb7338,...) at
> db_trace_self_wrapper+0x26
> kdb_backtrace(c08d467b,c0cb7338,c5d31a98,c5d2cb60,c5b72ac0,...) at
> kdb_backtrace+0x29
> _witness_debugger(c0cb7338,c0f7df0c,c0c9c4eb,c5d2cb60,c0ccfaf7,...) at
> _witness_debugger+0x25
> witness_checkorder(c0f7df0c,1,c0ccfaf7,1c6,0,...) at
> witness_checkorder+0x839
> _rw_rlock(c0f7df0c,c0ccfaf7,1c6,c5d33088,c5e8be24,...) at _rw_rlock+0x9c
> udp_input(c6905900,14,0,c5e8bd80,c0df9ee0,...) at udp_input+0x246
> ip_input(c6905900,c5f39240,c5b72bdc,c0745956,c0df9ee0,...) at
> ip_input+0x606
> netisr_dispatch_src(1,0,c6905900,c5b72c14,c0954161,...) at
> netisr_dispatch_src+0xcd
> netisr_dispatch(1,c6905900,c6018c00,c6018c00,c6925800,...) at
> netisr_dispatch+0x20
> ether_demux(c6018c00,c6905900,3,0,3,...) at ether_demux+0x1a1
> ether_input(c6018c00,c6905900,c119f2d7,ff7,63,...) at ether_input+0x365
> em_rxeof(c5e8bd80,109,c6016180,0,c5b72cc8,...) at em_rxeof+0x133
> em_msix_rx(c5dc7600,c5b72cc8,c088e0b4,c0e13740,c60342b8,...) at
> em_msix_rx+0x25
> intr_event_execute_handlers(c5d807f8,c6034280,c0cac35e,533,c60342f0,...) at
> intr_event_execute_handlers+0x125
> ithread_loop(c603b4a0,c5b72d38,c0cac0cd,343,c5d807f8,...) at
> ithread_loop+0x9f
> fork_exit(c0876da0,c603b4a0,c5b72d38) at fork_exit+0xb8
>
> fork_trampoline() at fork_trampoline+0x8
> --- trap 0, eip = 0, esp = 0xc5b72d70, ebp = 0 ---
>
> Perhaps because multi-queue is still enabled ?
>
>
> 0(i5b)% vmstat -i
> interrupt                          total       rate
> irq4: uart0                         6637         28
> irq21: ehci0                         382          1
> irq23: ehci1                         615          2
> cpu0: timer                       462573       1993
> irq256: em0                         7640         32
> irq257: em1                            5          0
> irq258: em1                            6          0
>
> irq261: em1                            2          0
> irq262: ahci0                         69          0
> cpu3: timer                       461507       1989
> cpu2: timer                       460985       1987
> cpu1: timer                       461545       1989
> Total                            1861966       8025
> 0(i5b)%
>
>
> em0: <Intel(R) PRO/1000 Network Connection 7.0.3> port 0x3040-0x305f mem
> 0xc1b00000-0xc1b1ffff,0xc1b25000-0xc1b25fff irq 20 at device 25.0 on pci0
> em0: Using MSI interrupt
> em0: [FILTER]
> em0: Ethernet address: 00:15:17:c8:4b:99
> ehci0: <Intel PCH USB 2.0 controller USB-B> mem 0xc1b22000-0xc1b223ff irq
> 21 at device 26.0 on pci0
> ehci0: [ITHREAD]
> usbus0: EHCI version 1.0
> usbus0: <Intel PCH USB 2.0 controller USB-B> on ehci0
> pcib2: <ACPI PCI-PCI bridge> irq 16 at device 28.0 on pci0
> pci2: <ACPI PCI bus> on pcib2
> pcib3: <ACPI PCI-PCI bridge> irq 16 at device 28.4 on pci0
> pci3: <ACPI PCI bus> on pcib3
> em1: <Intel(R) PRO/1000 Network Connection 7.0.3> port 0x1000-0x101f mem
> 0xc1900000-0xc191ffff,0xc1920000-0xc1923fff irq 16 at device 0.0 on pci3
> em1: Using MSIX interrupts with 5 vectors
> em1: [ITHREAD]
> em1: [ITHREAD]
> em1: [ITHREAD]
> em1: [ITHREAD]
> em1: [ITHREAD]
> em1: Ethernet address: 00:15:17:c8:4b:98
>
>
>
> --------------------------------------------------------------------
> Mike Tancsa,                                      tel +1 519 651 3400
> Sentex Communications,                            mike_at_sentex.net
> Providing Internet since 1994                    www.sentex.net
> Cambridge, Ontario Canada                         www.sentex.net/mike
>
>
Received on Fri Apr 09 2010 - 19:11:56 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:40:02 UTC