VU+ stuck at 'Starting...'

[danishdude]

Yesterday my box went belly-up suddenly. After a restart all i got was "Starting..."
No picture on tv...nothing.

Bring forth ye 'ol RS232-cable...<plug> - and lets see what it says - if anything. And yes - its breathing, albeit barely:


Normal 0x00000000 -> 0x00010000
Movable zone start PFN for each node
early_node_map[1] active PFN ranges
0: 0x00000000 -> 0x00010000
PERCPU: Embedded 7 pages/cpu @81203000 s4384 r8192 d16096 u32768
Built 1 zonelists in Zone order, mobility grouping on. Total pages: 65024
Kernel command line: bmem=112M ubi.mtd=0 root=ubi0:rootfs rootfstype=ubifs rw console=ttyS0,115200n8 rootflags=sync
PID hash table entries: 1024 (order: 0, 4096 bytes)
Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
Primary instruction cache 32kB, VIPT, 2-way, linesize 64 bytes.
Primary data cache 64kB, 4-way, VIPT, cache aliases, linesize 64 bytes
Memory: 138032k/262144k available (5534k kernel code, 124112k reserved, 1192k data, 248k init, 0k highmem)
Hierarchical RCU implementation.
NR_IRQS:128
Detected MIPS clock frequency: 404 MHz (202.493 MHz counter)
Console: colour dummy device 80x25
Calibrating delay loop... 403.45 BogoMIPS (lpj=201728)
pid_max: default: 32768 minimum: 301
Mount-cache hash table entries: 512
SMP: Booting CPU1...
CPU revision is: 0002a044 (Brcm4380)
FPU revision is: 00130001
Primary instruction cache 32kB, VIPT, 2-way, linesize 64 bytes.
Primary data cache 64kB, 4-way, VIPT, cache aliases, linesize 64 bytes
SMP: CPU1 is running
Brought up 2 CPUs
NET: Registered protocol family 16
PCI2.3->SDRAM window: 512 MB
bio: create slab <bio-0> at 0
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
Advanced Linux Sound Architecture Driver Version 1.0.24.
PCI: found device 14e4:8602 on SATA bus, slot 0 (irq 42)
pci 0000:01:00.0: BAR 5: assigned [mem 0x10510000-0x10510fff]
pci 0000:01:00.0: BAR 5: set to [mem 0x10510000-0x10510fff] (PCI address [0x10510000-0x10510fff])
pci 0000:01:00.0: BAR 6: assigned [mem 0x10511000-0x105117ff pref]
Bluetooth: Core ver 2.16
NET: Registered protocol family 31
Bluetooth: HCI device and connection manager initialized
Bluetooth: HCI socket layer initialized
Bluetooth: L2CAP socket layer initialized
cfg80211: Calling CRDA to update world regulatory domain
Switching to clocksource upg
NET: Registered protocol family 2
IP route cache hash table entries: 2048 (order: 1, 8192 bytes)
TCP established hash table entries: 8192 (order: 4, 65536 bytes)
TCP bind hash table entries: 8192 (order: 4, 65536 bytes)
TCP: Hash tables configured (established 8192 bind 8192)
TCP reno registered
UDP hash table entries: 128 (order: 0, 4096 bytes)
UDP-Lite hash table entries: 128 (order: 0, 4096 bytes)
NET: Registered protocol family 1
RPC: Registered named UNIX socket transport module.
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
fuse init (API version 7.17)
msgmni has been set to 269
io scheduler noop registered
io scheduler cfq registered (default)
Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
serial8250.0: ttyS0 at MMIO 0x10400b00 (irq = 22) is a 16550A
console [ttyS0] enabled, bootconsole disabled
console [ttyS0] enabled, bootconsole disabled
serial8250.0: ttyS1 at MMIO 0x10400b40 (irq = 66) is a 16550A
serial8250.0: ttyS2 at MMIO 0x10400b80 (irq = 67) is a 16550A
loop: module loaded
brcm-pm: enabling sata clocks
PCI: Enabling device 0000:01:00.0 (0000 -> 0003)
scsi0 : sata_brcmstb
scsi1 : sata_brcmstb
ata1: SATA max UDMA7 mmio m4096@0x10510000 port 0x10510000 irq 42
ata2: SATA max UDMA7 mmio m4096@0x10510000 port 0x10510100 irq 42
Broadcom STB NAND controller (BrcmNand Controller)
bcmemac: Broadcom STB 10/100 EMAC driver v3.0
bcmemac: registered interface #0 at 0x10080000 as 'eth0' (00:1d:ec:01:aa:a5)
bcmemac: not registering interface #1 at 0x10090000 (no PHY detected)
usbcore: registered new interface driver zd1201
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
brcm-pm: enabling usb clocks
ehci-brcm ehci-brcm.0: Broadcom STB EHCI
ehci-brcm ehci-brcm.0: new USB bus registered, assigned bus number 1
ehci-brcm ehci-brcm.0: irq 62, io mem 0x10480300
ehci-brcm ehci-brcm.0: USB 0.0 started, EHCI 1.00
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 2 ports detected
ehci-brcm ehci-brcm.1: Broadcom STB EHCI
ehci-brcm ehci-brcm.1: new USB bus registered, assigned bus number 2
ehci-brcm ehci-brcm.1: irq 57, io mem 0x10480500
ehci-brcm ehci-brcm.1: USB 0.0 started, EHCI 1.00
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 2 ports detected
ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
ohci-brcm ohci-brcm.0: Broadcom STB OHCI
ohci-brcm ohci-brcm.0: new USB bus registered, assigned bus number 3
ohci-brcm ohci-brcm.0: irq 63, io mem 0x10480400
hub 3-0:1.0: USB hub found
hub 3-0:1.0: 2 ports detected
ohci-brcm ohci-brcm.1: Broadcom STB OHCI
ohci-brcm ohci-brcm.1: new USB bus registered, assigned bus number 4
ohci-brcm ohci-brcm.1: irq 64, io mem 0x10480600
hub 4-0:1.0: USB hub found
hub 4-0:1.0: 2 ports detected
ata1: SATA link down (SStatus 4 SControl 300)
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
mousedev: PS/2 mouse device common for all mice
i2c /dev entries driver
lirc_dev: IR Remote Control driver registered, major 254
IR NEC protocol handler initialized
IR RC5(x) protocol handler initialized
IR RC6 protocol handler initialized
IR JVC protocol handler initialized
IR Sony protocol handler initialized
IR RC5 (streamzap) protocol handler initialized
IR MCE Keyboard/mouse protocol handler initialized
IR LIRC bridge handler initialized
Bluetooth: Generic Bluetooth USB driver ver 0.6
usbcore: registered new interface driver btusb
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
ALSA device list:
No soundcards found.
TCP cubic registered
NET: Registered protocol family 17
Bluetooth: HIDP (Human Interface Emulation) ver 1.2
lib80211: common routines for IEEE802.11 drivers
EBI CS0: setting up NAND flash (primary)
mtd->oobsize=0, mtd->eccOobSize=0
NAND_CS_NAND_XOR=00000001
B4: NandSelect=40000101, nandConfig=55042200, chipSelect=0
brcmnand_read_id: CS0: dev_id=ecf10095
After: NandSelect=40000101, nandConfig=55042200
Block size=00020000, erase shift=17
NAND Config: Reg=55042200, chipSize=128 MB, blockSize=128K, erase_shift=11
busWidth=1, pageSize=2048B, page_shift=11, page_mask=000007ff
BrcmNAND mfg ec f1 Samsung K9F1G08U0A 128MB on CS0


