Simpler Navigation for Servers and Operating Systems - Please Update Your Bookmarks
Completed: a much simpler Servers and Operating Systems section of the Community. We combined many of the older boards, so you won't have to click through so many levels to get at the information you need. Check the consolidated boards here as many sub-forums are now single boards.
If you have bookmarked forums or discussion boards in Servers and Operating Systems, we suggest you check and update them as needed.
Operating System - Tru64 Unix
cancel
Showing results for 
Search instead for 
Did you mean: 

es4100 crash when boot up trap: invalid memory read access from kernel mode

邹英琼_1
Occasional Contributor

es4100 crash when boot up trap: invalid memory read access from kernel mode

Compaq Tru64 UNIX P5.1A (Rev. 646); Sat Jan 25 03:26:26 EST 2003
Aug 22 13:03:37 scserver1 vmunix: physical memory = 2048.00 megabytes.
Aug 22 13:03:37 scserver1 vmunix: available memory = 1983.47 megabytes.
Aug 22 13:03:37 scserver1 vmunix: using 7784 buffers containing 60.81 megabytes of memory
Aug 22 13:03:37 scserver1 vmunix: Master cpu at slot 0
Aug 22 13:03:37 scserver1 vmunix: Starting secondary cpu 1
Aug 22 13:03:37 scserver1 vmunix: Firmware revision: 6.0
Aug 22 13:03:37 scserver1 vmunix: PALcode: UNIX version 1.23
Aug 22 13:03:37 scserver1 vmunix: AlphaServer 4100 5/533 4MB
Aug 22 13:03:37 scserver1 vmunix: pci1 (primary bus:1) at mcbus0 slot 5
Aug 22 13:03:37 scserver1 vmunix: Loading SIOP: script c0000000, reg 7faee00, data c000a000
Aug 22 13:03:37 scserver1 vmunix: scsi0 at psiop0 slot 0 rad 0
Aug 22 13:03:37 scserver1 vmunix: isp0 at pci1 slot 2
Aug 22 13:03:37 scserver1 vmunix: isp0: QLOGIC ISP1040B/V2
Aug 22 13:03:37 scserver1 vmunix: isp0: Firmware revision 5.57 (loaded by console)
Aug 22 13:03:37 scserver1 vmunix: isp0: Fast RAM timing enabled.
Aug 22 13:03:37 scserver1 vmunix: scsi1 at isp0 slot 0 rad 0
Aug 22 13:03:37 scserver1 vmunix: tu0: DECchip 21143: Revision: 3.0
Aug 22 13:03:37 scserver1 vmunix: tu0: auto negotiation capable device
Aug 22 13:03:37 scserver1 vmunix: tu0 at pci1 slot 4
Aug 22 13:03:37 scserver1 vmunix: tu0: DEC TULIP (10/100) Ethernet Interface, hardware address: 08-00-2B-C4-65-03
Aug 22 13:03:37 scserver1 vmunix: tu0: auto negotiation off: selecting 10BaseT (UTP) port: half duplex
Aug 22 13:03:37 scserver1 vmunix: pci0 (primary bus:0) at mcbus0 slot 4
Aug 22 13:03:37 scserver1 vmunix: eisa0 at pci0
Aug 22 13:03:37 scserver1 vmunix: ace0 at eisa0
Aug 22 13:03:37 scserver1 vmunix: ace1 at eisa0
Aug 22 13:03:37 scserver1 vmunix: comet0: Card type 'Elsa GLoria' with 8MB framebuffer memory.
Aug 22 13:03:37 scserver1 vmunix: comet0 at pci0 slot 2
Aug 22 13:03:37 scserver1 vmunix: mchan0: Module revision = 35
Aug 22 13:03:37 scserver1 vmunix: mchan0: jumpered as VH0 configuration
Aug 22 13:03:37 scserver1 vmunix: mchan0 at pci0 slot 3
Aug 22 13:03:37 scserver1 vmunix: emx0 at pci0 slot 4
Aug 22 13:03:37 scserver1 vmunix: KGPSA-BC : Driver Rev 2.06 : F/W Rev 3.03A1(1.31) : wwn 1000-0000-c922-553c
Aug 22 13:03:37 scserver1 vmunix: emx0: Using console topology setting of : Fabric
Aug 22 13:03:37 scserver1 vmunix: scsi2 at emx0 slot 0 rad 0
Aug 22 13:03:37 scserver1 vmunix: Created FRU table binary error log packet
Aug 22 13:03:37 scserver1 vmunix: kernel console: ace0
Aug 22 13:03:37 scserver1 vmunix: i2c: Server Management Hardware Present
Aug 22 13:03:37 scserver1 vmunix: dli: configured
Aug 22 13:03:37 scserver1 vmunix: NetRAIN configured.
Aug 22 13:03:37 scserver1 vmunix: TruCluster Server V5.1A (Rev. 1312); 01/25/03 02:08
Aug 22 13:03:37 scserver1 vmunix: TNC kproc_creator_daemon: Initialized and Ready
Aug 22 13:03:37 scserver1 vmunix: clubase: configured
Aug 22 13:03:37 scserver1 vmunix: Configuring RDG to use Memory Channel
Aug 22 13:03:37 scserver1 vmunix: ics_hl: Configuring memory channel as transport.
Aug 22 13:03:37 scserver1 vmunix: icsnet: configured
Aug 22 13:03:37 scserver1 vmunix: drd configured 0
Aug 22 13:03:37 scserver1 vmunix: kch: configured
Aug 22 13:03:37 scserver1 vmunix: dlm: configured
Aug 22 13:03:37 scserver1 vmunix: Starting CFS daemons
Aug 22 13:03:37 scserver1 vmunix: Registering CFS Services
Aug 22 13:03:37 scserver1 vmunix: Initializing CFSREC ICS Service
Aug 22 13:03:37 scserver1 vmunix: Registering CFSMSFS remote syscall interface
Aug 22 13:03:37 scserver1 vmunix: Registering CMS Services
Aug 22 13:03:37 scserver1 vmunix: rm slave: mchan0, hubslot = 0, phys_rail 0 (size 128 MB)
Aug 22 13:03:37 scserver1 vmunix: rm slave: log_rail 0 (size 128 MB), phys_rail 0 (mchan0)
Aug 22 13:03:37 scserver1 vmunix: ics_mct: icsinfo set for node 1
Aug 22 13:03:37 scserver1 vmunix: ics_mct: Declaring this node up 1
Aug 22 13:03:37 scserver1 vmunix: ics_mct: icsinfo set for node 2
Aug 22 13:03:37 scserver1 vmunix: CNX MGR: Join operation complete
Aug 22 13:03:37 scserver1 vmunix: CNX MGR: membership configuration index: 2 (2 additions, 0 removals)
Aug 22 13:03:37 scserver1 vmunix: CNX MGR: quorum (re)gained, (re)starting cluster operations.
Aug 22 13:03:37 scserver1 vmunix: Joining versw kch set.
Aug 22 13:03:37 scserver1 vmunix: CNX MGR: Node scserver1 1 incarn 0x563a8 csid 0x10002 has been added to the cluster
Aug 22 13:03:37 scserver1 vmunix: ics_mct: Declaring this node up 2
Aug 22 13:03:37 scserver1 vmunix: CNX MGR: Node scserver2 2 incarn 0xe3903 csid 0x10001 has been added to the cluster
Aug 22 13:03:37 scserver1 vmunix: dlm: resuming lock activity
Aug 22 13:03:37 scserver1 vmunix: kch: resuming activity
Aug 22 13:03:37 scserver1 vmunix: clsm: incoming CNX data: '卆 '
Aug 22 13:03:37 scserver1 vmunix: clsm: checking for peer configurations
Aug 22 13:03:37 scserver1 vmunix: clsm: initialized
Aug 22 13:03:37 scserver1 vmunix: Waiting for cluster mount to complete
Aug 22 13:03:37 scserver1 vmunix: vm_swap_init: swap is set to eager allocation mode
Aug 22 13:03:37 scserver1 vmunix: CMS: Joining deferred filesystem sets
Aug 22 13:03:37 scserver1 vmunix: CNX QDISK: Successfully claimed quorum disk, adding 1 vote.
Aug 22 13:04:09 scserver1 vmunix: cluster alias subsystem enabled
Aug 22 13:04:19 scserver1 vmunix: Environmental Monitoring Subsystem Configured.
Aug 22 13:17:26 scserver1 vmunix: Alpha boot: available memory from 0x3e44000 to 0x7fff6000
Aug 22 13:17:26 scserver1 vmunix: Compaq Tru64 UNIX V5.1A (Rev. 1885); Mon Aug 22 13:07:51 CST 2005
Aug 22 13:17:26 scserver1 vmunix: physical memory = 2048.00 megabytes.
Aug 22 13:17:26 scserver1 vmunix: available memory = 1985.69 megabytes.
Aug 22 13:17:26 scserver1 vmunix: using 7793 buffers containing 60.88 megabytes of memory
Aug 22 13:17:26 scserver1 vmunix: Master cpu at slot 0
Aug 22 13:17:26 scserver1 vmunix: Starting secondary cpu 1
Aug 22 13:17:26 scserver1 vmunix: Firmware revision: 6.0
Aug 22 13:17:26 scserver1 vmunix: PALcode: UNIX version 1.23
Aug 22 13:17:26 scserver1 vmunix: AlphaServer 4100 5/533 4MB
Aug 22 13:17:26 scserver1 vmunix: pci1 (primary bus:1) at mcbus0 slot 5
Aug 22 13:17:26 scserver1 vmunix: Loading SIOP: script c0000000, reg 7faee00, data c000a000
Aug 22 13:17:26 scserver1 vmunix: scsi0 at psiop0 slot 0 rad 0
Aug 22 13:17:26 scserver1 vmunix: isp0 at pci1 slot 2
Aug 22 13:17:26 scserver1 vmunix: isp0: QLOGIC ISP1040B/V2
Aug 22 13:17:26 scserver1 vmunix: isp0: Firmware revision 5.57 (loaded by console)
Aug 22 13:17:26 scserver1 vmunix: isp0: Fast RAM timing enabled.
Aug 22 13:17:26 scserver1 vmunix: scsi1 at isp0 slot 0 rad 0
Aug 22 13:17:26 scserver1 vmunix: tu0: DECchip 21143: Revision: 3.0
Aug 22 13:17:26 scserver1 vmunix: tu0: auto negotiation capable device
Aug 22 13:17:26 scserver1 vmunix: tu0 at pci1 slot 4
Aug 22 13:17:26 scserver1 vmunix: tu0: DEC TULIP (10/100) Ethernet Interface, hardware address: 08-00-2B-C4-65-03
Aug 22 13:17:26 scserver1 vmunix: tu0: auto negotiation off: selecting 10BaseT (UTP) port: half duplex
Aug 22 13:17:26 scserver1 vmunix: pci0 (primary bus:0) at mcbus0 slot 4
Aug 22 13:17:26 scserver1 vmunix: eisa0 at pci0
Aug 22 13:17:26 scserver1 vmunix: ace0 at eisa0
Aug 22 13:17:26 scserver1 vmunix: ace1 at eisa0
Aug 22 13:17:26 scserver1 vmunix: comet0: Card type 'Elsa GLoria' with 8MB framebuffer memory.
Aug 22 13:17:26 scserver1 vmunix: comet0 at pci0 slot 2
Aug 22 13:17:26 scserver1 vmunix: mchan0: Module revision = 35
Aug 22 13:17:26 scserver1 vmunix: mchan0: jumpered as VH0 configuration
Aug 22 13:17:26 scserver1 vmunix: mchan0 at pci0 slot 3
Aug 22 13:17:26 scserver1 vmunix: emx0 at pci0 slot 4
Aug 22 13:17:26 scserver1 vmunix: KGPSA-BC : Driver Rev 2.06 : F/W Rev 3.03A1(1.31) : wwn 1000-0000-c922-553c
Aug 22 13:17:26 scserver1 vmunix: emx0: Using console topology setting of : Fabric
Aug 22 13:17:26 scserver1 vmunix: scsi2 at emx0 slot 0 rad 0
Aug 22 13:17:26 scserver1 vmunix: Created FRU table binary error log packet
Aug 22 13:17:26 scserver1 vmunix: kernel console: ace0
Aug 22 13:17:26 scserver1 vmunix: dli: configured
Aug 22 13:17:26 scserver1 vmunix: NetRAIN configured.
Aug 22 13:17:26 scserver1 vmunix: ATM Subsystem configured with 2 restart threads
Aug 22 13:17:26 scserver1 vmunix: ATMUNI: configured
Aug 22 13:17:26 scserver1 vmunix: ATMSIG: 3.x (module=uni3x) configured
Aug 22 13:17:26 scserver1 vmunix: ILMI: 3.x (module=ilmi) configured
Aug 22 13:17:26 scserver1 vmunix: ATM IP: configured
Aug 22 13:17:26 scserver1 vmunix: ATM LANE: configured.
Aug 22 13:17:26 scserver1 vmunix: ATM IFMP: configured
Aug 22 13:17:26 scserver1 vmunix: TruCluster Server V5.1A (Rev. 1312); 01/25/03 02:08
Aug 22 13:17:26 scserver1 vmunix: TNC kproc_creator_daemon: Initialized and Ready
Aug 22 13:17:26 scserver1 vmunix: clubase: configured
Aug 22 13:17:26 scserver1 vmunix: Configuring RDG to use Memory Channel
Aug 22 13:17:26 scserver1 vmunix: ics_hl: Configuring memory channel as transport.
Aug 22 13:17:26 scserver1 vmunix: icsnet: configured
Aug 22 13:17:26 scserver1 vmunix: drd configured 0
Aug 22 13:17:26 scserver1 vmunix: kch: configured
Aug 22 13:17:26 scserver1 vmunix: dlm: configured
Aug 22 13:17:26 scserver1 vmunix: Starting CFS daemons
Aug 22 13:17:26 scserver1 vmunix: Registering CFS Services
Aug 22 13:17:26 scserver1 vmunix: Initializing CFSREC ICS Service
Aug 22 13:17:26 scserver1 vmunix: Registering CFSMSFS remote syscall interface
Aug 22 13:17:26 scserver1 vmunix: i2c: Server Management Hardware Present
Aug 22 13:17:26 scserver1 vmunix: Registering CMS Services
Aug 22 13:17:26 scserver1 vmunix: rm slave: mchan0, hubslot = 0, phys_rail 0 (size 128 MB)
Aug 22 13:17:26 scserver1 vmunix: rm slave: log_rail 0 (size 128 MB), phys_rail 0 (mchan0)
Aug 22 13:17:26 scserver1 vmunix: ics_mct: icsinfo set for node 1
Aug 22 13:17:26 scserver1 vmunix: ics_mct: Declaring this node up 1
Aug 22 13:17:26 scserver1 vmunix: ics_mct: icsinfo set for node 2
Aug 22 13:17:26 scserver1 vmunix: CNX MGR: Join operation complete
Aug 22 13:17:26 scserver1 vmunix: CNX MGR: membership configuration index: 4 (3 additions, 1 removals)
Aug 22 13:17:26 scserver1 vmunix: CNX MGR: quorum (re)gained, (re)starting cluster operations.
Aug 22 13:17:26 scserver1 vmunix: Joining versw kch set.
Aug 22 13:17:26 scserver1 vmunix: CNX MGR: Node scserver1 1 incarn 0xa13d0 csid 0x20002 has been added to the cluster
Aug 22 13:17:26 scserver1 vmunix: ics_mct: Declaring this node up 2
Aug 22 13:17:26 scserver1 vmunix: CNX MGR: Node scserver2 2 incarn 0xe3903 csid 0x10001 has been added to the cluster
Aug 22 13:17:26 scserver1 vmunix: dlm: resuming lock activity
Aug 22 13:17:26 scserver1 vmunix: kch: resuming activity
Aug 22 13:17:26 scserver1 vmunix: cam_logger: SCSI event packet
Aug 22 13:17:26 scserver1 vmunix: cam_logger: bus 1
Aug 22 13:17:26 scserver1 vmunix: isp_reinit
Aug 22 13:17:26 scserver1 vmunix: clsm: incoming CNX data: '卆 '
Aug 22 13:17:26 scserver1 vmunix: Beginning Adapter/Chip reinitialization (0x1)
Aug 22 13:17:26 scserver1 vmunix: cam_logger: SCSI event packet
Aug 22 13:17:26 scserver1 vmunix: cam_logger: bus 1
Aug 22 13:17:26 scserver1 vmunix: isp_cam_bus_reset_tmo
Aug 22 13:17:26 scserver1 vmunix: SCSI Bus Reset performed
Aug 22 13:17:26 scserver1 vmunix: clsm: checking for peer configurations
Aug 22 13:17:26 scserver1 vmunix: clsm: initialized
Aug 22 13:17:26 scserver1 vmunix: Waiting for cluster mount to complete
Aug 22 13:17:26 scserver1 vmunix: vm_swap_init: swap is set to eager allocation mode
Aug 22 13:17:26 scserver1 vmunix: CMS: Joining deferred filesystem sets
Aug 22 13:17:26 scserver1 vmunix: CNX QDISK: Successfully claimed quorum disk, adding 1 vote.
Aug 22 13:17:32 scserver1 vmunix: cluster alias subsystem enabled
Aug 22 13:17:43 scserver1 vmunix: Environmental Monitoring Subsystem Configured.
Aug 22 13:17:46 scserver1 vmunix:
Aug 22 13:17:46 scserver1 vmunix: trap: invalid memory read access from kernel mode
Aug 22 13:17:46 scserver1 vmunix:
Aug 22 13:17:46 scserver1 vmunix: faulting virtual address: 0x0000000000000010
Aug 22 13:17:46 scserver1 vmunix: pc of faulting instruction: 0xfffffc00007c683c
Aug 22 13:17:46 scserver1 vmunix: ra contents at time of fault: 0xfffffc000083e8bc
Aug 22 13:21:28 scserver1 vmunix: sp contents at time of fault: 0xfffffe04a1e4f230
Aug 22 13:21:28 scserver1 vmunix:
Aug 22 13:21:28 scserver1 vmunix: panic (cpu 0): kernel memory fault
Aug 22 13:21:28 scserver1 vmunix: syncing disks...
9 REPLIES
邹英琼_1
Occasional Contributor

