From: "Tvrtko A. Uršulin" <tvrtko@croadria.com>
To: xen-devel@lists.sourceforge.net
Cc: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
Subject: Re: Network interface problem
Date: Wed, 11 Feb 2004 12:46:24 +0100 [thread overview]
Message-ID: <200402111246.24382.tvrtko@croadria.com> (raw)
In-Reply-To: <E1Aqs73-0006gq-00@wisbech.cl.cam.ac.uk>
On Wednesday 11 February 2004 12:01, Keir Fraser wrote:
> In fact I will need the _full_ boot-time output both from Xen and from
> normal vanilla Linux 2.4.24 (not a vendor kernel!).
>
> Even if this weren't the case, I've quickly learned never to trust a
> bug report until I've personally eyeballed it. ;-)
That is a smart policy. I am sorry I tried to convince you to trust me. :) It
seems that tg3 issue really isn't related to Xen. It really doesn't work
under vanilla 2.4.24 with:
tg3.c:v2.3 (November 5, 2003)
tg3: Could not obtain valid ethernet address, aborting.
While under 2.4.24-grsec it does:
tg3.c:v2.3 (November 5, 2003)
eth0: Tigon3 [partno(BCM95702A20) rev 1002 PHY(5703)] (PCI:33MHz:32-bit)
10/100/1000BaseT Ethernet 00:08:02:f7:c1:fa
tg3: eth0: Link is up at 100 Mbps, full duplex.
tg3: eth0: Flow control is off for TX and off for RX.
That is really strange and I will post it to LKML and grsec MLs. Complete
kernel logs differ only in kernel memory usage and cpu speed calculation.
So it seems that I have never tried 2.4.24 vanilla before, only thought that I
did. :)
-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
next prev parent reply other threads:[~2004-02-11 11:46 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-11 10:05 Network interface problem Tvrtko A. Uršulin
2004-02-11 10:13 ` Rolf Neugebauer
2004-02-11 10:15 ` Keir Fraser
2004-02-11 10:34 ` Tvrtko A. Uršulin
2004-02-11 10:43 ` Keir Fraser
2004-02-11 10:59 ` Tvrtko A. Uršulin
2004-02-11 11:01 ` Keir Fraser
2004-02-11 11:46 ` Tvrtko A. Uršulin [this message]
2004-02-11 11:57 ` Keir Fraser
2004-02-11 12:14 ` Tvrtko A. Uršulin
2004-02-11 12:25 ` Ian Pratt
2004-02-11 12:40 ` Ian Pratt
2004-02-11 12:53 ` Tvrtko A. Uršulin
2004-02-11 13:40 ` Keir Fraser
2004-02-11 13:54 ` Keir Fraser
2004-02-17 5:32 ` stevegt
2004-02-17 7:44 ` Keir Fraser
2004-02-11 13:56 ` Tvrtko A. Uršulin
2004-02-11 13:57 ` Keir Fraser
2004-02-11 10:51 ` Rolf Neugebauer
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=200402111246.24382.tvrtko@croadria.com \
--to=tvrtko@croadria.com \
--cc=Keir.Fraser@cl.cam.ac.uk \
--cc=xen-devel@lists.sourceforge.net \
/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.