From: Grant Grundler <grundler@dsl2.external.hp.com>
To: DJ Tha Muggs <djmuggs@mail.cvee.org>
Cc: parisc-linux@parisc-linux.org
Subject: Re: [parisc-linux] IDE Harddisks in a C3K
Date: Sun, 31 Mar 2002 21:32:53 -0700 [thread overview]
Message-ID: <20020401043253.6579C484E@dsl2.external.hp.com> (raw)
In-Reply-To: Message from DJ Tha Muggs <djmuggs@mail.cvee.org> of "Sun, 31 Mar 2002 14:48:48 +0200." <20020331124848.GA291@cvee.org>
DJ Tha Muggs wrote:
> Anyone experienced with using IDE hdd's in a C3K?
Not me. I've only used the CD-ROM drive.
Note that suckyio got it's nick name for a reason.
I'm not sure I'd trust R/W data behind that interface.
Maybe if I could beat on it for a few days without errors,
I might change my mind. But I've got no incentive to do so.
> Are IDE badly supported or no one realy tried it yet?
probably both.
> <stack dump>
> WARNING! Stack pointer and cr30 do not correspond!
This msg probably means a driver referenced a user space
pointer without copy_from_user() or changing the "DS".
...
> Dumping virtual address stack instead
>
> Dumping Stack from 0x2a858000 to 0x2a8586c0:
*sigh*. I'm looking forward to stack unwinds under kdb.
...
> Kernel Fault: Code=26 regs=1a8586c0 (Addr=00000007)
variant of a data page fault.
>
> YZrvWESTHLNXBCVMcbcbcbcbOGFRQPDI
> PSW: 00000000000001101111111100001111 Not tainted
> r00-03 00000000 1031f810 1012ddc8 ffffffff
Return Pointer of most recent subroutine call.
> r20-23 0000009f 00000044 00000131 2ff00000
> r24-27 ffffffff 00000001 263ff120 10304010
Args are in r26, r25, ...
> IASQ: 00000000 00000000 IAOQ: 1012ae24 1012ae28
1012ae24 is address of faulting instruction.
Start here.
grant
prev parent reply other threads:[~2002-04-01 4:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-31 12:48 [parisc-linux] IDE Harddisks in a C3K DJ Tha Muggs
2002-04-01 4:32 ` Grant Grundler [this message]
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=20020401043253.6579C484E@dsl2.external.hp.com \
--to=grundler@dsl2.external.hp.com \
--cc=djmuggs@mail.cvee.org \
--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