From: Grant Grundler <grundler@parisc-linux.org>
To: John David Anglin <dave@hiauly1.hia.nrc.ca>
Cc: Carlos O'Donell <carlos@systemhalted.org>,
deller@gmx.de, linux-parisc@vger.kernel.org
Subject: Re: 2.6.28-rcX in pretty bad shape on parisc
Date: Mon, 8 Dec 2008 00:50:01 -0700 [thread overview]
Message-ID: <20081208075001.GB28779@colo.lackof.org> (raw)
In-Reply-To: <20081208045003.4CF644E99@hiauly1.hia.nrc.ca>
On Sun, Dec 07, 2008 at 11:50:02PM -0500, John David Anglin wrote:
> > Given your earlier comments it would seen the segfault is not
> > reproducible and happens often and randomly?
>
> I gave 2.6.28-rc7-git5 a try this evening. Hit the same error.
> While its occurence may be random, the identical fault occurred
> multiple times in a short period of testing.
I routinely get a segfault the first time I attempt to compile linux-2.6
kernel after reboot. If I "find linux-2.6 | xargs cksum", the kernel
builds fine.
> I see this bit of code in _dl_fixup:
>
> 0x401ed464 <_dl_fixup+172>: mfctl tr3,r21
> 0x401ed468 <_dl_fixup+176>: ldw -3e0(r21),ret0
> 0x401ed46c <_dl_fixup+180>: cmpib,<> 0,ret0,0x401ed628 <_dl_fixup+624>
>
> and
>
> 0x401ed5fc <_dl_fixup+580>: ldi 1,r24
> 0x401ed600 <_dl_fixup+584>: ldi 0,r23
> 0x401ed604 <_dl_fixup+588>: mfctl tr3,r26
> 0x401ed608 <_dl_fixup+592>: copy r24,r25
> 0x401ed60c <_dl_fixup+596>: ldo -3dc(r26),r26
> 0x401ed610 <_dl_fixup+600>: copy r19,r4
> 0x401ed614 <_dl_fixup+604>: be,l 100(sr2,r0),sr0,r31
> 0x401ed618 <_dl_fixup+608>: ldi d2,r20
>
> So, the code is using the thread register (cr27). Not sure what syscall
> this is. However, the problem might be TLS releated.
I have no idea if TLS makes a difference to kernel builds.
thanks,
grant
next prev parent reply other threads:[~2008-12-08 7:50 UTC|newest]
Thread overview: 63+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-18 20:04 2.6.28-rcX in pretty bad shape on parisc Helge Deller
2008-11-19 1:33 ` Thibaut VARENE
2008-11-19 15:47 ` Helge Deller
2008-11-19 2:31 ` James Bottomley
2008-11-19 9:13 ` Domenico Andreoli
2008-11-19 14:20 ` James Bottomley
2008-11-19 15:12 ` John David Anglin
2008-11-19 16:25 ` Helge Deller
2008-11-19 18:13 ` Helge Deller
2008-11-20 7:55 ` Helge Deller
2008-11-20 12:57 ` Thibaut VARENE
2008-11-20 15:14 ` John David Anglin
2008-11-20 3:51 ` John David Anglin
2008-11-20 16:57 ` John David Anglin
2008-11-22 5:57 ` Grant Grundler
2008-11-22 6:14 ` Grant Grundler
2008-11-22 19:48 ` John David Anglin
2008-11-22 21:37 ` John David Anglin
2008-11-22 23:01 ` James Bottomley
2008-11-23 16:54 ` John David Anglin
2008-11-22 6:11 ` Grant Grundler
2008-11-23 7:13 ` Grant Grundler
2008-11-23 16:36 ` John David Anglin
2008-11-23 16:57 ` John David Anglin
2008-11-25 2:54 ` John David Anglin
2008-11-25 13:33 ` Carlos O'Donell
2008-11-25 13:58 ` Guy Martin
2008-11-25 14:07 ` Carlos O'Donell
2008-11-26 17:51 ` Guy Martin
2008-11-30 20:24 ` John David Anglin
2008-11-30 21:03 ` Helge Deller
2008-12-02 0:00 ` John David Anglin
2008-12-01 10:54 ` Thibaut VARENE
2008-12-03 20:41 ` Helge Deller
2008-12-08 5:15 ` Kyle McMartin
2008-12-08 15:23 ` John David Anglin
2008-12-08 15:34 ` Kyle McMartin
2008-12-08 15:57 ` John David Anglin
2008-12-08 16:00 ` Kyle McMartin
2008-12-08 16:00 ` Kyle McMartin
2008-12-09 3:44 ` resource_size_t printk woes Kyle McMartin
2008-12-10 4:05 ` John David Anglin
2009-01-01 13:06 ` Helge Deller
2009-01-01 17:14 ` John David Anglin
2009-01-01 17:32 ` Helge Deller
2009-01-01 19:04 ` John David Anglin
2009-01-01 22:37 ` John David Anglin
2009-01-01 23:39 ` John David Anglin
2009-01-02 9:14 ` Helge Deller
2009-01-02 16:32 ` John David Anglin
2009-01-02 16:43 ` John David Anglin
2009-01-02 19:50 ` Grant Grundler
2008-12-08 4:50 ` 2.6.28-rcX in pretty bad shape on parisc John David Anglin
2008-12-08 7:50 ` Grant Grundler [this message]
2008-12-08 15:16 ` John David Anglin
2008-12-09 4:14 ` Kyle McMartin
2008-12-08 12:39 ` Carlos O'Donell
2008-12-08 14:54 ` John David Anglin
2008-12-08 15:02 ` Carlos O'Donell
2008-12-08 15:30 ` John David Anglin
2008-12-08 22:14 ` Carlos O'Donell
2008-12-08 22:39 ` John David Anglin
2008-12-09 0:01 ` Carlos O'Donell
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=20081208075001.GB28779@colo.lackof.org \
--to=grundler@parisc-linux.org \
--cc=carlos@systemhalted.org \
--cc=dave@hiauly1.hia.nrc.ca \
--cc=deller@gmx.de \
--cc=linux-parisc@vger.kernel.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.