Date: Wed, 19 Jun 2013 14:20:14 +0200 From: Andre Oppermann <andre@freebsd.org> To: Ian FREISLICH <ianf@clue.co.za> Cc: jeffr@FreeBSD.org, glebius@FreeBSD.org, current@freebsd.org Subject: Re: Panic in tcp_input Message-ID: <51C1A1FE.8040300@freebsd.org> In-Reply-To: <E1UpEmc-0000ls-7Q@clue.co.za> References: <51C17A3B.2030809@freebsd.org> <E1UpEPp-0000iW-Lq@clue.co.za> <E1UpEmc-0000ls-7Q@clue.co.za>
next in thread | previous in thread | raw e-mail | index | archive | help
On 19.06.2013 11:34, Ian FREISLICH wrote:
> Andre Oppermann wrote:
>> On 19.06.2013 11:10, Ian FREISLICH wrote:
>>> Hi
>>>
>>> I'm seeing this panic quite regularly now. Most recent sighting on r251858.
>>
>> This panic message is not very informative and very hard to extract any
>> meaningful hints. Do you have a core dump and matching debug kernel?
>
> I do. If you can send me your public ssh key in private email, I
> can give you access to the server in question.
It bombs while accessing a per-cpu counter:
(kgdb) frame 11
#11 0xffffffff8054518e in tcp_input (m=<value optimized out>, off0=Cannot access
memory at address 0x14)
at counter.h:45
45 __asm __volatile("addq\t%1,%%gs:(%0)"
This seems to be a fallout of the recent UMA changes and its interaction
with the per-cpu counter(9) system.
Adding in and handing over to Gleb and Jeff as they touched this area last.
--
Andre
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?51C1A1FE.8040300>