Dahua DH-NVR5208-P не включается (перегрет, не грузится kernel)

trass
Сообщения: 9
Зарегистрирован: 28 апр 2016, 20:49

Dahua DH-NVR5208-P не включается (перегрет, не грузится kernel)

Сообщение trass » 30 май 2017, 23:25

Здравствуйте! Есть 2 аппарата Dahua DH-NVR5208-P. Оба с заклинившими вентиляторами процессора TI8168-GP rev 2.1 и с потемневшей платой возле проца. Питания вроде как все в норме. Хотя одна цепь питания проца (потемневшая ) выдает 1В - не знаю нормальное или нет.
Вот то, что выдает после
setenv dh_keyboard 0
saveenv
reset:

Код: Выделить всё

U-Boot 2010.06-svn785 (Jul 03 2013 - 17:50:07)

TI8168-GP rev 2.1

ARM clk: 1200MHz
DDR clk: 796MHz
DSP clk: 813MHz
IVA clk: 531MHz
M3  clk: 250MHz

DRAM:  1 GiB
SPI:   info: found S25FL256S (32MiB)
Net:   Detected MACID:90:2:a9:b4:56:64
Ethernet PHY: GENERIC[0x70431] @ 0x00
DaVinci EMAC
Hit any key to stop autoboot:  0
SPI:   info: found S25FL256S (32MiB)
SPI probe: 32768 KiB S25FL256S at 0:0 is now current device
### CRAMFS loading '/boot/uImage' to 0x81000000
### CRAMFS load complete: 2593340 bytes loaded to 0x81000000
## Booting kernel from Legacy Image at 81000000 ...
   Image Name:   Linux-2.6.37
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2593276 Bytes = 2.5 MiB
   Load Address: 80008000
   Entry Point:  80008000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.
Linux version 2.6.37 (jenkins@localhost.localdomain) (gcc version 4.3.3 (Sourcery G++ Lite 2009q1-203) ) #1 Wed Sep 18 11:17:09 CST 2013, svn:2492
CPU: ARMv7 Processor [413fc082] revision 2 (ARMv7), cr=10c53c7f
CPU: VIPT nonaliasing data cache, VIPT aliasing instruction cache
Machine: ti8168evm
pcie: x2/gen1
reserved size = 0 at 0x0
Memory policy: ECC disabled, Data cache writeback
OMAP chip is TI8168 2.0
Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 68580
Kernel command line: mem=270M console=ttyO0,115200n8 rootfstype=cramfs root=/dev/mtdblock1 notifyk.vpssm3_sva=0xBFD00000 pcie=gen1 bpa2parts=dma:97M:0x8ac00000

dh_keyboard=0 load_modules=1 watchdog=1
bpa2: partition 'dma' created at 0x8ac00000, size 99328 kB (0x06100000 B)
PID hash table entries: 2048 (order: 1, 8192 bytes)
Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
Memory: 270MB = 270MB total
Memory: 169052k/169052k available, 107428k reserved, 0K highmem
Virtual kernel memory layout:
    vector  : 0xffff0000 - 0xffff1000   (   4 kB)
    fixmap  : 0xfff00000 - 0xfffe0000   ( 896 kB)
    DMA     : 0xffc00000 - 0xffe00000   (   2 MB)
    vmalloc : 0xd1000000 - 0xf8000000   ( 624 MB)
    lowmem  : 0xc0000000 - 0xd0e00000   ( 270 MB)
    pkmap   : 0xbfe00000 - 0xc0000000   (   2 MB)
    modules : 0xbf000000 - 0xbfe00000   (  14 MB)
      .init : 0xc0008000 - 0xc003d000   ( 212 kB)
      .text : 0xc003d000 - 0xc04ef000   (4808 kB)
      .data : 0xc04f0000 - 0xc0532140   ( 265 kB)
