I think you guys are spot on, this client is running on a Dell 1950.<br><br>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.
<br><br>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.<br><br>If anyone knows any different then please say so.
<br><br>Cheers,<br><br>Matt<br><br><div><span class="gmail_quote">On 07/11/2007, <b class="gmail_sendername">Balagopal Pillai</b> <<a href="mailto:pillai@mathstat.dal.ca">pillai@mathstat.dal.ca</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi,<br><br> Looks like the broadcom driver issue to me too. I had the<br>similar problem with kernel panic<br>for the Lustre kernel on Dell pe1950 with Centos 4.5 and updating the<br>bnx2 driver solved the issue.
<br>Also the interface has the tendency to drop frames. Increasing the rx<br>ring parameters with ethtool<br>fixes that problem.<br><br><br>Regards<br>Balagopal<br><br>Bernd Schubert wrote:<br>> Hi Matt,<br>><br>> On Wednesday 07 November 2007 12:50:32 Matt wrote:
<br>><br>>> Hi folks,<br>>><br>>> Built servers with Centos 5, and installed the lustre rhel5_x86 rpms<br>>> successfully, modified grub and booted in to the new kernel.<br>>><br>>> Configured a mgs/mdt two OSTs and a client.
<br>>><br>>> Now when running iozone from the client I always receive a kernel panic in<br>>> the lines of:<br>>><br>>> Call trace: <IRQ> [<ffffffff88149e4b>] : bnx2:bnx2_start_xmt+0x49/0x4d8
<br>>> Code: 49 8b 85 e8 00 00 00<br>>> RIP [<ffffffff88146e91>] : bnx2:bnx2_poll+0xf7/0xb75 RSP <......><br>>> CR2: 0.....<br>>> <0> Kernel Panic - not syncing : Fatal Exception
<br>>><br>>> I have attached a screenshot.<br>>><br>>> When I bounce the client and remount I can access the lustre fs fine, seems<br>>> to be purely a client issue.<br>>><br>>> Any ideas?
<br>>><br>><br>> looks very much like a bug in the broadcom nx2 driver. I would send it to<br>> linux-netdev. And as a first try I would check whats happens when you disable<br>> MSI for this driver.<br>
><br>> Cheers,<br>> Bernd<br>><br>><br>><br>><br><br>_______________________________________________<br>Lustre-discuss mailing list<br><a href="mailto:Lustre-discuss@clusterfs.com">Lustre-discuss@clusterfs.com
</a><br><a href="https://mail.clusterfs.com/mailman/listinfo/lustre-discuss">https://mail.clusterfs.com/mailman/listinfo/lustre-discuss</a><br></blockquote></div><br>