| To: | davem@xxxxxxxxxx (David S. Miller) |
|---|---|
| Subject: | Re: Oops: Process zebra, EIP is at fib_create_info+0x22b/0x580 |
| From: | Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx> |
| Date: | Sun, 22 Aug 2004 18:06:46 +1000 |
| Cc: | vrsbs@xxxxxxxxxxx, netdev@xxxxxxxxxxx |
| In-reply-to: | <20040821221751.547feefe.davem@redhat.com> |
| Organization: | Core |
| Sender: | netdev-bounce@xxxxxxxxxxx |
| User-agent: | tin/1.7.4-20040225 ("Benbecula") (UNIX) (Linux/2.4.26-1-686-smp (i686)) |
David S. Miller <davem@xxxxxxxxxx> wrote: > On Sun, 22 Aug 2004 00:04:17 +0300 > Joonas Kortesalmi <vrsbs@xxxxxxxxxxx> wrote: > >> Running 2.6.8.1 and got a nice Oops from zebra (quagga). > > Can you figure out where exactly this OOPS is in fib_create_info()? This is very similar to the report in the message titled "2.6.8 + sargs = pb" where fib_info_list was corrupted. In fact, the corrupted fib_next value here is exactly the same as the other report. Not only that, the value appears to be a valid i386 instruction possibly coming from somewhere else in net/ipv4 code. Do you know of any changes between 2.6.7 and 2.6.8 that might impact on the FIB stuff? Any locking changes? Thanks, -- Visit Openswan at http://www.openswan.org/ Email: Herbert Xu ~{PmV>HI~} <herbert@xxxxxxxxxxxxxxxxxxx> Home Page: http://gondor.apana.org.au/~herbert/ PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: 2.6.8-rc4-bk1 problem: unregister_netdevice: waiting for ppp0 to become free. Usage count = 1, Nuno Silva |
|---|---|
| Next by Date: | Re: 2.6.8-rc4-bk1 problem: unregister_netdevice: waiting for ppp0 to become free. Usage count = 1, Herbert Xu |
| Previous by Thread: | Re: Oops: Process zebra, EIP is at fib_create_info+0x22b/0x580, David S. Miller |
| Next by Thread: | Re: Oops: Process zebra, EIP is at fib_create_info+0x22b/0x580, Herbert Xu |
| Indexes: | [Date] [Thread] [Top] [All Lists] |