SLUB: Genslabs=11, HWalign=64, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
NR_IRQS:407
IRQ: Found an INTC at 0xfa200000 (revision 5.0) with 128 interrupts
Total of 128 interrupts on 1 active controller
GPMC revision 6.0
Trying to install interrupt handler for IRQ400
Trying to install interrupt handler for IRQ401
Trying to install interrupt handler for IRQ402
Trying to install interrupt handler for IRQ403
Trying to install interrupt handler for IRQ404
Trying to install interrupt handler for IRQ405
Trying to install interrupt handler for IRQ406
Trying to install type control for IRQ407
Trying to set irq flags for IRQ407
OMAP clockevent source: GPTIMER1 at 27000000 Hz
Console: colour dummy device 80x30
Calibrating delay loop... 1199.30 BogoMIPS (lpj=5996544)
pid_max: default: 32768 minimum: 301
Security Framework initialized
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
devtmpfs: initialized
omap_voltage_early_init: voltage driver support not added
regulator: core version 0.5
regulator: dummy:
NET: Registered protocol family 16
omap_voltage_domain_lookup: Voltage driver init not yet happened.Faulting!
omap_voltage_add_dev: VDD specified does not exist!
OMAP GPIO hardware version 0.1
OMAP GPIO hardware version 0.1
omap_mux_init: Add partition: #1: core, flags: 0
_omap_mux_get_by_name: Could not find signal i2c2_scl.i2c2_scl
_omap_mux_get_by_name: Could not find signal i2c2_sda.i2c2_sda
Configuring FLASH for boot-from-SPI
=========> audio clk init
hw-breakpoint: debug architecture 0x4 unsupported.
hw perfevents: enabled with ARMv7 Cortex-A8 PMU driver, 5 counters available
registered ti816x_sr device
pm_dbg_init: only OMAP3 supported
registered ti81xx_vpss device
registered ti81xx on-chip HDMI device
registered ti81xx_fb device
ti81xx_pcie: Invoking PCI BIOS...
ti81xx_pcie: Setting up Host Controller...
ti81xx_pcie: Register base mapped @0xd1020000
ti81xx_pcie: forcing link speed - GEN1
ti81xx_pcie: Starting PCI scan...
PCI: bus0: Fast back to back transfers enabled
bio: create slab <bio-0> at 0
vgaarb: loaded
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
USBSS revision 4ea20809
registerd cppi-dma Intr @ IRQ 17
Cppi41 Init Done
omap_i2c omap_i2c.1: bus 1 rev4.0 at 100 kHz
 [reg] 475:tps40400_probe TPS40400 exponent:-10
 [reg] 365:platform_fixup PMBUS_VOUT_SCALE_LOOP: 0xb933
 [reg] 390:platform_fixup PMBUS_IOUT_OC_FAULT_LIMIT: 0xf814
 [reg] 404:platform_fixup PMBUS_IOUT_CAL_GAIN: 0x88e5
 [reg] tps40400_get_voltage
 [reg] tps40400_check_current: Avg Output Current 2024mA!
 [reg] 169:tps40400_get_voltage Avg Current Output voltage 936718uV
regulator: pmbus_vr: 800 <--> 1050 mV at 936 mV
 [reg] 565:tps40400_probe Avg Current Output voltage 938281uV
 [reg] 575:tps40400_probe VOUT_CAL_OFFSET: 63
