public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
* Followup: PROBLEM: Kernel bug at tg3.c:2456
  2005-03-30 17:50 Sergio Chiesa
@ 2005-03-31 12:34 ` Sergio Chiesa
  0 siblings, 0 replies; 3+ messages in thread
From: Sergio Chiesa @ 2005-03-31 12:34 UTC (permalink / raw)
  To: linux-kernel

Sergio Chiesa wrote:

> 7.7.
> Well, it seems that with the original onboard raid controller the bug
> didn't trigger... the controller was swapped with the lsi logic by my
> supplier because it fails badly with raid-5 arrays (hw/fw related issue)
> I also tried the original broadcom driver version 7.3.5 with similar
> results...

I made some tests again, switching back to the onboard dual aic7902 scsi 
controller (non raid) the tg3 dont hung anymore.
I just noticed the IRQ mappings change between the two settings.
The Broadcom eth get always the IRQ #25, the two onboard scsi controllers 
get #24 and #25 (shared with the eth, is it harmful??) but the megaraid 
driver gets the IRQ #28

I think it is something IRQ related because if the eth hungs but the kernel 
is still running I see more than 140000 irq per second with "vmstat".

Hope it helps better!

Sergioc.

^ permalink raw reply	[flat|nested] 3+ messages in thread

* RE: Followup: PROBLEM: Kernel bug at tg3.c:2456
@ 2005-04-04 12:27 Ju, Seokmann
  2005-04-04 15:04 ` Sergio Chiesa
  0 siblings, 1 reply; 3+ messages in thread
From: Ju, Seokmann @ 2005-04-04 12:27 UTC (permalink / raw)
  To: 'Sergio Chiesa', linux-kernel

On Thursday, March 31, 2005 7:34 AM, Sergio wrote:
> I made some tests again, switching back to the onboard dual 
> aic7902 scsi 
> controller (non raid) the tg3 dont hung anymore.
> I just noticed the IRQ mappings change between the two settings.
> The Broadcom eth get always the IRQ #25, the two onboard scsi 
> controllers 
> get #24 and #25 (shared with the eth, is it harmful??) but 
> the megaraid 
> driver gets the IRQ #28
Can you please specify megaraid driver version?
It seems the megaraid driver gets unique IRQ and the IRQ dedicated to the
MegaRAID controller.
I don't see any problem concerning IRQ at this time. Difference of
performance in between MegaRAID and Adaptec can contribute the issue.

> Usually there
> are no messages on screen, but the last time I get "Kernel bug at
> tg3.c:2456"!! on the sender. The skb pointer in the tx_ring_info was
> null.... May it be queue overrun?
I would suggest to look into the issue from above perspective. 

Thank you.

Seokmann
LSI Logic Corporation.


> -----Original Message-----
> From: Sergio Chiesa [mailto:sergio.chiesa@eutelia.it] 
> Sent: Thursday, March 31, 2005 7:34 AM
> To: linux-kernel@vger.kernel.org
> Subject: Followup: PROBLEM: Kernel bug at tg3.c:2456
> 
> Sergio Chiesa wrote:
> 
> > 7.7.
> > Well, it seems that with the original onboard raid 
> controller the bug
> > didn't trigger... the controller was swapped with the lsi 
> logic by my
> > supplier because it fails badly with raid-5 arrays (hw/fw 
> related issue)
> > I also tried the original broadcom driver version 7.3.5 with similar
> > results...
> 
> I made some tests again, switching back to the onboard dual 
> aic7902 scsi 
> controller (non raid) the tg3 dont hung anymore.
> I just noticed the IRQ mappings change between the two settings.
> The Broadcom eth get always the IRQ #25, the two onboard scsi 
> controllers 
> get #24 and #25 (shared with the eth, is it harmful??) but 
> the megaraid 
> driver gets the IRQ #28
> 
> I think it is something IRQ related because if the eth hungs 
> but the kernel 
> is still running I see more than 140000 irq per second with "vmstat".
> 
> Hope it helps better!
> 
> Sergioc.
> -
> To unsubscribe from this list: send the line "unsubscribe 
> linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
> 

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: Followup: PROBLEM: Kernel bug at tg3.c:2456
  2005-04-04 12:27 Followup: PROBLEM: Kernel bug at tg3.c:2456 Ju, Seokmann
@ 2005-04-04 15:04 ` Sergio Chiesa
  0 siblings, 0 replies; 3+ messages in thread
From: Sergio Chiesa @ 2005-04-04 15:04 UTC (permalink / raw)
  To: linux-kernel; +Cc: Ju, Seokmann

Ju, Seokmann wrote:

> Can you please specify megaraid driver version?

the v2.4.29 bundled one, v2.10.3.
I'm going to try the last one from your site, the 2.10.9


>>Usually there
>>are no messages on screen, but the last time I get "Kernel bug at
>>tg3.c:2456"!! on the sender. The skb pointer in the tx_ring_info was
>>null.... May it be queue overrun?
> 
> I would suggest to look into the issue from above perspective. 

I found two very old posts (mid 2002) which recall very similar behaviou. I 
didn't find any fix to this two.

http://groups-beta.google.com/group/mlist.linux.kernel/browse_thread/thread/56c3c65c939f0baa/fd63101a0b32ea21?q=tg3&rnum=2#fd63101a0b32ea21
http://groups-beta.google.com/group/mlist.linux.kernel/browse_thread/thread/8b962774c3c5adef/ca778af36b802362?q=tg3&rnum=6#ca778af36b802362


TIA
Sergioc.

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2005-04-04 15:04 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2005-04-04 12:27 Followup: PROBLEM: Kernel bug at tg3.c:2456 Ju, Seokmann
2005-04-04 15:04 ` Sergio Chiesa
  -- strict thread matches above, loose matches on Subject: below --
2005-03-30 17:50 Sergio Chiesa
2005-03-31 12:34 ` Followup: " Sergio Chiesa

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox