| To: | Anton Blanchard <anton@xxxxxxxxx> |
|---|---|
| Subject: | Re: network lockup with latest BK (LLTX?) |
| From: | jamal <hadi@xxxxxxxxxx> |
| Date: | 14 Sep 2004 10:53:48 -0400 |
| Cc: | netdev@xxxxxxxxxxx |
| In-reply-to: | <20040914142447.GA5615@krispykreme> |
| Organization: | jamalopolous |
| References: | <20040914142447.GA5615@krispykreme> |
| Reply-to: | hadi@xxxxxxxxxx |
| Sender: | netdev-bounce@xxxxxxxxxxx |
Yep LLTX, use patch posted by Andi yesterday. cheers, jamal On Tue, 2004-09-14 at 10:24, Anton Blanchard wrote: > Hi, > > I have a machine with a number of e1000 adapters in it. It locked up > while I was bringing up the network interfaces. I have attached > backtraces of all relevant cpus. > > There are a bunch of cpus in arp_xmit -> dev_queue_xmit, these all > appear to be stuck on the dev->queue_lock. Looking closer, all cpus > other than cpu 4 are stuck on the same spinlock. And since we store the > cpu number in our spinlocks, we know that this lock is owned by cpu4. > > Looking at cpu4: > > pfifo_fast_dequeue+0x58/0x78 |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | network lockup with latest BK (LLTX?), Anton Blanchard |
|---|---|
| Next by Date: | Re: network lockup with latest BK (LLTX?), Anton Blanchard |
| Previous by Thread: | network lockup with latest BK (LLTX?), Anton Blanchard |
| Next by Thread: | Re: network lockup with latest BK (LLTX?), Anton Blanchard |
| Indexes: | [Date] [Thread] [Top] [All Lists] |