All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joel Soete <joel.soete@freebel.net>
To: Bruno Vidal <bruno_vidal@hpfrcu03.france.hp.com>
Cc: parisc-linux@lists.parisc-linux.org
Subject: [Fwd: Re: [parisc-linux] PA8000 modutils problems]
Date: Sun, 23 Jun 2002 12:09:57 +0000	[thread overview]
Message-ID: <3D15BA95.7070101@freebel.net> (raw)

Hi Bruno,

Till some month ago I encounter a problem when I compile the kernel with 
gcc-3.2 or gcc-3.1. Those kernels boot well but as soon as you try a 
network connection (telnet or ssh) the system crash.

It is a problem in network kernel part but dono yet if it is IP stack or 
  interface problem.

As some month ago could you send me your last lkcd code so that I could 
try to locate the problem with at least gdb?

Thanks in advance for your help,
	Joel

 > Dave,
 >
 > The problem mentionned in this mail:
 > 
http://lists.parisc-linux.org/pipermail/parisc-linux/2002-April/016119.html
 >
 > about gcc-3.2 is the same with gcc-3.1.
 >
 > Dono about some follow-up?
 >
 > Thanks for advise,
 > 	Joel
 >
 > PS:
 > What means PR (how to fil it)?
 > And what means insn?
 >
 > John David Anglin wrote:
 > >>Some weeks ago I also try to compile the kernel (32bits) with gcc-3.1
 > >>(cvs) and eventhought it boots fine there was a problem
 > >>with network connections (as well telnet which uses inetd as well 
as ssh
 > >>which using its own sshd; this confirm the problem of compilation in
 > >>network interface). Is this problem solved now?
 > >
 > >
 > > Not that I am aware of.  Maybe some of the debian folks have tried 
looking
 > > into it as they were talking about moving to a newer compiler 
release.
 > > If it is a compiler problem, I would need a test case showing the
 > > miscompilation and preferably a filed PR.
 > >
 > > Dave

                 reply	other threads:[~2002-06-23 12:08 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=3D15BA95.7070101@freebel.net \
    --to=joel.soete@freebel.net \
    --cc=bruno_vidal@hpfrcu03.france.hp.com \
    --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.