* b43 regression
@ 2007-12-10 10:36 Michael Buesch
2007-12-11 1:14 ` Brennan Ashton
0 siblings, 1 reply; 5+ messages in thread
From: Michael Buesch @ 2007-12-10 10:36 UTC (permalink / raw)
To: John Linville; +Cc: bcm43xx-dev, linux-wireless
I have identified another regression introduced by
commit f04b3787bbce4567e28069a9ec97dcd804626ac7.
On my device it shows up as broken transmission after
a suspend/resume cycle. The workaround for it is to boot
a known good driver (in my case the vendor driver in OSX)
and then reboot (without turning the machine off) into the
broken driver.
It seems like we unintentionally removed some significant
initialization step in that patch. I could not identify it, yet.
The patch I sent yesterday did fix two other bugs, but not this one.
I am trying to find the reason for this.
If someone wants to help searching, the best way would be to look
at that patch I mentioned above and compare the stuff that it
removes to the stuff that it adds. There must be some tiny line
that it removes but does not re-add it at another place.
Four eyes see more than two.
I have no idea how this bug could be related to the few bugreports
in the redhat bugzilla. Though, one could test that by trying a
kernel that does not include the patch.
Sorry for the inconvenience.
--
Greetings Michael.
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: b43 regression
2007-12-10 10:36 b43 regression Michael Buesch
@ 2007-12-11 1:14 ` Brennan Ashton
2007-12-11 11:02 ` Michael Buesch
0 siblings, 1 reply; 5+ messages in thread
From: Brennan Ashton @ 2007-12-11 1:14 UTC (permalink / raw)
To: Michael Buesch; +Cc: John Linville, linux-wireless, bcm43xx-dev
On Dec 10, 2007 2:36 AM, Michael Buesch <mb@bu3sch.de> wrote:
> I have identified another regression introduced by
> commit f04b3787bbce4567e28069a9ec97dcd804626ac7.
>
> On my device it shows up as broken transmission after
> a suspend/resume cycle. The workaround for it is to boot
> a known good driver (in my case the vendor driver in OSX)
> and then reboot (without turning the machine off) into the
> broken driver.
>
> It seems like we unintentionally removed some significant
> initialization step in that patch. I could not identify it, yet.
> The patch I sent yesterday did fix two other bugs, but not this one.
>
> I am trying to find the reason for this.
> If someone wants to help searching, the best way would be to look
> at that patch I mentioned above and compare the stuff that it
> removes to the stuff that it adds. There must be some tiny line
> that it removes but does not re-add it at another place.
> Four eyes see more than two.
>
> I have no idea how this bug could be related to the few bugreports
> in the redhat bugzilla. Though, one could test that by trying a
> kernel that does not include the patch.
>
> Sorry for the inconvenience.
>
> --
> Greetings Michael.
> _______________________________________________
> Bcm43xx-dev mailing list
> Bcm43xx-dev@lists.berlios.de
> https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
>
RE:
https://bugzilla.redhat.com/show_bug.cgi?id=412861
I downloaded the source for 2.6.23.8-63.fc8.src.rpm the package that
things started to stop working at, and could not find any part of this
patch applied, so at least for that bug it is something else.
--
Brennan Ashton
Bellingham, Washington
"The box said, 'Requires Windows XP or better'. So I installed Linux"
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: b43 regression
2007-12-11 1:14 ` Brennan Ashton
@ 2007-12-11 11:02 ` Michael Buesch
2007-12-12 3:16 ` Brennan Ashton
0 siblings, 1 reply; 5+ messages in thread
From: Michael Buesch @ 2007-12-11 11:02 UTC (permalink / raw)
To: Brennan Ashton; +Cc: John Linville, linux-wireless, bcm43xx-dev
On Tuesday 11 December 2007 02:14:05 Brennan Ashton wrote:
> https://bugzilla.redhat.com/show_bug.cgi?id=412861
> I downloaded the source for 2.6.23.8-63.fc8.src.rpm the package that
> things started to stop working at, and could not find any part of this
> patch applied, so at least for that bug it is something else.
>
Please find out which patch broke it then. Nobody but you can do this.
--
Greetings Michael.
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: b43 regression
2007-12-11 11:02 ` Michael Buesch
@ 2007-12-12 3:16 ` Brennan Ashton
2007-12-12 10:42 ` Michael Buesch
0 siblings, 1 reply; 5+ messages in thread
From: Brennan Ashton @ 2007-12-12 3:16 UTC (permalink / raw)
To: Michael Buesch; +Cc: John Linville, linux-wireless, bcm43xx-dev
On Dec 11, 2007 3:02 AM, Michael Buesch <mb@bu3sch.de> wrote:
> On Tuesday 11 December 2007 02:14:05 Brennan Ashton wrote:
> > https://bugzilla.redhat.com/show_bug.cgi?id=412861
> > I downloaded the source for 2.6.23.8-63.fc8.src.rpm the package that
> > things started to stop working at, and could not find any part of this
> > patch applied, so at least for that bug it is something else.
> >
>
> Please find out which patch broke it then. Nobody but you can do this.
What do you use to hammer the card with data to see if if fails? I
have been just surfing the web, and moving data back and forth, but it
is very inefficient and a poor form of a test. I think I may have
narrowed down the kernel were it starting failing, but I want to make
sure.
--
Brennan Ashton
Bellingham, Washington
"The box said, 'Requires Windows XP or better'. So I installed Linux"
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: b43 regression
2007-12-12 3:16 ` Brennan Ashton
@ 2007-12-12 10:42 ` Michael Buesch
0 siblings, 0 replies; 5+ messages in thread
From: Michael Buesch @ 2007-12-12 10:42 UTC (permalink / raw)
To: Brennan Ashton; +Cc: John Linville, linux-wireless, bcm43xx-dev
On Wednesday 12 December 2007 04:16:22 Brennan Ashton wrote:
> On Dec 11, 2007 3:02 AM, Michael Buesch <mb@bu3sch.de> wrote:
> > On Tuesday 11 December 2007 02:14:05 Brennan Ashton wrote:
> > > https://bugzilla.redhat.com/show_bug.cgi?id=412861
> > > I downloaded the source for 2.6.23.8-63.fc8.src.rpm the package that
> > > things started to stop working at, and could not find any part of this
> > > patch applied, so at least for that bug it is something else.
> > >
> >
> > Please find out which patch broke it then. Nobody but you can do this.
>
> What do you use to hammer the card with data to see if if fails? I
You can use iperf or simply wget some file from a http server in the
network.
--
Greetings Michael.
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2007-12-12 10:44 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2007-12-10 10:36 b43 regression Michael Buesch
2007-12-11 1:14 ` Brennan Ashton
2007-12-11 11:02 ` Michael Buesch
2007-12-12 3:16 ` Brennan Ashton
2007-12-12 10:42 ` Michael Buesch
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).