From: Andrew Morton <akpm@linux-foundation•org>
To: Michael <michael@moffatt•org.nz>
Cc: netdev@vger•kernel.org, bugzilla-daemon@bugzilla•kernel.org,
bugme-daemon@bugzilla•kernel.org,
Alan Cox <alan@lxorguk•ukuu.org.uk>
Subject: Re: [Bugme-new] [Bug 15091] New: starfire causes kernel BUG when interface goes up
Date: Mon, 25 Jan 2010 17:51:41 -0800 [thread overview]
Message-ID: <20100125175141.cf53de2b.akpm@linux-foundation.org> (raw)
In-Reply-To: <4B5E48FF.2050406@moffatt.org.nz>
On Tue, 26 Jan 2010 14:44:31 +1300 Michael <michael@moffatt•org.nz> wrote:
> Hi Andrew,
>
> I believe that this is a regression, yes.
>
> I will attempt to compile up some kernels this week and provide more
> info. Should I start at 26 and go up or at 31 and go down?
>
> I can't use anything lower than 26 according to udev. I was running 24
> but compiled 32 when I upgraded udev.
>
Thanks.
Starfire is a pretty rarely-used driver, I suspect. Hopefully someone
who understands the NAPI stuff can look at the code and go "ah-hah",
and save you all that work.
But if that doesn't happen then yup, a bisection would be good, thanks.
The best way to do it really is with git.
http://landley.net/writing/git-quick.html has an explanation.
next prev parent reply other threads:[~2010-01-26 1:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-15091-10286@http.bugzilla.kernel.org/>
2010-01-26 1:08 ` [Bugme-new] [Bug 15091] New: starfire causes kernel BUG when interface goes up Andrew Morton
2010-01-26 1:44 ` Michael
2010-01-26 1:51 ` Andrew Morton [this message]
2010-01-26 2:02 ` [PATCH] starfire: Clean up properly if firmware loading fails Ben Hutchings
2010-01-26 2:15 ` Andrew Morton
2010-01-26 2:32 ` Ben Hutchings
2010-01-26 2:58 ` Michael
2010-01-26 3:28 ` Andrew Morton
2010-01-26 5:51 ` Michael
2010-01-26 5:57 ` Andrew Morton
2010-01-26 14:40 ` Ben Hutchings
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=20100125175141.cf53de2b.akpm@linux-foundation.org \
--to=akpm@linux-foundation$(echo .)org \
--cc=alan@lxorguk$(echo .)ukuu.org.uk \
--cc=bugme-daemon@bugzilla$(echo .)kernel.org \
--cc=bugzilla-daemon@bugzilla$(echo .)kernel.org \
--cc=michael@moffatt$(echo .)org.nz \
--cc=netdev@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox