izmit escort escort ankara adana escort

 FAQ •  Search •  Register •  Login 

All times are UTC + 1 hour [ DST ]




Post new topic Reply to topic  [ 9 posts ] 
Author Message
 Post subject: sama5d36 random silent boot failure
PostPosted: Tue Aug 08, 2017 1:10 pm 
Offline

Joined: Thu Nov 07, 2013 10:59 am
Posts: 9
Hi list

I am using Atmel sama5d36 with buildroot, kernel 4.4 on a Shiratech AT-501 card.
I have been doing repeated startup tests and every now and then the boot stops silently, ending with:

"ubi0: background thread "ubi_bgt0d" started, PID 77
at91_rtc fffffeb0.rtc: setting system clock to 2007-01-01 00:00:08 UTC (1167609608)"

I have tried to increase the kernel log level to 7 in .config to get more debug but the startup log is always the same.

Does anyone have a useful hint regarding this issue?

Regards
Gudjon

Ps. I tried to add the full bootlog but .txt extension isn't allowed.


Top
 Profile  
Reply with quote  
 Post subject: Re: sama5d36 random silent boot failure
PostPosted: Tue Aug 08, 2017 9:27 pm 
Offline

Joined: Thu Apr 19, 2007 10:15 pm
Posts: 1470
Location: USA
gudjon wrote:
I have been doing repeated startup tests and every now and then the boot stops silently, ending with:

"ubi0: background thread "ubi_bgt0d" started, PID 77
at91_rtc fffffeb0.rtc: setting system clock to 2007-01-01 00:00:08 UTC (1167609608)"
Seeing just the last two lines is not sufficient to provide any analysis.

You report that the boot stops occasionally, so then that means that the boot does complete normally otherwise.
Since the kernel performs its initialization in a deterministic order for a given configuration, you know what should be displayed next.
Looking at (and providing) those subsequent lines is salient information that may point to what is hanging.

gudjon wrote:
I have tried to increase the kernel log level to 7 in .config to get more debug but the startup log is always the same.
Does "try" mean success or failure in making this change?
You shouldn't expect any KERN_DEBUG messages unless you compile with DEBUG defined.
BTW You don't have to rebuild the kernel just to change the defualt log level.
It can be set with the kernel command line parameter "loglevel=n".

gudjon wrote:
Ps. I tried to add the full bootlog but .txt extension isn't allowed.
If there are any clues in there that can help resolve this issue, then we won't see them (e.g. the UBI information is probably salient).
There are free cloud services.

Regards


Top
 Profile  
Reply with quote  
 Post subject: Re: sama5d36 random silent boot failure
PostPosted: Wed Aug 09, 2017 10:21 am 
Offline

Joined: Thu Nov 07, 2013 10:59 am
Posts: 9
Thanks for the answer blue_z

The board boots normally without problems on the average 50 times and then stops at the point I show. Full bootlog is inserted below.
Min value of successful boots is 2, max is 223.

I did change loglevel=7 in the kernel config.
CONFIG_MESSAGE_LOGLEVEL_DEFAULT=7
I also tried to set it in the u-boot command line.
setenv bootcmd "nand read 0x21000000 0x180000 0x80000;nand read 0x22000000 0x200000 0x600000;bootm 0x22000000 - 0x21000000;loglevel=7"
But there is no difference in the debug port logging.

Next tests will be to power on and off the AT-501 in the Shiratech motherboard and see if it changes the behaviour. But having some clue on how to get more debug information would be splendid before I start.

The full bootlog is here below. I don't find any errors explaining the failure.

Booting Linux on physical CPU 0x0
Linux version 4.4.52-01044-g97327a0bf237 (gudjon@hekla) (gcc version 4.9.3 (Buildroot 2016.02-g5c20640) ) #2 Wed Jun 7 08:58:18 CEST 2017
CPU: ARMv7 Processor [410fc051] revision 1 (ARMv7), cr=10c53c7d
CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
Machine model: Atmel SAMA5D36-EK
cma: Reserved 64 MiB at 0x28000000
Memory policy: Data cache writeback
CPU: All CPU(s) started in SVC mode.
Built 1 zonelists in Zone order, mobility grouping off. Total pages: 65024
Kernel command line: console=ttyS0,115200 mtdparts=atmel_nand:8M(bootstrap/uboot/kernel)ro,-(rootfs) rootfstype=ubifs ubi.mtd=1 root=ubi0:rootfs rw
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)
Memory: 188416K/262144K available (4140K kernel code, 158K rwdata, 892K rodata, 212K init, 170K bss, 8192K reserved, 65536K cma-reserved)
Virtual kernel memory layout:
vector : 0xffff0000 - 0xffff1000 ( 4 kB)
fixmap : 0xffc00000 - 0xfff00000 (3072 kB)
vmalloc : 0xd0800000 - 0xff800000 ( 752 MB)
lowmem : 0xc0000000 - 0xd0000000 ( 256 MB)
.text : 0xc0008000 - 0xc04f2384 (5033 kB)
.init : 0xc04f3000 - 0xc0528000 ( 212 kB)
.data : 0xc0528000 - 0xc054fbe0 ( 159 kB)
.bss : 0xc054fbe0 - 0xc057a6bc ( 171 kB)
NR_IRQS:16 nr_irqs:16 16
clocksource: pit: mask: 0xfffffff max_cycles: 0xfffffff, max_idle_ns: 14479245754 ns
sched_clock: 32 bits at 100 Hz, resolution 10000000ns, wraps every 21474836475000000ns
Console: colour dummy device 80x30
Calibrating delay loop... 351.43 BogoMIPS (lpj=1757184)
pid_max: default: 32768 minimum: 301
Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
CPU: Testing write buffer coherency: ok
Setting up static identity map for 0x20008200 - 0x20008258
devtmpfs: initialized
VFP support v0.3: implementor 41 architecture 2 part 30 variant 5 rev 1
clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
futex hash table entries: 256 (order: -1, 3072 bytes)
pinctrl core: initialized pinctrl subsystem
NET: Registered protocol family 16
DMA: preallocated 256 KiB pool for atomic coherent allocations
cpuidle: using governor ladder
cpuidle: using governor menu
AT91: Detected SoC family: sama5d3
AT91: Detected SoC: sama5d36, revision 2
gpio-at91 fffff200.gpio: at address d0818200
gpio-at91 fffff400.gpio: at address d081a400
gpio-at91 fffff600.gpio: at address d081c600
gpio-at91 fffff800.gpio: at address d081e800
gpio-at91 fffffa00.gpio: at address d0820a00
pinctrl-at91 ahb:apb:pinctrl@fffff200: initialized AT91 pinctrl driver
clocksource: tcb_clksrc: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 115833966437 ns
at_hdmac ffffe600.dma-controller: Atmel AHB DMA Controller ( cpy set slave sg-cpy ), 8 channels
at_hdmac ffffe800.dma-controller: Atmel AHB DMA Controller ( cpy set slave sg-cpy ), 8 channels
SCSI subsystem initialized
at91_i2c f0018000.i2c: using dma0chan0 (tx) and dma0chan1 (rx) for DMA transfers
at91_i2c f0018000.i2c: AT91 i2c bus driver (hw version: 0x402).
at91_i2c f801c000.i2c: using dma1chan0 (tx) and dma1chan1 (rx) for DMA transfers
at91_i2c f801c000.i2c: AT91 i2c bus driver (hw version: 0x402).
clocksource: Switched to clocksource tcb_clksrc
NET: Registered protocol family 2
TCP established hash table entries: 2048 (order: 1, 8192 bytes)
TCP bind hash table entries: 2048 (order: 1, 8192 bytes)
TCP: Hash tables configured (established 2048 bind 2048)
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 named UNIX socket transport module.
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
NET: Registered protocol family 38
io scheduler noop registered (default)
f001c000.serial: ttyS1 at MMIO 0xf001c000 (irq = 29, base_baud = 4125000) is a ATMEL_SERIAL
f0020000.serial: ttyS2 at MMIO 0xf0020000 (irq = 30, base_baud = 4125000) is a ATMEL_SERIAL
f0024000.serial: ttyS5 at MMIO 0xf0024000 (irq = 31, base_baud = 4125000) is a ATMEL_SERIAL
f8020000.serial: ttyS3 at MMIO 0xf8020000 (irq = 36, base_baud = 4125000) is a ATMEL_SERIAL
f8024000.serial: ttyS4 at MMIO 0xf8024000 (irq = 37, base_baud = 4125000) is a ATMEL_SERIAL
ffffee00.serial: ttyS0 at MMIO 0xffffee00 (irq = 44, base_baud = 8250000) is a ATMEL_SERIAL
console [ttyS0] enabled
f8028000.serial: ttyS6 at MMIO 0xf8028000 (irq = 54, base_baud = 4125000) is a ATMEL_SERIAL
brd: module loaded
loop: module loaded
atmel_nand_nfc 70000000.nfc: NFC is probed.
atmel_nand 60000000.nand: Use On Flash BBT
atmel_nand 60000000.nand: Using dma0chan2 for DMA transfers.
nand: device found, Manufacturer ID: 0x98, Chip ID: 0xda
nand: Toshiba NAND 256MiB 3,3V 8-bit
nand: 256 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 64
atmel_nand 60000000.nand: can't detect min. ECC, assume 2 bits in 512 bytes
atmel_nand 60000000.nand: Initialize PMECC params, cap: 2, sector: 512
atmel_nand 60000000.nand: Using NFC Sram read
Bad block table found at page 131008, version 0x01
Bad block table found at page 130944, version 0x01
2 cmdlinepart partitions found on MTD device atmel_nand
Creating 2 MTD partitions on "atmel_nand":
0x000000000000-0x000000800000 : "bootstrap/uboot/kernel"
0x000000800000-0x000010000000 : "rootfs"
atmel_spi f0004000.spi: version: 0x213
atmel_spi f0004000.spi: DMA TX channel not available, SPI unable to use DMA
atmel_spi f0004000.spi: Atmel SPI Controller using PIO only
atmel_spi f0004000.spi: Atmel SPI Controller at 0xf0004000 (irq 26)
atmel_spi f8008000.spi: version: 0x213
atmel_spi f8008000.spi: Using dma1chan2 (tx) and dma1chan3 (rx) for DMA transfers
atmel_spi f8008000.spi: Atmel SPI Controller at 0xf8008000 (irq 33)
libphy: MACB_mii_bus: probed
macb f0028000.ethernet eth0: Cadence GEM rev 0x00020119 at 0xf0028000 irq 51 (e8:99:5a:ff:00:ff)
macb f0028000.ethernet eth0: attached PHY driver [Micrel KSZ9031 Gigabit PHY] (mii_bus:phy_addr=f0028000.etherne:01, irq=113)
libphy: MACB_mii_bus: probed
macb f802c000.ethernet eth1: Cadence MACB rev 0x0001010c at 0xf802c000 irq 52 (e8:99:5a:ff:01:00)
macb f802c000.ethernet eth1: attached PHY driver [Generic PHY] (mii_bus:phy_addr=f802c000.etherne:01, irq=-1)
at91_i2c f0018000.i2c: controller timed out
qt1070 1-001b: can not read register, returned -110
qt1070 1-001b: ID -110 not supported
rtc rtc0: alarm rollover not handled
rtc rtc0: invalid alarm value: 1900-1-1 0:0:0
at91_rtc fffffeb0.rtc: rtc core: registered fffffeb0.rtc as rtc0
at91_rtc fffffeb0.rtc: AT91 Real Time Clock driver.
rtc-ds1307 2-0068: rtc core: registered ds1339 as rtc1
i2c /dev entries driver
AT91: Starting after wakeup
at91_wdt fffffe40.watchdog: watchdog is disabled
at91_wdt: probe of fffffe40.watchdog failed with error -22
sdhci: Secure Digital Host Controller Interface driver
sdhci: Copyright(c) Pierre Ossman
pinctrl-at91 ahb:apb:pinctrl@fffff200: pin pioD17 already requested by f001c000.serial; cannot claim for f0000000.mmc
pinctrl-at91 ahb:apb:pinctrl@fffff200: pin-113 (f0000000.mmc) status -22
pinctrl-at91 ahb:apb:pinctrl@fffff200: could not request pin 113 (pioD17) from group mmc0_cd on device ahb:apb:pinctrl@fffff200
atmel_mci f0000000.mmc: Error applying setting, reverse things back
atmel_mci f0000000.mmc: version: 0x505
atmel_mci f0000000.mmc: using dma0chan3 for DMA transfers
atmel_mci f0000000.mmc: Atmel MCI controller at 0xf0000000 irq 25, 1 slots
atmel_mci f8000000.mmc: version: 0x505
atmel_mci f8000000.mmc: using dma1chan4 for DMA transfers
mmc0: host does not support reading read-only switch, assuming write-enable
atmel_mci f8000000.mmc: Atmel MCI controller at 0xf8000000 irq 32, 1 slots
sdhci-pltfm: SDHCI platform and OF driver helper
atmel_aes f8038000.aes: version: 0x135
mmc0: new high speed SD card at address 1234
mmcblk0: mmc0:1234 SA02G 1.85 GiB
mmcblk0: p1
atmel_aes f8038000.aes: Atmel AES - Using dma1chan5, dma1chan6 for DMA transfers
atmel_sha f8034000.sha: version: 0x410
atmel_sha f8034000.sha: using dma1chan7 for DMA transfers
atmel_sha f8034000.sha: Atmel SHA1/SHA256/SHA224/SHA384/SHA512
atmel_tdes f803c000.tdes: version: 0x701
atmel_tdes f803c000.tdes: no DMA channel available
atmel_tdes f803c000.tdes: initialization failed.
atmel_tdes: probe of f803c000.tdes failed with error -12
iio iio:device0: Resolution used: 12 bits
input: at91_adc as /devices/soc0/ahb/ahb:apb/f8018000.adc/input/input0
NET: Registered protocol family 10
sit: IPv6 over IPv4 tunneling driver
NET: Registered protocol family 17
ubi0: default fastmap pool size: 95
ubi0: default fastmap WL pool size: 47
ubi0: attaching mtd1
random: nonblocking pool is initialized
ubi0: scanning is finished
ubi0: attached mtd1 (name "rootfs", size 248 MiB)
ubi0: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
ubi0: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
ubi0: VID header offset: 2048 (aligned 2048), data offset: 4096
ubi0: good PEBs: 1980, bad PEBs: 4, corrupted PEBs: 0
ubi0: user volume: 1, internal volumes: 1, max. volumes count: 128
ubi0: max/mean erase counter: 8/5, WL threshold: 4096, image sequence number: 1692838868
ubi0: available PEBs: 0, total reserved PEBs: 1980, PEBs reserved for bad PEB handling: 36
ubi0: background thread "ubi_bgt0d" started, PID 77
at91_rtc fffffeb0.rtc: setting system clock to 2007-01-01 00:00:08 UTC (1167609608)

Regards
Gudjon


Top
 Profile  
Reply with quote  
 Post subject: Re: sama5d36 random silent boot failure
PostPosted: Thu Aug 10, 2017 1:06 am 
Offline

Joined: Thu Apr 19, 2007 10:15 pm
Posts: 1470
Location: USA
One more time, what would display after those "last" lines on a successful boot?


Top
 Profile  
Reply with quote  
 Post subject: Re: sama5d36 random silent boot failure
PostPosted: Thu Aug 10, 2017 12:08 pm 
Offline

Joined: Thu Nov 07, 2013 10:59 am
Posts: 9
I'm sorry for having misunderstood your request. Below are lines from a successful boot (50 times more likely than a failed boot).

I did remove the at91_rtc kernel driver but no change in boot failure frequency.

The UBI filesystem is a prime suspect. Is it sensible to test if jffs2 makes any change?


sit: IPv6 over IPv4 tunneling driver
NET: Registered protocol family 17
ubi0: default fastmap pool size: 95
ubi0: default fastmap WL pool size: 47
ubi0: attaching mtd1
random: nonblocking pool is initialized
ubi0: scanning is finished
ubi0: attached mtd1 (name "rootfs", size 248 MiB)
ubi0: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
ubi0: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
ubi0: VID header offset: 2048 (aligned 2048), data offset: 4096
ubi0: good PEBs: 1980, bad PEBs: 4, corrupted PEBs: 0
ubi0: user volume: 1, internal volumes: 1, max. volumes count: 128
ubi0: max/mean erase counter: 13/7, WL threshold: 4096, image sequence number: 1692838868
ubi0: available PEBs: 0, total reserved PEBs: 1980, PEBs reserved for bad PEB handling: 36
ubi0: background thread "ubi_bgt0d" started, PID 79
rtc-ds1307 2-0068: setting system clock to 2017-08-10 07:53:14 UTC (1502351594)
########## The booting process stops here occasionally ############
UBIFS (ubi0:0): background thread "ubifs_bgt0_0" started, PID 81
UBIFS (ubi0:0): recovery needed
UBIFS (ubi0:0): recovery completed
UBIFS (ubi0:0): UBIFS: mounted UBI device 0, volume 0, name "rootfs"
UBIFS (ubi0:0): LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
UBIFS (ubi0:0): FS size: 147165184 bytes (140 MiB, 1159 LEBs), journal size 9023488 bytes (8 MiB, 72 LEBs)
UBIFS (ubi0:0): reserved for root: 0 bytes (0 KiB)
UBIFS (ubi0:0): media format: w4/r0 (latest is w4/r0), UUID DE92D88B-2AA2-4756-906B-FA3E2E98F272, small LPT model
VFS: Mounted root (ubifs filesystem) on device 0:13.
devtmpfs: mounted
Freeing unused kernel memory: 212K (c04f3000 - c0528000)
FAT-fs (mmcblk0p1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
Starting logging: OK
Setting GPIOS... done
Starting ResetButton... done
Initializing random number generator... done.
Starting network...
IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
udhcpc: option -h NAME is deprecated, use -x hostname:NAME
udhcpc (v1.24.1) started
Sending discover...
macb f802c000.ethernet eth1: link up (100/Full)
macb f0028000.ethernet eth0: link up (100/Full)
IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Sending discover...
Sending select for 192.168.1.105...
Lease of 192.168.1.105 obtained, lease time 86400
deleting routers
adding dns 192.168.0.1
adding dns 192.168.1.1

Regards
Gudjon


Top
 Profile  
Reply with quote  
 Post subject: Re: sama5d36 random silent boot failure
PostPosted: Fri Aug 11, 2017 3:02 am 
Offline

Joined: Thu Apr 19, 2007 10:15 pm
Posts: 1470
Location: USA
gudjon wrote:
Below are lines from a successful boot (50 times more likely than a failed boot).
...
The UBI filesystem is a prime suspect. Is it sensible to test if jffs2 makes any change?
You may be conflating UBI volume management with UBIFS (which may not be in the picture yet when the kernel hangs).

To confirm that UBI or UBIFS is the culprit, try inserting the option "initcall_debug" (and "loglevel=8") to the kernel command line (i.e via the bootargs variable in U-Boot).
When the kernel hangs, the last module called should be revealed.

A next step could be to make the "ubi_bgt0d" or "ubifs_bgt0_0" verbose, but maybe the "initcall_debug" output will produce a different suspect (e.g. pid 80).

What is this SoM installed in, a custom motherboard or the Shiratech carrier board?

Regards


Top
 Profile  
Reply with quote  
 Post subject: Re: sama5d36 random silent boot failure
PostPosted: Mon Aug 14, 2017 11:00 am 
Offline

Joined: Thu Nov 07, 2013 10:59 am
Posts: 9
Hi blue_z

Many thanks. I will test this as soon as I get back to work, 21'st of August.

blue_z wrote:
What is this SoM installed in, a custom motherboard or the Shiratech carrier board?

It is a system on Module that can be found here http://www.shiratech.com/products/at-501/ and they make a carrier board for testing but mainly I use the SoM on my own carrier board which I have been testing for any hardware glitches.

Regards
Gudjon


Top
 Profile  
Reply with quote  
 Post subject: Re: sama5d36 random silent boot failure
PostPosted: Mon Aug 21, 2017 10:07 pm 
Offline

Joined: Thu Nov 07, 2013 10:59 am
Posts: 9
Thanks blue_z

This initcall_debug worked like charm.
Now I get this debug information when the device stops.

initcall tk_debug_sleep_time_init+0x0/0x50 returned 0 after 17 usecs
calling fault_around_debugfs+0x0/0x4c @ 1
initcall fault_around_debugfs+0x0/0x4c returned 0 after 32 usecs
calling cma_debugfs_init+0x0/0x19c @ 1
initcall cma_debugfs_init+0x0/0x19c returned 0 after 110 usecs
calling ubifs_init+0x0/0xd8 @ 1
initcall ubifs_init+0x0/0xd8 returned 0 after 1067 usecs
calling prandom_reseed+0x0/0x70 @ 1
initcall prandom_reseed+0x0/0x70 returned 0 after 54 usecs
calling deferred_probe_initcall+0x0/0x88 @ 1
initcall deferred_probe_initcall+0x0/0x88 returned 0 after 439 usecs
calling ubi_init+0x0/0x268 @ 1
ubi0: default fastmap pool size: 95
ubi0: default fastmap WL pool size: 47
ubi0: attaching mtd1
random: nonblocking pool is initialized
ubi0: scanning is finished
ubi0: attached mtd1 (name "Partition_001", size 248 MiB)
ubi0: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
ubi0: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
ubi0: VID header offset: 2048 (aligned 2048), data offset: 4096
ubi0: good PEBs: 1980, bad PEBs: 4, corrupted PEBs: 0
ubi0: user volume: 1, internal volumes: 1, max. volumes count: 128
ubi0: max/mean erase counter: 13/7, WL threshold: 4096, image sequence number: 1692838868
ubi0: available PEBs: 0, total reserved PEBs: 1980, PEBs reserved for bad PEB handling: 36
ubi0: background thread "ubi_bgt0d" started, PID 79
initcall ubi_init+0x0/0x268 returned 0 after 1022900 usecs
calling gpio_keys_init+0x0/0x10 @ 1
initcall gpio_keys_init+0x0/0x10 returned 0 after 242 usecs
calling rtc_hctosys+0x0/0xf8 @ 1
rtc-ds1307 2-0068: setting system clock to 2017-08-21 19:39:47 UTC (1503344387)
initcall rtc_hctosys+0x0/0xf8 returned 0 after 7919 usecs
calling of_fdt_raw_init+0x0/0x74 @ 1
initcall of_fdt_raw_init+0x0/0x74 returned 0 after 660 usecs
calling clk_debug_init+0x0/0x12c @ 1
initcall clk_debug_init+0x0/0x12c returned 0 after 3765 usecs
calling register_sk_filter_ops+0x0/0x8 @ 1
initcall register_sk_filter_ops+0x0/0x8 returned 0 after 0 usecs
calling tcp_congestion_default+0x0/0xc @ 1
initcall tcp_congestion_default+0x0/0xc returned 0 after 3 usecs
calling ip_auto_config+0x0/0x103c @ 1
initcall ip_auto_config+0x0/0x103c returned 0 after 23 usecs
calling regulator_init_complete+0x0/0x48 @ 1
initcall regulator_init_complete+0x0/0x48 returned 0 after 6 usecs
calling clk_disable_unused+0x0/0x138 @ 1

### Without a stop, the next lines would be ####

initcall clk_disable_unused+0x0/0x138 returned 0 after 124 usecs
UBIFS (ubi0:0): background thread "ubifs_bgt0_0" started, PID 81
UBIFS (ubi0:0): recovery needed
UBIFS (ubi0:0): recovery completed
UBIFS (ubi0:0): UBIFS: mounted UBI device 0, volume 0, name "rootfs"
UBIFS (ubi0:0): LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
UBIFS (ubi0:0): FS size: 147165184 bytes (140 MiB, 1159 LEBs), journal size 9023488 bytes (8 MiB, 72 LEBs)
UBIFS (ubi0:0): reserved for root: 0 bytes (0 KiB)
UBIFS (ubi0:0): media format: w4/r0 (latest is w4/r0), UUID DE92D88B-2AA2-4756-906B-FA3E2E98F272, small LPT model
VFS: Mounted root (ubifs filesystem) on device 0:13.
devtmpfs: mounted

The regulator init looks suspect to me. I will take a better look at it unless someone comes up with a better idea.

Regards
Gudjon


Top
 Profile  
Reply with quote  
 Post subject: Re: sama5d36 random silent boot failure
PostPosted: Tue Aug 22, 2017 4:38 am 
Offline

Joined: Thu Apr 19, 2007 10:15 pm
Posts: 1470
Location: USA
gudjon wrote:
The regulator init looks suspect to me.
No, regulator_init_complete() did return normally.
The issue seems to be in clk_disable_unused() which is in drivers/clk/clk.c.

Regards


Top
 Profile  
Reply with quote  
Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 9 posts ] 

All times are UTC + 1 hour [ DST ]


Who is online

Users browsing this forum: No registered users and 0 guests


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to:  
cron