netdev - Re: Kernel Panics in the network stack

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 11 Dec 2009 19:44:17 -0500
From:	Neil Horman <nhorman@...driver.com>
To:	Kevin Constantine <kevin.constantine@...il.com>
Cc:	netdev@...r.kernel.org
Subject: Re: Kernel Panics in the network stack

On Fri, Dec 11, 2009 at 01:09:06PM -0800, Kevin Constantine wrote:
> Hey Everyone-
>
> I've been playing with an ARM based linuxstamp  
> http://opencircuits.com/Linuxstamp, and I've been seeing kernel panics  
> with both 2.6.28.3, and 2.6.30 within an hour or so of turning the  
> linuxstamp on.  The stack traces always seem to point at functions  
> related to networking.  I've pasted a couple of the crash outputs below.  
>  The linuxstamp isn't typically doing anything when the crashes occur,  
> in fact it'll crash even if I haven't logged in.
>
> If I ifconfig the interface down, the linuxstamp stays up indefinitely.  
> Any pointers in one direction or another would be much appreciated.
>
> I'm not sure if this is the right audience to help out or if the arm  
> lists might be better.  But in any event, any help would be really  
> appreciated.
>
>
Might be worth turning on slab debugging to see if you get any violations on
slabs prior to your oops.  I was just debugging something simmilar on e1000e,
and slab debug was an immense help

Neil

>
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html