All of lore.kernel.org
 help / color / mirror / Atom feed
From: Carlos O'Donell <carlos@baldric.uwo.ca>
To: "Bjoern A. Zeeb" <bzeeb-lists@lists.zabbadoz.net>
Cc: parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] [2.5] next issues ...
Date: Fri, 15 Nov 2002 12:50:32 -0500	[thread overview]
Message-ID: <20021115175032.GD5673@systemhalted> (raw)
In-Reply-To: <Pine.BSF.4.44.0211151707330.39295-100000@e0-0.zab2.int.zabbadoz.net>

> Hi,
> 
> 2.5.47-pa3 up and running I added my vlan interface, ssh'ed to the
> host and *buff*
> 

I noticed that your 'uname -a' says you compiled the kernel with gcc-3.2.
AFAIK we have yet to build a kernel with gcc-3.2 that survives network 
traffic. Perhaps try building the kernel with gcc 3.1 or 3.0? 

Helping track down the gcc-3.2 problem would be a wonderful thing :)

c.

  reply	other threads:[~2002-11-15 17:50 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-15 17:12 [parisc-linux] [2.5] next issues Bjoern A. Zeeb
2002-11-15 17:50 ` Carlos O'Donell [this message]
2002-11-15 19:10   ` John David Anglin
2002-11-15 19:21     ` Randolph Chung
2002-11-15 20:50       ` Carlos O'Donell
2002-11-18 13:34         ` jsoe0708
2002-11-15 22:17     ` Bjoern A. Zeeb
2002-11-15 22:45       ` John David Anglin
2002-11-15 23:29         ` Randolph Chung
2002-11-16  0:37           ` John David Anglin
2002-11-17  2:32             ` M. Grabert
2002-11-17 13:16         ` Bjoern A. Zeeb
2002-11-17 21:14           ` John David Anglin
2002-11-17 17:34     ` Bjoern A. Zeeb
2002-11-17 20:48       ` John David Anglin
2002-11-17 21:13         ` Bjoern A. Zeeb
2002-11-17 21:26           ` John David Anglin
2002-11-18 21:38             ` Bjoern A. Zeeb
2002-11-18 21:52               ` John David Anglin
2002-11-18 22:15                 ` Bjoern A. Zeeb
2002-11-18 22:21                   ` John David Anglin

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=20021115175032.GD5673@systemhalted \
    --to=carlos@baldric.uwo.ca \
    --cc=bzeeb-lists@lists.zabbadoz.net \
    --cc=parisc-linux@lists.parisc-linux.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.