This thread to collaborate all efforts towards porting kernel 3.4.x on to the Galaxy 3. If any developers wish to help then please let me know and I will add you to the SG3 group on Github (provided you have proven yourself capable of helping by forking the repository and submitting a pull request of changes you have made - I won't just add people if they are 'learning how to develop for Linux').
Changelog
https://github.com/sg3/android_kernel_samsung_s5p6442/commits/s5p6442-3.4
I chose the Github commit system to be the changelog as there are so many things going on at once it would be impossible to keep up with, and I cannot be assed explaining it. If you don't understand then ask, but please don't ask EVERYTHING. Most of the answers will be 'It just does'.
I am trying to follow the standard process for committing to GIT by doing 's5p6442: change' or 'apollo: change' so it is easier to see what is being fixed and why we are changing it so people reviewing code have an easier job. I expect other developers to follow this as well. Pull requests made that do not follow this naming convention will be rejected.
Source Code
Source: https://github.com/sg3/android_kernel_samsung_s5p6442
Members
The following members already have full read/write access to the repository:
cdesai
hillbeast <- has UART
marcellusbe <- has UART
moikop <- has UART
tom3q <- has UART
As you can see I also listed who has UART (that I currently know of). If you also have UART then let me know and I shall add it to the list. Having UART will be a huge help as it means we can see what is going on.
Why Do We Need Kernel 3.
Easier updating the kernel to add security and performance boosts from mainline Linux kernels
More support for new versions of Android
Android 4.0 was built upon Linux Kernel 3.0.x and therefore expects kernel 3.0s APIs
Faster, more secure system
NO SAMSUNG MORONIC CODE
Because it's just better
Please let me know if you are interested (able to) in helping this cause. Please don't put your hand up if you can't dedicate your phone to this. This will result in your phone being out of action quite a lot while we are testing, and if you need your phone 24/7 then you're going to need to keep flashing back. You will also NEED ODIN. Flashing from CWM is not an option.
Status
What is working
Basic mach-code for s5p6442
Serial/UART
CPU clock and most clock sources
Most mach addresses/IRQs/GPIOs
Kernel init
initramfs init
MTD/OneNAND
GPIO
Screen/Framebuffer
Keypad/buttons
Reboot
Real time clock
I2C over GPIO
HSMMC
What needs to be done
Samsung S3C I2C
Reboot modes
I2S
SDIO
Device Drivers (WiFi, Audio, sensors, etc)
UART Dump
Code:
Starting kernel at 0x22000000...
Uncompressing Linux... done, booting the kernel.
[ 0.000000] Booting Linux on physical CPU 0
[ 0.000000] Initializing cgroup subsys cpuset
[ 0.000000] Initializing cgroup subsys cpu
[ 0.000000] Linux version 3.4.27+ ([email protected]) (gcc version 4.6.2 20120613 (release) [ARM/embedded-4_6-branch revision 188521] (GNU Tools for ARM Embedded Processors) ) #Test Sun Jan 13 20:44:01 NZDT 2013
[ 0.000000] CPU: ARMv6-compatible processor [410fb767] revision 7 (ARMv6TEJ), cr=00c5387d
[ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT nonaliasing instruction cache
[ 0.000000] Machine: APOLLO
[ 0.000000] Memory policy: ECC disabled, Data cache writeback
[ 0.000000] CPU S5P6442 (id 0x36442000)
[ 0.000000] S3C24XX Clocks, Copyright 2004 Simtec Electronics
[ 0.000000] s5p6442_setup_clocks: clkdiv0 = 10100000
[ 0.000000] S5P6442: PLL settings, A=667000000, M=166000000, E=48000000
[ 0.000000] mout_apll: source is fout_apll (1), rate is 667000000
[ 0.000000] mout_mpll: source is fout_mpll (1), rate is 166000000
[ 0.000000] mout_epll: source is fout_epll (1), rate is 48000000
[ 0.000000] mout_arm: source is mout_apll (1), rate is 667000000
[ 0.000000] mout_d0: source is mout_mpll (1), rate is 166000000
[ 0.000000] mout_d0sync: source is mout_d0 (1), rate is 166000000
[ 0.000000] mout_d1: source is mout_mpll (1), rate is 166000000
[ 0.000000] mout_d1sync: source is mout_d1 (1), rate is 166000000
[ 0.000000] sclk_mfc: source is mout_mpll (0), rate is 166000000
[ 0.000000] sclk_mmc: source is mout_mpll (6), rate is 83000000
[ 0.000000] sclk_mmc: source is mout_mpll (6), rate is 83000000
[ 0.000000] sclk_mmc: source is mout_mpll (6), rate is 83000000
[ 0.000000] dout_a2m: source is fout_apll (1), rate is 667000000
[ 0.000000] dout_apll: source is mout_apll (1), rate is 667000000
[ 0.000000] hclkd1: source is mout_d1 (1), rate is 166000000
[ 0.000000] hclkd0: source is mout_d0 (1), rate is 166000000
[ 0.000000] pclkd0: source is mout_d0 (1), rate is 83000000
[ 0.000000] pclkd1: source is mout_d1 (1), rate is 83000000
[ 0.000000] S5P6442: HCLKD0=166000000, HCLKD1=166000000, PCLKD0=83000000, PCLKD1=83000000
[ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 84832
[ 0.000000] Kernel command line: console=ttySAC1,115200 version=Sbl(1.0.0) 2010-10-27 17:10:33
[ 0.000000] PID hash table entries: 2048 (order: 1, 8192 bytes)
[ 0.000000] Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
[ 0.000000] Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
[ 0.000000] allocated 1212416 bytes of page_cgroup
[ 0.000000] please try 'cgroup_disable=memory' option if you don't want memory cgroups
[ 0.000000] Memory: 256MB 80MB = 336MB total
[ 0.000000] Memory: 324804k/324804k available, 19260k reserved, 0K highmem
[ 0.000000] Virtual kernel memory layout:
[ 0.000000] vector : 0xffff0000 - 0xffff1000 ( 4 kB)
[ 0.000000] fixmap : 0xfff00000 - 0xfffe0000 ( 896 kB)
[ 0.000000] vmalloc : 0xe5800000 - 0xff000000 ( 408 MB)
[ 0.000000] lowmem : 0xc0000000 - 0xe5000000 ( 592 MB)
[ 0.000000] modules : 0xbf000000 - 0xc0000000 ( 16 MB)
[ 0.000000] .text : 0xc0008000 - 0xc0995db4 (9784 kB)
[ 0.000000] .init : 0xc0996000 - 0xc0c29000 (2636 kB)
[ 0.000000] .data : 0xc0c2a000 - 0xc0cae688 ( 530 kB)
[ 0.000000] .bss : 0xc0cae6ac - 0xc0e8bc38 (1910 kB)
[ 0.000000] SLUB: Genslabs=13, HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
[ 0.000000] NR_IRQS:208
[ 0.000000] VIC @f6000000: id 0x00041192, vendor 0x41
[ 0.000000] VIC @f6010000: id 0x00041192, vendor 0x41
[ 0.000000] VIC @f6020000: id 0x00041192, vendor 0x41
[ 0.000000] vic_register: too few VICs, increase CONFIG_ARM_VIC_NR
[ 0.000000] sched_clock: 32 bits at 41MHz, resolution 24ns, wraps every 103493ms
[ 0.000000] Console: colour dummy device 80x30
[ 0.000363] Calibrating delay loop... 663.55 BogoMIPS (lpj=1658880)
[ 0.060015] pid_max: default: 32768 minimum: 301
[ 0.060273] Security Framework initialized
[ 0.060345] AppArmor: AppArmor initialized
[ 0.060775] Mount-cache hash table entries: 512
[ 0.061926] Initializing cgroup subsys cpuacct
[ 0.061959] Initializing cgroup subsys memory
[ 0.062041] Initializing cgroup subsys devices
[ 0.062064] Initializing cgroup subsys freezer
[ 0.062082] Initializing cgroup subsys blkio
[ 0.062124] Initializing cgroup subsys perf_event
[ 0.062325] CPU: Testing write buffer coherency: ok
[ 0.062417] ftrace: allocating 24113 entries in 71 pages
[ 0.256329] hw perfevents: enabled with v6 PMU driver, 3 counters available
[ 0.256470] Setting up static identity map for 0x20652280 - 0x206522dc
[ 0.259465] devtmpfs: initialized
[ 0.261208] EVM: security.selinux
[ 0.261230] EVM: security.SMACK64
[ 0.261243] EVM: security.capability
[ 0.262295] gpiochip_add: registered GPIOs 0 to 7 on device: GPA0
[ 0.262327] gpiochip_add: registered GPIOs 9 to 10 on device: GPA1
[ 0.262348] gpiochip_add: registered GPIOs 12 to 15 on device: GPB
[ 0.262366] gpiochip_add: registered GPIOs 17 to 21 on device: GPC0
[ 0.262384] gpiochip_add: registered GPIOs 23 to 27 on device: GPC1
[ 0.262402] gpiochip_add: registered GPIOs 29 to 30 on device: GPD0
[ 0.262420] gpiochip_add: registered GPIOs 32 to 37 on device: GPD1
[ 0.262438] gpiochip_add: registered GPIOs 39 to 46 on device: GPE0
[ 0.262457] gpiochip_add: registered GPIOs 48 to 52 on device: GPE1
[ 0.262475] gpiochip_add: registered GPIOs 54 to 61 on device: GPF0
[ 0.262494] gpiochip_add: registered GPIOs 63 to 70 on device: GPF1
[ 0.262512] gpiochip_add: registered GPIOs 72 to 79 on device: GPF2
[ 0.262531] gpiochip_add: registered GPIOs 81 to 86 on device: GPF3
[ 0.262549] gpiochip_add: registered GPIOs 88 to 94 on device: GPG0
[ 0.262568] gpiochip_add: registered GPIOs 96 to 102 on device: GPG1
[ 0.262587] gpiochip_add: registered GPIOs 104 to 110 on device: GPG2
[ 0.262606] gpiochip_add: registered GPIOs 148 to 155 on device: GPJ0
[ 0.262624] gpiochip_add: registered GPIOs 157 to 162 on device: GPJ1
[ 0.262644] gpiochip_add: registered GPIOs 164 to 171 on device: GPJ2
[ 0.262664] gpiochip_add: registered GPIOs 173 to 180 on device: GPJ3
[ 0.262683] gpiochip_add: registered GPIOs 182 to 186 on device: GPJ4
[ 0.262702] gpiochip_add: registered GPIOs 188 to 195 on device: MP01
[ 0.262721] gpiochip_add: registered GPIOs 197 to 200 on device: MP02
[ 0.262739] gpiochip_add: registered GPIOs 202 to 206 on device: MP03
[ 0.262758] gpiochip_add: registered GPIOs 208 to 215 on device: MP04
[ 0.262777] gpiochip_add: registered GPIOs 217 to 224 on device: MP05
[ 0.262796] gpiochip_add: registered GPIOs 226 to 233 on device: MP06
[ 0.262815] gpiochip_add: registered GPIOs 235 to 242 on device: MP07
[ 0.262834] gpiochip_add: registered GPIOs 244 to 251 on device: MP10
[ 0.262853] gpiochip_add: registered GPIOs 112 to 119 on device: GPH0
[ 0.262872] gpiochip_add: registered GPIOs 121 to 128 on device: GPH1
[ 0.262891] gpiochip_add: registered GPIOs 130 to 137 on device: GPH2
[ 0.262910] gpiochip_add: registered GPIOs 139 to 146 on device: GPH3
[ 0.263470] dummy:
[ 0.264100] NET: Registered protocol family 16
[ 0.275100] apollo_machine_init : hw_rev_pin=0x0
[ 0.275128] apollo_machine_init : bootmode=0x0
[ 0.275146] apollo_machine_init : lcd_id=1
[ 0.275161] apollo_machine_init : uart_sel=1
[ 0.275216] hw-breakpoint: found 6 breakpoint and 1 watchpoint registers.
[ 0.275237] hw-breakpoint: maximum watchpoint size is 4 bytes.
[ 0.275523] S5P6442: Initializing architecture
[ 0.291494] bio: create slab <bio-0> at 0
[ 0.293402] SCSI subsystem initialized
[ 0.294000] usbcore: registered new interface driver usbfs
[ 0.294214] usbcore: registered new interface driver hub
[ 0.294630] usbcore: registered new device driver usb
[ 0.295434] i2c i2c-3: Not I2C compliant: can't read SCL
[ 0.295462] i2c i2c-3: Bus may be unreliable
[ 0.295487] i2c-gpio i2c-gpio.3: using pins 220 (SDA) and 219 (SCL, no clock stretching)
[ 0.296287] max8998 4-0066: No interrupt specified, no interrupts
[ 0.300785] VALIVE_1.1V: 1100 mV
[ 0.302519] VUSB+MIPI_1.1V: 1100 mV
[ 0.304283] VDAC_3.3V: 3300 mV
[ 0.306136] VTF_2.8V: 2800 mV
[ 0.307889] VCC_3.3V: 3300 mV
[ 0.310548] VLCD_1.8V: 1800 mV
[ 0.312288] VUSB+VADC_3.3V: 3300 mV
[ 0.314100] VCC+VCAM_2.8V: 2800 mV
[ 0.316692] VPLL_1.1V: 1100 mV
[ 0.318393] CAM_IO_2.8V: 2800 mV
[ 0.320204] CAM_ISP_1.2V: 1200 mV
[ 0.321958] CAM_A_2.8V: 2800 mV
[ 0.323682] CAM_CIF_1.8V: 1800 mV
[ 0.325508] CAM_AF_3.3V: 3300 mV
[ 0.327243] VMIPI_1.8V: 1800 mV
[ 0.329838] VCC_3.0V_LCD: 3000 mV
[ 0.331270] VARM_1.2V: 1200 mV
[ 0.332645] VINT_1.2V: 1200 mV
[ 0.334014] VCC_1.8V: 1800 mV
[ 0.336329] CAM_CORE_1.2V: 1200 mV
[ 0.337442] i2c-gpio i2c-gpio.4: using pins 182 (SDA) and 185 (SCL)
[ 0.337761] i2c-gpio i2c-gpio.7: using pins 153 (SDA) and 152 (SCL)
[ 0.338087] i2c-gpio i2c-gpio.8: using pins 34 (SDA) and 35 (SCL)
[ 0.338390] i2c-gpio i2c-gpio.9: using pins 178 (SDA) and 179 (SCL)
[ 0.338704] s3c-i2c s3c2410-i2c.0: slave address 0x10
[ 0.338750] s3c-i2c s3c2410-i2c.0: bus frequency set to 81 KHz
[ 0.338797] s3c-i2c s3c2410-i2c.0: cannot claim IRQ 78
[ 0.338850] s3c-i2c: probe of s3c2410-i2c.0 failed with error -38
[ 0.339021] s3c-i2c s3c2410-i2c.1: slave address 0x10
[ 0.339066] s3c-i2c s3c2410-i2c.1: bus frequency set to 81 KHz
[ 0.339106] s3c-i2c s3c2410-i2c.1: cannot claim IRQ 109
[ 0.339157] s3c-i2c: probe of s3c2410-i2c.1 failed with error -22
[ 0.339322] s3c-i2c s3c2410-i2c.2: slave address 0x10
[ 0.339364] s3c-i2c s3c2410-i2c.2: bus frequency set to 81 KHz
[ 0.339682] s3c-i2c s3c2410-i2c.2: i2c-2: S3C I2C adapter
[ 0.339810] Linux video capture interface: v2.00
[ 0.340585] Advanced Linux Sound Architecture Driver Version 1.0.25.
[ 0.341666] Bluetooth: Core ver 2.16
[ 0.341800] NET: Registered protocol family 31
[ 0.341822] Bluetooth: HCI device and connection manager initialized
[ 0.341843] Bluetooth: HCI socket layer initialized
[ 0.341860] Bluetooth: L2CAP socket layer initialized
[ 0.341920] Bluetooth: SCO socket layer initialized
[ 0.341941] NetLabel: Initializing
[ 0.341955] NetLabel: domain hash size = 128
[ 0.341967] NetLabel: protocols = UNLABELED CIPSOv4
[ 0.342112] NetLabel: unlabeled traffic allowed by default
[ 0.342849] Switching to clocksource s5p_clocksource_timer
[ 0.379780] AppArmor: AppArmor Filesystem Enabled
[ 0.409043] NET: Registered protocol family 2
[ 0.409412] IP route cache hash table entries: 4096 (order: 2, 16384 bytes)
[ 0.410301] TCP established hash table entries: 16384 (order: 5, 131072 bytes)
[ 0.411581] TCP bind hash table entries: 16384 (order: 4, 65536 bytes)
[ 0.412212] TCP: Hash tables configured (established 16384 bind 16384)
[ 0.412232] TCP: reno registered
[ 0.412256] UDP hash table entries: 256 (order: 0, 4096 bytes)
[ 0.412319] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
[ 0.412878] NET: Registered protocol family 1
[ 0.413878] RPC: Registered named UNIX socket transport module.
[ 0.413908] RPC: Registered udp transport module.
[ 0.413924] RPC: Registered tcp transport module.
[ 0.413940] RPC: Registered tcp NFSv4.1 backchannel transport module.
[ 2.313502] audit: initializing netlink socket (disabled)
[ 2.313597] type=2000 audit(2.175:1): initialized
[ 2.518638] VFS: Disk quotas dquot_6.5.2
[ 2.519085] Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[ 2.523547] NFS: Registering the id_resolver key type
[ 2.526646] fuse init (API version 7.18)
[ 2.527762] msgmni has been set to 634
[ 2.535433] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 253)
[ 2.535935] io scheduler noop registered
[ 2.535965] io scheduler deadline registered
[ 2.536070] io scheduler cfq registered (default)
[ 2.545209] Console: switching to colour frame buffer device 30x25
[ 2.549050] s3c-fb s3c-fb: window 0: fb
[ 2.549647] Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled
[ 2.564511] s5pv210-uart.0: ttySAC0 at MMIO 0xec000000 (irq = 74) is a S3C6400/10
[ 2.565120] s5pv210-uart.1: ttySAC1 at MMIO 0xec000400 (irq = 75) is a S3C6400/10
[ 3.688673] console [ttySAC1] enabled
[ 3.692714] s5pv210-uart.2: ttySAC2 at MMIO 0xec000800 (irq = 76) is a S3C6400/10
[ 3.701079] ramoops: platform device not found, using module parameters
[ 3.706799] ramoops: The memory size and the record size must be non-zero
[ 3.713399] ramoops: probe of ramoops failed with error -22
[ 3.735283] brd: module loaded
[ 3.744057] loop: module loaded
[ 3.745830] nbd: registered device at major 43
[ 3.762773] i2c-core: driver [fsa9480] using legacy suspend method
[ 3.763421] i2c-core: driver [fsa9480] using legacy resume method
[ 3.770606] mtdoops: mtd device (mtddev=name/number) must be supplied
[ 3.776125] =================================================================
[ 3.783321] Samsung OneNAND Driver (AUDI).
[ 3.787406] =================================================================
[ 3.794866] OneNAND: Clock gating is enabled.
[ 3.799181] Muxed OneNAND 512MB 1.8V 16-bit (0x50)
[ 3.803964] OneNAND version = 0x013e
[ 3.809584] Scanning device for bad blocks
[ 3.852229] onenand_bbt_wait: ecc error = 0x0001, controller error 0x0400
[ 3.853463] OneNAND eraseblock 320 is an initial bad block
[ 4.077529] OneNAND eraseblock 2047 is an initial bad block
[ 4.079391] Creating 8 MTD partitions on "s5p-onenand":
[ 4.082775] 0x000000a00000-0x000001180000 : "boot"
[ 4.090109] 0x000001180000-0x00000ed80000 : "system"
[ 4.095512] 0x00000ed80000-0x00001b800000 : "userdata"
[ 4.100622] 0x00001b800000-0x00001de00000 : "cache"
[ 4.105243] 0x00001de00000-0x00001f500000 : "efs"
[ 4.110030] 0x00001f500000-0x00001ffc0000 : "reservoir"
[ 4.115311] 0x00001ffc0000-0x000020000000 : "dgs"
[ 4.120079] 0x000000180000-0x000000200000 : "param"
[ 4.129186] Fixed MDIO Bus: probed
[ 4.129479] tun: Universal TUN/TAP device driver, 1.6
[ 4.132039] tun: (C) 1999-2004 Max Krasnyansky <[email protected]>
[ 4.138886] PPP generic driver version 2.4.2
[ 4.143197] PPP BSD Compression module registered
[ 4.147386] PPP Deflate Compression module registered
[ 4.155764] PPP MPPE Compression module registered
[ 4.157358] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[ 4.165883] mousedev: PS/2 mouse device common for all mice
[ 4.170690] input: samsung-keypad as /devices/platform/samsung-keypad/input/input0
[ 4.183677] max8998-rtc max8998-rtc: rtc core: registered max8998-rtc as rtc0
[ 4.185222] max8998-rtc max8998-rtc: Failed to request alarm IRQ: 9: -22
[ 4.192094] max8998-rtc max8998-rtc: RTC CHIP NAME: max8998-rtc
[ 4.198341] s3c-rtc s3c64xx-rtc: rtc disabled, re-enabling
[ 4.204232] s3c-rtc s3c64xx-rtc: rtc core: registered s3c as rtc1
[ 4.209837] s3c-rtc s3c64xx-rtc: warning: invalid RTC value so initializing it
[ 4.217293] i2c /dev entries driver
[ 4.223542] lirc_dev: IR Remote Control driver registered, major 252
[ 4.227104] IR NEC protocol handler initialized
[ 4.231789] IR RC5(x) protocol handler initialized
[ 4.236611] IR RC6 protocol handler initialized
[ 4.241188] IR JVC protocol handler initialized
[ 4.245773] IR Sony protocol handler initialized
[ 4.250448] IR RC5 (streamzap) protocol handler initialized
[ 4.256091] IR SANYO protocol handler initialized
[ 4.260894] IR MCE Keyboard/mouse protocol handler initialized
[ 4.266831] IR LIRC bridge handler initialized
[ 4.271884] vivi-000: V4L2 device registered as video0
[ 4.276490] Video Technology Magazine Virtual Video Capture Board ver 0.8.1 successfully loaded.
[ 4.286115] m2m-testdev m2m-testdev.0: mem2mem-testdevDevice registered as /dev/video1
[ 4.293614] S5P JPEG V4L2 Driver, (c) 2011 Samsung Electronics
[ 4.299987] s5p-jpeg s5p-jpeg.0: encoder device registered as /dev/video2
[ 4.306631] s5p-jpeg s5p-jpeg.0: decoder device registered as /dev/video3
[ 4.313092] s5p-jpeg s5p-jpeg.0: Samsung S5P JPEG codec
[ 4.319104] s5p-mfc s5p-mfc: decoder registered as /dev/video4
[ 4.324735] s5p-mfc s5p-mfc: encoder registered as /dev/video5
[ 4.331964] device-mapper: uevent: version 1.0.3
[ 4.335859] device-mapper: ioctl: 4.22.0-ioctl (2011-10-19) initialised: [email protected]
[ 4.344756] device-mapper: multipath: version 1.3.0 loaded
[ 4.349027] device-mapper: multipath round-robin: version 1.0.0 loaded
[ 4.355582] device-mapper: multipath queue-length: version 0.1.0 loaded
[ 4.362272] device-mapper: multipath service-time: version 0.2.0 loaded
[ 4.369166] Bluetooth: HCI UART driver ver 2.2
[ 4.373493] Bluetooth: HCI H4 protocol initialized
[ 4.378328] cpuidle: using governor ladder
[ 4.382413] cpuidle: using governor menu
[ 4.386665] sdhci: Secure Digital Host Controller Interface driver
[ 4.392711] sdhci: Copyright(c) Pierre Ossman
[ 4.397299] s3c-sdhci s3c-sdhci.0: clock source 0: mmc_busclk.0 (166000000 Hz)
[ 4.404494] s3c-sdhci s3c-sdhci.0: clock source 2: mmc_busclk.2 (83000000 Hz)
[ 4.413642] mmc0: SDHCI controller on samsung-hsmmc [s3c-sdhci.0] using ADMA
[ 4.419361] VTF_2.8V: operation not allowed
[ 4.423067] s3c-sdhci s3c-sdhci.0: could not set regulator OCR (-1)
[ 4.429579] s3c-sdhci s3c-sdhci.1: clock source 0: mmc_busclk.0 (166000000 Hz)
[ 4.436774] s3c-sdhci s3c-sdhci.1: clock source 2: mmc_busclk.2 (83000000 Hz)
[ 4.445522] VTF_2.8V: operation not allowed
[ 4.448203] s3c-sdhci s3c-sdhci.0: could not set regulator OCR (-1)
[ 4.454713] mmc1: no vmmc regulator found
[ 4.460242] mmc1: SDHCI controller on samsung-hsmmc [s3c-sdhci.1] using ADMA
[ 4.465940] s3c-sdhci s3c-sdhci.2: clock source 0: mmc_busclk.0 (166000000 Hz)
[ 4.476388] s3c-sdhci s3c-sdhci.2: clock source 2: mmc_busclk.2 (83000000 Hz)
[ 4.482175] VTF_2.8V: operation not allowed
[ 4.484543] s3c-sdhci s3c-sdhci.0: could not set regulator OCR (-1)
[ 4.491054] mmc2: no vmmc regulator found
[ 4.496685] mmc2: SDHCI controller on samsung-hsmmc [s3c-sdhci.2] using ADMA
[ 4.502247] sdhci-pltfm: SDHCI platform and OF driver helper
[ 4.509478] usbcore: registered new interface driver usbhid
[ 4.513457] usbhid: USB HID core driver
[ 4.518528] ashmem: initialized
[ 4.520813] logger: created 256K log 'log_main'
[ 4.528884] logger: created 256K log 'log_events'
[ 4.531558] logger: created 256K log 'log_radio'
[ 4.534910] logger: created 256K log 'log_system'
[ 4.552135] IPv4 over IPv4 tunneling driver
[ 4.553324] Initializing XFRM netlink socket
[ 4.555039] NET: Registered protocol family 17
[ 4.562972] NET: Registered protocol family 15
[ 4.565666] Bluetooth: RFCOMM TTY layer initialized
[ 4.569203] Bluetooth: RFCOMM socket layer initialized
[ 4.574203] Bluetooth: RFCOMM ver 1.11
[ 4.579328] NET: Registered protocol family 33
[ 4.584577] sctp: Hash tables configured (established 16384 bind 32768)
[ 4.589796] Registering the dns_resolver key type
[ 4.597496] VFP support v0.3: implementor 41 architecture 1 part 20 variant b rev 5
[ 4.604614] registered taskstats version 1
[ 4.614795] VCC_1.8V: incomplete constraints, leaving on
[ 4.615346] VINT_1.2V: incomplete constraints, leaving on
[ 4.621985] VARM_1.2V: incomplete constraints, leaving on
[ 4.626472] CAM_AF_3.3V: incomplete constraints, leaving on
[ 4.632575] CAM_ISP_1.2V: incomplete constraints, leaving on
[ 4.637494] CAM_IO_2.8V: incomplete constraints, leaving on
[ 4.643182] VPLL_1.1V: incomplete constraints, leaving on
[ 4.649650] VCC+VCAM_2.8V: incomplete constraints, leaving on
[ 4.656416] VUSB+VADC_3.3V: incomplete constraints, leaving on
[ 4.660221] VCC_3.3V: incomplete constraints, leaving on
[ 4.665695] VTF_2.8V: incomplete constraints, leaving on
[ 4.671548] VUSB+MIPI_1.1V: incomplete constraints, leaving on
[ 4.679449] input: gpio-keys as /devices/platform/gpio-keys.0/input/input1
[ 4.687987] max8998-rtc max8998-rtc: setting system clock to 2013-02-23 08:21:42 UTC (1361607702)
[ 4.692653] ALSA device list:
[ 4.695373] No soundcards found.
[ 4.699028] Warning: unable to open an initial console.
[ 4.730337] Freeing init memory: 2636K
[ 4.730385] Write protecting the kernel text section c0008000 - c090d000
[ 4.925033] mmc2: new SD card at address aaaa
[ 4.933164] mmcblk0: mmc2:aaaa SU01G 942 MiB
[ 4.936670] mmcblk0: p1
[ 5.113958] init: cannot open '/initlogo.rle'
[ 5.348302] EXT4-fs (mtdblock1): warning: maximal mount count reached, running e2fsck is recommended
[ 5.352863] EXT4-fs (mtdblock1): recovery complete
[ 5.357121] EXT4-fs (mtdblock1): mounted filesystem with ordered data mode. Opts: (null)
[ 5.366051] EXT4-fs (mtdblock1): re-mounted. Opts: (null)
[ 5.563526] EXT4-fs (mtdblock2): warning: maximal mount count reached, running e2fsck is recommended
[ 5.567565] EXT4-fs (mtdblock2): recovery complete
[ 5.572336] EXT4-fs (mtdblock2): mounted filesystem with ordered data mode. Opts: (null)
[ 5.638145] EXT4-fs (mtdblock3): warning: maximal mount count reached, running e2fsck is recommended
[ 5.642200] EXT4-fs (mtdblock3): recovery complete
[ 5.646958] EXT4-fs (mtdblock3): mounted filesystem with ordered data mode. Opts: (null)
[ 5.659542] EXT4-fs (mtdblock4): Unrecognized mount option "check=no" or missing value
[ 5.726831] lowmem_shrink: convert oom_adj to oom_score_adj:
[ 5.726892] oom_adj 0 => oom_score_adj 0
[ 5.730922] oom_adj 1 => oom_score_adj 58
[ 5.734942] oom_adj 2 => oom_score_adj 117
[ 5.739090] oom_adj 4 => oom_score_adj 235
[ 5.743230] oom_adj 7 => oom_score_adj 411
[ 5.747323] oom_adj 15 => oom_score_adj 1000
[ 5.752406] init (1): /proc/1/oom_adj is deprecated, please use /proc/1/oom_score_adj instead.
sh: can't access tty; job control turned off
# [ 6.736529] init: untracked pid 139 exited
[ 7.097207] warning: `rild' uses 32-bit capabilities (legacy support in use)
How To Build
git clone git://github.com/sg3/android_kernel_samsung_s5p6442 -b s5p6442-3.4 kernel-3.4
cd kernel-3.4
make ARCH=arm apollo_defconfig
./build.sh config
./build.sh
Things to be aware of
I feel these things should be mentioned as they are important changes that may disrupt peoples user experience on the phone.
Odin will not work anymore for flashing ROMs. It's as simple as that. We will no longer be using STL/BML/TFSR for interfacing with the NAND, and that is what ODIN expects to be working with: partitions in STL format. We simply will not support STL when this kernel is complete as it is closed source and will not function on kernel 3.x. We will be moving over to MTD which is mainline, and regularly gets updates to improve performance, reliability and in general to make it better.
Kernels will however be flashable from ODIN. This WILL NOT change. Kernels, modem.bin, Sbl and boot.bin will all still work from Odin. Data, system and cache will not.
I know this will annoy a few people, as it will disrupt me too as a developer and a Windows user, it's nice to be able to flash a ROM this way, but we're going to have to move towards distributing ROMs in system.imgs, or more preferably in update.zips.
There will be no support for Samsung Froyo/Eclair ROMs in kernel 3.x. The reasoning behind this is because Samsung ROMs want Samsung drivers and we won't be using any of them. We will be aiming to support CM7 and CM9, or generally any AOSP ROM, but not Samsungs proprietary ROM. You may think 'well why not make the drivers work for both', but the problem is not with making the drivers work, the problem is with the fact that a lot of these drivers were written for a kernel over 10 major versions out of date by now, and will not function on the new kernels APIs. If we try to make them work, it will make the kernel unstable and it's going to degrade the experience for the end user. As well as that, we don't know how half these drivers actually work because they are either coded so badly it's impossible to make heads or tails of it, or it's closed source and we can't find sources for it.
There are plenty of good custom kernels for Froyo, and I have heard word in the grapevine a few people want to make a custom Eclair kernel (not confirmed, and that is just rumours), but I will not be adding support for Froyo to kernel 3.x
Kernel 3.x will not allow us to work magic with the phone. Having a newer kernel won't allow us to make the CPU itself faster, we can't give it more RAM (or find more RAM in there). We won't be able to unlock more performance from x part. This is not a magical rebirth of the phone, this is just a major fix up of all the current issues we face with AOSP based ROMs on the phone. It will most likely make the phone faster, but we can't magically make it into a dual core or something like that. It just isn't possible.
I see a reserved post there!
And one more for good luck. Now you may post.
So many reserved posts WHOA!
could possibly add a guide to clone and build it
EDIT:
Btw, also add a note about the two branches on github
android-3.0 = android-common kernel from android.googlesource.com
linux-samsung = kgene/linux-samsung on kernel.org / github
+1! Yeah guys well done! Finally! Is it only me that I think that may we have a beta or final version of Gingerbread or (cross fingers) ICS if you guys port the 3.0 kernel for our phone?
Good to have a new thread now.....
All the best Mark & all the Devs in this project..
+1 Good luck!!
Good luck with this project
All the best.. Although this is gonna take much time still waiting patiently
I may sound like an ultra-noob here : But what is Kernel 3.0 ?
Google isn't help here
You could add this to the first post but only computer programmers will understand it, unlike me
ak700 said:
I may sound like an ultra-noob here : But what is Kernel 3.0 ?
Google isn't help here
Click to expand...
Click to collapse
Newer version of the kernel that will be completely built from scratch. tom3q did this on the Spica and it worked wonders, now it's time to do it to our phone.
Smonic said:
You could add this to the first post but only computer programmers will understand it, unlike me
Click to expand...
Click to collapse
I don't like kernel.org. They're hopeless, shown by their hacking last year and their slow recovery time, and then made worse for the fact that Linus Torvalds himself switched to Github.
This is what i wanted to see since long times now. I just wanto say thank you to all the devs for just trying
Frig. I was doing so well and then I hit a brick wall with bloody assembler...
Code:
[email protected]:~/devel/galaxy3/kernel-3.0$ ./build.sh Test
Setting kernel name to (Test)
Compiling the kernel
CHK include/linux/version.h
CHK include/generated/utsrelease.h
UPD include/generated/utsrelease.h
make[1]: `include/generated/mach-types.h' is up to date.
CALL scripts/checksyscalls.sh
CHK include/generated/compile.h
CC init/version.o
AS arch/arm/kernel/debug.o
arch/arm/kernel/debug.S: Assembler messages:
arch/arm/kernel/debug.S:157: Error: too many positional arguments
arch/arm/kernel/debug.S:173: Error: too many positional arguments
make[1]: *** [arch/arm/kernel/debug.o] Error 1
make: *** [arch/arm/kernel] Error 2
make: *** Waiting for unfinished jobs....
Anyone smarter than me with assember know what that means?
EDIT: It's to do with ASCII and UART
Line 156-170 debug.S
Code:
ENTRY(printascii)
addruart_current r3, r1, r2
b 2f
1: waituart r2, r3
senduart r1, r3
busyuart r2, r3
teq r1, #'\n'
moveq r1, #'\r'
beq 1b
2: teq r0, #0
ldrneb r1, [r0], #1
teqne r1, #0
bne 1b
mov pc, lr
ENDPROC(printascii)
hillbeast said:
Frig. I was doing so well and then I hit a brick wall with bloody assembler...
Code:
[email protected]:~/devel/galaxy3/kernel-3.0$ ./build.sh Test
Setting kernel name to (Test)
Compiling the kernel
CHK include/linux/version.h
CHK include/generated/utsrelease.h
UPD include/generated/utsrelease.h
make[1]: `include/generated/mach-types.h' is up to date.
CALL scripts/checksyscalls.sh
CHK include/generated/compile.h
CC init/version.o
AS arch/arm/kernel/debug.o
arch/arm/kernel/debug.S: Assembler messages:
arch/arm/kernel/debug.S:157: Error: too many positional arguments
arch/arm/kernel/debug.S:173: Error: too many positional arguments
make[1]: *** [arch/arm/kernel/debug.o] Error 1
make: *** [arch/arm/kernel] Error 2
make: *** Waiting for unfinished jobs....
Anyone smarter than me with assember know what that means?
EDIT: It's to do with ASCII and UART
Line 156-170 debug.S
Code:
ENTRY(printascii)
addruart_current r3, r1, r2
b 2f
1: waituart r2, r3
senduart r1, r3
busyuart r2, r3
teq r1, #'\n'
moveq r1, #'\r'
beq 1b
2: teq r0, #0
ldrneb r1, [r0], #1
teqne r1, #0
bne 1b
mov pc, lr
ENDPROC(printascii)
Click to expand...
Click to collapse
The error is not on /arch/arm/kernel/debug.S, it's on /arch/arm/mach-s5p6442/include/mach/debug-macro.S (Error caused by just putting Samsung's .32 code into 3.x I guess...).
Check out that addruart_current is defined a few lines before, and it refers to "adduart" which is defined at debug-macro.S (that's why before defining addruart_current, debug-macro.S is included).
And if you check debug-macro.S, you'll see that adduart is defined only with one parameter, when in debug.S it's used with two parameters. That's where the error comes from.
In order to fix this, you'll have to redo the debug-macro.S file so that adduart takes two parameters (IMO should be based in S5PC110 or Spica's (or maybe s5p64x0?) debug-macro.S).
moikop said:
The error is not on /arch/arm/kernel/debug.S, it's on /arch/arm/mach-s5p6442/include/mach/debug-macro.S (Error caused by just putting Samsung's .32 code into 3.x I guess...).
Check out that addruart_current is defined a few lines before, and it refers to "adduart" which is defined at debug-macro.S (that's why before defining addruart_current, debug-macro.S is included).
And if you check debug-macro.S, you'll see that adduart is defined only with one parameter, when in debug.S it's used with two parameters. That's where the error comes from.
In order to fix this, you'll have to redo the debug-macro.S file so that adduart takes two parameters (IMO should be based in S5PC110 or Spica's (or maybe s5p64x0?) debug-macro.S).
Click to expand...
Click to collapse
Brilliant. Now we're back to good ol' fixing up references.
hillbeast said:
Frig. I was doing so well and then I hit a brick wall with bloody assembler...
Code:
[email protected]:~/devel/galaxy3/kernel-3.0$ ./build.sh Test
Setting kernel name to (Test)
Compiling the kernel
CHK include/linux/version.h
CHK include/generated/utsrelease.h
UPD include/generated/utsrelease.h
make[1]: `include/generated/mach-types.h' is up to date.
CALL scripts/checksyscalls.sh
CHK include/generated/compile.h
CC init/version.o
AS arch/arm/kernel/debug.o
arch/arm/kernel/debug.S: Assembler messages:
arch/arm/kernel/debug.S:157: Error: too many positional arguments
arch/arm/kernel/debug.S:173: Error: too many positional arguments
make[1]: *** [arch/arm/kernel/debug.o] Error 1
make: *** [arch/arm/kernel] Error 2
make: *** Waiting for unfinished jobs....
Click to expand...
Click to collapse
you're using homebrew right? if yes, does it compile faster? in a word, ill grab my sis macbook pro !
BTW, which baseband are you gonna use for this kernel ?
I've installed the newest build for Cyanogengmod 11 that supports my exact phone (XT897c) and it works great. I've only been using it for a few days now and haven't ran into any major issues but one. The problem I continue to have is I cannot install Gapps and have the phone work properly. Everytime I install the correct Gapps (or any other variant for that matter) the phone stays locked up at the initial Motorola boot logo and will never continue loading. I've redownloaded and reinstalled both CM11 and various Gapps KK from different sites and methods without fixing the problem. Anyone have a suggestion?
sulken2000 said:
I've installed the newest build for Cyanogengmod 11 that supports my exact phone (XT897c) and it works great. I've only been using it for a few days now and haven't ran into any major issues but one. The problem I continue to have is I cannot install Gapps and have the phone work properly. Everytime I install the correct Gapps (or any other variant for that matter) the phone stays locked up at the initial Motorola boot logo and will never continue loading. I've redownloaded and reinstalled both CM11 and various Gapps KK from different sites and methods without fixing the problem. Anyone have a suggestion?
Click to expand...
Click to collapse
Download these cm11 gapps from dhacker29 (supports both dalvik and art).
Install CM11. let it boot
Install gapps. reboot which will probably fail.
if the above failed: re-install cm11, wipe cache/dalvik and reboot.
sulken2000 said:
I've installed the newest build for Cyanogengmod 11 that supports my exact phone (XT897c) and it works great. I've only been using it for a few days now and haven't ran into any major issues but one. The problem I continue to have is I cannot install Gapps and have the phone work properly. Everytime I install the correct Gapps (or any other variant for that matter) the phone stays locked up at the initial Motorola boot logo and will never continue loading. I've redownloaded and reinstalled both CM11 and various Gapps KK from different sites and methods without fixing the problem. Anyone have a suggestion?
Click to expand...
Click to collapse
If you're using xt897c CM11 build, you're using very outdated build.
Your exact phone is not xt897c, you have just xt897, as anyone else.
There's no such thing as xt897c phone, xt897c is something I've made up as a temporary measure until we'll be able to do a single world-phone build that will support both GSM and CDMA networks.
Since long time ago, xt897 (gsm) and xt897c (cdma) builds have been unified into a single xt897 (world phone) build which made xt897c builds obsolete.
Later on, the builds for the whole 1st gen family of Motorola msm8960 devices (razr hd, razr m, atrix hd, electrify m and photon q) have been unified into a single moto_msm8960 build. All those devices are very similar and have used a single common kernel from the beginning, since the CM 10.1 time).
If you want to install CM11 on your phone, you should install this:
http://download.cyanogenmod.org/?device=moto_msm8960
Any other CM11 build is obsolete.
Links to recommended CM 11 gapps can be found here:
http://wiki.cyanogenmod.org/w/Gapps
mrvek said:
Download these cm11 gapps from dhacker29 (supports both dalvik and art).
Install CM11. let it boot
Install gapps. reboot which will probably fail.
if the above failed: re-install cm11, wipe cache/dalvik and reboot.
Click to expand...
Click to collapse
I did in fact, download, redownload, install, reinstall, the Gapps from the link you provided, and got no advancements =( Unfortunately, I'll have to start all over from scratch most likely. I really appreciate your prompt response.
kabaldan said:
If you're using xt897c CM11 build, you're using very outdated build.
Your exact phone is not xt897c, you have just xt897, as anyone else.
There's no such thing as xt897c phone, xt897c is something I've made up as a temporary measure until we'll be able to do a single world-phone build that will support both GSM and CDMA networks.
Since long time ago, xt897 (gsm) and xt897c (cdma) builds have been unified into a single xt897 (world phone) build which made xt897c builds obsolete.
Later on, the builds for the whole 1st gen family of Motorola msm8960 devices (razr hd, razr m, atrix hd, electrify m and photon q) have been unified into a single moto_msm8960 build. All those devices are very similar and have used a single common kernel from the beginning, since the CM 10.1 time).
If you want to install CM11 on your phone, you should install this:
http://download.cyanogenmod.org/?device=moto_msm8960
Any other CM11 build is obsolete.
Links to recommended CM 11 gapps can be found here:
http://wiki.cyanogenmod.org/w/Gapps
Click to expand...
Click to collapse
That version still didn't work with Gapps. I've tried the many different ways of clearing cache, system, data, dalvik cache, etc etc. Nothing gets me past the Moto Logo. But, I've made another discovery, once I've installed CM11 on my phone, regardless of which of the two, once the phone has been turned off, it won't properly boot back up because it stays stuck that the Moto logo. The version you suggested loaded properly without Gapps installed just as the xt897c version did. But they both have the same "only works the first time no rebooting allowed" problem and neither work with Gapps.
One thing to note, I've used the CM10.1.3 (Stable) listed in the "xt897c" category as well as the Gapps (20130812) from the cyanogenmod website. Its what gave me the idea that my only option for CM via the CM website is the "xt897c" since that version of CM works flawlessly with Gapps installed (minus the lack of proper data connection (C Spire version) due to the rom having Sprint connection settings)
p.s. that is something I've been trying to search and "fix" for ages. I really hate being with a "lesser" company (C Spire) because of the lack of aftermarket and development support.
sulken2000 said:
That version still didn't work, I've tried the many different ways of clearing cash,system,data,dalvik,cache, etc etc. Nothing gets me past the Moto Logo. Hope there is another way.
One thing to note, I've used the CM10.1.3 (Stable) listed in the "xt897c" category as well as the Gapps (20130812) from the cyanogenmod website. Its what gave me the idea that my only option for CM via the CM website is the "xt897c" since that version of CM works flawlessly with Gapps installed (minus the lack of proper data connection (C Spire version) due to the rom having Sprint connection settings)
p.s. that is something I've been trying to search and "fix" for ages. I really hate being with a "lesser" company (C Spire) for the lack of aftermarket and development support.
Click to expand...
Click to collapse
Please, post the the info I requested here:
http://forum.xda-developers.com/showthread.php?t=2656570
I'm still waiting for any C Spire Photon Q owner to respond, so I could finally add the support for C Spire variant of XT897 to CM 11.0 moto_msm8960 unified builds.
Thanks.
kabaldan said:
Please, post the the info I requested here:
http://forum.xda-developers.com/showthread.php?t=2656570
I'm still waiting for any C Spire Photon Q owner to respond, so I could finally add the support for C Spire variant of XT897 to CM 11.0 moto_msm8960 unified builds.
Thanks.
Click to expand...
Click to collapse
Thanks for the prompt response. I have definitely come across that post in the past few days while trying to fix this irritating problem. I'll do some research to learn how to do that first and try to get you that info asap.
sulken2000 said:
...both have the same "only works the first time no rebooting allowed" problem and neither work with Gapps.
...
Click to expand...
Click to collapse
I noticed your remark above only now.
The symptom you mention seems to be caused by formatting of /data partition by recovery, which causes some not yet preciously determined filesystem corruption.
The second boot seems to be stalled, but what actually happens is that /data filesystem check and repair is running. And this repair will eventually finish, even though it can take tens of minutes. After the repair is done, the Android system boots fine and subsequent reboots are fine and fast.
Which recovery are you using? I use OpenRecovery 2.09 ( http://forum.xda-developers.com/showthread.php?t=2211579 ; see the last pages of the thread for a working download link), which actually does not re-format the /data partition filesystem when you do a data wipe/factory reset, it just deletes the content of the partition. So when using OpenRecovery, this corruption should not happen.
TWRP2.7.0.1
Sadly I'm also having troubles with my second Photon Q, this time from CSpire. Like Sulken's phone (also from CSpire) it doesn't survive reboot - however mine stops on unlocked bootloader warning. I was flashing Carbon 4.4 and suggested GAPPS first, but it wierdly let me send&receive smses and call people while on GSM network, however nobody could call me - line was busy. So I tried with CM11 and here everything is fine, however it also didn't survive reboot. On my first photon I always used TWRP but on this one, from CSpire, it cannot do factory reset - reboots on /data wiping, so I'm using OpenRecovery 2.09 now. Another very weird thing is that the phone won't boot after reflashing custom ROM. I'm doing a factory reset, flashing once again for example CM11 and it won't pass the unlocked bootloader warning, so I have to first do RSDLite+stock CSpire ROM and then flash CM11 once again, and then it works as long as I don't reboot...
I can't believe that nobody before tried SIM-mod & custom ROM on PhotonQ from CSpire... What's wrong? :/
micx_pl said:
Sadly I'm also having troubles with my second Photon Q, this time from CSpire. Like Sulken's phone (also from CSpire) it doesn't survive reboot - however mine stops on unlocked bootloader warning. I was flashing Carbon 4.4 and suggested GAPPS first, but it wierdly let me send&receive smses and call people while on GSM network, however nobody could call me - line was busy. So I tried with CM11 and here everything is fine, however it also didn't survive reboot. On my first photon I always used TWRP but on this one, from CSpire, it cannot do factory reset - reboots on /data wiping, so I'm using OpenRecovery 2.09 now. Another very weird thing is that the phone won't boot after reflashing custom ROM. I'm doing a factory reset, flashing once again for example CM11 and it won't pass the unlocked bootloader warning, so I have to first do RSDLite+stock CSpire ROM and then flash CM11 once again, and then it works as long as I don't reboot...
I can't believe that nobody before tried SIM-mod & custom ROM on PhotonQ from CSpire... What's wrong? :/
Click to expand...
Click to collapse
See my comment here: https://jira.cyanogenmod.org/browse...issuetabpanels:comment-tabpanel#comment-25465
How long have you let the phone to sit at the boot screen after the first reboot from working CM11?
(Make sure the battery is near full and keep the phone plugged to USB or power supply when attempting to wait over this stalled boot.)
If you want to get some information about what's going on while the boot is stalled, you should force a reboot by holding power button while waiting at the boot logo for some time already and also hold the volume-up button to reboot directly to recovery. Then post the content of /proc/last_kmsg captured via adb while the phone is in recovery after this forced reboot.
Code:
adb pull /proc/last_kmsg
Output of /proc/last_kmsg:
Code:
[ 0.211841,0] mot_init_factory_kill: Factory Kill Circuit: enabled
[ 0.221303,0] select_freq_plan: ACPU PVS: Fast
[ 0.221394,0] select_freq_plan: Max ACPU freq: 1512000 KHz
[ 0.224599,0] cpufreq_table_init: CPU0: 12 scaling frequencies supported.
[ 0.224721,0] cpufreq_table_init: CPU1: 12 scaling frequencies supported.
/////////////////////// CUT /////////////////////////
[ 0.946711,0] i2c-core: driver [tabla-i2c-core] using legacy suspend method
[ 0.946772,0] i2c-core: driver [tabla-i2c-core] using legacy resume method
[ 0.947352,0] Loading pn544 driver
[ 0.947443,0] pn544_probe : Probing pn544 driver
[ 0.947627,0] pn544_probe : PN544 Misc Minor: 26
[ 0.947718,0] pn544_probe : requesting IRQ 394
[ 0.948206,0] SCSI Media Changer driver v0.25
[ 0.948939,0] PPP generic driver version 2.4.2
[ 0.949092,0] PPP Deflate Compression module registered
[ 0.949183,0] PPP BSD Compression module registered
[ 0.949824,0] PPP MPPE Compression module registered
[ 0.949885,0] NET: Registered protocol family 24
[ 0.950007,0] SLIP: version 0.8.4-NET3.019-NEWTTY (dynamic channels, max=256) (6 bit encapsulation enabled).
[ 0.950129,0] CSLIP: code copyright 1989 Regents of the University of California.
[ 0.950465,0] tun: Universal TUN/TAP device driver, 1.6
[ 0.950587,0] tun: (C) 1999-2004 Max Krasnyansky <[email protected]>
[ 0.951228,0] usbcore: registered new interface driver asix
[ 0.951381,0] usbcore: registered new interface driver cdc_ether
[ 0.951472,0] usbcore: registered new interface driver net1080
[ 0.951625,0] usbcore: registered new interface driver cdc_subset
[ 0.951777,0] usbcore: registered new interface driver zaurus
[ 0.951869,0] usbcore: registered new interface driver MOSCHIP usb-ethernet driver
[ 0.951991,0] cdc_ncm: 04-Aug-2011
[ 0.952083,0] usbcore: registered new interface driver cdc_ncm
[ 0.952235,0] usbcore: registered new interface driver rmnet_usb
[ 0.952601,0] rmnet usb ctrl Initialized.
[ 0.952723,0] wcnss_wlan probed in built-in mode
[ 0.953151,0] rmnet_init: BAM devices[8]
[ 0.955989,0] msm_otg msm_otg: msm_otg probe
[ 0.956142,0] msm_otg msm_otg: OTG regs = e18a8000
[ 0.958492,0] msm_otg_probe: MSM OTG Driver will operate in ACCY CONTROL mode
[ 0.958614,0] msm_otg_init_sm: setting default inputs for ACCY mode
[ 0.959072,0] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[ 0.959621,0] usbcore: registered new interface driver cdc_acm
[ 0.959682,0] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters
[ 0.959865,0] usbcore: registered new interface driver usblp
[ 0.959926,0] Initializing USB Mass Storage driver...
[ 0.960079,0] usbcore: registered new interface driver usb-storage
[ 0.960140,0] USB Mass Storage support registered.
[ 0.960262,0] usbcore: registered new interface driver ums-alauda
[ 0.960384,0] usbcore: registered new interface driver ums-cypress
[ 0.960537,0] usbcore: registered new interface driver ums-datafab
[ 0.960689,0] usbcore: registered new interface driver ums-freecom
[ 0.960781,0] usbcore: registered new interface driver ums-isd200
[ 0.960933,0] usbcore: registered new interface driver ums-jumpshot
[ 0.961025,0] usbcore: registered new interface driver ums-karma
[ 0.961178,0] usbcore: registered new interface driver ums-onetouch
[ 0.961269,0] usbcore: registered new interface driver ums-sddr09
[ 0.961422,0] usbcore: registered new interface driver ums-sddr55
[ 0.961544,0] usbcore: registered new interface driver ums-usbat
[ 0.961727,0] usbcore: registered new interface driver usbserial
[ 0.961788,0] usbserial: USB Serial Driver core
[ 0.961941,0] USB Serial support registered for Qualcomm USB modem
[ 0.962032,0] usbcore: registered new interface driver qcserial
[ 0.962185,0] usbcore: registered new interface driver usb_ehset_test
[ 0.962307,0] usbcore: registered new interface driver diag_bridge
[ 0.962459,0] usbcore: registered new interface driver mdm_bridge
[ 0.963131,0] msm_hsusb msm_hsusb: [usb_gadget_probe_driver] hw_ep_max = 32
[ 0.964413,0] android_usb gadget: Mass Storage Function, version: 2009/09/11
[ 0.964535,0] android_usb gadget: Number of LUNs=1
[ 0.964596,0] lun0: LUN: removable file: (no medium)
[ 0.965237,0] android_usb gadget: android_usb ready
[ 0.966366,0] diagchar initialized now
[ 0.966549,0] mousedev: PS/2 mouse device common for all mice
[ 0.966854,0] gpio_set_debounce: gpio-184 status -22
[ 0.967037,0] gpio_set_debounce: gpio-11 status -22
[ 0.967312,0] input: gpio-keys as /devices/platform/gpio-keys/input/input0
[ 0.967373,0] added keypad filter to input dev gpio-keys
[ 0.968533,0] input: keypad_8960 as /devices/platform/msm_ssbi.0/pm8921-core/pm8xxx-keypad/input/input1
[ 0.968655,0] added keypad filter to input dev keypad_8960
[ 0.968930,0] usbcore: registered new interface driver xpad
[ 0.969113,0] usbcore: registered new interface driver usb_acecad
[ 0.969174,0] acecad: v3.2:USB Acecad Flair tablet driver
[ 0.969327,0] usbcore: registered new interface driver aiptek
[ 0.969418,0] aiptek: v2.3 (May 2, 2007):Aiptek HyperPen USB Tablet Driver (Linux 2.6.x)
[ 0.969510,0] aiptek: Bryan W. Headley/Chris Atenasio/Cedric Brun/Rene van Paassen
[ 0.969662,0] usbcore: registered new interface driver gtco
[ 0.969723,0] GTCO usb driver version: 2.00.0006
[ 0.969845,0] usbcore: registered new interface driver hanwang
[ 0.970028,0] usbcore: registered new interface driver kbtab
[ 0.970090,0] kbtab: v0.0.2:USB KB Gear JamStudio Tablet driver
[ 0.970242,0] usbcore: registered new interface driver wacom
[ 0.970303,0] wacom: v1.52:USB Wacom tablet driver
[ 0.970517,0] atmxt_probe: Driver: atmxt-i2c, Version: YN-04-01, Date: 2012-06-28
[ 0.971799,0] atmxt_probe: Probe successful.
[ 0.972195,0] input: light-prox as /devices/virtual/input/input2
[ 0.972470,0] ct406_probe: CT406 part detected
[ 0.973416,0] input: pmic8xxx_pwrkey as /devices/platform/msm_ssbi.0/pm8921-core/pm8xxx-pwrkey/input/input3
[ 0.973935,0] using input dev keypad_8960 for key reset
[ 0.973996,0] using input dev pmic8xxx_pwrkey for key reset
[ 0.974851,0] using rtc device, pm8xxx_rtc, for alarms
[ 0.974942,0] rtc-pm8xxx rtc-pm8xxx: rtc core: registered pm8xxx_rtc as rtc0
[ 0.975309,0] i2c /dev entries driver
[ 0.975614,0] Linux media interface: v0.10
[ 0.975766,0] lirc_dev: IR Remote Control driver registered, major 235
[ 0.975888,0] IR NEC protocol handler initialized
[ 0.975949,0] IR RC5(x) protocol handler initialized
[ 0.976041,0] IR RC6 protocol handler initialized
[ 0.976102,0] IR JVC protocol handler initialized
[ 0.976224,0] IR Sony protocol handler initialized
[ 0.976285,0] IR RC5 (streamzap) protocol handler initialized
[ 0.976377,0] IR LIRC bridge handler initialized
[ 0.976438,0] Linux video capture interface: v2.00
[ 0.976590,0] usbcore: registered new interface driver uvcvideo
[ 0.976712,0] USB Video Class driver (v1.1.0)
[ 0.976987,0] ov8820_power_up R:97 P:95 D:0 A:54 1.8:8921_l29
[ 0.977109,0] ov8820_regulator_on: 8921_l29 1800000
[ 1.069922,0] ov8820 chipid: 8820
[ 1.394750,0] ov8820: match_id success
[ 1.395116,0] msm_sensor_register mctl_node_name[0] = video1
[ 1.395177,0] ov8820_power_down
[ 1.430337,0] ov8820_regulator_off: 1.8
[ 1.440500,0] mt9m114_power_up R:76 D:89 A:82 CLK:24000000
[ 1.500137,0] mt9m114 id: 2481
[ 1.500198,0] mt9m114: match_id success
[ 1.500381,0] msm_sensor_register mctl_node_name[1] = video3
[ 1.500503,0] mt9m114_power_down
[ 1.504379,0] Driver for 1-wire Dallas network protocol.
[ 1.521318,0] lm75 10-0048: hwmon0: sensor 'tmp105'
[ 1.542041,0] pm8xxx_tm_probe: OK
[ 1.542591,0] device-mapper: uevent: version 1.0.3
[ 1.542957,0] device-mapper: ioctl: 4.20.0-ioctl (2011-02-02) initialised: [email protected]
[ 1.543293,0] cpuidle: using governor ladder
[ 1.543415,0] cpuidle: using governor menu
[ 1.543781,0] mmc0: mci-version: 18
[ 1.545460,0] mmc0: bam physical base=0x12402000
[ 1.545582,0] mmc0: bam virtual base=0xe18b4000
[ 1.545643,0] mmc0: BAM device registered. bam_handle=0xe06d3a00
[ 1.545856,0] sps:REVISION of BAM 0xe18b4000 is 0x5.
[ 1.546162,0] mmc0: Qualcomm MSM SDCC-BAM at 0x0000000012402000 irq 130
[ 1.546284,0] mmc0: Qualcomm MSM SDCC-DML at 0x0000000012400800
[ 1.546375,0] mmc0: No card detect facilities available
[ 1.546650,0] mmc0: Qualcomm MSM SDCC-core at 0x0000000012400000 irq 136,0 dma -1 dmacrcri -1
[ 1.546741,0] mmc0: 8 bit data mode enabled
[ 1.546833,0] mmc0: 4 bit data mode disabled
[ 1.546894,0] mmc0: polling status mode disabled
[ 1.547016,0] mmc0: MMC clock 400000 -> 96000000 Hz, PCLK 0 Hz
[ 1.547077,0] mmc0: Slot eject status = 0
[ 1.547138,0] mmc0: Power save feature enable = 1
[ 1.547260,0] mmc0: SPS-BAM data transfer mode available
[ 1.547474,0] mmc1: mci-version: 18
[ 1.550495,0] mmc1: bam physical base=0x12182000
[ 1.550556,0] mmc1: bam virtual base=0xe18fc000
[ 1.550648,0] mmc1: BAM device registered. bam_handle=0xdff1c000
[ 1.550831,0] sps:REVISION of BAM 0xe18fc000 is 0x5.
[ 1.551106,0] mmc1: Qualcomm MSM SDCC-BAM at 0x0000000012182000 irq 128
[ 1.551228,0] mmc1: Qualcomm MSM SDCC-DML at 0x0000000012180800
[ 1.551838,0] mmc1: Qualcomm MSM SDCC-core at 0x0000000012180000 irq 134,651 dma -1 dmacrcri -1
[ 1.551899,0] mmc1: 8 bit data mode disabled
[ 1.552021,0] mmc1: 4 bit data mode enabled
[ 1.552083,0] mmc1: polling status mode disabled
[ 1.552144,0] mmc1: MMC clock 400000 -> 96000000 Hz, PCLK 0 Hz
[ 1.552235,0] mmc1: Slot eject status = 1
[ 1.552327,0] mmc1: Power save feature enable = 1
[ 1.552418,0] mmc1: SPS-BAM data transfer mode available
[ 1.552784,0] pm8xxx_rgb_led_probe: num_leds is 3
[ 1.552968,0] Registered led device: red
[ 1.553029,0] create_pm8xxx_rgb_led: LED class red, gpio 175, can sleep = 1
[ 1.553151,0] create_pm8xxx_rgb_led: requested pwm for red, pwm_id=0
[ 1.553273,0] Registered led device: green
[ 1.553334,0] create_pm8xxx_rgb_led: LED class green, gpio 176, can sleep = 1
[ 1.553456,0] create_pm8xxx_rgb_led: requested pwm for green, pwm_id=1
[ 1.553639,0] Registered led device: blue
[ 1.553700,0] create_pm8xxx_rgb_led: LED class blue, gpio 177, can sleep = 1
[ 1.553822,0] create_pm8xxx_rgb_led: requested pwm for blue, pwm_id=2
[ 1.555440,0] Registered led device: torch-flash
[ 1.557424,0] usbcore: registered new interface driver usbhid
[ 1.557485,0] usbhid: USB HID core driver
[ 1.557820,0] logger: created 1024K log 'log_main'
[ 1.557942,0] logger: created 512K log 'log_events'
[ 1.558095,0] logger: created 64K log 'log_radio'
[ 1.558248,0] logger: created 64K log 'log_system'
[ 1.558492,0] zram: num_devices not specified. Using default: 1
[ 1.558583,0] zram: Creating 1 devices ...
[ 1.559072,0] zcache: using lzo compressor
[ 1.559438,0] zcache: cleancache enabled using kernel transcendent memory and compression buddies
[ 1.559804,0] usbcore: registered new interface driver snd-usb-audio
[ 1.560781,0] tabla_probe
[ 1.561666,0] msm_pcm_probe: dev name msm-voip-dsp
[ 1.562368,0] msm_pcm_probe: dev name msm-pcm-dsp
[ 1.562612,0] msm_pcm_probe: dev name msm-multi-ch-pcm-dsp
[ 1.562856,0] msm_pcm_probe: dev name msm-lowlatency-pcm-dsp
[ 1.563619,0] msm_compr_probe: dev name msm-compr-dsp
[ 1.563985,0] msm-pcm-lpa msm-pcm-lpa: msm_pcm_probe: dev name msm-pcm-lpa
[ 1.564840,0] msm8960_configure_headset_mic_gpios: US_EURO_, AV_SWITCH gpios not configured!!!
[ 1.564962,0] msm8960_audio_init Fail to configure headset mic gpios
[ 1.753639,0] MMI Battery EEPROM Read 192 Bytes
[ 1.753761,0] MMI Battery EEPROM Page 2 Checksum = 0
[ 1.753822,0] MMI Battery EEPROM Page 3 Checksum = 0
[ 1.753883,0] MMI Battery EEPROM Copyright Valid = 1
[ 1.754005,0] MMI Battery Full Capacity 0xAE
[ 1.754066,0] MMI Battery Peak Voltage 0xB9
[ 1.754188,0] MMI Battery DC Impedance 0x5E
[ 1.754249,0] MMI Battery Cell ID 0x4157
[ 1.772531,0] asoc: snd-soc-dummy-dai <-> MultiMedia1 mapping ok
[ 1.772928,0] asoc: snd-soc-dummy-dai <-> MultiMedia2 mapping ok
[ 1.773233,0] asoc: snd-soc-dummy-dai <-> CS-VOICE mapping ok
[ 1.773630,0] asoc: snd-soc-dummy-dai <-> VoIP mapping ok
[ 1.773935,0] asoc: snd-soc-dummy-dai <-> MultiMedia3 mapping ok
[ 1.774271,0] asoc: snd-soc-dummy-dai <-> SLIMBUS0_HOSTLESS mapping ok
[ 1.774668,0] asoc: snd-soc-dummy-dai <-> INT_FM_HOSTLESS mapping ok
[ 1.774942,0] asoc: msm-stub-rx <-> msm-dai-q6.241 mapping ok
[ 1.775278,0] asoc: msm-stub-tx <-> msm-dai-q6.240 mapping ok
[ 1.775614,0] asoc: snd-soc-dummy-dai <-> MultiMedia4 mapping ok
[ 1.776010,0] asoc: snd-soc-dummy-dai <-> AUXPCM_HOSTLESS mapping ok
[ 1.776316,0] asoc: snd-soc-dummy-dai <-> HDMI_HOSTLESS mapping ok
[ 1.776682,0] asoc: snd-soc-dummy-dai <-> VoLTE mapping ok
[ 1.777018,0] asoc: snd-soc-dummy-dai <-> Voice2 mapping ok
[ 1.777353,0] asoc: snd-soc-dummy-dai <-> MultiMedia5 mapping ok
[ 1.777628,0] asoc: msm-stub-rx <-> msm-dai-q6.12288 mapping ok
[ 1.777933,0] asoc: msm-stub-tx <-> msm-dai-q6.12289 mapping ok
[ 1.778208,0] asoc: msm-stub-rx <-> msm-dai-q6.12292 mapping ok
[ 1.778513,0] asoc: msm-stub-tx <-> msm-dai-q6.12293 mapping ok
[ 1.778788,0] asoc: msm-stub-rx <-> msm-dai-q6-hdmi.8 mapping ok
[ 1.779063,0] asoc: msm-stub-rx <-> msm-dai-q6.224 mapping ok
[ 1.779337,0] asoc: msm-stub-tx <-> msm-dai-q6.225 mapping ok
[ 1.779642,0] asoc: msm-stub-rx <-> msm-dai-q6.2 mapping ok
[ 1.779917,0] asoc: msm-stub-tx <-> msm-dai-q6.3 mapping ok
[ 1.780192,0] asoc: msm-stub-rx <-> msm-dai-q6.32773 mapping ok
[ 1.780497,0] asoc: msm-stub-tx <-> msm-dai-q6.32772 mapping ok
[ 1.780802,0] asoc: msm-stub-tx <-> msm-dai-q6.32771 mapping ok
[ 1.781107,0] msm8960_audrx_init : Tabla version 2
[ 1.781413,0] tabla_codec tabla_codec: Failed to add route ANCRight Headset Mic->MIC BIAS3 Internal1
[ 1.816847,0] asoc: tabla_rx1 <-> msm-dai-q6.16384 mapping ok
[ 1.818373,0] asoc: tabla_tx1 <-> msm-dai-q6.16385 mapping ok
[ 1.818953,0] asoc: tabla_tx2 <-> msm-dai-q6.16389 mapping ok
[ 1.819471,0] asoc: tabla_rx3 <-> msm-dai-q6.16388 mapping ok
[ 1.821364,0] input: msm8960-snd-card Button Jack as /devices/platform/soc-audio.0/sound/card0/input4
[ 1.821669,0] input: msm8960-snd-card Headset Jack as /devices/platform/soc-audio.0/sound/card0/input5
[ 1.824721,0] oprofile: using arm/armv7-krait
[ 1.824965,0] GACT probability NOT on
[ 1.825057,0] Mirror/redirect action on
[ 1.825118,0] u32 classifier
[ 1.825209,0] Actions configured
[ 1.825331,0] Netfilter messages via NETLINK v0.30.
[ 1.825423,0] nf_conntrack version 0.5.0 (12661 buckets, 50644 max)
[ 1.826033,0] ctnetlink v0.93: registering with nfnetlink.
[ 1.826155,0] NF_TPROXY: Transparent proxy support initialized, version 4.1.0
[ 1.826247,0] NF_TPROXY: Copyright (c) 2006-2007 BalaBit IT Ltd.
[ 1.826705,0] xt_time: kernel timezone is -0000
[ 1.826888,0] ip_tables: (C) 2000-2006 Netfilter Core Team
[ 1.827132,0] arp_tables: (C) 2002 David S. Miller
[ 1.827285,0] TCP bic registered
[ 1.827346,0] TCP cubic registered
[ 1.827407,0] TCP htcp registered
[ 1.827529,0] Initializing XFRM netlink socket
[ 1.828139,0] NET: Registered protocol family 10
[ 1.829391,0] Mobile IPv6
[ 1.829482,0] ip6_tables: (C) 2000-2006 Netfilter Core Team
[ 1.829696,0] IPv6 over IPv4 tunneling driver
[ 1.830489,0] NET: Registered protocol family 17
[ 1.830581,0] NET: Registered protocol family 15
[ 1.830703,0] Bridge firewalling registered
[ 1.830947,0] Bluetooth: RFCOMM TTY layer initialized
[ 1.831039,0] Bluetooth: RFCOMM socket layer initialized
[ 1.831130,0] Bluetooth: RFCOMM ver 1.11
[ 1.831191,0] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 1.831313,0] Bluetooth: BNEP filters: protocol multicast
[ 1.831374,0] Bluetooth: HIDP (Human Interface Emulation) ver 1.2
[ 1.831619,0] L2TP core driver, V2.0
[ 1.831680,0] Registering the dns_resolver key type
[ 1.831741,0] VFP support v0.3: implementor 51 architecture 64 part 4d variant 1 rev 0
[ 1.831954,0] Registering SWP/SWPB emulation handler
[ 1.841385,0] clock_late_init() disabled 199 unused clocks
[ 1.849504,0] MSM Watchdog Initialized
[ 1.854509,1] registered taskstats version 1
[ 1.855943,0] Powering up HoneyBadger
[ 1.909690,0] EMU-det(request_gpios): requesting gpio[2] EMU_SCI_OUT_GPIO-205
[ 1.909812,0] EMU-det(request_gpios): gpio 205 is IN
[ 1.909964,0] EMU-det(request_gpios): exporting gpio EMU_SCI_OUT_GPIO-205
[ 1.910056,0] EMU-det(request_gpios): couldn't find OPTIONAL EMU_ID_EN_GPIO
[ 1.910117,0] EMU-det(request_gpios): requesting gpio[0] EMU_MUX_CTRL0_GPIO-107
[ 1.910239,0] EMU-det(request_gpios): gpio 107 is OUT
[ 1.910300,0] EMU-det(request_gpios): requesting gpio[1] EMU_MUX_CTRL1_GPIO-96
[ 1.910422,0] EMU-det(request_gpios): gpio 96 is OUT
[ 1.910483,0] EMU-det(request_gpios): requesting gpio[4] SEMU_PPD_DET_GPIO-174
[ 1.910605,0] EMU-det(request_gpios): gpio 174 is IN
[ 1.910788,0] EMU-det(request_gpios): exporting gpio SEMU_PPD_DET_GPIO-174
[ 1.910849,0] EMU-det(request_gpios): requesting gpio[5] SEMU_ALT_MODE_EN_GPIO-186
[ 1.911033,0] EMU-det(request_gpios): exporting gpio SEMU_ALT_MODE_EN_GPIO-186
[ 1.911094,0] EMU-det(request_gpios): couldn't find OPTIONAL EMU_ID_GPIO
[ 1.911216,0] EMU-det(request_gpios): requesting gpio[7] DMB_PPD_DET_GPIO-204
[ 1.911338,0] EMU-det(request_gpios): gpio 204 is IN
[ 1.911460,0] EMU-det(request_gpios): exporting gpio DMB_PPD_DET_GPIO-204
[ 1.911582,0] EMU-det(request_gpios): requesting gpio[8] DPLUS_GPIO-192
[ 1.911643,0] EMU-det(request_gpios): requesting gpio[9] DMINUS_GPIO-172
[ 1.911765,0] EMU-det(request_gpios): requesting gpio[10] WHISPER_UART_TX_GPIO-18
[ 1.911857,0] EMU-det(request_gpios): gpio 18 is OUT
[ 1.911979,0] EMU-det(request_gpios): exporting gpio WHISPER_UART_TX_GPIO-18
[ 1.912101,0] EMU-det(request_gpios): requesting gpio[11] WHISPER_UART_RX_GPIO-19
[ 1.912162,0] EMU-det(request_gpios): gpio 19 is IN
[ 1.912345,0] EMU-det(request_gpios): exporting gpio WHISPER_UART_RX_GPIO-19
[ 1.912406,0] EMU-det(request_gpios): requesting gpio[12] TX_PAIR_GPIO-173
[ 1.912528,0] EMU-det(request_gpios): requesting gpio[13] RX_PAIR_GPIO-193
[ 1.912650,0] EMU-det(emu_id_protection_setup): No neccessary action
[ 1.912711,0] EMU-det(emu_det_probe): done with gpios
[ 1.933496,0] mmc0: new high speed DDR MMC card at address 0001
[ 1.934411,0] mmcblk0: mmc0:0001 008G4B 7.40 GiB
[ 1.936365,0] mmcblk0boot0: mmc0:0001 008G4B partition 1 2.00 MiB
[ 1.936975,0] mmcblk0boot1: mmc0:0001 008G4B partition 2 2.00 MiB
[ 1.937158,1] msm_otg msm_otg: phy_reset: success
[ 1.943171,0] mmcblk0: p1 p2 p3 p4 p5 p6 p7 p8 p9 p10 p11 p12 p13 p14 p15 p16 p17 p18 p19 p20 p21 p22 p23 p24 p25 p26 p27 p28 p29 p30 p31 p32 p33 p34 p35 p36 p37 p38 p39
[ 1.947077,0] apanic: Bound to mmc block device 'mmcblk0p33(259:1)'
[ 1.947169,0] apanic: No panic data available
[ 1.950160,0] mmcblk0boot1: unknown partition table
[ 1.953120,0] mmcblk0boot0: unknown partition table
[ 2.039859,1] EMU-det(request_irqs): requesting irq[1] EMU_SCI_OUT_GPIO-577
[ 2.040470,1] EMU-det(request_irqs): requesting irq[0] SEMU_PPD_DET_GPIO-654
[ 2.040866,1] EMU-det(emu_det_probe): done with irqs
[ 2.041233,1] EMU-det(emu_det_probe): registered callback with PM8921
[ 2.042698,1] EMU-det(emu_det_probe): EMU detection driver started
[ 2.043522,1] rtc-pm8xxx rtc-pm8xxx: setting system clock to 2014-04-06 07:20:10 UTC (1396768810)
[ 2.045444,0] Battery Cell ID Found: 3
[ 2.046909,0] read_shutdown_soc: shutdown_soc = 72
[ 2.048069,0] read_ocv_trim: program rev reg is 0x4b
[ 2.053349,0] adjust_remaining_charge_for_shutdown_soc: shutdown_soc = 72 forcing it now
[ 2.053715,0] adjust_remaining_charge_for_shutdown_soc: To force shutdown_soc = 72, rc = 1263806, pc = 72, ocv mv = 4027
[ 2.054082,0] adjust_remaining_charge_for_shutdown_soc: test revlookup pc = 73 for ocv = 4027
[ 2.054265,0] calculate_state_of_charge: Forcing SHUTDOWN_SOC = 72
[ 2.054631,0] pm8921_bms_probe: OK battery_capacity_at_boot=72 volt = 3755310 ocv = 4027000
[ 2.057652,0] get_prop_batt_status: alarm_state=0,batt_valid=0
[ 2.061193,0] pm8921_is_battery_charging: called before init
[ 2.061468,0] calculate_state_of_charge: Forcing SHUTDOWN_SOC = 72
[ 2.070502,0] get_prop_batt_status: alarm_state=0,batt_valid=0
[ 2.070837,0] get_prop_batt_status: alarm_state=0,batt_valid=0
[ 2.073462,0] calculate_state_of_charge: Forcing SHUTDOWN_SOC = 72
[ 2.083503,0] EMU-det(emu_det_vbus_state): PM8921 USBIN callback: out
[ 2.086464,0] Battery Cell ID Found: 3
[ 2.089760,0] ALSA device list:
[ 2.089913,0] #0: msm8960-snd-card
[ 2.090248,0] Warning: unable to open an initial console.
[ 2.092415,0] Freeing init memory: 992K
[ 2.108713,1] SELinux: 1024 avtab hash slots, 3544 rules.
[ 2.113749,1] SELinux: 1024 avtab hash slots, 3544 rules.
[ 2.113810,1] SELinux: 1 users, 2 roles, 344 types, 1 bools, 1 sens, 1024 cats
[ 2.114054,1] SELinux: 84 classes, 3544 rules
[ 2.114878,1] SELinux: Completing initialization.
[ 2.114970,1] SELinux: Setting up existing superblocks.
[ 2.115061,1] SELinux: initialized (dev sysfs, type sysfs), uses genfs_contexts
[ 2.115183,1] SELinux: initialized (dev rootfs, type rootfs), uses genfs_contexts
[ 2.115305,1] SELinux: initialized (dev bdev, type bdev), not configured for labeling
[ 2.115428,1] SELinux: initialized (dev proc, type proc), uses genfs_contexts
[ 2.115550,1] SELinux: initialized (dev tmpfs, type tmpfs), uses transition SIDs
[ 2.115641,1] SELinux: initialized (dev debugfs, type debugfs), uses genfs_contexts
[ 2.121806,1] SELinux: initialized (dev sockfs, type sockfs), uses task SIDs
[ 2.121928,1] SELinux: initialized (dev pipefs, type pipefs), uses task SIDs
[ 2.121989,1] SELinux: initialized (dev anon_inodefs, type anon_inodefs), not configured for labeling
[ 2.122112,1] SELinux: initialized (dev devpts, type devpts), uses transition SIDs
[ 2.122264,1] SELinux: initialized (dev selinuxfs, type selinuxfs), uses genfs_contexts
[ 2.122386,1] SELinux: initialized (dev tmpfs, type tmpfs), uses transition SIDs
[ 2.122539,1] SELinux: initialized (dev sysfs, type sysfs), uses genfs_contexts
[ 2.129772,0] EMU-det(detection_work): state CONFIG, time since last run -297880 ms
[ 2.130169,0] EMU-det(alt_mode_setup): SEMU_ALT_MODE_EN is standard
[ 2.139783,0] EMU-det(detection_work): state SAMPLE, time since last run 10 ms
[ 2.141217,0] EMU-det(adc_vbus_get): vbus=34 mV
[ 2.199816,0] EMU-det(get_sense): SEMU_PPD_DET: ID floating
[ 2.252189,1] type=1403 audit(1396768810.700:2): policy loaded auid=4294967295 ses=4294967295
[ 2.252403,1] SELinux: Loaded policy from /sepolicy
[ 2.256493,1] SELinux: Loaded file_contexts from /file_contexts
[ 2.260247,0] EMU-det(get_sense): No need to check DMB_PPD_DET_N
[ 2.260613,0] EMU-det(sense_dp_dm): D+/D- mask: 0x10
[ 2.260827,0] EMU-det(get_sense): irq=0, SESS_END, FLOAT, NO_DCD,
[ 2.261132,0] EMU-det(detection_work): SAMPLE keep waiting ...
[ 2.269952,0] EMU-det(detection_work): state SAMPLE, time since last run 130 ms
[ 2.271448,0] EMU-det(adc_vbus_get): vbus=34 mV
[ 2.329925,0] EMU-det(get_sense): SEMU_PPD_DET: ID floating
[ 2.389928,0] EMU-det(get_sense): No need to check DMB_PPD_DET_N
[ 2.390141,0] EMU-det(sense_dp_dm): D+/D- mask: 0x10
[ 2.390477,0] EMU-det(get_sense): irq=0, SESS_END, FLOAT, NO_DCD,
[ 2.390691,0] EMU-det(detection_work): state IDENTIFY, time since last run 120 ms
[ 2.392217,0] EMU-det(adc_vbus_get): vbus=34 mV
[ 2.460369,0] EMU-det(get_sense): SEMU_PPD_DET: ID floating
[ 2.519975,0] EMU-det(get_sense): No need to check DMB_PPD_DET_N
[ 2.520189,0] EMU-det(sense_dp_dm): D+/D- mask: 0x10
[ 2.520524,0] EMU-det(get_sense): irq=0, SESS_END, FLOAT, NO_DCD,
[ 2.520708,0] EMU-det(detection_work): no accessory
[ 2.521043,0] EMU-det(notify_accy): EMU detection Notify: NONE
[ 2.521471,0] EMU-det(alt_mode_setup): SEMU_ALT_MODE_EN is standard
[ 2.521776,0] EMU-det(emu_id_protection_setup): No neccessary action
[ 2.521989,0] msm_otg msm_otg: received DISCONNECTED event
[ 2.522325,0] msm_otg msm_otg: UNDEFINED --> IDLE
[ 2.523638,0] pm8921_chg_accy_notify: pm8921_chg_accy_notify: accy_state: 7
[ 2.524767,0] msm_otg msm_otg: USB in low power mode
[ 2.526781,0] calculate_state_of_charge: Forcing SHUTDOWN_SOC = 72
[ 3.609095,1] init: could not import file '/init.carrier.rc' from '/init.rc'
[ 3.610621,1] init (1): /proc/1/oom_adj is deprecated, please use /proc/1/oom_score_adj instead.
[ 3.611689,1] init: do_chown: Could not access /selinux/booleans
[ 3.668213,0] calculate_state_of_charge: Forcing SHUTDOWN_SOC = 72
[ 4.120921,1] SELinux: initialized (dev cgroup, type cgroup), uses genfs_contexts
[ 4.122325,1] SELinux: initialized (dev tmpfs, type tmpfs), uses transition SIDs
[ 4.129742,1] SELinux: initialized (dev tmpfs, type tmpfs), uses transition SIDs
[ 4.130627,1] SELinux: initialized (dev tmpfs, type tmpfs), uses transition SIDs
[ 4.131603,1] SELinux: initialized (dev tmpfs, type tmpfs), uses transition SIDs
[ 4.280970,1] SELinux: initialized (dev cgroup, type cgroup), uses genfs_contexts
[ 4.311277,0] zcache: created ephemeral tmem pool, id=0, client=65535
[ 4.312620,0] EXT4-fs (mmcblk0p37): recovery complete
[ 4.312833,0] EXT4-fs (mmcblk0p37): mounted filesystem with ordered data mode. Opts: noauto_da_alloc,barrier=1
[ 4.313200,0] SELinux: initialized (dev mmcblk0p37, type ext4), uses xattr
[ 4.324034,0] zcache: created ephemeral tmem pool, id=1, client=65535
[ 4.324767,0] EXT4-fs (mmcblk0p39): mounted filesystem with ordered data mode. Opts: nomblk_io_submit,errors=remount-ro
[ 4.325164,0] SELinux: initialized (dev mmcblk0p39, type ext4), uses xattr
[ 4.325927,0] zcache: destroyed pool id=1, cli_id=65535
[ 4.360842,1] fs_mgr: Running /system/bin/e2fsck on /dev/block/platform/msm_sdcc.1/by-name/userdata
[ 4.368197,1] atmxt_tdat_callback: Processing atmxt-r2.tdat...
[ 4.369082,1] input: atmxt-i2c as /devices/virtual/input/input6
[ 4.401312,0] atmxt_set_ic_state: IC state UNKNOWN -> PRESENT
[ 4.401709,0] atmxt_restart_ic: Family ID: 0x82, Variant ID: 0x1A, Version: 0x10, Build: 0xAA, Matrix: 24x14, Objects: 22
[ 4.408484,0] atmxt_message_handler6: Touch IC reset complete.
[ 4.408698,0] atmxt_message_handler6: Touch IC is calibrating.
[ 4.409064,0] atmxt_set_ic_state: IC state PRESENT -> ACTIVE
[ 4.409705,0] atmxt_set_drv_state: Driver state INIT -> ACTIVE
[ 4.410254,0] atmxt_tdat_callback: Touch initialization successful.
[ 4.411719,1] atmxt_active_handler: Received invalid data: 0xFF 0x90 0xE9 0xD5 0x0C 0x00 0x00 0x00 0xFF 0x90 0xE9 0xD5 0x0C 0x00 0x00 0x00.
[ 4.412238,1] atmxt_active_handler: Touch active handler failed with error code -22.
[ 4.413764,1] atmxt_message_handler6: Touch IC calibration complete.
[ 4.558583,1] atmxt_message_handler6: Touch IC is calibrating.
[ 4.591271,1] atmxt_message_handler6: Touch IC calibration complete.
[ 5.421303,0] lm3532_bl_work: enabling PWM
[ 32.090920,0] shutdown_soc_work: not forcing shutdown soc anymore
[ 1404.024049,0] Report pwrkey press event
[ 1404.087501,0] pm8xxx_irq_mask_ack: mask acking rouge irq=664 pmirq=224
[ 1410.810773,0] resout_irq_handler PMIC Initiated shutdown
[ 1410.810834,0] PMIC Initiated shutdown cpu_power_off cpu=0
[ 1410.810834,1] PMIC Initiated shutdown cpu_power_off cpu=1
[ 1410.811017,0] Powering off the SoC
[ 1410.811109,0] Calling scm to disable arbiter
[ 1410.811231,0] SCM returned even when asked to busy loop rc=-4
[ 1410.811292,0] waiting on pmic to shut msm down
18 Corrected bytes, 0 unrecoverable blocks
CPU type is ACPU PVS: Fast
That was after like 20-30 minutes of booting. Thanks in advance
EDIT:
Oups. "The text that you have entered is too long (39454 characters). Please shorten it to 30000 characters long." I'll cut the begining...
EDIT2:
It booted up! I rebooted it once again and left it at my desk. When I came back after 1h, it was already on the home screen! thanks for help kabaldan I think such info could be put as NOTICE on main rom page, I think normally everyone would consider its stuck when it's not booting in a few minutes...
Thank you Kabaldan!
It took exactly 40 minutes my Photon Q to reboot from /data filesystem check. I used:
* cm-11-20140505-SNAPSHOT-M6-moto_msm8960.zip from download.cyanogenmod.org/?type=snapshot&device=moto_msm8960
* TWRP 2.7.0.1
* gapps-kk-20140105-signed.zip from wiki.cyanogenmod.org/w/Google_Apps
micx_pl said:
Output of /proc/last_kmsg:
Code:
…
[ 4.591271,1] atmxt_message_handler6: Touch IC calibration complete.
[ 5.421303,0] lm3532_bl_work: enabling PWM
[U][ 32.090920,0] shutdown_soc_work: not forcing shutdown soc anymore[/U]
[ 1404.024049,0] Report pwrkey press event
[ 1404.087501,0] pm8xxx_irq_mask_ack: mask acking rouge irq=664 pmirq=224
[ 1410.810773,0] resout_irq_handler PMIC Initiated shutdown
…
Click to expand...
Click to collapse
Thanks for that intel. Am I right, that this is the "breaking point" in the log, when the mentioned repair starts and -later- the reset is initiated? My log has the same "breaking point" in it: https://www.dropbox.com/s/0iqdr30jmhft2co/last_kmsg
So is this the same phenomenon? This is the first time I pulled a log using adb, but do not recognise anything going on here.
kabaldan said:
If you want to get some information about what's going on while the boot is stalled, …
Click to expand...
Click to collapse
Edit:
May this also help with errors mounting certain partions within TWRP and is there a way to fix this - maybe through adb? Because doing a quick search I found this guide (fore theKindle, though): http://forum.xda-developers.com/showthread.php?t=1949372
Schattenspieler said:
Thanks for that intel. Am I right, that this is the "breaking point" in the log, when the mentioned repair starts and -later- the reset is initiated? My log has the same "breaking point" in it: https://www.dropbox.com/s/0iqdr30jmhft2co/last_kmsg
So is this the same phenomenon? This is the first time I pulled a log using adb, but do not recognise anything going on here.
Edit:
May this also help with errors mounting certain partions within TWRP and is there a way to fix this - maybe through adb? Because doing a quick search I found this guide (fore theKindle, though): http://forum.xda-developers.com/showthread.php?t=1949372
Click to expand...
Click to collapse
The significant point in the above log is:
Code:
[ 4.360842,1] fs_mgr: Running /system/bin/e2fsck on /dev/block/platform/msm_sdcc.1/by-name/userdata
and the important fact is that it is not followed by any more e2fsck messages, which means that for the duration of the log, e2fsck hasn't finished the work yet.
e2fsck is still repairing userdata and the init is waiting for userdata mount to continue the boot process, but in the end the user keeps power button pressed to enforce reboot, so e2fsck is aborted and the filesystem left damaged.
In your log, you can even see that the active process at the point of premature, user-enforced reboot was e2fsck:
Code:
[ 279.105569,0] Report pwrkey press event
[ 286.105966,0] Power key held for 7 seconds; will reboot on release.
[ 286.473981,1] current process is 140:e2fsck, prio is 120.
kabaldan said:
In your log, you can even see that the active process at the point of premature, user-enforced reboot was e2fsck:
Click to expand...
Click to collapse
Now that you mention it! I didn't think, e2fsck was a specific command, but more of a boot state code (sort of thing). But I should have searched. Now i see the "e2fs" (the filesystem) and "ck" as in check. :silly:
I now restored a TWRP backup with 4.4.3 and have been fine since. So there is either something wrong with the 4.4.4 CarbonROM on the Photon oder with TWRP, when installing the/some ROMs. Seeing this thread, I tend towards the second.
Schattenspieler said:
Now that you mention it! I didn't think, e2fsck was a specific command, but more of a boot state code (sort of thing). But I should have searched. Now i see the "e2fs" (the filesystem) and "ck" as in check. :silly:
I now restored a TWRP backup with 4.4.3 and have been fine since. So there is either something wrong with the 4.4.4 CarbonROM on the Photon oder with TWRP, when installing the/some ROMs. Seeing this thread, I tend towards the second.
Click to expand...
Click to collapse
If you had let it boot, it probably would have been fine.