Hi all,
Here is a list of some known regressions in 2.6.22-rc2.
Feel free to add new regressions/remove fixed etc.
http://kernelnewbies.org/known_regressions
Networking
Subject : OOPS triggered by ip(8) deconfiguring a network interface
References : http://bugzilla.kernel.org/show_bug.cgi?id=8491
Submitter : Ben Collins <[email protected]>
Status : Unknown
Subject : panic with e1000 driver on HP Integrity servers
References : http://bugzilla.kernel.org/show_bug.cgi?id=8455
Submitter : Doug Chapman <[email protected]>
Caused-By : Auke Kok <[email protected]>
commit e0aac5a289b1dacbc94bd9ae8c449bcdf9ab508c
Status : problem is being debugged
Regards,
Michal
--
Michal K. K. Piotrowski
Kernel Monkeys
(http://kernel.wikidot.com/start)
From: Michal Piotrowski <[email protected]>
Date: Sun, 20 May 2007 00:06:33 +0200
> Subject : OOPS triggered by ip(8) deconfiguring a network interface
> References : http://bugzilla.kernel.org/show_bug.cgi?id=8491
> Submitter : Ben Collins <[email protected]>
> Status : Unknown
Might be fixed by:
http://marc.info/?l=linux-netdev&m=117915849224816&w=2
I'll merge that patch in and we'll see what happens.
On Sat, 19 May 2007 15:38:29 -0700 (PDT)
David Miller <[email protected]> wrote:
> From: Michal Piotrowski <[email protected]>
> Date: Sun, 20 May 2007 00:06:33 +0200
>
> > Subject : OOPS triggered by ip(8) deconfiguring a network interface
> > References : http://bugzilla.kernel.org/show_bug.cgi?id=8491
> > Submitter : Ben Collins <[email protected]>
> > Status : Unknown
>
> Might be fixed by:
>
> http://marc.info/?l=linux-netdev&m=117915849224816&w=2
>
> I'll merge that patch in and we'll see what happens.
> -
> To unsubscribe from this list: send the line "unsubscribe netdev" in
> the body of a message to [email protected]
> More majordomo info at http://vger.kernel.org/majordomo-info.html
Looks more like the IPV6 SNMP6 OOPS, I saw and fixed with:
commit 5632c5152aa621885d87ea0b8fdd5a6bb9f69c6f
Author: Stephen Hemminger <[email protected]>
Date: Sat Apr 28 21:16:39 2007 -0700
[IPV6]: Track device renames in snmp6.
When network device's are renamed, the IPV6 snmp6 code
gets confused. It doesn't track name changes so it will OOPS
when network device's are removed.
The fix is trivial, just unregister/re-register in notify handler.
Signed-off-by: Stephen Hemminger <[email protected]>
Signed-off-by: David S. Miller <[email protected]>
--
Stephen Hemminger <[email protected]>
Stephen Hemminger <[email protected]> wrote:
>
> Looks more like the IPV6 SNMP6 OOPS, I saw and fixed with:
>
> commit 5632c5152aa621885d87ea0b8fdd5a6bb9f69c6f
> Author: Stephen Hemminger <[email protected]>
> Date: Sat Apr 28 21:16:39 2007 -0700
>
> [IPV6]: Track device renames in snmp6.
>
> When network device's are renamed, the IPV6 snmp6 code
> gets confused. It doesn't track name changes so it will OOPS
> when network device's are removed.
>
> The fix is trivial, just unregister/re-register in notify handler.
>
> Signed-off-by: Stephen Hemminger <[email protected]>
> Signed-off-by: David S. Miller <[email protected]>
It's quite possible that this fixes it, especially since the version
in Ubuntu's bug report came out the day before your fix went in :)
However, I don't really get why it's crashing in the first place.
Without your patch, if the device is renamed the proc entry just
keeps the original name. When it goes down it should still get
removed correctly.
Could you explain this in a bit more detail?
Thanks,
--
Visit Openswan at http://www.openswan.org/
Email: Herbert Xu ~{PmV>HI~} <[email protected]>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt