Author Topic: 3300 MX alwasy reboot (HwReset)  (Read 1212 times)

Offline ksrichard

  • New Member
  • *
  • Posts: 3
  • Country: tw
  • Karma: +0/-0
    • View Profile
3300 MX alwasy reboot (HwReset)
« on: February 02, 2017, 08:18:19 PM »
my 3300 MX can not boot successfully it always reboot , Please help me what is wrong with it

MITEL SYSTEM ROM R2.2/1 Oct  5 2006 (83)

CCA Number          : 56005413 RB.2
System Model        : 00470000 F200
CPU Model           : 8250 R0064
Reset Config        : 04043047
Bus Clock (MHz)     : 66
CPM Clock (MHz)     : 198
Core Clock (MHz)    : 297
Internal Memory Map : f0000000
Main Memory (MB)    : 256
Local Memory (MB)   : 16
Flash Memory (MB)   : 2
MAC Address         : 08000f16f1c1
MMC CPLD            : R2
ATA CPLD            : R3
POST Bypass         : 0
Watchdog Bypass     : 0
Slot Id             : 0


Disk Configuration Started.
Creating block device for controller  0 drive 0... done.
Creating CBIO device for controller  0 drive 0... done.
Attaching to partition table for 4 partitions on controller 0 drive 0... done.
Creating Cache Layer for partition 0 (/ata00) on controller 0 drive 0... done.
Creating Dos FS device for partition 0 (/ata00) on controller 0 drive 0... done.

Disk Configuration Complete.
Loading /ata00/Rtc8260...54993488
Starting at 0x10000...


Disk Configuration Started.
Creating block device for controller  0 drive 0... done.
Creating CBIO device for controller  0 drive 0... done.
Attaching to partition table for 4 partitions on controller 0 drive 0... done.
Creating Cache Layer for partition 0 (/sysro) on controller 0 drive 0... done.
Creating Cache Layer for partition 1 (/db) on controller 0 drive 0... done.
Creating Cache Layer for partition 2 (/vmail) on controller 0 drive 0... done.
Creating Dos FS device for partition 0 (/sysro) on controller 0 drive 0... done.

Creating Dos FS device for partition 1 (/db) on controller 0 drive 0... done.
Creating Dos FS device for partition 2 (/vmail) on controller 0 drive 0... done.

Disk Configuration Complete.
/vmail/  - disk check in progress ...






FAT handler information:
------------------------
 - allocation group size:       59 clusters
 - free space on volume:        2,165,559,296 bytes
Attached TCP/IP interface to motfcc unit 0
Attaching interface lo0...done
Unable to add route to 192.168.0.0; errno = 0xffffffff.

Adding 130012 symbols for standalone.
Last reset cause was (0x83) POWER_ON_RESET
->

There is no host relink.
There is no relink on the disk.
02/02/2017 15:50:53> SoftLog - WARNING - MSPLogServer - OtpLogs.cpp(57)
   PostSoftwareLogA: Called before calling OtpLogStartup

02/02/2017 15:50:53> SoftLog - INFO    - MIFSM - MiFsmEventUtil.cpp(25)
   Internal Message
RegisterEventUtil - Task: N/A
Registering event utility for FSM engine ID 0

02/02/2017 15:50:53> SoftLog - INFO    - MIFSM - MiFsmEventUtil.cpp(25)
   Internal Message
RegisterEventUtil - Task: N/A
Registering event utility for FSM engine ID 2

relink_call_ctors start
relink_call_ctors done

Executing S10startup script



Call Engine Layer Coordinator SUCCESSFULLY started.

Reminder: use -d option when running dbasrv from command line.
UDT msgsys userID is 199489392.
ENABLING COMMANDS

instruction access
Exception next instruction address: 0x33cc33cc
Machine Status Register: 0x4000b032
Condition Register: 0x50000059
Task: 0x36756c0 "Emu68k"
Database verification passed: /db/nvmdb/files/databver.db
Database verification passed: /db/nvmdb/files/nvmusers.db

ignore dup exception

instruction access
Exception next instruction address: 0x33cc33cc
Machine Status Register: 0x4000b032
Condition Register: 0x50000059

instruction access
Exception next instruction address: 0x33cc33cc
Machine Status Register: 0x4000b032
Condition Register: 0x50000059

instruction access
Exception next instruction address: 0x33cc33cc
Machine Status Register: 0x4000b032
Condition Register: 0x50000059
0x3671c40 (SysPreMort0): MccVerifyChParamaters::semTake-> 0 errno: 3997697 FAILE
D
0x3671c40 (SysPreMort0): MccVerifyChParamaters::semTake-> 0 errno: 3997697 FAILE
D
Task SysPreMort0 being deleted while ACTIVE
Raised Critical Alarm on Stale Tasks
RaiseAlarm alarm severity critical, forcing machine shutdown
MnTftp: waiting for thread to terminate. 98 seconds left.
WARNING-System shutdown requested by task: tTMonitor
Critical Alarm being raised upon detecting the following task suspended: Emu68k
taskId 0x36756c0 crash time FRI FEB 03 07:45:19 2017

MnTftp:Thread terminate signal received
MnFileCache: waiting for thread to terminate. 18 seconds left.
MnFileCache: thread terminate signal received
0x367df40 (HwReset): ==> WARNING: System Shutdown about to

MITEL SYSTEM ROM R2.2/1 Oct  5 2006 (103)

CCA Number          : 56005413 RB.2
System Model        : 00470000 F200
CPU Model           : 8250 R0064
Reset Config        : 04043047
Bus Clock (MHz)     : 66
CPM Clock (MHz)     : 198
Core Clock (MHz)    : 297
Internal Memory Map : f0000000
Main Memory (MB)    : 256
Local Memory (MB)   : 16
Flash Memory (MB)   : 2
MAC Address         : 08000f16f1c1
MMC CPLD            : R2
ATA CPLD            : R3
POST Bypass         : 0
Watchdog Bypass     : 0
Slot Id             : 0


Offline ralph

  • Mitel Forums Admin
  • Hero Member
  • *****
  • Posts: 5739
  • Country: us
  • Karma: +468/-0
  • Published Author: http://amzn.to/2dcYSY5
    • View Profile
Re: 3300 MX alwasy reboot (HwReset)
« Reply #1 on: February 03, 2017, 07:51:20 AM »
I think you probably have defective hardware.

Ralph


 

Sitemap 1 2 3 4 5 6 7 8 9 10