public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: devzero@web.de
To: linux-kernel@vger.kernel.org
Cc: cebbert@redhat.com, hidave.darkstar@gmail.com, jeremy@goop.org
Subject: netsc520 - skeleton in the closet ?
Date: Sun, 13 Apr 2008 14:45:18 +0200	[thread overview]
Message-ID: <237143435@web.de> (raw)

i'm doing some module testing from time to time and i'm somewhat sure, that there is an issue with netsc520 module, as i have seen more than one occasion that after load/unloading of that module (w/o presence of the appropriate hw), other modules had issues.

see http://marc.info/?l=linux-kernel&m=120664963508105&w=2 for example.

now,by chance i came across this one: http://marc.info/?l=linux-kernel&m=118274309325836&w=2

>> > >> netsc520 is doing iounmap() of an area it did
>> > >> ioremap_nocache() on earlier, because it has now failed to
>> > >> find a device. Why it went BUG() I have no idea.
>> > >>
>> > >
>> > > Hi, maybe some config option cause this issue, here is my current
>> > > working-ok config file:
>> >
>> > What are the differences from the non-working config?
>> >
>> >     J
>> >
>> The diffrences is net520c item.
>>
>sorry it is netsc520, I will post the patch after a while.

so, it sounds there is a known issue with netsc520, but i'm not sure if it's the related and if that mentioned patch has been posted, at least i don't find it in git due to x86/64 unification.

maybe someone has a clue.... ?

_____________________________________________________________________
Der WEB.DE SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen!
http://smartsurfer.web.de/?mc=100071&distributionid=000000000066


             reply	other threads:[~2008-04-13 12:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-13 12:45 devzero [this message]
2008-04-14  1:35 ` netsc520 - skeleton in the closet ? Dave Young

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=237143435@web.de \
    --to=devzero@web.de \
    --cc=cebbert@redhat.com \
    --cc=hidave.darkstar@gmail.com \
    --cc=jeremy@goop.org \
    --cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox