All times are UTC-06:00




Post new topic  Reply to topic  [ 26 posts ] 
Author Message
PostPosted: Thu Sep 30, 2010 12:13 am 
Offline

Joined: Tue Mar 31, 2009 10:24 pm
Posts: 171
Gentlemen,

As it was already noted by Peter in the blog section, the boot process in maverick ends rather abruptly during init with the following error messages:
Code:
init: ureadahead main process (1033) terminated with status 5
mountall: Disconnected from Plymouth
init: plymouth main process (1034) killed by SEGV signal
init: plymouth-splash main process (1201) terminated with status 2
(remark: Above is Peter's error log. In my case ureadahead main process is 1032 and plymouth main process is 1033)

For reference, here's is what kramic with a similar 'stock' 2.6.31.14 kernel (from gitorious::efikamx-10.07.11) says at the exact same place during init (karmic does not use plymouth):
Code:
init: ureadahead main process (1031) terminated with status 5
init: procps main process (1045) terminated with status 255
and the boot continues normally.

Below is dmesg from the problematic maverick-minimal on a rev. 1.3 smarttop, kernel 2.6.31.4-no_devtmpfs.
Code:
U-Boot 2009.01-1.2.19-lange51 (May 06 2010 - 11:52:45)

CPU: Freescale i.MX51 family 3.0V at 800 MHz
mx51 pll1: 800MHz
mx51 pll2: 665MHz
mx51 pll3: 216MHz
ipg clock : 66500000Hz
ipg per clock : 665000000Hz
uart clock : 66500000Hz
cspi clock : 54000000Hz
Board: MX51 LANGE51 3.0 [POR]
DRAM: 512 MB
JEDEC ID: 0xbf:0x25:0x4a
Reading SPI NOR flash 0x40000 [0x10000 bytes] -> ram 0x975f06e8
.SUCCESS

*** Warning - bad CRC, using default environment

In: serial
Out: serial
Err: serial
board id: 1.0.1, rev1.3
Boot Source: SPI NOR FLASH BOOT
SD card.
Vendor: Man 1b OEM SM "00000" Date 07/2010
Product: 320698060
Revision: 1.0
reading uImage
reading system.conf

** Unable to read "system.conf" from mmc 0:1 **
Boot Cmd: run sd_boot
Hit any key to stop autoboot: 0
## Error: "base_cmd99" not defined
SD card.
Vendor: Man 1b OEM SM "00000" Date 07/2010
Product: 320698060
Revision: 1.0
reading uImage
## Booting kernel from Legacy Image at 90007fc0 ...
Image Name: Linux-2.6.31.14-efikamx
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 2657404 Bytes = 2.5 MB
Load Address: 90008000
Entry Point: 90008000
Verifying Checksum ... OK
Loading Kernel Image ... OK
OK

Starting kernel ...

Uncompressing Linux................................................................................................................................................................. done, b.
[ 0.000000] Linux version 2.6.31.14-efikamx (neko@excel) (gcc version 4.4.1 (Sourcery G++ Lite 2010q1-202) ) #4 PREEMPT Sun Sep 26 11:34:20 CDT 2010
[ 0.000000] CPU: ARMv7 Processor [412fc085] revision 5 (ARMv7), cr=10c53c7f
[ 0.000000] CPU: VIPT nonaliasing data cache, VIPT nonaliasing instruction cache
[ 0.000000] Machine: Genesi Efika MX (Smarttop)
[ 0.000000] Memory policy: ECC disabled, Data cache writeback
[ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 105664
[ 0.000000] Kernel command line: noinitrd console=ttymxc0,115200 console=tty1 root=/dev/mmcblk0p2 rw
[ 0.000000] PID hash table entries: 2048 (order: 11, 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] Memory: 416MB = 416MB total
[ 0.000000] Memory: 416700KB available (4556K code, 528K data, 136K init, 0K highmem)
[ 0.000000] SLUB: Genslabs=11, HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
[ 0.000000] Hierarchical RCU implementation.
[ 0.000000] NR_IRQS:368
[ 0.000000] MXC IRQ initialized
[ 0.000000] MXC_Early serial console at MMIO 0x73fbc000 (options '115200')
[ 0.000000] console [ttymxc0] enabled
[ 0.000000] Console: colour dummy device 80x30
[ 0.000000] console handover: boot [ttymxc0] -> real [tty1]
[ 0.000000] Linux version 2.6.31.14-efikamx (neko@excel) (gcc version 4.4.1 (Sourcery G++ Lite 2010q1-202) ) #4 PREEMPT Sun Sep 26 11:34:20 CDT 2010
[ 0.000000] CPU: ARMv7 Processor [412fc085] revision 5 (ARMv7), cr=10c53c7f
[ 0.000000] CPU: VIPT nonaliasing data cache, VIPT nonaliasing instruction cache
[ 0.000000] Machine: Genesi Efika MX (Smarttop)
[ 0.000000] Memory policy: ECC disabled, Data cache writeback
[ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 105664
[ 0.000000] Kernel command line: noinitrd console=ttymxc0,115200 console=tty1 root=/dev/mmcblk0p2 rw
[ 0.000000] PID hash table entries: 2048 (order: 11, 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] Memory: 416MB = 416MB total
[ 0.000000] Memory: 416700KB available (4556K code, 528K data, 136K init, 0K highmem)
[ 0.000000] SLUB: Genslabs=11, HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
[ 0.000000] Hierarchical RCU implementation.
[ 0.000000] NR_IRQS:368
[ 0.000000] MXC IRQ initialized
[ 0.000000] MXC_Early serial console at MMIO 0x73fbc000 (options '115200')
[ 0.000000] console [ttymxc0] enabled
[ 0.000000] Console: colour dummy device 80x30
[ 0.000000] console handover: boot [ttymxc0] -> real [tty1]
[ 0.000000] Calibrating delay loop... 799.53 BogoMIPS (lpj=3997696)
[ 0.000000] Mount-cache hash table entries: 512
[ 0.000000] CPU: Testing write buffer coherency: ok
[ 0.000000] regulator: core version 0.5
[ 0.000000] NET: Registered protocol family 16
[ 0.000000] i.MX IRAM pool: 128 KB@0x9a840000
[ 0.000000] IRAM READY
[ 0.000000] CPU is i.MX51 Revision 3.0
[ 0.000000] MXC GPIO hardware
[ 0.000000] Efika MX: IOMUX for Board ID (3 pins)
[ 0.000000] Efika MX: IOMUX for General GPIO Stuff (7 pins)
[ 0.000000] Efika MX: IOMUX for SPI (6 pins)
[ 0.000000] Efika MX: IOMUX for PMIC (1 pins)
[ 0.000000] Efika MX: IOMUX for I2C (4 pins)
[ 0.000000] Efika MX: IOMUX for USB (29 pins)
[ 0.000000] Efika MX: IOMUX for ATA (29 pins)
[ 0.000000] Efika MX: Initializing SD card IOMUX (external, mmc0)
[ 0.000000] Efika MX: IOMUX for WDOG (1.2) (1 pins)
[ 0.000000] Efika MX: IOMUX for LED (3 pins)
[ 0.000000] Efika MX: IOMUX for Power Key (1 pins)
[ 0.000000] Efika MX: AIPS1_BASE_ADDR = 0x73f00000
[ 0.000000] Efika MX: AIPS1_BASE_ADDR_VIRT = 0xf7e00000, io_pg_offst = 0x3df8
[ 0.000000] Efika MX: PHYS_OFFSET = 0x90000000
[ 0.000000] Efika MX Revision 1.3
[ 0.000000] Using SDMA I.API
[ 0.000000] MXC DMA API initialized
[ 0.000000] bio: create slab <bio-0> at 0
[ 0.000000] SCSI subsystem initialized
[ 0.000000] CSPI: mxc_spi-0 probed
[ 0.000000] usbcore: registered new interface driver usbfs
[ 0.000000] usbcore: registered new interface driver hub
[ 0.000000] usbcore: registered new device driver usb
[ 0.000000] IPU DMFC NORMAL mode: 1(0~1), 5B(4,5), 5F(6,7)
[ 0.000000] mc13892 Rev 2.0 FinVer 2 detected
[ 0.000000] Initializing regulators for Efika MX
[ 0.000000] regulator: SW1: 600 <--> 1375 mV
[ 0.000000] regulator: SW2: 900 <--> 1850 mV
[ 0.000000] regulator: SW3: 1100 <--> 1850 mV
[ 0.000000] regulator: SW4: 1100 <--> 1850 mV
[ 0.000000] regulator: SWBST: 0 mV
[ 0.000000] regulator: VIOHI: 0 mV
[ 0.000000] regulator: VPLL: 1050 <--> 1800 mV
[ 0.000000] regulator: VDIG: 1650 mV
[ 0.000000] regulator: VSD: 1800 <--> 3150 mV
[ 0.000000] regulator: VUSB2: 2400 <--> 2775 mV
[ 0.000000] regulator: VVIDEO: 2775 mV
[ 0.000000] regulator: VAUDIO: 2300 <--> 3000 mV
[ 0.000000] regulator: VCAM: 2500 <--> 3000 mV fast normal
[ 0.000000] regulator: VGEN1: 1200 <--> 3150 mV
[ 0.000000] regulator: VGEN2: 1200 <--> 3150 mV
[ 0.000000] regulator: VGEN3: 1800 <--> 2900 mV
[ 0.000000] regulator: VUSB: 0 mV
[ 0.000000] regulator: GPO1: 0 mV
[ 0.000000] regulator: GPO2: 0 mV
[ 0.000000] regulator: GPO3: 0 mV
[ 0.000000] regulator: GPO4: 0 mV
[ 0.000000] Device spi1.0 probed
[ 0.524215] NET: Registered protocol family 2
[ 0.524549] IP route cache hash table entries: 4096 (order: 2, 16384 bytes)
[ 0.525432] TCP established hash table entries: 16384 (order: 5, 131072 bytes)
[ 0.526011] TCP bind hash table entries: 16384 (order: 4, 65536 bytes)
[ 0.526308] TCP: Hash tables configured (established 16384 bind 16384)
[ 0.526335] TCP reno registered
[ 0.526522] NET: Registered protocol family 1
[ 0.527340] LPMode driver module loaded
[ 0.527375] Static Power Management for Freescale i.MX51
[ 0.527660] PM driver module loaded
[ 0.527922] sdram autogating driver module loaded
[ 0.528233] Bus freq driver module loaded
[ 0.528290] mxc_dvfs_core_probe
[ 0.528560] DVFS driver module loaded
[ 0.528594] i.MXC CPU frequency driver
[ 0.529227] DVFS PER driver module loaded
[ 0.530926] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[ 0.530998] msgmni has been set to 814
[ 0.534713] alg: No test for stdrng (krng)
[ 0.535067] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
[ 0.535112] io scheduler noop registered (default)
[ 0.535148] io scheduler cfq registered
[ 0.535655] *** sii9022_probe
[ 0.537949] *** mxc_init_fb vmode= video-mode=1 clock_auto=1
[ 0.537975] registering framebuffer for HDMI
[ 0.539194] mode_option=800x600-16@60
[ 0.540091] mxc_ipu mxc_ipu: Channel already disabled 9
[ 0.540103] mxc_ipu mxc_ipu: Channel already uninitialized 9
[ 0.540120] mxcfb_di_clock_adjust pixelclk=25000 rate=80000000
[ 0.540170] orig: parent=pll3 clk=216000000 this=ipu_di0_clk di_clk=27000000
[ 0.540295] adjust: parent=pll3 clk=80000000 this=ipu_di0_clk di_clk=40000000 ret=0 ret=0
[ 0.540406] skip sii9022_reinit!
[ 0.540436] mxc_ipu mxc_ipu: WARNING: adapt panel end blank lines
[ 0.708897] pclk 25000 same to previous one, skipping!
[ 0.708906] skip sii9022_reinit!
[ 0.708924] mxc_ipu mxc_ipu: WARNING: adapt panel end blank lines
[ 0.733355] Console: switching to colour frame buffer device 100x37
[ 0.878888] pclk 25000 same to previous one, skipping!
[ 0.878896] skip sii9022_reinit!
[ 0.878914] mxc_ipu mxc_ipu: WARNING: adapt panel end blank lines
[ 0.919570] registering framebuffer for VPU overlay
[ 0.922173] mxc_sdc_fb mxc_sdc_fb.2: Unable to allocate framebuffer memory
[ 0.924497] mxc_sdc_fb: probe of mxc_sdc_fb.2 failed with error -12
[ 0.926787] *** sii9022 lcd_probe
[ 0.929079] *** sii9022 lcd_init_fb
[ 0.948867] mxcfb_read_edid2
[ 0.978717] 00ffffffffffff001e6d01000101010102100103805c34960acf32a3574cb023
[ 0.981311] 094b4b2fce003140454061400101010101010101010164190040410026301888
[ 0.983910] 3600980732000018000000fd00384b1e3d08000a202020202020000000fc0034
[ 0.986549] 3250433344562d55440a2020000000fc005044500a20202020202020202001bc
[ 0.989224] 020313f144840503022315075065030c001000011d007251d01e206e28550098
[ 0.991919] 073200001e011d8018711c1620582c250098073200009e8c0ad08a20e02d1010
[ 0.994617] 3e96009807320000188c0ad08a20e02d10103e96009807320000180000000000
[ 0.997327] 00000000000000000000000000000000000000000000000000000000000000c4
[ 1.000260] ----------------------------------------
[ 1.002701] Revision number: 3
[ 1.005067] DTV underscan: Supported
[ 1.007424] Basic audio: Supported
[ 1.009794] Sink device: TV, HDMI
[ 1.012150] ========================================
[ 1.014521] Display Information (EDID)
[ 1.016864] ========================================
[ 1.019236] EDID Version 1.3
[ 1.021571] Manufacturer: GSM
[ 1.023921] Model: 1
[ 1.026220] Serial#: 16843009
[ 1.028485] Year: 2006 Week 2
[ 1.030707] Monitor Name: 42PC3DV-UD
[ 1.032875] Monitor Name: PDP
[ 1.034987] Display Characteristics:
[ 1.037071] Monitor Operating Limits: From EDID
[ 1.039204] H: 30-61KHz V: 56-75Hz DCLK: 80MHz
[ 1.041313] Digital Display Input
[ 1.041383] Sync:
[ 1.045356] Max H-size in cm: 92
[ 1.047344] Max V-size in cm: 52
[ 1.049298] Gamma: 2.50
[ 1.051197] DPMS: Active no, Suspend no, Standby no
[ 1.053092] RGB Color Display
[ 1.054945] Chroma
[ 1.056745] RedX: 0.640 RedY: 0.340
[ 1.058599] GreenX: 0.300 GreenY: 0.690
[ 1.060462] BlueX: 0.137 BlueY: 0.038
[ 1.062272] WhiteX: 0.293 WhiteY: 0.295
[ 1.064043] First DETAILED Timing is preferred
[ 1.065795] Detailed Timings
[ 1.067488] "1024x768@60" 65 1024 1048 1184 1344 768 771 777 806 -hsync -vsync
[ 1.069308] Supported VESA Modes
[ 1.071027] 640x480@60Hz
[ 1.072698] 640x480@72Hz
[ 1.074320] 640x480@75Hz
[ 1.075866] 800x600@56Hz
[ 1.077376] 800x600@60Hz
[ 1.078863] 800x600@72Hz
[ 1.080322] 800x600@75Hz
[ 1.081773] 1024x768@60Hz
[ 1.083191] 1024x768@70Hz
[ 1.084556] 1024x768@75Hz
[ 1.085884] Manufacturer's mask: 0
[ 1.087198] Standard Timings
[ 1.088512] 640x480@60Hz
[ 1.089842] 800x600@60Hz
[ 1.091149] 1024x768@60Hz
[ 1.092449] Detail Timings
[ 1.093743] ----------------------------------------
[ 1.095102] EIA/CEA-861 Information
[ 1.096447] Revision number: 3
[ 1.097763] DTV underscan: Supported
[ 1.099087] Basic audio: Supported
[ 1.100383] Detailed Timings
[ 1.101676] "1280x720@60" 74 1280 1390 1430 1650 720 725 730 750 +hsync +vsync
[ 1.103126] "1920x1080i@60" 74 1920 2008 2052 2200 1080 1084 1094 1124 +hsync +vsync
[ 1.104648] "720x480@59" 27 720 736 798 858 480 489 495 525 -hsync -vsync
[ 1.106214] "720x480@59" 27 720 736 798 858 480 489 495 525 -hsync -vsync
[ 1.107744] ========================================
[ 1.109245] Monitor/TV supported modelines
[ 1.110757] "1024x768@60" 65.02 1024 1048 1184 1344 768 771 777 806 -hsync -vsync
[ 1.112398] "640x480@60" 25.200 640 656 752 800 480 490 492 525 -hsync -vsync
[ 1.114076] "640x480@72" 31.500 640 664 704 832 480 489 491 520 -hsync -vsync
[ 1.115750] "640x480@75" 31.500 640 656 720 840 480 481 484 500 -hsync -vsync
[ 1.117423] "800x600@56" 36.01 800 824 896 1024 600 601 603 625 +hsync +vsync
[ 1.119133] "800x600@60" 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync
[ 1.120814] "800x600@72" 50.00 800 856 976 1040 600 637 643 666 +hsync +vsync
[ 1.122444] "800x600@75" 49.500 800 816 896 1056 600 601 604 625 +hsync +vsync
[ 1.124052] "1024x768@60" 65.02 1024 1048 1184 1344 768 771 777 806 -hsync -vsync
[ 1.125716] "1024x768@70" 75.01 1024 1048 1184 1328 768 771 777 806 -hsync -vsync
[ 1.127385] "1024x768@75" 78.802 1024 1040 1136 1312 768 769 772 800 +hsync +vsync
[ 1.129131] "640x480@60" 25.200 640 656 752 800 480 490 492 525 -hsync -vsync
[ 1.130934] "800x600@60" 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync
[ 1.132783] "1024x768@60" 65.02 1024 1048 1184 1344 768 771 777 806 -hsync -vsync
[ 1.134707] "1280x720@60" 74.250 1280 1390 1430 1650 720 725 730 750 +hsync +vsync
[ 1.136673] "1920x1080i@60" 74.250 1920 2008 2052 2200 1080 1084 1094 1124 +hsync +vsync
[ 1.138739] "720x480@59" 27.00 720 736 798 858 480 489 495 525 -hsync -vsync
[ 1.140890] "720x480@59" 27.00 720 736 798 858 480 489 495 525 -hsync -vsync
[ 1.143027] 640x480@75 pclk=31746 removed (lower margin does not meet IPU restrictions)
[ 1.145199] 800x600@56 pclk=27777 removed (lower margin does not meet IPU restrictions)
[ 1.147335] 800x600@60 pclk=25000 removed (lower margin does not meet IPU restrictions)
[ 1.149479] 800x600@75 pclk=20202 removed (lower margin does not meet IPU restrictions)
[ 1.151620] 1024x768@75 pclk=12690 removed (lower margin does not meet IPU restrictions)
[ 1.153822] 800x600@60 pclk=25000 removed (lower margin does not meet IPU restrictions)
[ 1.156092] 1920x1080i@60 pclk=13468 removed (interlaced)
[ 1.158371] 720x480@59 pclk=37037 removed (duplicate)
[ 1.160667] mxcfb_update_default_var mode_opt=<NULL> vmode=
[ 1.162976] 1280x720@60 pclk=13468 nearest mode is 1280x720@60 pclk=13468
[ 1.165342] nearest mode geometry 1280 720 13468
[ 1.167727] nearest mode timings 13468 220 110 20 5 40 5
[ 1.170129] nearest mode flag 1 sync 3 vmode 0
[ 1.172476] mxcfb_di_clock_adjust pixelclk=13468 rate=148500000
[ 1.174861] orig: parent=pll3 clk=80000000 this=ipu_di0_clk di_clk=40000000
[ 1.177328] adjust: parent=pll3 clk=148500000 this=ipu_di0_clk di_clk=74250000 ret=0 ret=0
[ 1.179827] sii9022_reinit 1280x720 13468
[ 1.322892] sii9022 1-0039: geometry 1280 720 1280 720 0
[ 1.325341] sii9022 1-0039: timings 13468 220 110 20 5 40 5
[ 1.327711] sii9022 1-0039: accel 0 sync 3 vmode=0
[ 1.330036] sii9022 1-0039: pclk 7425 refresh 6024 total x 1650 y 750
[ 1.332395] sii9022 1-0039: vmap idx=6 vcode=4
[ 1.335150] hdmi audio mute
[ 1.345598] hdmi audio unmute
[ 1.488893] pclk 13468 same to previous one, skipping!
[ 1.488902] sii9022_reinit 1280x720 13468 same to previous one, skipping
[ 1.508902] IPU DMFC DP HIGH RESOLUTION: 1(0,1), 5B(2~5), 5F(6,7)
[ 1.525898] sii9022 1-0039: turning on LCD
[ 1.779133] Serial: MXC Internal UART driver
[ 1.779477] mxcintuart.0: ttymxc0 at MMIO 0x73fbc000 (irq = 31) is a Freescale i.MX
[ 1.779686] console [ttymxc0] enabled
[ 3.706003] mxcintuart.1: ttymxc1 at MMIO 0x73fc0000 (irq = 32) is a Freescale i.MX
[ 3.718424] mxcintuart.2: ttymxc2 at MMIO 0x7000c000 (irq = 33) is a Freescale i.MX
[ 3.734793] loop: module loaded
[ 3.743081] pata_fsl pata_fsl: rchan=29 wchan=28
[ 3.751799] scsi0 : pata_fsl
[ 3.758973] ata1: PATA max UDMA/44 irq 70
[ 3.768765] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[ 3.888887] fsl-ehci fsl-ehci.0: Freescale On-Chip EHCI Host Controller
[ 3.899879] fsl-ehci fsl-ehci.0: new USB bus registered, assigned bus number 1
[ 3.939202] fsl-ehci fsl-ehci.0: irq 18, io base 0x73f80000
[ 3.948383] ata1.00: ATA-8: SanDisk pSSD-P2 8GB, SSD 5.20, max UDMA/133
[ 3.958632] ata1.00: 15649200 sectors, multi 0: LBA48
[ 3.967617] fsl-ehci fsl-ehci.0: USB 2.0 started, EHCI 1.00
[ 3.977639] usb usb1: configuration #1 chosen from 1 choice
[ 3.987753] hub 1-0:1.0: USB hub found
[ 3.995328] hub 1-0:1.0: 1 port detected
[ 4.009424] ata1.00: configured for UDMA/44
[ 4.029201] scsi 0:0:0:0: Direct-Access ATA SanDisk pSSD-P2 SSD PQ: 0 ANSI: 5
[ 4.042210] sd 0:0:0:0: [sda] 15649200 512-byte logical blocks: (8.01 GB/7.46 GiB)
[ 4.053777] sd 0:0:0:0: [sda] Write Protect is off
[ 4.062394] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 4.075781] sda:
[ 4.078802] sd 0:0:0:0: Attached scsi generic sg0 type 0
[ 4.092335] sda1 sda2
[ 4.100277] sd 0:0:0:0: [sda] Attached SCSI disk
[ 4.218892] usb 1-1: new high speed USB device using fsl-ehci and address 2
[ 4.229694] fsl-ehci fsl-ehci.1: Freescale On-Chip EHCI Host Controller
[ 4.240901] fsl-ehci fsl-ehci.1: new USB bus registered, assigned bus number 2
[ 4.278899] fsl-ehci fsl-ehci.1: irq 14, io base 0x73f80200
[ 4.388872] fsl-ehci fsl-ehci.1: USB 2.0 started, EHCI 1.00
[ 4.398823] usb usb2: configuration #1 chosen from 1 choice
[ 4.408678] hub 2-0:1.0: USB hub found
[ 4.416262] hub 2-0:1.0: 1 port detected
[ 4.424680] usbcore: registered new interface driver libusual
[ 4.435311] mice: PS/2 mouse device common for all mice
[ 4.445026] MXC keypad loaded
[ 4.452542] mc13892 rtc probe start
[ 4.460855] pmic_rtc pmic_rtc.1: rtc core: registered pmic_rtc as rtc0
[ 4.471500] mc13892 rtc probe succeed
[ 4.479789] usb 1-1: configuration #1 chosen from 1 choice
[ 4.489377] i2c /dev entries driver
[ 4.497647] Linux video capture interface: v2.00
[ 4.507990] MXC Video Output MXC Video Output.0: Registered device video0
[ 4.518700] MXC WatchDog Driver 2.0
[ 4.526116] clk: Unable to get requested clock: wdog_clk
[ 4.535772] MXC Watchdog # 0 Timer: initial timeout 60 sec
[ 4.545475] cpuidle: using governor ladder
[ 4.553367] cpuidle: using governor menu
[ 4.561647] PMIC Character device: successfully loaded
[ 4.571431] VPU initialized
[ 4.578326] mxsdhci: MXC Secure Digital Host Controller Interface driver
[ 4.588881] mxsdhci: MXC SDHCI Controller Driver.
[ 4.597687] mmc0: SDHCI detect irq 128 irq 1 INTERNAL DMA
[ 4.607320] Registered led device: efikamx:green
[ 4.615720] Registered led device: efikamx:red
[ 4.634088] Registered led device: efikamx:blue
[ 4.646593] usbcore: registered new interface driver usbhid
[ 4.655834] usbhid: v2.6:USB HID core driver
[ 4.675007] Advanced Linux Sound Architecture Driver Version 1.0.20.
[ 4.733684] sgtl5000-i2c 1-000a: SGTL5000 revision 17
[ 4.748901] usb 2-1: new high speed USB device using fsl-ehci and address 2
[ 4.808977] mmc0: new high speed SDHC card at address 0002
[ 4.818518] mmcblk0: mmc0:0002 00000 7.49 GiB
[ 4.826829] mmcblk0: p1 p2
[ 4.840437] No device for DAI imx-ssi-1-0
[ 4.847909] No device for DAI imx-ssi-1-1
[ 4.855361] No device for DAI imx-ssi-2-0
[ 4.862676] No device for DAI imx-ssi-2-1
[ 4.870843] DMA Sound Buffers Allocated:UseIram=1 buf->addr=1fff6000 buf->area=9a856000 size=24576
[ 4.883489] DMA Sound Buffers Allocated:UseIram=1 buf->addr=a82b8000 buf->area=f9e30000 size=24576
[ 4.895765] asoc: SGTL5000 <-> imx-ssi-2-0 mapping ok
[ 4.930399] usb 2-1: configuration #1 chosen from 1 choice
[ 4.940035] hub 2-1:1.0: USB hub found
[ 4.947191] hub 2-1:1.0: 4 ports detected
[ 4.966274] ALSA device list:
[ 4.972783] #0: imx-3stack (SGTL5000)
[ 4.980747] TCP cubic registered
[ 4.987303] NET: Registered protocol family 17
[ 4.995063] ThumbEE CPU extension supported.
[ 5.002600] VFP support v0.3: implementor 41 architecture 3 part 30 variant c rev 2
[ 5.015324] regulator_init_complete: incomplete constraints, leaving GPO4 on
[ 5.026013] regulator_init_complete: incomplete constraints, leaving GPO3 on
[ 5.036345] regulator_init_complete: incomplete constraints, leaving GPO2 on
[ 5.046591] regulator_init_complete: incomplete constraints, leaving GPO1 on
[ 5.056779] regulator_init_complete: incomplete constraints, leaving VGEN3 on
[ 5.066864] regulator_init_complete: incomplete constraints, leaving VGEN2 on
[ 5.077016] regulator_init_complete: incomplete constraints, leaving VGEN1 on
[ 5.087098] regulator_init_complete: incomplete constraints, leaving VCAM on
[ 5.097032] regulator_init_complete: incomplete constraints, leaving VAUDIO on
[ 5.107102] regulator_init_complete: incomplete constraints, leaving VSD on
[ 5.116716] regulator_init_complete: incomplete constraints, leaving SWBST on
[ 5.127032] pmic_rtc pmic_rtc.1: setting system clock to 2010-09-30 03:51:26 UTC (1285818686)
[ 5.317949] VFS: Mounted root (ext2 filesystem) on device 179:2.
[ 5.327180] Freeing init memory: 136K
[ 5.334079] usb 2-1.1: new high speed USB device using fsl-ehci and address 3
[ 5.467782] usb 2-1.1: configuration #1 chosen from 1 choice
Things appear normal above.

So, what can we do to help ourselves? - Lose plymouth, or at least its splash-screen.

And here's where I got stuck. After editing all occurrences of '/bin/plymouth show-splash' in the plymouth config files to something harmless like 'plymouth help' the init process stops with a complaint that /root is not ready to be mounted, press 'S' to skip or 'M' for manual intervention, or something along these lines.

As I am out of steam for tonight, I'm just leaving here my findings for somebody else to give it a try.


Top
   
 Post subject:
PostPosted: Thu Sep 30, 2010 2:26 am 
Offline

Joined: Thu Jul 28, 2005 12:41 am
Posts: 1066
I removed a couple of plymouth packages (only plymouth and libplymouth2 remaind). Booting still stops, but now at least "alt+ctrl+del" works, I don't need to disconnect power any more. I'll let you know, if I find anything.

_________________
CzP
http://czanik.blogs.balabit.com/


Top
   
 Post subject:
PostPosted: Thu Sep 30, 2010 2:53 am 
Offline

Joined: Thu Jul 28, 2005 12:41 am
Posts: 1066
OK, problem solved. It was not plymouth, which caused the booting troubles. It was mountall, or rather fstab in the maverick image. It uses labels to identify partitions. Obviously, my system did not use these labels and mountall failed. Workaround: label the partitions. In my case I extraced Maverick to the pata device, so:
Code:
e2label /dev/sda2 MAV_SYS
doslaboel /dev/sda1 MAV_BOOT
Strangely I have a 1280x720 resolution, which looks strange on a 1680x1050 22" screen...

On TO2 MMC does not work with the released kernel, but AFAIK it is being worked on.

_________________
CzP
http://czanik.blogs.balabit.com/


Top
   
 Post subject:
PostPosted: Thu Sep 30, 2010 11:34 am 
Offline

Joined: Tue Mar 31, 2009 10:24 pm
Posts: 171
Thanks, Peter, great work. Looks like I'll be booting up maverick tonight, after all.


Top
   
 Post subject:
PostPosted: Sun Oct 03, 2010 3:36 am 
Offline

Joined: Thu Jul 28, 2005 12:41 am
Posts: 1066
What are your experiences? For me the new kernel / Maverick are quite problematic on my TO2 nettop:

* Xorg eats all available CPU time (idle time is constantly 0% while X runs)

* mmc does not work. If I put in an SD card, all I get is an "MMC disconnected" message.

* halt/reboot does not work and file systems don't get umounted properly. This way filesystem needs to be recovered on each startup from one or more errors

And a problem, which also effects Karmic (with the kernel from April): if I have an USB HDD attached at boot time, the device itself is recognized (it's also shown on the output of lsusb), but partitions on it are not found. This way I can't put it into fstab. Partitions are found if I disconnect and reconnect the HDD or connect it only after the machine is booted to the login prompt. OpenSUSE and Ubuntu x86 don't have this problem.

_________________
CzP
http://czanik.blogs.balabit.com/


Top
   
 Post subject:
PostPosted: Sun Oct 03, 2010 5:12 am 
Offline

Joined: Tue Feb 03, 2009 7:32 am
Posts: 19
Location: Toronto, Canada
I definitely have the same issue(s) as Peter has described (same kernel).

I just received my netbook on Friday and I'm very pleased with it overall - thanks Genesi!

To what Peter has indicated, I too see the issue with X (X.org) using significant CPU. Additionally, the fact that reboot does not work.

I'm on a learning curve with it and hope to provide more feedback later this week.

Cheers,

Gabor


Top
   
 Post subject:
PostPosted: Sun Oct 03, 2010 8:59 am 
Offline

Joined: Tue Mar 31, 2009 10:24 pm
Posts: 171
Peter, here are my observations:

* front MMC has been out of order on TO2 with 2.6.31.14 kernel from branch efikamx-10.07.11 since the beginning (it does work on TO3 though). I had intentions for a 'find the differences' side-by-side investigation with 2.6.31.12.3, but I don't have access to a TO2 anymore, so such an exercise would be of dubious value.

* Xorg behaves normally here, but consider the fact I run naked X for my purposes, i.e.
Code:
sudo service gdm stop
sudo X -noreset
so my setup might not be a representative case.

What constantly eats a tiny CPU% in my case, is one of the wlan-related daemons - RtmpMlmeTask. May have something to do with the fact that the wlan interface keeps trying to do something on my wlan, as its TX/RX count keeps steadily growing over time (but I'm running my smarttop wired).

* From what I remember, I used to have issues with rebooting 2.6.31.14 + karmic on TO2 initially, but the effect was eventually gone - cannot really tell when. Currently TO3 too has reboot issues with the 'stock' 31.14 kernel + maverick, but that's a low-priority issue for me, and I've done nothing to investigate it.


Top
   
 Post subject:
PostPosted: Mon Oct 04, 2010 12:19 pm 
Offline
Genesi

Joined: Tue Feb 07, 2006 4:49 pm
Posts: 145
Location: San Antonio, TX
Quote:
Peter, here are my observations:

* front MMC has been out of order on TO2 with 2.6.31.14 kernel from branch efikamx-10.07.11 since the beginning (it does work on TO3 though). I had intentions for a 'find the differences' side-by-side investigation with 2.6.31.12.3, but I don't have access to a TO2 anymore, so such an exercise would be of dubious value.

* Xorg behaves normally here, but consider the fact I run naked X for my purposes, i.e.
Code:
sudo service gdm stop
sudo X -noreset
so my setup might not be a representative case.

What constantly eats a tiny CPU% in my case, is one of the wlan-related daemons - RtmpMlmeTask. May have something to do with the fact that the wlan interface keeps trying to do something on my wlan, as its TX/RX count keeps steadily growing over time (but I'm running my smarttop wired).

* From what I remember, I used to have issues with rebooting 2.6.31.14 + karmic on TO2 initially, but the effect was eventually gone - cannot really tell when. Currently TO3 too has reboot issues with the 'stock' 31.14 kernel + maverick, but that's a low-priority issue for me, and I've done nothing to investigate it.
You may want to try to update your kernel again. There were a few different commits to git recently which (should) fix the mmc slot (at least the front slot, I haven't tested the internal on my TO2.)


Top
   
 Post subject:
PostPosted: Tue Oct 05, 2010 12:49 am 
Offline

Joined: Thu Jul 28, 2005 12:41 am
Posts: 1066
OK. How can I check it out from git? http://www.gitorious.org/efikamx/linux- ... x-10.07.11 , which is linked from the kernel support page seems to be over a month old, so dates well before your fixes...

_________________
CzP
http://czanik.blogs.balabit.com/


Top
   
 Post subject:
PostPosted: Tue Oct 05, 2010 8:08 am 
Offline

Joined: Tue Mar 31, 2009 10:24 pm
Posts: 171
Quote:
You may want to try to update your kernel again. There were a few different commits to git recently which (should) fix the mmc slot (at least the front slot, I haven't tested the internal on my TO2.)
Good to hear. I'm TO2-less but I know people who will be happy.

Apropos, I pull occasionally from efikamx-10.07.11, and there has been nothing new in that branch. Are all new changes going into the smartbook branch now?


Top
   
 Post subject:
PostPosted: Tue Oct 05, 2010 8:56 am 
Offline
Site Admin

Joined: Fri Sep 24, 2004 1:39 am
Posts: 1589
Location: Austin, TX
Quote:
OK. How can I check it out from git? http://www.gitorious.org/efikamx/linux- ... x-10.07.11 , which is linked from the kernel support page seems to be over a month old, so dates well before your fixes...
An EfikaMX kernel will build fine from the efikasb-10.07.11 branch.

The idea is we're merging the two platforms together so they both use the same IOMUX code and so on - otherwise a good proportion of it is duplicated. That's what the new branch is for, Smartbook support is basically not completed (yet) and will be final when all the fixes we made get merged back down into one "efikamx" codeset (with two machine descriptions but basically common init and code).

_________________
Matt Sealey


Top
   
PostPosted: Tue Oct 05, 2010 9:01 am 
Offline
Site Admin

Joined: Fri Sep 24, 2004 1:39 am
Posts: 1589
Location: Austin, TX
Quote:
Below is dmesg from the problematic maverick-minimal on a rev. 1.3 smarttop, kernel
2.6.31.4-no_devtmpfs.
Please use the standard (i.e. devtmpfs is implied enabled) kernel for Maverick :)

Plymouth is harmless and will give you a splash screen when we fix Initrd support. That relies on U-Boot being updated. Nearly there.

Booting up to a point where it just hangs after plymouth and ureadahead are culled isn't something I've seen. I've seen a rather long delay here (10 to 30 seconds) on random boxes, but never a hang that did not get it to the login prompt.

_________________
Matt Sealey


Top
   
PostPosted: Tue Oct 05, 2010 9:41 am 
Offline

Joined: Tue Mar 31, 2009 10:24 pm
Posts: 171
Quote:
Quote:
Below is dmesg from the problematic maverick-minimal on a rev. 1.3 smarttop, kernel
2.6.31.4-no_devtmpfs.
Please use the standard (i.e. devtmpfs is implied enabled) kernel for Maverick :)

Plymouth is harmless and will give you a splash screen when we fix Initrd support. That relies on U-Boot being updated. Nearly there.

Booting up to a point where it just hangs after plymouth and ureadahead are culled isn't something I've seen. I've seen a rather long delay here (10 to 30 seconds) on random boxes, but never a hang that did not get it to the login prompt.
Yes, I'm running the devtmpfs kernel now. Part of the original issue for me was that that plymouth SIGSEGV message was the last thing visible on my screen, as a phase offset in the video was putting the last lines off screen. Anyway, Peter spotted the offender (the volume names in fstab), so it's all loading and running now.

Speaking of which, I know now what Peter meant when he mentioned Xorg eating too much CPU% while idling. Yesterday I had my smarttop accidentially powered off by my 10-month old (lit power buttons and toddlers don't mix). Subsequently, the machine was powered on and left alone for approx. 30 min. When I returned to it I discovered one very hot smarttop. I've been able to get it so hot only under some very heavy lifting. Instead, this time it had merely booted, launched X and stayed at an error message dialogue box for the time it was unattended. Apparently that had produced enough activity to heat up the machine. Some part of the desktop is clearly busy when it should not be.


Top
   
PostPosted: Wed Oct 06, 2010 7:35 pm 
Offline
Site Admin

Joined: Fri Sep 24, 2004 1:39 am
Posts: 1589
Location: Austin, TX
Quote:
Quote:
Quote:
Below is dmesg from the problematic maverick-minimal on a rev. 1.3 smarttop, kernel
2.6.31.4-no_devtmpfs.
Please use the standard (i.e. devtmpfs is implied enabled) kernel for Maverick :)

Plymouth is harmless and will give you a splash screen when we fix Initrd support. That relies on U-Boot being updated. Nearly there.

Booting up to a point where it just hangs after plymouth and ureadahead are culled isn't something I've seen. I've seen a rather long delay here (10 to 30 seconds) on random boxes, but never a hang that did not get it to the login prompt.
Yes, I'm running the devtmpfs kernel now. Part of the original issue for me was that that plymouth SIGSEGV message was the last thing visible on my screen, as a phase offset in the video was putting the last lines off screen. Anyway, Peter spotted the offender (the volume names in fstab), so it's all loading and running now.
Indeed, the hang is 100% down to rootwait waiting for a disk (slow SD card usually making it wait more) so :)
Quote:
Speaking of which, I know now what Peter meant when he mentioned Xorg eating too much CPU% while idling. Yesterday I had my smarttop accidentially powered off by my 10-month old (lit power buttons and toddlers don't mix).
https://bugs.launchpad.net/ubuntu/+sour ... bug/640725

Please feel free to try the patch I noted, and to "bump" the bug to say this bug affects you. We are not sure it 100% fixes the problem (sigh) but it helps.
Quote:
Some part of the desktop is clearly busy when it should not be.
We think upstart is trying to grab a hold of the terminal and X is looking for events that match this kind of thing. The immediate way to get it to happen is to start the Xfce Terminal. Guaranteed invoking of the bug there. But it is not limited to that. We've had ideas like font smoothing or some kind of Cairo clip thing taking too much CPU but they got fixed and patched out of Maverick before we shipped the release.

_________________
Matt Sealey


Top
   
PostPosted: Wed Oct 06, 2010 7:41 pm 
Offline
Site Admin

Joined: Fri Sep 24, 2004 1:39 am
Posts: 1589
Location: Austin, TX
Quote:
Part of the original issue for me was that that plymouth SIGSEGV message was the last thing visible on my screen, as a phase offset in the video was putting the last lines off screen.
Try the latest of the efikasb-10.07.11 branch with the patch I made to cull modes that are not IPU compliant.

http://www.gitorious.org/efikamx/linux- ... 455cbf4bfb

It gets rid of a lot of useful modes, but.. none of them should phase offset anymore by having this weirdo hack applied to them.

This was done the day after I released the kernels to PD so nobody has it.. I'm not sure it's corrected and it's not tested 100% yet but I'd be curious to see how well it goes.

I have a debate raging in my head as to whether to build a new kernel NOW or just wait until next week when we're done with the merge.

_________________
Matt Sealey


Top
   
Display posts from previous:  Sort by  
Post new topic  Reply to topic  [ 26 posts ] 

All times are UTC-06:00


Who is online

Users browsing this forum: No registered users and 17 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

Search for:
Jump to:  
PowerDeveloper.org: Copyright © 2004-2012, Genesi USA, Inc. The Power Architecture and Power.org wordmarks and the Power and Power.org logos and related marks are trademarks and service marks licensed by Power.org.
All other names and trademarks used are property of their respective owners. Privacy Policy
Powered by phpBB® Forum Software © phpBB Group