parisc fixes for 2.6.24
PATCH 1/1 parisc fixes for 2.6.24
The following changes since commit 09b56adc98e0f8a21644fcb4d20ad367c3fceb55:
Linus Torvalds (1):
Linux 2.6.24-rc4
are available in the git repository at:
/pub/scm/linux/kernel/git/kyle/parisc-2.6.git master
Kyle McMartin (5):
Revert "[PARISC] import necessary bits of libgcc.a" [PARISC] timer interrupt should not be IRQ_DISABLED [PARISC] Update parisc-linux MAINTAINERS entries [PARISC] print more than one character at a time for pdc console [PARISC] lba_pci: pci_claim_resources disabled expansion roms
MAINTAINERS | 10 +- arch/parisc/Makefile | 2 +- arch/parisc/kernel/firmware.c | 88 +- arch/parisc/kernel/irq.c | 2 +- arch/parisc/kernel/parisc_ksyms.c | 22 + arch/parisc/kernel/pdc_cons.c | 11 +- arch/parisc/lib/Makefile | 2 +- arch/parisc/lib/libgcc/Makefile | 4 - arch/parisc/lib/libgcc/__ashldi3.c | 19 - arch/parisc/lib/libgcc/__ashrdi3.c | 19 - arch/parisc/lib/libgcc/__clzsi2.c | 30 - arch/parisc/lib/libgcc/__divdi3.c | 23 - arch/parisc/lib/libgcc/__divsi3.c | 23 - arch/parisc/lib/libgcc/__lshrdi3.c | 19 - arch/parisc/lib/libgcc/__moddi3.c | 23 - arch/parisc/lib/libgcc/__modsi3.c | 23 - arch/parisc/lib/libgcc/__muldi3.c | 22 - arch/parisc/lib/libgcc/__udivdi3.c | 7 - arch/parisc/lib/libgcc/__udivmoddi4.c | 31 - arch/parisc/lib/libgcc/__udivmodsi4.c | 31 - arch/parisc/lib/libgcc/__udivsi3.c | 7 - arch/parisc/lib/libgcc/__umoddi3.c | 10 - arch/parisc/lib/libgcc/__umodsi3.c | 10 - arch/parisc/lib/libgcc/__umulsidi3.c | 46 - arch/parisc/lib/libgcc/libgcc.h | 32 - arch/parisc/lib/milli/Makefile | 1 - arch/parisc/lib/milli/divI.S | 254 ---- arch/parisc/lib/milli/divU.S | 235 ---- arch/parisc/lib/milli/div_const.S | 682 ----------- arch/parisc/lib/milli/dyncall.S | 32 - arch/parisc/lib/milli/milli.S | 2071 --------------------------------- arch/parisc/lib/milli/milli.h | 165 --- arch/parisc/lib/milli/mulI.S | 474 -------- arch/parisc/lib/milli/remI.S | 185 --- arch/parisc/lib/milli/remU.S | 148 --- drivers/parisc/lba_pci.c | 10 +- include/asm-parisc/pdc.h | 3 +- 37 files changed, 73 insertions(+), 4703 deletions(-) delete mode 100644 arch/parisc/lib/libgcc/Makefile delete mode 100644 arch/parisc/lib/libgcc/__ashldi3.c delete mode 100644 arch/parisc/lib/libgcc/__ashrdi3.c delete mode 100644 arch/parisc/lib/libgcc/__clzsi2.c delete mode 100644 arch/parisc/lib/libgcc/__divdi3.c delete mode 100644 arch/parisc/lib/libgcc/__divsi3.c delete mode 100644 arch/parisc/lib/libgcc/__lshrdi3.c delete mode 100644 arch/parisc/lib/libgcc/__moddi3.c delete mode 100644 arch/parisc/lib/libgcc/__modsi3.c delete mode 100644 arch/parisc/lib/libgcc/__muldi3.c delete mode 100644 arch/parisc/lib/libgcc/__udivdi3.c delete mode 100644 arch/parisc/lib/libgcc/__udivmoddi4.c delete mode 100644 arch/parisc/lib/libgcc/__udivmodsi4.c delete mode 100644 arch/parisc/lib/libgcc/__udivsi3.c delete mode 100644 arch/parisc/lib/libgcc/__umoddi3.c delete mode 100644 arch/parisc/lib/libgcc/__umodsi3.c delete mode 100644 arch/parisc/lib/libgcc/__umulsidi3.c delete mode 100644 arch/parisc/lib/libgcc/libgcc.h delete mode 100644 arch/parisc/lib/milli/Makefile delete mode 100644 arch/parisc/lib/milli/divI.S delete mode 100644 arch/parisc/lib/milli/divU.S delete mode 100644 arch/parisc/lib/milli/div_const.S delete mode 100644 arch/parisc/lib/milli/dyncall.S delete mode 100644 arch/parisc/lib/milli/milli.S delete mode 100644 arch/parisc/lib/milli/milli.h delete mode 100644 arch/parisc/lib/milli/mulI.S delete mode 100644 arch/parisc/lib/milli/remI.S delete mode 100644 arch/parisc/lib/milli/remU.S
Kyle,
Quoted 3 lines
are available in the git repository at:
/pub/scm/linux/kernel/git/kyle/parisc-2.6.git master
I built a SMP PA8800 configuration from this respository yesterday. Aside from the timeout issue that I've mentioned before, I've experienced erratic login behavior with this new kernel. I see this in the debug log:
Dec 16 11:28:39 mx3210 kernel: Dec 16 11:28:39 mx3210 kernel: do_page_fault() pid=1460 command='login' type=15 address=0xff0ca4e0 Dec 16 11:28:39 mx3210 kernel: vm_start = 0xfaf7d000, vm_end = 0xfaf93000 Dec 16 11:28:39 mx3210 kernel: Dec 16 11:28:39 mx3210 kernel: YZrvWESTHLNXBCVMcbcbcbcbOGFRQPDI Dec 16 11:28:39 mx3210 kernel: PSW: 00000000000011001000000000001111 Not tainted Dec 16 11:28:39 mx3210 kernel: r00-03 000000ff000c800f 0000000000000000 0000000 0405f3eeb 00000000faf80bc0 Dec 16 11:28:39 mx3210 kernel: r04-07 0000000040631d74 000000006e6f626f 0000000 0ffffffff 0000000000000000 Dec 16 11:28:39 mx3210 kernel: r08-11 0000000000000003 00000000faf80c88 0000000000000000 0000000040002130 Dec 16 11:28:39 mx3210 kernel: r12-15 0000000040634454 0000000000000000 00000000ffffffff 00000000ffffffff Dec 16 11:28:39 mx3210 kernel: r16-19 000000006e6f626f 0000000040633574 0000000041111008 0000000040631d74 Dec 16 11:28:39 mx3210 kernel: r20-23 0000000004149814 0000000000000000 0000000004149814 0000000000004000 Dec 16 11:28:39 mx3210 kernel: r24-27 0000000000000018 000000004525a820 000000004525a820 0000000000019014 Dec 16 11:28:39 mx3210 kernel: r28-31 0000000004149840 000000000000636b 00000000ff0ca500 0000000041052605 Dec 16 11:28:39 mx3210 kernel: sr00-03 000000000f9f7000 0000000000000000 0000000000000000 000000000f9f7000 Dec 16 11:28:39 mx3210 kernel: sr04-07 000000000f9f7000 000000000f9f7000 000000000f9f7000 000000000f9f7000 Dec 16 11:28:39 mx3210 kernel: Dec 16 11:28:39 mx3210 kernel: VZOUICununcqcqcqcqcqcrmunTDVZOUI Dec 16 11:28:39 mx3210 kernel: FPSR: 00001000000000000000000000000000 Dec 16 11:28:39 mx3210 kernel: FPER1: 00000000 Dec 16 11:28:39 mx3210 kernel: fr00-03 0800000000000000 0000000000000000 0000000000000000 0000000000000000 Dec 16 11:28:39 mx3210 kernel: fr04-07 00000000405cc000 00000000404b3780 00000000404a9780 00000000404a94c0 Dec 16 06:47:38 mx3210 identd[6240]: started Dec 16 11:28:39 mx3210 kernel: Dec 16 11:28:39 mx3210 kernel: do_page_fault() pid=1460 command='login' type=15 address=0xff0ca4e0 Dec 16 11:28:39 mx3210 kernel: vm_start = 0xfaf7d000, vm_end = 0xfaf93000 Dec 16 06:47:38 mx3210 identd[6240]: started Dec 16 11:28:39 mx3210 kernel: Dec 16 11:28:39 mx3210 kernel: do_page_fault() pid=1460 command='login' type=15 address=0xff0ca4e0 Dec 16 11:28:39 mx3210 kernel: vm_start = 0xfaf7d000, vm_end = 0xfaf93000 Dec 16 11:28:39 mx3210 kernel: Dec 16 11:28:39 mx3210 kernel: YZrvWESTHLNXBCVMcbcbcbcbOGFRQPDI Dec 16 11:28:39 mx3210 kernel: PSW: 00000000000011001000000000001111 Not tainted Dec 16 11:28:39 mx3210 kernel: r00-03 000000ff000c800f 0000000000000000 0000000 0405f3eeb 00000000faf80bc0 Dec 16 11:28:39 mx3210 kernel: r04-07 0000000040631d74 000000006e6f626f 0000000 0ffffffff 0000000000000000 Dec 16 11:28:39 mx3210 kernel: r08-11 0000000000000003 00000000faf80c88 0000000000000000 0000000040002130 Dec 16 11:28:39 mx3210 kernel: r12-15 0000000040634454 0000000000000000 00000000ffffffff 00000000ffffffff Dec 16 11:28:39 mx3210 kernel: r16-19 000000006e6f626f 0000000040633574 0000000041111008 0000000040631d74 Dec 16 11:28:39 mx3210 kernel: r20-23 0000000004149814 0000000000000000 0000000004149814 0000000000004000 Dec 16 11:28:39 mx3210 kernel: r24-27 0000000000000018 000000004525a820 000000004525a820 0000000000019014 Dec 16 11:28:39 mx3210 kernel: r28-31 0000000004149840 000000000000636b 00000000ff0ca500 0000000041052605 Dec 16 11:28:39 mx3210 kernel: sr00-03 000000000f9f7000 0000000000000000 0000000000000000 000000000f9f7000 Dec 16 11:28:39 mx3210 kernel: sr04-07 000000000f9f7000 000000000f9f7000 000000000f9f7000 000000000f9f7000 Dec 16 11:28:39 mx3210 kernel: Dec 16 11:28:39 mx3210 kernel: VZOUICununcqcqcqcqcqcrmunTDVZOUI Dec 16 11:28:39 mx3210 kernel: FPSR: 00001000000000000000000000000000 Dec 16 11:28:39 mx3210 kernel: FPER1: 00000000 Dec 16 11:28:39 mx3210 kernel: fr00-03 0800000000000000 0000000000000000 0000000000000000 0000000000000000 Dec 16 11:28:39 mx3210 kernel: fr04-07 00000000405cc000 00000000404b3780 00000000404a9780 00000000404a94c0 Dec 16 11:28:39 mx3210 kernel: fr08-11 00000000401b195c 0000000000000001 00000000405b9540 0000000000000802 Dec 16 11:28:39 mx3210 kernel: fr12-15 0000000000000001 00000000404a94c0 000000007fc40108 00000000405f3b40 Dec 16 11:28:39 mx3210 kernel: fr16-19 00000000405ef528 fffffffffffff000 0000000000000000 0000000000000802 Dec 16 11:28:39 mx3210 kernel: fr20-23 000000007f4fa000 000000007fc403a8 0000000000000000 00000000cccccccd Dec 16 11:28:39 mx3210 kernel: fr24-27 000000a355555556 3fe0000000000000 412e848000000000 00000000001e8480 Dec 16 11:28:39 mx3210 kernel: fr28-31 0000000000000802 000000007f4fa000 000000007fc403a8 00000000405b9540 Dec 16 11:28:39 mx3210 kernel: Dec 16 11:28:39 mx3210 kernel: IASQ: 000000000f9f7000 000000000f9f7000 IAOQ: 00000000405f428b 00000000405f422b Dec 16 11:28:39 mx3210 kernel: IIR: 6bd33fc1 ISR: 000000000f9f7000 IOR: 00000000ff0ca4e0 Dec 16 11:28:39 mx3210 kernel: CPU: 1 CR30: 000000007e380000 CR31: fffffff0f0e098e0 Dec 16 11:28:39 mx3210 kernel: ORIG_R28: 0000000000000000 Dec 16 11:28:39 mx3210 kernel: IAOQ[0]: per_cpu__runqueues+0x748/0x14c0 Dec 16 11:28:39 mx3210 kernel: IAOQ[1]: per_cpu__runqueues+0x6e8/0x14c0 Dec 16 11:28:39 mx3210 kernel: RP(r2): per_cpu__runqueues+0x3a8/0x14c0
dave@hiauly6:~$ disasm 0x6bd33fc1 0: 6b d3 3f c1 stw r19,-20(sp)
This insn saves the PIC register. Typically, this save occurs in a function's prologue after the new frame is allocated.
The stack pointer (0xff0ca500) is clearly bad:
(gdb) p 0xff0ca500 - 0xfaf7d000
$1 = 68474112 (0x414d500)
(gdb) p 0xff0ca4e0 - 0xfaf7d000
$2 = 68474080
(gdb) p 0xfaf93000 - 0xfaf7d000
$3 = 90112
$ ulimit -s 16384 (kbytes)
It's not clear how the stack pointer got corrupted but it is correctly rounded. I haven't seen this problem with my 2.6.22 builds.
I think the following code is the problem. We seem to just have done an alloca:
(gdb) disass 0x405f4258 0x405f4298
Dump of assembler code from 0x405f4258 to 0x405f4298:0x405f4258 <nscd_getgr_r+1628>: cmpb,= r5,ret0,0x405f3fec <nscd_getgr_r+1008> 0x405f425c <nscd_getgr_r+1632>: copy r4,r190x405f4260 <nscd_getgr_r+1636>: b,l 0x405f3f14 <nscd_getgr_r+792>,r0 0x405f4264 <nscd_getgr_r+1640>: copy r15,r70x405f4268 <nscd_getgr_r+1644>: ldo -38(sp),ret00x405f426c <nscd_getgr_r+1648>: depw,z r31,29,30,r200x405f4270 <nscd_getgr_r+1652>: stw r20,3c(r3)0x405f4274 <nscd_getgr_r+1656>: copy ret0,r90x405f4278 <nscd_getgr_r+1660>: ldo 46(r20),ret00x405f427c <nscd_getgr_r+1664>: depwi 0,31,6,ret00x405f4280 <nscd_getgr_r+1668>: add,l sp,ret0,sp0x405f4284 <nscd_getgr_r+1672>: b,l 0x405f4228 <nscd_getgr_r+1580>,r0 0x405f4288 <nscd_getgr_r+1676>: stw r19,-20(sp)0x405f428c <nscd_getgr_r+1680>: ldo 46(r22),r200x405f4290 <nscd_getgr_r+1684>: depwi 0,31,6,r200x405f4294 <nscd_getgr_r+1688>: add,l sp,r20,sp
ret0 is 0x4149840. So, the previous stack pointer was 0xfaf80cc0. This is in the vm range. ret0 is set from r31. It's not clear what sets r31 as this block is entered with a branch.
I wasn't able to get an assembly dump with symbols. We have the following libraries:
(gdb) info shared
Quoted 1 line
From To Syms Read Shared Object Library
0x400fe380 0x40116d74 Yes /lib/ld.so.1 0x4004c9b0 0x40053588 Yes /lib/libcrypt.so.1 0x4045ff0c 0x404664a4 Yes /lib/libpam.so.0 0x40301b40 0x40302cb0 Yes /lib/libpam_misc.so.0 0x4050cb60 0x405fe6e0 Yes /lib/libc.so.6 0x400e6ce4 0x400e80b0 Yes /lib/libdl.so.2
The above suggests a bug in the libc nscd support or the kernel support for it in 2.6.24-rc4.
Dave
Signature · 2 lines
J. David Anglin [email protected] National Research Council of Canada (613) 990-0752 (FAX: 952-6602)
Quoted 4 lines · John David Anglin
I built a SMP PA8800 configuration from this respository yesterday. Aside from the timeout issue that I've mentioned before, I've experienced erratic login behavior with this new kernel. I see this in the debug log:
is this using debian sid? or testing? possibly during the update to glibc 2.7 a regression crept in?
cheers,
kyle
Quoted 2 lines
is this using debian sid? or testing? possibly during the update to glibc 2.7 a regression crept in?
It's libc6 2.7-3. I've remove nscd to see if this goes away.
Dave
Signature · 2 lines
J. David Anglin [email protected] National Research Council of Canada (613) 990-0752 (FAX: 952-6602)
Quoted 8 lines · John David Anglin
Quoted 4 lines
I built a SMP PA8800 configuration from this respository yesterday. Aside from the timeout issue that I've mentioned before, I've experienced erratic login behavior with this new kernel. I see this in the debug log:
is this using debian sid? or testing? possibly during the update to glibc 2.7 a regression crept in?
Haven't seen any issues after deleting nscd. However, I built a kernel defaulted from the 2.6.22 .config on gsyprf11 yesterday. This one panics during boot. It's in /boot/vmlinux-2.6.24-rc4.
Dave
Signature · 2 lines
J. David Anglin [email protected] National Research Council of Canada (613) 990-0752 (FAX: 952-6602)
Quoted 6 lines · John David Anglin
Quoted 6 lines · John David Anglin
Quoted 4 lines
I built a SMP PA8800 configuration from this respository yesterday. Aside from the timeout issue that I've mentioned before, I've experienced erratic login behavior with this new kernel. I see this in the debug log:
Quoted 7 lines
Quoted 2 lines
is this using debian sid? or testing? possibly during the update to glibc 2.7 a regression crept in?
Haven't seen any issues after deleting nscd. However, I built a kernel defaulted from the 2.6.22 .config on gsyprf11 yesterday. This one panics during boot. It's in
/boot/vmlinux-2.6.24-rc4.
you need -rc5, iirc i put some changes i nthere too.
Quoted 1 line
you need -rc5, iirc i put some changes i nthere too.
This was with kyle/parisc-2.6.git which last changed 11 days ago. Does the linux rc5 tree now have all the changes from your branch?
Dave
Signature · 2 lines
J. David Anglin [email protected] National Research Council of Canada (613) 990-0752 (FAX: 952-6602)
Quoted 5 lines · John David Anglin
Quoted 1 line
you need -rc5, iirc i put some changes i nthere too.
This was with kyle/parisc-2.6.git which last changed 11 days ago. Does the linux rc5 tree now have all the changes from your branch?
yeah, sorry, linus isn't terribly good at replying to pull requests. :)
Quoted 9 lines · Kyle McMartin
Quoted 5 lines · John David Anglin
Quoted 1 line
you need -rc5, iirc i put some changes i nthere too.
This was with kyle/parisc-2.6.git which last changed 11 days ago. Does the linux rc5 tree now have all the changes from your branch?
yeah, sorry, linus isn't terribly good at replying to pull requests. :)
huh. sorry, i'll put my dunce cap on. there must be further regressions. :/
i'll muck about tomorrow evening.
cheers,
kyle
Quoted 6 lines · John David Anglin
Quoted 6 lines · John David Anglin
Quoted 4 lines
I built a SMP PA8800 configuration from this respository yesterday. Aside from the timeout issue that I've mentioned before, I've experienced erratic login behavior with this new kernel. I see this in the debug log:
Quoted 7 lines
Quoted 2 lines
is this using debian sid? or testing? possibly during the update to glibc 2.7 a regression crept in?
Haven't seen any issues after deleting nscd. However, I built a kernel defaulted from the 2.6.22 .config on gsyprf11 yesterday. This one panics during boot. It's in
/boot/vmlinux-2.6.24-rc4.
sigh, i bet this is 84f4506cb788d85a50c97b399f2999f90e6272b0[1]
does gsyprf11 have a quad port ethernet card installed?
cheers, kyle
Quoted 3 lines
sigh, i bet this is 84f4506cb788d85a50c97b399f2999f90e6272b0[1]
does gsyprf11 have a quad port ethernet card installed?
Not sure of the specifics but I see:
20:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5703X Gigabit Ethernet (rev 02) 30:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5703X Gigabit Ethernet (rev 02)
These devices probably contain a Broadcom switch.
Dave
Signature · 2 lines
J. David Anglin [email protected] National Research Council of Canada (613) 990-0752 (FAX: 952-6602)
Quoted 10 lines · John David Anglin
Quoted 3 lines
sigh, i bet this is 84f4506cb788d85a50c97b399f2999f90e6272b0[1]
does gsyprf11 have a quad port ethernet card installed?
Not sure of the specifics but I see:
20:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5703X Gigabit Ethernet (rev 02) 30:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5703X Gigabit Ethernet (rev 02)These devices probably contain a Broadcom switch.
can you post the console log of where it fails and/or try reverting that changeset and rebuilding? that's the only obvious change that i can think of causing a panic on boot.
cheers,
kyle
On Tue, Dec 18, 2007 at 12:27:50AM -0500, Kyle McMartin wrote:
...
Quoted 2 lines
sigh, i bet this is 84f4506cb788d85a50c97b399f2999f90e6272b0[1] does gsyprf11 have a quad port ethernet card installed?
Nope. Eveything on PCI bus 0 is on the motherboard. It has three addon cards:
-+-[0000:30]-+-00.0 Broadcom Corporation NetXtreme BCM5703X Gigabit Ethernet | +-02.0 LSI Logic / Symbios Logic 53C896/897 | \-02.1 LSI Logic / Symbios Logic 53C896/897 +-[0000:20]---00.0 Broadcom Corporation NetXtreme BCM5703X Gigabit Ethernet
Two tg3 cards and a dual port sym2 card.
"ios" (cupertino test cluster) has a 4-port card if you want to netboot some kernels on "ios". It's currently sitting at a PDC prompt.
hth,
grant
Quoted 2 lines · John David Anglin
Quoted 1 line
Quoted 1 line
you need -rc5, iirc i put some changes i nthere too.
Tried -rc6. It also crashed on boot. Console log is below.
Dave
Signature · 141 lines
J. David Anglin [email protected] National Research Council of Canada (613) 990-0752 (FAX: 952-6602) Boot IO Dependent Code (IODC) revision 1 HARD Booted. palo ipl 1.14 root@duet Sat Apr 8 16:08:16 EDT 2006 Partition Start(MB) End(MB) Id Type 1 1 191 f0 Palo 2 192 1526 82 swap 3 1527 34732 83 ext2 PALO(F0) partition contains: PALO is formatted EXT2/3 Command line for kernel: ' root=/dev/sda3 console=ttyS0 palo_kernel=1/vmlinux' Selected kernel: /vmlinux from partition 1 Selected ramdisk: /initrd.img from partition 1 ELF64 executable Entry 00100000 first 00100000 n 2 Segment 0 load 00100000 size 5013504 mediaptr 0x1000 Segment 1 load 00608000 size 566144 mediaptr 0x4c9000 Loading ramdisk 3388537 bytes @ 3fcb3000... Branching to kernel entry point 0x00100000. If this is the last message you see, you may need to switch your console. This is a common symptom -- search the FAQ and mailing list at parisc-linux.org Linux version 2.6.24-rc6 (dave@gsyprf11) (gcc version 4.2.3 20071123 (prerelease) (Debian 4.2.2-4)) #1 SMP Fri Dec 21 19:07:38 PST 2007 FP[0] enabled: Rev 1 Model 19 The 64-bit Kernel has started... console [ttyB0] enabled Initialized PDC Console for debugging. Determining PDC firmware type: 64 bit PAT. model 00005e30 00000491 00000000 00000001 312b7146 100000f0 00000008 000000b2 000000b2 vers 00000203 CPUID vers 19 rev 8 (0x00000268) capabilities 0x5 model 9000/800/A500-7X Memory Ranges: 0) Start 0x0000000000000000 End 0x00000000efffffff Size 3840 MB 1) Start 0x0000000100000000 End 0x00000001ffffffff Size 4096 MB 2) Start 0x00000010f0000000 End 0x00000010ffffffff Size 256 MB Total Memory: 8192 MB initrd: 7fcb3000-7ffee479 initrd: reserving 3fcb3000-3ffee479 (mem_max 200000000) SMP: bootstrap CPU ID is 0 Built 3 zonelists in Zone order, mobility grouping on. Total pages: 2068480 Kernel command line: root=/dev/sda3 console=ttyS0 palo_kernel=1/vmlinux PID hash table entries: 4096 (order: 12, 32768 bytes) Console: colour dummy device 160x64 Dentry cache hash table entries: 1048576 (order: 11, 8388608 bytes) Inode-cache hash table entries: 524288 (order: 10, 4194304 bytes) Memory: 8234192k/8388608k available (3309k kernel code, 152804k reserved, 1538k data, 188k init) virtual kernel memory layout: vmalloc : 0x0000000000008000 - 0x000000003f000000 (1007 MB) memory : 0x0000000040000000 - 0x0000001140000000 (69632 MB) .init : 0x0000000040664000 - 0x0000000040693000 ( 188 kB) .data : 0x000000004043b568 - 0x00000000405bc000 (1538 kB) .text : 0x0000000040100000 - 0x000000004043b568 (3309 kB) Mount-cache hash table entries: 256 Brought up 1 CPUs net_namespace: 120 bytes NET: Registered protocol family 16 Searching for devices... Found devices: 1. Crescendo 750 W2 at 0xfffffffffffa0000 [160] { 0, 0x0, 0x5e3, 0x00004 } 2. Crescendo 750 W2 at 0xfffffffffffa2000 [162] { 0, 0x0, 0x5e3, 0x00004 } 3. Memory at 0xfffffffffed08000 [8] { 1, 0x0, 0x09b, 0x00009 } 4. Astro BC Runway Port at 0xfffffffffed00000 [0] { 12, 0x0, 0x582, 0x0000b } 5. Elroy PCI Bridge at 0xfffffffffed30000 [0/0] { 13, 0x0, 0x782, 0x0000a } 6. Elroy PCI Bridge at 0xfffffffffed34000 [0/2] { 13, 0x0, 0x782, 0x0000a } 7. Elroy PCI Bridge at 0xfffffffffed38000 [0/4] { 13, 0x0, 0x782, 0x0000a } 8. Elroy PCI Bridge at ********** VIRTUAL FRONT PANEL ********** System Boot detected ***************************************** LEDs: RUN ATTENTION FAULT REMOTE POWER ON FLASH OFF ON ON LED State: There was a system interruption that did not take the system down. Check Chassis and Console Logs for error messages. processor system initialization 1C00 ***************************************** ************ EARLY BOOT VFP ************* End of early boot detected ***************************************** ********** VIRTUAL FRONT PANEL ********** System Boot detected ***************************************** LEDs: RUN ATTENTION FAULT REMOTE POWER ON FLASH FLASH ON ON LED State: System Running. Unexpected Reboot. Non-critical Error Detected. Check Chassis and Console Logs for error messages. processor system panic 1B00 ***** EARLY BOOT VFP : SYSTEM ALERT ***** SYSTEM NAME: gsyprf11c DATE: 12/22/2007 TIME: 03:45:54 ALERT LEVEL: 12 = Software failure REASON FOR ALERT SOURCE: 1 = processor SOURCE DETAIL: 1 = processor general SOURCE ID: 0 PROBLEM DETAIL: 0 = no problem detail LEDs: RUN ATTENTION FAULT REMOTE POWER ON FLASH FLASH ON ON LED State: System Running. Unexpected Reboot. Non-critical Error Detected. Check Chassis and Console Logs for error messages. 0xA0E000C01100B009 00000000 00000520 - type 20 = major change in system state 0x58E008C01100B009 00006B0B 16032D36 - type 11 = Timestamp 12/22/2007 03:45:54 A/a: ack read of this entry - Q/q: quit Virtual Front Panel Display Anything else redisplay the log entry ->Choice:Timeout! ***************************************** ***** EARLY BOOT VFP : SYSTEM ALERT ***** SYSTEM NAME: gsyprf11c DATE: 12/22/2007 TIME: 03:45:55 ALERT LEVEL: 12 = Software failure REASON FOR ALERT SOURCE: 1 = processor SOURCE DETAIL: 1 = processor general SOURCE ID: 0 PROBLEM DETAIL: 0 = no problem detail LEDs: RUN ATTENTION FAULT REMOTE POWER ON FLASH FLASH ON ON LED State: System Running. Unexpected Reboot. Non-critical Error Detected. Check Chassis and Console Logs for error messages. 0xA0E000C01100B009 00000000 00000520 - type 20 = major change in system state 0x58E008C01100B009 00006B0B 16032D37 - type 11 = Timestamp 12/22/2007 03:45:55 A/a: ack read of this entry - Q/q: quit Virtual Front Panel Display Anything else redisplay the log entry
Quoted 5 lines · John David Anglin
Quoted 2 lines · John David Anglin
Quoted 1 line
Quoted 1 line
you need -rc5, iirc i put some changes i nthere too.
Tried -rc6. It also crashed on boot. Console log is below.
i'm confused... my pa8800 box boots fine. i'll poke around a bit later today.
regards,
kyle
Quoted 2 lines
i'm confused... my pa8800 box boots fine. i'll poke around a bit later today.
I think gsyprf11 is a pa8700, 750 MHz. It boots fine with 2.6.22.x plus your getdents compat patch. The config and kernel are in /boot.
My pa8800 boots with 2.6.24*.
Dave
Signature · 2 lines
J. David Anglin [email protected] National Research Council of Canada (613) 990-0752 (FAX: 952-6602)