Found NAND on CS0: ACC=d3000000, cfg=55042200, flashId=ecf10095, tim1=4232222d, tim2=00000d94
BrcmNAND version = 0x0201 128MB @00000000
B4: NandSelect=40000101, nandConfig=55042200, chipSelect=0
brcmnand_read_id: CS0: dev_id=ecf10095
After: NandSelect=40000101, nandConfig=55042200
Found NAND flash on Chip Select 0, chipSize=128MB, usable size=128MB, base=0
brcmnand_scan: B4 nand_select = 40000101
brcmnand_scan: After nand_select = 40000101
page_shift=11, bbt_erase_shift=17, chip_shift=27, phys_erase_shift=17
Brcm NAND controller version = 2.1 NAND flash size 128MB @18000000
ECC layout=brcmnand_oob_bch4_4k
brcmnand_scan: mtd->oobsize=64
brcmnand_scan: oobavail=50, eccsize=512, writesize=2048
brcmnand_scan, eccsize=512, writesize=2048, eccsteps=4, ecclevel=15, eccbytes=3
-->brcmnand_default_bbt
brcmnand_default_bbt: bbt_td = bbt_main_descr
Creating 7 MTD partitions on "brcmnand.0":
0x000000000000-0x000007600000 : "rootfs"
0x000007600000-0x000007a00000 : "kernel"
0x000007a00000-0x000007c00000 : "boot"
0x000007c00000-0x000007d00000 : "cfe"
0x000007d00000-0x000007d80000 : "mac"
0x000007d80000-0x000007e00000 : "env"
0x000007e00000-0x000007f00000 : "nvm"
UBI: attaching mtd0 to ubi0
UBI: physical eraseblock size: 131072 bytes (128 KiB)
UBI: logical eraseblock size: 126976 bytes
UBI: smallest flash I/O unit: 2048
UBI: VID header offset: 2048 (aligned 2048)
UBI: data offset: 4096
ata2: SATA link down (SStatus 4 SControl 300)
UBI: max. sequence number: 101
UBI: attached mtd0 to ubi0
UBI: MTD device name: "rootfs"
UBI: MTD device size: 118 MiB
UBI: number of good PEBs: 943
UBI: number of bad PEBs: 1
UBI: number of corrupted PEBs: 0
UBI: max. allowed volumes: 128
UBI: wear-leveling threshold: 4096
UBI: number of internal volumes: 1
UBI: number of user volumes: 1
UBI: available PEBs: 0
UBI: total number of reserved PEBs: 943
UBI: number of PEBs reserved for bad PEB handling: 9
UBI: max/mean erase counter: 2/0
UBI: image sequence number: 1367958133
UBI: background thread "ubi_bgt0d" started, PID 44
UBIFS: parse sync
UBIFS: recovery needed
UBIFS: recovery completed
UBIFS: mounted UBI device 0, volume 0, name "rootfs"
UBIFS: file system size: 116690944 bytes (113956 KiB, 111 MiB, 919 LEBs)
UBIFS: journal size: 9023488 bytes (8812 KiB, 8 MiB, 72 LEBs)
UBIFS: media format: w4/r0 (latest is w4/r0)
UBIFS: default compressor: lzo
UBIFS: reserved for root: 0 bytes (0 KiB)
VFS: Mounted root (ubifs filesystem) on device 0:12.
Freeing unused kernel memory: 248k freed
INIT: version 2.86 booting
Please wait: booting...
Root filesystem already rw, not remounting
Configuring update-modules.
procmk_init
dvb_bcm7335: module license 'Proprietary' taints kernel.
Disabling lock debugging due to kernel taint
DVB: registering new adapter (bm750)
CPU 0 Unable to handle kernel paging request at virtual address 00000004, epc == c07d4df0, ra == c06d06c4
Oops[#1]:
Cpu 0
$ 0 : 00000000 10008700 c07d4df0 c0ad0000
$ 4 : 00000000 884b5b80 00000000 00000000
$ 8 : 00000004 802b914c 00000000 00000000
$12 : 88c4cc00 00000000 00000200 00002711
$16 : 881aca00 88da398c 00000000 00000001
$20 : 88da3994 00000002 00000005 c06cf910
$24 : 00000000 802b9060
$28 : 88da2000 88da3918 c06cf960 c06d06c4
Hi : 00000000
Lo : 00000000
epc : c07d4df0 NEXUS_I2c_GetRegHandle+0x0/0x30 [dvb_bcm7335]
Tainted: P
ra : c06d06c4 NEXUS_Tuner_Open3440_impl+0x74/0x340 [dvb_bcm7335]
Status: 10008703 KERNEL EXL IE
Cause : 00800008
BadVA : 00000004
PrId : 0002a044 (Brcm4380)
Modules linked in: dvb_bcm7335(P+) procmk
Process modprobe (pid: 229, threadinfo=88da2000, task=88fa4988, tls=7713b490)
Stack : c0707010 c0708004 00000000 c06f4740 00000002 c0ad0dcc 00000003 00000001
88da398c c0ad0dd0 00000003 00000001 88da3994 c06ced24 c0ae0000 10008701
8777d680 00000026 88da398c 88da39a4 88da398c c06c4208 88da3a6c 8777df80
c0adb3c0 88da39e0 8843fa00 00000000 00000003 00000000 00000064 000186a0
87770001 00000000 00000000 00000001 01000100 00000100 000000bc 00000001
...
Call Trace:
[<c07d4df0>] NEXUS_I2c_GetRegHandle+0x0/0x30 [dvb_bcm7335]
[<c06d06c4>] NEXUS_Tuner_Open3440_impl+0x74/0x340 [dvb_bcm7335]
[<c06ced24>] NEXUS_Tuner_Open3440+0x28/0x48 [dvb_bcm7335]
[<c06c4208>] NEXUS_Platform_InitFrontend+0x23c/0x584 [dvb_bcm7335]
[<c06c2e5c>] NEXUS_Platform_Init+0x710/0x7c4 [dvb_bcm7335]
[<c0b540d8>] bcm7335_init+0xd8/0x854 [dvb_bcm7335]
[<80001450>] do_one_initcall+0x40/0x1f8
[<800726e0>] sys_init_module+0x174/0x14a0
[<8000e9fc>] stack_done+0x20/0x40




Code: 24020008 03e00008 24020008 <8c830004> 10a30008 24820064 50a00006 24820008 3c02c0ad
---[ end trace df588688b6a9d423 ]---
Anyone have an idea what went wrong around the kernel paging leading to Oops[#1]?

I've been trying to refresh images. Including new fresh ViX (first with the bootloader and then the image), and afterwards trying with a standard VU+ Duo image from the manufacturer (v7.0).

Still no tv for me - so would really appreciate it, if any of you experts could cast a working spell :)

[Zartmy]

UBI: attaching mtd0 to ubi0
UBI: physical eraseblock size: 131072 bytes (128 KiB)
UBI: logical eraseblock size: 126976 bytes
UBI: smallest flash I/O unit: 2048
UBI: VID header offset: 2048 (aligned 2048)
UBI: data offset: 4096
ata2: SATA link down (SStatus 4 SControl 300)
UBI: max. sequence number: 101
UBI: attached mtd0 to ubi0
UBI: MTD device name: "rootfs"
UBI: MTD device size: 118 MiB
UBI: number of good PEBs: 943
UBI: number of bad PEBs: 1
UBI: number of corrupted PEBs: 0
UBI: max. allowed volumes: 128
UBI: wear-leveling threshold: 4096
UBI: number of internal volumes: 1
UBI: number of user volumes: 1
UBI: available PEBs: 0
UBI: total number of reserved PEBs: 943
UBI: number of PEBs reserved for bad PEB handling: 9

I think the highlighted bit indicates that the internal flash memory is damaged.

Only strange thing i see (not counting the kernel crash ). Someone problary have a better answear...

[danishdude]

I think the highlighted bit indicates that the internal flash memory is damaged.

Only strange thing i see (not counting the kernel crash ). Someone problary have a better answear...Damn...*hmm*
Thanks for the swift reply, Zartmy.

I am about to try with VTi...just for kicks.

If anyone has an idea, please chime in. I have time to get it in for repair tomorrow. Sadly, it's just over one year old - and the shop only gives one year warranty :(

[danishdude]

Nope...VTi is a no-go too.
Apparently flashmemory-management insists on writing to the faulty PEB each time. It just puzzles me why there are 9 in reserve, if these cant be invoked when one goes bad!? :mad:

I will hand it over for repair. *bugger*

[Zartmy]

Well, it might aswell be faulty memory or something else. I think the filesystem UBIFS uses the reserve ones when it detects an error. Your problem is that the flashtool used when applying the image is writing the UBIFS image over the broken memory, so the ubi filesystem is broken the first time it boots. But still i am no expert in nand memory nor ubifs, I might be out cycling... (hmm is that expression valid in english?)

[danishdude]

Well, it might aswell be faulty memory or something else. I think the filesystem UBIFS uses the reserve ones when it detects an error. Your problem is that the flashtool used when applying the image is writing the UBIFS image over the broken memory, so the ubi filesystem is broken the first time it boots. But still i am no expert in nand memory nor ubifs, I might be out cycling... (hmm is that expression valid in english?)Makes perfect sense - and so does your cycling ;)

[75mak]

How does nand get damaged like that? Is there anything in particular you should avoid

[Zartmy]

How does nand get damaged like that? Is there anything in particular you should avoid

ESD Electric Discharge, wear and tear - nand flash and most flash memory has a finit number of write/erase cycles, read more on wikipedia http://en.wikipedia.org/wiki/Flash_memory#NAND_flash

Unless your inside your box doing stuff, like replacing the harddrive often, i dont think there is much you can do.

[danishdude]

It's just a shame, that a box only 16 months old already dies like that.
No excessive work been done on it. Only installed a harddrive, and flashed new images on it when they appeared. Typically a few months apart.
I am used to work with sensitive hardware like this (ESD) - so i guess i've just been unlucky.

[danishdude]

The poor sick Duo has now been turned in for repair.
Two dudes behind the counter didnt know sh** about Linux-receivers, and the fact that i produced a log showing the exact error. Oh no - it has to go to the distributor, who will test it for errors and so on...only to come up with the exact same diagnosis i left documented in the box.
So, instead of getting the mainboard exhanged immediately (or a replacement receiver), i will have to wait for the whole circus to rev up and take its turns. *sigh*
So, no receiver for me the next two/three/four weeks.

It's hard being a knowledgeable consumer :whistle:

I even considered buying a Solo as a replacement, and sell it again, when the other one came back. Or sell the Duo, when it has been repaired (i actually dont use the dual-tuners - so no need-to-have). The Solo, with it's interchangeable tuners could come in handy, if i, in the future, go from DVB-S to DVB-C.

#GoodthingidontwatchTHATmuchtv-otherwiseiwouldhavegonecrazy

Other than that...good morning from Scandinavia
:tea:

[danishdude]

16 months old - and the shop washes it's hands, and tells me i have to handle the problem myself, contacting the distributor directly (Digital Nordic Sweden) - as the warranty ran out four months ago. At the same time, they tell me i shouldnt get my hopes up, as i need to provide futher proof to the problem.(!!?) Apparently the serial-dump, showing the exact problem, is not enough - if you ask them.
What else do they want? What else can i do? Beats me...*sigh* :confused::mad:

Just ordered a new Uno instead (NOT a the same shop :D)
Now...what to do with the 'old' Duo. Will it blend? Can it burn?

(Four months out of warranty...*arrrrgh*)

[silverfox0786]

whats is the serial dump
im curious to see if its a fixable error


edit: sorry i see it post 1

[danishdude]

whats is the serial dump
im curious to see if its a fixable error
edit: sorry i see it post 1Looking forward to hear your input (output, actually) :)

[silverfox0786]

i dont think that PEB is your issue but i may be wrong

you do have a bad PEB thats true but

then you get 9 PEBS handled for that issue

if those 9 PEBS couldnt handle it then this is the sort of output you would have gotten

"UBI warning: cannot reserve enough PEBs for bad PEB
handling, reserved 0, need 20"


then there is also this that makes me wonder



Found NAND flash on Chip Select 0, chipSize=128MB, usable size=128MB, base=0

then there si this


UBIFS: recovery needed
UBIFS: recovery completed



and here is your problem

a faulty tuner card


dvb_bcm7335: module license 'Proprietary' taints kernel.
Disabling lock debugging due to kernel taint

[danishdude]

You NERD! :thumbsup:

...and thats meant in a positive way.
You have any idea if theres a fix - or do i need to have the entire tuner replaced?
(Why didnt i read more into Linux at an early age!? *hehe*)

[silverfox0786]

you prob need the tuner replaced

and then there is which tuner as duo is a twin unless its a single unit i cant remeber

but there si also the slight posability that the kernal is corrupt and due to that the tuner is failing

try this

reflash the DUO CFE again then flash the image

and whilest doing both get a serial output

i wanna see if anything fails there

[danishdude]

you prob need the tuner replaced

and then there is which tuner as duo is a twin unless its a single unit i cant remeber Twin-tuner, precisely.


but there si also the slight posability that the kernal is corrupt and due to that the tuner is failing

try this

reflash the DUO CFE again then flash the image "CFE"?


and whilest doing both get a serial output

i wanna see if anything fails thereYou got it! ...but i first have to get the darn thing back from the shop. I hope to get that done tomorrow. And then, i will log the f*** out of it, and present it for you.

Thanks again for taking your time. I really appreciate it! :thumbsup:

[silverfox0786]

Twin-tuner, precisely.
"CFE"?

this is the duo cfe it loaded the same way as flashing image


You got it! ...but i first have to get the darn thing back from the shop. I hope to get that done tomorrow. And then, i will log the f*** out of it, and present it for you.


once you get it back we shall see what gives


Thanks again for taking your time. I really appreciate it! :thumbsup:

dont mention it mate only trying to help

just hope you get it sorted and its a minor issue

[danishdude]

*ahh*...bootloader = CFE :D
I will look into it tomorrow - and bring forth the raw data afterwards.

*fingers crossed*

[silverfox0786]

*ahh*...bootloader = CFE :D
I will look into it tomorrow - and bring forth the raw data afterwards.

*fingers crossed*

good luck with it mate

[danishdude]

Got the box back - now time for CFE & Image (Original VU+ Duo)-flash.
Log's will be with you in a short while. :)

[danishdude]

CFE-flash:




BCM73350010
012
Shmoo Version=1.9


MEMC-00000000 RW=00000010 WW=00000049 G=00000001 R=00000008 W=00000016
MEMC-00000001 RW=00000010 WW=00000053 G=00000001 R=00000009 W=00000009 #$
3
COPY CODE
A567


BCM97335B0 CFE v2.17, CFE core v2.12, Endian Mode: Little
Build Date: Thu Sep 29 12:01:32 2011 (shcheong@ncsh)
Copyright (C) Broadcom Corporation.


writing vfd


DDR Freq: 395MHz
CPU speed: 405MHz
Memory Config: 32+16 non-UMA
Device Tech: 1Gb
Total memory: 384MB
Boot Device: NAND
ECC: Hamming
Total flash: 128MB


Initializing USB.
USB: Locating Class 09 Vendor 0000 Product 0000: USB Hub
USB: Locating Class 09 Vendor 0000 Product 0000: USB Hub


CFE initialized.


USB: New device connected to bus 1 hub 1 port 1
USB: Resetting device on bus 1 port 1
USB: Locating Class 08 Vendor 0951 Product 1607: Mass-Storage Device
USBMASS: Unit 0 connected
checking usb
Reading usbdisk0:/vuplus/duo/cfe_cfe_auto.bin: >> Done. 287604 bytes read


Programming...
done. 287604 bytes written0 0x20000 done
please remove usb first and reboot

[danishdude]

