From: Pierre JUHEN <pierre.juhen@wanadoo.fr>
To: Dan Dennedy <dan@dennedy.org>
Cc: linux-kernel@vger.kernel.org,
Andreas Bombe <andreas.bombe@munich.netsurf.de>,
"linux1394-devel@lists.sourceforge.net"
<linux1394-devel@lists.sourceforge.net>
Subject: Re: [pierre.juhen@wanadoo.fr: PROBLEM : OHCI1394 module crashes linux with 2.4.9 (and 2.4.8 ?)]
Date: Wed, 29 Aug 2001 23:33:52 +0200 [thread overview]
Message-ID: <3B8D5FC0.B2BB4FDD@wanadoo.fr> (raw)
In-Reply-To: <20010825031020.A30852@storm.local> <20010827225716.B5933@xtremedia>
I upgraded to gcc-2.96-85, which is supposed to be corrected. I
recompiled the kernel and modules.
It didn't solve the problem.
modprobe ohci-1394 still crashes the system
Thanks,
Regards,
Pierre
Dan Dennedy a écrit :
>
> On Fri, 24 Aug 2001 21:10:20 Andreas Bombe wrote:
> > This was sent to linux-kernel and me. See what you can make of it.
> >
> > ----- Forwarded message from Pierre JUHEN <pierre.juhen@wanadoo.fr> -----
> >
> > Subject: PROBLEM : OHCI1394 module crashes linux with 2.4.9 (and 2.4.8 ?)
> >
> > [4.] Linux version 2.4.9 (root@pierre.juhen) (gcc version 2.96 20000731
> > (Red Hat Linux 7.1 2.96-81)) #2 dim aoû 19 19:02:56 CEST 2001
> [..]
> > Gnu C 2.96
>
> Maybe the problem is gcc 2.96--the notorious redhat version.
>
> Try a google search on "gcc 2.96 -rpm" and see what it turns up.
>
> FWIW, for other users here, in Arne Schirmacher's DV forums, we also have
> reports from users that libdv compiled with gcc 2.96 is generating
> artifacts in their decoded images.
parent reply other threads:[~2001-08-29 21:28 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20010827225716.B5933@xtremedia>]
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=3B8D5FC0.B2BB4FDD@wanadoo.fr \
--to=pierre.juhen@wanadoo.fr \
--cc=andreas.bombe@munich.netsurf.de \
--cc=dan@dennedy.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux1394-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 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).