On Monday 07 November 2005 06:04 am, Radek Podgorny wrote:
> > On Sat, Nov 05, 2005 at 11:03:06PM +0100, Radek Podgorny wrote:
> >> Can't there be a problem in:
> >>
> >> samcop_sdi_card_power: MMC subsystem requesting bogus clock rate 0.
> >> Hardcoding
> >> prescaler to 255
> >>
> >> ?
> >
> > I thought the same thing. But the mmc system does not request a clock
> > rate when it is detecting the card. It doesn't determine a clock rate
> > until it has found a card and figured out how fast the card can go.
>
> Yup, the card is being detected just fine AFAIK. There only seems to be a
> problem with mounting it as root (cannot read it? whatever?)
>
> >> How is it even possible this message is printed several times during the
> >> boot?
> >> Shouldn't it be printed only once?
> >
> > This I don't have an answer to. I would expect the mmc system to only
> > require one power on for the card, another for the slot itself and then
> > a final call to set the clock rate for the card. But it prints out three
> > times at least. And since it doesn't print this when the clock rate is
> > properly supplied, it means that this function is called 4 times. A
> > little excessive. But this is purely mmc mechanics. The samcop driver is
> > just doing what the mmc system wants it to do.
>
> Well, can't this be a bug in mmc? It the mmc code vanilla or are there any
> hh specific modifications in your tree?
>
> Is there a way to enable something like "kernel call tree" so I can see
> what happens?
>
> >> My observations show the boot process stops for several seconds after
> >> the
> >>
> >> NET: Registered protocol family 1
> >>
> >> and before
> >>
> >> samcop_sdi_card_power: MMC subsystem requesting bogus clock rate 0.
> >> Hardcoding
> >> prescaler to 255
> >> Kernel panic - not syncing: VFS: Unable to mount root fs on
> >> unknown-block(254,2)
> >>
> >> Looks like samcop code is waiting for something. Any ideas what should I
> >> do to
> >> get more info on what's going on?
> >
> > I see something similar when I load the modules. Matt Reimer
> > hypothesised that it was the sdi timeout waiting for a large card to
> > respond. Which makes a lot of sense. But I have been unable to detect
> > the timeout condition when this happens.
>
> Sounds reasonable, we can investigate this later.
>
> > You can get more information if you turn on mmc debugging (configuration
> > option before kernel compilation). But you may need to instrument some
> > code in drivers/mmc/samcop_sdi.c to get down to the section you are
> > interested in.
>
> The debugging is already enabled, looks like I'll have to add more debug
> info to the code. The problem is I don't know what info may be valuable.
> Can you help me with what can be useful for you, please?
Send your .config.
> Could you post your bootup log (in the root-from-sd config) so I can see
> what it's supposed to look like? Thanks...
Below is my dmesg output on h2200.
Matt
Linux version 2.6.13-hh1 (mreimer_at_sermons.desiringGod.org) (gcc version 3.4.1)
#165 Fri Nov 4 17:46:58 PST 2005
CPU: XScale-PXA255 [69052d06] revision 6 (ARMv5TE)
Machine: HP iPAQ H2200
Memory policy: ECC disabled, Data cache writeback
Memory clock: 99.53MHz (*27)
Run Mode clock: 398.13MHz (*4)
Turbo Mode clock: 398.13MHz (*1.0, inactive)
CPU0: D VIVT undefined 5 cache
CPU0: I cache: 32768 bytes, associativity 32, 32 byte lines, 32 sets
CPU0: D cache: 32768 bytes, associativity 32, 32 byte lines, 32 sets
Built 1 zonelists
Kernel command line: cachepolicy=writeback console=ttyS0,115200n8
root=/dev/mmcblk0p1
PID hash table entries: 512 (order: 9, 8192 bytes)
Console: colour dummy device 80x30
Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
Memory: 64MB = 64MB total
Memory: 62592KB available (1810K code, 335K data, 80K init)
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
NET: Registered protocol family 16
platform_device_register hamcop
platform_device_register pxa2xx-keys
platform_device_register h2200 battery
platform_device_register s3c2410-ts
platform_device_register pxa2xx-mci
platform_device_register pxa2xx-udc
platform_device_register pxa2xx-fb
platform_device_register pxa2xx-uart
platform_device_register pxa2xx-uart
platform_device_register pxa2xx-uart
platform_device_register pxa2xx-i2c
platform_device_register pxa2xx-i2s
platform_device_register pxa2xx-uart
hamcop: using irq 104-129 on irq 28
platform_device_register samcop adc
platform_device_register hamcop nand
platform_device_register samcop owm
platform_device_register hamcop leds
platform_device_register samcop dma
SAMCOP DMA Driver, (c) 2003-2004 Simtec Electronics
DMA channel 0 at c4902400, irq 120
platform_device_register samcop sdi
NetWinder Floating Point Emulator V0.97 (double precision)
JFFS2 version 2.2. (NAND) (C) 2001-2003 Red Hat, Inc.
Initializing Cryptographic API
ttyS0 at MMIO 0x40100000 (irq = 15) is a FFUART
ttyS1 at MMIO 0x40200000 (irq = 14) is a BTUART
ttyS2 at MMIO 0x40700000 (irq = 13) is a STUART
ttyS3 at MMIO 0x41600000 (irq = 0) is a HWUART
io scheduler noop registered
RAMDISK driver initialized: 16 RAM disks of 8192K size 1024 blocksize
NAND device: Manufacturer ID: 0xec, Chip ID: 0x75 (Samsung NAND 32MiB 3,3V
8-bit)
Scanning device for bad blocks
Using builtin partition definition
Creating 4 MTD partitions on "NAND 32MiB 3,3V 8-bit":
0x00000000-0x00004000 : "HTC first-stage bootstrap"
0x00004000-0x00028000 : "HTC rescue bootloader"
0x00028000-0x00168000 : "second-stage loader"
0x00168000-0x02000000 : "root fs"
pxa2xx_udc: version 4-May-2005
dmabounce: registered device samcop sdi on platform bus
samcop sdi: probe: irq=124 irq_cd=31 dma=0.
samcop sdi: initialisation done.
NET: Registered protocol family 2
IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
TCP established hash table entries: 4096 (order: 3, 32768 bytes)
TCP bind hash table entries: 4096 (order: 2, 16384 bytes)
TCP: Hash tables configured (established 4096 bind 4096)
TCP reno registered
TCP bic registered
NET: Registered protocol family 1
mmc0: host does not support reading read-only switch. assuming write-enable.
mmcblk0: mmc0:0002 SD512 503296KiB
mmcblk0: p1
EXT2-fs warning: mounting unchecked fs, running e2fsck is recommended
VFS: Mounted root (ext2 filesystem).
Freeing init memory: 80K
INIT: version 2.86 booting
Creating initial device nodes...
mount: Mounting proc on /proc failed: Device or resource busy
/dev/fb/0: No such file or directory
Setting up IP spoofing protection: rp_filter.
Configuring network interfaces... done.
Starting portmap daemon: portmap.
Turning echo off on /dev/tts/3
Nothing to be done
INIT: Entering runlevel: 5
Starting Dropbear SSH server: dropbear.
Starting advanced power management daemon: apmd.
apmd[1956]: apmd 3.2.1 interfacing with apm driver 1.13 and APM BIOS 1.2
Starting system message bus: dbus-1.
Starting syslogd/klogd: done
Starting Bluetooth subsystem: hcid sdpdCan't open HIDP control socket:
Protocol
not supported
hidd rfcomm.
Starting at daemon: atd.
Starting GPE display manager: gpe-dm
Familiar Linux v0.8.3-prerelease-snapshot-20051006 h2200 tts/0
h2200 login:
Received on Mon Nov 07 2005 - 19:49:15 EST
This archive was generated by hypermail 2.2.0 : Mon Nov 07 2005 - 19:49:23 EST