Following flash of official VU+ Duo-image (v7.0 - http://www.world-of-satellite.com/showthread.php?15694-New-Image-(V7-0)-Released-Vuduo)




BCM73350010
012
Shmoo Version=1.9


MEMC-00000000 RW=00000010 WW=00000049 G=00000001 R=00000008 W=00000016
MEMC-00000001 RW=00000010 WW=00000053 G=00000001 R=00000009 W=00000009 #$
3
COPY CODE
A567


BCM97335B0 CFE v2.17, CFE core v2.12, Endian Mode: Little
Build Date: Thu Sep 29 12:01:32 2011 (shcheong@ncsh)
Copyright (C) Broadcom Corporation.


writing vfd


DDR Freq: 395MHz
CPU speed: 405MHz
Memory Config: 32+16 non-UMA
Device Tech: 1Gb
Total memory: 384MB
Boot Device: NAND
ECC: Hamming
Total flash: 128MB


Initializing USB.
USB: Locating Class 09 Vendor 0000 Product 0000: USB Hub
USB: Locating Class 09 Vendor 0000 Product 0000: USB Hub


CFE initialized.


USB: New device connected to bus 1 hub 1 port 1
USB: Resetting device on bus 1 port 1
USB: Locating Class 08 Vendor 0951 Product 1607: Mass-Storage Device
USBMASS: Unit 0 connected
checking usb
Reading usbdisk0:/vuplus/duo/cfe_cfe_auto.bin: >> Done. 287604 bytes read


Programming...
done. 287604 bytes written0 0x20000 done
please remove usb first and reboot
USB: Device disconnected from bus 1 hub 1 port 1
USBMASS: USB unit 0 disconnected


BCM73350010
012
Shmoo Version=1.9


MEMC-00000000 RW=00000010 WW=00000049 G=00000001 R=00000008 W=00000016
MEMC-00000001 RW=00000010 WW=00000053 G=00000001 R=00000009 W=00000009 #$
3
COPY CODE
A567


BCM97335B0 CFE v2.17, CFE core v2.12, Endian Mode: Little
Build Date: Thu Sep 29 12:01:32 2011 (shcheong@ncsh)
Copyright (C) Broadcom Corporation.


writing vfd


DDR Freq: 395MHz
CPU speed: 405MHz
Memory Config: 32+16 non-UMA
Device Tech: 1Gb
Total memory: 384MB
Boot Device: NAND
ECC: Hamming
Total flash: 128MB


Initializing USB.
USB: Locating Class 09 Vendor 0000 Product 0000: USB Hub
USB: Locating Class 09 Vendor 0000 Product 0000: USB Hub


CFE initialized.


USB: New device connected to bus 1 hub 1 port 1
USB: Resetting device on bus 1 port 1
USB: Locating Class 08 Vendor 0951 Product 1607: Mass-Storage Device
USBMASS: Unit 0 connected
checking usb
Reading usbdisk0:/vuplus/duo/cfe_cfe_auto.bin: >> Skipping...: File not found
Reading usbdisk0:/vuplus/duo/root_cfe_auto.jffs2: >> Done. 84803584 bytes read
================================================== ======================
nand_erase_block 0x18020000 0x20000 done
nand_erase_block skipping: at blk addr = 0x18020000
================================================== ======================


Programming...
done. 84803584 bytes written0x20000 done
Reading usbdisk0:/vuplus/duo/boot_cfe_auto.jffs2: >> Done. 576 bytes read
================================================== ======================
================================================== ======================


Programming...
done. 576 bytes written0000 0x20000 done
Reading usbdisk0:/vuplus/duo/kernel_cfe_auto.bin: >> Done. 3675896 bytes read


Programming...
done. 3675896 bytes written 0x20000 done
please remove usb first and reboot
USB: Device disconnected from bus 1 hub 1 port 1
USBMASS: USB unit 0 disconnected


Now...time to reboot. Log will follow shortly.

[danishdude]

Reboot done.
Logging completed.
Still hanging at "Starting...", while trying to init the DVB-module...throwing err's at the end.


BCM73350010
012
Shmoo Version=1.9


MEMC-00000000 RW=00000010 WW=00000049 G=00000001 R=00000008 W=00000016
MEMC-00000001 RW=00000010 WW=00000053 G=00000001 R=00000009 W=00000009 #$
3
COPY CODE
A567


BCM97335B0 CFE v2.17, CFE core v2.12, Endian Mode: Little
Build Date: Thu Sep 29 12:01:32 2011 (shcheong@ncsh)
Copyright (C) Broadcom Corporation.


writing vfd


DDR Freq: 395MHz
CPU speed: 405MHz
Memory Config: 32+16 non-UMA
Device Tech: 1Gb
Total memory: 384MB
Boot Device: NAND
ECC: Hamming
Total flash: 128MB


Initializing USB.
USB: Locating Class 09 Vendor 0000 Product 0000: USB Hub
USB: Locating Class 09 Vendor 0000 Product 0000: USB Hub


CFE initialized.


checking usb
Loader:elf Filesys:raw Dev:flash0.kernel File: Options:rootfstype=jffs2 root=/dev/mtdblock0 rw mem=0x8000000 bcmrac=3
Loading: 0x80001000/7237920 0x806e8120/123248 Entry address is 0x80570e70
TP1 Entry Address at 0x80000ffc = 80570e70
Starting program at 0x80570e70


Linux version 3.1.1 (vuplus@team3-server) (gcc version 4.4.3 (GCC) ) #1 SMP Fri Jan 20 03:11:22 KST 2012
Fetching vars from bootloader... found 11 vars.
Early serial console at MMIO32 0x10400b00 (options '115200n8')
bootconsole [uart0] enabled
Options: sata=1 enet=1 emac_1=1 no_mdio=0 docsis=0 pci=1 smp=1 moca=0 usb=1
Using 256 MB + 128 MB RAM (from CFE)
bootconsole [early0] enabled
CPU revision is: 0002a044 (Brcm4380)
FPU revision is: 00130001
Determined physical RAM map:
memory: 10000000 @ 00000000 (usable)
bmem: adding 112 MB RESERVED region at 144 MB (0x07000000@0x09000000)
Initrd not found or empty - disabling initrd
Zone PFN ranges:
Normal 0x00000000 -> 0x00010000
Movable zone start PFN for each node
early_node_map[1] active PFN ranges
0: 0x00000000 -> 0x00010000
PERCPU: Embedded 7 pages/cpu @81203000 s4384 r8192 d16096 u32768
Built 1 zonelists in Zone order, mobility grouping on. Total pages: 65024
Kernel command line: bmem=112M ubi.mtd=0 root=ubi0:rootfs rootfstype=ubifs rw rootflags=sync
PID hash table entries: 1024 (order: 0, 4096 bytes)
Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
Primary instruction cache 32kB, VIPT, 2-way, linesize 64 bytes.
Primary data cache 64kB, 4-way, VIPT, cache aliases, linesize 64 bytes
Memory: 137936k/262144k available (5617k kernel code, 124208k reserved, 1204k data, 248k init, 0k highmem)
Hierarchical RCU implementation.
NR_IRQS:128
Detected MIPS clock frequency: 404 MHz (202.497 MHz counter)
Calibrating delay loop... 403.45 BogoMIPS (lpj=201728)
pid_max: default: 32768 minimum: 301
Mount-cache hash table entries: 512
SMP: Booting CPU1...
CPU revision is: 0002a044 (Brcm4380)
FPU revision is: 00130001
Primary instruction cache 32kB, VIPT, 2-way, linesize 64 bytes.
Primary data cache 64kB, 4-way, VIPT, cache aliases, linesize 64 bytes
SMP: CPU1 is running
Brought up 2 CPUs
NET: Registered protocol family 16
PCI2.3->SDRAM window: 512 MB
bio: create slab <bio-0> at 0
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
Advanced Linux Sound Architecture Driver Version 1.0.24.
PCI: found device 14e4:8602 on SATA bus, slot 0 (irq 42)
pci 0000:01:00.0: BAR 5: assigned [mem 0x10510000-0x10510fff]
pci 0000:01:00.0: BAR 5: set to [mem 0x10510000-0x10510fff] (PCI address [0x10510000-0x10510fff])
pci 0000:01:00.0: BAR 6: assigned [mem 0x10511000-0x105117ff pref]
Bluetooth: Core ver 2.16
NET: Registered protocol family 31
Bluetooth: HCI device and connection manager initialized
Bluetooth: HCI socket layer initialized
Bluetooth: L2CAP socket layer initialized
cfg80211: Calling CRDA to update world regulatory domain
Switching to clocksource upg
NET: Registered protocol family 2
IP route cache hash table entries: 2048 (order: 1, 8192 bytes)
TCP established hash table entries: 8192 (order: 4, 65536 bytes)
TCP bind hash table entries: 8192 (order: 4, 65536 bytes)
TCP: Hash tables configured (established 8192 bind 8192)
TCP reno registered
UDP hash table entries: 128 (order: 0, 4096 bytes)
UDP-Lite hash table entries: 128 (order: 0, 4096 bytes)
NET: Registered protocol family 1
RPC: Registered named UNIX socket transport module.
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
NTFS driver 2.1.30 [Flags: R/W].
JFFS2 version 2.2. (NAND) (SUMMARY) © 2001-2006 Red Hat, Inc.
msgmni has been set to 269
io scheduler noop registered
io scheduler cfq registered (default)
Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
serial8250.0: ttyS0 at MMIO 0x10400b00 (irq = 22) is a 16550A
console [ttyS0] enabled, bootconsole disabled
console [ttyS0] enabled, bootconsole disabled
serial8250.0: ttyS1 at MMIO 0x10400b40 (irq = 66) is a 16550A
serial8250.0: ttyS2 at MMIO 0x10400b80 (irq = 67) is a 16550A
loop: module loaded
brcm-pm: enabling sata clocks
PCI: Enabling device 0000:01:00.0 (0000 -> 0003)
scsi0 : sata_brcmstb
scsi1 : sata_brcmstb
ata1: SATA max UDMA7 mmio m4096@0x10510000 port 0x10510000 irq 42
ata2: SATA max UDMA7 mmio m4096@0x10510000 port 0x10510100 irq 42
Broadcom STB NAND controller (BrcmNand Controller)
bcmemac: Broadcom STB 10/100 EMAC driver v3.0
bcmemac: registered interface #0 at 0x10080000 as 'eth0' (00:1d:ec:01:aa:a5)
bcmemac: not registering interface #1 at 0x10090000 (no PHY detected)
usbcore: registered new interface driver zd1201
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
brcm-pm: enabling usb clocks
ehci-brcm ehci-brcm.0: Broadcom STB EHCI
ehci-brcm ehci-brcm.0: new USB bus registered, assigned bus number 1
ehci-brcm ehci-brcm.0: irq 62, io mem 0x10480300
ehci-brcm ehci-brcm.0: USB 0.0 started, EHCI 1.00
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 2 ports detected
ehci-brcm ehci-brcm.1: Broadcom STB EHCI
ehci-brcm ehci-brcm.1: new USB bus registered, assigned bus number 2
ehci-brcm ehci-brcm.1: irq 57, io mem 0x10480500
ehci-brcm ehci-brcm.1: USB 0.0 started, EHCI 1.00
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 2 ports detected
ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
ohci-brcm ohci-brcm.0: Broadcom STB OHCI
ohci-brcm ohci-brcm.0: new USB bus registered, assigned bus number 3
ohci-brcm ohci-brcm.0: irq 63, io mem 0x10480400
hub 3-0:1.0: USB hub found
hub 3-0:1.0: 2 ports detected
ohci-brcm ohci-brcm.1: Broadcom STB OHCI
ohci-brcm ohci-brcm.1: new USB bus registered, assigned bus number 4
ohci-brcm ohci-brcm.1: irq 64, io mem 0x10480600
hub 4-0:1.0: USB hub found
hub 4-0:1.0: 2 ports detected
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
ata1: SATA link down (SStatus 4 SControl 300)
USB Mass Storage support registered.
mousedev: PS/2 mouse device common for all mice
i2c /dev entries driver
lirc_dev: IR Remote Control driver registered, major 254
IR NEC protocol handler initialized
IR RC5(x) protocol handler initialized
IR RC6 protocol handler initialized
IR JVC protocol handler initialized
IR Sony protocol handler initialized
IR RC5 (streamzap) protocol handler initialized
IR MCE Keyboard/mouse protocol handler initialized
IR LIRC bridge handler initialized
Linux video capture interface: v2.00
Bluetooth: Generic Bluetooth USB driver ver 0.6
usbcore: registered new interface driver btusb
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
ALSA device list:
No soundcards found.
TCP cubic registered
NET: Registered protocol family 17
Bluetooth: HIDP (Human Interface Emulation) ver 1.2
lib80211: common routines for IEEE802.11 drivers
EBI CS0: setting up NAND flash (primary)
mtd->oobsize=0, mtd->eccOobSize=0
NAND_CS_NAND_XOR=00000001
B4: NandSelect=40000101, nandConfig=55042200, chipSelect=0
brcmnand_read_id: CS0: dev_id=ecf10095
After: NandSelect=40000101, nandConfig=55042200
Block size=00020000, erase shift=17
NAND Config: Reg=55042200, chipSize=128 MB, blockSize=128K, erase_shift=11
busWidth=1, pageSize=2048B, page_shift=11, page_mask=000007ff
BrcmNAND mfg ec f1 Samsung K9F1G08U0A 128MB on CS0


Found NAND on CS0: ACC=d3000000, cfg=55042200, flashId=ecf10095, tim1=4232222d, tim2=00000d94
BrcmNAND version = 0x0201 128MB @00000000
B4: NandSelect=40000101, nandConfig=55042200, chipSelect=0
brcmnand_read_id: CS0: dev_id=ecf10095
After: NandSelect=40000101, nandConfig=55042200
Found NAND flash on Chip Select 0, chipSize=128MB, usable size=128MB, base=0
brcmnand_scan: B4 nand_select = 40000101
brcmnand_scan: After nand_select = 40000101
page_shift=11, bbt_erase_shift=17, chip_shift=27, phys_erase_shift=17
Brcm NAND controller version = 2.1 NAND flash size 128MB @18000000
ECC layout=brcmnand_oob_bch4_4k
brcmnand_scan: mtd->oobsize=64
brcmnand_scan: oobavail=50, eccsize=512, writesize=2048
brcmnand_scan, eccsize=512, writesize=2048, eccsteps=4, ecclevel=15, eccbytes=3
-->brcmnand_default_bbt
brcmnand_default_bbt: bbt_td = bbt_main_descr
Creating 7 MTD partitions on "brcmnand.0":
0x000000000000-0x000007600000 : "rootfs"
0x000007600000-0x000007a00000 : "kernel"
0x000007a00000-0x000007c00000 : "boot"
0x000007c00000-0x000007d00000 : "cfe"
0x000007d00000-0x000007d80000 : "mac"
0x000007d80000-0x000007e00000 : "env"
0x000007e00000-0x000007f00000 : "nvm"
UBI: attaching mtd0 to ubi0
UBI: physical eraseblock size: 131072 bytes (128 KiB)
UBI: logical eraseblock size: 126976 bytes
UBI: smallest flash I/O unit: 2048
UBI: VID header offset: 2048 (aligned 2048)
UBI: data offset: 4096
ata2: SATA link down (SStatus 4 SControl 300)
UBI: max. sequence number: 122
UBI: attached mtd0 to ubi0
UBI: MTD device name: "rootfs"
UBI: MTD device size: 118 MiB
UBI: number of good PEBs: 943
UBI: number of bad PEBs: 1
UBI: number of corrupted PEBs: 0
UBI: max. allowed volumes: 128
UBI: wear-leveling threshold: 4096
UBI: number of internal volumes: 1
UBI: number of user volumes: 1
UBI: available PEBs: 0
UBI: total number of reserved PEBs: 943
UBI: number of PEBs reserved for bad PEB handling: 9
UBI: max/mean erase counter: 2/0
UBI: image sequence number: 69128578
UI: background thread "ubi_bgt0d" started, PID 44
UBIFS: parse sync
UBIFS: recovery needed
UBIFS: recovery completed
UBIFS: mounted UBI device 0, volume 0, name "rootfs"
UBIFS: file system size: 116690944 bytes (113956 KiB, 111 MiB, 919 LEBs)
UBIFS: journal size: 9023488 bytes (8812 KiB, 8 MiB, 72 LEBs)
UBIFS: media format: w4/r0 (latest is w4/r0)
UBIFS: default compressor: lzo
UBIFS: reserved for root: 0 bytes (0 KiB)
VFS: Mounted root (ubifs filesystem) on device 0:12.
Freeing unused kernel memory: 248k freed
mount: mounting sysfs on /sys failed: Device or resource busy
procmk_init
dvb_bcm7335: module license 'Proprietary' taints kernel.
Disabling lock debugging due to kernel taint
DVB: registering new adapter (bm750)
CPU 0 Unable to handle kernel paging request at virtual address 00000004, epc == c08390e0, ra == c07349b4
Oops[#1]:
Cpu 0
$ 0 : 00000000 10008700 c08390e0 c0b30000
$ 4 : 00000000 884d9980 00000000 00000000
$ 8 : 00000004 802cf02c 00000000 00000000
$12 : 88c4bc80 00000000 00000200 00002711
$16 : 873ef780 884c398c 00000000 00000001
$20 : 884c3994 00000002 00000005 c0733c00
$24 : 00000000 802cef40
$28 : 884c2000 884c3918 c0733c50 c07349b4
Hi : 00000000
Lo : 00000000
epc : c08390e0 NEXUS_I2c_GetRegHandle+0x0/0x30 [dvb_bcm7335]
Tainted: P
ra : c07349b4 NEXUS_Tuner_Open3440_impl+0x74/0x340 [dvb_bcm7335]
Status: 10008703 KERNEL EXL IE
Cause : 00800008
BadVA : 00000004
PrId : 0002a044 (Brcm4380)
Modules linked in: dvb_bcm7335(P+) procmk
Process modprobe (pid: 61, threadinfo=884c2000, task=88482e00, tls=7713a490)
Stack : c076b300 c076c2f4 00000000 c0758a30 00000002 c0b350cc 00000003 00000001
884c398c c0b350d0 00000003 00000001 884c3994 c0733014 884a2a80 c075f0f8
873e7600 00000026 884c398c 884c39a4 884c398c c07284f8 884c39d4 873e7f00
c0b3f6c0 884c39e0 873e5780 00000000 00000003 00000000 00000064 000186a0
873e0001 00000000 00000000 00000001 01000100 00000100 000000bc 00000001
...
Call Trace:
[<c08390e0>] NEXUS_I2c_GetRegHandle+0x0/0x30 [dvb_bcm7335]
[<c07349b4>] NEXUS_Tuner_Open3440_impl+0x74/0x340 [dvb_bcm7335]
[<c0733014>] NEXUS_Tuner_Open3440+0x28/0x48 [dvb_bcm7335]
[<c07284f8>] NEXUS_Platform_InitFrontend+0x23c/0x584 [dvb_bcm7335]
[<c072714c>] NEXUS_Platform_Init+0x710/0x7c4 [dvb_bcm7335]
[<c0bb80d8>] bcm7335_init+0xd8/0x854 [dvb_bcm7335]
[<80001584>] do_one_initcall+0x174/0x1f8
[<80074da8>] sys_init_module+0x174/0x14a0
[<8000e9fc>] stack_done+0x20/0x40




Code: 24020008 03e00008 24020008 <8c830004> 10a30008 24820064 50a00006 24820008 3c02c0b3
---[ end trace 5f393c090917fc75 ]---
brcmfb: gave up waiting for init of module dvb_bcm7335.
brcmfb: Unknown symbol bcm7335_fb_sync (err -16)
brcmfb: gave up waiting for init of module dvb_bcm7335.
brcmfb: Unknown symbol bcm7335_fb_fillrect (err -16)
brcmfb: gave up waiting for init of module dvb_bcm7335.
brcmfb: Unknown symbol bcm7335_fb_ioctl (err -16)
brcmfb: gave up waiting for init of module dvb_bcm7335.
brcmfb: Unknown symbol bcm7335_fb_copyarea (err -16)
brcmfb: gave up waiting for init of module dvb_bcm7335.
brcmfb: Unknown symbol bcm7335_fb_start (err -16)
brcmfb: gave up waiting for init of module dvb_bcm7335.
brcmfb: Unknown symbol bcm7335_fb_pan_display (err -16)
brcmfb: gave up waiting for init of module dvb_bcm7335.
brcmfb: Unknown symbol bcm7335_fb_imageblit (err -16)
brcmfb: gave up waiting for init of module dvb_bcm7335.
brcmfb: Unknown symbol bcm7335_fb_blank (err -16)
brcmfb: gave up waiting for init of module dvb_bcm7335.
brcmfb: Unknown symbol bcm7335_fb_cursor (err -16)
ð <powered down here>
Is there any chance something can be done, besides having the entire systemboard exchanged? (the tuner is soldered on to the systemboard - and not an interchangeable-module :()

[silverfox0786]

defo looks like a tuner fault

dunno if spare tuners can be brought let alone what yr soldering skills are like

[Larry-G]

You can buy a replacement main board assembly which comes with the tuners but it's not a cheap option and i have only seen them on sale in Australia of all places

[danishdude]

defo looks like a tuner fault Bummer... :(
dunno if spare tuners can be brought let alone what yr soldering skills are likeTuner is built-in on the board - and my soldering-skills are not THAT hardcore ;)http://i39.tinypic.com/2res4zo.jpg

[danishdude]

[QUOTE=pheonix;123182]You can buy a replacement main board assembly which comes with the tuners but it's not a cheap option and i have only seen them on sale in Australia of all places

175,- Aussie smackaroos...*hmm*

[silverfox0786]

looks like a new mainboard

seems to me the tuner chip is burnt out

15697

[danishdude]

looks like a new mainboard seems to me the tuner chip is burnt out15697Nope - thats me that had a finger there (checking for signs of excessive heat (after it was powered down) = missing dust.
It looks like this, when it's clean:http://i43.tinypic.com/1zfkebb.jpg

http://i39.tinypic.com/291mjxv.jpg

;)

[silverfox0786]

:roflmao:

i would suggest cut yr losses on it maybe sell it as faulty repairs or spares

and continue on with the uno unless you get a reasonable repair quote

try emailing support@vuplus.com and see if they willing to do an out of warranty repair

[danishdude]

:roflmao:

i would suggest cut yr losses on it maybe sell it as faulty repairs or spares

and continue on with the uno unless you get a reasonable repair quote

try emailing support@vuplus.com and see if they willing to do an out of warranty repairSumming up time/fuel/money/p&p...i think i will see if anyone can use it for spares - and go forth with the Uno as replacement.

Thanks for your help, Silverfox. It was an interesting run, this one :thumbsup:

[silverfox0786]

i wish i could have helped more mate

yeah it was a good run

and i love yr avatar its wicked

put up for sale i might i might give it a punt for the housing

[Maxwell]

I would be interested in having it as a non working unit as i want to experiment with some hardware mods, I have a wanted thread on here http://www.world-of-satellite.com/showthread.php?16657-cheap-vu-duo-for-hardware-development

[danishdude]

Wonder what it's worth. Also, shipping from Sweden to abroad would cost something. Worth it?

[Maxwell]

possibly worth it - can you check out some postage prices at your end also I dont need the remote so you could possibly sell that seperately, as to what the duo is worth with a dead tuner I really dont know

[Larry-G]

well I've just given you some plus rep for that avatar alone. It's bloody great.

[danishdude]

well I've just given you some plus rep for that avatar alone. It's bloody great.Well...might as well get the best out of it, right! :D

[danishdude]

possibly worth it - can you check out some postage prices at your end also I dont need the remote so you could possibly sell that seperately, as to what the duo is worth with a dead tuner I really dont knowYour profile doesnt state where youre located - so i guess it's kinda hard checking rates :wave:

[Stanman]

I believe his in the UK

[Maxwell]

I believe his in the UK

Swindon UK to be exact ;)

[silverfox0786]

guys please make a for sale or whats it worth thread

:)

thats why i never made an offer myself as im intyreseted in the housing for it

[Maxwell]

@Danishdude we can carry on the negotiation on my wanted thread http://www.world-of-satellite.com/showthread.php?16657-cheap-vu-duo-for-hardware-development

[danishdude]

@Danishdude we can carry on the negotiation on my wanted thread http://www.world-of-satellite.com/showthread.php?16657-cheap-vu-duo-for-hardware-developmentDeal. Lets continue overthere.

[danishdude]

guys please make a for sale or whats it worth thread

:)