regulator: tps40400 probe done.
omap_i2c omap_i2c.2: bus 2 rev4.0 at 100 kHz
cfg80211: Calling CRDA to update world regulatory domain
Switching to clocksource gp timer
musb-hdrc: version 6.0, host, debug=0
musb-hdrc musb-hdrc.0: dma type: dma-cppi41
MUSB controller-0 revision 4ea20800
musb-hdrc musb-hdrc.0: MUSB HDRC host driver
musb-hdrc musb-hdrc.0: new USB bus registered, assigned bus number 1
usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb1: Product: MUSB HDRC host driver
usb usb1: Manufacturer: Linux 2.6.37 musb-hcd
usb usb1: SerialNumber: musb-hdrc.0
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 1 port detected
musb-hdrc musb-hdrc.0: USB Host mode controller at d101e000 using DMA, IRQ 18
musb-hdrc musb-hdrc.1: dma type: dma-cppi41
MUSB controller-1 revision 4ea20800
musb-hdrc musb-hdrc.1: MUSB HDRC host driver
musb-hdrc musb-hdrc.1: new USB bus registered, assigned bus number 2
usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb2: Product: MUSB HDRC host driver
usb usb2: Manufacturer: Linux 2.6.37 musb-hcd
usb usb2: SerialNumber: musb-hdrc.1
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 1 port detected
musb-hdrc musb-hdrc.1: USB Host mode controller at d1026800 using DMA, IRQ 19
NET: Registered protocol family 2
IP route cache hash table entries: 4096 (order: 2, 16384 bytes)
TCP established hash table entries: 16384 (order: 5, 131072 bytes)
TCP bind hash table entries: 16384 (order: 4, 65536 bytes)
TCP: Hash tables configured (established 16384 bind 16384)
TCP reno registered
UDP hash table entries: 256 (order: 0, 4096 bytes)
UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
NET: Registered protocol family 1
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
NetWinder Floating Point Emulator V0.97 (double precision)
PMU: registered new PMU device of type 0
Switched to NOHz mode on CPU #0
omap-iommu omap-iommu.0: ducati registered
omap-iommu omap-iommu.1: sys registered
Fun BPAMEM_init Line 409: <6>bpamem_init
JFFS2 version 2.2. (NAND) © 2001-2006 Red Hat, Inc.
ROMFS MTD (C) 2007 Red Hat, Inc.
msgmni has been set to 330
io scheduler noop registered
io scheduler deadline registered
io scheduler cfq registered (default)
Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
omap_uart.0: ttyO0 at MMIO 0x48020000 (irq = 72) is a OMAP UART0
ti81xx_interrupt 977: musb(1): VBUSERR: device may be drawing more current devctl(80) Restarting musb....
ti81xx_interrupt 977: musb(0): VBUSERR: device may be drawing more current devctl(80) Restarting musb....
console [ttyO0] enabled
omap_uart.1: ttyO1 at MMIO 0x48022000 (irq = 73) is a OMAP UART1
omap_uart.2: ttyO2 at MMIO 0x48024000 (irq = 74) is a OMAP UART2
brd: module loaded
loop: module loaded
ahci probe: devid name is ahci
ahci CAP register dump =0x6726ff81
Modified ahci CAP register dump =0x6f26ff81
ahci ahci.0: forcing PORTS_IMPL to 0x3
ahci: SSS flag set, parallel bus scan disabled
ahci ahci.0: AHCI 0001.0100 32 slots 2 ports 3 Gbps 0x3 impl platform mode
ahci ahci.0: flags: ncq sntf stag pm led clo only pmp pio slum part ccc
evm_deferred_musb_restart 850: deferred musb restart musbid(1)
evm_deferred_musb_restart 850: deferred musb restart musbid(0)
ti81xx_interrupt 977: musb(1): VBUSERR: device may be drawing more current devctl(80) Restarting musb....
evm_deferred_musb_restart 850: deferred musb restart musbid(1)
ti81xx_interrupt 977: musb(0): VBUSERR: device may be drawing more current devctl(80) Restarting musb....
evm_deferred_musb_restart 850: deferred musb restart musbid(0)
ti81xx_interrupt 977: musb(1): VBUSERR: device may be drawing more current devctl(80) Restarting musb....
evm_deferred_musb_restart 850: deferred musb restart musbid(1)
ti81xx_interrupt 977: musb(0): VBUSERR: device may be drawing more current devctl(80) Restarting musb....
evm_deferred_musb_restart 850: deferred musb restart musbid(0)
ti81xx_interrupt 977: musb(1): VBUSERR: device may be drawing more current devctl(80) Restarting musb....
evm_deferred_musb_restart 850: deferred musb restart musbid(1)
ti81xx_interrupt 977: musb(0): VBUSERR: device may be drawing more current devctl(80) Restarting musb....
evm_deferred_musb_restart 850: deferred musb restart musbid(0)
ti81xx_interrupt 977: musb(1): VBUSERR: device may be drawing more current devctl(80) Restarting musb....
evm_deferred_musb_restart 850: deferred musb restart musbid(1)
ti81xx_interrupt 977: musb(0): VBUSERR: device may be drawing more current devctl(80) Restarting musb....
evm_deferred_musb_restart 850: deferred musb restart musbid(0)
ti81xx_interrupt 977: musb(1): VBUSERR: device may be drawing more current devctl(80) Restarting musb....
evm_deferred_musb_restart 850: deferred musb restart musbid(1)
ti81xx_interrupt 977: musb(0): VBUSERR: device may be drawing more current devctl(80) Restarting musb....
evm_deferred_musb_restart 850: deferred musb restart musbid(0)
ti81xx_interrupt 977: musb(1): VBUSERR: device may be drawing more current devctl(80) Restarting musb....
evm_deferred_musb_restart 850: deferred musb restart musbid(1)
ti81xx_interrupt 977: musb(0): VBUSERR: device may be drawing more current devctl(80) Restarting musb....
evm_deferred_musb_restart 850: deferred musb restart musbid(0)
ti81xx_interrupt 977: musb(1): VBUSERR: device may be drawing more current devctl(80) Restarting musb....
evm_deferred_musb_restart 850: deferred musb restart musbid(1)
ti81xx_interrupt 977: musb(0): VBUSERR: device may be drawing more current devctl(80) Restarting musb....
evm_deferred_musb_restart 850: deferred musb restart musbid(0)
ti81xx_interrupt 977: musb(1): VBUSERR: device may be drawing more current devctl(80) Restarting musb....
evm_deferred_musb_restart 850: deferred musb restart musbid(1)
ti81xx_interrupt 977: musb(0): VBUSERR: device may be drawing more current devctl(80) Restarting musb....
evm_deferred_musb_restart 850: deferred musb restart musbid(0)
ti81xx_interrupt 977: musb(1): VBUSERR: device may be drawing more current devctl(80) Restarting musb....
evm_deferred_musb_restart 850: deferred musb restart musbid(1)
ti81xx_interrupt 977: musb(0): VBUSERR: device may be drawing more current devctl(80) Restarting musb....
evm_deferred_musb_restart 850: deferred musb restart musbid(0)
ti81xx_interrupt 977: musb(1): VBUSERR: device may be drawing more current devctl(80) Restarting musb....
evm_deferred_musb_restart 850: deferred musb restart musbid(1)
ti81xx_interrupt 977: musb(0): VBUSERR: device may be drawing more current devctl(80) Restarting musb....
evm_deferred_musb_restart 850: deferred musb restart musbid(0)
ti81xx_interrupt 977: musb(1): VBUSERR: device may be drawing more current devctl(80) Restarting musb....
evm_deferred_musb_restart 850: deferred musb restart musbid(1)
ti81xx_interrupt 977: musb(0): VBUSERR: device may be drawing more current devctl(80) Restarting musb....
evm_deferred_musb_restart 850: deferred musb restart musbid(0)
ti81xx_interrupt 977: musb(1): VBUSERR: device may be drawing more current devctl(80) Restarting musb....
evm_deferred_musb_restart 850: deferred musb restart musbid(1)
ti81xx_interrupt 977: musb(0): VBUSERR: device may be drawing more current devctl(80) Restarting musb....
evm_deferred_musb_restart 850: deferred musb restart musbid(0)
ti81xx_interrupt 977: musb(1): VBUSERR: device may be drawing more current devctl(80) Restarting musb....
evm_deferred_musb_restart 850: deferred musb restart musbid(1)
ti81xx_interrupt 977: musb(0): VBUSERR: device may be drawing more current devctl(80) Restarting musb....
evm_deferred_musb_restart 850: deferred musb restart musbid(0)
ti81xx_interrupt 977: musb(1): VBUSERR: device may be drawing more current devctl(80) Restarting musb....
evm_deferred_musb_restart 850: deferred musb restart musbid(1)
ti81xx_interrupt 977: musb(0): VBUSERR: device may be drawing more current devctl(80) Restarting musb....
evm_deferred_musb_restart 850: deferred musb restart musbid(0)
ti81xx_interrupt 977: musb(1): VBUSERR: device may be drawing more current devctl(80) Restarting musb....
evm_deferred_musb_restart 850: deferred musb restart musbid(1)
ti81xx_interrupt 977: musb(0): VBUSERR: device may be drawing more current devctl(80) Restarting musb....
evm_deferred_musb_restart 850: deferred musb restart musbid(0)
ti81xx_interrupt 977: musb(1): VBUSERR: device may be drawing more current devctl(80) Restarting musb....
evm_deferred_musb_restart 850: deferred musb restart musbid(1)
ti81xx_interrupt 977: musb(0): VBUSERR: device may be drawing more current devctl(80) Restarting musb....
evm_deferred_musb_restart 850: deferred musb restart musbid(0)
ti81xx_interrupt 977: musb(1): VBUSERR: device may be drawing more current devctl(80) Restarting musb....
evm_deferred_musb_restart 850: deferred musb restart musbid(1)



