From: Oliver Hartkopp <oliver@hartkopp.net>
To: Michael Marineau <mike@marineau.org>
Cc: David Miller <davem@davemloft.net>,
jaswinder@infradead.org, jgarzik@redhat.com,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-next@vger.kernel.org, mchan@broadcom.com
Subject: Re: [PATCH -net-next 3/4] firmware: convert tg3 driver to request_firmware()
Date: Wed, 07 Jan 2009 10:31:23 +0100 [thread overview]
Message-ID: <4964766B.2080105@hartkopp.net> (raw)
In-Reply-To: <20090107031724.GA6118@porter.dyn.128.marineau.org>
Michael Marineau wrote:
> On Mon, Jan 05, 2009 at 04:01:12PM -0800, David Miller wrote:
>
>> From: Oliver Hartkopp <oliver@hartkopp.net>
>> Date: Mon, 05 Jan 2009 14:28:30 +0100
>>
>>
>>> 2. I got this inconsistent lock state, i've not seen before:
>>>
>> I know what causes it. It's this change:
>>
>> commit 22604c866889c4b2e12b73cbf1683bda1b72a313
>> Author: Michael Marineau <mike@marineau.org>
>> Date: Sun Jan 4 17:18:51 2009 -0800
>>
>> net: Fix for initial link state in 2.6.28
>>
>> It causes us to now call the linkwatch even trigger code inside of
>> software interrupt context, but that is illegal because that code path
>> takes the dev_base_lock rwlock as a writer.
>>
>> I'm going to revert, and Michael will need to find a way to fix the
>> initial link state issue without adding locking problems :-)
>>
>
> Ok, here's another try. Rather than find a safer way to sync up the
> operstate variable with the normal state flags I decided to just nuke
> operstate entirely, it just duplicated what was already in the state
> flags for the most part.
Hi Michael,
i just compiled my current net-2.6 with your new patch and had no
problems booting my machine afterwards.
Holding the relevant information in one place looks like a good approach
to me even though i did not test the functionality in detail.
Thanks,
Oliver
next prev parent reply other threads:[~2009-01-07 9:31 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-30 8:41 [PATCH -net-next 3/4] firmware: convert tg3 driver to request_firmware() Jaswinder Singh Rajput
2009-01-05 0:11 ` David Miller
2009-01-05 13:28 ` Oliver Hartkopp
2009-01-05 13:58 ` Oliver Hartkopp
2009-01-05 14:12 ` Jaswinder Singh Rajput
2009-01-05 14:22 ` David Woodhouse
2009-01-05 14:47 ` Jaswinder Singh Rajput
2009-01-05 14:58 ` Oliver Hartkopp
2009-01-05 15:06 ` Jaswinder Singh Rajput
2009-01-06 0:01 ` David Miller
2009-01-07 3:17 ` Michael Marineau
2009-01-07 9:31 ` Oliver Hartkopp [this message]
2009-01-07 23:06 ` Michael Marineau
2009-01-13 0:10 ` David Miller
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=4964766B.2080105@hartkopp.net \
--to=oliver@hartkopp.net \
--cc=davem@davemloft.net \
--cc=jaswinder@infradead.org \
--cc=jgarzik@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mchan@broadcom.com \
--cc=mike@marineau.org \
--cc=netdev@vger.kernel.org \
/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.