thats why i never made an offer myself as im intyreseted in the housing for itGood point. I will make a thread in the whats it worh-section. I guess thats a bit easier, if several are interested in the corpse.

UPDATE: Here's the thread -> http://www.world-of-satellite.com/showthread.php?16905-VU-Duo-dead-tuner&p=123227

[Zartmy]

i dont think that PEB is your issue but i may be wrong
and here is your problem

a faulty tuner card


dvb_bcm7335: module license 'Proprietary' taints kernel.
Disabling lock debugging due to kernel taint


Thats just the message you will get when using a close source licensed module under linux. It has nothing todo with a faulty tuner.

[danishdude]

Thats just the message you will get when using a close source licensed module under linux. It has nothing todo with a faulty tuner.NOW i'm getting confused! (...and it has nothing to do with the whizzky in my glass :confused::D)

[Zartmy]

16 months old - and the shop washes it's hands, and tells me i have to handle the problem myself, contacting the distributor directly (Digital Nordic Sweden) - as the warranty ran out four months ago. At the same time, they tell me i shouldnt get my hopes up, as i need to provide futher proof to the problem.(!!?) Apparently the serial-dump, showing the exact problem, is not enough - if you ask them.
What else do they want? What else can i do? Beats me...*sigh* :confused::mad:


Your shop is talking bull, they have to make the service request from digital nordic. States so very clearly on there homepage -
http://www.digitalnordic.se/egensida/rma-service/501