Я так понимаю, что то перегружается из-за превышения тока потребления. Может проц сдох? Подскажите, пожалуйста.
Вложения
IMG_20170530_215938.jpg
IMG_20170530_215938.jpg (425.34 КБ) 4621 просмотр

iTuneDVR
Сообщения: 3220
Зарегистрирован: 24 авг 2013, 11:05

Re: Dahua DH-NVR5208-P не включается (перегрет, не грузится kernel)

Сообщение iTuneDVR » 30 май 2017, 23:54

Это весь лог?
Стоит для чистоты эксперимента, раз уже в TTL, то сделать восстановление через run up правильным образом и лог старта сюда.

Да, печаль с вентлятором.

Адаптер питания старый или новый?

trass
Сообщения: 9
Зарегистрирован: 28 апр 2016, 20:49

Re: Dahua DH-NVR5208-P не включается (перегрет, не грузится kernel)

Сообщение trass » 31 май 2017, 00:08

Вот лог второго рега:

Код: Выделить всё

U-Boot 2010.06-svn785 (Jul 03 2013 - 17:50:07)

TI8168-GP rev 2.1

ARM clk: 1200MHz
DDR clk: 796MHz
DSP clk: 813MHz
IVA clk: 531MHz
M3  clk: 250MHz

DRAM:  1 GiB
SPI:   info: found S25FL256S (32MiB)
Net:   Detected MACID:90:2:a9:b4:56:67
Ethernet PHY: GENERIC[0xffffffff] @ 0x00
DaVinci EMAC
Hit any key to stop autoboot:  0
SPI:   info: found S25FL256S (32MiB)
SPI probe: 32768 KiB S25FL256S at 0:0 is now current device
### CRAMFS loading '/boot/uImage' to 0x81000000
### CRAMFS load complete: 2593340 bytes loaded to 0x81000000
## Booting kernel from Legacy Image at 81000000 ...
   Image Name:   Linux-2.6.37
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2593276 Bytes = 2.5 MiB
   Load Address: 80008000
   Entry Point:  80008000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.
