in6.c and panic: 0xc63dd000 must be migratable

[Doug Barton]

On 04/08/2011 17:57, Bjoern A. Zeeb wrote:
> On Fri, 8 Apr 2011, Doug Barton wrote:
>
>> Bjoern,
>>
>> We're seeing something very similar to the following with pf and IPv6:
>
> similar to what?

We're seeing the "must be migratable" part of the panic, but nothing else.

> It would be helpful to include more data in your problem reports.
>
> What freebsd release?

Yeah, sorry, not my best effort, but we were in the middle of a crisis. 
:)  This is 8-stable (post 8.2-RELEASE) i386.

> Can you reproduce it? If so, how?

Not at will, but it's happened twice now.

>> panic: 0xc63dd000 must be migratable
>> cpuid = 1
>> panic: 0xc63dd000 must be migratable
>> cpuid = 1
>> panic: 0xc63dd000 must be migratable
>> cpuid = 1
>> panic: 0xc63dd000 must be migratable
>> cpuid = 1
>> panic: 0xc63dd000 must be migratable
>> cpuid = 1
>> panic: 0xc63dd000 must be migratable
>> cpuid = 1
>> panic: 0xc63dd000 must be migratable
>> cpuid = 1

This is the bit we see. Breaking to the debugger hasn't worked, and 
dumping is not an option (I inherited this system, trying to get it 
tuned up now).

> Depsite being in the subject that's just follow-up problems, though
> thinking about it (very wild guess) -- how many cores do you have and are you
> running with flowtable enabled?

It's an SMP system, and yes, FLOWTABLE was in the kernel config. I took 
that out, and got the KDB options sorted out so that if it happens again 
hopefully I can get a stack trace. Thanks for the FLOWTABLE suggestion, 
wish I'd remembered that one myself. :)


Doug

-- 

	Nothin' ever doesn't change, but nothin' changes much.
			-- OK Go

	Breadth of IT experience, and depth of knowledge in the DNS.
	Yours for the right price.  :)  http://SupersetSolutions.com/