From: Sid Boyce <g3vbv@blueyonder.co.uk>
To: Len Brown <lenb@kernel.org>
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
linux-acpi@vger.kernel.org
Subject: Re: 2.6.19 and up to 2.6.20-rc2 Ethernet problems x86_64
Date: Fri, 05 Jan 2007 09:09:53 +0000 [thread overview]
Message-ID: <459E15E1.3010708@blueyonder.co.uk> (raw)
In-Reply-To: <200701030117.31737.lenb@kernel.org>
Len Brown wrote:
>> ..same problem with 2.6.20-rc3. Last worked with
>> 2.6.19-rc6-git12, so it was 2.6.19 where it failed.
>>
>
>
>
>> Attaching both case1 normal, case2 acpi=noirq. With acpi=noirq ethernet
>> doesn't get configured, route -n says it's an Unsupported operation,
>> ifconfig only shows for localhost, ifconfig eth0 192.168.10.5 also
>> complains of a config error.
>>
>
> It seems that the "acpi=noirq" (and probably also the acpi=off) case
> is simply an additional broken case, not a success case to compare to.
>
> The thing we really want to compare is dmesg and /proc/interrupts
> from 2.6.19-rc6-git12, and the broken current release.
> Perhaps you can put that info in the bug report when you file it.
>
> thanks,
> -Len
>
>
>
>
2.6.19-rc6-git12 fails in exactly the same way, from /var/log/messages
it seems 2.6.19-rc6 19/11/06 first saw the problem, details later when I
boot 2.6.19-rc5.
If I boot an affected kernel with the SuSEfirewall2 enabled and then
stop the firewall, the problems goes away.
Regards
Sid.
--
Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot
Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Specialist, Cricket Coach
Microsoft Windows Free Zone - Linux used for all Computing Tasks
next prev parent reply other threads:[~2007-01-05 9:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-02 15:41 2.6.19 and up to 2.6.20-rc2 Ethernet problems x86_64 Sid Boyce
2007-01-02 16:59 ` Len Brown
2007-01-02 22:57 ` Sid Boyce
2007-01-03 6:17 ` Len Brown
2007-01-05 9:09 ` Sid Boyce [this message]
[not found] <20061229063254.GA1628@ff.dom.local>
[not found] ` <4595CD1B.2020102@blueyonder.co.uk>
[not found] ` <20070102115050.GA3449@ff.dom.local>
[not found] ` <459A7AF1.5060702@blueyonder.co.uk>
2007-01-03 10:48 ` Jarek Poplawski
2007-01-03 16:53 ` Sid Boyce
2007-01-04 11:46 ` Jarek Poplawski
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=459E15E1.3010708@blueyonder.co.uk \
--to=g3vbv@blueyonder.co.uk \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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 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).