[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: booting L2000 from netinstall image and netboot fails with panic



Grant Grundler wrote:

ugh. I really hate how HP VFP hides/prempts console output.
In order to see the missing console bits, one has to type ^B and
then "cl" (console log) to find the missing parts.

I did not know that VFP does such ugly things. So I retried with
vmalloc=256M (Is that a reasonable value?)

Here we are, booted from netinstall CD, interacted with IPL.

Command line for kernel: 'root=/dev/ram ramdisk_size=125800 console=ttyS0 TERM=vt102 vmalloc=256M palo_kernel=0'0/vmlinux'
Selected kernel: '0/vmlinux from partition 0
Selected ramdisk: /ramdisk from partition 0
Warning: kernel name doesn't end with 32 or 64 -- Guessing... Choosing 64-bit kernelELF64 executable
Entry 00100000 first 00100000 n 3
Segment 0 load 00100000 size 3850240 mediaptr 0x1000
Segment 1 load 00504000 size 383288 mediaptr 0x3ad000
Segment 2 load 00564000 size 381062 mediaptr 0x40b000
Loading ramdisk 4468640 bytes @ 3fbac000...
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.18-4-parisc64 (Debian 2.6.18.dfsg.1-11) (waldi@debian.org) (gcc version 4.1.2 20061115 (prerelease) (Debian 4.1.1-21)) #1 Wed Feb 21 10:20:02 MST 2007
FP[0] enabled: Rev 1 Model 16
The 64-bit Kernel has started...
Initialized PDC Console for debugging.
Determining PDC firmware type: 64 bit PAT.
model 00005c50 00000491 00000000 00000002 08ef50ff 100000f0 00000008 000000b2 000000b2
vers  00000301
CPUID vers 17 rev 11 (0x0000022b)
capabilities 0x1
model 9000/800/L2000-36
Total Memory: 1024 MB
initrd: 4fbac000-4ffeefa0
initrd: reserving 3fbac000-3ffeefa0 (mem_max 40000000)
Built 1 zonelists.  Total pages: 262144
Kernel command line: root=/dev/ram ramdisk_size=125800 console=ttyS0 TERM=vt102 vmalloc=256M palo_kernel=0'0/vmlinux
PID hash table entries: 4096 (order: 12, 32768 bytes)
start_kernel(): bug: interrupts were enabled early
Console: colour dummy device 160x64
Dentry cache hash table entries: 131072 (order: 8, 1048576 bytes)
Inode-cache hash table entries: 65536 (order: 7, 524288 bytes)
Memory: 1048576k available
Security Framework v1.0.0 initialized
SELinux:  Disabled at boot.
Capability LSM initialized
Mount-cache hash table entries: 256
checking if image is initramfs... it is
Freeing initrd memory: 4363k freed
NET: Registered protocol family 16
EISA bus registered
Searching for devices...
Found devices:
1. Rhapsody 360 at 0xfffffffffffa0000 [160] { 0, 0x0, 0x5c5, 0x00004 }
2. Rhapsody 360 at 0xfffffffffffa2000 [162] { 0, 0x0, 0x5c5, 0x00004 }
3. Rhapsody 360 at 0xfffffffffffa4000 [164] { 0, 0x0, 0x5c5, 0x00004 }
4. Rhapsody 360 at 0xfffffffffffa6000 [166] { 0, 0x0, 0x5c5, 0x00004 }
5. Memory at 0xfffffffffed08000 [8] { 1, 0x0, 0x095, 0x00009 }
6. Astro BC Runway Port at 0xfffffffffed00000 [0] { 12, 0x0, 0x582, 0x0000b }
7. Elroy PCI Bridge at 0xfffffffffed30000 [0/0] { 13, 0x0, 0x782, 0x0000a }
8. Elroy PCI Bridge at 0xfffffffffed32000 [0/1] { 13, 0x0, 0x782, 0x0000a }
9. Elroy PCI Bridge at 0xfffffffffed34000 [0/2] { 13, 0x0, 0x782, 0x0000a }
10. Elroy PCI Bridge at 0xfffffffffed36000 [0/3] { 13, 0x0, 0x782, 0x0000a }
11. Elroy PCI Bridge at 0xfffffffffed38000 [0/4] { 13, 0x0, 0x782, 0x0000a }
12. Elroy PCI Bridge at 0xfffffffffed3a000 [0/5] { 13, 0x0, 0x782, 0x0000a }
13. Elroy PCI Bridge at 0xfffffffffed3c000 [0/6] { 13, 0x0, 0x782, 0x0000a }
14. Elroy PCI Bridge at 0xfffffffffed3e000 [0/7] { 13, 0x0, 0x782, 0x0000a }
Enabling PDC_PAT chassis codes support v0.05

********** 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
*****************************************
allocation failed: out of vmalloc space - use vmalloc=<size> to increase size.
Elroy version TR3.0 (0x4) found at 0xfffffffffed3c000
allocation failed: out of vmalloc space - use vmalloc=<size> to increase size.
Elroy version TR3.0 (0x4) found at 0xfffffffffed3e000
allocation failed: out of vmalloc space - use vmalloc=<size> to increase size.
NET: Registered protocol family 2
IP route cache hash table entries: 32768 (order: 6, 262144 bytes)
TCP established hash table entries: 131072 (order: 8, 1048576 bytes)
TCP bind hash table entries: 65536 (order: 7, 524288 bytes)
TCP: Hash tables configured (established 131072 bind 65536)
TCP reno registered
Chassis warnings not supported.
unwind_init: start = 0x103e7520, end = 0x1040cf40, entries = 9634
Performance monitoring counters enabled for Rhapsody 360
audit: initializing netlink socket (disabled)
audit(1180967387.874:1): initialized
VFS: Disk quotas dquot_6.5.1
Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
Initializing Cryptographic API
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered (default)
PDC Stable Storage facility v0.30
Soft power switch support not available.
STI GSC/PCI core graphics driver Version 0.9a
Generic RTC Driver v1.07
Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing enabled
0000:00:04.0: ttyS0 at MMIO 0xfffffffff8000000 (irq = 69) is a 16550A
0000:00:04.0: ttyS1 at MMIO 0xfffffffff8000008 (irq = 69) is a 16550A
0000:00:04.0: ttyS2 at MMIO 0xfffffffff8000010 (irq = 69) is a 16550A
0000:00:05.0: ttyS3 at MMIO 0xfffffffff8006000 (irq = 70) is a 16550A
Couldn't register serial port 0000:00:05.0: -28
RAMDISK driver initialized: 16 RAM disks of 125800K size 1024 blocksize
mice: PS/2 mouse device common for all mice
TCP bic registered
NET: Registered protocol family 1
NET: Registered protocol family 17
Freeing unused kernel memory: 376k freed

********** 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
*****************************************
tulip0: no phy info, aborting mtable build
tulip0:  MII transceiver #1 config 1000 status 782d advertising 01e1.
eth0: Digital DS21142/43 Tulip rev 65 at Port 0x80, 00:10:83:FC:42:A3, IRQ 65.

********** 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 *************
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


Thats what VFP did showed up, now the missing part from cl:
0000:00:04.0: ttyS1 at MMIO 0xfffffffff8000008 (irq = 69) is a 16550A
0000:00:04.0: ttyS2 at MMIO 0xfffffffff8000010 (irq = 69) is a 16550A
0000:00:05.0: ttyS3 at MMIO 0xfffffffff8006000 (irq = 70) is a 16550A
Couldn't register serial port 0000:00:05.0: -28
RAMDISK driver initialized: 16 RAM disks of 65353K size 1024 blocksize
mice: PS/2 mouse device common for all mice
TCP bic registered
NET: Registered protocol family 1
NET: Registered protocol family 17
Freeing unused kernel memory: 376k freed
Linux Tulip driver version 1.1.13-NAPI (May 11, 2002)
tulip0: no phy info, aborting mtable build
tulip0:  MII transceiver #1 config 1000 status 782d advertising 01e1.
eth0: Digital DS21142/43 Tulip rev 65 at Port 0x80, 00:10:83:FC:42:A3, IRQ 65.
Backtrace:
 [<000000001011a60c>] outl+0x7c/0x88
 [<0000000010282ab4>] ioport_write32+0x14/0x20
 [<0000000010282ec8>] iowrite32+0x38/0x60
 [<0000000004086d54>] tulip_read_eeprom+0x64/0x240 [tulip]

 [<000000000408e154>] tulip_init_one+0x724/0x1110 [tulip]
 [<0000000010288fd0>] pci_device_probe+0x88/0xc8
 [<00000000102d82c0>] driver_probe_device+0x80/0xf8
 [<00000000102d84f4>] __driver_attach+0xac/0x138
 [<00000000102d791c>] bus_for_each_dev+0x6c/0xd0
 [<00000000102d8188>] driver_attach+0x28/0x38
 [<00000000102d731c>] bus_add_driver+0xb4/0x1d8
 [<00000000102d88d0>] driver_register+0xb8/0xc8
 [<0000000010289248>] __pci_register_driver+0x50/0x98
 [<000000000006c094>] tulip_init+0x74/0x80 [tulip]
 [<0000000010159fc4>] sys_init_module+0x17cc/0x1a00
 [<0000000010104f94>] syscall_exit+0x0/0x14


Kernel Fault: Code=15 regs=000000004e98cb50 (Addr=0000000000012000)

     YZrvWESTHLNXBCVMcbcbcbcbOGFRQPDI
PSW: 00001000000001001111111100001111 Not tainted
r00-03  000000ff0804ff0f 0000000010560d20 000000001011a60c 8000000000030048
r04-07  0000000004081000 000000000000000c 000000000000000c 8000000000030030

r08-11  0000000000000000 00000000000006ff 000000004e97c420 8000000000030000
r12-15  0000000000000003 000000004ffb0070 0000000000000048 000000000409248c
r16-19  0000000000000000 00000000000001c2 000000000005ce88 0000000000000000
r20-23  000000004ffaf400 0000000000000040 0000000000008010 0000000000000002
r24-27  0000004800480000 0000000000012000 000000004ff66a00 000000001054fd20
r28-31  000000000000fffc 000000004e98cb20 000000004e98cb50 0000000000012000
sr00-03  000000000023b800 0000000000000000 0000000000000000 000000000023b800
sr04-07  0000000000000000 0000000000000000 0000000000000000 0000000000000000

IASQ: 0000000000000000 0000000000000000 IAOQ: 00000000102903e0 00000000102903e4
 IIR: 0ff81280    ISR: 0000000000000000  IOR: 0000000000012000
 CPU:        0   CR30: 000000004e98c000 CR31: 0000000010508000
 ORIG_R28: 00000000105138c0
 IAOQ[0]: lba_pat_out32+0x30/0x50
 IAOQ[1]: lba_pat_out32+0x34/0x50
 RP(r2): outl+0x7c/0x88
Kernel panic - not syncing: Kernel Fault




then we go into the next try:
Firmware Version  41.39

Duplex Console IO Dependent Code (IODC) revision 1

------------------------------------------------------------------------------
   (c) Copyright 1995-2000, Hewlett-Packard Company, All rights reserved
------------------------------------------------------------------------------

  Processor   Speed            State           CoProcessor State  Cache Size
  Number                                       State              Inst    Data
  ---------  --------   ---------------------  -----------------  ------------
      0      360  MHz   Active                 Functional         512 KB   1 MB
      1      360  MHz   Idle                   Functional         512 KB   1 MB
      2      360  MHz   Idle                   Functional         512 KB   1 MB
      3      360  MHz   Idle                   Functional         512 KB   1 MB

  Central Bus Speed (in MHz)  :         82
  Available Memory            :    1048576  KB
  Good Memory Required        :      16580  KB



Anyway, the actual tombstone that we want to see can be acquired
in two ways:
1) ^B and then "cl" to review the entire console output. My guess is
the boot history is long gone and you'll need to try this again.

I hope above is sufficent.

2) answer "y" to "Interact with Boot loader" question.
   entire the number of the last parameter (as if you wanted
   to edit that paramter. _append_ "pdcchassis=0" to disable
   the OS from sending chassis codes to the firmware.
   This avoids the VFP from preempting the normal console output.
did not try this as the CL did show up things

This is the last I've heard about a driver for Tachlite:
http://www.ussg.iu.edu/hypermail/linux/kernel/0508.2/0113.html

This is no problem, as there is nothing behind this cards
at the moment. So the kernel should just ignore them.



Thanks

Christian



Reply to: