[parisc-linux-cvs] linux-2.6 willy

[Joel Soete]

Hello Willy,

> 
> CVSROOT:	/var/cvs
> Module name:	linux-2.6
> Changes by:	willy at cvs.parisc-linux.org	2005-01-20 15:47:03
> 
> Modified files:
> 	drivers/parisc : lba_pci.c 
> 
> Log message:
> 	Rename lba_cfg_ops to elroy_cfg_ops
> 	Use mercury_cfg_ops for TR4.0 Elroy
> 	Don't check for a non-1,2 or 4 size in the cfg_ops
> 	Call LBA_CFG_ADDR_SETUP instead of LBA_CFG_TR4_ADDR_SETUP in elroy_cfg_ops
> 	Don't read back from LBA_PCI_CFG_ADDR in LBA_CFG_TR4_ADDR_SETUP
> 	Remove LBA_FLAG_NO_DMA_DURING_CFG since it's always set for elroy_cfg_ops
> 	Remove LBA_TR4PLUS since we no longer need to test for it.
> 	Inline lba_common_init() into lba_driver_probe()
> 	Move TR2.1 check into an elroy-only path
> 	Check for LBAs that aren't Elroy, Mercury or Quicksilver.
> 
> Patches:
> http://cvs.parisc-linux.org/linux-2.6/drivers/parisc/lba_pci.c.diff?cvsroot=&r1=1.27&r2=1.28
> 
mmm this 64bit kernel failed to boot on b2k :-(
Command line for kernel: 'root=/dev/md2 HOME=/ panic=120 profile=2 console=ttyS0
TERM=vt102 palo_kernel=2/vmlinux-2.6.11-rc1-pa4-b2k
64'
Selected kernel: /vmlinux-2.6.11-rc1-pa4-b2k64 from partition 2
ELF64 executable
Entry 00100000 first 00100000 n 2
Segment 0 load 00100000 size 4810112 mediaptr 0x1000
Segment 1 load 00598000 size 675974 mediaptr 0x498000
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

....
I just grab the piminfo but not yet have time to analyse it (sorry) but already
noticed:
[...]
HPMC PIM Analysis Information:

Timestamp =
  Fri Jan  21 15:37:27 GMT 2005    (20:05:01:21:15:37:27)


'9000/785 B,C,J Workstation HPMC PIM Analysis (per-CPU)', rev 0, 1304 bytes:

A Data I/O Fetch Timeout occurred while CPU 0 was
requesting information from a device with the address 0xfffed30048.


Memory/IO Controller Error Analysis Information:

The Memory/IO Controller only observed the Broadcast Error.  It did not log
any additional information about the HPMC.

[...]

I will try to analyse this in more detail later...

Thanks,
    Joel