From: Jarek Poplawski <jarkao2@o2.pl>
To: Jon Nelson <jnelson@jamponi.net>
Cc: netdev@vger.kernel.org, bugme-daemon@bugzilla.kernel.org,
mchan@broadcom.com, Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [Bugme-new] [Bug 9391] New: Netgear GA320T(tg3) strange errors and non-workingness
Date: Fri, 16 Nov 2007 09:30:07 +0100 [thread overview]
Message-ID: <20071116083007.GA2124@ff.dom.local> (raw)
In-Reply-To: <20071115181809.592a110c.akpm@linux-foundation.org>
On 16-11-2007 03:18, Andrew Morton wrote:
> On Thu, 15 Nov 2007 18:04:19 -0800 (PST) bugme-daemon@bugzilla.kernel.org wrote:
>
>> http://bugzilla.kernel.org/show_bug.cgi?id=9391
>>
>> Summary: Netgear GA320T(tg3) strange errors and non-workingness
>> Product: Drivers
>> Version: 2.5
>> KernelVersion: 2.6.22.12 (openSUSE 10.3)
...
I see we have a new thread for this...
Jon, maybe it's only me, but this really looks strange. I don't know
this board, but probably these interrupts shouldn't look like this.
It seems there is a problem with detecting your apic. I'm not sure
if this is a default SUSE kernel, but maybe it would be better to
try some current live-cd distro with good hardware detection. tg3
card & driver seem to have quite good opinions, especially if msi
interrupts could be used.
Btw., these logs (dmesg, lspci) could be much longer... (Somebody
might even think you have something to hide; it would be better to
mask only personal data then.)
Cheers,
Jarek P.
next prev parent reply other threads:[~2007-11-16 8:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-9391-10286@http.bugzilla.kernel.org/>
2007-11-16 2:18 ` [Bugme-new] [Bug 9391] New: Netgear GA320T(tg3) strange errors and non-workingness Andrew Morton
2007-11-16 8:30 ` Jarek Poplawski [this message]
2007-11-16 14:08 ` Jon Nelson
2007-11-16 16:55 ` Michael Chan
2007-11-16 19: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=20071116083007.GA2124@ff.dom.local \
--to=jarkao2@o2.pl \
--cc=akpm@linux-foundation.org \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=jnelson@jamponi.net \
--cc=mchan@broadcom.com \
--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).