Kernel panics with 7.2 and ANS
david.kinnvall at alertir.com
Fri Nov 9 00:42:01 CST 2001
I have begun testing these new drivers on my 7.2-machine
in the office. 13 hours of Cerberus and counting, with no
hiccups so far. Looking good! I will do some evil network
stuff as well, including failover during massive traffic.
Still curious about if and when versions for the later RH
errata kernels, preferably with source, will appear...?
(My reasoning: Since the errata kernels are officialy
released kernels, there should be officially supported
drivers for them as well, no? My 7.1-machines are still
running 2.4.3 because of this.)
----- Original Message -----
From: "Michael E Brown" <michael_e_brown at dell.com>
To: "David Kinnvall" <david.kinnvall at alertir.com>
Cc: <Linux-PowerEdge at dell.com>
Sent: Tuesday, November 06, 2001 5:15 PM
Subject: Re: Kernel panics with 7.2 and ANS
> Attached are the "Dell Official" Red Hat Linux 7.2 drivers for Intel
> Broadcom network cards. They are compiled for 2.4.7-10.
> I will officially announce them when we finally get the links into our
> download page. Our NIC team was delayed by a procedural problem
> them posted, but they should show up in the next week or so. These are
> the official released drivers for 7.2 and if you have any problems
> them please call Dell technical support.
> David Kinnvall wrote:
> >From: "Ard van Breemen" <ard at telegraafnet.nl>
> >>On Mon, Nov 05, 2001 at 10:45:59AM -0800, Jeremy Stoltz wrote:
> >>>I have several 1550's which I recently started using Intel's ANS
> >>>etherchannel. I was having problems with occasional kernel panics
> >>>machines. Yesterday I upgraded the machines to use e100-1.6.22 and
> >>>iANS-1.4.27. I saw a kernel panic on most of the machines with in a
> >>>hours of the upgrade.
> >>>I'm using Redhat 7.2 with 2.4.7-10smp on these machines. Any
> >>>how to
> >>>resolve this issue?
> >>Yes: use a serial console, and cut and paste the panics and the
> >>and send them to this list.
> >>Ehhh, also run them through ksymoops before sending them to this
> >>If the panic seemed to be caused by iANS, you have to contact intel.
> >>Anyway, by using iANS, your kernel is tainted, so support is less
> >>likely to come from kernel-hackers.
> >>But without the panics and the oopses, we cannot help you.
> >To add one more, albeit neither this one with anything more
> >helpful such as panics and/or oopses, I ran into this one as
> >well. Crashes with iANS loaded, on any kernel except the
> >2.4.3 from Red Hat 7.1. Upgrades to later kernels for 7.1
> >or a major upgrade to Red Hat 7.2 with any of the kernels
> >available for that release all lead to the same result:
> >crash and burn. Remove the iANS driver and all is well.
> >Temporary solution on my part: Run Red Hat 7.2 on my dev.
> >servers in-house without iANS, stay with Red Hat 7.1 and
> >2.4.3 on my production servers and wait. If I get the time
> >and hardware necessary I'll try to reproduce and record
> >some useful data next time around.
> >In other words: It's a problem with iANS and kernel revs.
> >This would be the time to bug Intel, I guess.
> >Linux-PowerEdge mailing list
> >Linux-PowerEdge at dell.com
More information about the Linux-PowerEdge