From: supersud501 <supersud501@yahoo.de>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Stephen Hemminger <shemminger@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
netdev@vger.kernel.org, linux-acpi@vger.kernel.org,
bugme-daemon@bugzilla.kernel.org
Subject: Re: [Bugme-new] [Bug 9721] New: wake on lan fails with sky2 module
Date: Sun, 13 Jan 2008 16:08:38 +0100 [thread overview]
Message-ID: <478A2976.9000204@yahoo.de> (raw)
In-Reply-To: <478A1083.5060406@yahoo.de>
supersud501 wrote:
>
>
> Rafael J. Wysocki wrote:
>
>>
>> Since it seems to be 100% reproducible, it would be very helpful if
>> you could
>> use git-bisect to identify the offending commit.
>>
>
> allright, bisect found the offending commit, here's what i've done:
>
> first i started bisect with the following command (since i assumed it is
> a net-driver problem):
>
> git-bisect start 'v2.6.24-rc6' 'v2.6.23' '--' 'drivers/net/'
>
> after building many kernels and saying good/bad if wol worked/didn't
> work etc. it identified the following commit:
>
> # bad: [ac93a3946b676025fa55356180e8321639744b31] sky2: enable PCI
> config writes
>
> and refs/bisect/bad gives:
>
> 14:16:53 /usr/src/linux-2.6/.git # cat refs/bisect/bad
> ac93a3946b676025fa55356180e8321639744b31
>
>
> need some more info?
>
i just checked it: commented out the passage of the commit in kernel
2.6.24-rc7-git4 and compiled it: wol WORKS. so this one line is causing
my wol-disturbance...
but i noticed another "bug" on 2.6.24-rc7-git with sky2: dmesg shows a
lot of lines every 5 seconds:
[...]
[ 357.400462] sky2 0000:02:00.0: error interrupt status=0xc0000000
[ 362.442039] printk: 41 messages suppressed.
[ 362.442043] sky2 0000:02:00.0: error interrupt status=0x80000000
[ 367.439151] printk: 18 messages suppressed.
[ 367.439156] sky2 0000:02:00.0: error interrupt status=0x80000000
[ 372.436267] printk: 30 messages suppressed.
[ 372.436271] sky2 0000:02:00.0: error interrupt status=0x80000000
[ 377.350236] printk: 19 messages suppressed.
[...]
since i do not notice any errors (yet) i'll wait till next rc, maybe it
will be gone then...
but i'm happy wol works again on 2.6.24 :)
next prev parent reply other threads:[~2008-01-13 15:08 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-9721-10286@http.bugzilla.kernel.org/>
2008-01-10 0:03 ` [Bugme-new] [Bug 9721] New: wake on lan fails with sky2 module Andrew Morton
2008-01-10 4:52 ` Stephen Hemminger
2008-01-10 19:35 ` supersud501
2008-01-11 20:23 ` supersud501
2008-01-11 21:16 ` Rafael J. Wysocki
2008-01-11 22:19 ` supersud501
2008-01-11 23:10 ` Rafael J. Wysocki
2008-01-12 12:24 ` supersud501
2008-01-12 19:13 ` Rafael J. Wysocki
2008-01-13 13:22 ` supersud501
2008-01-13 15:08 ` supersud501 [this message]
2008-01-13 19:27 ` Andrew Morton
2008-01-13 20:27 ` supersud501
2008-01-13 20:57 ` Andrew Morton
2008-01-13 21:25 ` Rafael J. Wysocki
2008-01-13 21:27 ` Rafael J. Wysocki
2008-01-13 22:53 ` supersud501
2008-01-14 18:14 ` [RFT] sky2: wake-on-lan configuration issues Stephen Hemminger
2008-01-14 21:05 ` supersud501
2008-01-17 21:08 ` Tino Keitel
2008-01-17 23:22 ` Andrew Morton
2008-01-14 16:39 ` [Bugme-new] [Bug 9721] New: wake on lan fails with sky2 module Stephen Hemminger
2008-01-14 20:50 ` Andrew Morton
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=478A2976.9000204@yahoo.de \
--to=supersud501@yahoo.de \
--cc=akpm@linux-foundation.org \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rjw@sisk.pl \
--cc=shemminger@linux-foundation.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.