From: Richard Hirst <rhirst@linuxcare.com>
To: CHS <chs@23.org>
Cc: parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] New list member..
Date: Wed, 13 Jun 2001 14:34:42 +0100 [thread overview]
Message-ID: <20010613143442.K16532@linuxcare.com> (raw)
In-Reply-To: <Pine.LNX.4.30.0106121514010.23761-100000@methlab.23.org>; from chs@23.org on Tue, Jun 12, 2001 at 03:19:46PM -0700
On Tue, Jun 12, 2001 at 03:19:46PM -0700, CHS wrote:
>
> Hello all. Just wanted to say hello. I've been working with linux for
> about 7 years now, mainly with the slackware and redhat distributions.
> This weekend I picked up a 712/80 for free, and after getting a CDROM
> drive working on it (long story), managed to go through the single easiest
> linux install in my entire life. Keep in mind I've never even touched an
> HP PA-RISC machine until this weekend. So a big hearty kudos to you guys!
> I had a couple questions though:
>
> 1.) The machine seems to work generally pretty OK, except that I get
> kernel panics fairly often. This did not hinder the install at all though.
> any ideas?
You don't say if you are serial or graphical (sti) console based.
I certainly wouldn't expect kernel panics "fairly often" with a
serial console. For sti console, there are some known issues, for
example, hitting <escape> in vi tends to crash the kernel. sti console
is much less tested than serial also. The vi problem is fixed in our
latest kernel source, and you can work round it by changing your terminal
type (from TERM=linux to TERM=vt100, iirc).
If you are sti console based then it is painful, but if you could copy
down the register dump (not the stack dump, most of which will have
scrolled off the screen), then I might be able to tell you more.
If you are serial based, you should be able to capture the output
easily enough.
Richard
next prev parent reply other threads:[~2001-06-13 13:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-12 22:19 [parisc-linux] New list member CHS
2001-06-13 0:42 ` Stan Sieler
2001-06-12 23:47 ` CHS
2001-06-13 13:34 ` Richard Hirst [this message]
2001-06-13 18:27 ` CHS
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=20010613143442.K16532@linuxcare.com \
--to=rhirst@linuxcare.com \
--cc=chs@23.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox