From: Michael Buesch <mb@bu3sch.de>
To: Maximilian Engelhardt <maxi@daemonizer.de>
Cc: netdev <netdev@vger.kernel.org>,
"linux-kernel" <linux-kernel@vger.kernel.org>,
"linux-wireless" <linux-wireless@vger.kernel.org>,
Gary Zambrano <zambrano@broadcom.com>,
Stephen Hemminger <shemminger@linux-foundation.org>,
"Jeff Garzik" <jgarzik@pobox.com>,
"Arnaldo Carvalho de Melo" <acme@ghostprotocols.net>
Subject: Re: b44: high ping times with wireless-dev
Date: Sun, 17 Jun 2007 14:12:44 +0200 [thread overview]
Message-ID: <200706171412.45074.mb@bu3sch.de> (raw)
In-Reply-To: <200706171403.34299.maxi@daemonizer.de>
On Sunday 17 June 2007 14:03:30 Maximilian Engelhardt wrote:
> On Sunday 17 June 2007, Michael Buesch wrote:
> > On Saturday 16 June 2007 23:27:43 Maximilian Engelhardt wrote:
> > > [...]
> > > ACPI: PCI Interrupt Link [LNKD] enabled at IRQ 10
> > > ACPI: PCI Interrupt 0000:02:02.0[A] -> Link [LNKD] -> GSI 10 (level, low)
> > > -> IRQ 10
> > > ssb: Sonics Silicon Backplane found on PCI device 0000:02:02.0
> > > b44.c:v2.0
> > > eth0: Broadcom 44xx/47xx 10/100BaseT Ethernet 00:c0:9f:29:99:a7
> > > [...]
> >
> > Ok, I prepared two debugging patches.
> >
> > Please enable SonicsSiliconBackplane Debugging in the kernel kconfig,
> > so I can get more detail information about your card.
> > Device Drivers/Sonics Silicon Backplane/SSB debugging
> > (Must disable "No SSB kernel messages")
> >
> > Please apply and test the attached debugging patches in a row.
> > So apply patch 1 and test if it works again. If not, apply
> > patch 2 and test if it works.
> > Always save complete dmesg log on each test run and send it to me.
> >
> > Thanks for testing.
> > (This time it seems we are actually getting somewhere, when
> > dealing with sane people. :D )
>
> I did the tests with my kernel where only the card is on interrupt 10. dmesg
> is attached.
> With the first patch applied networking does work again. I also additionally
> tried patch2 and it also does work.
Great!
To me this seems to be a silicon bug. The IRQ routing value, which is read
from the chip here, is hardcoded in the old b44 driver.
I'll implement a workaround for this and submit a patch.
--
Greetings Michael.
WARNING: multiple messages have this Message-ID (diff)
From: Michael Buesch <mb-fseUSCV1ubazQB+pC5nmwQ@public.gmane.org>
To: Maximilian Engelhardt <maxi-OwNUvPV92VfddJNmlsFzeA@public.gmane.org>
Cc: netdev <netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"linux-kernel"
<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"linux-wireless"
<linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Gary Zambrano <zambrano-dY08KVG/lbpWk0Htik3J/w@public.gmane.org>,
Stephen Hemminger
<shemminger-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org>,
"Jeff Garzik" <jgarzik-e+AXbWqSrlAAvxtiuMwx3w@public.gmane.org>,
"Arnaldo Carvalho de Melo"
<acme-f8uhVLnGfZaxAyOMLChx1axOck334EZe@public.gmane.org>
Subject: Re: b44: high ping times with wireless-dev
Date: Sun, 17 Jun 2007 14:12:44 +0200 [thread overview]
Message-ID: <200706171412.45074.mb@bu3sch.de> (raw)
In-Reply-To: <200706171403.34299.maxi-OwNUvPV92VfddJNmlsFzeA@public.gmane.org>
On Sunday 17 June 2007 14:03:30 Maximilian Engelhardt wrote:
> On Sunday 17 June 2007, Michael Buesch wrote:
> > On Saturday 16 June 2007 23:27:43 Maximilian Engelhardt wrote:
> > > [...]
> > > ACPI: PCI Interrupt Link [LNKD] enabled at IRQ 10
> > > ACPI: PCI Interrupt 0000:02:02.0[A] -> Link [LNKD] -> GSI 10 (level, low)
> > > -> IRQ 10
> > > ssb: Sonics Silicon Backplane found on PCI device 0000:02:02.0
> > > b44.c:v2.0
> > > eth0: Broadcom 44xx/47xx 10/100BaseT Ethernet 00:c0:9f:29:99:a7
> > > [...]
> >
> > Ok, I prepared two debugging patches.
> >
> > Please enable SonicsSiliconBackplane Debugging in the kernel kconfig,
> > so I can get more detail information about your card.
> > Device Drivers/Sonics Silicon Backplane/SSB debugging
> > (Must disable "No SSB kernel messages")
> >
> > Please apply and test the attached debugging patches in a row.
> > So apply patch 1 and test if it works again. If not, apply
> > patch 2 and test if it works.
> > Always save complete dmesg log on each test run and send it to me.
> >
> > Thanks for testing.
> > (This time it seems we are actually getting somewhere, when
> > dealing with sane people. :D )
>
> I did the tests with my kernel where only the card is on interrupt 10. dmesg
> is attached.
> With the first patch applied networking does work again. I also additionally
> tried patch2 and it also does work.
Great!
To me this seems to be a silicon bug. The IRQ routing value, which is read
from the chip here, is hardcoded in the old b44 driver.
I'll implement a workaround for this and submit a patch.
--
Greetings Michael.
next prev parent reply other threads:[~2007-06-17 12:12 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-16 21:27 b44: high ping times with wireless-dev Maximilian Engelhardt
2007-06-16 22:49 ` Stephen Hemminger
2007-06-16 22:49 ` Stephen Hemminger
2007-06-17 0:42 ` Maximilian Engelhardt
2007-06-17 2:32 ` Michael Buesch
2007-06-17 2:32 ` Michael Buesch
2007-06-17 10:55 ` Michael Buesch
2007-06-17 11:08 ` Michael Buesch
2007-06-17 11:08 ` Michael Buesch
2007-06-17 12:03 ` Maximilian Engelhardt
2007-06-17 12:03 ` Maximilian Engelhardt
2007-06-17 12:12 ` Michael Buesch [this message]
2007-06-17 12:12 ` Michael Buesch
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200706171412.45074.mb@bu3sch.de \
--to=mb@bu3sch.de \
--cc=acme@ghostprotocols.net \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=maxi@daemonizer.de \
--cc=netdev@vger.kernel.org \
--cc=shemminger@linux-foundation.org \
--cc=zambrano@broadcom.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.