[parisc-linux] kdb_v21 branch updated to -pa26, and kallsyms cross-compile

[parisc-linux] kdb_v21 branch updated to -pa26, and kallsyms cross-compile

[Carlos O'Donell Jr.]

Parisc,

All the changes from -pa24 to -p26 have been merged into the
kdb-v21 tree (that Randolph graciously started!). Thanks go
to bame's recipe!

A few tests show that it is equivalent to the patches I had 
produced (fixes to traps.c for the soft power button).

If kdb is your bag, then it should all be set to go!

---

On another note... until I get a really fast PA box, I'm going
to be cross-compiling all the time. There are issues cross-compiling 
a kdb'd kernel, and the problem is called 'kallsyms'.

After a bout of idiocy and help from Jess I had a cross version
of kallsyms (never forget to 'unset CC'). 

It seemed like I was home free, except that I ran into the same
problem as before (even with the supposed _new_ cross kallsyms).

.tmp_vmlinux1: ELF file .tmp_vmlinux1 not for this architecture

I check ./src/modutils/obj/obj_load.c and find:

  if (f->header.e_ident[EI_CLASS] != ELFCLASSM
      || f->header.e_ident[EI_DATA] != ELFDATAM
      || f->header.e_ident[EI_VERSION] != EV_CURRENT
      || !MATCH_MACHINE(f->header.e_machine))
    {
       error("ELF file %s not for this architecture", filename);
       return NULL;
    }

So I breakup the values and test individually...

.tmp_vmlinux1: ELF file .tmp_vmlinux1 not for this architecture (!MATCH_MACHINE)

The MATCH_MACHINE macro is pretty dumb.
#define MATCH_MACHINE(x)  (x == EM_PARISC)

printf what e_machine header is set to:

ELF e_machine header is 3840
.tmp_vmlinux1: ELF file .tmp_vmlinux1 not for this architecture (!MATCH_MACHINE)

I'm not sure I've _ever_ seen a EM_??? value that big (EM_PARISC=15).
A closer inspection reveals that 3840 is 15 but byte swapped.

Which leaves me wondering... what else is going to be bytesex broke in
a cross modutils?

Is anyone familiar with modutils?
What would be a good way to include some cross-kallsyms support?

c.

Re: [parisc-linux] kdb_v21 branch updated to -pa26, and kallsyms cross-compile

[Patrick Caulfield]

On Mon, May 27, 2002 at 12:13:21AM -0400, Carlos O'Donell Jr. wrote:
> Parisc,
> 
> All the changes from -pa24 to -p26 have been merged into the
> kdb-v21 tree (that Randolph graciously started!). Thanks go
> to bame's recipe!
> 
> A few tests show that it is equivalent to the patches I had 
> produced (fixes to traps.c for the soft power button).
> 
> If kdb is your bag, then it should all be set to go!

I can't get it to boot on my C110 - it gets stuck at the old familar "if this is
the last message you see" message. I can run the Debian 2.4.18 kernel OK on this
box.

Any ideas anyone?

patrick

Re: [parisc-linux] kdb_v21 branch updated to -pa26, and kallsyms cross-compile

[Orac]

I have it running on a C110 currently. It was installed however on a
712/100 and drive was copied and kernel recompiled for the 7200 series
CPU. Are you running graphic or serial console? I am running serial
console only.

MaShaun Jones


On Tue, 28 May 2002, Patrick Caulfield wrote:

> On Mon, May 27, 2002 at 12:13:21AM -0400, Carlos O'Donell Jr. wrote:
> > Parisc,
> > 
> > All the changes from -pa24 to -p26 have been merged into the
> > kdb-v21 tree (that Randolph graciously started!). Thanks go
> > to bame's recipe!
> > 
> > A few tests show that it is equivalent to the patches I had 
> > produced (fixes to traps.c for the soft power button).
> > 
> > If kdb is your bag, then it should all be set to go!
> 
> I can't get it to boot on my C110 - it gets stuck at the old familar "if this is
> the last message you see" message. I can run the Debian 2.4.18 kernel OK on this
> box.
> 
> Any ideas anyone?
> 
> patrick
> 
> 
> _______________________________________________
> parisc-linux mailing list
> parisc-linux@lists.parisc-linux.org
> http://lists.parisc-linux.org/mailman/listinfo/parisc-linux
> 

Re: [parisc-linux] kdb_v21 branch updated to -pa26, and kallsyms cross-compile

[Patrick Caulfield]

On Tue, May 28, 2002 at 09:49:36AM -0500, Orac wrote:
> I have it running on a C110 currently. It was installed however on a
> 712/100 and drive was copied and kernel recompiled for the 7200 series
> CPU. Are you running graphic or serial console? I am running serial
> console only.
 
Serial. I've tried leaving after boot to see if it comes up but I can't see it
but nothing seems to happen (can't ping the box).

Could you send me your .config (or even the kernel!) please?

patrick

Re: [parisc-linux] kdb_v21 branch updated to -pa26, and kallsyms cross-compile

[Carlos O'Donell Jr.]

> I can't get it to boot on my C110 - it gets stuck at the old familar "if this is
> the last message you see" message. I can run the Debian 2.4.18 kernel OK on this
> box.
> Any ideas anyone?
> patricki

What gcc version are you using to compile your kernel?
What kernel parameters have you appended?
What version of modutils are you using?
Send your .config?
Serial console?

Helpful is the documentation can be found at:
http://oss.sgi.com/projects/kdb/

c.

Re: [parisc-linux] kdb_v21 branch updated to -pa26, and kallsyms cross-compile

[Patrick Caulfield]

[-- Attachment #1: Type: text/plain, Size: 1605 bytes --]

On Tue, May 28, 2002 at 01:29:33PM -0400, Carlos O'Donell Jr. wrote:
> 
> > I can't get it to boot on my C110 - it gets stuck at the old familar "if this is
> > the last message you see" message. I can run the Debian 2.4.18 kernel OK on this
> > box.
> > Any ideas anyone?
> > patricki
> 
> What gcc version are you using to compile your kernel?

3.0.4, this is a Debian "woody" installaion.

> What kernel parameters have you appended?
Just the defaults added by PALO (which include console=ttyS0)

> What version of modutils are you using?
2.4.15 FWIW

> Send your .config?
Attached

> Serial console?

yes
 
> Helpful is the documentation can be found at:
> http://oss.sgi.com/projects/kdb/

I've used KDB before on intel machines (until I discovered kgdb!) I was hoping
to find a kdb patch for parisc on that site so I could apply it to a known,
working kernel but there only appears to be intel & sparc ones.

I've had a good play with this last night and it seems to be the kernel config
but I'm not sure why. I copied the .config from the working Debian kernel, did a
"make oldconfig" and built it but...

Anyway. I plugged in a monitor and keyboard so I could see what's really going
on and I can see that the kernel /does/ boot but it can't find the FW scsi
controller and therefore the root filesystem.

So the problem is that I seem to have have configged out the serial console and
the SCSI controller but I'm not sure how. It must be something stupid I've done
but I can't see it.

Honest, I've built Linux kernels for sparc, alpha, intel and mips before, but
this one's beaten me!

patrick


[-- Attachment #2: pa-config --]
[-- Type: text/plain, Size: 16024 bytes --]

#
# Automatically generated by make menuconfig: don't edit
#
CONFIG_PARISC=y
# CONFIG_UID16 is not set
CONFIG_RWSEM_GENERIC_SPINLOCK=y
# CONFIG_RWSEM_XCHGADD_ALGORITHM is not set

#
# Code maturity level options
#
CONFIG_EXPERIMENTAL=y

#
# Loadable module support
#
CONFIG_MODULES=y
# CONFIG_MODVERSIONS is not set
CONFIG_KMOD=y

#
# Processor type
#
# CONFIG_PA7100 is not set
CONFIG_PA7200=y
# CONFIG_PA7100LC is not set
# CONFIG_PA8X00 is not set
CONFIG_PA11=y

#
# General options
#
# CONFIG_SMP is not set
CONFIG_CHASSIS_LCD_LED=y
# CONFIG_KWDB is not set
CONFIG_IOMMU_CCIO=y
CONFIG_GSC=y
CONFIG_GSC_LASI=y
CONFIG_GSC_WAX=y
CONFIG_EISA=y
CONFIG_ISA=y
CONFIG_PCI=y
CONFIG_GSC_DINO=y
CONFIG_PCI_LBA=y
CONFIG_IOSAPIC=y
CONFIG_IOMMU_SBA=y
CONFIG_SUPERIO=y
# CONFIG_PCI_NAMES is not set

#
# General setup
#
CONFIG_HOTPLUG=y
CONFIG_NET=y
CONFIG_SYSVIPC=y
# CONFIG_BSD_PROCESS_ACCT is not set
CONFIG_SYSCTL=y
CONFIG_KCORE_ELF=y
CONFIG_BINFMT_ELF=y
CONFIG_BINFMT_SOM=y
# CONFIG_BINFMT_MISC is not set
# CONFIG_PM is not set

#
# Parallel port support
#
CONFIG_PARPORT=y
CONFIG_PARPORT_PC=y
CONFIG_PARPORT_PC_CML1=y
# CONFIG_PARPORT_SERIAL is not set
# CONFIG_PARPORT_PC_FIFO is not set
# CONFIG_PARPORT_PC_SUPERIO is not set
# CONFIG_PARPORT_PC_PCMCIA is not set
# CONFIG_PARPORT_AMIGA is not set
# CONFIG_PARPORT_MFC3 is not set
# CONFIG_PARPORT_ATARI is not set
CONFIG_PARPORT_GSC=y
# CONFIG_PARPORT_SUNBPP is not set
# CONFIG_PARPORT_OTHER is not set
# CONFIG_PARPORT_1284 is not set

#
# Block devices
#
# CONFIG_BLK_DEV_FD is not set
# CONFIG_BLK_DEV_XD is not set
# CONFIG_PARIDE is not set
# CONFIG_BLK_CPQ_DA is not set
# CONFIG_BLK_CPQ_CISS_DA is not set
# CONFIG_BLK_DEV_DAC960 is not set
CONFIG_BLK_DEV_LOOP=y
CONFIG_BLK_DEV_NBD=m
CONFIG_BLK_DEV_RAM=y
CONFIG_BLK_DEV_RAM_SIZE=6144
# CONFIG_BLK_DEV_INITRD is not set

#
# Multi-device support (RAID and LVM)
#
CONFIG_MD=y
# CONFIG_BLK_DEV_MD is not set
# CONFIG_MD_LINEAR is not set
# CONFIG_MD_RAID0 is not set
# CONFIG_MD_RAID1 is not set
# CONFIG_MD_RAID5 is not set
# CONFIG_MD_MULTIPATH is not set
CONFIG_BLK_DEV_LVM=m

#
# Networking options
#
CONFIG_PACKET=y
CONFIG_PACKET_MMAP=y
CONFIG_NETLINK_DEV=y
CONFIG_NETFILTER=y
CONFIG_NETFILTER_DEBUG=y
CONFIG_FILTER=y
CONFIG_UNIX=y
CONFIG_INET=y
CONFIG_IP_MULTICAST=y
# CONFIG_IP_ADVANCED_ROUTER is not set
# CONFIG_IP_PNP is not set
# CONFIG_NET_IPIP is not set
# CONFIG_NET_IPGRE is not set
# CONFIG_IP_MROUTE is not set
# CONFIG_ARPD is not set
# CONFIG_INET_ECN is not set
# CONFIG_SYN_COOKIES is not set

#
#   IP: Netfilter Configuration
#
CONFIG_IP_NF_CONNTRACK=m
CONFIG_IP_NF_FTP=m
# CONFIG_IP_NF_IRC is not set
# CONFIG_IP_NF_QUEUE is not set
CONFIG_IP_NF_IPTABLES=m
CONFIG_IP_NF_MATCH_LIMIT=m
CONFIG_IP_NF_MATCH_MAC=m
CONFIG_IP_NF_MATCH_MARK=m
CONFIG_IP_NF_MATCH_MULTIPORT=m
CONFIG_IP_NF_MATCH_TOS=m
# CONFIG_IP_NF_MATCH_AH_ESP is not set
# CONFIG_IP_NF_MATCH_LENGTH is not set
# CONFIG_IP_NF_MATCH_TTL is not set
CONFIG_IP_NF_MATCH_TCPMSS=m
CONFIG_IP_NF_MATCH_STATE=m
CONFIG_IP_NF_MATCH_UNCLEAN=m
CONFIG_IP_NF_MATCH_OWNER=m
CONFIG_IP_NF_FILTER=m
CONFIG_IP_NF_TARGET_REJECT=m
CONFIG_IP_NF_TARGET_MIRROR=m
CONFIG_IP_NF_NAT=m
CONFIG_IP_NF_NAT_NEEDED=y
CONFIG_IP_NF_TARGET_MASQUERADE=m
CONFIG_IP_NF_TARGET_REDIRECT=m
# CONFIG_IP_NF_NAT_SNMP_BASIC is not set
CONFIG_IP_NF_NAT_FTP=m
CONFIG_IP_NF_MANGLE=m
CONFIG_IP_NF_TARGET_TOS=m
CONFIG_IP_NF_TARGET_MARK=m
CONFIG_IP_NF_TARGET_LOG=m
# CONFIG_IP_NF_TARGET_ULOG is not set
CONFIG_IP_NF_TARGET_TCPMSS=m
CONFIG_IP_NF_COMPAT_IPCHAINS=m
CONFIG_IP_NF_NAT_NEEDED=y
CONFIG_IP_NF_COMPAT_IPFWADM=m
CONFIG_IP_NF_NAT_NEEDED=y
# CONFIG_IPV6 is not set
# CONFIG_KHTTPD is not set
# CONFIG_ATM is not set
# CONFIG_VLAN_8021Q is not set
# CONFIG_IPX is not set
# CONFIG_ATALK is not set
CONFIG_DECNET=m
# CONFIG_DECNET_SIOCGIFCONF is not set
# CONFIG_DECNET_ROUTER is not set
# CONFIG_BRIDGE is not set
# CONFIG_X25 is not set
# CONFIG_LAPB is not set
# CONFIG_LLC is not set
# CONFIG_NET_DIVERT is not set
# CONFIG_ECONET is not set
# CONFIG_WAN_ROUTER is not set
# CONFIG_NET_FASTROUTE is not set
# CONFIG_NET_HW_FLOWCONTROL is not set

#
# QoS and/or fair queueing
#
# CONFIG_NET_SCHED is not set

#
# ATA/IDE/MFM/RLL support
#
# CONFIG_IDE is not set
# CONFIG_BLK_DEV_IDE_MODES is not set
# CONFIG_BLK_DEV_HD is not set

#
# SCSI support
#
CONFIG_SCSI=y
CONFIG_BLK_DEV_SD=y
CONFIG_SD_EXTRA_DEVS=40
CONFIG_CHR_DEV_ST=y
# CONFIG_CHR_DEV_OSST is not set
CONFIG_BLK_DEV_SR=y
# CONFIG_BLK_DEV_SR_VENDOR is not set
CONFIG_SR_EXTRA_DEVS=2
CONFIG_CHR_DEV_SG=y
# CONFIG_SCSI_DEBUG_QUEUES is not set
# CONFIG_SCSI_MULTI_LUN is not set
# CONFIG_SCSI_CONSTANTS is not set
# CONFIG_SCSI_LOGGING is not set

#
# SCSI low-level drivers
#
# CONFIG_BLK_DEV_3W_XXXX_RAID is not set
# CONFIG_SCSI_7000FASST is not set
# CONFIG_SCSI_ACARD is not set
# CONFIG_SCSI_AHA152X is not set
# CONFIG_SCSI_AHA1542 is not set
# CONFIG_SCSI_AHA1740 is not set
# CONFIG_SCSI_AACRAID is not set
# CONFIG_SCSI_AIC7XXX is not set
# CONFIG_SCSI_AIC7XXX_OLD is not set
# CONFIG_SCSI_DPT_I2O is not set
# CONFIG_SCSI_ADVANSYS is not set
# CONFIG_SCSI_IN2000 is not set
# CONFIG_SCSI_AM53C974 is not set
# CONFIG_SCSI_MEGARAID is not set
# CONFIG_SCSI_BUSLOGIC is not set
# CONFIG_SCSI_CPQFCTS is not set
# CONFIG_SCSI_DMX3191D is not set
# CONFIG_SCSI_DTC3280 is not set
# CONFIG_SCSI_EATA is not set
# CONFIG_SCSI_EATA_DMA is not set
# CONFIG_SCSI_EATA_PIO is not set
# CONFIG_SCSI_FUTURE_DOMAIN is not set
# CONFIG_SCSI_GDTH is not set
# CONFIG_SCSI_GENERIC_NCR5380 is not set
# CONFIG_SCSI_INITIO is not set
# CONFIG_SCSI_INIA100 is not set
# CONFIG_SCSI_PPA is not set
# CONFIG_SCSI_IMM is not set
# CONFIG_SCSI_NCR53C406A is not set
CONFIG_SCSI_LASI700=y
CONFIG_53C700_MEM_MAPPED=y
CONFIG_53C700_LE_ON_BE=y
CONFIG_53C700_USE_CONSISTENT=y
# CONFIG_SCSI_NCR53C7xx is not set
# CONFIG_SCSI_SYM53C8XX_2 is not set
# CONFIG_SCSI_NCR53C8XX is not set
CONFIG_SCSI_SYM53C8XX=y
CONFIG_SCSI_ZALON=y
CONFIG_SCSI_NCR53C8XX_DEFAULT_TAGS=8
CONFIG_SCSI_NCR53C8XX_MAX_TAGS=32
CONFIG_SCSI_NCR53C8XX_SYNC=20
# CONFIG_SCSI_NCR53C8XX_PROFILE is not set
# CONFIG_SCSI_NCR53C8XX_IOMAPPED is not set
# CONFIG_SCSI_NCR53C8XX_SYMBIOS_COMPAT is not set
# CONFIG_SCSI_PAS16 is not set
# CONFIG_SCSI_PCI2000 is not set
# CONFIG_SCSI_PCI2220I is not set
# CONFIG_SCSI_PSI240I is not set
# CONFIG_SCSI_QLOGIC_FAS is not set
# CONFIG_SCSI_QLOGIC_ISP is not set
# CONFIG_SCSI_QLOGIC_FC is not set
# CONFIG_SCSI_QLOGIC_1280 is not set
# CONFIG_SCSI_SIM710 is not set
# CONFIG_SCSI_SYM53C416 is not set
# CONFIG_SCSI_DC390T is not set
# CONFIG_SCSI_T128 is not set
# CONFIG_SCSI_U14_34F is not set
# CONFIG_SCSI_DEBUG is not set

#
# PCMCIA SCSI adapter support
#
# CONFIG_SCSI_PCMCIA is not set

#
# Network device support
#
CONFIG_NETDEVICES=y

#
# ARCnet devices
#
# CONFIG_ARCNET is not set
CONFIG_DUMMY=m
# CONFIG_BONDING is not set
# CONFIG_EQUALIZER is not set
CONFIG_TUN=m
# CONFIG_ETHERTAP is not set

#
# Ethernet (10 or 100Mbit)
#
CONFIG_NET_ETHERNET=y
CONFIG_LASI_82596=y
# CONFIG_SUNLANCE is not set
CONFIG_HAPPYMEAL=m
# CONFIG_SUNBMAC is not set
# CONFIG_SUNQE is not set
# CONFIG_SUNGEM is not set
# CONFIG_NET_VENDOR_3COM is not set
# CONFIG_LANCE is not set
# CONFIG_NET_VENDOR_SMC is not set
# CONFIG_NET_VENDOR_RACAL is not set
# CONFIG_AT1700 is not set
# CONFIG_DEPCA is not set
# CONFIG_HP100 is not set
# CONFIG_NET_ISA is not set
# CONFIG_NET_PCI is not set
# CONFIG_NET_POCKET is not set

#
# Ethernet (1000 Mbit)
#
CONFIG_ACENIC=m
# CONFIG_ACENIC_OMIT_TIGON_I is not set
# CONFIG_DL2K is not set
# CONFIG_MYRI_SBUS is not set
# CONFIG_NS83820 is not set
CONFIG_HAMACHI=m
CONFIG_YELLOWFIN=m
CONFIG_SK98LIN=m
# CONFIG_FDDI is not set
# CONFIG_HIPPI is not set
# CONFIG_PLIP is not set
# CONFIG_PPP is not set
# CONFIG_SLIP is not set

#
# Wireless LAN (non-hamradio)
#
# CONFIG_NET_RADIO is not set

#
# Token Ring devices
#
# CONFIG_TR is not set
# CONFIG_NET_FC is not set
# CONFIG_RCPCI is not set
# CONFIG_SHAPER is not set

#
# Wan interfaces
#
# CONFIG_WAN is not set

#
# PCMCIA network device support
#
# CONFIG_NET_PCMCIA is not set

#
# Input core support
#
# CONFIG_INPUT is not set
# CONFIG_INPUT_KEYBDEV is not set
# CONFIG_INPUT_MOUSEDEV is not set
# CONFIG_INPUT_JOYDEV is not set
# CONFIG_INPUT_EVDEV is not set

#
# Character devices
#
CONFIG_VT=y
CONFIG_VT_CONSOLE=y
CONFIG_GSC_PS2=y
CONFIG_HIL=y
CONFIG_SERIAL=y
CONFIG_SERIAL_CONSOLE=y
CONFIG_SERIAL_GSC=y
# CONFIG_SERIAL_EXTENDED is not set
# CONFIG_SERIAL_NONSTANDARD is not set
CONFIG_UNIX98_PTYS=y
CONFIG_UNIX98_PTY_COUNT=256
CONFIG_PRINTER=y
# CONFIG_LP_CONSOLE is not set
# CONFIG_PPDEV is not set

#
# I2C support
#
# CONFIG_I2C is not set

#
# Mice
#
# CONFIG_BUSMOUSE is not set
CONFIG_MOUSE=y
CONFIG_PSMOUSE=y
# CONFIG_82C710_MOUSE is not set
# CONFIG_PC110_PAD is not set

#
# Joysticks
#
# CONFIG_INPUT_GAMEPORT is not set
# CONFIG_QIC02_TAPE is not set

#
# Watchdog Cards
#
# CONFIG_WATCHDOG is not set
CONFIG_GENRTC=y
# CONFIG_INTEL_RNG is not set
# CONFIG_NVRAM is not set
# CONFIG_RTC is not set
# CONFIG_DTLK is not set
# CONFIG_R3964 is not set
# CONFIG_APPLICOM is not set

#
# Ftape, the floppy tape device driver
#
# CONFIG_FTAPE is not set
# CONFIG_AGP is not set
# CONFIG_DRM is not set

#
# PCMCIA character devices
#
# CONFIG_PCMCIA_SERIAL_CS is not set

#
# Multimedia devices
#
# CONFIG_VIDEO_DEV is not set

#
# File systems
#
# CONFIG_QUOTA is not set
# CONFIG_AUTOFS_FS is not set
CONFIG_AUTOFS4_FS=y
CONFIG_REISERFS_FS=y
# CONFIG_REISERFS_CHECK is not set
# CONFIG_REISERFS_PROC_INFO is not set
# CONFIG_ADFS_FS is not set
# CONFIG_ADFS_FS_RW is not set
# CONFIG_AFFS_FS is not set
# CONFIG_HFS_FS is not set
# CONFIG_BFS_FS is not set
CONFIG_EXT3_FS=y
CONFIG_JBD=y
# CONFIG_JBD_DEBUG is not set
# CONFIG_FAT_FS is not set
# CONFIG_MSDOS_FS is not set
# CONFIG_UMSDOS_FS is not set
# CONFIG_VFAT_FS is not set
# CONFIG_EFS_FS is not set
# CONFIG_JFFS_FS is not set
# CONFIG_JFFS2_FS is not set
# CONFIG_CRAMFS is not set
CONFIG_TMPFS=y
# CONFIG_RAMFS is not set
CONFIG_ISO9660_FS=y
CONFIG_JOLIET=y
# CONFIG_ZISOFS is not set
# CONFIG_MINIX_FS is not set
# CONFIG_VXFS_FS is not set
# CONFIG_NTFS_FS is not set
# CONFIG_NTFS_RW is not set
# CONFIG_HPFS_FS is not set
CONFIG_PROC_FS=y
# CONFIG_DEVFS_FS is not set
# CONFIG_DEVFS_MOUNT is not set
# CONFIG_DEVFS_DEBUG is not set
CONFIG_DEVPTS_FS=y
# CONFIG_QNX4FS_FS is not set
# CONFIG_QNX4FS_RW is not set
# CONFIG_ROMFS_FS is not set
CONFIG_EXT2_FS=y
# CONFIG_SYSV_FS is not set
# CONFIG_UDF_FS is not set
# CONFIG_UDF_RW is not set
# CONFIG_UFS_FS is not set
# CONFIG_UFS_FS_WRITE is not set

#
# Network File Systems
#
# CONFIG_CODA_FS is not set
# CONFIG_INTERMEZZO_FS is not set
CONFIG_NFS_FS=y
CONFIG_NFS_V3=y
# CONFIG_ROOT_NFS is not set
CONFIG_NFSD=y
CONFIG_NFSD_V3=y
CONFIG_SUNRPC=y
CONFIG_LOCKD=y
CONFIG_LOCKD_V4=y
# CONFIG_SMB_FS is not set
# CONFIG_NCP_FS is not set
# CONFIG_NCPFS_PACKET_SIGNING is not set
# CONFIG_NCPFS_IOCTL_LOCKING is not set
# CONFIG_NCPFS_STRONG is not set
# CONFIG_NCPFS_NFS_NS is not set
# CONFIG_NCPFS_OS2_NS is not set
# CONFIG_NCPFS_SMALLDOS is not set
# CONFIG_NCPFS_NLS is not set
# CONFIG_NCPFS_EXTRAS is not set
# CONFIG_ZISOFS_FS is not set
# CONFIG_ZLIB_FS_INFLATE is not set

#
# Partition Types
#
# CONFIG_PARTITION_ADVANCED is not set
CONFIG_MSDOS_PARTITION=y
# CONFIG_SMB_NLS is not set
CONFIG_NLS=y

#
# Native Language Support
#
CONFIG_NLS_DEFAULT="iso8859-1"
# CONFIG_NLS_CODEPAGE_437 is not set
# CONFIG_NLS_CODEPAGE_737 is not set
# CONFIG_NLS_CODEPAGE_775 is not set
# CONFIG_NLS_CODEPAGE_850 is not set
# CONFIG_NLS_CODEPAGE_852 is not set
# CONFIG_NLS_CODEPAGE_855 is not set
# CONFIG_NLS_CODEPAGE_857 is not set
# CONFIG_NLS_CODEPAGE_860 is not set
# CONFIG_NLS_CODEPAGE_861 is not set
# CONFIG_NLS_CODEPAGE_862 is not set
# CONFIG_NLS_CODEPAGE_863 is not set
# CONFIG_NLS_CODEPAGE_864 is not set
# CONFIG_NLS_CODEPAGE_865 is not set
# CONFIG_NLS_CODEPAGE_866 is not set
# CONFIG_NLS_CODEPAGE_869 is not set
# CONFIG_NLS_CODEPAGE_936 is not set
# CONFIG_NLS_CODEPAGE_950 is not set
# CONFIG_NLS_CODEPAGE_932 is not set
# CONFIG_NLS_CODEPAGE_949 is not set
# CONFIG_NLS_CODEPAGE_874 is not set
# CONFIG_NLS_ISO8859_8 is not set
# CONFIG_NLS_CODEPAGE_1250 is not set
# CONFIG_NLS_CODEPAGE_1251 is not set
# CONFIG_NLS_ISO8859_1 is not set
# CONFIG_NLS_ISO8859_2 is not set
# CONFIG_NLS_ISO8859_3 is not set
# CONFIG_NLS_ISO8859_4 is not set
# CONFIG_NLS_ISO8859_5 is not set
# CONFIG_NLS_ISO8859_6 is not set
# CONFIG_NLS_ISO8859_7 is not set
# CONFIG_NLS_ISO8859_9 is not set
# CONFIG_NLS_ISO8859_13 is not set
# CONFIG_NLS_ISO8859_14 is not set
# CONFIG_NLS_ISO8859_15 is not set
# CONFIG_NLS_KOI8_R is not set
# CONFIG_NLS_KOI8_U is not set
# CONFIG_NLS_UTF8 is not set

#
# Console drivers
#

#
# Frame-buffer support
#
# CONFIG_FB is not set
CONFIG_STI_CONSOLE=y
CONFIG_DUMMY_CONSOLE=y
CONFIG_DUMMY_CONSOLE=y
CONFIG_FBCON=y
CONFIG_FBCON_FONT=y
CONFIG_FONT_8x8=y
CONFIG_FONT_8x16=y
CONFIG_FONT_6x11=y
CONFIG_FONT_SUN12x22=y

#
# Sound
#
CONFIG_SOUND=y
# CONFIG_SOUND_BT878 is not set
# CONFIG_SOUND_CMPCI is not set
# CONFIG_SOUND_EMU10K1 is not set
# CONFIG_MIDI_EMU10K1 is not set
# CONFIG_SOUND_FUSION is not set
# CONFIG_SOUND_CS4281 is not set
# CONFIG_SOUND_ES1370 is not set
# CONFIG_SOUND_ES1371 is not set
# CONFIG_SOUND_ESSSOLO1 is not set
# CONFIG_SOUND_MAESTRO is not set
# CONFIG_SOUND_MAESTRO3 is not set
# CONFIG_SOUND_ICH is not set
CONFIG_SOUND_HARMONY=y
# CONFIG_SOUND_RME96XX is not set
# CONFIG_SOUND_SONICVIBES is not set
# CONFIG_SOUND_TRIDENT is not set
# CONFIG_SOUND_MSNDCLAS is not set
# CONFIG_SOUND_MSNDPIN is not set
# CONFIG_SOUND_VIA82CXXX is not set
# CONFIG_MIDI_VIA82CXXX is not set
# CONFIG_SOUND_OSS is not set
# CONFIG_SOUND_TVMIXER is not set

#
# USB support
#
CONFIG_USB=m
# CONFIG_USB_DEBUG is not set
CONFIG_USB_DEVICEFS=y
# CONFIG_USB_BANDWIDTH is not set
# CONFIG_USB_LONG_TIMEOUT is not set
# CONFIG_USB_UHCI is not set
# CONFIG_USB_UHCI_ALT is not set
CONFIG_USB_OHCI=m
# CONFIG_USB_AUDIO is not set
# CONFIG_USB_BLUETOOTH is not set
CONFIG_USB_STORAGE=m
# CONFIG_USB_STORAGE_DEBUG is not set
# CONFIG_USB_STORAGE_DATAFAB is not set
# CONFIG_USB_STORAGE_FREECOM is not set
# CONFIG_USB_STORAGE_ISD200 is not set
# CONFIG_USB_STORAGE_DPCM is not set
# CONFIG_USB_STORAGE_HP8200e is not set
# CONFIG_USB_STORAGE_SDDR09 is not set
# CONFIG_USB_STORAGE_JUMPSHOT is not set
# CONFIG_USB_ACM is not set
# CONFIG_USB_PRINTER is not set
# CONFIG_USB_DC2XX is not set
# CONFIG_USB_MDC800 is not set
# CONFIG_USB_SCANNER is not set
# CONFIG_USB_MICROTEK is not set
# CONFIG_USB_HPUSBSCSI is not set
# CONFIG_USB_PEGASUS is not set
# CONFIG_USB_KAWETH is not set
# CONFIG_USB_CATC is not set
# CONFIG_USB_CDCETHER is not set
# CONFIG_USB_USBNET is not set
# CONFIG_USB_USS720 is not set

#
# USB Serial Converter support
#
# CONFIG_USB_SERIAL is not set
# CONFIG_USB_SERIAL_GENERIC is not set
# CONFIG_USB_SERIAL_BELKIN is not set
# CONFIG_USB_SERIAL_WHITEHEAT is not set
# CONFIG_USB_SERIAL_DIGI_ACCELEPORT is not set
# CONFIG_USB_SERIAL_EMPEG is not set
# CONFIG_USB_SERIAL_FTDI_SIO is not set
# CONFIG_USB_SERIAL_VISOR is not set
# CONFIG_USB_SERIAL_IPAQ is not set
# CONFIG_USB_SERIAL_IR is not set
# CONFIG_USB_SERIAL_EDGEPORT is not set
# CONFIG_USB_SERIAL_KEYSPAN_PDA is not set
# CONFIG_USB_SERIAL_KEYSPAN is not set
# CONFIG_USB_SERIAL_KEYSPAN_USA28 is not set
# CONFIG_USB_SERIAL_KEYSPAN_USA28X is not set
# CONFIG_USB_SERIAL_KEYSPAN_USA28XA is not set
# CONFIG_USB_SERIAL_KEYSPAN_USA28XB is not set
# CONFIG_USB_SERIAL_KEYSPAN_USA19 is not set
# CONFIG_USB_SERIAL_KEYSPAN_USA18X is not set
# CONFIG_USB_SERIAL_KEYSPAN_USA19W is not set
# CONFIG_USB_SERIAL_KEYSPAN_USA49W is not set
# CONFIG_USB_SERIAL_MCT_U232 is not set
# CONFIG_USB_SERIAL_KLSI is not set
# CONFIG_USB_SERIAL_PL2303 is not set
# CONFIG_USB_SERIAL_CYBERJACK is not set
# CONFIG_USB_SERIAL_XIRCOM is not set
# CONFIG_USB_SERIAL_OMNINET is not set
# CONFIG_USB_RIO500 is not set

#
# Kernel hacking
#
CONFIG_MAGIC_SYSRQ=y
CONFIG_KDB=y
CONFIG_KDB_MODULES=y
CONFIG_KDB_OFF=y
CONFIG_KALLSYMS=y

Re: [parisc-linux] kdb_v21 branch updated to -pa26, and kallsyms cross-compile

[Carlos O'Donell Jr.]

> > Send your .config?
> Attached

Here's your problem:
...
CONFIG_KDB_OFF=y
...

Either set that to 'CONFIG_KDB_OFF=n'
or boot with 'kdb=on' as a kernel paramter.
(Checkout the help text in the kernel hacking option).

Some of this stuff changed in the latest kdb version.

I'm not sure why the kernel can't find the FW scsi controller.
That will be problem number two :)

c.

Re: [parisc-linux] kdb_v21 branch updated to -pa26, and kallsyms cross-compile

[Patrick Caulfield]

On Wed, May 29, 2002 at 08:21:07AM -0400, Carlos O'Donell Jr. wrote:
> > > Send your .config?
> > Attached
> 
> Here's your problem:
> ...
> CONFIG_KDB_OFF=y
> ...

That's only set like that as a last-dich attempt to get it to work :-(

I'm going to have to give up on this, I can't spend all week trying to get it to
work. What I don't understand is that I move a working .config to the new kernel
source and both the serial console AND the scsi stop working.

Ah well, it was a nice idea while it lasted. It's just a bit hard debugging code
when the only error you get is "Stack pointer and cr30 do not cor
respond" repeated endlessly....

patrick

Re: [parisc-linux] kdb_v21 branch updated to -pa26, and kallsyms cross-compile

[Carlos O'Donell Jr.]

> 
> That's only set like that as a last-dich attempt to get it to work :-(
> 
> I'm going to have to give up on this, I can't spend all week trying to get it to
> work. What I don't understand is that I move a working .config to the new kernel
> source and both the serial console AND the scsi stop working.
> 
> Ah well, it was a nice idea while it lasted. It's just a bit hard debugging code
> when the only error you get is "Stack pointer and cr30 do not cor
> respond" repeated endlessly....
> 
> patrick
>

You can't always copy a .config from kernel to kernel. The kernel source
dictates what will be _in_ the .config. I usually run 'make mrproper'
and then have 'make oldconfig' or 'make ???config' recreate the config files
to suit the material in the kernel.

When switching to a new source tree I recommend:
make mrproper
make oldconfig
make menuconfig (to suit your tastes)
...


As for the endless 'Stack pointer and cr30 do not correspond!'....

I believe that is a bug in traps.c and I have code to give a proper dump.
I haven't been able to get anyone who knows to explain how the dump_stack in 
traps should _really_ work :)

AFAI understand the following works (I've tested it on my kernels with what 
looks to be a successfull dump while doing some bad things (props to Bame
for helping me out) ;)

BTW, what led me to this solution is that the printk in the else is
completely bogus... so I rewrote the else.

Q: When do you get 'Stack pointer and cr30 do not correspond'?

==========
--- ./linux/arch/parisc/kernel/traps.c     Tue May 21 00:01:37 2002
+++ ./linux/arch/parisc/kernel/traps.c     Tue May 21 00:30:42 2002
@@ -189,10 +189,25 @@
                }
                else
                {
-                   /* Stack Dump! */
-                   printk(KERN_CRIT "WARNING! Stack pointer and cr30 do not correspond!\n");
-                   printk(KERN_CRIT "Dumping virtual address stack instead\n");
-                   dump_stack((unsigned long)__va(stack_start), (unsigned long)__va(sp), 0);
+
+                   stack_start = sp & ~(INIT_TASK_SIZE - 1);
+                   if (stack_start == cr30) {
+
+                       /* We're in a non-interrupt stack and cr30 matches
+                          the start of the stack */
+
+                       dump_stack(stack_start, sp, 0);
+
+                   }
+                   else
+                   {
+
+                       /* Stack Dump! */
+                       printk(KERN_CRIT "WARNING! Stack pointer and cr30 do not correspond!\n");
+                       printk(KERN_CRIT "Dumping virtual address stack instead\n");
+                       dump_stack((unsigned long)__va(stack_start), (unsigned long)__va(sp), 0);
+
+                   }
                }
        }
 #endif
========== 

Re: [parisc-linux] kdb_v21 branch updated to -pa26, and kallsyms cross-compile

[Patrick Caulfield]

On Wed, May 29, 2002 at 11:01:18AM -0400, Carlos O'Donell Jr. wrote:
> >
> 
> You can't always copy a .config from kernel to kernel. The kernel source
> dictates what will be _in_ the .config. I usually run 'make mrproper'
> and then have 'make oldconfig' or 'make ???config' recreate the config files
> to suit the material in the kernel.
> 
> When switching to a new source tree I recommend:
> make mrproper
> make oldconfig
> make menuconfig (to suit your tastes)

Oh, I'm doing that. I just tried it again, it was either that or throw it out
of the window.

Is there parisc version of the kdb patch I could try applying to a kernel
source I know works maybe ?

> As for the endless 'Stack pointer and cr30 do not correspond!'....
> 
> I believe that is a bug in traps.c and I have code to give a proper dump.
> I haven't been able to get anyone who knows to explain how the dump_stack in 
> traps should _really_ work :)

Thanks, I'll try that out.
 
> AFAI understand the following works (I've tested it on my kernels with what 
> looks to be a successfull dump while doing some bad things (props to Bame
> for helping me out) ;)
> 
> BTW, what led me to this solution is that the printk in the else is
> completely bogus... so I rewrote the else.
> 
> Q: When do you get 'Stack pointer and cr30 do not correspond'?

When it hits my buggy code :-) 

patrick

Re: [parisc-linux] kdb_v21 branch updated to -pa26, and kallsyms cross-compile

[Carlos O'Donell Jr.]

> 
> Oh, I'm doing that. I just tried it again, it was either that or throw it out
> of the window.
> 
> Is there parisc version of the kdb patch I could try applying to a kernel
> source I know works maybe ?
>

We are trying not to maintian patches but rather a branch of the
kernel representing common-2 + parisc specific kdb changes.

Look at this if you want to see the patch method:
http://lists.parisc-linux.org/pipermail/parisc-linux/2002-May/016246.html

The kdb_v21 branch is where all the changes and fixes will go :)

c. 

Re: [parisc-linux] kdb_v21 branch updated to -pa26, and kallsyms cross-compile

[Patrick Caulfield]

On Wed, May 29, 2002 at 01:26:31PM -0400, Carlos O'Donell Jr. wrote:
> > 
> > Oh, I'm doing that. I just tried it again, it was either that or throw it out
> > of the window.
> > 
> > Is there parisc version of the kdb patch I could try applying to a kernel
> > source I know works maybe ?
> >
> 
> We are trying not to maintian patches but rather a branch of the
> kernel representing common-2 + parisc specific kdb changes.

I can understand the logic of that and if it worked for me I would regard it as
the best solution to the problem if maintaing two sets of patches.
 
> Look at this if you want to see the patch method:
> http://lists.parisc-linux.org/pipermail/parisc-linux/2002-May/016246.html

Thanks, I'll try that on my Debian kernel and see what happens. Despite my
frustrations I really do want to get kdb working on this box. I like my HP box a
lot and I've got some kernel code that really does need fixing for that
platform.

+ we have a long weekend off coming up here in Britain and it's the perfect
diversion for that essay I really have to write ... :-)
 
