Thanks for the suggestions. I have tried the unpatched 2.6.33.7 kernel, and the problem does not occur. The hardware is a single board industrial computer with the network controllers onboard, so I cannot easily try different NICs. I have not seen the problem occur with only one port in use, but I have not tested that long enough to be positive. One thing that may be a little odd about this computer is that both Ethernet controllers (Intel 82559) share the same PCI interrupt. Interrupt sharing should be OK, but since adjacent PCI slots in normal PCs generally use different interrupts, it may not occur often in other systems. On Fri, Aug 13, 2010 at 1:56 PM, Darcy Watkins <DWatkins@xxxxxxxxxxx> wrote: > Hi John, > > I use Fedora 13 which has 2.6.33.6 as the kernel (without RT). > > My machine has three net i/f in it. Two PCI net cards with Realtek > chipset and Intel PRO built into the mainboard's chipset. > > When I installed Fedora using the netboot USB flash drive, it insisted > on using one of the Realtek interfaces for Internet connection so that > is my eth0. All fine. > > More recently, I activated the other two net i/f for private LAN to > target HW test network. I set one to 10.0.0.1 and the other to > 192.168.101.4 and connected them to the target network. Note that they > were both connected to the same network switch. > > Shortly after that, the system froze. After reboot it would run for a > while and then freeze. I unplugged the net i/f based on the Intel PRO > and all has been fine since. > > I mention all this because you once mentioned you were using two Intel > net i/f. It may not even be RT related. > > I suggest you try (not in any particular order, but each on its own)... > > - running with only one net i/f connected > - building a side-by-side vanilla kernel 2.6.33.7 (without RT patch) > and running your two net i/f without RT > - using different net i/f cards (say based on Realtek or something > other than Intel) try running it with RT > > If you see your system behavior change related to any of these, it > possibly may not be RT patch related (or it could be tied to a specific > driver). > > Regards, > > Darcy > > -----Original Message----- > From: linux-rt-users-owner@xxxxxxxxxxxxxxx > [mailto:linux-rt-users-owner@xxxxxxxxxxxxxxx] On Behalf Of John > Culvertson > Sent: Friday, August 13, 2010 10:38 AM > To: linux-rt-users@xxxxxxxxxxxxxxx > Subject: Re: 2.6.33.6-rt28 kernel oops while stressing network > > Since it was my understanding that x86 was the most mature and stable > architecture for preempt-rt, I was surprised when I immediately > encountered problems. Is this typical when trying the patches on a > new platform? Like I mentioned before, I am a newbie with preempt-rt. > > On Wed, Aug 11, 2010 at 12:53 PM, John Culvertson > <jculvertson@xxxxxxxxx> wrote: >> I updated to 2.6.33.7-rt29, and I am seeing similar symptoms. >> >> [ 2120.781166] BUG: unable to handle kernel paging request at c11cd497 >> [ 2120.784018] IP: [<c11d5ce2>] tcp_set_skb_tso_segs+0x33/0x85 >> [ 2120.784018] *pde = 1d7f6063 *pte = 011cd161 >> [ 2120.784018] Oops: 0003 [#1] PREEMPT > -- > To unsubscribe from this list: send the line "unsubscribe > linux-rt-users" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html > -- To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
