From: Carlos O'Donell <carlos@systemhalted.org>
To: John David Anglin <dave@hiauly1.hia.nrc.ca>
Cc: parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] Why gas kills the hppa-linux kernel and what you can
Date: Thu, 30 Jun 2005 15:17:43 -0400 [thread overview]
Message-ID: <20050630191743.GN5269@systemhalted.org> (raw)
In-Reply-To: <200506301907.j5UJ7UAx029747@hiauly1.hia.nrc.ca>
On Thu, Jun 30, 2005 at 03:07:30PM -0400, John David Anglin wrote:
> > IAOQ[0]: memset+0x24/0xac
> > IAOQ[1]: memset+0x28/0xac
>
> It looks like memset has been passed a bad address.
>
Who passed the bad page?
I see this from the userspace/kernel side:
as-new D 10109D08 0 1065 748 (NOTLB)
Backtrace:
[<10100eac>] schedule+0x4a0/0x6f8
[<10101b10>] io_schedule+0x3c/0x68
[<101404d8>] sync_page+0x40/0x68
[<10102078>] __wait_on_bit_lock+0xdc/0xf0
[<101410a4>] __lock_page+0x98/0xa4
[<101532fc>] do_swap_page+0x36c/0x400
[<10153c94>] handle_mm_fault+0x120/0x204
[<10103558>] do_page_fault+0x214/0x2a4
[<10104fd4>] handle_interruption+0x2bc/0x5e8
[<1010a088>] intr_check_sig+0x0/0xc
[<1014c388>] __pagevec_lru_add_active+0xfc/0x144
[<10129e98>] tasklet_action+0x70/0xe0
[<10162fd4>] dentry_open+0x120/0x1c0
[<10162fd4>] dentry_open+0x120/0x1c0
[<10162fd4>] dentry_open+0x120/0x1c0
[<10162fd4>] dentry_open+0x120/0x1c0
Clearly as-new is toast and swapping the system like made.
c.
_______________________________________________
parisc-linux mailing list
parisc-linux@lists.parisc-linux.org
http://lists.parisc-linux.org/mailman/listinfo/parisc-linux
prev parent reply other threads:[~2005-06-30 19:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-30 18:36 [parisc-linux] Why gas kills the hppa-linux kernel and what you can do about it Carlos O'Donell
2005-06-30 18:41 ` Carlos O'Donell
2005-06-30 19:07 ` [parisc-linux] Why gas kills the hppa-linux kernel and what you can John David Anglin
2005-06-30 19:17 ` Carlos O'Donell [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=20050630191743.GN5269@systemhalted.org \
--to=carlos@systemhalted.org \
--cc=dave@hiauly1.hia.nrc.ca \
--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