I just wanted to report that I found this problem on a Dell PowerEdge  
2850 (with the e1000 driver) as well.  However, upgrading to kernel  
2.6.9-11 on the PE 2850 seems to fix this problem, and I'm upgrading  
the kernel on the PE 750 this weekend and I suspect this will fix the  
problem on it as well.

Greg


On Jun 9, 2005, at 8:59 AM, Gregory Harris wrote:

> Interesting.  I am not using SCSI; I'm using the Dell CERC SATA  
> controller as well as iptables.  I guess I can either of them out  
> and see what happens.
>
> For reference, Here's my lspci output (minus the e1000 devices I  
> currently disabled in BIOS):
>
> 00:00.0 Host bridge: Intel Corp. 82875P/E7210 Memory Controller Hub  
> (rev 02)
> 00:1c.0 PCI bridge: Intel Corp. 6300ESB 64-bit PCI-X Bridge (rev 02)
> 00:1d.0 USB Controller: Intel Corp. 6300ESB USB Universal Host  
> Controller (rev 02)
> 00:1d.1 USB Controller: Intel Corp. 6300ESB USB Universal Host  
> Controller (rev 02)
> 00:1d.4 System peripheral: Intel Corp. 6300ESB Watchdog Timer (rev 02)
> 00:1d.5 PIC: Intel Corp. 6300ESB I/O Advanced Programmable  
> Interrupt Controller (rev 02)
> 00:1d.7 USB Controller: Intel Corp. 6300ESB USB2 Enhanced Host  
> Controller (rev 02)
> 00:1e.0 PCI bridge: Intel Corp. 82801 PCI Bridge (rev 0a)
> 00:1f.0 ISA bridge: Intel Corp. 6300ESB LPC Interface Controller  
> (rev 02)
> 00:1f.2 IDE interface: Intel Corp. 6300ESB SATA Storage Controller  
> (rev 02)
> 00:1f.3 SMBus: Intel Corp. 6300ESB SMBus Controller (rev 02)
> 01:01.0 RAID bus controller: Adaptec AAC-RAID (rev 01)
> 02:0e.0 VGA compatible controller: ATI Technologies Inc Rage XL  
> (rev 27)
>
> Thanks for your input.
>
> Greg
>
> Joakim Sernbrant wrote:
>
>> I have installed SL4 on a Dell PE650 without any problems. Not using
>> SCSI/iptables though...
>> [root@trick ~]# uname -a; lsmod; lspci
>> Linux trick 2.6.9-5.0.5.EL #1 Tue Apr 19 14:33:20 CDT 2005 i686 i686
>> i386 GNU/Linux
>> Module                  Size  Used by
>> md5                     4033  1
>> ipv6                  232833  14
>> parport_pc             24705  0
>> lp                     12077  0
>> parport                37129  2 parport_pc,lp
>> autofs4                23237  0
>> sunrpc                157093  1
>> button                  6481  0
>> battery                 8901  0
>> ac                      4805  0
>> ohci_hcd               21329  0
>> e1000                  79309  0
>> floppy                 58481  0
>> dm_snapshot            17029  0
>> dm_zero                 2369  0
>> dm_mirror              22957  2
>> ext3                  116809  2
>> jbd                    71257  1 ext3
>> dm_mod                 54741  6 dm_snapshot,dm_zero,dm_mirror
>> 00:00.0 Host bridge: ServerWorks GCNB-LE Host Bridge (rev 32)
>> 00:00.1 Host bridge: ServerWorks GCNB-LE Host Bridge
>> 00:04.0 VGA compatible controller: ATI Technologies Inc Rage XL  
>> (rev 27)
>> 00:05.0 IDE interface: Silicon Image, Inc. (formerly CMD  
>> Technology Inc)
>> PCI0680 Ultra ATA-133 Host Controller (rev 02)
>> 00:0f.0 Host bridge: ServerWorks CSB6 South Bridge (rev a0)
>> 00:0f.1 IDE interface: ServerWorks CSB6 RAID/IDE Controller (rev a0)
>> 00:0f.2 USB Controller: ServerWorks CSB6 OHCI USB Controller (rev 05)
>> 00:0f.3 ISA bridge: ServerWorks GCLE-2 Host Bridge
>> 00:10.0 Host bridge: ServerWorks CIOB-E I/O Bridge with Gigabit  
>> Ethernet
>> (rev 12)
>> 00:10.2 Host bridge: ServerWorks CIOB-E I/O Bridge with Gigabit  
>> Ethernet
>> (rev 12)
>> 01:03.0 Ethernet controller: Intel Corp. 82546EB Gigabit Ethernet
>> Controller (Copper) (rev 01)
>> 01:03.1 Ethernet controller: Intel Corp. 82546EB Gigabit Ethernet
>> Controller (Copper) (rev 01)
>>
>>> -----Original Message-----
>>> From: [log in to unmask]  
>>> [mailto:[log in to unmask]] On Behalf  
>>> Of Gregory Harris
>>> Sent: Wednesday, June 08, 2005 23:40
>>> To: John Franks
>>> Cc: [log in to unmask]
>>> Subject: Re: SL4 on dell poweredge 750 problems
>>>
>>> I have been doing more investigation on this issue.  You are  
>>> right about the ethernet drivers.  But it does not only happen  
>>> when using ssh, it also happens at the console until a ping  
>>> packet (or some other network activity) brings the race condition  
>>> back to normal.
>>>
>>> After disabling the two onboard e1000 network ports and  
>>> installing a 3c905 network card, the race condition no longer  
>>> occurs.  So I believe that there is a problem with the e1000  
>>> kernel module causing a race condition.  I have only been able to  
>>> verify this on the PowerEdge 750. If anybody else has an e1000  
>>> card and would like to test this it would be great, but I would  
>>> wager this problem exists on all systems with the e1000 driver.
>>>
>>> I guess for now, I will sit it out with a different network card  
>>> replacing the onboard one until the upstream vendor releases a  
>>> new kernel fix.
>>>
>>> Greg
>>>
>>> John Franks wrote:
>>>
>>>
>>>> Does this happen only when using ssh?  If so, I would suspect  
>>>> issues
>>>> with the ethernet drivers.  There have been problems with
>>>>
>>>
>>> the drivers
>>>
>>>
>>>> for some Broadcom devices.  You might check out redhat bugzilla.
>>>> On Fri, 2005-05-13 at 09:08 -0500, Gregory Harris wrote:
>>>>
>>>>
>>>>
>>>>> Hi Folks,
>>>>>
>>>>> SL4 works great on all of the Dell Optiplex GX280's I've
>>>>>
>>>
>>> tried it on.
>>>
>>>>> However, I'm having some rather mysterious behavior on a
>>>>>
>>>
>>> dell poweredge
>>>
>>>>> 750.  Dell has said they will start certifying hardware and
>>>>>
>>>
>>> officially
>>>
>>>>> supporting the vendor's enterprise 4 operating system next
>>>>>
>>>
>>> month, so it
>>>
>>>>> may not be worth the effort to try to figure this out.  Anyhow,  
>>>>> I thought I'd sent to the list and see if anybody else is  
>>>>> having any issues like this.
>>>>>
>>>>> 1.  Sometimes, processes just seem to hang.  I've noticed
>>>>>
>>>
>>> this over an
>>>
>>>>> SSH session, a lot of times when using the yum command.  I
>>>>>
>>>
>>> ssh in to the
>>>
>>>>> server and see the process still in the process table.
>>>>>
>>>>> 2.  Doing a 'service iptables restart', the system stalls on  
>>>>> the "Unloading iptables modules:".  If I go to a different
>>>>>
>>>
>>> window and ping
>>>
>>>>> the server, the iptables service restart resumes.
>>>>>
>>>>> These issues aren't sounding like userland issues to me,
>>>>>
>>>
>>> although they
>>>
>>>>> very well could be.  Here are the kernel modules the
>>>>>
>>>
>>> machine is using:
>>>
>>>
>>>>> Module                  Size  Used by
>>>>> ipt_REJECT             10561  1
>>>>> ipt_state               5825  14
>>>>> ip_conntrack           45701  1 ipt_state
>>>>> iptable_filter          6721  1
>>>>> ip_tables              21441  3  
>>>>> ipt_REJECT,ipt_state,iptable_filter
>>>>> md5                     8001  1
>>>>> ipv6                  238945  16
>>>>> parport_pc             27905  0
>>>>> lp                     15405  0
>>>>> parport                37641  2 parport_pc,lp
>>>>> autofs4                22085  0
>>>>> nfs                   200997  6
>>>>> lockd                  65129  2 nfs
>>>>> sunrpc                137637  9 nfs,lockd
>>>>> dm_mod                 57157  0
>>>>> button                 10449  0
>>>>> battery                12869  0
>>>>> ac                      8773  0
>>>>> uhci_hcd               32473  0
>>>>> ehci_hcd               31813  0
>>>>> e1000                  82253  0
>>>>> floppy                 58065  0
>>>>> ext3                  118473  3
>>>>> jbd                    59481  1 ext3
>>>>> ata_piix               12357  0
>>>>> libata                 44229  1 ata_piix
>>>>> aacraid                44529  4
>>>>> sd_mod                 20545  5
>>>>> scsi_mod              116301  3 libata,aacraid,sd_mod
>>>>>
>>>>> Thanks,
>>>>>
>>>>> Greg
>>>>>
>>>>>
>>>>>
>>>
>>> -- 
>>>
>>> Gregory Harris
>>> Network Specialist
>>> Department of Mathematics
>>> The University of Kansas
>>> [log in to unmask]
>>> (785) 864-7311
>>>
>>>
>
> -- 
>
> Gregory Harris
> Network Specialist
> Department of Mathematics
> The University of Kansas
> [log in to unmask]
> (785) 864-7311
>