[parisc-linux] Verify stack trace address - Joel

["Carlos O'Donell Jr." <carlos@baldric.uwo.ca>]

Joel,

> Here is the full output:
> Command line for kernel: 'root=/dev/sda5 HOME=/ console=ttyS0 TERM=vt102
> palo_kernel=3/vmlinux-kdb-gcc32'
> Selected kernel: /vmlinux-kdb-gcc32 from partition 3
> ELF32 executable
> Entry 00100000 first 00100000 n 5
> Segment 0 load 00100000 size 1989640 mediaptr 0x1000
> Segment 1 load 002e6000 size 767080 mediaptr 0x1e7000
> Segment 2 load 003a4000 size 396036 mediaptr 0x2a3000
> Segment 3 load 00408000 size 8192 mediaptr 0x304000
> Segment 4 load 00410000 size 32768 mediaptr 0x306000
> 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.4.18-pa26 (root@palx2000) (gcc version 3.2 20020530
> (experimental)) #1 Thu Jun 6 16:50:34 CEST 2002
> FP[0] enabled: Rev 1 Model 16
> The 32-bit Kernel has started...
> unwind_init: start = 0x10387405, end = 0x103a1468, entries = 6662
> 
> Stack: 10408600 Cannot find unwind entry for 0x1010c9c0
> 
> Call Trace: 
>         [<1010c880>]
            ^^^^^^^^

> Cannot find unwind entry for 0x1010c9c0
                               ^^^^^^^^^^

Can you find that address in your System.map to verify where that is?
If it's in unwind_table_init then the 'end[-1]' fix might be what is
needed.

 
> Code: 0e a0 10 93 4b d6 3f 91 0a 78 0a 13 6b 53 00 20 0a b6 04 14 
> Initialized PDC Console for debugging.
> Determining PDC firmware type: System Map.
> model 00005d00 00000481 00000000 00000002 77e93910 100000f0 00000008 000000b2
> 000000b2
> vers  00000301
> CPUID vers 17 rev 11 (0x0000022b)
> capabilities 0x3
> model 9000/785/B2000
> Total Memory: 256 Mb
> pagetable_init
> On node 0 totalpages: 65536
> zone(0): 65536 pages.
> zone(1): 0 pages.
> zone(2): 0 pages.
> LCD display at f05d0008,f05d0000 registered
> Kernel command line: root=/dev/sda5 HOME=/ console=ttyS0 TERM=vt102
> palo_kernel=3/vmlinux-kdb-gcc32
> Console: colour dummy device 160x64
> Initialized PDC Console for debugging.
> Calibrating delay loop... 799.53 BogoMIPS
> Memory: 254520k available
> kdb version 2.1 by Scott Lurndal, Keith Owens. Copyright SGI, All Rights Reserved
> Dentry-cache hash table entries: 32768 (order: 6, 262144 bytes)
> Inode-cache hash table entries: 16384 (order: 5, 131072 bytes)
> Mount-cache hash table entries: 4096 (order: 3, 32768 bytes)
> Buffer-cache hash table entries: 16384 (order: 4, 65536 bytes)
> Page-cache hash table entries: 65536 (order: 6, 262144 bytes)
> Searching for devices...
>

For some reason device detection becomes bogus and broken with
kdb enabled. So far we've seen SCSI, Serial, PCI/EISA all die with
kdb enabled. Maybe they're not dead and just moving _really_ slowly.

I'm going camping this weekend, so it's anyones game until Monday
afternoon (which I have off too!!) :)

c.