From: Benjamin Herrenschmidt <benh@kernel•crashing.org>
To: will_schmidt@vnet•ibm.com
Cc: linuxppc-dev@ozlabs•org, Paul Mackerras <paulus@samba•org>
Subject: Re: Program Check (700) in lpar.c:551 was: Re: patches in powerpc.git
Date: Thu, 08 Feb 2007 08:16:08 +1100 [thread overview]
Message-ID: <1170882968.2620.296.camel@localhost.localdomain> (raw)
In-Reply-To: <1170882651.6619.64.camel@localhost>
On Wed, 2007-02-07 at 15:10 -0600, Will Schmidt wrote:
> On Wed, 2007-07-02 at 15:03 +1100, Paul Mackerras wrote:
> > [POWERPC] Make pSeries use the H_BULK_REMOVE hypervisor call
>
>
> looks like this one ( f03e64f2ca6ee3d0b7824536b1940497701fe766 ) makes
> my JS20 tip over. I backed it just that patch and booted
> successfully, but havnt done any more poking than that.
What about "di c000000000035744" ?
Would it be possible that H_BULK_REMOVE isn't implemented by the js20's
firmware ?
Ben.
> console output follows:
> -----------------------------------------------------
> ppc64_pft_size = 0x19
> physicalMemorySize = 0x7c000000
> ppc64_caches.dcache_line_size = 0x80
> ppc64_caches.icache_line_size = 0x80
> htab_address = 0x0000000000000000
> htab_hash_mask = 0x3ffff
> -----------------------------------------------------
> PPC64 nvram contains 16384 bytes
> Zone PFN ranges:
> DMA 0 -> 507904
> Normal 507904 -> 507904
> early_node_map[1] active PFN ranges
> 0: 0 -> 507904
> [boot]0015 Setup Done
> Built 1 zonelists. Total pages: 500960
> Dentry cache hash table entries: 262144 (order: 9, 2097152 bytes)
> Inode-cache hash table entries: 131072 (order: 8, 1048576 bytes)
> freeing bootmem node 0
> Memory: 1986112k/2031616k available (6436k kernel code, 45504k reserved,
> 1392k data, 535k bss, 256k init)
> Mount-cache hash table entries: 256
> Processor 1 found.
> Brought up 2 CPUs
> ------------[ cut here ]------------
> kernel BUG
> at /kernels/powerpc.git.test/arch/powerpc/platforms/pseries/lpar.c:551!
> cpu 0x1: Vector: 700 (Program Check) at [c00000000264f280]
> pc: c000000000035744: .pSeries_lpar_flush_hash_range+0x12c/0x228
> lr: c000000000035738: .pSeries_lpar_flush_hash_range+0x120/0x228
> sp: c00000000264f500
> msr: 8000000000029032
> current = 0xc00000000ffdc810
> paca = 0xc00000000066ce00
> pid = 1, comm = swapper
> kernel BUG
> at /kernels/powerpc.git.test/arch/powerpc/platforms/pseries/lpar.c:551!
> enter ? for help
> [c00000000264f500] c0000000000357fc .pSeries_lpar_flush_hash_range
> +0x1e4/0x228 (unreliable)
> [c00000000264f620] c00000000002ce04 .flush_hash_range+0x50/0xb8
> [c00000000264f6c0] c00000000002d948 .__flush_tlb_pending+0xec/0x114
> [c00000000264f770] c0000000000a71ec .unmap_vm_area+0x1a8/0x270
> [c00000000264f840] c0000000000a7314 .remove_vm_area+0x60/0xb8
> [c00000000264f8d0] c0000000000a73bc .__vunmap+0x50/0x100
> [c00000000264f960] c000000000048a0c .build_sched_domains+0xdd8/0x10a0
> [c00000000264fd90] c000000000048d10 .arch_init_sched_domains+0x3c/0x54
> [c00000000264fe30] c00000000061e938 .sched_init_smp+0x2c/0xe0
> [c00000000264fec0] c000000000009310 .init+0x144/0x3b8
> [c00000000264ff90] c0000000000253b8 .kernel_thread+0x4c/0x68
> 1:mon>
> 1:mon> r
> R00 = fffffffffffffffd R16 = 4000000001c00000
> R01 = c00000000264f500 R17 = c00000000056c708
> R02 = c0000000007a5d50 R18 = 0000000000000000
> R03 = 0000000000000001 R19 = c00000000264fe00
> R04 = c000000002395018 R20 = 0000000000a00000
> R05 = 000000000000002d R21 = c0000000007d8000
> R06 = 420000000004d7a0 R22 = 00000000000000c0
> R07 = 000000000000002d R23 = 0000000000000001
> R08 = 420000000004d7b8 R24 = 0000000000000001
> R09 = 0000f09b89af5000 R25 = 0000000000000000
> R10 = 420000000004d7b0 R26 = 0000000000000000
> R11 = 0000f09b89af5000 R27 = 0000000000000003
> R12 = c00000000264f580 R28 = c00000000264f5b0
> R13 = c00000000066ce00 R29 = 0000000000000030
> R14 = fffffffffff81980 R30 = 4200000000000000
> R15 = c00000000056dd20 R31 = c000000002393310
> pc = c000000000035744 .pSeries_lpar_flush_hash_range+0x12c/0x228
> lr = c000000000035738 .pSeries_lpar_flush_hash_range+0x120/0x228
> msr = 8000000000029032 cr = 24000022
> ctr = 00000000000246fc xer = 00000000200fffff trap = 700
> 1:mon>
>
> -Will
>
> _______________________________________________
> Linuxppc-dev mailing list
> Linuxppc-dev@ozlabs•org
> https://ozlabs.org/mailman/listinfo/linuxppc-dev
next prev parent reply other threads:[~2007-02-07 21:16 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-07 4:03 patches in powerpc.git Paul Mackerras
2007-02-07 4:14 ` Grant Likely
2007-02-07 4:25 ` Olof Johansson
2007-02-07 4:55 ` Stephen Rothwell
2007-02-07 16:38 ` Will Schmidt
2007-02-07 23:42 ` Stephen Rothwell
2007-02-07 6:38 ` Pavel Fedin
2007-02-07 15:22 ` Vitaly Bordug
2007-02-07 22:07 ` Paul Mackerras
2007-02-07 7:39 ` Olof Johansson
2007-02-07 12:18 ` Johannes Berg
2007-02-07 16:11 ` Geert Uytterhoeven
2007-02-08 0:03 ` Paul Mackerras
2007-02-08 14:02 ` Geert Uytterhoeven
2007-02-08 18:42 ` James Simmons
2007-02-07 20:10 ` Guennadi Liakhovetski
2007-02-07 22:24 ` Paul Mackerras
2007-02-07 22:49 ` Guennadi Liakhovetski
2007-02-08 0:01 ` Kumar Gala
2007-02-07 21:10 ` Program Check (700) in lpar.c:551 was: " Will Schmidt
2007-02-07 21:16 ` Benjamin Herrenschmidt [this message]
2007-02-07 21:26 ` Benjamin Herrenschmidt
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=1170882968.2620.296.camel@localhost.localdomain \
--to=benh@kernel$(echo .)crashing.org \
--cc=linuxppc-dev@ozlabs$(echo .)org \
--cc=paulus@samba$(echo .)org \
--cc=will_schmidt@vnet$(echo .)ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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