Summary: | [bce] [panic] kernel panic in bce0 driver | ||
---|---|---|---|
Product: | Base System | Reporter: | Konstantin <Konstantin.Malov> |
Component: | kern | Assignee: | freebsd-bugs (Nobody) <bugs> |
Status: | Open --- | ||
Severity: | Affects Only Me | Keywords: | crash |
Priority: | Normal | ||
Version: | Unspecified | ||
Hardware: | Any | ||
OS: | Any |
Description
Konstantin
2011-02-24 14:10:07 UTC
Responsible Changed From-To: freebsd-bugs->freebsd-net Over to maintainer(s). Looks like 131209 bug report has the same root cause with 155004 http://www.freebsd.org/cgi/query-pr.cgi?pr=131209 -- Konstantin Malov External Services Group system administrator Kaspersky Lab. - Russian Federation Tel: +7(495)797-8700 (ext. 2867) http://www.kaspersky.com<http://www.kaspersky.com/> State Changed From-To: open->feedback As you see, this backtrace looks wrong. It can't generate a NULL pointer dereference at line 5771. Are you using stock bce(4) without any changes? Probably the m0 could be a NULL and it could be dereferenced later. Could you go frame 8 and do the following? p m0 p sw_rx_cons_idx p sc->rx_mbuf_ptr[sw_rx_cons_idx] By chance, did the panic happen when you reboot your box or down/up the interface? Or if you happen to know a way to reproduce the issue could you share it with us? Responsible Changed From-To: freebsd-net->yongari Grab. For bugs matching the following criteria: Status: In Progress Changed: (is less than) 2014-06-01 Reset to default assignee and clear in-progress tags. Mail being skipped Keyword: crash – in lieu of summary line prefix: [panic] * bulk change for the keyword * summary lines may be edited manually (not in bulk). Keyword descriptions and search interface: <https://bugs.freebsd.org/bugzilla/describekeywords.cgi> |