Re: Cannot boot 2.6.26 kernel on HPPA N4000

View: New views
8 Messages — Rating Filter:   Alert me  

Parent Message unknown Re: Cannot boot 2.6.26 kernel on HPPA N4000

by Moritz Muehlenhoff :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

On Mon, Mar 16, 2009 at 11:25:51AM -0700, Marc Rodriguez wrote:

> Package: linux-image
> Version: 2.6.26-parisc64
> Severity: Critical
>
>
> Attempting to boot a 2.6.26 kernel on an HP N4000 machine (64 bit PA-RISC)
> yields the following results (beginning at system startup):
> <<Beginning of error>>
>
>
>
> GSP Host Name:  uninitialized
>
> GSP> co
>
>
> CO
>
> You are now leaving the Guardian Service Processor Command Interface
> and returning to the console mode. Type Ctrl B to reactivate it.
>
>
>
> Configuration Menu: Enter command > ma
>  ---- Main
> Menu ---------------------------------------------------------------
>
>      Command                           Description
>      -------                           -----------
>      BOot [PRI|ALT|<path>]             Boot from specified path
>      PAth [PRI|ALT] [<path>]           Display or modify a path
>      SEArch [DIsplay|IPL] [<path>]     Search for boot devices
>
>      COnfiguration menu                Displays or sets boot values
>      INformation menu                  Displays hardware information
>      SERvice menu                      Displays service commands
>
>      DIsplay                           Redisplay the current menu
>      HElp [<menu>|<command>]           Display help for menu or command
>      RESET                             Restart the system
> ----
> Main Menu: Enter command or menu > bo
>
> Interact with IPL (Y, N, or Cancel)?> y
>  Booting...
> Boot IO Dependent Code (IODC) revision 1
>
>
> HARD Booted.
> palo ipl 1.14 root@duet Sat Apr  8 16:08:16 EDT 2006
>
> Skipping extended partition 6 - beyond reach of IPL
>
> Partition Start(MB) End(MB) Id Type
>
>
> 1               1      31   f0 Palo
>
>
> 2              32     156   83 ext2
>
>
> 5             157   67413   83 ext2
>
> PALO(F0) partition contains:
>
>     0/vmlinux64 6300839 bytes @ 0x48000
>
>
> Information: No console specified on kernel command line. This is normal.
>
> PALO will choose the console currently used by firmware (serial).Current
> command line:
>
> 2/vmlinux root=/dev/sda5 initrd=2/initrd.img HOME=/ console=ttyS0 TERM=vt102
>
>  0: 2/vmlinux
>
>  1: root=/dev/sda5
>
>  2: initrd=2/initrd.img
>
>  3: HOME=/
>
>  4: console=ttyS0
>
>  5: TERM=vt102
>
>
> <#>    edit the numbered field
>
> 'b'    boot with this command line
>
> 'r'    restore command line
>
> 'l'    list dir
>
> ? 0 b
>
>
> Command line for kernel: 'root=/dev/sda5 HOME=/ console=ttyS0 TERM=vt102
> palo_kernel=2/vmlinux'
>
> Selected kernel: /vmlinux from partition 2
>
> Selected ramdisk: /initrd.img from partition 2
>
> ELF64 executable
>
> Entry 00100000 first 00100000 n 3
>
> Segment 0 load 00100000 size 4648960 mediaptr 0x1000
>
> Segment 1 load 005c4000 size 395160 mediaptr 0x470000
>
> Segment 2 load 00628000 size 304384 mediaptr 0x4d1000
>
> Loading ramdisk 6339147 bytes @ 3f9e3000...
>
> 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.26 (2.6.26) (root@sys0t-debian) (gcc version 4.3.2 (GCC) )
> #1 SMP Mon Mar 16 07:17:55 MDT 2009
> FP[0] enabled: Rev 1 Model 16
> The 64-bit Kernel has started...
> console [ttyB0] enabled
> Initialized PDC Console for debugging.
> Determining PDC firmware type: 64 bit PAT.
> model 00005cc0 00000491 00000000 00000002 28f7f76d 100000f0 00000008
> 000000b2 000000b2
> vers  00000203
> CPUID vers 17 rev 8 (0x00000228)
> capabilities 0x1
> model 9000/800/N4000-44
> Memory Ranges:
>  0) Start 0x0000000000000000 End 0x000000007fffffff Size   2048 MB
>  1) Start 0x0000000180000000 End 0x00000001ffffffff Size   2048 MB
> Total Memory: 4096 MB
> initrd: 7f9e3000-7ffeea4b
> initrd: reserving 3f9e3000-3ffeea4b (mem_max 100000000)
> SMP: bootstrap CPU ID is 0
> Built 2 zonelists in Zone order, mobility grouping on.  Total pages: 1034240
> Kernel command line: root=/dev/sda5 HOME=/ console=ttyS0 TERM=vt102
> palo_kernel=2/vmlinux
> PID hash table entries: 4096 (order: 12, 32768 bytes)
> Console: colour dummy device 160x64
> Dentry cache hash table entries: 524288 (order: 10, 4194304 bytes)
> Inode-cache hash table entries: 262144 (order: 9, 2097152 bytes)
> Memory: 4109824k/4194304k available (3121k kernel code, 83764k reserved,
> 1370k data, 300k init)
> virtual kernel memory layout:
>     vmalloc : 0x0000000000008000 - 0x000000003f000000   (1007 MB)
>     memory  : 0x0000000040000000 - 0x0000000240000000   (8192 MB)
>       .init : 0x0000000040628000 - 0x0000000040673000   ( 300 kB)
>       .data : 0x000000004040c518 - 0x0000000040563000   (1370 kB)
>       .text : 0x0000000040100000 - 0x000000004040c518   (3121 kB)
> Security Framework initialized
> SELinux:  Disabled at boot.
> Capability LSM initialized
> Mount-cache hash table entries: 256
> Brought up 1 CPUs
> net_namespace: 1168 bytes
> NET: Registered protocol family 16
> EISA bus registered
> Searching for devices...
> Found devices:
> 1. Prelude W 440 at 0xfffffffffed25000 [37] { 0, 0x0, 0x5cc, 0x00004 }
> 2. Prelude W 440 at 0xfffffffffed2d000 [45] { 0, 0x0, 0x5cc, 0x00004 }
> 3. Prelude W 440 at 0xfffffffffed65000 [101] { 0, 0x0, 0x5cc, 0x00004 }
> 4. Prelude W 440 at 0xfffffffffed6d000 [109] { 0, 0x0, 0x5cc, 0x00004 }
> 5. DEW BC Runway Port at 0xfffffffffed24000 [36] { 7, 0x0, 0x584, 0x0000c }
> 6. DEW BC Runway Port at 0xfffffffffed2c000 [44] { 7, 0x0, 0x584, 0x0000c }
> 7. DEW BC Runway Port at 0xfffffffffed64000 [100] { 7, 0x0, 0x584, 0x0000c }
> 8. DEW BC Runway Port at 0xfffffffffed6c000 [108] { 7, 0x0, 0x584, 0x0000c }
> 9. Memory at 0xfffffffffedc0000 [192] { 1, 0x0, 0x090, 0x00009 }
> 10. IKE I/O BC Merced Port at 0xfffffffffed00000 [0] { 7, 0x0, 0x803,
> 0x0000c }
> 11. Elroy PCI Bridge at 0xffffffffbffe0000 [0/0] { 13, 0x0, 0x782, 0x0000a }
> 12. Elroy PCI Bridge at 0xffffffffbffe2000 [0/1] { 13, 0x0, 0x782, 0x0000a }
> 13. Elroy PCI Bridge at 0xffffffffbffe4000 [0/2] { 13, 0x0, 0x782, 0x0000a }
> 14. Elroy PCI Bridge at 0xffffffffbffe8000 [0/4] { 13, 0x0, 0x782, 0x0000a }
> 15. Elroy PCI Bridge at 0xffffffffbffea000 [0/5] { 13, 0x0, 0x782, 0x0000a }
> 16. Elroy PCI Bridge at 0xffffffffbfff0000 [0/8] { 13, 0x0, 0x782, 0x0000a }
> 17. Elroy PCI Bridge at 0xffffffffbfff4000 [0/10] { 13, 0x0, 0x782,
> 0x0000a }
> 18. Elroy PCI Bridge at 0xffffffffbfff8000 [0/12] { 13, 0x0, 0x782,
> 0x0000a }
> 19. IKE I/O BC Merced Port at 0xfffffffffed40000 [1] { 7, 0x0, 0x803,
> 0x0000c }
> 20. Elroy PCI Bridge at 0xfffffffffece0000 [1/0] { 13, 0x0, 0x782, 0x0000a }
> 21. Elroy PCI Bridge at 0xfffffffffece4000 [1/2] { 13, 0x0, 0x782, 0x0000a }
> 22. Elroy PCI Bridge at 0xfffffffffece8000 [1/4] { 13, 0x0, 0x782, 0x0000a }
> 23. Elroy PCI Bridge at 0xfffffffffecf0000 [1/8] { 13, 0x0, 0x782, 0x0000a }
> 24. Elroy PCI Bridge at 0xfffffffffecf4000 [1/10] { 13, 0x0, 0x782,
> 0x0000a }
> 25. Elroy PCI Bridge at 0xfffffffffecf8000 [1/12] { 13, 0x0, 0x782,
> 0x0000a }
> Enabling PDC_PAT chassis codes support v0.05
>
> ********** VIRTUAL FRONT PANEL **********
> System Boot detected
> *****************************************
> processor        system initialization 1C00
>
> *****************************************
>
> ************ EARLY BOOT VFP *************
> End of early boot detected
> *****************************************
> Releasing cpu 3 now, hpa=fffffffffed6d000
> FP[3] enabled: Rev 1 Model 16
> CPU(s): 4 x PA8500 (PCX-W) at 440.000000 MHz
> Setting cache flush threshold to 100000 (4 CPUs online)
> SBA found Ike rev 2 at 0xfffffffffed00000
> SBA found Ike rev 2 at 0xfffffffffed40000
> proc_dir_entry 'sba_iommu' already registered
> Backtrace:
>  [<000000004011bc58>] parisc_show_stack+0x48/0xe8
>  [<000000004011bd0c>] show_stack+0x14/0x20
>  [<00000000402c7818>] memcpy+0x28/0x40
>  [<00000000402243dc>] __proc_create+0xf4/0x188
>  [<000000004032cdf0>] driver_probe_device+0x148/0x278
>  [<000000004010347c>] ret_from_kernel_thread+0x24/0x40
>
> proc_dir_entry 'sba_iommu-bitmap' already registered
> Backtrace:
>  [<000000004011bc58>] parisc_show_stack+0x48/0xe8
>  [<000000004011bd0c>] show_stack+0x14/0x20
>  [<00000000402c7818>] memcpy+0x28/0x40
>  [<00000000402243dc>] __proc_create+0xf4/0x188
>  [<000000004032cdf0>] driver_probe_device+0x148/0x278
>  [<000000004010347c>] ret_from_kernel_thread+0x24/0x40
>
> Elroy version TR2.2 (0x3) found at 0xffffffffbffe0000
> Elroy version TR2.2 (0x3) found at 0xffffffffbffe2000
> Elroy version TR3.0 (0x4) found at 0xffffffffbffe4000
> Elroy version TR3.0 (0x4) found at 0xffffffffbffe8000
> Elroy version TR3.0 (0x4) found at 0xffffffffbffea000
> Elroy version TR3.0 (0x4) found at 0xffffffffbfff0000
> Elroy version TR3.0 (0x4) found at 0xffffffffbfff4000
> Elroy version TR3.0 (0x4) found at 0xffffffffbfff8000
> Elroy version TR3.0 (0x4) found at 0xfffffffffece0000
> Elroy version TR3.0 (0x4) found at 0xfffffffffece4000
> Elroy version TR3.0 (0x4) found at 0xfffffffffece8000
> Elroy version TR3.0 (0x4) found at 0xfffffffffecf0000
> Elroy version TR3.0 (0x4) found at 0xfffffffffecf4000
> PCI: Address space collision on region 0 of device 0000:d0:00.0
> [70e0800:70e08ff]
> Elroy version TR3.0 (0x4) found at 0xfffffffffecf8000
> powersw: Soft power switch support not available.
> NET: Registered protocol family 2
> IP route cache hash table entries: 131072 (order: 8, 1048576 bytes)
> TCP established hash table entries: 262144 (order: 10, 4194304 bytes)
> TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
> TCP: Hash tables configured (established 262144 bind 65536)
> TCP reno registered
> NET: Registered protocol family 1
> checking if image is initramfs... it is
> Freeing initrd memory: 6190k freed
> Chassis warnings not supported.
> unwind_init: start = 0x404a7224, end = 0x404d19c4, entries = 10874
> Performance monitoring counters enabled for Prelude W 440
> audit: initializing netlink socket (disabled)
> type=2000 audit(1237216652.238:1): initialized
> VFS: Disk quotas dquot_6.5.1
> Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
> msgmni has been set to 8040
> io scheduler noop registered
> io scheduler anticipatory registered
> io scheduler deadline registered
> io scheduler cfq registered (default)
> PDC Stable Storage facility v0.30
> STI GSC/PCI core graphics driver Version 0.9a
> Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing enabled
> serial 0000:00:04.0: enabling device (0146 -> 0147)
> 0000:00:04.0: ttyS0 at MMIO 0xffffffff80000000 (irq = 70) is a 16550A
> console handover: boot [ttyB0] -> real [ttyS0]
> 0000:00:04.0: ttyS1 at MMIO 0xffffffff80000008 (irq = 70) is a 16550A
> 0000:00:04.0: ttyS2 at MMIO 0xffffffff80000010 (irq = 70) is a 16550A
> serial 0000:00:05.0: enabling device (0000 -> 0003)
> serial 0000:00:05.0: enabling SERR and PARITY (0003 -> 0143)
> 0000:00:05.0: ttyS3 at MMIO 0xffffffff80003000 (irq = 71) is a 16550A
> Couldn't register serial port 0000:00:05.0: -28
> brd: module loaded
> mice: PS/2 mouse device common for all mice
> TCP bic registered
> NET: Registered protocol family 17
> RPC: Registered udp transport module.
> RPC: Registered tcp transport module.
> Freeing unused kernel memory: <0>------------[ cut here ]------------
> Badness at arch/parisc/kernel/smp.c:323
>
>      YZrvWESTHLNXBCVMcbcbcbcbOGFRQPDI
> PSW: 00001000000001001111111100001110 Not tainted
> r00-03  000000ff0804ff0e 00000000406242a0 0000000040126378 00000000405f8740
> r04-07  0000000040612aa0 0000000000000000 0000000000000001 00000000bfc60220
> r08-11  000000004066d668 0000000040613aa0 0000000000000000 00000000bfc60110
> r12-15  00000000406142a0 0000000000000001 00000000406202a0 0000000040622aa0
> r16-19  00000000406132a0 0406152a0 00000000406152a0 0000000000000004
> r20-23  0000000000000000 0000000040673000 00000000405f31a0 0000000000000001
> r24-27  0000000000000001 0000000000000000 0000000000000002 0000000040612aa0
> r28-31  000000000800000e 00000000bfc605a0 00000000bfc605d0 0000000000000004
> sr00-03  0000000000000000 0000000000000000 0000000000000000 0000000000000000
> sr04-07  0000000000000000 0000000000000000 0000000000000000 0000000000000000
>
> IASQ: 0000000000000000 0000000000000000 IAOQ: 0000000040126388
> 00000000401263IR: 03ffe01f    ISR: 0000000000000000  IOR: 0000000000000000
>  CPU:        0   CR30: 00000000bfc60000 CR31: 0000000010578000
>  ORIG_R28: 00000000bf801be0
>  IAOQ[0]: smp_call_function+0x70/0x3a0
>  IAOQ[1]: smp_call_function+0x74/0x3a0
>  RP(r2): smp_call_function+0x60/0x3a0
> Backtrace:
>  [<00000000401556d8>] on_each_cpu+0x28/0x68
>  [<000000004011ad08>] flush_data_cache+0x28/0x38
>  [<000000004011a17c>] free_initmem+0x94/0x340
>  [<0000000040119324>] 0x228
>  [<0000000040628638>] kernel_init+0x4b8/0x508
>
> 300k freed
>
> ********** VIRTUAL FRONT PANEL **********
> System Boot detected
> *****************************************
> processor        system initialization 1C00
>
> *****************************************
>
> ************ EARLY BOOT VFP *************
> End of early boot detected
> *****************************************
> Begin: Loading essential drivers ... SCSI subsystem initialized
> done.
> Begin: Running /scripts/init-premount ... Linux Tulip driver version
> 1.1.15-NAPI (Feb 27, 2007)
> tulip 0000:00:00.0: enabling device (0140 -> 0143)
> tulip0: no phy info, aborting mtable build
> tulip0:  MII transceiver #1 config 1000 status 7809 advertising 0061.
> eth0: Digital DS21142/43 Tulip rev 65 at MMIO 0xffffffff80004000,
> 00:10:83:96:71:d4, IRQ 66.
> sym53c8xx 0000:00:01.0: enabling device (0000 -> 0003)
> sym53c8xx 0000:00:01.0: enabling SERR and PARITY (0003 -> 0143)
> sym0: <895> rev 0x1 at pci 0000:00:01.0 irq 67
> sym0: PA-RISC Firmware, ID 7, Fast-40, SE, parity checking
> sym0: SCSI BUS has been reset.
> sym0: SCSI BUS mode change from SE to SE.
> sym0: SCSI BUS has been reset.
> scsi0 : sym-2.2.3
> scsi 0:0:2:0: CD-ROM            HP       DVD-ROM 304      2.01 PQ: 0 ANSI: 2
>  target0:0:2: Beginning Domain Validation
>  target0:0:2: asynchronous
>  target0:0:2: FAST-20 SCSI 20.0 MB/s ST (50 ns, offset 16)
>  target0:0:2: Domain Validation skipping write tests
>  target0:0:2: Ending Domain Validation
> sym53c8xx 0000:00:02.0: enabling device (0146 -> 0147)
> sym1: <875> rev 0x14 at pci 0000:00:02.0 irq 68
> sym1: PA-RISC Firmware, ID 7, Fast-20, SE, parity checking
> sym1: SCSI BUS has been reset.
> scsi1 : sym-2.2.3
> scsi 1:0:6:0: Direct-Access     SEAGATE  ST373405LC       0003 PQ: 0 ANSI: 3
>  target1:0:6: tagged command queuing enabled, command queue depth 16.
>  target1:0:6: Beginning Domain Validation
>  target1:0:6: asynchronous
>  target1:0:6: wide asynchronous
>  target1:0:6: FAST-20 WIDE SCSI 40.0 MB/s ST (50 ns, offset 16)
>  target1:0:6: Domain Validation skipping write tests
>  target1:0:6: Ending Domain Validation
> sym53c8xx 0000:00:02.1: enabling device (0000 -> 0003)
> sym53c8xx 0000:00:02.1: enabling SERR and PARITY (0003 -> 0143)
> sym2: <875> rev 0x14 at pci 0000:00:02.1 irq 69
> sym2: PA-RISC Firmware, ID 7, Fast-20, SE, parity checking
> sym2: SCSI BUS has been reset.
> scsi2 : sym-2.2.3
> scsi 2:0:6:0: Direct-Access     SEAGATE  ST373405LC       0003 PQ: 0 ANSI: 3
>  target2:0:6: tagged command queuing enabled, command queue depth 16.
>  target2:0:6: Beginning Domain Validation
>  target2:0:6: asynchronous
>  target2:0:6: wide asynchronous
>  target2:0:6: FAST-20 WIDE SCSI 40.0 MB/s ST (50 ns, offset 16)
>  target2:0:6: Domain Validation skipping write tests
>  target2:0:6: Ending Domain Validation
> sym53c8xx 0000:20:00.0: enabling device (0000 -> 0003)
> sym53c8xx 0000:20:00.0: enabling SERR and PARITY (0003 -> 0143)
> sym3: <896> rev 0x7 at pci 0000:20:00.0 irq 72
> sym3: PA-RISC Firmware, ID 7, Fast-40, LVD, parity checking
> sym3: SCSI BUS has been reset.
> scsi3 : sym-2.2.3
> scsi 3:0:0:0: Direct-Access     COMPAQ   BF07288285       HPB3 PQ: 0 ANSI: 3
>  target3:0:0: tagged command queuing enabled, command queue depth 16.
>  target3:0:0: Beginning Domain Validation
>  target3:0:0: asynchronous
>  target3:0:0: wide asynchronous
>  target3:0:0: FAST-40 WIDE SCSI 80.0 MB/s ST (25 ns, offset 31)
>  target3:0:0: Domain Validation skipping write tests
>  target3:0:0: Ending Domain Validation
> scsi 3:0:1:0: Direct-Access     COMPAQ   BF07288285       HPB3 PQ: 0 ANSI: 3
>  target3:0:1: tagged command queuing enabled, command queue depth 16.
>  target3:0:1: Beginning Domain Validation
>  target3:0:1: asynchronous
>  target3:0:1: wide asynchronous
>  target3:0:1: FAST-40 WIDE SCSI 80.0 MB/s ST (25 ns, offset 31)
>  target3:0:1: Domain Validation skipping write tests
>  target3:0:1: Ending Domain Validation
> scsi 3:0:2:0: Direct-Access     COMPAQ   BF07288285       HPB3 PQ: 0 ANSI: 3
>  target3:0:2: tagged command queuing enabled, command queue depth 16.
>  target3:0:2: Beginning Domain Validation
>  target3:0:2: asynchronous
>  target3:0:2: wide asynchronous
>  target3:0:2: FAST-40 WIDE SCSI 80.0 MB/s ST (25 ns, offset 31)
>  target3:0:2: Domain Validation skipping write tests
>  target3:0:2: Ending Domain Validation
> scsi 3:0:3:0: Direct-Access     COMPAQ   BF07288285       HPB3 PQ: 0 ANSI: 3
>  target3:0:3: tagged command queuing enabled, command queue depth 16.
>  target3:0:3: Beginning Domain Validation
>  target3:0:3: asynchronous
>  target3:0:3: wide asynchronous
>  target3:0:3: FAST-40 WIDE SCSI 80.0 MB/s ST (25 ns, offset 31)
>  target3:0:3: Domain Validation skipping write tests
>  target3:0:3: Ending Domain Validation
> scsi 3:0:4:0: Direct-Access     COMPAQ   BF07288285       HPB3 PQ: 0 ANSI: 3
>  target3:0:4: tagged command queuing enabled, command queue depth 16.
>  target3:0:4: Beginning Domain Validation
>  target3:0:4: asynchronous
>  target3:0:4: wide asynchronous
>  target3:0:4: FAST-40 WIDE SCSI 80.0 MB/s ST (25 ns, offset 31)
>  target3:0:4: Domain Validation skipping write tests
>  target3:0:4: Ending Domain Validation
> scsi 3:0:5:0: Direct-Access     COMPAQ   BF07288285       HPB3 PQ: 0 ANSI: 3
>  target3:0:5: tagged command queuing enabled, command queue depth 16.
>  target3:0:5: Beginning Domain Validation
>  target3:0:5: asynchronous
>  target3:0:5: wide asynchronous
>  target3:0:5: FAST-40 WIDE SCSI 80.0 MB/s ST (25 ns, offset 31)
>  target3:0:5: Domain Validation skipping write tests
>  target3:0:5: Ending Domain Validation
> scsi 3:0:8:0: Direct-Access     COMPAQ   BF07289BC4       HPB1 PQ: 0 ANSI: 3
>  target3:0:8: tagged command queuing enabled, command queue depth 16.
>  target3:0:8: Beginning Domain Validation
>  target3:0:8: asynchronous
>  target3:0:8: wide asynchronous
>  target3:0:8: FAST-40 WIDE SCSI 80.0 MB/s ST (25 ns, offset 31)
>  target3:0:8: Domain Validation skipping write tests
>  target3:0:8: Ending Domain Validation
> scsi 3:0:15:0: Processor         COMPAQ   PROLIANT 4L7E*DB 2.30 PQ: 0 ANSI:
> 2
>  target3:0:15: Beginning Domain Validation
> scsi 3:0:15:0: phase change 6-7 6@0025ffa0 resid=4.
>  target3:0:15: asynchronous
>  target3:0:15: Ending Domain Validation
> sym53c8xx 0000:20:00.1: enabling device (0000 -> 0003)
> sym53c8xx 0000:20:00.1: enabling SERR and PARITY (0003 -> 0143)
> sym4: <896> rev 0x7 at pci 0000:20:00.1 irq 73
> sym4: PA-RISC Firmware, ID 7, Fast-40, LVD, parity checking
> sym4: SCSI BUS has been reset.
> scsi4 : sym-2.2.3
> scsi 4:0:0:0: Direct-Access     COMPAQ   BF07288285       HPB3 PQ: 0 ANSI: 3
>  target4:0:0: tagged command queuing enabled, command queue depth 16.
>  target4:0:0: Beginning Domain Validation
>  target4:0:0: asynchronous
>  target4:0:0: wide asynchronous
>  target4:0:0: FAST-40 WIDE SCSI 80.0 MB/s ST (25 ns, offset 31)
>  target4:0:0: Domain Validation skipping write tests
>  target4:0:0: Ending Domain Validation
> scsi 4:0:1:0: Direct-Access     COMPAQ   BF07288285       HPB3 PQ: 0 ANSI: 3
>  target4:0:1: tagged command queuing enabled, command queue depth 16.
>  target4:0:1: Beginning Domain Validation
>  target4:0:1: asynchronous
>  target4:0:1: wide asynchronous
>  target4:0:1: FAST-40 WIDE SCSI 80.0 MB/s ST (25 ns, offset 31)
>  target4:0:1: Domain Validation skipping write tests
>  target4:0:1: Ending Domain Validation
> scsi 4:0:2:0: Direct-Access     COMPAQ   BF07288285       HPB3 PQ: 0 ANSI: 3
>  target4:0:2: tagged command queuing enabled, command queue depth 16.
>  target4:0:2: Beginning Domain Validation
>  target4:0:2: asynchronous
>  target4:0:2: wide asynchronous
>  target4:0:2: FAST-40 WIDE SCSI 80.0 MB/s ST (25 ns, offset 31)
>  target4:0:2: Domain Validation skipping write tests
>  target4:0:2: Ending Domain Validation
> scsi 4:0:3:0: Direct-Access     COMPAQ   BF07288285       HPB3 PQ: 0 ANSI: 3
>  target4:0:3: tagged command queuing enabled, command queue depth 16.
>  target4:0:3: Beginning Domain Validation
>  target4:0:3: asynchronous
>  target4:0:3: wide asynchronous
>  target4:0:3: FAST-40 WIDE SCSI 80.0 MB/s ST (25 ns, offset 31)
>  target4:0:3: Domain Validation skipping write tests
>  target4:0:3: Ending Domain Validation
> scsi 4:0:4:0: Direct-Access     COMPAQ   BF07288285       HPB3 PQ: 0 ANSI: 3
>  target4:0:4: tagged command queuing enabled, command queue depth 16.
>  target4:0:4: Beginning Domain Validation
>  target4:0:4: asynchronous
>  target4:0:4: wide asynchronous
>  target4:0:4: FAST-40 WIDE SCSI 80.0 MB/s ST (25 ns, offset 31)
>  target4:0:4: Domain Validation skipping write tests
>  target4:0:4: Ending Domain Validation
> scsi 4:0:5:0: Direct-Access     COMPAQ   BF07288285       HPB3 PQ: 0 ANSI: 3
>  target4:0:5: tagged command queuing enabled, command queue depth 16.
>  target4:0:5: Beginning Domain Validation
>  target4:0:5: asynchronous
>  target4:0:5: wide asynchronous
>  target4:0:5: FAST-40 WIDE SCSI 80.0 MB/s ST (25 ns, offset 31)
>  target4:0:5: Domain Validation skipping write tests
>  target4:0:5: Ending Domain Validation
> scsi 4:0:8:0: Direct-Access     COMPAQ   BF07288285       HPB3 PQ: 0 ANSI: 3
>  target4:0:8: tagged command queuing enabled, command queue depth 16.
>  target4:0:8: Beginning Domain Validation
>  target4:0:8: asynchronous
>  target4:0:8: wide asynchronous
>  target4:0:8: FAST-40 WIDE SCSI 80.0 MB/s ST (25 ns, offset 31)
>  target4:0:8: Domain Validation skipping write tests
>  target4:0:8: Ending Domain Validation
> sym53c8xx 0000:d0:00.0: enabling device (0000 -> 0003)
> sym53c8xx 0000:d0:00.0: enabling SERR and PARITY (0003 -> 0143)
>
> ************* SYSTEM ALERT **************
> SYSTEM NAME: uninitialized
> DATE: 03/16/2009 TIME: 15:18:15
> ALERT LEVEL: 7 = reserved
>
> REASON FOR ALERT
> SOURCE: 0 = unknown, no source stated
> SOURCE DETAIL: 0 = unknown, no source stated   SOURCE ID: FF
> PROBLEM DETAIL: 0 = no problem detail
>
> LEDs:  RUN      ATTENTION     FAULT     REMOTE     POWER
>        ON       FLASH         OFF       ON         ON
>
> 0x0000187000FF6292 00000000 00000000 - type  0 = Data Field Unused
> 0x5800187000FF6292 00006D02 100F120F - type 11 = Timestamp 03/16/2009
> 15:18:15
> A: ack read of this entry - X: Disable all future alert messages
> Anything else skip redisplay the log entry
> ->Choice:a
> *****************************************
> <<End of error message>>
>
> We found a similiar error at http://lkml.org/lkml/2008/7/16/327 that
> explains the inability to boot a 2.6.26 kernel that has the
> CONFIG_PRINTK_TIME flag set to y.  We recompiled a version of that kernel
> with the flag set to n (it was already set to that value) and we get a
> little farther in the boot sequence but end up with the same error message.
> What/how can we get this version of the kernel to boot?  We are attempting
> to run Debian 5.0 but end up with a non-working df if we use kernel
> 2.6.18-6-parisc64 (which is the version of the kernel that is installed with
> 4.0).  2.6.18-6 is the only other linux kernel that we have successfully
> booted with.
> Thanks,
> Marc

[Adding debian-hppa to CC and quoting in full]

Is this a known issue, has it been fixed in current kernels from unstable?

Cheers,
        Moritz


--
To UNSUBSCRIBE, email to debian-hppa-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...


Re: Cannot boot 2.6.26 kernel on HPPA N4000

by Thibaut VARENE-6 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

On Sat, Jul 25, 2009 at 4:10 PM, Moritz Muehlenhoff<jmm@...> wrote:

> [Adding debian-hppa to CC and quoting in full]
>
> Is this a known issue, has it been fixed in current kernels from unstable?

I believe this relates to that previous post:
http://www.mail-archive.com/debian-hppa@.../msg06301.html

Debian kernel seems to triggers HPMCs with PCI addon cards. It's been
discussed previously here, dunno what the status of that bug is, but
iirc it doesn't affect upstream.

HTH

--
Thibaut VARENE
http://www.parisc-linux.org/~varenet/


--
To UNSUBSCRIBE, email to debian-hppa-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...


Re: Cannot boot 2.6.26 kernel on HPPA N4000

by Grant Grundler :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Moritz,
thanks for forwarding...

On Sat, Jul 25, 2009 at 04:10:04PM +0200, Moritz Muehlenhoff wrote:
> > Attempting to boot a 2.6.26 kernel on an HP N4000 machine (64 bit PA-RISC)
> > yields the following results (beginning at system startup):
> > <<Beginning of error>>

...
> > Elroy version TR3.0 (0x4) found at 0xfffffffffecf4000
> > PCI: Address space collision on region 0 of device 0000:d0:00.0
> > [70e0800:70e08ff]
...
> > sym53c8xx 0000:d0:00.0: enabling device (0000 -> 0003)
> > sym53c8xx 0000:d0:00.0: enabling SERR and PARITY (0003 -> 0143)
> >
> > ************* SYSTEM ALERT **************
...
> > 0x0000187000FF6292 00000000 00000000 - type  0 = Data Field Unused
> > 0x5800187000FF6292 00006D02 100F120F - type 11 = Timestamp 03/16/2009

The address space collision is likely the cause of this HPMC.
(0xff6292 == HPMC)

With HPMC's, "PIM" info is worth collecting. See
    http://www.parisc-linux.org/faq/kernelbug-howto.html

for details on how to collect PIM info.

It would also be helpful to collect "in io" output from the same PDC
prompt that allows one to run "ser pim" and "clearpim".

Lastly, if an older kernel does boot, "lspci -v" would be helpful.


> Is this a known issue, has it been fixed in current kernels from unstable?

The "parenting" of resources in the generic PCI support has been changed.
I can't say if it fixes this problem. Is it possible to test a 2.6.30
or 2.6.31-rc kernel?