[stick50jr]

Thats just the message you will get when using a close source licensed module under linux. It has nothing todo with a faulty tuner.

I agree, I get this same message even though my VuDuo is serviceable. The following command was used to check whether my usb tuner was being recognised, but I got the 'tainted' kernel message as well:

dmesg | grep dvb

dvb_bcm7335: module license 'Proprietary' taints kernel.
dvb-usb: found a 'Avermedia TwinStar' in cold state, will try to load a firmware
dvb-usb: downloading firmware from file 'dvb-usb-af9035-01.fw'
dvb-usb: found a 'Avermedia TwinStar' in warm state.
dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
dvb-usb: Avermedia TwinStar successfully initialized and connected.
usbcore: registered new interface driver dvb_usb_af9035

Your tuner may be stuffed, but this message doesn't provide any indication.

[danishdude]

I am all ears.
/learning-mode ON

:p

[silverfox0786]

I agree, I get this same message even though my VuDuo is serviceable. The following command was used to check whether my usb tuner was being recognised, but I got the 'tainted' kernel message as well:

dmesg | grep dvb

dvb_bcm7335: module license 'Proprietary' taints kernel.
dvb-usb: found a 'Avermedia TwinStar' in cold state, will try to load a firmware
dvb-usb: downloading firmware from file 'dvb-usb-af9035-01.fw'
dvb-usb: found a 'Avermedia TwinStar' in warm state.
dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
dvb-usb: Avermedia TwinStar successfully initialized and connected.
usbcore: registered new interface driver dvb_usb_af9035

Your tuner may be stuffed, but this message doesn't provide any indication.

agreed but you dont get this straight after


Disabling lock debugging due to kernel taint

[ashehzad]

Hi Guys,

