Hi folks, Built servers with Centos 5, and installed the lustre rhel5_x86 rpms successfully, modified grub and booted in to the new kernel. Configured a mgs/mdt two OSTs and a client. Now when running iozone from the client I always receive a kernel panic in the lines of: Call trace: <IRQ> [<ffffffff88149e4b>] : bnx2:bnx2_start_xmt+0x49/0x4d8 Code: 49 8b 85 e8 00 00 00 RIP [<ffffffff88146e91>] : bnx2:bnx2_poll+0xf7/0xb75 RSP <......> CR2: 0..... <0> Kernel Panic - not syncing : Fatal Exception I can grab the full panic if it''s beneficial. When I bounce the client and remount I can access the lustre fs fine, seems to be purely a client issue. Any ideas? Thanks, Matt -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.lustre.org/pipermail/lustre-discuss/attachments/20071107/133b1535/attachment-0002.html
Hi folks, Built servers with Centos 5, and installed the lustre rhel5_x86 rpms successfully, modified grub and booted in to the new kernel. Configured a mgs/mdt two OSTs and a client. Now when running iozone from the client I always receive a kernel panic in the lines of: Call trace: <IRQ> [<ffffffff88149e4b>] : bnx2:bnx2_start_xmt+0x49/0x4d8 Code: 49 8b 85 e8 00 00 00 RIP [<ffffffff88146e91>] : bnx2:bnx2_poll+0xf7/0xb75 RSP <......> CR2: 0..... <0> Kernel Panic - not syncing : Fatal Exception I have attached a screenshot. When I bounce the client and remount I can access the lustre fs fine, seems to be purely a client issue. Any ideas? Thanks, Matt -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.lustre.org/pipermail/lustre-discuss/attachments/20071107/93451b98/attachment-0002.html -------------- next part -------------- A non-text attachment was scrubbed... Name: sl09_kernelPanic.JPG Type: image/jpeg Size: 906536 bytes Desc: not available Url : http://lists.lustre.org/pipermail/lustre-discuss/attachments/20071107/93451b98/attachment-0002.jpe
Bernd Schubert
2007-Nov-07 12:35 UTC
[Lustre-discuss] Fwd: lustre 1.6.3 prod - client kernel panic
Hi Matt, On Wednesday 07 November 2007 12:50:32 Matt wrote:> Hi folks, > > Built servers with Centos 5, and installed the lustre rhel5_x86 rpms > successfully, modified grub and booted in to the new kernel. > > Configured a mgs/mdt two OSTs and a client. > > Now when running iozone from the client I always receive a kernel panic in > the lines of: > > Call trace: <IRQ> [<ffffffff88149e4b>] : bnx2:bnx2_start_xmt+0x49/0x4d8 > Code: 49 8b 85 e8 00 00 00 > RIP [<ffffffff88146e91>] : bnx2:bnx2_poll+0xf7/0xb75 RSP <......> > CR2: 0..... > <0> Kernel Panic - not syncing : Fatal Exception > > I have attached a screenshot. > > When I bounce the client and remount I can access the lustre fs fine, seems > to be purely a client issue. > > Any ideas?looks very much like a bug in the broadcom nx2 driver. I would send it to linux-netdev. And as a first try I would check whats happens when you disable MSI for this driver. Cheers, Bernd -- Bernd Schubert Q-Leap Networks GmbH
Balagopal Pillai
2007-Nov-07 13:15 UTC
[Lustre-discuss] Fwd: lustre 1.6.3 prod - client kernel panic
Hi,
Looks like the broadcom driver issue to me too. I had the
similar problem with kernel panic
for the Lustre kernel on Dell pe1950 with Centos 4.5 and updating the
bnx2 driver solved the issue.
Also the interface has the tendency to drop frames. Increasing the rx
ring parameters with ethtool
fixes that problem.
Regards
Balagopal
Bernd Schubert wrote:> Hi Matt,
>
> On Wednesday 07 November 2007 12:50:32 Matt wrote:
>
>> Hi folks,
>>
>> Built servers with Centos 5, and installed the lustre rhel5_x86 rpms
>> successfully, modified grub and booted in to the new kernel.
>>
>> Configured a mgs/mdt two OSTs and a client.
>>
>> Now when running iozone from the client I always receive a kernel panic
in
>> the lines of:
>>
>> Call trace: <IRQ> [<ffffffff88149e4b>] :
bnx2:bnx2_start_xmt+0x49/0x4d8
>> Code: 49 8b 85 e8 00 00 00
>> RIP [<ffffffff88146e91>] : bnx2:bnx2_poll+0xf7/0xb75 RSP
<......>
>> CR2: 0.....
>> <0> Kernel Panic - not syncing : Fatal Exception
>>
>> I have attached a screenshot.
>>
>> When I bounce the client and remount I can access the lustre fs fine,
seems
>> to be purely a client issue.
>>
>> Any ideas?
>>
>
> looks very much like a bug in the broadcom nx2 driver. I would send it to
> linux-netdev. And as a first try I would check whats happens when you
disable
> MSI for this driver.
>
> Cheers,
> Bernd
>
>
>
>
I think you guys are spot on, this client is running on a Dell 1950. I''m in the process of rebuilding the box with the Centos 5 kernel along with the source so I can patch it with lustre to build my own kernel and obviously build the bnx2 driver. I would obviously rather just use the lustre rpm''s like I have been doing, but was unable to build the bnx2 driver against the lustre kernel source. I''m guessing because it''s not complete. If anyone knows any different then please say so. Cheers, Matt On 07/11/2007, Balagopal Pillai <pillai at mathstat.dal.ca> wrote:> > Hi, > > Looks like the broadcom driver issue to me too. I had the > similar problem with kernel panic > for the Lustre kernel on Dell pe1950 with Centos 4.5 and updating the > bnx2 driver solved the issue. > Also the interface has the tendency to drop frames. Increasing the rx > ring parameters with ethtool > fixes that problem. > > > Regards > Balagopal > > Bernd Schubert wrote: > > Hi Matt, > > > > On Wednesday 07 November 2007 12:50:32 Matt wrote: > > > >> Hi folks, > >> > >> Built servers with Centos 5, and installed the lustre rhel5_x86 rpms > >> successfully, modified grub and booted in to the new kernel. > >> > >> Configured a mgs/mdt two OSTs and a client. > >> > >> Now when running iozone from the client I always receive a kernel panic > in > >> the lines of: > >> > >> Call trace: <IRQ> [<ffffffff88149e4b>] : bnx2:bnx2_start_xmt+0x49/0x4d8 > >> Code: 49 8b 85 e8 00 00 00 > >> RIP [<ffffffff88146e91>] : bnx2:bnx2_poll+0xf7/0xb75 RSP <......> > >> CR2: 0..... > >> <0> Kernel Panic - not syncing : Fatal Exception > >> > >> I have attached a screenshot. > >> > >> When I bounce the client and remount I can access the lustre fs fine, > seems > >> to be purely a client issue. > >> > >> Any ideas? > >> > > > > looks very much like a bug in the broadcom nx2 driver. I would send it > to > > linux-netdev. And as a first try I would check whats happens when you > disable > > MSI for this driver. > > > > Cheers, > > Bernd > > > > > > > > > > _______________________________________________ > Lustre-discuss mailing list > Lustre-discuss at clusterfs.com > https://mail.clusterfs.com/mailman/listinfo/lustre-discuss >-------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.lustre.org/pipermail/lustre-discuss/attachments/20071107/beaa98a5/attachment-0002.html
Wojciech Turek
2007-Nov-07 15:35 UTC
[Lustre-discuss] Fwd: lustre 1.6.3 prod - client kernel panic
Hi, What Kernel version you are using for your production Lustre? Is it pre-patched 2.6.9-55.0.9.EL_lustre.1.6.3smp ? We had very similar problem with bnx2 driver on old kernel 2.6.9. Upgrading kernel to latest version helped. The bnx2 issue is mentioned in the kernel''s release notes. Best regards, Wojciech On 7 Nov 2007, at 15:19, Matt wrote:> I think you guys are spot on, this client is running on a Dell 1950. > > I''m in the process of rebuilding the box with the Centos 5 kernel > along with the source so I can patch it with lustre to build my own > kernel and obviously build the bnx2 driver. > > I would obviously rather just use the lustre rpm''s like I have been > doing, but was unable to build the bnx2 driver against the lustre > kernel source. I''m guessing because it''s not complete. > > If anyone knows any different then please say so. > > Cheers, > > Matt > > On 07/11/2007, Balagopal Pillai <pillai at mathstat.dal.ca> wrote: > Hi, > > Looks like the broadcom driver issue to me too. I had the > similar problem with kernel panic > for the Lustre kernel on Dell pe1950 with Centos 4.5 and updating the > bnx2 driver solved the issue. > Also the interface has the tendency to drop frames. Increasing the rx > ring parameters with ethtool > fixes that problem. > > > Regards > Balagopal > > Bernd Schubert wrote: > > Hi Matt, > > > > On Wednesday 07 November 2007 12:50:32 Matt wrote: > > > >> Hi folks, > >> > >> Built servers with Centos 5, and installed the lustre rhel5_x86 > rpms > >> successfully, modified grub and booted in to the new kernel. > >> > >> Configured a mgs/mdt two OSTs and a client. > >> > >> Now when running iozone from the client I always receive a > kernel panic in > >> the lines of: > >> > >> Call trace: <IRQ> [<ffffffff88149e4b>] : bnx2:bnx2_start_xmt > +0x49/0x4d8 > >> Code: 49 8b 85 e8 00 00 00 > >> RIP [<ffffffff88146e91>] : bnx2:bnx2_poll+0xf7/0xb75 RSP <......> > >> CR2: 0..... > >> <0> Kernel Panic - not syncing : Fatal Exception > >> > >> I have attached a screenshot. > >> > >> When I bounce the client and remount I can access the lustre fs > fine, seems > >> to be purely a client issue. > >> > >> Any ideas? > >> > > > > looks very much like a bug in the broadcom nx2 driver. I would > send it to > > linux-netdev. And as a first try I would check whats happens when > you disable > > MSI for this driver. > > > > Cheers, > > Bernd > > > > > > > > > > _______________________________________________ > Lustre-discuss mailing list > Lustre-discuss at clusterfs.com > https://mail.clusterfs.com/mailman/listinfo/lustre-discuss > > _______________________________________________ > Lustre-discuss mailing list > Lustre-discuss at clusterfs.com > https://mail.clusterfs.com/mailman/listinfo/lustre-discussMr Wojciech Turek Assistant System Manager University of Cambridge High Performance Computing service email: wjt27 at cam.ac.uk tel. +441223763517 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.lustre.org/pipermail/lustre-discuss/attachments/20071107/f3f000a7/attachment-0002.html
Balagopal Pillai
2007-Nov-07 15:54 UTC
[Lustre-discuss] Fwd: lustre 1.6.3 prod - client kernel panic
Hi,
Since its centos 5 , it will be 2.6.18 series. 2.6.9-55 is the
rhel 4.5 or centos 4.5 series kernel. For the bnx2 build from source,
the complete Lustre rebuild is not needed. There was an extra step to
prepare the Lustre kernel sources form the src rpm, so that extra
modules can
be built from the kernel source. I don''t remember that. Probably
someone
in the list can help. I replaced the bnx2 driver that came with
Lustre kernel with the latest one built from sources on the dell 1950
and didn''t have that panic problem yet. Also ethtool -G <interface
name>
rx 4080
solves the frame drop issue for bnx2.
Regards
Balagopal
Wojciech Turek wrote:> Hi,
>
> What Kernel version you are using for your production Lustre? Is
> it pre-patched 2.6.9-55.0.9.EL_lustre.1.6.3smp ?
> We had very similar problem with bnx2 driver on old kernel 2.6.9.
> Upgrading kernel to latest version helped. The bnx2 issue is mentioned
> in the kernel''s release notes.
>
> Best regards,
>
> Wojciech
> On 7 Nov 2007, at 15:19, Matt wrote:
>
>> I think you guys are spot on, this client is running on a Dell 1950.
>>
>> I''m in the process of rebuilding the box with the Centos 5
kernel
>> along with the source so I can patch it with lustre to build my own
>> kernel and obviously build the bnx2 driver.
>>
>> I would obviously rather just use the lustre rpm''s like I have
been
>> doing, but was unable to build the bnx2 driver against the lustre
>> kernel source. I''m guessing because it''s not
complete.
>>
>> If anyone knows any different then please say so.
>>
>> Cheers,
>>
>> Matt
>>
>> On 07/11/2007, *Balagopal Pillai* <pillai at mathstat.dal.ca
>> <mailto:pillai at mathstat.dal.ca>> wrote:
>>
>> Hi,
>>
>> Looks like the broadcom driver issue to me too. I had
the
>> similar problem with kernel panic
>> for the Lustre kernel on Dell pe1950 with Centos 4.5 and updating
the
>> bnx2 driver solved the issue.
>> Also the interface has the tendency to drop frames. Increasing the
rx
>> ring parameters with ethtool
>> fixes that problem.
>>
>>
>> Regards
>> Balagopal
>>
>> Bernd Schubert wrote:
>> > Hi Matt,
>> >
>> > On Wednesday 07 November 2007 12:50:32 Matt wrote:
>> >
>> >> Hi folks,
>> >>
>> >> Built servers with Centos 5, and installed the lustre
>> rhel5_x86 rpms
>> >> successfully, modified grub and booted in to the new
kernel.
>> >>
>> >> Configured a mgs/mdt two OSTs and a client.
>> >>
>> >> Now when running iozone from the client I always receive a
>> kernel panic in
>> >> the lines of:
>> >>
>> >> Call trace: <IRQ> [<ffffffff88149e4b>] :
>> bnx2:bnx2_start_xmt+0x49/0x4d8
>> >> Code: 49 8b 85 e8 00 00 00
>> >> RIP [<ffffffff88146e91>] : bnx2:bnx2_poll+0xf7/0xb75
RSP <......>
>> >> CR2: 0.....
>> >> <0> Kernel Panic - not syncing : Fatal Exception
>> >>
>> >> I have attached a screenshot.
>> >>
>> >> When I bounce the client and remount I can access the
lustre
>> fs fine, seems
>> >> to be purely a client issue.
>> >>
>> >> Any ideas?
>> >>
>> >
>> > looks very much like a bug in the broadcom nx2 driver. I would
>> send it to
>> > linux-netdev. And as a first try I would check whats happens
>> when you disable
>> > MSI for this driver.
>> >
>> > Cheers,
>> > Bernd
>> >
>> >
>> >
>> >
>>
>> _______________________________________________
>> Lustre-discuss mailing list
>> Lustre-discuss at clusterfs.com <mailto:Lustre-discuss at
clusterfs.com>
>> https://mail.clusterfs.com/mailman/listinfo/lustre-discuss
>>
>>
>> _______________________________________________
>> Lustre-discuss mailing list
>> Lustre-discuss at clusterfs.com <mailto:Lustre-discuss at
clusterfs.com>
>> https://mail.clusterfs.com/mailman/listinfo/lustre-discuss
>
> Mr Wojciech Turek
> Assistant System Manager
> University of Cambridge
> High Performance Computing service
> email: wjt27 at cam.ac.uk <mailto:wjt27 at cam.ac.uk>
> tel. +441223763517
>
>
>
Balagopal Pillai
2007-Nov-07 16:01 UTC
[Lustre-discuss] Fwd: lustre 1.6.3 prod - client kernel panic
Hi,
Now i remember what i did to build the bnx2 sources. Here is the
part from Lustre Manual.
"
The kernel-source and lustre-source packages are provided in case you
need to build external kernel modules or use additional network types.
They are not required to run Lustre.
Once you have your Lustre source tree you can build Lustre by running
the sequence of commands given below.
$ cd <path to kernel tree>
$ cp /boot/config-''uname -r'' .config
$ make oldconfig || make menuconfig
# For 2.6 kernels
$ make include/asm
$ make include/linux/version.h
$ make SUBDIRS=scripts
"
This is it!!
Regards
Balagopal
Matt wrote:> I think you guys are spot on, this client is running on a Dell 1950.
>
> I''m in the process of rebuilding the box with the Centos 5 kernel
> along with the source so I can patch it with lustre to build my own
> kernel and obviously build the bnx2 driver.
>
> I would obviously rather just use the lustre rpm''s like I have
been
> doing, but was unable to build the bnx2 driver against the lustre
> kernel source. I''m guessing because it''s not complete.
>
> If anyone knows any different then please say so.
>
> Cheers,
>
> Matt
>
> On 07/11/2007, *Balagopal Pillai* <pillai at mathstat.dal.ca
> <mailto:pillai at mathstat.dal.ca>> wrote:
>
> Hi,
>
> Looks like the broadcom driver issue to me too. I had the
> similar problem with kernel panic
> for the Lustre kernel on Dell pe1950 with Centos 4.5 and updating the
> bnx2 driver solved the issue.
> Also the interface has the tendency to drop frames. Increasing the rx
> ring parameters with ethtool
> fixes that problem.
>
>
> Regards
> Balagopal
>
> Bernd Schubert wrote:
> > Hi Matt,
> >
> > On Wednesday 07 November 2007 12:50:32 Matt wrote:
> >
> >> Hi folks,
> >>
> >> Built servers with Centos 5, and installed the lustre
rhel5_x86
> rpms
> >> successfully, modified grub and booted in to the new kernel.
> >>
> >> Configured a mgs/mdt two OSTs and a client.
> >>
> >> Now when running iozone from the client I always receive a
> kernel panic in
> >> the lines of:
> >>
> >> Call trace: <IRQ> [<ffffffff88149e4b>] :
> bnx2:bnx2_start_xmt+0x49/0x4d8
> >> Code: 49 8b 85 e8 00 00 00
> >> RIP [<ffffffff88146e91>] : bnx2:bnx2_poll+0xf7/0xb75 RSP
<......>
> >> CR2: 0.....
> >> <0> Kernel Panic - not syncing : Fatal Exception
> >>
> >> I have attached a screenshot.
> >>
> >> When I bounce the client and remount I can access the lustre
fs
> fine, seems
> >> to be purely a client issue.
> >>
> >> Any ideas?
> >>
> >
> > looks very much like a bug in the broadcom nx2 driver. I would
> send it to
> > linux-netdev. And as a first try I would check whats happens
> when you disable
> > MSI for this driver.
> >
> > Cheers,
> > Bernd
> >
> >
> >
> >
>
> _______________________________________________
> Lustre-discuss mailing list
> Lustre-discuss at clusterfs.com <mailto:Lustre-discuss at
clusterfs.com>
> https://mail.clusterfs.com/mailman/listinfo/lustre-discuss
>
>
Cheers Balagopal! I was in the process of building my own kernel, which looks to have worked - I got the rpms in the build directory. But I followed your commands to enable me to build it under the Centos5 with the lustre kernel source installed. Working like a charm now! How did you see if the interface was dropping frames? On 07/11/2007, Balagopal Pillai <pillai at mathstat.dal.ca> wrote:> > Hi, > > Now i remember what i did to build the bnx2 sources. Here is the > part from Lustre Manual. > > " > > The kernel-source and lustre-source packages are provided in case you > need to build external kernel modules or use additional network types. > They are not required to run Lustre. > > Once you have your Lustre source tree you can build Lustre by running > the sequence of commands given below. > > $ cd <path to kernel tree> > > $ cp /boot/config-''uname -r'' .config > > $ make oldconfig || make menuconfig > > # For 2.6 kernels > > $ make include/asm > > $ make include/linux/version.h > > $ make SUBDIRS=scripts > > " > > This is it!! > > > Regards > Balagopal > > > > > > Matt wrote: > > I think you guys are spot on, this client is running on a Dell 1950. > > > > I''m in the process of rebuilding the box with the Centos 5 kernel > > along with the source so I can patch it with lustre to build my own > > kernel and obviously build the bnx2 driver. > > > > I would obviously rather just use the lustre rpm''s like I have been > > doing, but was unable to build the bnx2 driver against the lustre > > kernel source. I''m guessing because it''s not complete. > > > > If anyone knows any different then please say so. > > > > Cheers, > > > > Matt > > > > On 07/11/2007, *Balagopal Pillai* <pillai at mathstat.dal.ca > > <mailto:pillai at mathstat.dal.ca>> wrote: > > > > Hi, > > > > Looks like the broadcom driver issue to me too. I had > the > > similar problem with kernel panic > > for the Lustre kernel on Dell pe1950 with Centos 4.5 and updating > the > > bnx2 driver solved the issue. > > Also the interface has the tendency to drop frames. Increasing the > rx > > ring parameters with ethtool > > fixes that problem. > > > > > > Regards > > Balagopal > > > > Bernd Schubert wrote: > > > Hi Matt, > > > > > > On Wednesday 07 November 2007 12:50:32 Matt wrote: > > > > > >> Hi folks, > > >> > > >> Built servers with Centos 5, and installed the lustre rhel5_x86 > > rpms > > >> successfully, modified grub and booted in to the new kernel. > > >> > > >> Configured a mgs/mdt two OSTs and a client. > > >> > > >> Now when running iozone from the client I always receive a > > kernel panic in > > >> the lines of: > > >> > > >> Call trace: <IRQ> [<ffffffff88149e4b>] : > > bnx2:bnx2_start_xmt+0x49/0x4d8 > > >> Code: 49 8b 85 e8 00 00 00 > > >> RIP [<ffffffff88146e91>] : bnx2:bnx2_poll+0xf7/0xb75 RSP <......> > > >> CR2: 0..... > > >> <0> Kernel Panic - not syncing : Fatal Exception > > >> > > >> I have attached a screenshot. > > >> > > >> When I bounce the client and remount I can access the lustre fs > > fine, seems > > >> to be purely a client issue. > > >> > > >> Any ideas? > > >> > > > > > > looks very much like a bug in the broadcom nx2 driver. I would > > send it to > > > linux-netdev. And as a first try I would check whats happens > > when you disable > > > MSI for this driver. > > > > > > Cheers, > > > Bernd > > > > > > > > > > > > > > > > _______________________________________________ > > Lustre-discuss mailing list > > Lustre-discuss at clusterfs.com <mailto:Lustre-discuss at clusterfs.com> > > https://mail.clusterfs.com/mailman/listinfo/lustre-discuss > > > > >-------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.lustre.org/pipermail/lustre-discuss/attachments/20071108/12652393/attachment-0002.html
Balagopal Pillai
2007-Nov-08 13:29 UTC
[Lustre-discuss] Fwd: lustre 1.6.3 prod - client kernel panic
Hi,
The interface won''t drop frames on light load. It will start
dropping eventually. Please try ifconfig <interface> and see any errors
or drops or
overruns. If you see some, try the detailed statistics for the interface
with ethtool. This is especially bad for the ost/mds/mgs servers.
I had instability for Lustre with the servers randomly crashing and
volumes hanging up on clients. I blamed the LACP and bonding on the
servers initially. But it turned out to be the massive drop
of frames on the bonded interface that caused it. After fixing the
problem, its stable.
Regards
Balagopal
Matt wrote:> Cheers Balagopal! I was in the process of building my own kernel,
> which looks to have worked - I got the rpms in the build directory.
>
> But I followed your commands to enable me to build it under the
> Centos5 with the lustre kernel source installed. Working like a charm
> now!
>
> How did you see if the interface was dropping frames?
>
> On 07/11/2007, *Balagopal Pillai* <pillai at mathstat.dal.ca
> <mailto:pillai at mathstat.dal.ca>> wrote:
>
> Hi,
>
> Now i remember what i did to build the bnx2 sources. Here
> is the
> part from Lustre Manual.
>
> "
>
> The kernel-source and lustre-source packages are provided in case you
> need to build external kernel modules or use additional network types.
> They are not required to run Lustre.
>
> Once you have your Lustre source tree you can build Lustre by running
> the sequence of commands given below.
>
> $ cd <path to kernel tree>
>
> $ cp /boot/config-''uname -r'' .config
>
> $ make oldconfig || make menuconfig
>
> # For 2.6 kernels
>
> $ make include/asm
>
> $ make include/linux/version.h
>
> $ make SUBDIRS=scripts
>
> "
>
> This is it!!
>
>
> Regards
> Balagopal
>
>
>
>
>
> Matt wrote:
> > I think you guys are spot on, this client is running on a Dell
1950.
> >
> > I''m in the process of rebuilding the box with the Centos
5 kernel
> > along with the source so I can patch it with lustre to build my
own
> > kernel and obviously build the bnx2 driver.
> >
> > I would obviously rather just use the lustre rpm''s like I
have been
> > doing, but was unable to build the bnx2 driver against the lustre
> > kernel source. I''m guessing because it''s not
complete.
> >
> > If anyone knows any different then please say so.
> >
> > Cheers,
> >
> > Matt
> >
> > On 07/11/2007, *Balagopal Pillai* < pillai at mathstat.dal.ca
> <mailto:pillai at mathstat.dal.ca>
> > <mailto:pillai at mathstat.dal.ca <mailto:pillai at
mathstat.dal.ca>>>
> wrote:
> >
> > Hi,
> >
> > Looks like the broadcom driver issue to me too.
> I had the
> > similar problem with kernel panic
> > for the Lustre kernel on Dell pe1950 with Centos 4.5 and
> updating the
> > bnx2 driver solved the issue.
> > Also the interface has the tendency to drop frames.
> Increasing the rx
> > ring parameters with ethtool
> > fixes that problem.
> >
> >
> > Regards
> > Balagopal
> >
> > Bernd Schubert wrote:
> > > Hi Matt,
> > >
> > > On Wednesday 07 November 2007 12:50:32 Matt wrote:
> > >
> > >> Hi folks,
> > >>
> > >> Built servers with Centos 5, and installed the lustre
> rhel5_x86
> > rpms
> > >> successfully, modified grub and booted in to the new
kernel.
> > >>
> > >> Configured a mgs/mdt two OSTs and a client.
> > >>
> > >> Now when running iozone from the client I always
receive a
> > kernel panic in
> > >> the lines of:
> > >>
> > >> Call trace: <IRQ> [<ffffffff88149e4b>] :
> > bnx2:bnx2_start_xmt+0x49/0x4d8
> > >> Code: 49 8b 85 e8 00 00 00
> > >> RIP [<ffffffff88146e91>] :
bnx2:bnx2_poll+0xf7/0xb75 RSP
> <......>
> > >> CR2: 0.....
> > >> <0> Kernel Panic - not syncing : Fatal
Exception
> > >>
> > >> I have attached a screenshot.
> > >>
> > >> When I bounce the client and remount I can access the
> lustre fs
> > fine, seems
> > >> to be purely a client issue.
> > >>
> > >> Any ideas?
> > >>
> > >
> > > looks very much like a bug in the broadcom nx2 driver. I
> would
> > send it to
> > > linux-netdev. And as a first try I would check whats
happens
> > when you disable
> > > MSI for this driver.
> > >
> > > Cheers,
> > > Bernd
> > >
> > >
> > >
> > >
> >
> > _______________________________________________
> > Lustre-discuss mailing list
> > Lustre-discuss at clusterfs.com
> <mailto:Lustre-discuss at clusterfs.com>
> <mailto:Lustre-discuss at clusterfs.com
> <mailto:Lustre-discuss at clusterfs.com>>
> > https://mail.clusterfs.com/mailman/listinfo/lustre-discuss
> <https://mail.clusterfs.com/mailman/listinfo/lustre-discuss>
> >
> >
>
>