Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Grant Grundler <grundler@cup.hp.com>
To: parisc-linux@thepuffingroup.com
Subject: [parisc-linux] sh segfaults
Date: Thu, 25 Jan 2001 22:15:27 -0800 (PST)	[thread overview]
Message-ID: <200101260615.WAA23253@milano.cup.hp.com> (raw)


Hi all,
So despite booting our shiny new 2.4.0 kernel fine and being able to rcp
the sources to attempt a native build, "make oldconfig" consistently
sees a segfault:

c3k:/usr/src/linux \<535\>make oldconfig > /dev/null

do_page_fault() pid=561 command='sh' type=15 address=0x000006e4

     YZrvWESTHLNXBCVMcbcbcbcbOGFRQPDI
PSW: 00000000000001001111111100001011
r0-3     00000000 00000368 000327a3 bb002490
r4-7     4001399b 00000000 401cf630 401d2fbc
r8-11    00076d74 00000000 bb002490 000c3110
r12-15   ffffffff 00000000 00000000 00000001
r16-19   0000005c 00000000 00000000 401d2fbc
r20-23   fffff000 400eb63c 0007e498 00000008
r24-27   00000000 bb002908 00000002 00076808
r28-31   0000023a 0000002f bb002880 400eb663
sr0-3    00000368 00000368 00000000 00000368
sr4-7    00000368 00000368 00000368 00000368

IASQ: 00000368 00000368 IAOQ: 000327a3 000327a7
 IIR: 483306f8    ISR: 00000368  IOR: 000006e4
ORIG_R28: 00000001
make: *** [oldconfig] Segmentation fault
c3k:/usr/src/linux \<536\>


And redirecting output to /dev/null doesn't always work either.
Sometimes I just get back an error msg.
This wasn't happening with the previous kernels.

This is unfortunately on the same proto-c3k that couldn't run hwclock.sh
at boot up before though that worked fine on my c3k at work. So it
might just be the machine. If others could verify...

thanks,
grant

             reply	other threads:[~2001-01-26  6:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-26  6:15 Grant Grundler [this message]
2001-01-26 13:46 ` [parisc-linux] sh segfaults Richard Hirst

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=200101260615.WAA23253@milano.cup.hp.com \
    --to=grundler@cup.hp.com \
    --cc=parisc-linux@thepuffingroup.com \
    /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