patrick

Re: [parisc-linux] kdb_v21 branch updated to -pa26, and kallsyms cross-compile

[Patrick Caulfield]

Hmmm

CONFIG_KDB=y      : no serial console or FW SCSI
CONFIG_KDB=n      : all works fine.

bizarre!

patrick

Re: [parisc-linux] kdb_v21 branch updated to -pa26, and kallsyms cross-compile

[Patrick Caulfield]

On Thu, May 30, 2002 at 01:35:15PM -0400, Carlos O'Donell Jr. wrote:
> > Hmmm
> > CONFIG_KDB=y      : no serial console or FW SCSI
> > CONFIG_KDB=n      : all works fine.
> > bizarre!
> > patrick
> >
> 
> Did you try building+booting from the kdb patches?

Yes, exactly the same results. There's some thing different about the
binary vmlinux thatmay, or may not, be relevant. The kdb one seems to
have fewer segments than a non-kdb one:

(Normal boot:)
ELF32 executable
Entry 00100000 first 00100000 n 6
Segment 0 load 00100000 size 1937528 mediaptr 0x1000
Segment 1 load 002da000 size 295576 mediaptr 0x1db000
Segment 2 load 00324000 size 247332 mediaptr 0x224000
Segment 3 load 00364000 size 8192 mediaptr 0x261000
Segment 4 load 00368000 size 32768 mediaptr 0x263000
Segment 5 load 00391084 size 97664 mediaptr 0x26b084
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

(total segment size: 2619060)


KDB boot:
ELF32 executable
Entry 00100000 first 00100000 n 4
Segment 0 load 00100000 size 2035156 mediaptr 0x1000
Segment 1 load 002f2000 size 692152 mediaptr 0x1f2000
Segment 2 load 0039c000 size 253952 mediaptr 0x29b000
Segment 3 load 003e0000 size 32768 mediaptr 0x2d9000
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

(total segment size: 3014028)


Patrick

Re: [parisc-linux] kdb_v21 branch updated to -pa26, and kallsyms cross-compile

[Carlos O'Donell Jr.]

> 
> Yes, exactly the same results. There's some thing different about the
> binary vmlinux thatmay, or may not, be relevant. The kdb one seems to
> have fewer segments than a non-kdb one:
> 

Yes. Something is broke.

I just recently cleaned up my src trees and rebuilt a
kdb enabled kernel and I get the same result on my 712/60.

/me puts thinking cap on...

The _interesting_ thing would be to diff the System.map's
for kdb-on vs. kdb-off to see is anything is explicitly being
removed.

I'll start a build going.

c.

Re: [parisc-linux] kdb_v21 branch updated to -pa26, and kallsyms cross-compile

[Patrick Caulfield]

On Fri, May 31, 2002 at 08:54:19AM -0400, Carlos O'Donell Jr. wrote:
> > 
> > Yes, exactly the same results. There's some thing different about the
> > binary vmlinux thatmay, or may not, be relevant. The kdb one seems to
> > have fewer segments than a non-kdb one:
> > 
> 
> Yes. Something is broke.
> 
> I just recently cleaned up my src trees and rebuilt a
> kdb enabled kernel and I get the same result on my 712/60.

I'm glad it's not just me :-)
 
> /me puts thinking cap on...
> 
> The _interesting_ thing would be to diff the System.map's
> for kdb-on vs. kdb-off to see is anything is explicitly being
> removed.

My guess was the the scsi __init functions were not getting called for some
reason, I have the System.map files for both builds but they both look OK (not
that I ful understand the kernel __init system though) 


patrick

Re: [parisc-linux] kdb_v21 branch updated to -pa26, and kallsyms cross-compile

[Carlos O'Donell Jr.]

> 
> > The _interesting_ thing would be to diff the System.map's
> > for kdb-on vs. kdb-off to see is anything is explicitly being
> > removed.
> 
> My guess was the the scsi __init functions were not getting called for some
> reason, I have the System.map files for both builds but they both look OK (not
> that I ful understand the kernel __init system though) 
>

Yeah, I've run through the kdb and non-kdb builds and everything
is okay. 

I think there are two maybe three places where kdb initializes 
certain structures during startup. I'm going to have to check 
those paths to see how far it gets before dying.

Any comments from the crowd would be helpfull :)

/me goes off to add some printk's and extra checks
c. 

Re: [parisc-linux] kdb_v21 branch updated to -pa26, and kallsyms cross-compile

[Randolph Chung]

> I think there are two maybe three places where kdb initializes 
> certain structures during startup. I'm going to have to check 
> those paths to see how far it gets before dying.
> 
> Any comments from the crowd would be helpfull :)
> 
> /me goes off to add some printk's and extra check

