On 10 June 2011 19:48, K. Macy wrote:
> This recent commit changed the way that the value for size being
> passed to m_getjcl is initialized. Not seeing any obvious bugs, and
> not having any additional context I would guess that that you're
> receiving an interrupt before adapter->rx_mbuf_sz is s
Interrupts are not enabled til after that is set, so I don't think this
theory
works, sorry.
Jack
On Fri, Jun 10, 2011 at 12:48 PM, K. Macy wrote:
> This recent commit changed the way that the value for size being
> passed to m_getjcl is initialized. Not seeing any obvious bugs, and
> not havi
This recent commit changed the way that the value for size being
passed to m_getjcl is initialized. Not seeing any obvious bugs, and
not having any additional context I would guess that that you're
receiving an interrupt before adapter->rx_mbuf_sz is set. I trust jfv@
to look in to this shortly.
h
On Fri, June 10, 2011 11:22 am, Kim Culhan wrote:
> Booting from FreeBSD-9.0-CURRENT-201105-amd64-memstick
> the kernel panics:
>
> panic: m_getzone: m_getjcl: invalid cluster type
Found a ps2 keyboard works in the debugger (not usb) and backtrace is here:
http://www.flickr.com/photos/opensolaris
Booting from FreeBSD-9.0-CURRENT-201105-amd64-memstick
the kernel panics:
panic: m_getzone: m_getjcl: invalid cluster type
http://www.flickr.com/photos/opensolaris/5818432532/in/photostream
The hardware is:
http://www.supermicro.com/products/motherboard/QPI/5500/X8DTL-3F.cfm
The cpu's are Inte