thanks,
grant


--
To UNSUBSCRIBE, email to debian-hppa-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...


Re: Cannot boot 2.6.26 kernel on HPPA N4000

by Grant Grundler :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

On Sat, Jul 25, 2009 at 05:08:24PM +0200, Thibaut VARENE wrote:

> On Sat, Jul 25, 2009 at 4:10 PM, Moritz Muehlenhoff<jmm@...> wrote:
>
> > [Adding debian-hppa to CC and quoting in full]
> >
> > Is this a known issue, has it been fixed in current kernels from unstable?
>
> I believe this relates to that previous post:
> http://www.mail-archive.com/debian-hppa@.../msg06301.html
>
> Debian kernel seems to triggers HPMCs with PCI addon cards. It's been
> discussed previously here, dunno what the status of that bug is, but
> iirc it doesn't affect upstream.


While many PCI cards won't work in PARISC systems, some do including many
of those sold by HP. For generic PCI support, AFAIK, only PCI-PCI bridge
support is broken and I've not tested those in a while. I have two systems
setup in Cupertino Test Ring which each have one add-on card with PCI-PCI
bridge (rio and ios).

cheers,
grant


--
To UNSUBSCRIBE, email to debian-hppa-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...


Re: Cannot boot 2.6.26 kernel on HPPA N4000