i've been offline for a bit so i might have missed something... but aiui
the symptom you've been seeing is that it hangs at the "If this is the
last message you see" message? has anyone tried to compile a kernel with
early bootup messages (there's a #define in pdc_cons.c to enable this)
and see if they get farther?

there are some debugging stuff that you can turn on in
arch/parisc/kernel/unwind.c ... that piece of code has caused some hangs 
in the past, you might want to enable those printks as well.

randolph
-- 
   @..@                                         http://www.TauSq.org/
  (----)
 ( >__< )
 ^^ ~~ ^^

Re: [parisc-linux] kdb_v21 branch updated to -pa26, and kallsyms cross-compile

[joel.soete]

Hi Randolph,

I remember that I do it when you suggest it and iirc it help to goes further in
the boot. But I could not confirm at 100% because I had some hpmc problem with
my b2000 test server. Sorry, i will try to solved this problem first then come
back to you.

Joel

Quoting Randolph Chung <randolph@tausq.org>:

> > I think there are two maybe three places where kdb initializes 
> > certain structures during startup. I'm going to have to check 
> > those paths to see how far it gets before dying.
> > 
> > Any comments from the crowd would be helpfull :)
> > 
> > /me goes off to add some printk's and extra check
> 
> i've been offline for a bit so i might have missed something... but
> aiui
> the symptom you've been seeing is that it hangs at the "If this is the
> last message you see" message? has anyone tried to compile a kernel
> with
> early bootup messages (there's a #define in pdc_cons.c to enable this)
> and see if they get farther?
> 
> there are some debugging stuff that you can turn on in
> arch/parisc/kernel/unwind.c ... that piece of code has caused some hangs
> 
> in the past, you might want to enable those printks as well.
> 
> randolph
> -- 
>    @..@                                         http://www.TauSq.org/
>   (----)
>  ( >__< )
>  ^^ ~~ ^^
> 
> _______________________________________________
> parisc-linux mailing list
> parisc-linux@lists.parisc-linux.org
> http://lists.parisc-linux.org/mailman/listinfo/parisc-linux
> 
> 


-------------------------------------------------
This mail sent through Tiscali Webmail (http://webmail.tiscali.be)

Re: [parisc-linux] kdb_v21 branch updated to -pa26, and kallsyms cross-compile

[Carlos O'Donell Jr.]

> 
> i've been offline for a bit so i might have missed something... but aiui
> the symptom you've been seeing is that it hangs at the "If this is the
> last message you see" message? has anyone tried to compile a kernel with
> early bootup messages (there's a #define in pdc_cons.c to enable this)
> and see if they get farther?
> 
> there are some debugging stuff that you can turn on in
> arch/parisc/kernel/unwind.c ... that piece of code has caused some hangs 
> in the past, you might want to enable those printks as well.
> 
> randolph

Yeah I've seen the code in pdc_cons.c, but I didn't know about 
the issues with the stack unwinding (though I just read JDA's
comments in the code... so I'll look at that).

I'll hack on this tonight and see how far I get.
Currently my test box is turned off, and since I haven't
built my remote power switch (spp + solid state relay) ....
I can't reboot the sucker :}

Thanks to the external led I know that the box (712/60) doesn't 
get far since it never reaches the pdc soft power button 
initialization routine (__init power_init).

c.

Re: [parisc-linux] kdb_v21 branch updated to -pa26, and kallsyms cross-compile

[Patrick Caulfield]

On Tue, Jun 04, 2002 at 08:49:54AM -0700, Randolph Chung wrote:
> > I think there are two maybe three places where kdb initializes 
> > certain structures during startup. I'm going to have to check 
> > those paths to see how far it gets before dying.
> > 
> > Any comments from the crowd would be helpfull :)
> > 
> > /me goes off to add some printk's and extra check
> 
> i've been offline for a bit so i might have missed something... but aiui
> the symptom you've been seeing is that it hangs at the "If this is the
> last message you see" message? has anyone tried to compile a kernel with
> early bootup messages (there's a #define in pdc_cons.c to enable this)
> and see if they get farther?
> 
> there are some debugging stuff that you can turn on in
> arch/parisc/kernel/unwind.c ... that piece of code has caused some hangs 
> in the past, you might want to enable those printks as well.


The odd thing is that is just seems to disable the FW SCSI and the serial
console. If I hook up a monitor (rather a feat of equopment mbving in my house
unfortunately!) I can see the boot getting as far as failing to mount the root
filesystem.

patrick

Re: [parisc-linux] kdb_v21 branch updated to -pa26, and kallsyms cross-compile

[joel.soete]

Hi all,

It seems that the b2000 I used to test gcc-3.2 does not crash anymore :) with
all kernels :)) (pl 2.4.18 or my stuff on 2.4.19)? (I feel that fs corruption
occurs and was not detected immideately?)

Well I come back to you to see what should be the useable kdb config (to
investigate the network problem with kernel compiled with gcc-3.1 or -3.2).

Mine is now:
CONFIG_MAGIC_SYSRQ=Y
CONFIG_KDB=Y
CONFIG_KDB_MODULES=Y
# CONFIG_KDB_OFF IS NOT SET
CONFIG_KALLSYMS=Y

Thanks a lot,
    Joel

Quoting Randolph Chung <randolph@tausq.org>:

> > I think there are two maybe three places where kdb initializes 
> > certain structures during startup. I'm going to have to check 
> > those paths to see how far it gets before dying.
> > 
> > Any comments from the crowd would be helpfull :)
> > 
> > /me goes off to add some printk's and extra check
> 
> i've been offline for a bit so i might have missed something... but
> aiui
> the symptom you've been seeing is that it hangs at the "If this is the
> last message you see" message? has anyone tried to compile a kernel
> with
> early bootup messages (there's a #define in pdc_cons.c to enable this)
> and see if they get farther?
> 
> there are some debugging stuff that you can turn on in
> arch/parisc/kernel/unwind.c ... that piece of code has caused some hangs
> 
> in the past, you might want to enable those printks as well.
> 
> randolph
> -- 
>    @..@                                         http://www.TauSq.org/
>   (----)
>  ( >__< )
>  ^^ ~~ ^^
> 
> _______________________________________________
> parisc-linux mailing list
> parisc-linux@lists.parisc-linux.org
> http://lists.parisc-linux.org/mailman/listinfo/parisc-linux
> 
> 


-------------------------------------------------
This mail sent through Tiscali Webmail (http://webmail.tiscali.be)

Re: [parisc-linux] kdb_v21 branch updated to -pa26, and kallsyms cross-compile

[Randolph Chung]

> Mine is now:
> CONFIG_MAGIC_SYSRQ=Y
> CONFIG_KDB=Y
> CONFIG_KDB_MODULES=Y
> # CONFIG_KDB_OFF IS NOT SET
> CONFIG_KALLSYMS=Y
> 

that looks fine.

randolph

Re: [parisc-linux] kdb_v21 branch updated to -pa26, and kallsyms cross-compile

[Carlos O'Donell Jr.]

> 
> Well I come back to you to see what should be the useable kdb config (to
> investigate the network problem with kernel compiled with gcc-3.1 or -3.2).
> 
> Mine is now:
> CONFIG_MAGIC_SYSRQ=Y
> CONFIG_KDB=Y
> CONFIG_KDB_MODULES=Y
> # CONFIG_KDB_OFF IS NOT SET
> CONFIG_KALLSYMS=Y
> 
> Thanks a lot,
>     Joel
>

Does you system boot with kdb enabled?

I think I might have gotten a bit farther, I have a few
hours to do more testing tonight and I'll post later.

c. 

Re: [parisc-linux] kdb_v21 branch updated to -pa26, and kallsyms cross-compile

[joel.soete]

Hi Carlos,

Quoting "Carlos O'Donell Jr." <carlos@baldric.uwo.ca>:

> > 
> > Well I come back to you to see what should be the useable kdb config
> (to
> > investigate the network problem with kernel compiled with gcc-3.1 or
> -3.2).
> > 
> > Mine is now:
> > CONFIG_MAGIC_SYSRQ=Y
> > CONFIG_KDB=Y
> > CONFIG_KDB_MODULES=Y
> > # CONFIG_KDB_OFF IS NOT SET
> > CONFIG_KALLSYMS=Y
> > 
> > Thanks a lot,
> >     Joel
> >
> 
> Does you system boot with kdb enabled?

Now I had a kdb kernel (cvs branch KDB_21) compile with gcc-3.2 and also #define
EARLY_BOOTUP_DEBUG 1. But this kernel hang on:
...
Search for devices...

And the green diode on the ide-cdrom of my b2000 stay on continuously.


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

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



-------------------------------------------------
This mail sent through Tiscali Webmail (http://webmail.tiscali.be)

[parisc-linux] Verify stack trace address - Joel

[Carlos O'Donell Jr.]

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. 

Re: [parisc-linux] Verify stack trace address - Joel

[joel.soete]

Hi C,

Two news (a bad and a good as usual).

I had actually an hardware problem with this test b2000 so that I could not any
more reboot it.
So the bad news is that I could not verify anything right now.

For the good news is that we have maintenance contract and the problem occurs
now during the launch of stm under hpux.

So I can open a call and pieces are already order to repair it Monday.

Quoting "Carlos O'Donell Jr." <carlos@baldric.uwo.ca>:

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

I will check it asap and let you inform

> 
> 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!!) :)
> 
Have a nice week-end,
    Joel


-------------------------------------------------
This mail sent through Tiscali Webmail (http://webmail.tiscali.be)