All of lore.kernel.org
 help / color / mirror / Atom feed
From: Scott Parish <srparish@us.ibm.com>
To: Gerd Knorr <kraxel@bytesex.org>
Cc: xen-devel@lists.xensource.com, Scott Parish <srparish@us.ibm.com>
Subject: Re: Re: [patch] convert page-l3.h macros to inlines
Date: Fri, 13 May 2005 17:48:02 +0000	[thread overview]
Message-ID: <20050513174802.GG27910@us.ibm.com> (raw)
In-Reply-To: <20050513162544.GA13042@bytesex>

On Fri, May 13, 2005 at 06:25:44PM +0200, Gerd Knorr wrote:

> > preempt off didn't help either.
> 
> Seems to be the same very place.  Adding current->comm to the
> printk next to the BUG() should show which process this is,
> probably it is the same every time which triggers some bug.
> If so, can you place the binary somewhere?
>
> The system looks like Debian, correct?
>
> Any difference when you move away /lib/tls (probably not, but
> who knows ...) ?
>
> Sticking some debug printk into mm_walk which triggers depending
> on current->comm might help to see what is going on.

I'm getting to a prompt now, although the system is still _very_ flaky
and crashes (same basic trace: mm_walk..)

/lib/tls didn't seem to have any effect when it was crashing during
boot, and it still doesn't seem to have any effect now that its
finishing boot.

somewhere along the lines i told debian to update itself, and this
might have been what got me to a prompt. (fwiw i'm running debian sid)

current->comm might have showed more consistancy earlier, but now its
as random as when i crash (which i haven't been able to consistantly
reproduce or consistantly avoid reproducing). i've seen stuff like
"sshd" "bash" "rcX" so far.

the rest of this data is stuff i collected before moving to your 7th
patch release. i can reproduce it if needed, but it was kind of tedious
and nothing appears to have changed about the details of the crash..

+ the crash is always the last mm_walk_set_prot() in mm_walk(), that is
the one for ptes.

+ the crash is always when pte == 0x15555000 (where pte is type 'pte_t *')

+ the pmd (pmd_t *) always has the lowest bits of 0xd60

+ the pte == 0x15555000 will appear in the middle of a seemingly fine
  pmd. by "continue"ing if pte == 0x15555000, i found there's a cluster
  of them:

...
mw pmd: 0xcf49fd50 pte: 0xc007d000
mw pmd: 0xcf49fd58 pte: 0xc007c000
mw pmd: 0xcf49fd60 pte: 0x15555000
mw pmd: 0xcf49fd68 pte: 0x15555000
mw pmd: 0xcf49fda0 pte: 0x15555000
...
mw pmd: 0xcf49ff48 pte: 0x15555000
mw pmd: 0xcf49ff50 pte: 0x15555000
mw pmd: 0xcf49ff58 pte: 0x15555000
mw pmd: 0xcf49ff60 pte: 0xcf4a0000
mw pmd: 0xcf49ff68 pte: 0xcf4a1000
mw pmd: 0xcf49ff70 pte: 0xcf4b2000
mw pmd: 0xcf49ff78 pte: 0xcf49f000
mw pmd: 0xcf49ff80 pte: 0x15555000
mw pmd: 0xcf49ff88 pte: 0x15555000
mw pmd: 0xcf49ff90 pte: 0x15555000
mw pmd: 0xcf49ff98 pte: 0x15555000
mw pmd: 0xcf49ffa0 pte: 0xbffff000
mw pmd: 0xcf49ffa8 pte: 0x15555000
mw pmd: 0xcf49ffb0 pte: 0x15555000
mw pmd: 0xcf49ffb8 pte: 0x15555000
mw pmd: 0xcf49ffc0 pte: 0x15555000
mw pmd: 0xcf49ffc8 pte: 0x15555000
mw pmd: 0xcf49ffd0 pte: 0x15555000
mw pmd: 0xcf49ffd8 pte: 0x15555000
mw pmd: 0xcf49ffe0 pte: 0x15555000
mw pmd: 0xcf49ffe8 pte: 0x15555000
mw pmd: 0xcf49fff0 pte: 0x15555000
mw pmd: 0xcf49fff8 pte: 0x15555000
mw pmd: 0xc0536df8 pte: 0xcf276000
mw pmd: 0xc0536e00 pte: 0xcf277000
mw pmd: 0xc0536ff8 pte: 0xcece8000

that's all i can think of right now that i found interesting

sRp

-- 
Scott Parish
Signed-off-by: srparish@us.ibm.com

  reply	other threads:[~2005-05-13 17:48 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-13 11:16 [patch] convert page-l3.h macros to inlines Scott Parish
2005-05-13 12:12 ` Gerd Knorr
2005-05-13 13:36   ` Scott Parish
2005-05-13 13:57     ` Scott Parish
2005-05-13 16:25       ` Gerd Knorr
2005-05-13 17:48         ` Scott Parish [this message]
2005-05-17 21:48           ` Scott Parish

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=20050513174802.GG27910@us.ibm.com \
    --to=srparish@us.ibm.com \
    --cc=kraxel@bytesex.org \
    --cc=xen-devel@lists.xensource.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.