I am new to this forum, i am having problem upgrading firmware on the VU+duo.
I am trying to upgrade BH 1.6.6 to any new 1.6.7,1.7.X but it failed.
It can only accept 1.6.6 :(

I know, i have to upgrade updrade bootloader fthen i have to upgrade firmware but it fails.
Please see the log below. I can also see there are few bad sector on the Flash i see those errors even when i flash 1.6.6 but it runs OK :(

Any idea and help would be highly appreciated.


MEMC-00000000 RW=0000000F WW=00000045 G=00000001 R=00000008 W=00000018
MEMC-00000001 RW=00000010 WW=0000004D G=00000001 R=00000009 W=00000006 #$
3
COPY CODE
A567

BCM97335B0 CFE v2.17, CFE core v2.12, Endian Mode: Little
Build Date: Thu Sep 29 12:01:32 2011 (shcheong@ncsh)
Copyright (C) Broadcom Corporation.

writing vfd

DDR Freq: 395MHz
CPU speed: 405MHz
Memory Config: 32+16 non-UMA
Device Tech: 1Gb
Total memory: 384MB
Boot Device: NAND
ECC: Hamming
Total flash: 128MB

Initializing USB.
USB: Locating Class 09 Vendor 0000 Product 0000: USB Hub
USB: Locating Class 09 Vendor 0000 Product 0000: USB Hub

CFE initialized.

checking usb
Loader:elf Filesys:raw Dev:flash0.kernel File: Options:rootfstype=jffs2 root=/dev/mtdblock0 rw mem=0x8000000 bcmrac=3
Loading: 0x80001000/7024928 0x806b4120/124048 Entry address is 0x80540b60
TP1 Entry Address at 0x80000ffc = 80540b60
Starting program at 0x80540b60

Linux version 3.1.1 (vix@buildpc) (gcc version 4.6.4 20120303 (prerelease) (GCC) ) #1 SMP Sat Oct 20 05:45:24 BST 2012
Fetching vars from bootloader... found 11 vars.
Options: sata=1 enet=1 emac_1=1 no_mdio=0 docsis=0 pci=1 smp=1 moca=0 usb=1
Using 256 MB + 128 MB RAM (from CFE)
CPU revision is: 0002a044 (Brcm4380)
FPU revision is: 00130001
Determined physical RAM map:
memory: 10000000 @ 00000000 (usable)
bmem: adding 112 MB RESERVED region at 144 MB (0x07000000@0x09000000)
Zone PFN ranges:
Normal 0x00000000 -> 0x00010000
Movable zone start PFN for each node
early_node_map[1] active PFN ranges
0: 0x00000000 -> 0x00010000
PERCPU: Embedded 7 pages/cpu @81203000 s4384 r8192 d16096 u32768
Built 1 zonelists in Zone order, mobility grouping on. Total pages: 65024
Kernel command line: bmem=112M ubi.mtd=0 root=ubi0:rootfs rootfstype=ubifs rw console=ttyS0,115200n8 rootflags=sync
PID hash table entries: 1024 (order: 0, 4096 bytes)
Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
Primary instruction cache 32kB, VIPT, 2-way, linesize 64 bytes.
Primary data cache 64kB, 4-way, VIPT, cache aliases, linesize 64 bytes
Memory: 138144k/262144k available (5436k kernel code, 124000k reserved, 1189k data, 236k init, 0k highmem)
Hierarchical RCU implementation.
NR_IRQS:128
Detected MIPS clock frequency: 404 MHz (202.497 MHz counter)
Console: colour dummy device 80x25
Calibrating delay loop... 403.45 BogoMIPS (lpj=201728)
pid_max: default: 32768 minimum: 301
Mount-cache hash table entries: 512
SMP: Booting CPU1...
CPU revision is: 0002a044 (Brcm4380)
FPU revision is: 00130001
Primary instruction cache 32kB, VIPT, 2-way, linesize 64 bytes.
Primary data cache 64kB, 4-way, VIPT, cache aliases, linesize 64 bytes
SMP: CPU1 is running
Brought up 2 CPUs
devtmpfs: initialized
NET: Registered protocol family 16
PCI2.3->SDRAM window: 512 MB
bio: create slab <bio-0> at 0
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
Advanced Linux Sound Architecture Driver Version 1.0.24.
PCI: found device 14e4:8602 on SATA bus, slot 0 (irq 42)
pci 0000:01:00.0: BAR 5: assigned [mem 0x10510000-0x10510fff]
pci 0000:01:00.0: BAR 5: set to [mem 0x10510000-0x10510fff] (PCI address [0x10510000-0x10510fff])
pci 0000:01:00.0: BAR 6: assigned [mem 0x10511000-0x105117ff pref]
Bluetooth: Core ver 2.16
NET: Registered protocol family 31
Bluetooth: HCI device and connection manager initialized
Bluetooth: HCI socket layer initialized
Bluetooth: L2CAP socket layer initialized
Switching to clocksource upg
cfg80211: Calling CRDA to update world regulatory domain
NET: Registered protocol family 2
IP route cache hash table entries: 2048 (order: 1, 8192 bytes)
TCP established hash table entries: 8192 (order: 4, 65536 bytes)
TCP bind hash table entries: 8192 (order: 4, 65536 bytes)
TCP: Hash tables configured (established 8192 bind 8192)
TCP reno registered
UDP hash table entries: 128 (order: 0, 4096 bytes)
UDP-Lite hash table entries: 128 (order: 0, 4096 bytes)
NET: Registered protocol family 1
RPC: Registered named UNIX socket transport module.
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
fuse init (API version 7.17)
msgmni has been set to 269
io scheduler noop registered
io scheduler cfq registered (default)
Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
serial8250.0: ttyS0 at MMIO 0x10400b00 (irq = 22) is a 16550A
console [ttyS0] enabled
serial8250.0: ttyS1 at MMIO 0x10400b40 (irq = 66) is a 16550A
serial8250.0: ttyS2 at MMIO 0x10400b80 (irq = 67) is a 16550A
loop: module loaded
brcm-pm: enabling sata clocks
PCI: Enabling device 0000:01:00.0 (0000 -> 0003)
scsi0 : sata_brcmstb
scsi1 : sata_brcmstb
ata1: SATA max UDMA7 mmio m4096@0x10510000 port 0x10510000 irq 42
ata2: SATA max UDMA7 mmio m4096@0x10510000 port 0x10510100 irq 42
Broadcom STB NAND controller (BrcmNand Controller)
bcmemac: Broadcom STB 10/100 EMAC driver v3.0
bcmemac: registered interface #0 at 0x10080000 as 'eth0' (00:1d:ec:cb:96:39)
bcmemac: not registering interface #1 at 0x10090000 (no PHY detected)
usbcore: registered new interface driver zd1201
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
brcm-pm: enabling usb clocks
ehci-brcm ehci-brcm.0: Broadcom STB EHCI
ehci-brcm ehci-brcm.0: new USB bus registered, assigned bus number 1
ehci-brcm ehci-brcm.0: irq 62, io mem 0x10480300
ehci-brcm ehci-brcm.0: USB 0.0 started, EHCI 1.00
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 2 ports detected
ehci-brcm ehci-brcm.1: Broadcom STB EHCI
ehci-brcm ehci-brcm.1: new USB bus registered, assigned bus number 2
ehci-brcm ehci-brcm.1: irq 57, io mem 0x10480500
ehci-brcm ehci-brcm.1: USB 0.0 started, EHCI 1.00
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 2 ports detected
ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
ohci-brcm ohci-brcm.0: Broadcom STB OHCI
ohci-brcm ohci-brcm.0: new USB bus registered, assigned bus number 3
ohci-brcm ohci-brcm.0: irq 63, io mem 0x10480400
hub 3-0:1.0: USB hub found
hub 3-0:1.0: 2 ports detected
ohci-brcm ohci-brcm.1: Broadcom STB OHCI
ohci-brcm ohci-brcm.1: new USB bus registered, assigned bus number 4
ohci-brcm ohci-brcm.1: irq 64, io mem 0x10480600
hub 4-0:1.0: USB hub found
hub 4-0:1.0: 2 ports detected
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
ata1: SATA link down (SStatus 4 SControl 300)
USB Mass Storage support registered.
mousedev: PS/2 mouse device common for all mice
i2c /dev entries driver
lirc_dev: IR Remote Control driver registered, major 254
IR NEC protocol handler initialized
IR RC5(x) protocol handler initialized
IR RC6 protocol handler initialized
IR JVC protocol handler initialized
IR Sony protocol handler initialized
IR RC5 (streamzap) protocol handler initialized
IR MCE Keyboard/mouse protocol handler initialized
IR LIRC bridge handler initialized
Bluetooth: Generic Bluetooth USB driver ver 0.6
usbcore: registered new interface driver btusb
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
ALSA device list:
No soundcards found.
TCP cubic registered
NET: Registered protocol family 17
Bluetooth: HIDP (Human Interface Emulation) ver 1.2
lib80211: common routines for IEEE802.11 drivers
Registering the dns_resolver key type
EBI CS0: setting up NAND flash (primary)
mtd->oobsize=0, mtd->eccOobSize=0
NAND_CS_NAND_XOR=00000001
B4: NandSelect=40000101, nandConfig=55042200, chipSelect=0
brcmnand_read_id: CS0: dev_id=ecf10095
After: NandSelect=40000101, nandConfig=55042200
Block size=00020000, erase shift=17
NAND Config: Reg=55042200, chipSize=128 MB, blockSize=128K, erase_shift=11
busWidth=1, pageSize=2048B, page_shift=11, page_mask=000007ff
BrcmNAND mfg ec f1 Samsung K9F1G08U0A 128MB on CS0

Found NAND on CS0: ACC=d3000000, cfg=55042200, flashId=ecf10095, tim1=4232222d, tim2=00000d94
BrcmNAND version = 0x0201 128MB @00000000
B4: NandSelect=40000101, nandConfig=55042200, chipSelect=0
brcmnand_read_id: CS0: dev_id=ecf10095
After: NandSelect=40000101, nandConfig=55042200
Found NAND flash on Chip Select 0, chipSize=128MB, usable size=128MB, base=0
brcmnand_scan: B4 nand_select = 40000101
brcmnand_scan: After nand_select = 40000101
page_shift=11, bbt_erase_shift=17, chip_shift=27, phys_erase_shift=17
Brcm NAND controller version = 2.1 NAND flash size 128MB @18000000
ECC layout=brcmnand_oob_bch4_4k
brcmnand_scan: mtd->oobsize=64
brcmnand_scan: oobavail=50, eccsize=512, writesize=2048
brcmnand_scan, eccsize=512, writesize=2048, eccsteps=4, ecclevel=15, eccbytes=3
-->brcmnand_default_bbt
brcmnand_default_bbt: bbt_td = bbt_main_descr
Creating 7 MTD partitions on "brcmnand.0":
0x000000000000-0x000007600000 : "rootfs"
0x000007600000-0x000007a00000 : "kernel"
0x000007a00000-0x000007c00000 : "boot"
0x000007c00000-0x000007d00000 : "cfe"
0x000007d00000-0x000007d80000 : "mac"
0x000007d80000-0x000007e00000 : "env"
0x000007e00000-0x000007f00000 : "nvm"
UBI: attaching mtd0 to ubi0
UBI: physical eraseblock size: 131072 bytes (128 KiB)
UBI: logical eraseblock size: 126976 bytes
UBI: smallest flash I/O unit: 2048
UBI: VID header offset: 2048 (aligned 2048)
UBI: data offset: 4096
ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
ata2.00: ATA-8: ST3500312CS, SC13, max UDMA/133
ata2.00: 976773168 sectors, multi 0: LBA48 NCQ (depth 0/32)
ata2.00: configured for UDMA/133
scsi 1:0:0:0: Direct-Access ATA ST3500312CS SC13 PQ: 0 ANSI: 5
sd 1:0:0:0: [sda] 976773168 512-byte logical blocks: (500 GB/465 GiB)
sd 1:0:0:0: Attached scsi generic sg0 type 0
sd 1:0:0:0: [sda] Write Protect is off
sd 1:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sda: sda1
sd 1:0:0:0: [sda] Attached SCSI disk
UBI: max. sequence number: 93
UBI: attached mtd0 to ubi0
UBI: MTD device name: "rootfs"
UBI: MTD device size: 118 MiB
UBI: number of good PEBs: 941
UBI: number of bad PEBs: 3
UBI: number of corrupted PEBs: 0
UBI: max. allowed volumes: 128
UBI: wear-leveling threshold: 4096
UBI: number of internal volumes: 1
UBI: number of user volumes: 1
UBI: available PEBs: 0
UBI: total number of reserved PEBs: 941
UBI: number of PEBs reserved for bad PEB handling: 9
UBI: max/mean erase counter: 2/0
UBI: image sequence number: 1615474374
UBI: background thread "ubi_bgt0d" started, PID 45
UBIFS: parse sync
UBIFS: recovery needed
UBIFS: recovery completed
UBIFS: mounted UBI device 0, volume 0, name "rootfs"
UBIFS: file system size: 116436992 bytes (113708 KiB, 111 MiB, 917 LEBs)
UBIFS: journal size: 9023488 bytes (8812 KiB, 8 MiB, 72 LEBs)
UBIFS: media format: w4/r0 (latest is w4/r0)
UBIFS: default compressor: lzo
UBIFS: reserved for root: 0 bytes (0 KiB)
VFS: Mounted root (ubifs filesystem) on device 0:13.
devtmpfs: mounted
Freeing unused kernel memory: 236k freed
INIT: version 2.88 booting
EXT4-fs (sda1): warning: maximal mount count reached, running e2fsck is recommended
EXT4-fs (sda1): recovery complete
EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null)
procmk_init
dvb_bcm7335: module license 'Proprietary' taints kernel.
Disabling lock debugging due to kernel taint
DVB: registering new adapter (bm750)
bcm7335: hotplug_callback():
Hotplug - status.connected 0
CPU 0 Unable to handle kernel paging request at virtual address c06c7790, epc == c06c7790, ra == 80074244
Oops[#1]:
Cpu 0
$ 0 : 00000000 10008700 c06c7790 00060000
$ 4 : 0000000d c0abe9e4 00000000 00000048
$ 8 : 10008700 1000001f 00000000 00000800
$12 : 00000000 80678398 0000000a 7faa4718
$16 : 88496400 00010000 00000000 00000000
$20 : 0000000d 8063ed80 80640000 806c0000
$24 : 0000004f 779fce28
$28 : 884d2000 884d3778 805d1f64 80074244
Hi : 00000000
Lo : 00004e84
epc : c06c7790 0xc06c7790
Tainted: P
ra : 80074244 handle_irq_event_percpu+0x78/0x310
Status: 10008302 KERNEL EXL
Cause : 00800008
BadVA : c06c7790
PrId : 0002a044 (Brcm4380)
Modules linked in: procmk
Process modprobe (pid: 96, threadinfo=884d2000, task=88de5218, tls=77b79490)
Stack : 380754db 0000000a 10008700 00000000 81203580 80648160 8063ed80 00010000
00000001 00000020 00001400 fffff7ff 88ec8480 806d0000 88eb4400 8007452c
81203508 806480a0 00000100 8007b07c 00000100 8063e640 8063ed80 800773d0
00000000 8063e664 00000100 8063e640 0000000a 00000000 0000000d 80073964
88eb4400 80077f48 806b3b40 8002523c 00000000 80006854 00000009 00000000
...
Call Trace:
[<8007452c>] handle_irq_event+0x50/0x84
[<8007b07c>] __rcu_process_callbacks+0x60/0x478
[<800773d0>] handle_level_irq+0xd8/0x188
[<80073964>] generic_handle_irq+0x34/0x54
[<80077f48>] handle_percpu_irq+0x8c/0xc0
[<8002523c>] task_tick_fair+0x58/0x170
[<80006854>] do_IRQ+0x18/0x24
[<80002324>] brcm_intc_dispatch+0x90/0x220
[<8003a070>] do_softirq+0xa4/0xac
[<80002710>] plat_irq_dispatch+0xc8/0x104
[<8002adbc>] find_busiest_group+0x208/0xa64
[<80004a84>] ret_from_irq+0x0/0x4
[<80358b60>] brcmnand_cache_is_valid.constprop.11+0x74/0x268
[<8029daf0>] __udelay+0x40/0x50
[<803579b8>] brcmnand_ctrl_writeAddr+0xa4/0xe8
[<8035abbc>] brcmnand_ctrl_posted_read_cache+0xd8/0x8fc
[<803577f0>] brcmnand_read_page+0x110/0x234
[<80357dbc>] brcmnand_release_device+0x38/0x60
[<80359920>] brcmnand_do_read_ops+0xfc/0x2c0
[<80359bac>] brcmnand_read+0xc8/0x13c
[<80335558>] part_read+0x8c/0x138
[<80367cc4>] ubi_eba_read_leb+0x194/0x320
[<80369d48>] ubi_io_read+0x98/0x1bc
[<80367c60>] ubi_eba_read_leb+0x130/0x320
[<80367088>] ubi_leb_read+0xdc/0x164
[<802199b0>] ubifs_leb_read+0x34/0xa4
[<80004358>] brcmstb_send_ipi_mask+0x30/0x70
[<8007b07c>] __rcu_process_callbacks+0x60/0x478
[<8021c68c>] fallible_read_node+0x64/0x1b8
[<8021dc64>] ubifs_lookup_level0+0xd4/0x1f8
[<80550000>] __kprobes_text_end+0x13b8/0x1670
[<80012890>] local_r4k_flush_data_cache_page+0x0/0x10
[<8021dea4>] ubifs_tnc_locate+0x11c/0x244
[<80210500>] do_readpage+0x2d8/0x604
[<800870e8>] __alloc_pages_nodemask+0xec/0x630
[<80212a90>] ubifs_readpage+0x60/0x430
[<8007fd50>] add_to_page_cache_locked+0x9c/0x1cc
[<800825c4>] filemap_fault+0x434/0x5c0
[<800a04ac>] __do_fault+0x8c/0x708
[<800a439c>] handle_pte_fault+0x128/0xa7c
[<800a0c28>] tlb_flush_mmu+0x78/0xa4
[<800a1100>] free_pgtables+0xd0/0x110
[<800a4db4>] handle_mm_fault+0xc4/0x120
[<80010838>] do_page_fault+0x128/0x330
[<80022f2c>] set_next_entity+0x40/0x8c
[<800253e8>] pick_next_task_fair+0x94/0x110
[<800a75a0>] remove_vma+0x64/0xac
[<8054ae58>] __schedule+0x118/0x9cc
[<800a87c4>] do_munmap+0x1cc/0x344
[<800a9ec4>] sys_munmap+0x4c/0x68
[<80004a60>] ret_from_exception+0x0/0x24


Code: (Bad address in epc)

---[ end trace e65f297c518e5117 ]---
Kernel panic - not syncing: Fatal exception in interrupt
Rebooting in 180 seconds..

[judge]

original box or clone?

[srprizze]

How to flash / Upgrade Vu+ Uno via USB memory stick
How to flash a VU+ Uno using a USB stick
Quick guide how to flash a VU+ Uno receiver with a USB stick. Tools required are just your favourite image and at least a 128mb memory stick formatted FAT32.

1. Format you memory stick on you PC FAT32.
2. Create a directory in called vuplus.
3. Within the the vuplus directory create another folder called uno.
4. Unzip the USB upgrade files (4) into that directory.
The 4 files are :
boot_cfe_auto.jffs2
kernel_cfe_auto.bin
root_cfe_auto.jffs2
splash_cfe_auto.bin
5. Power off your VU+ Uno.
6. Insert memory stick into front USB slot.
7. Power on your VU+ Uno and follow the on screen instructions.

On Screen Instructions will include press ch- on the Uno [not remote] to initiate flash
This must be done within 10 seconds as i have found or it will boot box as normal
once done it will advise you to remove USB Stick and reboot

Thats it your done.

[finbarr]

Hi guys,

I have a similar issue to the OP when using my Vu Duo running Vix 808. I've re flashed a couple of times, but still see the issue.

Problem: i have a power timer set to reboot the box during the night, but once or twice a week, the box is stuck with the 'Starting...' Message on the front panel. (no red right though)

Box details:
- Genuine duo bought from world of sat.
- I have a USB key in the back, formatted by Vix. With an active 64MG swap, and holds EPG data from XMLTV for 28,2E + picons.
- I have a Sony PlayTV DVB-T dual tuner plugged in.

Plugins installed:
- MyMatrix active skin
- Ondemand
- ocram shd picons
- dib0700 drivers from feeds.

I don't have logs from a time when it happened, but I do have logs from a good startup which might help. I will post those in a minute. Some interesting things I see in the logs (are these bad??)

root@vuduo:~# cat /var/log/messages | grep -i peb
Jan 1 01:00:31 vuduo user.notice kernel: UBI: number of good PEBs: 939
Jan 1 01:00:31 vuduo user.notice kernel: UBI: number of bad PEBs: 5
Jan 1 01:00:31 vuduo user.notice kernel: UBI: number of corrupted PEBs: 0
Jan 1 01:00:31 vuduo user.notice kernel: UBI: available PEBs: 0
Jan 1 01:00:31 vuduo user.notice kernel: UBI: total number of reserved PEBs: 939
Jan 1 01:00:31 vuduo user.notice kernel: UBI: number of PEBs reserved for bad PEB handling: 9
root@vuduo:~#



cat /var/log/messages | grep -i "kernel t"
Jan 1 01:00:31 vuduo user.warn kernel: Disabling lock debugging due to kernel taint
root@vuduo:~#

[finbarr]

Log

32974

[judge]

Could be off track here, but last lines of that log read:

Mar 5 22:09:31 vuduo daemon.notice automount[655]: >> mount: mounting /dev/logs on /autofs/logs failed: No such file or directory
Mar 5 22:09:31 vuduo daemon.err automount[655]: mount(generic): failed to mount /dev/logs (type auto) on /autofs/logs
Mar 5 22:09:31 vuduo daemon.err automount[655]: failed to mount /autofs/logs

Have you now or ever had network mounts set-up on the Duo?

[finbarr]

Nope, never set up shares or mounts.

[mickyblueys]

I had this issue on both my duo's, it is quite common, to get around the issue, I cancelled my reboot power timer and set it to just restart the gui instead, this resets the boxes clock so that my epg and autobouquets still do there daily updates. ......So now I haven't had the ...starting....problem since!

Hope this helps.

Sent from my GT-I9195 using Tapatalk

[finbarr]

Just to report that your fix has worked beautifully after more than a week or testing. Not a single Starting... message staying put. Cheers MickyB