Linux version 2.6.37 (jenkins@localhost.localdomain) (gcc version 4.3.3 (Sourcery G++ Lite 2009q1-203) ) #1 Wed Sep 18 11:17:09 CST 2013, svn:2492
CPU: ARMv7 Processor [413fc082] revision 2 (ARMv7), cr=10c53c7f
CPU: VIPT nonaliasing data cache, VIPT aliasing instruction cache
Machine: ti8168evm
pcie: x2/gen1
reserved size = 0 at 0x0
Memory policy: ECC disabled, Data cache writeback
OMAP chip is TI8168 2.0
Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 68580
Kernel command line: mem=270M console=ttyO0,115200n8 rootfstype=cramfs root=/dev/mtdblock1 notifyk.vpssm3_sva=0xBFD00000 pcie=gen1 bpa2parts=dma:97M:0x8ac00000 dh_keyboard=0 load_modules=1 watchdog=1
bpa2: partition 'dma' created at 0x8ac00000, size 99328 kB (0x06100000 B)
PID hash table entries: 2048 (order: 1, 8192 bytes)
Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
Memory: 270MB = 270MB total
Memory: 169052k/169052k available, 107428k reserved, 0K highmem
Virtual kernel memory layout:
    vector  : 0xffff0000 - 0xffff1000   (   4 kB)
    fixmap  : 0xfff00000 - 0xfffe0000   ( 896 kB)
    DMA     : 0xffc00000 - 0xffe00000   (   2 MB)
    vmalloc : 0xd1000000 - 0xf8000000   ( 624 MB)
    lowmem  : 0xc0000000 - 0xd0e00000   ( 270 MB)
    pkmap   : 0xbfe00000 - 0xc0000000   (   2 MB)
    modules : 0xbf000000 - 0xbfe00000   (  14 MB)
      .init : 0xc0008000 - 0xc003d000   ( 212 kB)
      .text : 0xc003d000 - 0xc04ef000   (4808 kB)
      .data : 0xc04f0000 - 0xc0532140   ( 265 kB)
SLUB: Genslabs=11, HWalign=64, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
NR_IRQS:407
IRQ: Found an INTC at 0xfa200000 (revision 5.0) with 128 interrupts
Total of 128 interrupts on 1 active controller
GPMC revision 6.0
Trying to install interrupt handler for IRQ400
Trying to install interrupt handler for IRQ401
Trying to install interrupt handler for IRQ402
Trying to install interrupt handler for IRQ403
Trying to install interrupt handler for IRQ404
Trying to install interrupt handler for IRQ405
Trying to install interrupt handler for IRQ406
Trying to install type control for IRQ407
Trying to set irq flags for IRQ407
OMAP clockevent source: GPTIMER1 at 27000000 Hz
Console: colour dummy device 80x30
Calibrating delay loop... 1199.30 BogoMIPS (lpj=5996544)
pid_max: default: 32768 minimum: 301
Security Framework initialized
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
devtmpfs: initialized
omap_voltage_early_init: voltage driver support not added
regulator: core version 0.5
regulator: dummy:
NET: Registered protocol family 16
omap_voltage_domain_lookup: Voltage driver init not yet happened.Faulting!
omap_voltage_add_dev: VDD specified does not exist!
OMAP GPIO hardware version 0.1
OMAP GPIO hardware version 0.1
omap_mux_init: Add partition: #1: core, flags: 0
_omap_mux_get_by_name: Could not find signal i2c2_scl.i2c2_scl
_omap_mux_get_by_name: Could not find signal i2c2_sda.i2c2_sda
Configuring FLASH for boot-from-SPI
=========> audio clk init
hw-breakpoint: debug architecture 0x4 unsupported.
hw perfevents: enabled with ARMv7 Cortex-A8 PMU driver, 5 counters available
registered ti816x_sr device
pm_dbg_init: only OMAP3 supported
registered ti81xx_vpss device
registered ti81xx on-chip HDMI device
registered ti81xx_fb device
ti81xx_pcie: Invoking PCI BIOS...
ti81xx_pcie: Setting up Host Controller...
ti81xx_pcie: Register base mapped @0xd1020000
ti81xx_pcie: forcing link speed - GEN1
ti81xx_pcie: Starting PCI scan...
PCI: bus0: Fast back to back transfers enabled
bio: create slab <bio-0> at 0
vgaarb: loaded
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
USBSS revision 4ea20809
registerd cppi-dma Intr @ IRQ 17
Cppi41 Init Done
omap_i2c omap_i2c.1: bus 1 rev4.0 at 100 kHz
 [reg] 475:tps40400_probe TPS40400 exponent:-10
 [reg] 365:platform_fixup PMBUS_VOUT_SCALE_LOOP: 0xb933
 [reg] 390:platform_fixup PMBUS_IOUT_OC_FAULT_LIMIT: 0xf814
 [reg] 404:platform_fixup PMBUS_IOUT_CAL_GAIN: 0x88e5
 [reg] tps40400_get_voltage
 [reg] tps40400_check_current: Avg Output Current 1740mA!
 [reg] 169:tps40400_get_voltage Avg Current Output voltage 932812uV