by Thibaut VARENE-6 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

On Sun, Jul 26, 2009 at 4:45 PM, Grant
Grundler<grundler@...> wrote:
> On Sat, Jul 25, 2009 at 05:08:24PM +0200, Thibaut VARENE wrote:

>> Debian kernel seems to triggers HPMCs with PCI addon cards. It's been
>> discussed previously here, dunno what the status of that bug is, but
>> iirc it doesn't affect upstream.
>
>
> While many PCI cards won't work in PARISC systems, some do including many
> of those sold by HP. For generic PCI support, AFAIK, only PCI-PCI bridge
> support is broken and I've not tested those in a while. I have two systems
> setup in Cupertino Test Ring which each have one add-on card with PCI-PCI
> bridge (rio and ios).

I guess this wasn't obvious enough from the thread I was pointing to,
but this bug affects otherwise perfectly working PCI cards (such as
tulip, SYM2, or tg3). As I said, only 2.6.26 from Debian seems to be
affected (among the few kernels I've tested).

HTH

--
Thibaut VARENE
http://www.parisc-linux.org/~varenet/


--
To UNSUBSCRIBE, email to debian-hppa-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...


Re: Bug#519984: Cannot boot 2.6.26 kernel on HPPA N4000

by dann frazier-3 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

On Sun, Jul 26, 2009 at 04:59:34PM +0200, Thibaut VARENE wrote:

> On Sun, Jul 26, 2009 at 4:45 PM, Grant
> Grundler<grundler@...> wrote:
> > On Sat, Jul 25, 2009 at 05:08:24PM +0200, Thibaut VARENE wrote:
>
> >> Debian kernel seems to triggers HPMCs with PCI addon cards. It's been
> >> discussed previously here, dunno what the status of that bug is, but
> >> iirc it doesn't affect upstream.
> >
> >
> > While many PCI cards won't work in PARISC systems, some do including many
> > of those sold by HP. For generic PCI support, AFAIK, only PCI-PCI bridge
> > support is broken and I've not tested those in a while. I have two systems
> > setup in Cupertino Test Ring which each have one add-on card with PCI-PCI
> > bridge (rio and ios).
>
> I guess this wasn't obvious enough from the thread I was pointing to,
> but this bug affects otherwise perfectly working PCI cards (such as
> tulip, SYM2, or tg3). As I said, only 2.6.26 from Debian seems to be
> affected (among the few kernels I've tested).

If we can narrow down the fix/config, we can try and fix it in a point
release.

--
dann frazier


--
To UNSUBSCRIBE, email to debian-hppa-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...


Re: Cannot boot 2.6.26 kernel on HPPA N4000

by Moritz Muehlenhoff :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

On Sun, Jul 26, 2009 at 08:39:22AM -0600, Grant Grundler wrote:

> Moritz,
> thanks for forwarding...
>
> On Sat, Jul 25, 2009 at 04:10:04PM +0200, Moritz Muehlenhoff wrote:
> > > Attempting to boot a 2.6.26 kernel on an HP N4000 machine (64 bit PA-RISC)
> > > yields the following results (beginning at system startup):
> > > <<Beginning of error>>
>
> ...
> > > Elroy version TR3.0 (0x4) found at 0xfffffffffecf4000
> > > PCI: Address space collision on region 0 of device 0000:d0:00.0
> > > [70e0800:70e08ff]
> ...
> > > sym53c8xx 0000:d0:00.0: enabling device (0000 -> 0003)
> > > sym53c8xx 0000:d0:00.0: enabling SERR and PARITY (0003 -> 0143)
> > >
> > > ************* SYSTEM ALERT **************
> ...
> > > 0x0000187000FF6292 00000000 00000000 - type  0 = Data Field Unused
> > > 0x5800187000FF6292 00006D02 100F120F - type 11 = Timestamp 03/16/2009
>
> The address space collision is likely the cause of this HPMC.
> (0xff6292 == HPMC)
>
> With HPMC's, "PIM" info is worth collecting. See
>     http://www.parisc-linux.org/faq/kernelbug-howto.html
>
> for details on how to collect PIM info.
>
> It would also be helpful to collect "in io" output from the same PDC
> prompt that allows one to run "ser pim" and "clearpim".
>
> Lastly, if an older kernel does boot, "lspci -v" would be helpful.
>
>
> > Is this a known issue, has it been fixed in current kernels from unstable?
>
> The "parenting" of resources in the generic PCI support has been changed.
> I can't say if it fixes this problem. Is it possible to test a 2.6.30
> or 2.6.31-rc kernel?

That will be difficult for the bug submitter, since the current versions
of the debian installer are not yet based on 2.6.30 AFAICT.

However, maybe the PCI card, which causes the collision can be temporarily
removed, so that the installation proceeds. After that, the 2.6.30 kernel
from unstable could be installed and the PCI card re-plugged in.

Marc, would you be able to test this?

Cheers,
        Moritz










--
To UNSUBSCRIBE, email to debian-hppa-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...


Re: Cannot boot 2.6.26 kernel on HPPA N4000

by Grant Grundler :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

On Mon, Jul 27, 2009 at 11:16:21PM +0200, Moritz Muehlenhoff wrote:
...
> However, maybe the PCI card, which causes the collision can be temporarily
> removed, so that the installation proceeds. After that, the 2.6.30 kernel
> from unstable could be installed and the PCI card re-plugged in.

That sounds like a good idea. I don't have a better one other than
providing the kernel binaries from a custom build.

thanks,
grant

> Marc, would you be able to test this?
>
> Cheers,
>         Moritz
>
>
>
>
>
>
>
>


--
To UNSUBSCRIBE, email to debian-hppa-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...