Re: Frequent network code panics

[Masanobu SAITOH <msaitoh%execsw.org@localhost>]

On 2017/03/28 16:07, Hauke Fath wrote:
> On Tue, 28 Mar 2017 14:16:05 +0900, Masanobu SAITOH wrote:
> > > or, with either ixg0 of wm0,
> >
> > ixg0 "or" wm0?
>
> Yes, of course, sorry.
>
> > Could you show me the stack trace of wm?
>
> fatal page fault in supervisor mode
> trap type 6 code 0 rip ffffffff801d5cab cs 8 rflags 10202 cr2 20000000c
> ilevel 6 rsp fffffe810e873c88
> curlwp 0xfffffe821e73b840 pid 0.2 lowest kstack 0xfffffe810e8712c0
> panic: trap
> cpu0: Begin traceback...
> vpanic() at netbsd:vpanic+0x13c
> snprintf() at netbsd:snprintf
> startlwp() at netbsd:startlwp
> alltraps() at netbsd:alltraps+0x96
> wm_intr() at netbsd:wm_intr+0x3e0
> intr_biglock_wrapper() at netbsd:intr_biglock_wrapper+0x19
> Xintr_ioapic_level1() at netbsd:Xintr_ioapic_level1+0xf2
> --- interrupt ---
> x86_mwait() at netbsd:x86_mwait+0xd
> acpicpu_cstate_idle_enter() at netbsd:acpicpu_cstate_idle_enter+0xc2
> acpicpu_cstate_idle() at netbsd:acpicpu_cstate_idle+0x6d
> idle_loop() at netbsd:idle_loop+0xe8
> cpu0: End traceback...
> rebooting...
>
> Cheerio,
> hauke

someone (carp, pf or othes) broke memory?

Source code line of the following two address
might show what happened, but it would hard
to know the reason...

> wm_intr() at netbsd:wm_intr+0x3e0

> ixgbe_rxeof.isra.9() at netbsd:ixgbe_rxeof.isra.9+0x14a


--
-----------------------------------------------
                SAITOH Masanobu (msaitoh%execsw.org@localhost
                                 msaitoh%netbsd.org@localhost)