regulator: pmbus_vr: 800 <--> 1050 mV at 932 mV
 [reg] 565:tps40400_probe Avg Current Output voltage 930468uV
 [reg] 575:tps40400_probe VOUT_CAL_OFFSET: 71
regulator: tps40400 probe done.
omap_i2c omap_i2c.2: bus 2 rev4.0 at 100 kHz
cfg80211: Calling CRDA to update world regulatory domain
Switching to clocksource gp timer
musb-hdrc: version 6.0, host, debug=0
musb-hdrc musb-hdrc.0: dma type: dma-cppi41
MUSB controller-0 revision 4ea20800
musb-hdrc musb-hdrc.0: MUSB HDRC host driver
musb-hdrc musb-hdrc.0: new USB bus registered, assigned bus number 1
usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb1: Product: MUSB HDRC host driver
usb usb1: Manufacturer: Linux 2.6.37 musb-hcd
usb usb1: SerialNumber: musb-hdrc.0
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 1 port detected
musb-hdrc musb-hdrc.0: USB Host mode controller at d101e000 using DMA, IRQ 18
musb-hdrc musb-hdrc.1: dma type: dma-cppi41
MUSB controller-1 revision 4ea20800
musb-hdrc musb-hdrc.1: MUSB HDRC host driver
musb-hdrc musb-hdrc.1: new USB bus registered, assigned bus number 2
usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb2: Product: MUSB HDRC host driver
usb usb2: Manufacturer: Linux 2.6.37 musb-hcd
usb usb2: SerialNumber: musb-hdrc.1
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 1 port detected
musb-hdrc musb-hdrc.1: USB Host mode controller at d1026800 using DMA, IRQ 19
NET: Registered protocol family 2
IP route cache hash table entries: 4096 (order: 2, 16384 bytes)
TCP established hash table entries: 16384 (order: 5, 131072 bytes)
TCP bind hash table entries: 16384 (order: 4, 65536 bytes)
TCP: Hash tables configured (established 16384 bind 16384)
TCP reno registered
UDP hash table entries: 256 (order: 0, 4096 bytes)
UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
NET: Registered protocol family 1
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
NetWinder Floating Point Emulator V0.97 (double precision)
PMU: registered new PMU device of type 0
Switched to NOHz mode on CPU #0
omap-iommu omap-iommu.0: ducati registered
omap-iommu omap-iommu.1: sys registered
Fun BPAMEM_init Line 409: <6>bpamem_init
JFFS2 version 2.2. (NAND) © 2001-2006 Red Hat, Inc.
ROMFS MTD (C) 2007 Red Hat, Inc.
msgmni has been set to 330
io scheduler noop registered
io scheduler deadline registered
io scheduler cfq registered (default)
Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
omap_uart.0: ttyO0 at MMIO 0x48020000 (irq = 72) is a OMAP UART0
ti81xx_interrupt 977: musb(1): VBUSERR: device may be drawing more current devctl(80) Restarting musb....
ti81xx_interrupt 977: musb(0): VBUSERR: device may be drawing more current devctl(80) Restarting musb....
console [ttyO0] enabled
omap_uart.1: ttyO1 at MMIO 0x48022000 (irq = 73) is a OMAP UART1
omap_uart.2: ttyO2 at MMIO 0x48024000 (irq = 74) is a OMAP UART2
brd: module loaded
loop: module loaded
ahci probe: devid name is ahci
ahci CAP register dump =0x6726ff81
Modified ahci CAP register dump =0x6f26ff81
ahci ahci.0: forcing PORTS_IMPL to 0x3
ahci: SSS flag set, parallel bus scan disabled
ahci ahci.0: AHCI 0001.0100 32 slots 2 ports 3 Gbps 0x3 impl platform mode
ahci ahci.0: flags: ncq sntf stag pm led clo only pmp pio slum part ccc
evm_deferred_musb_restart 850: deferred musb restart musbid(1)
evm_deferred_musb_restart 850: deferred musb restart musbid(0)
ti81xx_interrupt 977: musb(1): VBUSERR: device may be drawing more current devctl(80) Restarting musb....
evm_deferred_musb_restart 850: deferred musb restart musbid(1)
ti81xx_interrupt 977: musb(0): VBUSERR: device may be drawing more current devctl(80) Restarting musb....
evm_deferred_musb_restart 850: deferred musb restart musbid(0)
ti81xx_interrupt 977: musb(1): VBUSERR: device may be drawing more current devctl(80) Restarting musb....
evm_deferred_musb_restart 850: deferred musb restart musbid(1)
ti81xx_interrupt 977: musb(0): VBUSERR: device may be drawing more current devctl(80) Restarting musb....
evm_deferred_musb_restart 850: deferred musb restart musbid(0)
ti81xx_interrupt 977: musb(1): VBUSERR: device may be drawing more current devctl(80) Restarting musb....
evm_deferred_musb_restart 850: deferred musb restart musbid(1)
ti81xx_interrupt 977: musb(0): VBUSERR: device may be drawing more current devctl(80) Restarting musb....
evm_deferred_musb_restart 850: deferred musb restart musbid(0)
ti81xx_interrupt 977: musb(1): VBUSERR: device may be drawing more current devctl(80) Restarting musb....
evm_deferred_musb_restart 850: deferred musb restart musbid(1)
ti81xx_interrupt 977: musb(0): VBUSERR: device may be drawing more current devctl(80) Restarting musb....
evm_deferred_musb_restart 850: deferred musb restart musbid(0)
ti81xx_interrupt 977: musb(1): VBUSERR: device may be drawing more current devctl(80) Restarting musb....
evm_deferred_musb_restart 850: deferred musb restart musbid(1)
ti81xx_interrupt 977: musb(0): VBUSERR: device may be drawing more current devctl(80) Restarting musb....
evm_deferred_musb_restart 850: deferred musb restart musbid(0)
ti81xx_interrupt 977: musb(1): VBUSERR: device may be drawing more current devctl(80) Restarting musb....
evm_deferred_musb_restart 850: deferred musb restart musbid(1)
ti81xx_interrupt 977: musb(0): VBUSERR: device may be drawing more current devctl(80) Restarting musb....
evm_deferred_musb_restart 850: deferred musb restart musbid(0)
ti81xx_interrupt 977: musb(1): VBUSERR: device may be drawing more current devctl(80) Restarting musb....
evm_deferred_musb_restart 850: deferred musb restart musbid(1)
ti81xx_interrupt 977: musb(0): VBUSERR: device may be drawing more current devctl(80) Restarting musb....
evm_deferred_musb_restart 850: deferred musb restart musbid(0)
ti81xx_interrupt 977: musb(1): VBUSERR: device may be drawing more current devctl(80) Restarting musb....
evm_deferred_musb_restart 850: deferred musb restart musbid(1)
ti81xx_interrupt 977: musb(0): VBUSERR: device may be drawing more current devctl(80) Restarting musb....
evm_deferred_musb_restart 850: deferred musb restart musbid(0)
ti81xx_interrupt 977: musb(1): VBUSERR: device may be drawing more current devctl(80) Restarting musb....
evm_deferred_musb_restart 850: deferred musb restart musbid(1)
ti81xx_interrupt 977: musb(0): VBUSERR: device may be drawing more current devctl(80) Restarting musb....
evm_deferred_musb_restart 850: deferred musb restart musbid(0)
ti81xx_interrupt 977: musb(1): VBUSERR: device may be drawing more current devctl(80) Restarting musb....
evm_deferred_musb_restart 850: deferred musb restart musbid(1)
ti81xx_interrupt 977: musb(0): VBUSERR: device may be drawing more current devctl(80) Restarting musb....
evm_deferred_musb_restart 850: deferred musb restart musbid(0)
ti81xx_interrupt 977: musb(1): VBUSERR: device may be drawing more current devctl(80) Restarting musb....
evm_deferred_musb_restart 850: deferred musb restart musbid(1)
ti81xx_interrupt 977: musb(0): VBUSERR: device may be drawing more current devctl(80) Restarting musb....
evm_deferred_musb_restart 850: deferred musb restart musbid(0)
ti81xx_interrupt 977: musb(1): VBUSERR: device may be drawing more current devctl(80) Restarting musb....
evm_deferred_musb_restart 850: deferred musb restart musbid(1)
ti81xx_interrupt 977: musb(0): VBUSERR: device may be drawing more current devctl(80) Restarting musb....
evm_deferred_musb_restart 850: deferred musb restart musbid(0)
ti81xx_interrupt 977: musb(1): VBUSERR: device may be drawing more current devctl(80) Restarting musb....
evm_deferred_musb_restart 850: deferred musb restart musbid(1)
ti81xx_interrupt 977: musb(0): VBUSERR: device may be drawing more current devctl(80) Restarting musb....
evm_deferred_musb_restart 850: deferred musb restart musbid(0)
ti81xx_interrupt 977: musb(1): VBUSERR: device may be drawing more current devctl(80) Restarting musb....
evm_deferred_musb_restart 850: deferred musb restart musbid(1)
ti81xx_interrupt 977: musb(0): VBUSERR: device may be drawing more current devctl(80) Restarting musb....
evm_deferred_musb_restart 850: deferred musb restart musbid(0)
ti81xx_interrupt 977: musb(1): VBUSERR: device may be drawing more current devctl(80) Restarting musb....
evm_deferred_musb_restart 850: deferred musb restart musbid(1)
ti81xx_interrupt 977: musb(0): VBUSERR: device may be drawing more current devctl(80) Restarting musb....
evm_deferred_musb_restart 850: deferred musb restart musbid(0)
ti81xx_interrupt 977: musb(1): VBUSERR: device may be drawing more current devctl(80) Restarting musb....
evm_deferred_musb_restart 850: deferred musb restart musbid(1)
ti81xx_interrupt 977: musb(0): VBUSERR: device may be drawing more current devctl(80) Restarting musb....
evm_deferred_musb_restart 850: deferred musb restart musbid(0)
ti81xx_interrupt 977: musb(1): VBUSERR: device may be drawing more current devctl(80) Restarting musb....
evm_deferred_musb_restart 850: deferred musb restart musbid(1)
ti81xx_interrupt 977: musb(0): VBUSERR: device may be drawing more current devctl(80) Restarting musb....
evm_deferred_musb_restart 850: deferred musb restart musbid(0)
ti81xx_interrupt 977: musb(1): VBUSERR: device may be drawing more current devctl(80) Restarting musb....
evm_deferred_musb_restart 850: deferred musb restart musbid(1)
ti81xx_interrupt 977: musb(0): VBUSERR: device may be drawing more current devctl(80) Restarting musb....
evm_deferred_musb_restart 850: deferred musb restart musbid(0)
ti81xx_interrupt 977: musb(1): VBUSERR: device may be drawing more current devctl(80) Restarting musb....
evm_deferred_musb_restart 850: deferred musb restart musbid(1)
ti81xx_interrupt 977: musb(0): VBUSERR: device may be drawing more current devctl(80) Restarting musb....
evm_deferred_musb_restart 850: deferred musb restart musbid(0)
ti81xx_interrupt 977: musb(1): VBUSERR: device may be drawing more current devctl(80) Restarting musb....
evm_deferred_musb_restart 850: deferred musb restart musbid(1)
ti81xx_interrupt 977: musb(0): VBUSERR: device may be drawing more current devctl(80) Restarting musb....
evm_deferred_musb_restart 850: deferred musb restart musbid(0)
ti81xx_interrupt 977: musb(1): VBUSERR: device may be drawing more current devctl(80) Restarting musb....
evm_deferred_musb_restart 850: deferred musb restart musbid(1)
ti81xx_interrupt 977: musb(0): VBUSERR: device may be drawing more current devctl(80) Restarting musb....
evm_deferred_musb_restart 850: deferred musb restart musbid(0)
ti81xx_interrupt 977: musb(1): VBUSERR: device may be drawing more current devctl(80) Restarting musb....