Re: es4100 crash when boot up trap: invalid memory read access from kernel mode

i test my hardware ,no problem from in my computer .

os: 5.1a, trucluster 5.1,DATABASE:ORACLE
Ross Minkov
Esteemed Contributor

Re: es4100 crash when boot up trap: invalid memory read access from kernel mode

From SRM try:

>>> test

did you see any problems reported?

>>> show memory

did you see all of the memory you had reported?

-Ross
邹英琼_1
Occasional Contributor

Re: es4100 crash when boot up trap: invalid memory read access from kernel mode

i test my memory ,is good ,

>>> test

no errolg found .

>>>show memeory

is ok ,no error found .

Venkatesh BL
Honored Contributor

Re: es4100 crash when boot up trap: invalid memory read access from kernel mode

Did you try booting through 'genvmunix'? May be the crash files in /var/adm/crash would have some useful info.
Michael Schulte zur Sur
Honored Contributor

Re: es4100 crash when boot up trap: invalid memory read access from kernel mode

Hi,

what version is your patch kit?

greetings,

Michael
Ivan Ferreira
Honored Contributor

Re: es4100 crash when boot up trap: invalid memory read access from kernel mode

Are you able to boot in single user mode?

boot -fl s

Are you able to boot one node at the time?
Por que hacerlo dificil si es posible hacerlo facil? - Why do it the hard way, when you can do it the easy way?
Aaron Biver_2
Frequent Advisor

Re: es4100 crash when boot up trap: invalid memory read access from kernel mode

please post the stack trace. This can be obtained this way, for example:

# ksh
# dbx -k /var/adm/crash/vm*.$((`cat bounds` - 1)) <t
q
EOF
(this runs dbx on the most recent crashdump, gets the stack trace, then quits)
Martin Moore
HPE Pro

Re: es4100 crash when boot up trap: invalid memory read access from kernel mode

Your EISA configuration information in NVRAM might be corrupt. This is particularly likely if you've recently upgraded the o/s or firmware on the system.

Try re-running the ECU (EISA Configuration Utility). Just bring it up, do "Save & Exit", then power-cycle the system and try to boot it.

Martin
I work for HP
A quick resolution to technical issues for your HP Enterprise products is just a click away HP Support Center Knowledge-base
See Self Help Post for more details

Ralf Puchner
Honored Contributor

Re: es4100 crash when boot up trap: invalid memory read access from kernel mode

a "invalid memory read access from kernel mode" is not hardware related. A crash analyze without a crash-data file is useless and if the crash-data file does not contain known issues you must provide the crash itself and vmzcore.

But a crash analyze need time and knowledge, so please open a call within the HP support center.
Help() { FirstReadManual(urgently); Go_to_it;; }