From: joel.soete@freebel.net
To: parisc-linux@parisc-linux.org
Cc: John David Anglin <dave@hiauly1.hia.nrc.ca>,
INVALID_ADDRESS@.SYNTAX-ERROR
Subject: Re: [parisc-linux] gcc-cvs problem
Date: Tue, 04 Jun 2002 18:52:44 +0200 (CEST) [thread overview]
Message-ID: <1023209564.3cfcf05ce80e8@webmail.tiscalinet.be> (raw)
In-Reply-To: <1023172365.3cfc5f0d1b7f7@webmail.tiscalinet.be>
I not yet quiet sure that is not an hardware problem but I reboot on the kernel
2.4.18-pa29 and an hpmc occurs after an some minutes without doing anything else
then let it run for itself?
Then I reboot on hpux (10.20), unfortunately no problem occurs during the 4
hours it runs.
So now I reboot in su mode to move back ext3 to ext2 my all fs.
Then reboot in mu. It works and it is on going to recompile toolchain but it is
now so slow (even badly then a 712/80).
Is there other thing to do than backup, re-mkfs, restore to recover some
performance?
Thanks in advance for advice,
Joel
Quoting joel.soete@freebel.net:
> Quoting John David Anglin <dave@hiauly1.hia.nrc.ca>:
>
> > > I really have no chance with this b2000:
> > > I broken first my install and now it makes a HPMC in the middle of
> > binutils
> > > build and the pim info are not clear :((
> >
> > I'd try a new kernel first.
>
> Very strange behaviour:
> with some difficulties I reach to restart a kernel then I launch my
> toolchain
> script (which failled because of __therad problem), I change the faulty
> header
> and finaly relaunch script which failled in a tar xjf (some time during
> the
> first extract of binutils, some time during the second extract of gcc32)
> what
> ever the kernel I used 2.4.18-pa24 2.4.18-pa24+lvm1.0.4
> 2.4.19-pre8-pa29?.
>
> But thanks to the console logs grab with minicom I reach to notice the
> "BUG":
>
> Debian GNU/Linux 3.0 palx2000 ttyS0
>
> palx2000 login:
>
> kernel BUG at superio.c:109!
> WARNING! Stack pointer and cr30 do not correspond!
> Dumping virtual address stack instead
>
> Dumping Stack from 0x2ee00000 to 0x2ee00bc0:
> ...
>
> What could the reason why the tar xjf is successfull a first time and
> when it is
> relaunched, it fails? Ext3 fs (I am not sure how can I change back to
> ext2) bash
> (which other sh may I try) ?
>
>
> Joel
>
> PS: after a cleanpim it seems to be easiest to reboot?
>
> -------------------------------------------------
> This mail sent through Tiscali Webmail (http://webmail.tiscali.be)
>
> _______________________________________________
> parisc-linux mailing list
> parisc-linux@lists.parisc-linux.org
> http://lists.parisc-linux.org/mailman/listinfo/parisc-linux
>
>
-------------------------------------------------
This mail sent through Tiscali Webmail (http://webmail.tiscali.be)
next prev parent reply other threads:[~2002-06-04 16:52 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-30 17:22 [parisc-linux] gcc-cvs problem joel.soete
2002-05-30 17:51 ` John David Anglin
2002-05-31 15:14 ` joel.soete
2002-05-31 17:15 ` John David Anglin
2002-06-01 19:11 ` Joel Soete
2002-06-02 0:45 ` John David Anglin
2002-06-03 15:47 ` joel.soete
2002-06-03 14:58 ` joel.soete
2002-06-03 15:12 ` John David Anglin
2002-06-03 17:09 ` joel.soete
2002-06-03 17:38 ` John David Anglin
2002-06-04 6:32 ` joel.soete
2002-06-04 16:52 ` joel.soete [this message]
2002-06-05 16:11 ` joel.soete
2002-06-05 17:17 ` joel.soete
2002-06-05 17:34 ` 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=1023209564.3cfcf05ce80e8@webmail.tiscalinet.be \
--to=joel.soete@freebel.net \
--cc=dave@hiauly1.hia.nrc.ca \
--cc=parisc-linux@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox