From: DaMouse Networks <damouse@ntlworld.com>
To: Francois Romieu <romieu@fr.zoreil.com>
Cc: netdev@oss.sgi.com
Subject: Re: [BUG] 2.6.1-rc1-mm1 with r8169 driver
Date: Sun, 11 Jan 2004 13:59:00 +0000 [thread overview]
Message-ID: <20040111135900.1acb95b3@EozVul.WORKGROUP> (raw)
In-Reply-To: <20040111141806.A19535@electric-eye.fr.zoreil.com>
[-- Attachment #1: Type: text/plain, Size: 1192 bytes --]
Same results for non-SMP kernel (kpanic after a few minutes of surfing and also when i ran ping -f).
Stock 2.6.1 runs fine with my 7000 (ping -f) packets to the router :).
debug-stuff for 2.6.1-r8169 (2.6.1+the r8169 that we've applied so far) is attached.
-DaMouse
On Sun, 11 Jan 2004 14:18:06 +0100
Francois Romieu <romieu@fr.zoreil.com> wrote:
> DaMouse Networks <damouse@ntlworld.com> :
> > Ok, looks like my additional testing with ping -f is bringing out the bugs
> > in this baby, once I'd got past the r8169-rx-fill-typo.patch it borked on
> > "ping -f" with the kpanic I pictured last time. Looks like I shoulda tested
> > that also last time :/. I have attached the files you requested any other
> > stuff you need just ask :)
>
> Fine. I'll dig it this evening.
>
> (/me gives a quick sight...)
>
> Hmmm... acpi + HT smp.
>
> Can you (no more request until I cook something, no joke :o) ):
> - check that plain 2.6.1 driver does not panic under 'ping -f' ?
> - compile a non SMP enabled kernel and see if patched r8169 is stable
> - during normal traffic
> - during 'ping -f'
>
> Please Cc: netdev@oss.sgi.com and include the relevant 'dmesg' output.
>
> --
> Ueimor
[-- Attachment #2: debug.tar.bz2 --]
[-- Type: application/octet-stream, Size: 6523 bytes --]
parent reply other threads:[~2004-01-11 13:59 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20040111141806.A19535@electric-eye.fr.zoreil.com>]
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=20040111135900.1acb95b3@EozVul.WORKGROUP \
--to=damouse@ntlworld.com \
--cc=netdev@oss.sgi.com \
--cc=romieu@fr.zoreil.com \
/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