From: willy@thepuffingroup.com
To: Grant Grundler <grundler@cup.hp.com>
Cc: parisc-linux@thepuffingroup.com
Subject: Re: [parisc-linux] code 28 trap
Date: Thu, 24 Feb 2000 22:49:34 -0500 [thread overview]
Message-ID: <20000224224934.N9944@thepuffingroup.com> (raw)
In-Reply-To: <200002250259.SAA04374@milano.cup.hp.com>; from Grant Grundler on Thu, Feb 24, 2000 at 06:59:49PM -0800
On Thu, Feb 24, 2000 at 06:59:49PM -0800, Grant Grundler wrote:
>
> Hi folks,
> I'm getting a "Code 28" interrupt on my c3000.
> I've appended the full console output.
>
> IOAQ points to ip_rcv+156.
> GR02 points to net_bh+620
>
> 0xc01ca024 <ip_rcv+156>: ldw 0(sr0,r4),r25
>
> and GR4 == c7e8702e.
> GR4 is aligned on 2byte, not 4 byte which the ldw wants.
>
> I've reproduced the problem in another chunk of code:
> 0xc01fa82c <ic_bootp_recv+76>: ldw 0(sr0,r4),r25
>
> In this case: gr4 == c7f7e82e and gr2 == c01ce708 (net_bh+576)
Uh oh. We really need a kernel unaligned trap handler. Some of
the network protocols rely on that being handled right (yes, i know.
it sucks.) I was about to say `I really don't think this applies to
IP or BOOTP/IP', when I remembered...
http://boudicca.tux.org/hypermail/linux-kernel/2000week06/0092.html
There was a bug in 2.3.41, looks like it didn't get fixed in .42, that
caused things to get unaligned once in a while. Doh! Anyone want to
volunteer to write an unaligned trap handler...?
next prev parent reply other threads:[~2000-02-25 4:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-02-25 2:59 [parisc-linux] code 28 trap Grant Grundler
2000-02-25 3:49 ` willy [this message]
2000-02-25 20:36 ` Grant Grundler
2000-02-25 22:03 ` Philipp Rumpf
2000-03-03 21:53 ` Thomas Bogendoerfer
2000-02-25 23:17 ` Philipp Rumpf
-- strict thread matches above, loose matches on Subject: below --
2000-02-25 20:17 HOLBROOK,SCOTT (HP-FtCollins,ex1)
2000-02-25 20:23 HOLBROOK,SCOTT (HP-FtCollins,ex1)
2000-02-25 21:49 ` Philipp Rumpf
2000-02-25 20:42 Mike Hibler
2000-02-26 0:35 John Marvin
2000-02-26 0:53 ` Philipp Rumpf
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=20000224224934.N9944@thepuffingroup.com \
--to=willy@thepuffingroup.com \
--cc=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