trass
Сообщения: 9
Зарегистрирован: 28 апр 2016, 20:49

Re: Dahua DH-NVR5208-P не включается (перегрет, не грузится kernel)

Сообщение trass » 31 май 2017, 00:15

Адаптер (всмысле Блок питания) родной, нагрузку держит нормльно, не просидает.
На другом реге выдает такие же напряжения в этом участке. Контроллер питания там стоит TPS40400, вокруг нее на обоих регах были вздуты/заменены электролиты. В логах, кстати, есть инфа по опросу этой микры.

iTuneDVR
Сообщения: 3220
Зарегистрирован: 24 авг 2013, 11:05

Re: Dahua DH-NVR5208-P не включается (перегрет, не грузится kernel)

Сообщение iTuneDVR » 31 май 2017, 00:15

Да уж, может быть и такое, что камню плохо, ведь это SoC и там всё на нём.
Адаптер стоит всё таки заведомо рабочий.

trass
Сообщения: 9
Зарегистрирован: 28 апр 2016, 20:49

Re: Dahua DH-NVR5208-P не включается (перегрет, не грузится kernel)

Сообщение trass » 31 май 2017, 00:36

Спасибо за быстрый ответ. Завтра еще попробую отсоединить это питание и померять без нагрузки и "покурить" даташит TPS-ки, что она выдает.

iTuneDVR
Сообщения: 3220
Зарегистрирован: 24 авг 2013, 11:05

Re: Dahua DH-NVR5208-P не включается (перегрет, не грузится kernel)

Сообщение iTuneDVR » 31 май 2017, 00:42

Сбрасывать со счетов ничего не нужно, тут мелочей нет!


Вернуться в «Видеорегистраторы DAHUA»