[Xenomai-help] Adeos patched kernel hangs mounting root file system

[Xenomai-help] Adeos patched kernel hangs mounting root file system

[Bob Feretich]

  I have been trying to apply the Adeos patch to a 2.6.31 system. The 
patch applies cleanly, but the system (BeagleBoard) boot hangs waiting 
for the root file system to be mounted via the SD card (/dev/mmcblk0p2).

Note: Although the Adeos patch is applied, Xenomai is not configured in 
the .config file.
(The boot still hangs in the same spot if Xenomai is configured, but a 
few more Xenomai messages appear,)
> Reading boot sector
> Loading u-boot.bin from mmc
>
>
> U-Boot 2009.06-rc2 (Nov 02 2009 - 23:57:20)
>
> OMAP3530-GP ES3.0, CPU-OPP2 L3-165MHz
> OMAP3 Beagle board + LPDDR/NAND
> DRAM:  256 MB
> NAND:  256 MiB
> In:    serial
> Out:   serial
> Err:   serial
> Board revision C
> Die ID #317000030000000004013f8a1701a01b
> Hit any key to stop autoboot:  0
> mmc1 is available
> reading uImage
>
> 1911632 bytes read
> ## Booting kernel from Legacy Image at 80300000 ...
>    Image Name:   Angstrom/2.6.31/beagleboard
>    Image Type:   ARM Linux Kernel Image (uncompressed)
>    Data Size:    1911568 Bytes =  1.8 MB
>    Load Address: 80008000
>    Entry Point:  80008000
>    Verifying Checksum ... OK
>    Loading Kernel Image ... OK
> OK
>
> Starting kernel ...
>
> Uncompressing 
> Linux................................................................................................
> ......................... done, booting the kernel.
> Linux version 2.6.31-omap1 (Bob@domain.hid) (gcc version 4.3.3 (GCC) 
> ) #2 Sun Jul 18 18:16:32 PDT 2010
> CPU: ARMv7 Processor [411fc083] revision 3 (ARMv7), cr=10c53c7f
> CPU: VIPT nonaliasing data cache, VIPT nonaliasing instruction cache
> Machine: OMAP3 Beagle Board
> Memory policy: ECC disabled, Data cache writeback
> OMAP3430 ES3.0
> SRAM: Mapped pa 0x40200000 to va 0xe3000000 size: 0x100000
> Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 65024
> Kernel command line: console=ttyS2,115200n8 root=/dev/mmcblk0p2 rw 
> rootfstype=ext3 rootwait
> PID hash table entries: 1024 (order: 10, 4096 bytes)
> Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
> Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
> Memory: 128MB 128MB = 256MB total
> Memory: 255744KB available (3320K code, 332K data, 132K init, 0K highmem)
> NR_IRQS:402
> Clocking rate (Crystal/Core/MPU): 26.0/332/500 MHz
> Reprogramming SDRC clock to 332000000 Hz
> GPMC revision 5.0
> IRQ: Found an INTC at 0xd8200000 (revision 4.0) with 96 interrupts
> Total of 96 interrupts on 1 active controller
> OMAP34xx GPIO hardware version 2.5
> OMAP clockevent source: GPTIMER1 at 13000000 Hz
> I-pipe 1.16-01: pipeline enabled.
> Console: colour dummy device 80x30
> Calibrating delay loop... 498.07 BogoMIPS (lpj=2490368)
> Mount-cache hash table entries: 512
> CPU: Testing write buffer coherency: ok
> regulator: core version 0.5
> NET: Registered protocol family 16
> Found NAND on CS0
> Registering NAND on CS0
> OMAP DMA hardware revision 4.0
> bio: create slab <bio-0> at 0
> i2c_omap i2c_omap.1: bus 1 rev3.12 at 2600 kHz
> twl4030: PIH (irq 7) chaining IRQs 368..375
> twl4030: power (irq 373) chaining IRQs 376..383
> twl4030: gpio (irq 368) chaining IRQs 384..401
> regulator: VMMC1: 1850 <--> 3150 mV normal standby
> regulator: VDAC: 1800 mV normal standby
> regulator: VUSB1V5: 1500 mV normal standby
> regulator: VUSB1V8: 1800 mV normal standby
> regulator: VUSB3V1: 3100 mV normal standby
> regulator: VPLL2: 1800 mV normal standby
> regulator: VSIM: 1800 <--> 3000 mV normal standby
> i2c_omap i2c_omap.3: bus 3 rev3.12 at 100 kHz
> SCSI subsystem initialized
> twl4030_usb twl4030_usb: Initialized TWL4030 USB module
> usbcore: registered new interface driver usbfs
> usbcore: registered new interface driver hub
> usbcore: registered new device driver usb
> musb_hdrc: version 6.0, musb-dma, otg (peripheral+host), debug=0
> musb_hdrc: USB OTG mode controller at d80ab000 using DMA, IRQ 92
> NET: Registered protocol family 2
> IP route cache hash table entries: 2048 (order: 1, 8192 bytes)
> TCP established hash table entries: 8192 (order: 4, 65536 bytes)
> TCP bind hash table entries: 8192 (order: 3, 32768 bytes)
> TCP: Hash tables configured (established 8192 bind 8192)
> TCP reno registered
> NET: Registered protocol family 1
> VFS: Disk quotas dquot_6.5.2
> Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
> JFFS2 version 2.2. (NAND) �© 2001-2006 Red Hat, Inc.
> msgmni has been set to 499
> alg: No test for stdrng (krng)
> Block layer SCSI generic (bsg) driver version 0.4 loaded (major 253)
> io scheduler noop registered
> io scheduler anticipatory registered (default)
> io scheduler deadline registered
> io scheduler cfq registered
> Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
> serial8250.0: ttyS0 at MMIO 0x4806a000 (irq = 72) is a ST16654
> serial8250.1: ttyS1 at MMIO 0x4806c000 (irq = 73) is a ST16654
> serial8250.2: ttyS2 at MMIO 0x49020000 (irq = 74) is a ST16654
> console [ttyS2] enabled
> brd: module loaded
> loop: module loaded
> i2c /dev entries driver
> usbcore: registered new interface driver asix
> usbcore: registered new interface driver cdc_ether
> usbcore: registered new interface driver net1080
> usbcore: registered new interface driver cdc_subset
> usbcore: registered new interface driver zaurus
> usbmon: debugfs is not available
> ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
> ehci-omap ehci-omap.0: OMAP-EHCI Host Controller
> ehci-omap ehci-omap.0: new USB bus registered, assigned bus number 1
> ehci-omap ehci-omap.0: irq 77, io mem 0x48064800
> ehci-omap ehci-omap.0: USB 2.0 started, EHCI 1.00
> usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
> usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
> usb usb1: Product: OMAP-EHCI Host Controller
> usb usb1: Manufacturer: Linux 2.6.31-omap1 ehci_hcd
> usb usb1: SerialNumber: ehci-omap.0
> usb usb1: configuration #1 chosen from 1 choice
> hub 1-0:1.0: USB hub found
> hub 1-0:1.0: 3 ports detected
> g_ether gadget: using random self ethernet address
> g_ether gadget: using random host ethernet address
> usb0: MAC c2:de:6e:33:e8:94
> usb0: HOST MAC de:88:51:65:85:d5
> g_ether gadget: Ethernet Gadget, version: Memorial Day 2008
> g_ether gadget: g_ether ready
> musb_hdrc musb_hdrc: MUSB HDRC host driver
> musb_hdrc musb_hdrc: new USB bus registered, assigned bus number 2
> usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
> usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
> usb usb2: Product: MUSB HDRC host driver
> usb usb2: Manufacturer: Linux 2.6.31-omap1 musb-hcd
> usb usb2: SerialNumber: musb_hdrc
> usb usb2: configuration #1 chosen from 1 choice
> hub 2-0:1.0: USB hub found
> hub 2-0:1.0: 1 port detected
> twl4030_rtc twl4030_rtc: rtc core: registered twl4030_rtc as rtc0
> sdhci: Secure Digital Host Controller Interface driver
> sdhci: Copyright(c) Pierre Ossman
> mmci-omap-hs mmci-omap-hs.0: Failed to get debounce clock
> TCP cubic registered
> NET: Registered protocol family 17
> NET: Registered protocol family 15
> RPC: Registered udp transport module.
> RPC: Registered tcp transport module.
> Power Management for TI OMAP3.
> VFP support v0.3: implementor 41 architecture 3 part 30 variant c rev 1
> regulator_init_complete: incomplete constraints, leaving VDVI on
> regulator_init_complete: incomplete constraints, leaving VDAC on
> twl4030_rtc twl4030_rtc: setting system clock to 2000-01-01 00:05:44 
> UTC (946685144)
> Waiting for root device /dev/mmcblk0p2...

I think the hang may have something to do with "OMAP clockevent source: 
GPTIMER1 at 13000000 Hz". The Adeo patch changes this from the GPTimer12 
at 32768 Hz.
(Note that on this chip, GPTimer12 is one of the timers with special 
time-of-day (exact 1 millisecond tick capability) logic.)

The below is the diff result comparing against a successful boot log 
without the Adeos patch.

> [Bob@domain.hid ~]$  diff L100718BootNoXeno.txt 
> L100718BootXenoPatchedButDisabled.txt
> 20c20
> < 1885804 bytes read
> ---
> > 1911632 bytes read
> 24c24
> <    Data Size:    1885740 Bytes =  1.8 MB
> ---
> >    Data Size:    1911568 Bytes =  1.8 MB
> 34,35c34,35
> < ....................... done, booting the kernel.
> < Linux version 2.6.31-omap1 (Bob@domain.hid) (gcc version 4.3.3 
> (GCC) ) #1 Sun Jul 18 00:08:49 PDT 2010
> ---
> > ......................... done, booting the kernel.
> > Linux version 2.6.31-omap1 (Bob@domain.hid) (gcc version 4.3.3 
> (GCC) ) #2 Sun Jul 18 18:16:32 PDT 2010
> 48c48
> < Memory: 255872KB available (3264K code, 291K data, 132K init, 0K 
> highmem)
> ---
> > Memory: 255744KB available (3320K code, 332K data, 132K init, 0K 
> highmem)
> 56c56,57
> < OMAP clockevent source: GPTIMER12 at 32768 Hz
> ---
> > OMAP clockevent source: GPTIMER1 at 13000000 Hz
> > I-pipe 1.16-01: pipeline enabled.
> 58c59
> < Calibrating delay loop... 477.86 BogoMIPS (lpj=1863680)
> ---
> > Calibrating delay loop... 498.07 BogoMIPS (lpj=2490368)
> 96c97
> < msgmni has been set to 500
> ---
> > msgmni has been set to 499
> 132,133c133,134
> < usb0: MAC 22:8d:c8:09:48:2e
> < usb0: HOST MAC 36:3d:ab:d8:fa:11
> ---
> > usb0: MAC c2:de:6e:33:e8:94
> > usb0: HOST MAC de:88:51:65:85:d5
> 147,148d147
> < twl4030_rtc twl4030_rtc: Power up reset detected.
> < twl4030_rtc twl4030_rtc: Enabling TWL4030-RTC.
> 161c160
> < twl4030_rtc twl4030_rtc: setting system clock to 2000-01-01 00:00:00 
> UTC (946684800)
> ---
> > twl4030_rtc twl4030_rtc: setting system clock to 2000-01-01 00:05:44 
> UTC (946685144)
The is where the console output of the Adeos patched kernel stops.
> 163,203d161
> < mmc0: new high speed SDHC card at address 1234
> < mmcblk0: mmc0:1234 SA04G 3.68 GiB
> <  mmcblk0: p1 p2
> < kjournald starting.  Commit interval 5 seconds
> < EXT3 FS on mmcblk0p2, internal journal
> < EXT3-fs: recovery complete.
> < EXT3-fs: mounted filesystem with writeback data mode.
> < VFS: Mounted root (ext3 filesystem) on device 179:2.
> < Freeing init memory: 132K
> < INIT: version 2.86 booting
> < Please wait: booting...
> < Starting udev
> < Remounting root file system...
> < Caching udev devnodes
> < Populating dev cache
> < root: mount: mounting rootfs on / failed: No such file or directory
> < Configuring network interfaces... ifconfig: SIOCGIFFLAGS: No such device
> < done.
> < Setting up IP spoofing protection: rp_filter.
> < Tue May 18 20:58:00 UTC 2010
> < Starting to configure packages...
> < Nothing to be done
> < Finished to configure packages.
> < INIT: Entering runlevel: 5
> < Starting Dropbear SSH server: dropbear.
> < Starting syslogd/klogd: done
> <
> < .-------.
> < |       |                  .-.
> < |   |   |-----.-----.-----.| |   .----..-----.-----.
> < |       |     | __  |  ---'| '--.|  .-'|     |     |
> < |   |   |  |  |     |---  ||  --'|  |  |  '  | | | |
> < '---'---'--'--'--.  |-----''----''--'  '-----'-'-'-'
> <                 -'  |
> <                 '---'
> <
> < The Angstrom Distribution beagleboard ttyS2
> <
> < Angstrom 2010.4-test-20100518 beagleboard ttyS2
> <
> < beagleboard login:
> [Bob@domain.hid ~]$ 
Although the above console log states "Angstrom", most of the 
distribution specific patches have been removed. Only the USB driver and 
MADC patches remain. These show no conflicts with Adeos patches.

I suspect that the change in the event source timer rate is confusing 
the waiting for the root file system to mount.

Does anyone know a way to fix this?

Regards,
Bob Feretich

Re: [Xenomai-help] Adeos patched kernel hangs mounting root file system

[Gilles Chanteperdrix]

Bob Feretich wrote:
> I suspect that the change in the event source timer rate is confusing 
> the waiting for the root file system to mount.
> 
> Does anyone know a way to fix this?

The Adeos patch simply forces Kconfig to disable the 32kHz clock,
because with a 32kHz clock source, we would only get a 30us granularity
for timer and clock services, which we find unacceptable. But the option
exists for a vanilla kernel as well.

You should try and disable the 32kHz clock on a vanilla kernel, if you
get the same issue, you should report it to the proper mailing list. If
you do net get it, then you have another issue, such as a edge/level
interrupts issue, and should give us more details such as the contents
of /proc/interrupts.

I also happen to run an OMAP3 based system, and I can mount and write to
an SD card with Xenomai without any problem (it is a 2.6.33 kernel,
tested with I-pipe version 1.16-01 and 1.17-01).

-- 
					    Gilles.

Re: [Xenomai-help] Adeos patched kernel hangs mounting root file system

[Bob Feretich]

  Thank you for the quick reply.

I rebuilt the non-Adeos patched kernel with the 32 KHz clocked disabled. 
It booted correctly, so that wasn't the problem.  I didn't see any other 
significant differences in the console boot logs.

The console log for the non-Adeos patched kernel with the 32 KHz clocked 
disabled is pasted below. The /proc/interrupts contents is displayed at 
the end.

I used the 1.16-01 patch.

> Reading boot sector
> Loading u-boot.bin from mmc
>
>
> U-Boot 2009.06-rc2 (Nov 02 2009 - 23:57:20)
>
> OMAP3530-GP ES3.0, CPU-OPP2 L3-165MHz
> OMAP3 Beagle board + LPDDR/NAND
> DRAM:  256 MB
> NAND:  256 MiB
> In:    serial
> Out:   serial
> Err:   serial
> Board revision C
> Die ID #317000030000000004013f8a1701a01b
> Hit any key to stop autoboot:  0
> mmc1 is available
> reading uImage
>
> 1867604 bytes read
> ## Booting kernel from Legacy Image at 80300000 ...
>    Image Name:   Angstrom/2.6.31/beagleboard
>    Image Type:   ARM Linux Kernel Image (uncompressed)
>    Data Size:    1867540 Bytes =  1.8 MB
>    Load Address: 80008000
>    Entry Point:  80008000
>    Verifying Checksum ... OK
>    Loading Kernel Image ... OK
> OK
>
> Starting kernel ...
>
> Uncompressing 
> Linux.........................................................................................
> ............................. done, booting the kernel.
> Linux version 2.6.31-omap1 (Bob@domain.hid) (gcc version 4.3.3 (GCC) 
> ) #2 Sun Jul 18 22:38:24 PDT 2010
> CPU: ARMv7 Processor [411fc083] revision 3 (ARMv7), cr=10c53c7f
> CPU: VIPT nonaliasing data cache, VIPT nonaliasing instruction cache
> Machine: OMAP3 Beagle Board
> Memory policy: ECC disabled, Data cache writeback
> OMAP3430 ES3.0
> SRAM: Mapped pa 0x40200000 to va 0xe3000000 size: 0x100000
> Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 65024
> Kernel command line: console=ttyS2,115200n8 root=/dev/mmcblk0p2 rw 
> rootfstype=ext3 rootwait
> PID hash table entries: 1024 (order: 10, 4096 bytes)
> Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
> Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
> Memory: 128MB 128MB = 256MB total
> Memory: 255872KB available (3232K code, 290K data, 132K init, 0K highmem)
> NR_IRQS:402
> Clocking rate (Crystal/Core/MPU): 26.0/332/500 MHz
> Reprogramming SDRC clock to 332000000 Hz
> GPMC revision 5.0
> IRQ: Found an INTC at 0xd8200000 (revision 4.0) with 96 interrupts
> Total of 96 interrupts on 1 active controller
> OMAP34xx GPIO hardware version 2.5
> OMAP clockevent source: GPTIMER1 at 13000000 Hz
> Console: colour dummy device 80x30
> Calibrating delay loop... 498.07 BogoMIPS (lpj=2490368)
> Mount-cache hash table entries: 512
> CPU: Testing write buffer coherency: ok
> regulator: core version 0.5
> NET: Registered protocol family 16
> Found NAND on CS0
> Registering NAND on CS0
> OMAP DMA hardware revision 4.0
> bio: create slab <bio-0> at 0
> i2c_omap i2c_omap.1: bus 1 rev3.12 at 2600 kHz
> twl4030: PIH (irq 7) chaining IRQs 368..375
> twl4030: power (irq 373) chaining IRQs 376..383
> twl4030: gpio (irq 368) chaining IRQs 384..401
> regulator: VMMC1: 1850 <--> 3150 mV normal standby
> regulator: VDAC: 1800 mV normal standby
> regulator: VUSB1V5: 1500 mV normal standby
> regulator: VUSB1V8: 1800 mV normal standby
> regulator: VUSB3V1: 3100 mV normal standby
> regulator: VPLL2: 1800 mV normal standby
> regulator: VSIM: 1800 <--> 3000 mV normal standby
> i2c_omap i2c_omap.3: bus 3 rev3.12 at 100 kHz
> SCSI subsystem initialized
> twl4030_usb twl4030_usb: Initialized TWL4030 USB module
> usbcore: registered new interface driver usbfs
> usbcore: registered new interface driver hub
> usbcore: registered new device driver usb
> musb_hdrc: version 6.0, musb-dma, otg (peripheral+host), debug=0
> musb_hdrc: USB OTG mode controller at d80ab000 using DMA, IRQ 92
> NET: Registered protocol family 2
> IP route cache hash table entries: 2048 (order: 1, 8192 bytes)
> TCP established hash table entries: 8192 (order: 4, 65536 bytes)
> TCP bind hash table entries: 8192 (order: 3, 32768 bytes)
> TCP: Hash tables configured (established 8192 bind 8192)
> TCP reno registered
> NET: Registered protocol family 1
> VFS: Disk quotas dquot_6.5.2
> Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
> JFFS2 version 2.2. (NAND) �© 2001-2006 Red Hat, Inc.
> msgmni has been set to 500
> alg: No test for stdrng (krng)
> Block layer SCSI generic (bsg) driver version 0.4 loaded (major 254)
> io scheduler noop registered
> io scheduler anticipatory registered (default)
> io scheduler deadline registered
> io scheduler cfq registered
> Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
> serial8250.0: ttyS0 at MMIO 0x4806a000 (irq = 72) is a ST16654
> serial8250.1: ttyS1 at MMIO 0x4806c000 (irq = 73) is a ST16654
> serial8250.2: ttyS2 at MMIO 0x49020000 (irq = 74) is a ST16654
> console [ttyS2] enabled
> brd: module loaded
> loop: module loaded
> i2c /dev entries driver
> usbcore: registered new interface driver asix
> usbcore: registered new interface driver cdc_ether
> usbcore: registered new interface driver net1080
> usbcore: registered new interface driver cdc_subset
> usbcore: registered new interface driver zaurus
> usbmon: debugfs is not available
> ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
> ehci-omap ehci-omap.0: OMAP-EHCI Host Controller
> ehci-omap ehci-omap.0: new USB bus registered, assigned bus number 1
> ehci-omap ehci-omap.0: irq 77, io mem 0x48064800
> ehci-omap ehci-omap.0: USB 2.0 started, EHCI 1.00
> usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
> usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
> usb usb1: Product: OMAP-EHCI Host Controller
> usb usb1: Manufacturer: Linux 2.6.31-omap1 ehci_hcd
> usb usb1: SerialNumber: ehci-omap.0
> usb usb1: configuration #1 chosen from 1 choice
> hub 1-0:1.0: USB hub found
> hub 1-0:1.0: 3 ports detected
> g_ether gadget: using random self ethernet address
> g_ether gadget: using random host ethernet address
> usb0: MAC 8a:fe:ec:d2:7c:3d
> usb0: HOST MAC 9a:ca:2d:10:da:55
> g_ether gadget: Ethernet Gadget, version: Memorial Day 2008
> g_ether gadget: g_ether ready
> musb_hdrc musb_hdrc: MUSB HDRC host driver
> musb_hdrc musb_hdrc: new USB bus registered, assigned bus number 2
> usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
> usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
> usb usb2: Product: MUSB HDRC host driver
> usb usb2: Manufacturer: Linux 2.6.31-omap1 musb-hcd
> usb usb2: SerialNumber: musb_hdrc
> usb usb2: configuration #1 chosen from 1 choice
> hub 2-0:1.0: USB hub found
> hub 2-0:1.0: 1 port detected
> mmci-omap-hs mmci-omap-hs.0: Failed to get debounce clock
> TCP cubic registered
> NET: Registered protocol family 17
> NET: Registered protocol family 15
> RPC: Registered udp transport module.
> RPC: Registered tcp transport module.
> Power Management for TI OMAP3.
> VFP support v0.3: implementor 41 architecture 3 part 30 variant c rev 1
> regulator_init_complete: incomplete constraints, leaving VDVI on
> regulator_init_complete: incomplete constraints, leaving VDAC on
> Waiting for root device /dev/mmcblk0p2...
> mmc0: new high speed SDHC card at address 1234
> mmcblk0: mmc0:1234 SA04G 3.68 GiB
>  mmcblk0: p1 p2
> kjournald starting.  Commit interval 5 seconds
> EXT3 FS on mmcblk0p2, internal journal
> EXT3-fs: mounted filesystem with writeback data mode.
> VFS: Mounted root (ext3 filesystem) on device 179:2.
> Freeing init memory: 132K
> INIT: version 2.86 booting
> Please wait: booting...
> Starting udev
> Remounting root file system...
> Caching udev devnodes
> Populating dev cache
> root: mount: mounting rootfs on / failed: No such file or directory
> Configuring network interfaces... ifconfig: SIOCGIFFLAGS: No such device
> done.
> Setting up IP spoofing protection: rp_filter.
> hwclock: can't open '/dev/misc/rtc': No such file or directory
> Tue May 18 20:58:00 UTC 2010
> hwclock: can't open '/dev/misc/rtc': No such file or directory
> Configuring update-modules.
> Starting to configure packages...
> Nothing to be done
> Finished to configure packages.
> INIT: Entering runlevel: 5
> Creating Dropbear SSH server RSA host key.
> Will output 1024 bit rsa secret key to 
> '/etc/dropbear/dropbear_rsa_host_key'
> Generating key, this may take a while...
> Public key portion is:
> ssh-rsa 
> AAAAB3NzaC1yc2EAAAADAQABAAAAgwDJb1gWi2/u83v7e+S9Ij31aK/QMD72J47fdtDm4jn37GTq6JpL7UxsmcTGRB30bmKFzMhP
> w0uCsbTAeU29KOG6BdlSYK1oI5bDl7jdYHeBvhoejrDCvdp3R9//3rVs0y+c7WYgDRid5aOxSSUAg2j+Ec6PuGniLBNYWOG7mJmru79P 
> roo
> t@domain.hid
> Fingerprint: md5 c6:e9:c0:07:33:e3:5c:61:35:a5:e0:24:e0:41:03:86
> Starting Dropbear SSH server: dropbear.
> Starting syslogd/klogd: done
>
> .-------.
> |       |                  .-.
> |   |   |-----.-----.-----.| |   .----..-----.-----.
> |       |     | __  |  ---'| '--.|  .-'|     |     |
> |   |   |  |  |     |---  ||  --'|  |  |  '  | | | |
> '---'---'--'--'--.  |-----''----''--'  '-----'-'-'-'
>                 -'  |
>                 '---'
>
> The Angstrom Distribution beagleboard ttyS2
>
> Angstrom 2010.4-test-20100518 beagleboard ttyS2
>
> beagleboard login: root
> root@domain.hid:~# cat /proc/interrupts
>            CPU0
>   7:          2        INTC  TWL4030-PIH
>  11:          0        INTC  prcm
>  12:       1078        INTC  DMA
>  37:       1009        INTC  gp timer
>  56:        273        INTC  i2c_omap
>  61:          0        INTC  i2c_omap
>  72:          1        INTC  serial idle
>  73:          1        INTC  serial idle
>  74:        158        INTC  serial idle, serial
>  77:          0        INTC  ehci_hcd:usb1
>  83:       1346        INTC  mmc0
>  92:          1        INTC  musb_hdrc
>  93:          0        INTC  musb_hdrc
> 378:          2     twl4030  twl4030_usb
> 384:          0     twl4030  mmc0
> Err:          0
> root@domain.hid:~# 
Regards,
Bob Feretich

On 7/18/2010 9:19 PM, Gilles Chanteperdrix wrote:
> Bob Feretich wrote:
>> I suspect that the change in the event source timer rate is confusing
>> the waiting for the root file system to mount.
>>
>> Does anyone know a way to fix this?
> The Adeos patch simply forces Kconfig to disable the 32kHz clock,
> because with a 32kHz clock source, we would only get a 30us granularity
> for timer and clock services, which we find unacceptable. But the option
> exists for a vanilla kernel as well.
>
> You should try and disable the 32kHz clock on a vanilla kernel, if you
> get the same issue, you should report it to the proper mailing list. If
> you do net get it, then you have another issue, such as a edge/level
> interrupts issue, and should give us more details such as the contents
> of /proc/interrupts.
>
> I also happen to run an OMAP3 based system, and I can mount and write to
> an SD card with Xenomai without any problem (it is a 2.6.33 kernel,
> tested with I-pipe version 1.16-01 and 1.17-01).
>

Re: [Xenomai-help] Adeos patched kernel hangs mounting root file system

[Gilles Chanteperdrix]

Bob Feretich wrote:
>   Thank you for the quick reply.
> 
> I rebuilt the non-Adeos patched kernel with the 32 KHz clocked disabled. 
> It booted correctly, so that wasn't the problem.  I didn't see any other 
> significant differences in the console boot logs.
> 
> The console log for the non-Adeos patched kernel with the 32 KHz clocked 
> disabled is pasted below. The /proc/interrupts contents is displayed at 
> the end.
> 
> I used the 1.16-01 patch.
> 
>> Reading boot sector
>> Loading u-boot.bin from mmc
>>
>>
>> U-Boot 2009.06-rc2 (Nov 02 2009 - 23:57:20)
>>
>> OMAP3530-GP ES3.0, CPU-OPP2 L3-165MHz
>> OMAP3 Beagle board + LPDDR/NAND
>> DRAM:  256 MB
>> NAND:  256 MiB
>> In:    serial
>> Out:   serial
>> Err:   serial
>> Board revision C
>> Die ID #317000030000000004013f8a1701a01b
>> Hit any key to stop autoboot:  0
>> mmc1 is available
>> reading uImage
>>
>> 1867604 bytes read
>> ## Booting kernel from Legacy Image at 80300000 ...
>>    Image Name:   Angstrom/2.6.31/beagleboard
>>    Image Type:   ARM Linux Kernel Image (uncompressed)
>>    Data Size:    1867540 Bytes =  1.8 MB
>>    Load Address: 80008000
>>    Entry Point:  80008000
>>    Verifying Checksum ... OK
>>    Loading Kernel Image ... OK
>> OK
>>
>> Starting kernel ...
>>
>> Uncompressing 
>> Linux.........................................................................................
>> ............................. done, booting the kernel.
>> Linux version 2.6.31-omap1 (Bob@domain.hid) (gcc version 4.3.3 (GCC) 
>> ) #2 Sun Jul 18 22:38:24 PDT 2010
>> CPU: ARMv7 Processor [411fc083] revision 3 (ARMv7), cr=10c53c7f
>> CPU: VIPT nonaliasing data cache, VIPT nonaliasing instruction cache
>> Machine: OMAP3 Beagle Board
>> Memory policy: ECC disabled, Data cache writeback
>> OMAP3430 ES3.0
>> SRAM: Mapped pa 0x40200000 to va 0xe3000000 size: 0x100000
>> Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 65024
>> Kernel command line: console=ttyS2,115200n8 root=/dev/mmcblk0p2 rw 
>> rootfstype=ext3 rootwait
>> PID hash table entries: 1024 (order: 10, 4096 bytes)
>> Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
>> Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
>> Memory: 128MB 128MB = 256MB total
>> Memory: 255872KB available (3232K code, 290K data, 132K init, 0K highmem)
>> NR_IRQS:402
>> Clocking rate (Crystal/Core/MPU): 26.0/332/500 MHz
>> Reprogramming SDRC clock to 332000000 Hz
>> GPMC revision 5.0
>> IRQ: Found an INTC at 0xd8200000 (revision 4.0) with 96 interrupts
>> Total of 96 interrupts on 1 active controller
>> OMAP34xx GPIO hardware version 2.5
>> OMAP clockevent source: GPTIMER1 at 13000000 Hz
>> Console: colour dummy device 80x30
>> Calibrating delay loop... 498.07 BogoMIPS (lpj=2490368)
>> Mount-cache hash table entries: 512
>> CPU: Testing write buffer coherency: ok
>> regulator: core version 0.5
>> NET: Registered protocol family 16
>> Found NAND on CS0
>> Registering NAND on CS0
>> OMAP DMA hardware revision 4.0
>> bio: create slab <bio-0> at 0
>> i2c_omap i2c_omap.1: bus 1 rev3.12 at 2600 kHz
>> twl4030: PIH (irq 7) chaining IRQs 368..375
>> twl4030: power (irq 373) chaining IRQs 376..383
>> twl4030: gpio (irq 368) chaining IRQs 384..401
>> regulator: VMMC1: 1850 <--> 3150 mV normal standby
>> regulator: VDAC: 1800 mV normal standby
>> regulator: VUSB1V5: 1500 mV normal standby
>> regulator: VUSB1V8: 1800 mV normal standby
>> regulator: VUSB3V1: 3100 mV normal standby
>> regulator: VPLL2: 1800 mV normal standby
>> regulator: VSIM: 1800 <--> 3000 mV normal standby
>> i2c_omap i2c_omap.3: bus 3 rev3.12 at 100 kHz
>> SCSI subsystem initialized
>> twl4030_usb twl4030_usb: Initialized TWL4030 USB module
>> usbcore: registered new interface driver usbfs
>> usbcore: registered new interface driver hub
>> usbcore: registered new device driver usb
>> musb_hdrc: version 6.0, musb-dma, otg (peripheral+host), debug=0
>> musb_hdrc: USB OTG mode controller at d80ab000 using DMA, IRQ 92
>> NET: Registered protocol family 2
>> IP route cache hash table entries: 2048 (order: 1, 8192 bytes)
>> TCP established hash table entries: 8192 (order: 4, 65536 bytes)
>> TCP bind hash table entries: 8192 (order: 3, 32768 bytes)
>> TCP: Hash tables configured (established 8192 bind 8192)
>> TCP reno registered
>> NET: Registered protocol family 1
>> VFS: Disk quotas dquot_6.5.2
>> Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
>> JFFS2 version 2.2. (NAND) �© 2001-2006 Red Hat, Inc.
>> msgmni has been set to 500
>> alg: No test for stdrng (krng)
>> Block layer SCSI generic (bsg) driver version 0.4 loaded (major 254)
>> io scheduler noop registered
>> io scheduler anticipatory registered (default)
>> io scheduler deadline registered
>> io scheduler cfq registered
>> Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
>> serial8250.0: ttyS0 at MMIO 0x4806a000 (irq = 72) is a ST16654
>> serial8250.1: ttyS1 at MMIO 0x4806c000 (irq = 73) is a ST16654
>> serial8250.2: ttyS2 at MMIO 0x49020000 (irq = 74) is a ST16654
>> console [ttyS2] enabled
>> brd: module loaded
>> loop: module loaded
>> i2c /dev entries driver
>> usbcore: registered new interface driver asix
>> usbcore: registered new interface driver cdc_ether
>> usbcore: registered new interface driver net1080
>> usbcore: registered new interface driver cdc_subset
>> usbcore: registered new interface driver zaurus
>> usbmon: debugfs is not available
>> ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
>> ehci-omap ehci-omap.0: OMAP-EHCI Host Controller
>> ehci-omap ehci-omap.0: new USB bus registered, assigned bus number 1
>> ehci-omap ehci-omap.0: irq 77, io mem 0x48064800
>> ehci-omap ehci-omap.0: USB 2.0 started, EHCI 1.00
>> usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
>> usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
>> usb usb1: Product: OMAP-EHCI Host Controller
>> usb usb1: Manufacturer: Linux 2.6.31-omap1 ehci_hcd
>> usb usb1: SerialNumber: ehci-omap.0
>> usb usb1: configuration #1 chosen from 1 choice
>> hub 1-0:1.0: USB hub found
>> hub 1-0:1.0: 3 ports detected
>> g_ether gadget: using random self ethernet address
>> g_ether gadget: using random host ethernet address
>> usb0: MAC 8a:fe:ec:d2:7c:3d
>> usb0: HOST MAC 9a:ca:2d:10:da:55
>> g_ether gadget: Ethernet Gadget, version: Memorial Day 2008
>> g_ether gadget: g_ether ready
>> musb_hdrc musb_hdrc: MUSB HDRC host driver
>> musb_hdrc musb_hdrc: new USB bus registered, assigned bus number 2
>> usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
>> usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
>> usb usb2: Product: MUSB HDRC host driver
>> usb usb2: Manufacturer: Linux 2.6.31-omap1 musb-hcd
>> usb usb2: SerialNumber: musb_hdrc
>> usb usb2: configuration #1 chosen from 1 choice
>> hub 2-0:1.0: USB hub found
>> hub 2-0:1.0: 1 port detected
>> mmci-omap-hs mmci-omap-hs.0: Failed to get debounce clock
>> TCP cubic registered
>> NET: Registered protocol family 17
>> NET: Registered protocol family 15
>> RPC: Registered udp transport module.
>> RPC: Registered tcp transport module.
>> Power Management for TI OMAP3.
>> VFP support v0.3: implementor 41 architecture 3 part 30 variant c rev 1
>> regulator_init_complete: incomplete constraints, leaving VDVI on
>> regulator_init_complete: incomplete constraints, leaving VDAC on
>> Waiting for root device /dev/mmcblk0p2...
>> mmc0: new high speed SDHC card at address 1234
>> mmcblk0: mmc0:1234 SA04G 3.68 GiB
>>  mmcblk0: p1 p2
>> kjournald starting.  Commit interval 5 seconds
>> EXT3 FS on mmcblk0p2, internal journal
>> EXT3-fs: mounted filesystem with writeback data mode.
>> VFS: Mounted root (ext3 filesystem) on device 179:2.
>> Freeing init memory: 132K
>> INIT: version 2.86 booting
>> Please wait: booting...
>> Starting udev
>> Remounting root file system...
>> Caching udev devnodes
>> Populating dev cache
>> root: mount: mounting rootfs on / failed: No such file or directory
>> Configuring network interfaces... ifconfig: SIOCGIFFLAGS: No such device
>> done.
>> Setting up IP spoofing protection: rp_filter.
>> hwclock: can't open '/dev/misc/rtc': No such file or directory
>> Tue May 18 20:58:00 UTC 2010
>> hwclock: can't open '/dev/misc/rtc': No such file or directory
>> Configuring update-modules.
>> Starting to configure packages...
>> Nothing to be done
>> Finished to configure packages.
>> INIT: Entering runlevel: 5
>> Creating Dropbear SSH server RSA host key.
>> Will output 1024 bit rsa secret key to 
>> '/etc/dropbear/dropbear_rsa_host_key'
>> Generating key, this may take a while...
>> Public key portion is:
>> ssh-rsa 
>> AAAAB3NzaC1yc2EAAAADAQABAAAAgwDJb1gWi2/u83v7e+S9Ij31aK/QMD72J47fdtDm4jn37GTq6JpL7UxsmcTGRB30bmKFzMhP
>> w0uCsbTAeU29KOG6BdlSYK1oI5bDl7jdYHeBvhoejrDCvdp3R9//3rVs0y+c7WYgDRid5aOxSSUAg2j+Ec6PuGniLBNYWOG7mJmru79P 
>> roo
>> t@domain.hid
>> Fingerprint: md5 c6:e9:c0:07:33:e3:5c:61:35:a5:e0:24:e0:41:03:86
>> Starting Dropbear SSH server: dropbear.
>> Starting syslogd/klogd: done
>>
>> .-------.
>> |       |                  .-.
>> |   |   |-----.-----.-----.| |   .----..-----.-----.
>> |       |     | __  |  ---'| '--.|  .-'|     |     |
>> |   |   |  |  |     |---  ||  --'|  |  |  '  | | | |
>> '---'---'--'--'--.  |-----''----''--'  '-----'-'-'-'
>>                 -'  |
>>                 '---'
>>
>> The Angstrom Distribution beagleboard ttyS2
>>
>> Angstrom 2010.4-test-20100518 beagleboard ttyS2
>>
>> beagleboard login: root
>> root@domain.hid:~# cat /proc/interrupts
>>            CPU0
>>   7:          2        INTC  TWL4030-PIH
>>  11:          0        INTC  prcm
>>  12:       1078        INTC  DMA
>>  37:       1009        INTC  gp timer
>>  56:        273        INTC  i2c_omap
>>  61:          0        INTC  i2c_omap
>>  72:          1        INTC  serial idle
>>  73:          1        INTC  serial idle
>>  74:        158        INTC  serial idle, serial
>>  77:          0        INTC  ehci_hcd:usb1
>>  83:       1346        INTC  mmc0
>>  92:          1        INTC  musb_hdrc
>>  93:          0        INTC  musb_hdrc
>> 378:          2     twl4030  twl4030_usb
>> 384:          0     twl4030  mmc0
>> Err:          0
>> root@domain.hid

Ok. Several questions: what is this MADC patch you were talking about?
If this is a kernel patch, if yes, could you try and remove it?

You have an error message about mmc:
mmci-omap-hs mmci-omap-hs.0: Failed to get debounce clock

which I do not have. Could this not explain some issues?

You are using the 2.6.31 kernel which does not work for you, whereas
2.6.33 works for me. Could you test 2.6.33?

-- 
					    Gilles.

Re: [Xenomai-help] Adeos patched kernel hangs mounting root file system

[Bob Feretich]

[-- Attachment #1: Type: text/plain, Size: 10548 bytes --]

  The debounce clock is not the source of the problem.
On the 2430 chip, the debounce clock is under software control. For the 
OMAP3 chips, its been placed under hardware control. So the 2.6.31 
kernel classifies the  this message as a warning...

1053         host->dbclk = clk_get(&pdev->dev, "mmchsdb_fck");
1054         /*
1055          * MMC can still work without debounce clock.
1056          */
1057         if (IS_ERR(host->dbclk))
1058                 dev_warn(mmc_dev(host->mmc), "Failed to get 
debounce clock\n");
1059         else

In the 2.6.33 kernel the message has been made 2430 specific...

1709         if (cpu_is_omap2430()) {
1710                 host->dbclk = clk_get(&pdev->dev, "mmchsdb_fck");
1711                 /*
1712                  * MMC can still work without debounce clock.
1713                  */
1714                 if (IS_ERR(host->dbclk))
1715                         dev_warn(mmc_dev(host->mmc),
1716                                 "Failed to get debounce clock\n");
1717                 else
... snipped ...                                       " clk failed\n");
1724         }

I removed all of the patches  and rebuilt without the Adeos patch. I 
lost host USB Host Port capability, but the BeagleBoard booted.

I then applied the Adeos patch, but disabled Xenomai. The result is the 
same. The board hangs waiting for /dev/mmcblk0p2.

Reading boot sector
Loading u-boot.bin from mmc


U-Boot 2009.06-rc2 (Nov 02 2009 - 23:57:20)

OMAP3530-GP ES3.0, CPU-OPP2 L3-165MHz
OMAP3 Beagle board + LPDDR/NAND
DRAM:  256 MB
NAND:  256 MiB
In:    serial
Out:   serial
Err:   serial
Board revision C
Die ID #317000030000000004013f8a1701a01b
Hit any key to stop autoboot:  0
mmc1 is available
reading uImage

1882552 bytes read
## Booting kernel from Legacy Image at 80300000 ...
    Image Name:   Angstrom/2.6.31/beagleboard
    Image Type:   ARM Linux Kernel Image (uncompressed)
    Data Size:    1882488 Bytes =  1.8 MB
    Load Address: 80008000
    Entry Point:  80008000
    Verifying Checksum ... OK
    Loading Kernel Image ... OK
OK

Starting kernel ...

Uncompressing 
Linux.........................................................................................
.............................. done, booting the kernel.
Linux version 2.6.31-omap1 (Bob@domain.hid) (gcc version 4.3.3 (GCC) ) 
#3 Mon Jul 19 14:55:27 PDT 2010
CPU: ARMv7 Processor [411fc083] revision 3 (ARMv7), cr=10c53c7f
CPU: VIPT nonaliasing data cache, VIPT nonaliasing instruction cache
Machine: OMAP3 Beagle Board
Memory policy: ECC disabled, Data cache writeback
OMAP3430 ES3.0
SRAM: Mapped pa 0x40200000 to va 0xe3000000 size: 0x100000
Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 65024
Kernel command line: console=ttyS2,115200n8 root=/dev/mmcblk0p2 rw 
rootfstype=ext3 rootwait
PID hash table entries: 1024 (order: 10, 4096 bytes)
Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
Memory: 128MB 128MB = 256MB total
Memory: 255872KB available (3268K code, 331K data, 132K init, 0K highmem)
NR_IRQS:402
Clocking rate (Crystal/Core/MPU): 26.0/332/500 MHz
Reprogramming SDRC clock to 332000000 Hz
GPMC revision 5.0
IRQ: Found an INTC at 0xd8200000 (revision 4.0) with 96 interrupts
Total of 96 interrupts on 1 active controller
OMAP34xx GPIO hardware version 2.5
OMAP clockevent source: GPTIMER1 at 13000000 Hz
I-pipe 1.16-01: pipeline enabled.
Console: colour dummy device 80x30
Calibrating delay loop... 498.07 BogoMIPS (lpj=2490368)
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
regulator: core version 0.5
NET: Registered protocol family 16
Found NAND on CS0
Registering NAND on CS0
OMAP DMA hardware revision 4.0
bio: create slab <bio-0> at 0
i2c_omap i2c_omap.1: bus 1 rev3.12 at 2600 kHz
twl4030: PIH (irq 7) chaining IRQs 368..375
twl4030: power (irq 373) chaining IRQs 376..383
twl4030: gpio (irq 368) chaining IRQs 384..401
regulator: VMMC1: 1850 <--> 3150 mV normal standby
regulator: VDAC: 1800 mV normal standby
regulator: VUSB1V5: 1500 mV normal standby
regulator: VUSB1V8: 1800 mV normal standby
regulator: VUSB3V1: 3100 mV normal standby
regulator: VPLL2: 1800 mV normal standby
regulator: VSIM: 1800 <--> 3000 mV normal standby
i2c_omap i2c_omap.3: bus 3 rev3.12 at 100 kHz
SCSI subsystem initialized
twl4030_usb twl4030_usb: Initialized TWL4030 USB module
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
musb_hdrc: version 6.0, musb-dma, otg (peripheral+host), debug=0
musb_hdrc: USB OTG mode controller at d80ab000 using DMA, IRQ 92
NET: Registered protocol family 2
IP route cache hash table entries: 2048 (order: 1, 8192 bytes)
TCP established hash table entries: 8192 (order: 4, 65536 bytes)
TCP bind hash table entries: 8192 (order: 3, 32768 bytes)
TCP: Hash tables configured (established 8192 bind 8192)
TCP reno registered
NET: Registered protocol family 1
VFS: Disk quotas dquot_6.5.2
Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
JFFS2 version 2.2. (NAND) �© 2001-2006 Red Hat, Inc.
msgmni has been set to 500
alg: No test for stdrng (krng)
Block layer SCSI generic (bsg) driver version 0.4 loaded (major 253)
io scheduler noop registered
io scheduler anticipatory registered (default)
io scheduler deadline registered
io scheduler cfq registered
Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
serial8250.0: ttyS0 at MMIO 0x4806a000 (irq = 72) is a ST16654
serial8250.1: ttyS1 at MMIO 0x4806c000 (irq = 73) is a ST16654
serial8250.2: ttyS2 at MMIO 0x49020000 (irq = 74) is a ST16654
console [ttyS2] enabled
brd: module loaded
loop: module loaded
i2c /dev entries driver
usbcore: registered new interface driver asix
usbcore: registered new interface driver cdc_ether
usbcore: registered new interface driver net1080
usbcore: registered new interface driver cdc_subset
usbcore: registered new interface driver zaurus
usbmon: debugfs is not available
g_ether gadget: using random self ethernet address
g_ether gadget: using random host ethernet address
usb0: MAC b2:59:96:51:13:fa
usb0: HOST MAC da:76:f6:16:2e:21
g_ether gadget: Ethernet Gadget, version: Memorial Day 2008
g_ether gadget: g_ether ready
musb_hdrc musb_hdrc: MUSB HDRC host driver
musb_hdrc musb_hdrc: new USB bus registered, assigned bus number 1
usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb1: Product: MUSB HDRC host driver
usb usb1: Manufacturer: Linux 2.6.31-omap1 musb-hcd
usb usb1: SerialNumber: musb_hdrc
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 1 port detected
mmci-omap-hs mmci-omap-hs.0: Failed to get debounce clock
TCP cubic registered
NET: Registered protocol family 17
NET: Registered protocol family 15
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
Power Management for TI OMAP3.
VFP support v0.3: implementor 41 architecture 3 part 30 variant c rev 1
regulator_init_complete: incomplete constraints, leaving VDVI on
regulator_init_complete: incomplete constraints, leaving VDAC on
drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
Waiting for root device /dev/mmcblk0p2...

The Angstrom developers are working at 2.6.32. The 2.6.31 kernel is the 
newest kernel that both Angstrom and Xenomai support. I know that not 
applying the patches that Angstrom provided 2.6.31 kernel, broke the 
ability of my BeagleBoard to use the EHCI USB host Port on the board.

I suspect that the problem is something specific to the way the 
BeagleBoard uses the OMAP3530 as an SD card controller. There are 
multiple ways to attach a SD card interface to a OMAP3 chip. There may 
be a difference between the board that you are using and the BeagleBoard.

The SD cards that I am using are Class 4 (4-bit wide) 2 to 4 GB cards. 
The BeagleBoard attaches the SD card interface to the MMC1 port. SD 
cards can also be attached via an SPI bus.
How does the SD card attache in your board?

The BeagleBoard SRM references a "Card Detect" interrupt.8.11.3 Card Detect
> When a card is inserted into the SD/MMC connector, the Card Detect pin 
> is grounded.
> This is detected on pin P12 of the TPS65950. An interrupt, if enabled, 
> is sent to the
> OMAP3530 via the interrupt pin. The SW can be written such that the 
> system comes out of sleep or a reduced frequency mode when the card is 
> detected.
There doesn't seem to be any other interrupt signal external to the OMAP 
chip.

I'll dig deeper and find out specifically which interrupts the 
BeagleBoard SD card affects.

Regards,
Bob Feretich

On 7/19/2010 1:31 AM, Gilles Chanteperdrix wrote:
> Bob Feretich wrote:
>>    Thank you for the quick reply.
>>
>> I rebuilt the non-Adeos patched kernel with the 32 KHz clocked disabled.
>> It booted correctly, so that wasn't the problem.  I didn't see any other
>> significant differences in the console boot logs.
>>
>> The console log for the non-Adeos patched kernel with the 32 KHz clocked
>> disabled is pasted below. The /proc/interrupts contents is displayed at
>> the end.
>>
>> I used the 1.16-01 patch.
>>
>>> Reading boot sector
>>> Loading u-boot.bin from mmc
>>>
>>>
>>> ... snipped ...
>>>
>>> beagleboard login: root
>>> root@domain.hid:~# cat /proc/interrupts
>>>             CPU0
>>>    7:          2        INTC  TWL4030-PIH
>>>   11:          0        INTC  prcm
>>>   12:       1078        INTC  DMA
>>>   37:       1009        INTC  gp timer
>>>   56:        273        INTC  i2c_omap
>>>   61:          0        INTC  i2c_omap
>>>   72:          1        INTC  serial idle
>>>   73:          1        INTC  serial idle
>>>   74:        158        INTC  serial idle, serial
>>>   77:          0        INTC  ehci_hcd:usb1
>>>   83:       1346        INTC  mmc0
>>>   92:          1        INTC  musb_hdrc
>>>   93:          0        INTC  musb_hdrc
>>> 378:          2     twl4030  twl4030_usb
>>> 384:          0     twl4030  mmc0
>>> Err:          0
>>> root@domain.hid:~#
> Ok. Several questions: what is this MADC patch you were talking about?
> If this is a kernel patch, if yes, could you try and remove it?
>
> You have an error message about mmc:
> mmci-omap-hs mmci-omap-hs.0: Failed to get debounce clock
>
> which I do not have. Could this not explain some issues?
>
> You are using the 2.6.31 kernel which does not work for you, whereas
> 2.6.33 works for me. Could you test 2.6.33?
>

[-- Attachment #2: Type: text/html, Size: 13811 bytes --]

Re: [Xenomai-help] Adeos patched kernel hangs mounting root file system

[Gilles Chanteperdrix]

Bob Feretich wrote:
>   The debounce clock is not the source of the problem.
> On the 2430 chip, the debounce clock is under software control. For the 
> OMAP3 chips, its been placed under hardware control. So the 2.6.31 
> kernel classifies the  this message as a warning...
> 
> 1053         host->dbclk = clk_get(&pdev->dev, "mmchsdb_fck");
> 1054         /*
> 1055          * MMC can still work without debounce clock.
> 1056          */
> 1057         if (IS_ERR(host->dbclk))
> 1058                 dev_warn(mmc_dev(host->mmc), "Failed to get 
> debounce clock\n");
> 1059         else
> 
> In the 2.6.33 kernel the message has been made 2430 specific...
> 
> 1709         if (cpu_is_omap2430()) {
> 1710                 host->dbclk = clk_get(&pdev->dev, "mmchsdb_fck");
> 1711                 /*
> 1712                  * MMC can still work without debounce clock.
> 1713                  */
> 1714                 if (IS_ERR(host->dbclk))
> 1715                         dev_warn(mmc_dev(host->mmc),
> 1716                                 "Failed to get debounce clock\n");
> 1717                 else
> ... snipped ...                                       " clk failed\n");
> 1724         }
> 
> I removed all of the patches  and rebuilt without the Adeos patch. I 
> lost host USB Host Port capability, but the BeagleBoard booted.
> 
> I then applied the Adeos patch, but disabled Xenomai. The result is the 
> same. The board hangs waiting for /dev/mmcblk0p2.

What about testing 2.6.33 ?

-- 
					    Gilles.

Re: [Xenomai-help] Adeos patched kernel hangs mounting root file system

[Bob Feretich]

[-- Attachment #1: Type: text/plain, Size: 2017 bytes --]

  On the BeagleBoard...

    * The SD card/MMC is attached to the OMAP3530 chip MMC1 hardware
      Port. (The chip has 3 SD/MMC ports, numbered 1, 2, and 3.) The
      BeagleBoard connects the MMC2 port to an expansion connector and
      its not used in my application. The BeagleBoard does not use MMC3
      (not connected to anything).
    * The MMC1 hardware port is the first mmc port and is referred to in
      the kernel mmc0.
    * The OMAP controller for this port interrupts on IRQ 83.
    * The OMAP controller also uses SDMA channels 60 and 61 which
      results in other IRQs from the DMA controller.
    * The Card Detect signal from the SD card/MMC interface is wired to
      a TPS65950 chip
    * This TPS65950 chip presents the Card Detect interrupt to the
      OMAP3530 via sys_nirq[0]. This signal is mapped to IRQ 7. The
      TPS65950 can funnel up to 18 interrupts into sys_nirq[0].
    * The Level 2 interrupt handler maps the Card Detect interrupt to
      IRQ 384.  IRQ 384 is the first IRQ of the TWL4030 GPIO IRQ space.
      Apparently the the TWL4030 interrupt mapping is used for the TPS65950.
    * My SD card has two partitions. The first is a FAT partition
      containing the u-boot and kernel boot image. The second is a ext3
      partition containing the root file system.

It's possible that the kernel is expecting a Card Detect interrupt to 
proceed with the mounting of the root file system. I noticed that the 
/proc/interrupts listing that I mailed you showed 2 interrupts each on 
IRQ 384 and on IRQ 7.
Does Xenomai support TWL4030 style Level 2 interrupts?
Could pending interrupts have gotten lost when when Adeos initializes?

Regards,
Bob Feretich

On 7/19/2010 5:15 PM, Bob Feretich wrote:
> The debounce clock is not the source of the problem.
> On the 2430 chip, the debounce clock is under software control. For 
> the OMAP3 chips, its been placed under hardware control. So the 2.6.31 
> kernel classifies the  this message as a warning...
... snipped ...


[-- Attachment #2: Type: text/html, Size: 2578 bytes --]

Re: [Xenomai-help] Adeos patched kernel hangs mounting root file system

[Gilles Chanteperdrix]

Bob Feretich wrote:
>   On the BeagleBoard...
> 
>     * The SD card/MMC is attached to the OMAP3530 chip MMC1 hardware
>       Port. (The chip has 3 SD/MMC ports, numbered 1, 2, and 3.) The
>       BeagleBoard connects the MMC2 port to an expansion connector and
>       its not used in my application. The BeagleBoard does not use MMC3
>       (not connected to anything).
>     * The MMC1 hardware port is the first mmc port and is referred to in
>       the kernel mmc0.
>     * The OMAP controller for this port interrupts on IRQ 83.
>     * The OMAP controller also uses SDMA channels 60 and 61 which
>       results in other IRQs from the DMA controller.
>     * The Card Detect signal from the SD card/MMC interface is wired to
>       a TPS65950 chip
>     * This TPS65950 chip presents the Card Detect interrupt to the
>       OMAP3530 via sys_nirq[0]. This signal is mapped to IRQ 7. The
>       TPS65950 can funnel up to 18 interrupts into sys_nirq[0].
>     * The Level 2 interrupt handler maps the Card Detect interrupt to
>       IRQ 384.  IRQ 384 is the first IRQ of the TWL4030 GPIO IRQ space.
>       Apparently the the TWL4030 interrupt mapping is used for the TPS65950.
>     * My SD card has two partitions. The first is a FAT partition
>       containing the u-boot and kernel boot image. The second is a ext3
>       partition containing the root file system.
> 
> It's possible that the kernel is expecting a Card Detect interrupt to 
> proceed with the mounting of the root file system. I noticed that the 
> /proc/interrupts listing that I mailed you showed 2 interrupts each on 
> IRQ 384 and on IRQ 7.
> Does Xenomai support TWL4030 style Level 2 interrupts?
> Could pending interrupts have gotten lost when when Adeos initializes?

Could you test 2.6.33 ?

-- 
					    Gilles.

Re: [Xenomai-help] Adeos patched kernel hangs mounting root file system

[Bob Feretich]

  Angstrom doesn't support 2.6.33 yet. The Angstrom developers are 
working at 2.6.32. The 2.6.31 kernel is the newest kernel that both 
Angstrom and Xenomai support.

That said, I could grab a 2.6.33 kernel and drop it in to see what 
happens. I build everything via OpenEmbedded. I would either need to 
create the OpenEmbedded receipes for the 2.6.33 kernel (which I don't 
know how to do right now); or set up a build environment for the kernel 
outside OpenEmbedded, then merge it back in (also haven't this done 
before).

Either would be a fair amount of work. I'd like to hear your response to 
my last e-mail detailing the specific IRQs involved and support for a 
Level 2 interrupt handler before I start.

Regards,
Bob

On 7/20/2010 12:11 AM, Gilles Chanteperdrix wrote:
> ... snipped ...
> What about testing 2.6.33 ?
>

Re: [Xenomai-help] Adeos patched kernel hangs mounting root file system

[Gilles Chanteperdrix]

Bob Feretich wrote:
>   Angstrom doesn't support 2.6.33 yet. The Angstrom developers are 
> working at 2.6.32. The 2.6.31 kernel is the newest kernel that both 
> Angstrom and Xenomai support.
> 
> That said, I could grab a 2.6.33 kernel and drop it in to see what 
> happens. I build everything via OpenEmbedded. I would either need to 
> create the OpenEmbedded receipes for the 2.6.33 kernel (which I don't 
> know how to do right now); or set up a build environment for the kernel 
> outside OpenEmbedded, then merge it back in (also haven't this done 
> before).
> 
> Either would be a fair amount of work. I'd like to hear your response to 
> my last e-mail detailing the specific IRQs involved and support for a 
> Level 2 interrupt handler before I start.

Building a kernel by using only its build system is pretty easy.
Building it for Xenomai involves one more step: running the
prepare-kernel.sh script, but that is not very complicated either.

The situation we have is:
2.6.31 does not work for you on Beagle
2.6.33 works for me on IGEPv2.

The fact that 2.6.33 works for me rules out automatically anything that
would be missing in the Adeos patch.

Now we have two possibilities, either the problem comes from a
difference between 2.6.31 and 2.6.33, or it comes from a difference
between Beagle and IGEP. And since I do not have time to test 2.6.31, I
ask you to test 2.6.33.

-- 
					    Gilles.

Re: [Xenomai-help] Adeos patched kernel hangs mounting root file system

[Gilles Chanteperdrix]

Gilles Chanteperdrix wrote:
> Bob Feretich wrote:
>>   Angstrom doesn't support 2.6.33 yet. The Angstrom developers are 
>> working at 2.6.32. The 2.6.31 kernel is the newest kernel that both 
>> Angstrom and Xenomai support.
>>
>> That said, I could grab a 2.6.33 kernel and drop it in to see what 
>> happens. I build everything via OpenEmbedded. I would either need to 
>> create the OpenEmbedded receipes for the 2.6.33 kernel (which I don't 
>> know how to do right now); or set up a build environment for the kernel 
>> outside OpenEmbedded, then merge it back in (also haven't this done 
>> before).
>>
>> Either would be a fair amount of work. I'd like to hear your response to 
>> my last e-mail detailing the specific IRQs involved and support for a 
>> Level 2 interrupt handler before I start.
> 
> Building a kernel by using only its build system is pretty easy.
> Building it for Xenomai involves one more step: running the
> prepare-kernel.sh script, but that is not very complicated either.
> 
> The situation we have is:
> 2.6.31 does not work for you on Beagle
> 2.6.33 works for me on IGEPv2.
> 
> The fact that 2.6.33 works for me rules out automatically anything that
> would be missing in the Adeos patch.
> 
> Now we have two possibilities, either the problem comes from a
> difference between 2.6.31 and 2.6.33, or it comes from a difference
> between Beagle and IGEP. And since I do not have time to test 2.6.31, I
> ask you to test 2.6.33.

The thing I did not explain is that 2.6.31 has no support for the IGEPV2
board. So, to get it working I would need to backport the board support.

However, I can compile a 2.6.33 kernel with a configuration for the
beagle board. To be sure that the configuration works for you, I would
need your .config though.

-- 
					    Gilles.

Re: [Xenomai-help] Adeos patched kernel hangs mounting root file system

[Bob Feretich]

  I have downloaded the 2.6.33 omap kernel and I 'm starting to work 
with it. I'll write again when I have a clean boot of the vanilla kernel 
and tried to boot again with the Adeos patch.

I think that I figured out how to tell OpenEmbedded to build it.

When you display /proc/interrupts on the IGEPv2, do you see interrupts 
occuring at IRQs greater or equal to IRQ 384?
Do you see the same number reflected in IRQ 7?

In order to exclude as much Angstrom stuff and my stuff as possible 
during this debug, I have reverted to the vanilla kernel's 
arch/arm/configs/omap3_beagle/defconfig file.

Regards,
Bob Feretich

On 7/20/2010 9:29 AM, Gilles Chanteperdrix wrote:
> Gilles Chanteperdrix wrote:
>> Bob Feretich wrote:
>>>    Angstrom doesn't support 2.6.33 yet. The Angstrom developers are
>>> working at 2.6.32. The 2.6.31 kernel is the newest kernel that both
>>> Angstrom and Xenomai support.
>>>
>>> That said, I could grab a 2.6.33 kernel and drop it in to see what
>>> happens. I build everything via OpenEmbedded. I would either need to
>>> create the OpenEmbedded receipes for the 2.6.33 kernel (which I don't
>>> know how to do right now); or set up a build environment for the kernel
>>> outside OpenEmbedded, then merge it back in (also haven't this done
>>> before).
>>>
>>> Either would be a fair amount of work. I'd like to hear your response to
>>> my last e-mail detailing the specific IRQs involved and support for a
>>> Level 2 interrupt handler before I start.
>> Building a kernel by using only its build system is pretty easy.
>> Building it for Xenomai involves one more step: running the
>> prepare-kernel.sh script, but that is not very complicated either.
>>
>> The situation we have is:
>> 2.6.31 does not work for you on Beagle
>> 2.6.33 works for me on IGEPv2.
>>
>> The fact that 2.6.33 works for me rules out automatically anything that
>> would be missing in the Adeos patch.
>>
>> Now we have two possibilities, either the problem comes from a
>> difference between 2.6.31 and 2.6.33, or it comes from a difference
>> between Beagle and IGEP. And since I do not have time to test 2.6.31, I
>> ask you to test 2.6.33.
> The thing I did not explain is that 2.6.31 has no support for the IGEPV2
> board. So, to get it working I would need to backport the board support.
>
> However, I can compile a 2.6.33 kernel with a configuration for the
> beagle board. To be sure that the configuration works for you, I would
> need your .config though.
>

Re: [Xenomai-help] Adeos patched kernel hangs mounting root file system

[Gilles Chanteperdrix]

Bob Feretich wrote:
>   I have downloaded the 2.6.33 omap kernel and I 'm starting to work 
> with it. I'll write again when I have a clean boot of the vanilla kernel 
> and tried to boot again with the Adeos patch.
> 
> I think that I figured out how to tell OpenEmbedded to build it.
> 
> When you display /proc/interrupts on the IGEPv2, do you see interrupts 
> occuring at IRQs greater or equal to IRQ 384?
> Do you see the same number reflected in IRQ 7?

I see this:
           CPU0
  7:     104068        INTC  TWL4030-PIH
 12:          4        INTC  DMA
 37:       1408        INTC  gp timer
 56:     313486        INTC  i2c_omap
 61:          0        INTC  i2c_omap
 74:         42        INTC  serial
 77:         93        INTC  ehci_hcd:usb2
 83:         66        INTC  mmc0
 86:         12        INTC  mmc1
 92:          1        INTC  musb_hdrc
336:        809        GPIO  eth0
378:          0     twl4030  twl4030_usb
384:          0     twl4030  mmc0

I believe the interrupts tagged "twl4030" are chained interrupts. Having
looked at the code, these interrupts are not chained the usual way
because they require i2c communication, which in turn requires a context
allowed to sleep, so they are dispatched by a kernel thread.


-- 
					    Gilles.

Re: [Xenomai-help] Adeos patched kernel hangs mounting root file system

[Bob Feretich]

[-- Attachment #1: Type: text/plain, Size: 3387 bytes --]

  Xenomai booted with the 2.6.33 kernel on BeagleBoard!
I built the below 2.6.33 kernels...

    * No Angstrom patches, no Adeos patch - - it booted, I noticed that
      /proc/interrupts showed no interrupts occurred on IRQs 7 or 378
      (SD card Detect). The 2.6.31 kernel showed 2 on each IRQ just
      after boot.
    * No Angstrom patches, Adeos patch, but Xenomai disabled - - it
      booted. Still no interrupts on IRQs 7 or 378.
    * No Angstrom patches, Adeos patch, and Xenomai enabled - - it
      booted! :-)   Still no interrupts on IRQs 7 or 378.

Something obviously changed in the kernel between 2.6.31 and 2.6.33 to 
suppress the IRQ 378 interrupts that occurred at boot time. This change 
*may* be the reason that Xenomai works on the Beagleboard at 2.6.33, but 
not at 2.6.31.

I suspect that the Adeos patch may have trouble handling Level 2 
interrupts coming through a twl4030 device. I know that it is an OMAP 
design practice to route the SD/MMC Card Detect interrupt through this 
device. The device also controls several voltage regulators supplying 
power to the board and OMAP chip. Overvoltage/undervoltage/thermal 
alerts may also be originated by this device.

The easiest way to test the twl4030 interrupt handling may be to use the 
SD Card for a removable file system (not root). If the file system 
automounts when the SD Card is plugged in, that would indicate that the 
twl4030 interrupts are being handled correctly. From the available 
documentation, the micro-SD card slot on the IGEPv2 should be able to be 
used for this testing.

My current dilemma is to figure out how to move the pieces of Angstrom 
that I want from the 2.6.32 kernel system to the 2.6.33 kernel ahead of 
the Angstrom train. :-(

Many thanks for you help Gilles.

Now that I can see Xenomai running, is there any documentation that 
describes useful things I can poke to obtain Xenomai state, status and 
statistics? (for example the meanings of the data in the /proc/Xemomai 
directory)

Regards,
Bob Feretich

On 7/20/2010 2:24 PM, Gilles Chanteperdrix wrote:
> Bob Feretich wrote:
>>    I have downloaded the 2.6.33 omap kernel and I 'm starting to work
>> with it. I'll write again when I have a clean boot of the vanilla kernel
>> and tried to boot again with the Adeos patch.
>>
>> I think that I figured out how to tell OpenEmbedded to build it.
>>
>> When you display /proc/interrupts on the IGEPv2, do you see interrupts
>> occuring at IRQs greater or equal to IRQ 384?
>> Do you see the same number reflected in IRQ 7?
> I see this:
>             CPU0
>    7:     104068        INTC  TWL4030-PIH
>   12:          4        INTC  DMA
>   37:       1408        INTC  gp timer
>   56:     313486        INTC  i2c_omap
>   61:          0        INTC  i2c_omap
>   74:         42        INTC  serial
>   77:         93        INTC  ehci_hcd:usb2
>   83:         66        INTC  mmc0
>   86:         12        INTC  mmc1
>   92:          1        INTC  musb_hdrc
> 336:        809        GPIO  eth0
> 378:          0     twl4030  twl4030_usb
> 384:          0     twl4030  mmc0
>
> I believe the interrupts tagged "twl4030" are chained interrupts. Having
> looked at the code, these interrupts are not chained the usual way
> because they require i2c communication, which in turn requires a context
> allowed to sleep, so they are dispatched by a kernel thread.
>
>

[-- Attachment #2: Type: text/html, Size: 4135 bytes --]

Re: [Xenomai-help] Adeos patched kernel hangs mounting root file system

[Gilles Chanteperdrix]

Bob Feretich wrote:
>   Xenomai booted with the 2.6.33 kernel on BeagleBoard!
> I built the below 2.6.33 kernels...
> 
>     * No Angstrom patches, no Adeos patch - - it booted, I noticed that
>       /proc/interrupts showed no interrupts occurred on IRQs 7 or 378
>       (SD card Detect). The 2.6.31 kernel showed 2 on each IRQ just
>       after boot.
>     * No Angstrom patches, Adeos patch, but Xenomai disabled - - it
>       booted. Still no interrupts on IRQs 7 or 378.
>     * No Angstrom patches, Adeos patch, and Xenomai enabled - - it
>       booted! :-)   Still no interrupts on IRQs 7 or 378.
> 
> Something obviously changed in the kernel between 2.6.31 and 2.6.33 to 
> suppress the IRQ 378 interrupts that occurred at boot time. This change 
> *may* be the reason that Xenomai works on the Beagleboard at 2.6.33, but 
> not at 2.6.31.
> 
> I suspect that the Adeos patch may have trouble handling Level 2 
> interrupts coming through a twl4030 device. I know that it is an OMAP 
> design practice to route the SD/MMC Card Detect interrupt through this 
> device. The device also controls several voltage regulators supplying 
> power to the board and OMAP chip. Overvoltage/undervoltage/thermal 
> alerts may also be originated by this device.

That is not really possible. The Adeos pipeline does not really "see"
the twl4030 level 2 interrupts, as I said, these are dispatched manually
by a thread, and not handled by the usual chained interrupts mechanism.

However, I had trouble with this code on 2.6.33 generating spurious i2c
interrupts, which lead me to the following patch:
http://git.xenomai.org/?p=ipipe-gch.git;a=commitdiff;h=cdc72520c88b329fa785b0e1f45392cdfff10ec6;hp=e52fee515be7c5b914c201c19604cd700afbc44f

which I backported to 2.6.31 without testing it. Could you try and
revert it?

> 
> The easiest way to test the twl4030 interrupt handling may be to use the 
> SD Card for a removable file system (not root). If the file system 
> automounts when the SD Card is plugged in, that would indicate that the 
> twl4030 interrupts are being handled correctly. From the available 
> documentation, the micro-SD card slot on the IGEPv2 should be able to be 
> used for this testing.

I tested reads and writes on the sd card on IGEPv2, it works, generating
interrupts.

> 
> My current dilemma is to figure out how to move the pieces of Angstrom 
> that I want from the 2.6.32 kernel system to the 2.6.33 kernel ahead of 
> the Angstrom train. :-(

We probably can get 2.6.31 to work, we just have to figure out what is
wrong.

> 
> Many thanks for you help Gilles.
> 
> Now that I can see Xenomai running, is there any documentation that 
> describes useful things I can poke to obtain Xenomai state, status and 
> statistics? (for example the meanings of the data in the /proc/Xemomai 
> directory)

We have this for /proc/xenomai/sched:
http://www.xenomai.org/index.php/Proc/xenomai/sched

You also have /proc/xenomai/stat, but I do not think we have a detailed
page for it.

> 
> Regards,
> Bob Feretich
> 
> On 7/20/2010 2:24 PM, Gilles Chanteperdrix wrote:
>> Bob Feretich wrote:
>>>    I have downloaded the 2.6.33 omap kernel and I 'm starting to work
>>> with it. I'll write again when I have a clean boot of the vanilla kernel
>>> and tried to boot again with the Adeos patch.
>>>
>>> I think that I figured out how to tell OpenEmbedded to build it.
>>>
>>> When you display /proc/interrupts on the IGEPv2, do you see interrupts
>>> occuring at IRQs greater or equal to IRQ 384?
>>> Do you see the same number reflected in IRQ 7?
>> I see this:
>>             CPU0
>>    7:     104068        INTC  TWL4030-PIH
>>   12:          4        INTC  DMA
>>   37:       1408        INTC  gp timer
>>   56:     313486        INTC  i2c_omap
>>   61:          0        INTC  i2c_omap
>>   74:         42        INTC  serial
>>   77:         93        INTC  ehci_hcd:usb2
>>   83:         66        INTC  mmc0
>>   86:         12        INTC  mmc1
>>   92:          1        INTC  musb_hdrc
>> 336:        809        GPIO  eth0
>> 378:          0     twl4030  twl4030_usb
>> 384:          0     twl4030  mmc0
>>
>> I believe the interrupts tagged "twl4030" are chained interrupts. Having
>> looked at the code, these interrupts are not chained the usual way
>> because they require i2c communication, which in turn requires a context
>> allowed to sleep, so they are dispatched by a kernel thread.
>>
>>
> 


-- 
					    Gilles.

Re: [Xenomai-help] Adeos patched kernel hangs mounting root file system

[Bob Feretich]

[-- Attachment #1: Type: text/plain, Size: 2406 bytes --]

  Comments inline...

On 7/20/2010 10:24 PM, Gilles Chanteperdrix wrote:
> ... snipped ...
> However, I had trouble with this code on 2.6.33 generating spurious i2c
> interrupts, which lead me to the following patch:
> http://git.xenomai.org/?p=ipipe-gch.git;a=commitdiff;h=cdc72520c88b329fa785b0e1f45392cdfff10ec6;hp=e52fee515be7c5b914c201c19604cd700afbc44f
>
> which I backported to 2.6.31 without testing it. Could you try and
> revert it?
Sure. I'll start tomorrow.
>> The easiest way to test the twl4030 interrupt handling may be to use the
>> SD Card for a removable file system (not root). If the file system
>> automounts when the SD Card is plugged in, that would indicate that the
>> twl4030 interrupts are being handled correctly. From the available
>> documentation, the micro-SD card slot on the IGEPv2 should be able to be
>> used for this testing.
> I tested reads and writes on the sd card on IGEPv2, it works, generating
> interrupts.
>
Reading and writing is all done via IRQ 83 (for MMC1) and IRQ 86 (for 
MMC2).  It would not exercise IRQ 384.

The /proc/interrupts that you posted showed...
  83:         66        INTC  mmc0
  86:         12        INTC  mmc1
  92:          1        INTC  musb_hdrc
336:        809        GPIO  eth0
378:          0     twl4030  twl4030_usb
384:          0     twl4030  mmc0

IRQ 378 is a USB power system interrupt of some sort. The twl4030 family 
power interrupts for OMAP3 are in the range of IRQ 376 
(TWL4030_PWR_IRQ_BASE) to IRQ 383 (TWL4030_PWR_IRQ_END).

IRQ 384 is the first GPIO pin on the twl4030. On the BeagleBoard, it's 
connected to the SD Card Detect circuit. I believe that is also true for 
the IGEPv2. The Level 2 GPIO interrupts (from the twl4030 family chip, 
not OMAP chip GPIO pins) are in the range of IRQ 384 
(TWL4030_GPIO_IRQ_BASE) to IRQ 383 (TWL4030_GPIO_IRQ_END).

Note that the above ranges apply to all boards that use an OMAP3 chip. 
Of course future changes to the kernel's interrupt handlers can reassign 
any IRQ above 95. (OMAP3 chip hardware IRQs stop at 95. The rest are 
software assigned.)
>> My current dilemma is to figure out how to move the pieces of Angstrom
>> that I want from the 2.6.32 kernel system to the 2.6.33 kernel ahead of
>> the Angstrom train. :-(
> We probably can get 2.6.31 to work, we just have to figure out what is
> wrong.
Thanks for your willingness to help.

Regards,
Bob Feretich

[-- Attachment #2: Type: text/html, Size: 3654 bytes --]

Re: [Xenomai-help] Adeos patched kernel hangs mounting root file system

[Bob Feretich]

[-- Attachment #1: Type: text/plain, Size: 7664 bytes --]

  I reverted the patch that you suggested. Spurious interrupts crashed 
the kernel during boot. (console log below)

The only data that I have to go on for the difference between the Adeos 
hang on 2.6.31 and successful boot on 2.6.33 is interrupts on IRQ 384, 
which occur on 2.6.31 but not 2.6.33.
This change in interrupts is independent of the Adeos patch, so I will 
build a vanilla 2.6.32 kernel and see if the interrupts occur there. 
This may help isolate which kernel change made the difference.

Regards,
Bob Feretich

Boot log with 2.6.31 patch reverted...
Texas Instruments X-Loader 1.4.2 (Feb 19 2009 - 12:01:24)
Reading boot sector
Loading u-boot.bin from mmc


U-Boot 2009.06-rc2 (Nov 02 2009 - 23:57:20)

OMAP3530-GP ES3.0, CPU-OPP2 L3-165MHz
OMAP3 Beagle board + LPDDR/NAND
DRAM:  256 MB
NAND:  256 MiB
In:    serial
Out:   serial
Err:   serial
Board revision C
Die ID #317000030000000004013f8a1701a01b
Hit any key to stop autoboot:  0
mmc1 is available
reading uImage

1882564 bytes read
## Booting kernel from Legacy Image at 80300000 ...
    Image Name:   Angstrom/2.6.31/beagleboard
    Image Type:   ARM Linux Kernel Image (uncompressed)
    Data Size:    1882500 Bytes =  1.8 MB
    Load Address: 80008000
    Entry Point:  80008000
    Verifying Checksum ... OK
    Loading Kernel Image ... OK
OK

Starting kernel ...

Uncompressing 
Linux....................................................................................................
................... done, booting the kernel.
Linux version 2.6.31-omap1 (Bob@domain.hid) (gcc version 4.3.3 (GCC) ) 
#1 Wed Jul 21 12:11:46 PDT 2010
CPU: ARMv7 Processor [411fc083] revision 3 (ARMv7), cr=10c53c7f
CPU: VIPT nonaliasing data cache, VIPT nonaliasing instruction cache
Machine: OMAP3 Beagle Board
Memory policy: ECC disabled, Data cache writeback
OMAP3430 ES3.0
SRAM: Mapped pa 0x40200000 to va 0xe3000000 size: 0x100000
Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 65024
Kernel command line: console=ttyS2,115200n8 root=/dev/mmcblk0p2 rw 
rootfstype=ext3 rootwait
PID hash table entries: 1024 (order: 10, 4096 bytes)
Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
Memory: 128MB 128MB = 256MB total
Memory: 255872KB available (3268K code, 331K data, 132K init, 0K highmem)
NR_IRQS:402
Clocking rate (Crystal/Core/MPU): 26.0/332/500 MHz
Reprogramming SDRC clock to 332000000 Hz
GPMC revision 5.0
IRQ: Found an INTC at 0xd8200000 (revision 4.0) with 96 interrupts
Total of 96 interrupts on 1 active controller
OMAP34xx GPIO hardware version 2.5
OMAP clockevent source: GPTIMER1 at 13000000 Hz
I-pipe 1.16-01: pipeline enabled.
Console: colour dummy device 80x30
Calibrating delay loop... 498.07 BogoMIPS (lpj=2490368)
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
regulator: core version 0.5
NET: Registered protocol family 16
Found NAND on CS0
Registering NAND on CS0
OMAP DMA hardware revision 4.0
bio: create slab <bio-0> at 0
i2c_omap i2c_omap.1: bus 1 rev3.12 at 2600 kHz
twl4030: PIH (irq 7) chaining IRQs 368..375
twl4030: power (irq 373) chaining IRQs 376..383
twl4030: gpio (irq 368) chaining IRQs 384..401
regulator: VMMC1: 1850 <--> 3150 mV normal standby
regulator: VDAC: 1800 mV normal standby
regulator: VUSB1V5: 1500 mV normal standby
regulator: VUSB1V8: 1800 mV normal standby
regulator: VUSB3V1: 3100 mV normal standby
regulator: VPLL2: 1800 mV normal standby
regulator: VSIM: 1800 <--> 3000 mV normal standby
i2c_omap i2c_omap.3: bus 3 rev3.12 at 100 kHz
SCSI subsystem initialized
twl4030_usb twl4030_usb: Initialized TWL4030 USB module
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
musb_hdrc: version 6.0, musb-dma, otg (peripheral+host), debug=0
musb_hdrc: USB OTG mode controller at d80ab000 using DMA, IRQ 92
NET: Registered protocol family 2
IP route cache hash table entries: 2048 (order: 1, 8192 bytes)
TCP established hash table entries: 8192 (order: 4, 65536 bytes)
TCP bind hash table entries: 8192 (order: 3, 32768 bytes)
TCP: Hash tables configured (established 8192 bind 8192)
TCP reno registered
NET: Registered protocol family 1
VFS: Disk quotas dquot_6.5.2
Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
JFFS2 version 2.2. (NAND) �© 2001-2006 Red Hat, Inc.
msgmni has been set to 500
alg: No test for stdrng (krng)
Block layer SCSI generic (bsg) driver version 0.4 loaded (major 253)
io scheduler noop registered
io scheduler anticipatory registered (default)
io scheduler deadline registered
io scheduler cfq registered
Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
serial8250.0: ttyS0 at MMIO 0x4806a000 (irq = 72) is a ST16654
serial8250.1: ttyS1 at MMIO 0x4806c000 (irq = 73) is a ST16654
serial8250.2: ttyS2 at MMIO 0x49020000 (irq = 74) is a ST16654
console [ttyS2] enabled
brd: module loaded
loop: module loaded
i2c /dev entries driver
usbcore: registered new interface driver asix
usbcore: registered new interface driver cdc_ether
usbcore: registered new interface driver net1080
usbcore: registered new interface driver cdc_subset
usbcore: registered new interface driver zaurus
usbmon: debugfs is not available
g_ether gadget: using random self ethernet address
g_ether gadget: using random host ethernet address
usb0: MAC 0a:42:53:3d:f4:42
usb0: HOST MAC 7a:a1:c1:fe:37:e9
g_ether gadget: Ethernet Gadget, version: Memorial Day 2008
g_ether gadget: g_ether ready
musb_hdrc musb_hdrc: MUSB HDRC host driver
musb_hdrc musb_hdrc: new USB bus registered, assigned bus number 1
usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb1: Product: MUSB HDRC host driver
usb usb1: Manufacturer: Linux 2.6.31-omap1 musb-hcd
usb usb1: SerialNumber: musb_hdrc
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 1 port detected
mmci-omap-hs mmci-omap-hs.0: Failed to get debounce clock
TCP cubic registered
NET: Registered protocol family 17
NET: Registered protocol family 15
Spurious irq 95: 0xffffffdf, please flush posted write for irq 56

... a total of 1023 of these messages are generated ...

Spurious irq 95: 0xffffffdf, please flush posted write for irq 56
Unable to handle kernel NULL pointer dereference at virtual address 00000060
pgd = c0004000
[00000060] *pgd=00000000
Internal error: Oops: 0 [#1]
Modules linked in:
CPU: 0    Not tainted  (2.6.31-omap1 #1)
PC is at 0x60
LR is at irq_enter+0x10/0x64
pc : [<00000060>]    lr : [<c004f61c>]    psr: a0000193
sp : cf81a010  ip : cf81a000  fp : fffffffb
r10: 00000004  r9 : ffffffff  r8 : c038c9f8
r7 : c038ca18  r6 : c03b3b80  r5 : 00000000  r4 : 00000042
r3 : 0000005f  r2 : cf81a018  r1 : c0377ccf  r0 : c0076954
Flags: NzCv  IRQs off  FIQs on  Mode SVC_32  ISA ARM  Segment user
Control: 10c5387d  Table: 80004019  DAC: 00000017
Process ��;� (pid: 0, stack limit = 0xcf8182e8)

On 7/20/2010 10:24 PM, Gilles Chanteperdrix wrote:
> That is not really possible. The Adeos pipeline does not really "see"
> the twl4030 level 2 interrupts, as I said, these are dispatched manually
> by a thread, and not handled by the usual chained interrupts mechanism.
>
> However, I had trouble with this code on 2.6.33 generating spurious i2c
> interrupts, which lead me to the following patch:
> http://git.xenomai.org/?p=ipipe-gch.git;a=commitdiff;h=cdc72520c88b329fa785b0e1f45392cdfff10ec6;hp=e52fee515be7c5b914c201c19604cd700afbc44f
>
> which I backported to 2.6.31 without testing it. Could you try and
> revert it?

[-- Attachment #2: Type: text/html, Size: 10465 bytes --]

Re: [Xenomai-help] Adeos patched kernel hangs mounting root file system

[Bob Feretich]

[-- Attachment #1: Type: text/plain, Size: 14665 bytes --]

  When I boot the vanilla 2.6.32 omap kernel and mount the SD-card as 
the root file system no interrupts occur on IRQ 384. So, this change 
must have occurred in the 2.6.32 release.
That *may* mean that the Adeos patch will work  with 2.6.32.

Although this kernel did not cause IRQ 384 interrupts, there were two 
IRQ 378 interrupts from the USB power system. I believe that the IRQ 378 
interrupts are handled via I2C by the same kernel task that handles IRQ 
384.  If I am guessing correctly, the lack of interrupts on IRQ 384 
would permit the kernel to boot even with an Adeos patch applied. The 
interrupts on IRQ 378 could then be checked to see if they were handled 
by the I2C interrupt handler. This Level2 2 interrupt handler task 
should be invoked by the IRQ 7 interrupts, read the twl chip, and post 
interrupts to IRQ 378. If something is wrong, then the IRQ 378 counter 
won't reflect the IRQ 7 count.

How difficult is it to port enough of the Adeos patch to 2.6.32 to 
permit booting with Xenomai disabled?

I will examine the 2.6.32 kernel development logs for entries related to 
this change.

Regards,
Bob Feretich

Console log follows...
Texas Instruments X-Loader 1.4.2 (Feb 19 2009 - 12:01:24)
Reading boot sector
Loading u-boot.bin from mmc


U-Boot 2009.06-rc2 (Nov 02 2009 - 23:57:20)

OMAP3530-GP ES3.0, CPU-OPP2 L3-165MHz
OMAP3 Beagle board + LPDDR/NAND
DRAM:  256 MB
NAND:  256 MiB
In:    serial
Out:   serial
Err:   serial
Board revision C
Die ID #317000030000000004013f8a1701a01b
Hit any key to stop autoboot:  0
mmc1 is available
reading uImage

2659320 bytes read
## Booting kernel from Legacy Image at 80300000 ...
    Image Name:   Angstrom/2.6.32/beagleboard
    Image Type:   ARM Linux Kernel Image (uncompressed)
    Data Size:    2659256 Bytes =  2.5 MB
    Load Address: 80008000
    Entry Point:  80008000
    Verifying Checksum ... OK
    Loading Kernel Image ... OK
OK

Starting kernel ...

Uncompressing 
Linux....................................................................................................
......................................................................... done, 
booting the kernel.
[    0.000000] Linux version 2.6.32 (Bob@domain.hid) (gcc version 
4.3.3 (GCC) ) #1 PREEMPT Wed Jul 21 14:15:03 PDT 20
10
[    0.000000] CPU: ARMv7 Processor [411fc083] revision 3 (ARMv7), 
cr=10c53c7f
[    0.000000] CPU: VIPT nonaliasing data cache, VIPT nonaliasing 
instruction cache
[    0.000000] Machine: OMAP3 Beagle Board
[    0.000000] Memory policy: ECC disabled, Data cache writeback
[    0.000000] OMAP3430/3530 ES3.0 (l2cache iva sgx neon isp )
[    0.000000] SRAM: Mapped pa 0x40200000 to va 0xfe400000 size: 0x100000
[    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  
Total pages: 65024
[    0.000000] Kernel command line: console=ttyS2,115200n8 
root=/dev/mmcblk0p2 rw rootfstype=ext3 rootwait
[    0.000000] PID hash table entries: 1024 (order: 0, 4096 bytes)
[    0.000000] Dentry cache hash table entries: 32768 (order: 5, 131072 
bytes)
[    0.000000] Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
[    0.000000] Memory: 128MB 128MB = 256MB total
[    0.000000] Memory: 253952KB available (4860K code, 559K data, 164K 
init, 0K highmem)
[    0.000000] Hierarchical RCU implementation.
[    0.000000] NR_IRQS:402
[    0.000000] Clocking rate (Crystal/Core/MPU): 26.0/332/500 MHz
[    0.000000] Reprogramming SDRC clock to 332000000 Hz
[    0.000000] GPMC revision 5.0
[    0.000000] IRQ: Found an INTC at 0xfa200000 (revision 4.0) with 96 
interrupts
[    0.000000] Total of 96 interrupts on 1 active controller
[    0.000000] OMAP GPIO hardware version 2.5
[    0.000000] OMAP clockevent source: GPTIMER12 at 32768 Hz
[    0.000000] Console: colour dummy device 80x30
[    0.000000] Calibrating delay loop... 480.01 BogoMIPS (lpj=1875968)
[    0.000000] Mount-cache hash table entries: 512
[    0.000000] CPU: Testing write buffer coherency: ok
[    0.000000] devtmpfs: initialized
[    0.000000] regulator: core version 0.5
[    0.000000] NET: Registered protocol family 16
[    0.000000] Found NAND on CS0
[    0.000000] Registering NAND on CS0
[   18.373596] OMAP DMA hardware revision 4.0
[   18.379821] bio: create slab <bio-0> at 0
[   18.381439] SCSI subsystem initialized
[   18.382171] usbcore: registered new interface driver usbfs
[   18.382354] usbcore: registered new interface driver hub
[   18.382568] usbcore: registered new device driver usb
[   18.383026] i2c_omap i2c_omap.1: bus 1 rev3.12 at 2600 kHz
[   18.386108] twl4030: PIH (irq 7) chaining IRQs 368..375
[   18.386138] twl4030: power (irq 373) chaining IRQs 376..383
[   18.386505] twl4030: gpio (irq 368) chaining IRQs 384..401
[   18.387969] regulator: VUSB1V5: 1500 mV normal standby
[   18.388305] regulator: VUSB1V8: 1800 mV normal standby
[   18.388671] regulator: VUSB3V1: 3100 mV normal standby
[   18.390106] twl4030_usb twl4030_usb: Initialized TWL4030 USB module
[   18.390563] regulator: VMMC1: 1850 <--> 3150 mV normal standby
[   18.390869] regulator: VDAC: 1800 mV normal standby
[   18.391204] regulator: VPLL2: 1800 mV normal standby
[   18.391510] regulator: VSIM: 1800 <--> 3000 mV normal standby
[   18.403625] i2c_omap i2c_omap.3: bus 3 rev3.12 at 100 kHz
[   18.404998] Switching to clocksource 32k_counter
[   18.416595] musb_hdrc: version 6.0, musb-dma, otg (peripheral+host), 
debug=0
[   18.420166] musb_hdrc: USB OTG mode controller at fa0ab000 using DMA, 
IRQ 92
[   18.420898] NET: Registered protocol family 2
[   18.421173] IP route cache hash table entries: 2048 (order: 1, 8192 
bytes)
[   18.421844] TCP established hash table entries: 8192 (order: 4, 65536 
bytes)
[   18.422088] TCP bind hash table entries: 8192 (order: 3, 32768 bytes)
[   18.422241] TCP: Hash tables configured (established 8192 bind 8192)
[   18.422271] TCP reno registered
[   18.422546] NET: Registered protocol family 1
[   18.423095] RPC: Registered udp transport module.
[   18.423095] RPC: Registered tcp transport module.
[   18.423126] RPC: Registered tcp NFSv4.1 backchannel transport module.
[   18.425628] VFS: Disk quotas dquot_6.5.2
[   18.425750] Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[   18.427154] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[   18.428161] JFFS2 version 2.2. (NAND) (SUMMARY)  �ݩ 2001-2006 Red 
Hat, Inc.
[   18.429351] msgmni has been set to 496
[   18.434722] alg: No test for stdrng (krng)
[   18.435089] Block layer SCSI generic (bsg) driver version 0.4 loaded 
(major 254)
[   18.435119] io scheduler noop registered
[   18.435150] io scheduler anticipatory registered
[   18.435150] io scheduler deadline registered
[   18.435333] io scheduler cfq registered (default)
[   18.447570] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
[   18.468475] serial8250.0: ttyS0 at MMIO 0x4806a000 (irq = 72) is a 
ST16654
[   18.488403] serial8250.1: ttyS1 at MMIO 0x4806c000 (irq = 73) is a 
ST16654
[   18.508300] serial8250.2: ttyS2 at MMIO 0x49020000 (irq = 74) is a 
ST16654
[   18.940307] console [ttyS2] enabled
[   18.952697] brd: module loaded
[   18.960174] loop: module loaded
[   18.964416] omap2-nand driver initializing
[   18.968963] NAND device: Manufacturer ID: 0x2c, Chip ID: 0xba (Micron 
NAND 256MiB 1,8V 16-bit)
[   18.978149] cmdlinepart partition parsing not available
[   18.983489] Creating 5 MTD partitions on "omap2-nand":
[   18.988677] 0x000000000000-0x000000080000 : "X-Loader"
[   18.995330] 0x000000080000-0x000000260000 : "U-Boot"
[   19.002105] 0x000000260000-0x000000280000 : "U-Boot Env"
[   19.008514] 0x000000280000-0x000000680000 : "Kernel"
[   19.016113] 0x000000680000-0x000010000000 : "File System"
[   19.124450] usbcore: registered new interface driver catc
[   19.129882] catc: v2.8:CATC EL1210A NetMate USB Ethernet driver
[   19.135955] usbcore: registered new interface driver kaweth
[   19.141632] pegasus: v0.6.14 (2006/09/27), Pegasus/Pegasus II USB 
Ethernet driver
[   19.149261] usbcore: registered new interface driver pegasus
[   19.154998] rtl8150: v0.6.2 (2004/08/27):rtl8150 based usb-ethernet 
driver
[   19.162048] usbcore: registered new interface driver rtl8150
[   19.167846] usbcore: registered new interface driver asix
[   19.173400] usbcore: registered new interface driver cdc_ether
[   19.179412] usbcore: registered new interface driver dm9601
[   19.185119] usbcore: registered new interface driver smsc95xx
[   19.191040] usbcore: registered new interface driver gl620a
[   19.196777] usbcore: registered new interface driver net1080
[   19.202575] usbcore: registered new interface driver plusb
[   19.208190] usbcore: registered new interface driver rndis_host
[   19.214263] usbcore: registered new interface driver cdc_subset
[   19.220367] usbcore: registered new interface driver zaurus
[   19.226104] usbcore: registered new interface driver MOSCHIP 
usb-ethernet driver
[   19.234161] Initializing USB Mass Storage driver...
[   19.239196] usbcore: registered new interface driver usb-storage
[   19.245330] USB Mass Storage support registered.
[   19.250061] g_ether gadget: using random self ethernet address
[   19.255950] g_ether gadget: using random host ethernet address
[   19.262390] usb0: MAC 76:ff:8e:a3:38:74
[   19.266326] usb0: HOST MAC 92:e6:7c:a6:1a:38
[   19.270660] g_ether gadget: Ethernet Gadget, version: Memorial Day 2008
[   19.277374] g_ether gadget: g_ether ready
[   19.281433] musb_hdrc musb_hdrc: MUSB HDRC host driver
[   19.287078] musb_hdrc musb_hdrc: new USB bus registered, assigned bus 
number 1
[   19.294555] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[   19.301422] usb usb1: New USB device strings: Mfr=3, Product=2, 
SerialNumber=1
[   19.308715] usb usb1: Product: MUSB HDRC host driver
[   19.313751] usb usb1: Manufacturer: Linux 2.6.32 musb-hcd
[   19.319213] usb usb1: SerialNumber: musb_hdrc
[   19.324157] usb usb1: configuration #1 chosen from 1 choice
[   19.330078] hub 1-0:1.0: USB hub found
[   19.333953] hub 1-0:1.0: 1 port detected
[   19.338867] mice: PS/2 mouse device common for all mice
[   19.344665] input: gpio-keys as /devices/platform/gpio-keys/input/input0
[   19.352996] input: twl4030_pwrbutton as 
/devices/platform/i2c_omap.1/i2c-1/1-0049/twl4030_pwrbutton/input/input1
[   19.363922] i2c /dev entries driver
[   19.475860] Registered led device: beagleboard::usr0
[   19.481018] Registered led device: beagleboard::usr1
[   19.486724] Registered led device: beagleboard::pmu_stat
[   19.492309] oprofile: using arm/armv7
[   19.496276] TCP cubic registered
[   19.499603] NET: Registered protocol family 17
[   19.504119] NET: Registered protocol family 15
[   19.508728] ThumbEE CPU extension supported.
[   19.513031] Power Management for TI OMAP3.
[   19.528015] VFP support v0.3: implementor 41 architecture 3 part 30 
variant c rev 1
[   19.536712] registered taskstats version 1
[   19.542541] regulator_init_complete: incomplete constraints, leaving 
VDVI on
[   19.549804] regulator_init_complete: incomplete constraints, leaving 
VDAC on
[   19.557556] Waiting for root device /dev/mmcblk0p2...
[   19.842773] mmc0: new high speed SDHC card at address cd63
[   19.848846] mmcblk0: mmc0:cd63 SD04G 3.69 GiB
[   19.853790]  mmcblk0: p1 p2
[   19.896240] kjournald starting.  Commit interval 5 seconds
[   20.155639] EXT3 FS on mmcblk0p2, internal journal
[   20.160491] EXT3-fs: mounted filesystem with writeback data mode.
[   20.166717] VFS: Mounted root (ext3 filesystem) on device 179:2.
[   20.175598] devtmpfs: mounted
[   20.178741] Freeing init memory: 164K
INIT: version 2.86 booting
Please wait: booting...
Starting udev
Remounting root file system...
Caching udev devnodes
Populating dev cache
root: mount: mounting rootfs on / failed: No such file or directory
Configuring network interfaces... ifconfig: SIOCGIFFLAGS: No such device
done.
Setting up IP spoofing protection: rp_filter.
hwclock: can't open '/dev/misc/rtc': No such file or directory
Tue May 18 20:58:00 UTC 2010
hwclock: can't open '/dev/misc/rtc': No such file or directory
Configuring update-modules.
Starting to configure packages...
Nothing to be done
Finished to configure packages.
INIT: Entering runlevel: 5
Creating Dropbear SSH server RSA host key.
Will output 1024 bit rsa secret key to '/etc/dropbear/dropbear_rsa_host_key'
Generating key, this may take a while...
Public key portion is:
ssh-rsa 
AAAAB3NzaC1yc2EAAAADAQABAAAAgwCFnP91SQbJJLLS7KMeQYYjBm2KLETrqGJtmHxTotPEBJi8cgFBkW2ZBk8mgz+u92kJOkKmk/UJtV/gkXo
sibLr41W2CJyf6ILPujqZk0RvGxybuW5dp18C2rP9uW3vPhQ4GDrXG3s5i7r/s5hvgWtY8QDXcYVLtZUsx6B/fufK+aaT 
root@domain.hid
Fingerprint: md5 59:56:33:4a:a7:8f:ba:e6:33:43:2d:d1:3d:a6:83:1e
Starting Dropbear SSH server: dropbear.
Starting syslogd/klogd: done

.-------.
|       |                  .-.
|   |   |-----.-----.-----.| |   .----..-----.-----.
|       |     | __  |  ---'| '--.|  .-'|     |     |
|   |   |  |  |     |---  ||  --'|  |  |  '  | | | |
'---'---'--'--'--.  |-----''----''--'  '-----'-'-'-'
                 -'  |
                 '---'

The Angstrom Distribution beagleboard ttyS2

Angstrom 2010.4-test-20100518 beagleboard ttyS2

beagleboard login: root
root@domain.hid:~# cat /proc/interrupts
            CPU0
   7:          2        INTC  TWL4030-PIH
  11:          0        INTC  prcm
  12:       1114        INTC  DMA
  56:        304        INTC  i2c_omap
  61:          0        INTC  i2c_omap
  72:          1        INTC  serial idle
  73:          1        INTC  serial idle
  74:        201        INTC  serial idle, serial
  83:       1976        INTC  mmc0
  92:          1        INTC  musb_hdrc
  93:          0        INTC  musb_hdrc
  95:       3266        INTC  gp timer
167:          0        GPIO  user
376:          0     twl4030  twl4030_pwrbutton
378:          2     twl4030  twl4030_usb
384:          0     twl4030  mmc0
Err:          0
root@domain.hid:~#

On 7/21/2010 1:33 PM, Bob Feretich wrote:
> I reverted the patch that you suggested. Spurious interrupts crashed 
> the kernel during boot. (console log below)
>
> The only data that I have to go on for the difference between the 
> Adeos hang on 2.6.31 and successful boot on 2.6.33 is interrupts on 
> IRQ 384, which occur on 2.6.31 but not 2.6.33.
> This change in interrupts is independent of the Adeos patch, so I will 
> build a vanilla 2.6.32 kernel and see if the interrupts occur there. 
> This may help isolate which kernel change made the difference.
>
> Regards,
> Bob Feretich
>
> Boot log with 2.6.31 patch reverted...
> Texas Instruments X-Loader 1.4.2 (Feb 19 2009 - 12:01:24)
> Reading boot sector
> ... snipped ...

[-- Attachment #2: Type: text/html, Size: 19814 bytes --]

Re: [Xenomai-help] Adeos patched kernel hangs mounting root file system - correction

[Bob Feretich]

[-- Attachment #1: Type: text/plain, Size: 19183 bytes --]

  In the past several messages, I reported that applying the Adeos patch 
on the BeagleBoard caused some failures that may be related to IRQ 384 
interrupts (SD card detect). I now believe that I misread the output and 
that all my reports should reference IRQ 378 rather than IRQ 384.

The twl level 2 interrupt handler is used for both of these IRQs, so it 
could still be that source of the boot hangs.

Excerpts from the console logs are shown below.

It is still suspicious that IRQ 378 interrupts are present in kernels 
where the Adeos patch hangs and not present where it is successful. 
However, since the hang seems to be related to the remounting of the SD 
card (mmc0) as the root file system and IRQ 378 seems to be unrelated to 
this action, the suspicion is weak.

Regards,
Bob Feretich

2.6.31 without Adeos patch (below); hangs with Adeos patch
cat /proc/interrupts
            CPU0
   7:          2        INTC  TWL4030-PIH
  11:          0        INTC  prcm
  12:       1011        INTC  DMA
  56:        313        INTC  i2c_omap
  61:          0        INTC  i2c_omap
  72:          1        INTC  serial idle
  73:          1        INTC  serial idle
  74:        107        INTC  serial idle, serial
  77:          0        INTC  ehci_hcd:usb1
  83:       1414        INTC  mmc0
  92:          1        INTC  musb_hdrc
  93:          0        INTC  musb_hdrc
  95:       1921        INTC  gp timer
378:          2     twl4030  twl4030_usb
379:          0     twl4030  rtc0
384:          0     twl4030  mmc0
Err:          0

2.6.32 without Adeos patch (below): no Adeos patch available
cat /proc/interrupts
            CPU0
   7:          2        INTC  TWL4030-PIH
  11:          0        INTC  prcm
  12:       1001        INTC  DMA
  56:        304        INTC  i2c_omap
  61:          0        INTC  i2c_omap
  72:          1        INTC  serial idle
  73:          1        INTC  serial idle
  74:        109        INTC  serial idle, serial
  83:       1794        INTC  mmc0
  92:          1        INTC  musb_hdrc
  93:          0        INTC  musb_hdrc
  95:       2382        INTC  gp timer
167:          0        GPIO  user
376:          0     twl4030  twl4030_pwrbutton
378:          2     twl4030  twl4030_usb
384:          0     twl4030  mmc0
Err:          0

2.6.33 without Adeos patch (below):
cat /proc/interrupts
            CPU0
   7:          0        INTC  TWL4030-PIH
  11:          0        INTC  prcm
  12:       1037        INTC  DMA
  37:        773        INTC  gp timer
  56:        318        INTC  i2c_omap
  61:          0        INTC  i2c_omap
  72:          1        INTC  serial idle
  73:          1        INTC  serial idle
  74:        115        INTC  serial idle, serial
  77:          0        INTC  ehci_hcd:usb1
  83:      14790        INTC  mmc0
  92:          0        INTC  musb_hdrc
  93:          0        INTC  musb_hdrc
378:          0     twl4030  twl4030_usb
379:          0     twl4030  rtc0
384:          0     twl4030  mmc0
Err:          0

2.6.33 with Adeos patch (below);
cat /proc/interrupts
            CPU0
   7:          0        INTC  TWL4030-PIH
  11:          0        INTC  prcm
  12:       1288        INTC  DMA
  37:       1366        INTC  gp timer
  56:        446        INTC  i2c_omap
  61:          0        INTC  i2c_omap
  72:          1        INTC  serial idle
  73:          1        INTC  serial idle
  74:        283        INTC  serial idle, serial
  77:          0        INTC  ehci_hcd:usb1
  83:       2312        INTC  mmc0
  92:          0        INTC  musb_hdrc
  93:          0        INTC  musb_hdrc
378:          0     twl4030  twl4030_usb
379:          0     twl4030  rtc0
384:          0     twl4030  mmc0
Err:          0
root@domain.hid:~# cat /proc/xenomai/irq
IRQ         CPU0
  37:        1376         [timer]
418:           0         [virtual]


On 7/21/2010 4:30 PM, Bob Feretich wrote:
> When I boot the vanilla 2.6.32 omap kernel and mount the SD-card as 
> the root file system no interrupts occur on IRQ 384. So, this change 
> must have occurred in the 2.6.32 release.
> That *may* mean that the Adeos patch will work  with 2.6.32.
>
> Although this kernel did not cause IRQ 384 interrupts, there were two 
> IRQ 378 interrupts from the USB power system. I believe that the IRQ 
> 378 interrupts are handled via I2C by the same kernel task that 
> handles IRQ 384.  If I am guessing correctly, the lack of interrupts 
> on IRQ 384 would permit the kernel to boot even with an Adeos patch 
> applied. The interrupts on IRQ 378 could then be checked to see if 
> they were handled by the I2C interrupt handler. This Level2 2 
> interrupt handler task should be invoked by the IRQ 7 interrupts, read 
> the twl chip, and post interrupts to IRQ 378. If something is wrong, 
> then the IRQ 378 counter won't reflect the IRQ 7 count.
>
> How difficult is it to port enough of the Adeos patch to 2.6.32 to 
> permit booting with Xenomai disabled?
>
> I will examine the 2.6.32 kernel development logs for entries related 
> to this change.
>
> Regards,
> Bob Feretich
>
> Console log follows...
> Texas Instruments X-Loader 1.4.2 (Feb 19 2009 - 12:01:24)
> Reading boot sector
> Loading u-boot.bin from mmc
>
>
> U-Boot 2009.06-rc2 (Nov 02 2009 - 23:57:20)
>
> OMAP3530-GP ES3.0, CPU-OPP2 L3-165MHz
> OMAP3 Beagle board + LPDDR/NAND
> DRAM:  256 MB
> NAND:  256 MiB
> In:    serial
> Out:   serial
> Err:   serial
> Board revision C
> Die ID #317000030000000004013f8a1701a01b
> Hit any key to stop autoboot:  0
> mmc1 is available
> reading uImage
>
> 2659320 bytes read
> ## Booting kernel from Legacy Image at 80300000 ...
>    Image Name:   Angstrom/2.6.32/beagleboard
>    Image Type:   ARM Linux Kernel Image (uncompressed)
>    Data Size:    2659256 Bytes =  2.5 MB
>    Load Address: 80008000
>    Entry Point:  80008000
>    Verifying Checksum ... OK
>    Loading Kernel Image ... OK
> OK
>
> Starting kernel ...
>
> Uncompressing 
> Linux....................................................................................................
> ......................................................................... 
> done, booting the kernel.
> [    0.000000] Linux version 2.6.32 (Bob@domain.hid) (gcc version 
> 4.3.3 (GCC) ) #1 PREEMPT Wed Jul 21 14:15:03 PDT 20
> 10
> [    0.000000] CPU: ARMv7 Processor [411fc083] revision 3 (ARMv7), 
> cr=10c53c7f
> [    0.000000] CPU: VIPT nonaliasing data cache, VIPT nonaliasing 
> instruction cache
> [    0.000000] Machine: OMAP3 Beagle Board
> [    0.000000] Memory policy: ECC disabled, Data cache writeback
> [    0.000000] OMAP3430/3530 ES3.0 (l2cache iva sgx neon isp )
> [    0.000000] SRAM: Mapped pa 0x40200000 to va 0xfe400000 size: 0x100000
> [    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  
> Total pages: 65024
> [    0.000000] Kernel command line: console=ttyS2,115200n8 
> root=/dev/mmcblk0p2 rw rootfstype=ext3 rootwait
> [    0.000000] PID hash table entries: 1024 (order: 0, 4096 bytes)
> [    0.000000] Dentry cache hash table entries: 32768 (order: 5, 
> 131072 bytes)
> [    0.000000] Inode-cache hash table entries: 16384 (order: 4, 65536 
> bytes)
> [    0.000000] Memory: 128MB 128MB = 256MB total
> [    0.000000] Memory: 253952KB available (4860K code, 559K data, 164K 
> init, 0K highmem)
> [    0.000000] Hierarchical RCU implementation.
> [    0.000000] NR_IRQS:402
> [    0.000000] Clocking rate (Crystal/Core/MPU): 26.0/332/500 MHz
> [    0.000000] Reprogramming SDRC clock to 332000000 Hz
> [    0.000000] GPMC revision 5.0
> [    0.000000] IRQ: Found an INTC at 0xfa200000 (revision 4.0) with 96 
> interrupts
> [    0.000000] Total of 96 interrupts on 1 active controller
> [    0.000000] OMAP GPIO hardware version 2.5
> [    0.000000] OMAP clockevent source: GPTIMER12 at 32768 Hz
> [    0.000000] Console: colour dummy device 80x30
> [    0.000000] Calibrating delay loop... 480.01 BogoMIPS (lpj=1875968)
> [    0.000000] Mount-cache hash table entries: 512
> [    0.000000] CPU: Testing write buffer coherency: ok
> [    0.000000] devtmpfs: initialized
> [    0.000000] regulator: core version 0.5
> [    0.000000] NET: Registered protocol family 16
> [    0.000000] Found NAND on CS0
> [    0.000000] Registering NAND on CS0
> [   18.373596] OMAP DMA hardware revision 4.0
> [   18.379821] bio: create slab <bio-0> at 0
> [   18.381439] SCSI subsystem initialized
> [   18.382171] usbcore: registered new interface driver usbfs
> [   18.382354] usbcore: registered new interface driver hub
> [   18.382568] usbcore: registered new device driver usb
> [   18.383026] i2c_omap i2c_omap.1: bus 1 rev3.12 at 2600 kHz
> [   18.386108] twl4030: PIH (irq 7) chaining IRQs 368..375
> [   18.386138] twl4030: power (irq 373) chaining IRQs 376..383
> [   18.386505] twl4030: gpio (irq 368) chaining IRQs 384..401
> [   18.387969] regulator: VUSB1V5: 1500 mV normal standby
> [   18.388305] regulator: VUSB1V8: 1800 mV normal standby
> [   18.388671] regulator: VUSB3V1: 3100 mV normal standby
> [   18.390106] twl4030_usb twl4030_usb: Initialized TWL4030 USB module
> [   18.390563] regulator: VMMC1: 1850 <--> 3150 mV normal standby
> [   18.390869] regulator: VDAC: 1800 mV normal standby
> [   18.391204] regulator: VPLL2: 1800 mV normal standby
> [   18.391510] regulator: VSIM: 1800 <--> 3000 mV normal standby
> [   18.403625] i2c_omap i2c_omap.3: bus 3 rev3.12 at 100 kHz
> [   18.404998] Switching to clocksource 32k_counter
> [   18.416595] musb_hdrc: version 6.0, musb-dma, otg 
> (peripheral+host), debug=0
> [   18.420166] musb_hdrc: USB OTG mode controller at fa0ab000 using 
> DMA, IRQ 92
> [   18.420898] NET: Registered protocol family 2
> [   18.421173] IP route cache hash table entries: 2048 (order: 1, 8192 
> bytes)
> [   18.421844] TCP established hash table entries: 8192 (order: 4, 
> 65536 bytes)
> [   18.422088] TCP bind hash table entries: 8192 (order: 3, 32768 bytes)
> [   18.422241] TCP: Hash tables configured (established 8192 bind 8192)
> [   18.422271] TCP reno registered
> [   18.422546] NET: Registered protocol family 1
> [   18.423095] RPC: Registered udp transport module.
> [   18.423095] RPC: Registered tcp transport module.
> [   18.423126] RPC: Registered tcp NFSv4.1 backchannel transport module.
> [   18.425628] VFS: Disk quotas dquot_6.5.2
> [   18.425750] Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
> [   18.427154] squashfs: version 4.0 (2009/01/31) Phillip Lougher
> [   18.428161] JFFS2 version 2.2. (NAND) (SUMMARY)  �ݩ 2001-2006 
> Red Hat, Inc.
> [   18.429351] msgmni has been set to 496
> [   18.434722] alg: No test for stdrng (krng)
> [   18.435089] Block layer SCSI generic (bsg) driver version 0.4 
> loaded (major 254)
> [   18.435119] io scheduler noop registered
> [   18.435150] io scheduler anticipatory registered
> [   18.435150] io scheduler deadline registered
> [   18.435333] io scheduler cfq registered (default)
> [   18.447570] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
> [   18.468475] serial8250.0: ttyS0 at MMIO 0x4806a000 (irq = 72) is a 
> ST16654
> [   18.488403] serial8250.1: ttyS1 at MMIO 0x4806c000 (irq = 73) is a 
> ST16654
> [   18.508300] serial8250.2: ttyS2 at MMIO 0x49020000 (irq = 74) is a 
> ST16654
> [   18.940307] console [ttyS2] enabled
> [   18.952697] brd: module loaded
> [   18.960174] loop: module loaded
> [   18.964416] omap2-nand driver initializing
> [   18.968963] NAND device: Manufacturer ID: 0x2c, Chip ID: 0xba 
> (Micron NAND 256MiB 1,8V 16-bit)
> [   18.978149] cmdlinepart partition parsing not available
> [   18.983489] Creating 5 MTD partitions on "omap2-nand":
> [   18.988677] 0x000000000000-0x000000080000 : "X-Loader"
> [   18.995330] 0x000000080000-0x000000260000 : "U-Boot"
> [   19.002105] 0x000000260000-0x000000280000 : "U-Boot Env"
> [   19.008514] 0x000000280000-0x000000680000 : "Kernel"
> [   19.016113] 0x000000680000-0x000010000000 : "File System"
> [   19.124450] usbcore: registered new interface driver catc
> [   19.129882] catc: v2.8:CATC EL1210A NetMate USB Ethernet driver
> [   19.135955] usbcore: registered new interface driver kaweth
> [   19.141632] pegasus: v0.6.14 (2006/09/27), Pegasus/Pegasus II USB 
> Ethernet driver
> [   19.149261] usbcore: registered new interface driver pegasus
> [   19.154998] rtl8150: v0.6.2 (2004/08/27):rtl8150 based usb-ethernet 
> driver
> [   19.162048] usbcore: registered new interface driver rtl8150
> [   19.167846] usbcore: registered new interface driver asix
> [   19.173400] usbcore: registered new interface driver cdc_ether
> [   19.179412] usbcore: registered new interface driver dm9601
> [   19.185119] usbcore: registered new interface driver smsc95xx
> [   19.191040] usbcore: registered new interface driver gl620a
> [   19.196777] usbcore: registered new interface driver net1080
> [   19.202575] usbcore: registered new interface driver plusb
> [   19.208190] usbcore: registered new interface driver rndis_host
> [   19.214263] usbcore: registered new interface driver cdc_subset
> [   19.220367] usbcore: registered new interface driver zaurus
> [   19.226104] usbcore: registered new interface driver MOSCHIP 
> usb-ethernet driver
> [   19.234161] Initializing USB Mass Storage driver...
> [   19.239196] usbcore: registered new interface driver usb-storage
> [   19.245330] USB Mass Storage support registered.
> [   19.250061] g_ether gadget: using random self ethernet address
> [   19.255950] g_ether gadget: using random host ethernet address
> [   19.262390] usb0: MAC 76:ff:8e:a3:38:74
> [   19.266326] usb0: HOST MAC 92:e6:7c:a6:1a:38
> [   19.270660] g_ether gadget: Ethernet Gadget, version: Memorial Day 2008
> [   19.277374] g_ether gadget: g_ether ready
> [   19.281433] musb_hdrc musb_hdrc: MUSB HDRC host driver
> [   19.287078] musb_hdrc musb_hdrc: new USB bus registered, assigned 
> bus number 1
> [   19.294555] usb usb1: New USB device found, idVendor=1d6b, 
> idProduct=0002
> [   19.301422] usb usb1: New USB device strings: Mfr=3, Product=2, 
> SerialNumber=1
> [   19.308715] usb usb1: Product: MUSB HDRC host driver
> [   19.313751] usb usb1: Manufacturer: Linux 2.6.32 musb-hcd
> [   19.319213] usb usb1: SerialNumber: musb_hdrc
> [   19.324157] usb usb1: configuration #1 chosen from 1 choice
> [   19.330078] hub 1-0:1.0: USB hub found
> [   19.333953] hub 1-0:1.0: 1 port detected
> [   19.338867] mice: PS/2 mouse device common for all mice
> [   19.344665] input: gpio-keys as 
> /devices/platform/gpio-keys/input/input0
> [   19.352996] input: twl4030_pwrbutton as 
> /devices/platform/i2c_omap.1/i2c-1/1-0049/twl4030_pwrbutton/input/input1
> [   19.363922] i2c /dev entries driver
> [   19.475860] Registered led device: beagleboard::usr0
> [   19.481018] Registered led device: beagleboard::usr1
> [   19.486724] Registered led device: beagleboard::pmu_stat
> [   19.492309] oprofile: using arm/armv7
> [   19.496276] TCP cubic registered
> [   19.499603] NET: Registered protocol family 17
> [   19.504119] NET: Registered protocol family 15
> [   19.508728] ThumbEE CPU extension supported.
> [   19.513031] Power Management for TI OMAP3.
> [   19.528015] VFP support v0.3: implementor 41 architecture 3 part 30 
> variant c rev 1
> [   19.536712] registered taskstats version 1
> [   19.542541] regulator_init_complete: incomplete constraints, 
> leaving VDVI on
> [   19.549804] regulator_init_complete: incomplete constraints, 
> leaving VDAC on
> [   19.557556] Waiting for root device /dev/mmcblk0p2...
> [   19.842773] mmc0: new high speed SDHC card at address cd63
> [   19.848846] mmcblk0: mmc0:cd63 SD04G 3.69 GiB
> [   19.853790]  mmcblk0: p1 p2
> [   19.896240] kjournald starting.  Commit interval 5 seconds
> [   20.155639] EXT3 FS on mmcblk0p2, internal journal
> [   20.160491] EXT3-fs: mounted filesystem with writeback data mode.
> [   20.166717] VFS: Mounted root (ext3 filesystem) on device 179:2.
> [   20.175598] devtmpfs: mounted
> [   20.178741] Freeing init memory: 164K
> INIT: version 2.86 booting
> Please wait: booting...
> Starting udev
> Remounting root file system...
> Caching udev devnodes
> Populating dev cache
> root: mount: mounting rootfs on / failed: No such file or directory
> Configuring network interfaces... ifconfig: SIOCGIFFLAGS: No such device
> done.
> Setting up IP spoofing protection: rp_filter.
> hwclock: can't open '/dev/misc/rtc': No such file or directory
> Tue May 18 20:58:00 UTC 2010
> hwclock: can't open '/dev/misc/rtc': No such file or directory
> Configuring update-modules.
> Starting to configure packages...
> Nothing to be done
> Finished to configure packages.
> INIT: Entering runlevel: 5
> Creating Dropbear SSH server RSA host key.
> Will output 1024 bit rsa secret key to 
> '/etc/dropbear/dropbear_rsa_host_key'
> Generating key, this may take a while...
> Public key portion is:
> ssh-rsa 
> AAAAB3NzaC1yc2EAAAADAQABAAAAgwCFnP91SQbJJLLS7KMeQYYjBm2KLETrqGJtmHxTotPEBJi8cgFBkW2ZBk8mgz+u92kJOkKmk/UJtV/gkXo
> sibLr41W2CJyf6ILPujqZk0RvGxybuW5dp18C2rP9uW3vPhQ4GDrXG3s5i7r/s5hvgWtY8QDXcYVLtZUsx6B/fufK+aaT 
> root@domain.hid
> Fingerprint: md5 59:56:33:4a:a7:8f:ba:e6:33:43:2d:d1:3d:a6:83:1e
> Starting Dropbear SSH server: dropbear.
> Starting syslogd/klogd: done
>
> .-------.
> |       |                  .-.
> |   |   |-----.-----.-----.| |   .----..-----.-----.
> |       |     | __  |  ---'| '--.|  .-'|     |     |
> |   |   |  |  |     |---  ||  --'|  |  |  '  | | | |
> '---'---'--'--'--.  |-----''----''--'  '-----'-'-'-'
>                 -'  |
>                 '---'
>
> The Angstrom Distribution beagleboard ttyS2
>
> Angstrom 2010.4-test-20100518 beagleboard ttyS2
>
> beagleboard login: root
> root@domain.hid:~# cat /proc/interrupts
>            CPU0
>   7:          2        INTC  TWL4030-PIH
>  11:          0        INTC  prcm
>  12:       1114        INTC  DMA
>  56:        304        INTC  i2c_omap
>  61:          0        INTC  i2c_omap
>  72:          1        INTC  serial idle
>  73:          1        INTC  serial idle
>  74:        201        INTC  serial idle, serial
>  83:       1976        INTC  mmc0
>  92:          1        INTC  musb_hdrc
>  93:          0        INTC  musb_hdrc
>  95:       3266        INTC  gp timer
> 167:          0        GPIO  user
> 376:          0     twl4030  twl4030_pwrbutton
> 378:          2     twl4030  twl4030_usb
> 384:          0     twl4030  mmc0
> Err:          0
> root@domain.hid:~#
>
> On 7/21/2010 1:33 PM, Bob Feretich wrote:
>> I reverted the patch that you suggested. Spurious interrupts crashed 
>> the kernel during boot. (console log below)
>>
>> The only data that I have to go on for the difference between the 
>> Adeos hang on 2.6.31 and successful boot on 2.6.33 is interrupts on 
>> IRQ 384, which occur on 2.6.31 but not 2.6.33.
>> This change in interrupts is independent of the Adeos patch, so I 
>> will build a vanilla 2.6.32 kernel and see if the interrupts occur 
>> there. This may help isolate which kernel change made the difference.
>>
>> Regards,
>> Bob Feretich
>>
>> Boot log with 2.6.31 patch reverted...
>> Texas Instruments X-Loader 1.4.2 (Feb 19 2009 - 12:01:24)
>> Reading boot sector
>> ... snipped ...

[-- Attachment #2: Type: text/html, Size: 27134 bytes --]

Re: [Xenomai-help] Adeos patched kernel hangs mounting root file system - correction

[Gilles Chanteperdrix]

Bob Feretich wrote:
>    In the past several messages, I reported that applying the Adeos
> patch on the BeagleBoard caused some failures that may be related to IRQ
> 384 interrupts (SD card detect). I now believe that I misread the output
> and that all my reports should reference IRQ 378 rather than IRQ 384.
> 
> The twl level 2 interrupt handler is used for both of these IRQs, so it
> could still be that source of the boot hangs.
> 
> Excerpts from the console logs are shown below.
> 
> It is still suspicious that IRQ 378 interrupts are present in kernels
> where the Adeos patch hangs and not present where it is successful.
> However, since the hang seems to be related to the remounting of the SD
> card (mmc0) as the root file system and IRQ 378 seems to be unrelated to
> this action, the suspicion is weak.
> 
> Regards,
> Bob Feretich
> 
> 2.6.31 without Adeos patch (below); hangs with Adeos patch
> cat /proc/interrupts
>            CPU0
>   7:          2        INTC  TWL4030-PIH
>  11:          0        INTC  prcm
>  12:       1011        INTC  DMA
>  56:        313        INTC  i2c_omap
>  61:          0        INTC  i2c_omap
>  72:          1        INTC  serial idle
>  73:          1        INTC  serial idle
>  74:        107        INTC  serial idle, serial
>  77:          0        INTC  ehci_hcd:usb1
>  83:       1414        INTC  mmc0
>  92:          1        INTC  musb_hdrc
>  93:          0        INTC  musb_hdrc
>  95:       1921        INTC  gp timer
> 378:          2     twl4030  twl4030_usb
> 379:          0     twl4030  rtc0
> 384:          0     twl4030  mmc0
> Err:          0
> 
> 2.6.32 without Adeos patch (below): no Adeos patch available
> cat /proc/interrupts
>            CPU0
>   7:          2        INTC  TWL4030-PIH
>  11:          0        INTC  prcm
>  12:       1001        INTC  DMA
>  56:        304        INTC  i2c_omap
>  61:          0        INTC  i2c_omap
>  72:          1        INTC  serial idle
>  73:          1        INTC  serial idle
>  74:        109        INTC  serial idle, serial
>  83:       1794        INTC  mmc0
>  92:          1        INTC  musb_hdrc
>  93:          0        INTC  musb_hdrc
>  95:       2382        INTC  gp timer
> 167:          0        GPIO  user
> 376:          0     twl4030  twl4030_pwrbutton
> 378:          2     twl4030  twl4030_usb
> 384:          0     twl4030  mmc0
> Err:          0
> 
> 2.6.33 without Adeos patch (below):
> cat /proc/interrupts
>            CPU0
>   7:          0        INTC  TWL4030-PIH
>  11:          0        INTC  prcm
>  12:       1037        INTC  DMA
>  37:        773        INTC  gp timer
>  56:        318        INTC  i2c_omap
>  61:          0        INTC  i2c_omap
>  72:          1        INTC  serial idle
>  73:          1        INTC  serial idle
>  74:        115        INTC  serial idle, serial
>  77:          0        INTC  ehci_hcd:usb1
>  83:      14790        INTC  mmc0
>  92:          0        INTC  musb_hdrc
>  93:          0        INTC  musb_hdrc
> 378:          0     twl4030  twl4030_usb
> 379:          0     twl4030  rtc0
> 384:          0     twl4030  mmc0
> Err:          0
> 
> 2.6.33 with Adeos patch (below);
> cat /proc/interrupts 
>            CPU0
>   7:          0        INTC  TWL4030-PIH
>  11:          0        INTC  prcm
>  12:       1288        INTC  DMA
>  37:       1366        INTC  gp timer
>  56:        446        INTC  i2c_omap
>  61:          0        INTC  i2c_omap
>  72:          1        INTC  serial idle
>  73:          1        INTC  serial idle
>  74:        283        INTC  serial idle, serial
>  77:          0        INTC  ehci_hcd:usb1
>  83:       2312        INTC  mmc0
>  92:          0        INTC  musb_hdrc
>  93:          0        INTC  musb_hdrc
> 378:          0     twl4030  twl4030_usb
> 379:          0     twl4030  rtc0
> 384:          0     twl4030  mmc0
> Err:          0
> root@domain.hid:~# cat /proc/xenomai/irq 
> IRQ         CPU0
>  37:        1376         [timer]
> 418:           0         [virtual]

As I said, the absence of IRQ 378 in 2.6.33 looks like a regression,
which should be easy to find with git bisect. Then when you know the
commit which caused the regression, tell me, I will revert it on 2.6.33,
so that I can reproduce the bug you are facing on my board, and
hopefully what happens with the Adeos patch.

> 
> 
> On 7/21/2010 4:30 PM, Bob Feretich wrote:
>> When I boot the vanilla 2.6.32 omap kernel and mount the SD-card as
>> the root file system no interrupts occur on IRQ 384. So, this change
>> must have occurred in the 2.6.32 release.
>> That *may* mean that the Adeos patch will work  with 2.6.32.
>>
>> Although this kernel did not cause IRQ 384 interrupts, there were two
>> IRQ 378 interrupts from the USB power system. I believe that the IRQ
>> 378 interrupts are handled via I2C by the same kernel task that
>> handles IRQ 384.  If I am guessing correctly, the lack of interrupts
>> on IRQ 384 would permit the kernel to boot even with an Adeos patch
>> applied. The interrupts on IRQ 378 could then be checked to see if
>> they were handled by the I2C interrupt handler. This Level2 2
>> interrupt handler task should be invoked by the IRQ 7 interrupts, read
>> the twl chip, and post interrupts to IRQ 378. If something is wrong,
>> then the IRQ 378 counter won't reflect the IRQ 7 count.
>>
>> How difficult is it to port enough of the Adeos patch to 2.6.32 to
>> permit booting with Xenomai disabled?
>>
>> I will examine the 2.6.32 kernel development logs for entries related
>> to this change.
>>
>> Regards,
>> Bob Feretich
>>
>> Console log follows...
>> Texas Instruments X-Loader 1.4.2 (Feb 19 2009 - 12:01:24)
>> Reading boot sector
>> Loading u-boot.bin from mmc
>>
>>
>> U-Boot 2009.06-rc2 (Nov 02 2009 - 23:57:20)
>>
>> OMAP3530-GP ES3.0, CPU-OPP2 L3-165MHz
>> OMAP3 Beagle board + LPDDR/NAND
>> DRAM:  256 MB
>> NAND:  256 MiB
>> In:    serial
>> Out:   serial
>> Err:   serial
>> Board revision C
>> Die ID #317000030000000004013f8a1701a01b
>> Hit any key to stop autoboot:  0
>> mmc1 is available
>> reading uImage
>>
>> 2659320 bytes read
>> ## Booting kernel from Legacy Image at 80300000 ...
>>    Image Name:   Angstrom/2.6.32/beagleboard
>>    Image Type:   ARM Linux Kernel Image (uncompressed)
>>    Data Size:    2659256 Bytes =  2.5 MB
>>    Load Address: 80008000
>>    Entry Point:  80008000
>>    Verifying Checksum ... OK
>>    Loading Kernel Image ... OK
>> OK
>>
>> Starting kernel ...
>>
>> Uncompressing
>> Linux....................................................................................................
>> .........................................................................
>> done, booting the kernel.
>> [    0.000000] Linux version 2.6.32 (Bob@domain.hid
>> <mailto:Bob@domain.hid>) (gcc version 4.3.3 (GCC) ) #1 PREEMPT Wed
>> Jul 21 14:15:03 PDT 20
>> 10
>> [    0.000000] CPU: ARMv7 Processor [411fc083] revision 3 (ARMv7),
>> cr=10c53c7f
>> [    0.000000] CPU: VIPT nonaliasing data cache, VIPT nonaliasing
>> instruction cache
>> [    0.000000] Machine: OMAP3 Beagle Board
>> [    0.000000] Memory policy: ECC disabled, Data cache writeback
>> [    0.000000] OMAP3430/3530 ES3.0 (l2cache iva sgx neon isp )
>> [    0.000000] SRAM: Mapped pa 0x40200000 to va 0xfe400000 size: 0x100000
>> [    0.000000] Built 1 zonelists in Zone order, mobility grouping on. 
>> Total pages: 65024
>> [    0.000000] Kernel command line: console=ttyS2,115200n8
>> root=/dev/mmcblk0p2 rw rootfstype=ext3 rootwait
>> [    0.000000] PID hash table entries: 1024 (order: 0, 4096 bytes)
>> [    0.000000] Dentry cache hash table entries: 32768 (order: 5,
>> 131072 bytes)
>> [    0.000000] Inode-cache hash table entries: 16384 (order: 4, 65536
>> bytes)
>> [    0.000000] Memory: 128MB 128MB = 256MB total
>> [    0.000000] Memory: 253952KB available (4860K code, 559K data, 164K
>> init, 0K highmem)
>> [    0.000000] Hierarchical RCU implementation.
>> [    0.000000] NR_IRQS:402
>> [    0.000000] Clocking rate (Crystal/Core/MPU): 26.0/332/500 MHz
>> [    0.000000] Reprogramming SDRC clock to 332000000 Hz
>> [    0.000000] GPMC revision 5.0
>> [    0.000000] IRQ: Found an INTC at 0xfa200000 (revision 4.0) with 96
>> interrupts
>> [    0.000000] Total of 96 interrupts on 1 active controller
>> [    0.000000] OMAP GPIO hardware version 2.5
>> [    0.000000] OMAP clockevent source: GPTIMER12 at 32768 Hz
>> [    0.000000] Console: colour dummy device 80x30
>> [    0.000000] Calibrating delay loop... 480.01 BogoMIPS (lpj=1875968)
>> [    0.000000] Mount-cache hash table entries: 512
>> [    0.000000] CPU: Testing write buffer coherency: ok
>> [    0.000000] devtmpfs: initialized
>> [    0.000000] regulator: core version 0.5
>> [    0.000000] NET: Registered protocol family 16
>> [    0.000000] Found NAND on CS0
>> [    0.000000] Registering NAND on CS0
>> [   18.373596] OMAP DMA hardware revision 4.0
>> [   18.379821] bio: create slab <bio-0> at 0
>> [   18.381439] SCSI subsystem initialized
>> [   18.382171] usbcore: registered new interface driver usbfs
>> [   18.382354] usbcore: registered new interface driver hub
>> [   18.382568] usbcore: registered new device driver usb
>> [   18.383026] i2c_omap i2c_omap.1: bus 1 rev3.12 at 2600 kHz
>> [   18.386108] twl4030: PIH (irq 7) chaining IRQs 368..375
>> [   18.386138] twl4030: power (irq 373) chaining IRQs 376..383
>> [   18.386505] twl4030: gpio (irq 368) chaining IRQs 384..401
>> [   18.387969] regulator: VUSB1V5: 1500 mV normal standby
>> [   18.388305] regulator: VUSB1V8: 1800 mV normal standby
>> [   18.388671] regulator: VUSB3V1: 3100 mV normal standby
>> [   18.390106] twl4030_usb twl4030_usb: Initialized TWL4030 USB module
>> [   18.390563] regulator: VMMC1: 1850 <--> 3150 mV normal standby
>> [   18.390869] regulator: VDAC: 1800 mV normal standby
>> [   18.391204] regulator: VPLL2: 1800 mV normal standby
>> [   18.391510] regulator: VSIM: 1800 <--> 3000 mV normal standby
>> [   18.403625] i2c_omap i2c_omap.3: bus 3 rev3.12 at 100 kHz
>> [   18.404998] Switching to clocksource 32k_counter
>> [   18.416595] musb_hdrc: version 6.0, musb-dma, otg
>> (peripheral+host), debug=0
>> [   18.420166] musb_hdrc: USB OTG mode controller at fa0ab000 using
>> DMA, IRQ 92
>> [   18.420898] NET: Registered protocol family 2
>> [   18.421173] IP route cache hash table entries: 2048 (order: 1, 8192
>> bytes)
>> [   18.421844] TCP established hash table entries: 8192 (order: 4,
>> 65536 bytes)
>> [   18.422088] TCP bind hash table entries: 8192 (order: 3, 32768 bytes)
>> [   18.422241] TCP: Hash tables configured (established 8192 bind 8192)
>> [   18.422271] TCP reno registered
>> [   18.422546] NET: Registered protocol family 1
>> [   18.423095] RPC: Registered udp transport module.
>> [   18.423095] RPC: Registered tcp transport module.
>> [   18.423126] RPC: Registered tcp NFSv4.1 backchannel transport module.
>> [   18.425628] VFS: Disk quotas dquot_6.5.2
>> [   18.425750] Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
>> [   18.427154] squashfs: version 4.0 (2009/01/31) Phillip Lougher
>> [   18.428161] JFFS2 version 2.2. (NAND) (SUMMARY)  �ݩ 2001-2006
>> Red Hat, Inc.
>> [   18.429351] msgmni has been set to 496
>> [   18.434722] alg: No test for stdrng (krng)
>> [   18.435089] Block layer SCSI generic (bsg) driver version 0.4
>> loaded (major 254)
>> [   18.435119] io scheduler noop registered
>> [   18.435150] io scheduler anticipatory registered
>> [   18.435150] io scheduler deadline registered
>> [   18.435333] io scheduler cfq registered (default)
>> [   18.447570] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
>> [   18.468475] serial8250.0: ttyS0 at MMIO 0x4806a000 (irq = 72) is a
>> ST16654
>> [   18.488403] serial8250.1: ttyS1 at MMIO 0x4806c000 (irq = 73) is a
>> ST16654
>> [   18.508300] serial8250.2: ttyS2 at MMIO 0x49020000 (irq = 74) is a
>> ST16654
>> [   18.940307] console [ttyS2] enabled
>> [   18.952697] brd: module loaded
>> [   18.960174] loop: module loaded
>> [   18.964416] omap2-nand driver initializing
>> [   18.968963] NAND device: Manufacturer ID: 0x2c, Chip ID: 0xba
>> (Micron NAND 256MiB 1,8V 16-bit)
>> [   18.978149] cmdlinepart partition parsing not available
>> [   18.983489] Creating 5 MTD partitions on "omap2-nand":
>> [   18.988677] 0x000000000000-0x000000080000 : "X-Loader"
>> [   18.995330] 0x000000080000-0x000000260000 : "U-Boot"
>> [   19.002105] 0x000000260000-0x000000280000 : "U-Boot Env"
>> [   19.008514] 0x000000280000-0x000000680000 : "Kernel"
>> [   19.016113] 0x000000680000-0x000010000000 : "File System"
>> [   19.124450] usbcore: registered new interface driver catc
>> [   19.129882] catc: v2.8:CATC EL1210A NetMate USB Ethernet driver
>> [   19.135955] usbcore: registered new interface driver kaweth
>> [   19.141632] pegasus: v0.6.14 (2006/09/27), Pegasus/Pegasus II USB
>> Ethernet driver
>> [   19.149261] usbcore: registered new interface driver pegasus
>> [   19.154998] rtl8150: v0.6.2 (2004/08/27):rtl8150 based usb-ethernet
>> driver
>> [   19.162048] usbcore: registered new interface driver rtl8150
>> [   19.167846] usbcore: registered new interface driver asix
>> [   19.173400] usbcore: registered new interface driver cdc_ether
>> [   19.179412] usbcore: registered new interface driver dm9601
>> [   19.185119] usbcore: registered new interface driver smsc95xx
>> [   19.191040] usbcore: registered new interface driver gl620a
>> [   19.196777] usbcore: registered new interface driver net1080
>> [   19.202575] usbcore: registered new interface driver plusb
>> [   19.208190] usbcore: registered new interface driver rndis_host
>> [   19.214263] usbcore: registered new interface driver cdc_subset
>> [   19.220367] usbcore: registered new interface driver zaurus
>> [   19.226104] usbcore: registered new interface driver MOSCHIP
>> usb-ethernet driver
>> [   19.234161] Initializing USB Mass Storage driver...
>> [   19.239196] usbcore: registered new interface driver usb-storage
>> [   19.245330] USB Mass Storage support registered.
>> [   19.250061] g_ether gadget: using random self ethernet address
>> [   19.255950] g_ether gadget: using random host ethernet address
>> [   19.262390] usb0: MAC 76:ff:8e:a3:38:74
>> [   19.266326] usb0: HOST MAC 92:e6:7c:a6:1a:38
>> [   19.270660] g_ether gadget: Ethernet Gadget, version: Memorial Day 2008
>> [   19.277374] g_ether gadget: g_ether ready
>> [   19.281433] musb_hdrc musb_hdrc: MUSB HDRC host driver
>> [   19.287078] musb_hdrc musb_hdrc: new USB bus registered, assigned
>> bus number 1
>> [   19.294555] usb usb1: New USB device found, idVendor=1d6b,
>> idProduct=0002
>> [   19.301422] usb usb1: New USB device strings: Mfr=3, Product=2,
>> SerialNumber=1
>> [   19.308715] usb usb1: Product: MUSB HDRC host driver
>> [   19.313751] usb usb1: Manufacturer: Linux 2.6.32 musb-hcd
>> [   19.319213] usb usb1: SerialNumber: musb_hdrc
>> [   19.324157] usb usb1: configuration #1 chosen from 1 choice
>> [   19.330078] hub 1-0:1.0: USB hub found
>> [   19.333953] hub 1-0:1.0: 1 port detected
>> [   19.338867] mice: PS/2 mouse device common for all mice
>> [   19.344665] input: gpio-keys as
>> /devices/platform/gpio-keys/input/input0
>> [   19.352996] input: twl4030_pwrbutton as
>> /devices/platform/i2c_omap.1/i2c-1/1-0049/twl4030_pwrbutton/input/input1
>> [   19.363922] i2c /dev entries driver
>> [   19.475860] Registered led device: beagleboard::usr0
>> [   19.481018] Registered led device: beagleboard::usr1
>> [   19.486724] Registered led device: beagleboard::pmu_stat
>> [   19.492309] oprofile: using arm/armv7
>> [   19.496276] TCP cubic registered
>> [   19.499603] NET: Registered protocol family 17
>> [   19.504119] NET: Registered protocol family 15
>> [   19.508728] ThumbEE CPU extension supported.
>> [   19.513031] Power Management for TI OMAP3.
>> [   19.528015] VFP support v0.3: implementor 41 architecture 3 part 30
>> variant c rev 1
>> [   19.536712] registered taskstats version 1
>> [   19.542541] regulator_init_complete: incomplete constraints,
>> leaving VDVI on
>> [   19.549804] regulator_init_complete: incomplete constraints,
>> leaving VDAC on
>> [   19.557556] Waiting for root device /dev/mmcblk0p2...
>> [   19.842773] mmc0: new high speed SDHC card at address cd63
>> [   19.848846] mmcblk0: mmc0:cd63 SD04G 3.69 GiB
>> [   19.853790]  mmcblk0: p1 p2
>> [   19.896240] kjournald starting.  Commit interval 5 seconds
>> [   20.155639] EXT3 FS on mmcblk0p2, internal journal
>> [   20.160491] EXT3-fs: mounted filesystem with writeback data mode.
>> [   20.166717] VFS: Mounted root (ext3 filesystem) on device 179:2.
>> [   20.175598] devtmpfs: mounted
>> [   20.178741] Freeing init memory: 164K
>> INIT: version 2.86 booting
>> Please wait: booting...
>> Starting udev
>> Remounting root file system...
>> Caching udev devnodes
>> Populating dev cache
>> root: mount: mounting rootfs on / failed: No such file or directory
>> Configuring network interfaces... ifconfig: SIOCGIFFLAGS: No such device
>> done.
>> Setting up IP spoofing protection: rp_filter.
>> hwclock: can't open '/dev/misc/rtc': No such file or directory
>> Tue May 18 20:58:00 UTC 2010
>> hwclock: can't open '/dev/misc/rtc': No such file or directory
>> Configuring update-modules.
>> Starting to configure packages...
>> Nothing to be done
>> Finished to configure packages.
>> INIT: Entering runlevel: 5
>> Creating Dropbear SSH server RSA host key.
>> Will output 1024 bit rsa secret key to
>> '/etc/dropbear/dropbear_rsa_host_key'
>> Generating key, this may take a while...
>> Public key portion is:
>> ssh-rsa
>> AAAAB3NzaC1yc2EAAAADAQABAAAAgwCFnP91SQbJJLLS7KMeQYYjBm2KLETrqGJtmHxTotPEBJi8cgFBkW2ZBk8mgz+u92kJOkKmk/UJtV/gkXo
>> sibLr41W2CJyf6ILPujqZk0RvGxybuW5dp18C2rP9uW3vPhQ4GDrXG3s5i7r/s5hvgWtY8QDXcYVLtZUsx6B/fufK+aaT
>> root@domain.hid
>> Fingerprint: md5 59:56:33:4a:a7:8f:ba:e6:33:43:2d:d1:3d:a6:83:1e
>> Starting Dropbear SSH server: dropbear.
>> Starting syslogd/klogd: done
>>
>> .-------.                                          
>> |       |                  .-.                     
>> |   |   |-----.-----.-----.| |   .----..-----.-----.
>> |       |     | __  |  ---'| '--.|  .-'|     |     |
>> |   |   |  |  |     |---  ||  --'|  |  |  '  | | | |
>> '---'---'--'--'--.  |-----''----''--'  '-----'-'-'-'
>>                 -'  |
>>                 '---'
>>
>> The Angstrom Distribution beagleboard ttyS2
>>
>> Angstrom 2010.4-test-20100518 beagleboard ttyS2
>>
>> beagleboard login: root
>> root@domain.hid:~# cat /proc/interrupts
>>            CPU0
>>   7:          2        INTC  TWL4030-PIH
>>  11:          0        INTC  prcm
>>  12:       1114        INTC  DMA
>>  56:        304        INTC  i2c_omap
>>  61:          0        INTC  i2c_omap
>>  72:          1        INTC  serial idle
>>  73:          1        INTC  serial idle
>>  74:        201        INTC  serial idle, serial
>>  83:       1976        INTC  mmc0
>>  92:          1        INTC  musb_hdrc
>>  93:          0        INTC  musb_hdrc
>>  95:       3266        INTC  gp timer
>> 167:          0        GPIO  user
>> 376:          0     twl4030  twl4030_pwrbutton
>> 378:          2     twl4030  twl4030_usb
>> 384:          0     twl4030  mmc0
>> Err:          0
>> root@domain.hid:~#



>>
>> On 7/21/2010 1:33 PM, Bob Feretich wrote:
>>> I reverted the patch that you suggested. Spurious interrupts crashed
>>> the kernel during boot. (console log below)
>>>
>>> The only data that I have to go on for the difference between the
>>> Adeos hang on 2.6.31 and successful boot on 2.6.33 is interrupts on
>>> IRQ 384, which occur on 2.6.31 but not 2.6.33.
>>> This change in interrupts is independent of the Adeos patch, so I
>>> will build a vanilla 2.6.32 kernel and see if the interrupts occur
>>> there. This may help isolate which kernel change made the difference.
>>>
>>> Regards,
>>> Bob Feretich
>>>
>>> Boot log with 2.6.31 patch reverted...
>>> Texas Instruments X-Loader 1.4.2 (Feb 19 2009 - 12:01:24)
>>> Reading boot sector
>>> ... snipped ...


-- 
					    Gilles.

Re: [Xenomai-help] Adeos patched kernel hangs mounting root file system - correction

[Bob Feretich]

  Even bisecting I'd probably be looking at over 10 iterations.

First I think I will try to mount a tmpfs as root instead of the SD card.
Many changes went into the 2.6.33 hsmmc driver. Mounting a tmpfs as root 
would bypass all of these.

Mounting the SD card as root was supposed to be an expediency.
My final system will use a tmpfs as root anyway, so the time won't be 
wasted.

Eventually, I'll need to mount a file system on the SD card, but it 
won't be the root file system.

Thanks,
Bob Feretich

On 7/22/2010 3:14 PM, Gilles Chanteperdrix wrote:
> Bob Feretich wrote:
>>     In the past several messages, I reported that applying the Adeos
>> patch on the BeagleBoard caused some failures that may be related to IRQ
>> 384 interrupts (SD card detect). I now believe that I misread the output
>> and that all my reports should reference IRQ 378 rather than IRQ 384.
>>
>> The twl level 2 interrupt handler is used for both of these IRQs, so it
>> could still be that source of the boot hangs.
>>
>> Excerpts from the console logs are shown below.
>>
>> It is still suspicious that IRQ 378 interrupts are present in kernels
>> where the Adeos patch hangs and not present where it is successful.
>> However, since the hang seems to be related to the remounting of the SD
>> card (mmc0) as the root file system and IRQ 378 seems to be unrelated to
>> this action, the suspicion is weak.
>>
>> Regards,
>> Bob Feretich
>>
>> 2.6.31 without Adeos patch (below); hangs with Adeos patch
>> cat /proc/interrupts
>>             CPU0
>>    7:          2        INTC  TWL4030-PIH
>>   11:          0        INTC  prcm
>>   12:       1011        INTC  DMA
>>   56:        313        INTC  i2c_omap
>>   61:          0        INTC  i2c_omap
>>   72:          1        INTC  serial idle
>>   73:          1        INTC  serial idle
>>   74:        107        INTC  serial idle, serial
>>   77:          0        INTC  ehci_hcd:usb1
>>   83:       1414        INTC  mmc0
>>   92:          1        INTC  musb_hdrc
>>   93:          0        INTC  musb_hdrc
>>   95:       1921        INTC  gp timer
>> 378:          2     twl4030  twl4030_usb
>> 379:          0     twl4030  rtc0
>> 384:          0     twl4030  mmc0
>> Err:          0
>>
>> 2.6.32 without Adeos patch (below): no Adeos patch available
>> cat /proc/interrupts
>>             CPU0
>>    7:          2        INTC  TWL4030-PIH
>>   11:          0        INTC  prcm
>>   12:       1001        INTC  DMA
>>   56:        304        INTC  i2c_omap
>>   61:          0        INTC  i2c_omap
>>   72:          1        INTC  serial idle
>>   73:          1        INTC  serial idle
>>   74:        109        INTC  serial idle, serial
>>   83:       1794        INTC  mmc0
>>   92:          1        INTC  musb_hdrc
>>   93:          0        INTC  musb_hdrc
>>   95:       2382        INTC  gp timer
>> 167:          0        GPIO  user
>> 376:          0     twl4030  twl4030_pwrbutton
>> 378:          2     twl4030  twl4030_usb
>> 384:          0     twl4030  mmc0
>> Err:          0
>>
>> 2.6.33 without Adeos patch (below):
>> cat /proc/interrupts
>>             CPU0
>>    7:          0        INTC  TWL4030-PIH
>>   11:          0        INTC  prcm
>>   12:       1037        INTC  DMA
>>   37:        773        INTC  gp timer
>>   56:        318        INTC  i2c_omap
>>   61:          0        INTC  i2c_omap
>>   72:          1        INTC  serial idle
>>   73:          1        INTC  serial idle
>>   74:        115        INTC  serial idle, serial
>>   77:          0        INTC  ehci_hcd:usb1
>>   83:      14790        INTC  mmc0
>>   92:          0        INTC  musb_hdrc
>>   93:          0        INTC  musb_hdrc
>> 378:          0     twl4030  twl4030_usb
>> 379:          0     twl4030  rtc0
>> 384:          0     twl4030  mmc0
>> Err:          0
>>
>> 2.6.33 with Adeos patch (below);
>> cat /proc/interrupts
>>             CPU0
>>    7:          0        INTC  TWL4030-PIH
>>   11:          0        INTC  prcm
>>   12:       1288        INTC  DMA
>>   37:       1366        INTC  gp timer
>>   56:        446        INTC  i2c_omap
>>   61:          0        INTC  i2c_omap
>>   72:          1        INTC  serial idle
>>   73:          1        INTC  serial idle
>>   74:        283        INTC  serial idle, serial
>>   77:          0        INTC  ehci_hcd:usb1
>>   83:       2312        INTC  mmc0
>>   92:          0        INTC  musb_hdrc
>>   93:          0        INTC  musb_hdrc
>> 378:          0     twl4030  twl4030_usb
>> 379:          0     twl4030  rtc0
>> 384:          0     twl4030  mmc0
>> Err:          0
>> root@domain.hid:~# cat /proc/xenomai/irq
>> IRQ         CPU0
>>   37:        1376         [timer]
>> 418:           0         [virtual]
> As I said, the absence of IRQ 378 in 2.6.33 looks like a regression,
> which should be easy to find with git bisect. Then when you know the
> commit which caused the regression, tell me, I will revert it on 2.6.33,
> so that I can reproduce the bug you are facing on my board, and
> hopefully what happens with the Adeos patch.
>
>>
>> On 7/21/2010 4:30 PM, Bob Feretich wrote:
>>> When I boot the vanilla 2.6.32 omap kernel and mount the SD-card as
>>> the root file system no interrupts occur on IRQ 384. So, this change
>>> must have occurred in the 2.6.32 release.
>>> That *may* mean that the Adeos patch will work  with 2.6.32.
>>>
>>> Although this kernel did not cause IRQ 384 interrupts, there were two
>>> IRQ 378 interrupts from the USB power system. I believe that the IRQ
>>> 378 interrupts are handled via I2C by the same kernel task that
>>> handles IRQ 384.  If I am guessing correctly, the lack of interrupts
>>> on IRQ 384 would permit the kernel to boot even with an Adeos patch
>>> applied. The interrupts on IRQ 378 could then be checked to see if
>>> they were handled by the I2C interrupt handler. This Level2 2
>>> interrupt handler task should be invoked by the IRQ 7 interrupts, read
>>> the twl chip, and post interrupts to IRQ 378. If something is wrong,
>>> then the IRQ 378 counter won't reflect the IRQ 7 count.
>>>
>>> How difficult is it to port enough of the Adeos patch to 2.6.32 to
>>> permit booting with Xenomai disabled?
>>>
>>> I will examine the 2.6.32 kernel development logs for entries related
>>> to this change.
>>>
>>> Regards,
>>> Bob Feretich
>>>
>>> Console log follows...
>>> Texas Instruments X-Loader 1.4.2 (Feb 19 2009 - 12:01:24)
>>> Reading boot sector
>>> Loading u-boot.bin from mmc
>>>
>>>
>>> U-Boot 2009.06-rc2 (Nov 02 2009 - 23:57:20)
>>>
>>> OMAP3530-GP ES3.0, CPU-OPP2 L3-165MHz
>>> OMAP3 Beagle board + LPDDR/NAND
>>> DRAM:  256 MB
>>> NAND:  256 MiB
>>> In:    serial
>>> Out:   serial
>>> Err:   serial
>>> Board revision C
>>> Die ID #317000030000000004013f8a1701a01b
>>> Hit any key to stop autoboot:  0
>>> mmc1 is available
>>> reading uImage
>>>
>>> 2659320 bytes read
>>> ## Booting kernel from Legacy Image at 80300000 ...
>>>     Image Name:   Angstrom/2.6.32/beagleboard
>>>     Image Type:   ARM Linux Kernel Image (uncompressed)
>>>     Data Size:    2659256 Bytes =  2.5 MB
>>>     Load Address: 80008000
>>>     Entry Point:  80008000
>>>     Verifying Checksum ... OK
>>>     Loading Kernel Image ... OK
>>> OK
>>>
>>> Starting kernel ...
>>>
>>> Uncompressing
>>> Linux....................................................................................................
>>> .........................................................................
>>> done, booting the kernel.
>>> [    0.000000] Linux version 2.6.32 (Bob@domain.hid
>>> <mailto:Bob@domain.hid>) (gcc version 4.3.3 (GCC) ) #1 PREEMPT Wed
>>> Jul 21 14:15:03 PDT 20
>>> 10
>>> [    0.000000] CPU: ARMv7 Processor [411fc083] revision 3 (ARMv7),
>>> cr=10c53c7f
>>> [    0.000000] CPU: VIPT nonaliasing data cache, VIPT nonaliasing
>>> instruction cache
>>> [    0.000000] Machine: OMAP3 Beagle Board
>>> [    0.000000] Memory policy: ECC disabled, Data cache writeback
>>> [    0.000000] OMAP3430/3530 ES3.0 (l2cache iva sgx neon isp )
>>> [    0.000000] SRAM: Mapped pa 0x40200000 to va 0xfe400000 size: 0x100000
>>> [    0.000000] Built 1 zonelists in Zone order, mobility grouping on.
>>> Total pages: 65024
>>> [    0.000000] Kernel command line: console=ttyS2,115200n8
>>> root=/dev/mmcblk0p2 rw rootfstype=ext3 rootwait
>>> [    0.000000] PID hash table entries: 1024 (order: 0, 4096 bytes)
>>> [    0.000000] Dentry cache hash table entries: 32768 (order: 5,
>>> 131072 bytes)
>>> [    0.000000] Inode-cache hash table entries: 16384 (order: 4, 65536
>>> bytes)
>>> [    0.000000] Memory: 128MB 128MB = 256MB total
>>> [    0.000000] Memory: 253952KB available (4860K code, 559K data, 164K
>>> init, 0K highmem)
>>> [    0.000000] Hierarchical RCU implementation.
>>> [    0.000000] NR_IRQS:402
>>> [    0.000000] Clocking rate (Crystal/Core/MPU): 26.0/332/500 MHz
>>> [    0.000000] Reprogramming SDRC clock to 332000000 Hz
>>> [    0.000000] GPMC revision 5.0
>>> [    0.000000] IRQ: Found an INTC at 0xfa200000 (revision 4.0) with 96
>>> interrupts
>>> [    0.000000] Total of 96 interrupts on 1 active controller
>>> [    0.000000] OMAP GPIO hardware version 2.5
>>> [    0.000000] OMAP clockevent source: GPTIMER12 at 32768 Hz
>>> [    0.000000] Console: colour dummy device 80x30
>>> [    0.000000] Calibrating delay loop... 480.01 BogoMIPS (lpj=1875968)
>>> [    0.000000] Mount-cache hash table entries: 512
>>> [    0.000000] CPU: Testing write buffer coherency: ok
>>> [    0.000000] devtmpfs: initialized
>>> [    0.000000] regulator: core version 0.5
>>> [    0.000000] NET: Registered protocol family 16
>>> [    0.000000] Found NAND on CS0
>>> [    0.000000] Registering NAND on CS0
>>> [   18.373596] OMAP DMA hardware revision 4.0
>>> [   18.379821] bio: create slab<bio-0>  at 0
>>> [   18.381439] SCSI subsystem initialized
>>> [   18.382171] usbcore: registered new interface driver usbfs
>>> [   18.382354] usbcore: registered new interface driver hub
>>> [   18.382568] usbcore: registered new device driver usb
>>> [   18.383026] i2c_omap i2c_omap.1: bus 1 rev3.12 at 2600 kHz
>>> [   18.386108] twl4030: PIH (irq 7) chaining IRQs 368..375
>>> [   18.386138] twl4030: power (irq 373) chaining IRQs 376..383
>>> [   18.386505] twl4030: gpio (irq 368) chaining IRQs 384..401
>>> [   18.387969] regulator: VUSB1V5: 1500 mV normal standby
>>> [   18.388305] regulator: VUSB1V8: 1800 mV normal standby
>>> [   18.388671] regulator: VUSB3V1: 3100 mV normal standby
>>> [   18.390106] twl4030_usb twl4030_usb: Initialized TWL4030 USB module
>>> [   18.390563] regulator: VMMC1: 1850<-->  3150 mV normal standby
>>> [   18.390869] regulator: VDAC: 1800 mV normal standby
>>> [   18.391204] regulator: VPLL2: 1800 mV normal standby
>>> [   18.391510] regulator: VSIM: 1800<-->  3000 mV normal standby
>>> [   18.403625] i2c_omap i2c_omap.3: bus 3 rev3.12 at 100 kHz
>>> [   18.404998] Switching to clocksource 32k_counter
>>> [   18.416595] musb_hdrc: version 6.0, musb-dma, otg
>>> (peripheral+host), debug=0
>>> [   18.420166] musb_hdrc: USB OTG mode controller at fa0ab000 using
>>> DMA, IRQ 92
>>> [   18.420898] NET: Registered protocol family 2
>>> [   18.421173] IP route cache hash table entries: 2048 (order: 1, 8192
>>> bytes)
>>> [   18.421844] TCP established hash table entries: 8192 (order: 4,
>>> 65536 bytes)
>>> [   18.422088] TCP bind hash table entries: 8192 (order: 3, 32768 bytes)
>>> [   18.422241] TCP: Hash tables configured (established 8192 bind 8192)
>>> [   18.422271] TCP reno registered
>>> [   18.422546] NET: Registered protocol family 1
>>> [   18.423095] RPC: Registered udp transport module.
>>> [   18.423095] RPC: Registered tcp transport module.
>>> [   18.423126] RPC: Registered tcp NFSv4.1 backchannel transport module.
>>> [   18.425628] VFS: Disk quotas dquot_6.5.2
>>> [   18.425750] Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
>>> [   18.427154] squashfs: version 4.0 (2009/01/31) Phillip Lougher
>>> [   18.428161] JFFS2 version 2.2. (NAND) (SUMMARY)  �ݩ 2001-2006
>>> Red Hat, Inc.
>>> [   18.429351] msgmni has been set to 496
>>> [   18.434722] alg: No test for stdrng (krng)
>>> [   18.435089] Block layer SCSI generic (bsg) driver version 0.4
>>> loaded (major 254)
>>> [   18.435119] io scheduler noop registered
>>> [   18.435150] io scheduler anticipatory registered
>>> [   18.435150] io scheduler deadline registered
>>> [   18.435333] io scheduler cfq registered (default)
>>> [   18.447570] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
>>> [   18.468475] serial8250.0: ttyS0 at MMIO 0x4806a000 (irq = 72) is a
>>> ST16654
>>> [   18.488403] serial8250.1: ttyS1 at MMIO 0x4806c000 (irq = 73) is a
>>> ST16654
>>> [   18.508300] serial8250.2: ttyS2 at MMIO 0x49020000 (irq = 74) is a
>>> ST16654
>>> [   18.940307] console [ttyS2] enabled
>>> [   18.952697] brd: module loaded
>>> [   18.960174] loop: module loaded
>>> [   18.964416] omap2-nand driver initializing
>>> [   18.968963] NAND device: Manufacturer ID: 0x2c, Chip ID: 0xba
>>> (Micron NAND 256MiB 1,8V 16-bit)
>>> [   18.978149] cmdlinepart partition parsing not available
>>> [   18.983489] Creating 5 MTD partitions on "omap2-nand":
>>> [   18.988677] 0x000000000000-0x000000080000 : "X-Loader"
>>> [   18.995330] 0x000000080000-0x000000260000 : "U-Boot"
>>> [   19.002105] 0x000000260000-0x000000280000 : "U-Boot Env"
>>> [   19.008514] 0x000000280000-0x000000680000 : "Kernel"
>>> [   19.016113] 0x000000680000-0x000010000000 : "File System"
>>> [   19.124450] usbcore: registered new interface driver catc
>>> [   19.129882] catc: v2.8:CATC EL1210A NetMate USB Ethernet driver
>>> [   19.135955] usbcore: registered new interface driver kaweth
>>> [   19.141632] pegasus: v0.6.14 (2006/09/27), Pegasus/Pegasus II USB
>>> Ethernet driver
>>> [   19.149261] usbcore: registered new interface driver pegasus
>>> [   19.154998] rtl8150: v0.6.2 (2004/08/27):rtl8150 based usb-ethernet
>>> driver
>>> [   19.162048] usbcore: registered new interface driver rtl8150
>>> [   19.167846] usbcore: registered new interface driver asix
>>> [   19.173400] usbcore: registered new interface driver cdc_ether
>>> [   19.179412] usbcore: registered new interface driver dm9601
>>> [   19.185119] usbcore: registered new interface driver smsc95xx
>>> [   19.191040] usbcore: registered new interface driver gl620a
>>> [   19.196777] usbcore: registered new interface driver net1080
>>> [   19.202575] usbcore: registered new interface driver plusb
>>> [   19.208190] usbcore: registered new interface driver rndis_host
>>> [   19.214263] usbcore: registered new interface driver cdc_subset
>>> [   19.220367] usbcore: registered new interface driver zaurus
>>> [   19.226104] usbcore: registered new interface driver MOSCHIP
>>> usb-ethernet driver
>>> [   19.234161] Initializing USB Mass Storage driver...
>>> [   19.239196] usbcore: registered new interface driver usb-storage
>>> [   19.245330] USB Mass Storage support registered.
>>> [   19.250061] g_ether gadget: using random self ethernet address
>>> [   19.255950] g_ether gadget: using random host ethernet address
>>> [   19.262390] usb0: MAC 76:ff:8e:a3:38:74
>>> [   19.266326] usb0: HOST MAC 92:e6:7c:a6:1a:38
>>> [   19.270660] g_ether gadget: Ethernet Gadget, version: Memorial Day 2008
>>> [   19.277374] g_ether gadget: g_ether ready
>>> [   19.281433] musb_hdrc musb_hdrc: MUSB HDRC host driver
>>> [   19.287078] musb_hdrc musb_hdrc: new USB bus registered, assigned
>>> bus number 1
>>> [   19.294555] usb usb1: New USB device found, idVendor=1d6b,
>>> idProduct=0002
>>> [   19.301422] usb usb1: New USB device strings: Mfr=3, Product=2,
>>> SerialNumber=1
>>> [   19.308715] usb usb1: Product: MUSB HDRC host driver
>>> [   19.313751] usb usb1: Manufacturer: Linux 2.6.32 musb-hcd
>>> [   19.319213] usb usb1: SerialNumber: musb_hdrc
>>> [   19.324157] usb usb1: configuration #1 chosen from 1 choice
>>> [   19.330078] hub 1-0:1.0: USB hub found
>>> [   19.333953] hub 1-0:1.0: 1 port detected
>>> [   19.338867] mice: PS/2 mouse device common for all mice
>>> [   19.344665] input: gpio-keys as
>>> /devices/platform/gpio-keys/input/input0
>>> [   19.352996] input: twl4030_pwrbutton as
>>> /devices/platform/i2c_omap.1/i2c-1/1-0049/twl4030_pwrbutton/input/input1
>>> [   19.363922] i2c /dev entries driver
>>> [   19.475860] Registered led device: beagleboard::usr0
>>> [   19.481018] Registered led device: beagleboard::usr1
>>> [   19.486724] Registered led device: beagleboard::pmu_stat
>>> [   19.492309] oprofile: using arm/armv7
>>> [   19.496276] TCP cubic registered
>>> [   19.499603] NET: Registered protocol family 17
>>> [   19.504119] NET: Registered protocol family 15
>>> [   19.508728] ThumbEE CPU extension supported.
>>> [   19.513031] Power Management for TI OMAP3.
>>> [   19.528015] VFP support v0.3: implementor 41 architecture 3 part 30
>>> variant c rev 1
>>> [   19.536712] registered taskstats version 1
>>> [   19.542541] regulator_init_complete: incomplete constraints,
>>> leaving VDVI on
>>> [   19.549804] regulator_init_complete: incomplete constraints,
>>> leaving VDAC on
>>> [   19.557556] Waiting for root device /dev/mmcblk0p2...
>>> [   19.842773] mmc0: new high speed SDHC card at address cd63
>>> [   19.848846] mmcblk0: mmc0:cd63 SD04G 3.69 GiB
>>> [   19.853790]  mmcblk0: p1 p2
>>> [   19.896240] kjournald starting.  Commit interval 5 seconds
>>> [   20.155639] EXT3 FS on mmcblk0p2, internal journal
>>> [   20.160491] EXT3-fs: mounted filesystem with writeback data mode.
>>> [   20.166717] VFS: Mounted root (ext3 filesystem) on device 179:2.
>>> [   20.175598] devtmpfs: mounted
>>> [   20.178741] Freeing init memory: 164K
>>> INIT: version 2.86 booting
>>> Please wait: booting...
>>> Starting udev
>>> Remounting root file system...
>>> Caching udev devnodes
>>> Populating dev cache
>>> root: mount: mounting rootfs on / failed: No such file or directory
>>> Configuring network interfaces... ifconfig: SIOCGIFFLAGS: No such device
>>> done.
>>> Setting up IP spoofing protection: rp_filter.
>>> hwclock: can't open '/dev/misc/rtc': No such file or directory
>>> Tue May 18 20:58:00 UTC 2010
>>> hwclock: can't open '/dev/misc/rtc': No such file or directory
>>> Configuring update-modules.
>>> Starting to configure packages...
>>> Nothing to be done
>>> Finished to configure packages.
>>> INIT: Entering runlevel: 5
>>> Creating Dropbear SSH server RSA host key.
>>> Will output 1024 bit rsa secret key to
>>> '/etc/dropbear/dropbear_rsa_host_key'
>>> Generating key, this may take a while...
>>> Public key portion is:
>>> ssh-rsa
>>> AAAAB3NzaC1yc2EAAAADAQABAAAAgwCFnP91SQbJJLLS7KMeQYYjBm2KLETrqGJtmHxTotPEBJi8cgFBkW2ZBk8mgz+u92kJOkKmk/UJtV/gkXo
>>> sibLr41W2CJyf6ILPujqZk0RvGxybuW5dp18C2rP9uW3vPhQ4GDrXG3s5i7r/s5hvgWtY8QDXcYVLtZUsx6B/fufK+aaT
>>> root@domain.hid
>>> Fingerprint: md5 59:56:33:4a:a7:8f:ba:e6:33:43:2d:d1:3d:a6:83:1e
>>> Starting Dropbear SSH server: dropbear.
>>> Starting syslogd/klogd: done
>>>
>>> .-------.
>>> |       |                  .-.
>>> |   |   |-----.-----.-----.| |   .----..-----.-----.
>>> |       |     | __  |  ---'| '--.|  .-'|     |     |
>>> |   |   |  |  |     |---  ||  --'|  |  |  '  | | | |
>>> '---'---'--'--'--.  |-----''----''--'  '-----'-'-'-'
>>>                  -'  |
>>>                  '---'
>>>
>>> The Angstrom Distribution beagleboard ttyS2
>>>
>>> Angstrom 2010.4-test-20100518 beagleboard ttyS2
>>>
>>> beagleboard login: root
>>> root@domain.hid:~# cat /proc/interrupts
>>>             CPU0
>>>    7:          2        INTC  TWL4030-PIH
>>>   11:          0        INTC  prcm
>>>   12:       1114        INTC  DMA
>>>   56:        304        INTC  i2c_omap
>>>   61:          0        INTC  i2c_omap
>>>   72:          1        INTC  serial idle
>>>   73:          1        INTC  serial idle
>>>   74:        201        INTC  serial idle, serial
>>>   83:       1976        INTC  mmc0
>>>   92:          1        INTC  musb_hdrc
>>>   93:          0        INTC  musb_hdrc
>>>   95:       3266        INTC  gp timer
>>> 167:          0        GPIO  user
>>> 376:          0     twl4030  twl4030_pwrbutton
>>> 378:          2     twl4030  twl4030_usb
>>> 384:          0     twl4030  mmc0
>>> Err:          0
>>> root@domain.hid:~#
>
>
>>> On 7/21/2010 1:33 PM, Bob Feretich wrote:
>>>> I reverted the patch that you suggested. Spurious interrupts crashed
>>>> the kernel during boot. (console log below)
>>>>
>>>> The only data that I have to go on for the difference between the
>>>> Adeos hang on 2.6.31 and successful boot on 2.6.33 is interrupts on
>>>> IRQ 384, which occur on 2.6.31 but not 2.6.33.
>>>> This change in interrupts is independent of the Adeos patch, so I
>>>> will build a vanilla 2.6.32 kernel and see if the interrupts occur
>>>> there. This may help isolate which kernel change made the difference.
>>>>
>>>> Regards,
>>>> Bob Feretich
>>>>
>>>> Boot log with 2.6.31 patch reverted...
>>>> Texas Instruments X-Loader 1.4.2 (Feb 19 2009 - 12:01:24)
>>>> Reading boot sector
>>>> ... snipped ...
>

Re: [Xenomai-help] Adeos patched kernel hangs mounting root file system - correction

[Gilles Chanteperdrix]

Bob Feretich wrote:
>   Even bisecting I'd probably be looking at over 10 iterations.

So ? Every iteration takes about 2 minutes to compile, 2 minutes to
test, that is 20 minutes.

-- 
					    Gilles.

Re: [Xenomai-help] Adeos patched kernel hangs mounting root file system - correction

[Bob Feretich]

  I guess that I need to buy a new build server. My turn around time on 
a new kernel is about 2 hours. (1.1 GHz Athelon 1.5 GB RAM 1-core)
It's fine for compiling my applications and drivers. I hadn't planned on 
building multiple kernels per day.

Regards,
Bob

On 7/22/2010 4:35 PM, Gilles Chanteperdrix wrote:
> Bob Feretich wrote:
>>    Even bisecting I'd probably be looking at over 10 iterations.
> So ? Every iteration takes about 2 minutes to compile, 2 minutes to
> test, that is 20 minutes.
>

Re: [Xenomai-help] Adeos patched kernel hangs mounting root file system - correction

[Gilles Chanteperdrix]

Bob Feretich wrote:
>   I guess that I need to buy a new build server. My turn around time on 
> a new kernel is about 2 hours. (1.1 GHz Athelon 1.5 GB RAM 1-core)
> It's fine for compiling my applications and drivers. I hadn't planned on 
> building multiple kernels per day.

That is because you restart building the kernel from scratch every time.
If, on the other hand, you only re-run make in the kernel build-tree
after having changed a few files in the source tree under git control,
the kernel build system will only re-build those files which have
changed. And I guess you mean an x86 kernel, because an ARM kernel
usually has far less options than an x86 kernel and is really fast to
compile.

If you want to be able to debug Linux kernel issues, you can not keep a
turn around time of 2 hours.

-- 
					    Gilles.

Re: [Xenomai-help] Adeos patch prevents IRQ 384 (MMC Chip Detect) on omap-2.6.33

[Bob Feretich]

[-- Attachment #1: Type: text/plain, Size: 6468 bytes --]

  I have started a new thread with a name that better describes the 
failure I am seeing. This may or may not be the reason I was seeing root 
file system mount hang on omap-2.6.31 (previous thread).

The SD card/MMC  "Chip Detect" interrupt (activated when a SD card is 
inserted or removed) can't be tested when the root file system is on the 
SD card. So I rebuilt my 2.6.33 BeagleBoard system to mount the root 
file system via NFS. Now the  failure of Xenomai to handle twl4030 
interrupts can be identified and isolated.

2.6.33 without the Adeos patch...
The Angstrom Distribution beagleboard ttyS2

Angstrom 2010.4-test-20100518 beagleboard ttyS2

beagleboard login: root
root@domain.hid:~# cat /proc/interrupts
            CPU0
   7:          2        INTC  TWL4030-PIH
  12:        203        INTC  DMA
  37:       1219        INTC  gp timer
  56:        368        INTC  i2c_omap
  61:          0        INTC  i2c_omap
  74:        125        INTC  serial
  77:      10694        INTC  ehci_hcd:usb2
  83:        106        INTC  mmc0
  92:          1        INTC  musb_hdrc
  93:          0        INTC  musb_hdrc
378:          2     twl4030  twl4030_usb
379:          0     twl4030  rtc0
384:          0     twl4030  mmc0
Err:          0
root@domain.hid:~# ls /dev
block               ram6                tty39
... snipped ...
mem                 tty2                tty58
mmcblk0             tty20               tty59
mmcblk0p1           tty21               tty6
mmcblk0p2           tty22               tty60
network_latency     tty23               tty61
... snipped ...
root@domain.hid:~# umount /dev/mmcblk0p1
root@domain.hid:~# umount /dev/mmcblk0p2

****** I removed the SD card here ****************************

root@domain.hid:~# [  122.126495] mmc0: card 0007 removed
root@domain.hid:~# ls /dev
block               ram9                tty40
... snipped ...
mem                 tty21               tty59 <=== mmc entries are gone
network_latency     tty22               tty6
... snipped ...
root@domain.hid:~# cat /proc/interrupts
            CPU0
   7:          3        INTC  TWL4030-PIH
  12:        208        INTC  DMA
  37:       2477        INTC  gp timer
  56:        388        INTC  i2c_omap
  61:          0        INTC  i2c_omap
  74:        437        INTC  serial
  77:      12374        INTC  ehci_hcd:usb2
  83:        135        INTC  mmc0
  92:          1        INTC  musb_hdrc
  93:          0        INTC  musb_hdrc
378:          2     twl4030  twl4030_usb
379:          0     twl4030  rtc0
384:          1     twl4030  mmc0 <===== notice the Chip Detect irpt
Err:          0

****** I reinserted the SD card here ****************************

root@domain.hid:~# [  270.691955] mmc0: new high speed SD card at 
address 0007
[  270.699981] mmcblk0: mmc0:0007 SD01G 972 MiB
[  270.704742]  mmcblk0: p1 p2
[  271.448608] EXT2-fs (mmcblk0p2): warning: mounting ext3 filesystem as 
ext2
[  271.455749] EXT2-fs (mmcblk0p2): warning: mounting unchecked fs, 
running e2fsck is recommended

root@domain.hid:~# cat /proc/interrupts
            CPU0
   7:          4        INTC  TWL4030-PIH
  12:        358        INTC  DMA
  37:       3520        INTC  gp timer
  56:        416        INTC  i2c_omap
  61:          0        INTC  i2c_omap
  74:        625        INTC  serial
  77:      14021        INTC  ehci_hcd:usb2
  83:        247        INTC  mmc0
  92:          1        INTC  musb_hdrc
  93:          0        INTC  musb_hdrc
378:          2     twl4030  twl4030_usb
379:          0     twl4030  rtc0
384:          2     twl4030  mmc0 <===== notice second Chip Detect irpt
Err:          0

2.6.33 with the Adeos patch and Xenomai enabled...
The Angstrom Distribution beagleboard ttyS2

Angstrom 2010.4-test-20100518 beagleboard ttyS2

beagleboard login: root
root@domain.hid:~# cat /proc/interrupts
            CPU0
   7:     161656        INTC  TWL4030-PIH
  12:        176        INTC  DMA
  37:       2642        INTC  gp timer
  56:     585760        INTC  i2c_omap
  61:          0        INTC  i2c_omap
  74:         85        INTC  serial
  77:      11018        INTC  ehci_hcd:usb2
  83:        144        INTC  mmc0
  92:          1        INTC  musb_hdrc
  93:          0        INTC  musb_hdrc
378:          0     twl4030  twl4030_usb
379:          0     twl4030  rtc0
384:          0     twl4030  mmc0
Err:          0
root@domain.hid:~# ls /dev
block               rtp11               tty29
... snipped ...
mem                 rtp30               tty48
mmcblk0             rtp31               tty49
mmcblk0p1           rtp4                tty5
mmcblk0p2           rtp5                tty50
network_latency     rtp6                tty51
... snipped ...
root@domain.hid:~# umount /dev/mmcblk0p1
root@domain.hid:~# umount /dev/mmcblk0p2

****** I removed the SD card here, no removal msg  *****************

root@domain.hid:~# ls /dev
block               rtp11               tty29
... snipped ...
mem                 rtp30               tty48
mmcblk0             rtp31               tty49
mmcblk0p1           rtp4                tty5
mmcblk0p2           rtp5                tty50
network_latency     rtp6                tty51
... snipped ...
root@domain.hid:~# cat /proc/interrupts
            CPU0
   7:    1106318        INTC  TWL4030-PIH
  12:        180        INTC  DMA
  37:      13933        INTC  gp timer
  56:    4029606        INTC  i2c_omap
  61:          0        INTC  i2c_omap
  74:        440        INTC  serial
  77:      12416        INTC  ehci_hcd:usb2
  83:        364        INTC  mmc0
  92:          1        INTC  musb_hdrc
  93:          0        INTC  musb_hdrc
378:          0     twl4030  twl4030_usb <=== also 0, but not sure if 
its meaningful
379:          0     twl4030  rtc0
384:          0     twl4030  mmc0 <===== no Chip Detect irpt
Err:          0

Reinserting the SD card did not result in a message. The SD card file 
systems seemed to be in a half mounted state.

I suspect that this bug effects all interrupts received via twl4030 
family devices.

Regards,
Bob Feretich

On 7/22/2010 3:14 PM, Gilles Chanteperdrix wrote:
> ... snipped ...
> As I said, the absence of IRQ 378 in 2.6.33 looks like a regression,
> which should be easy to find with git bisect. Then when you know the
> commit which caused the regression, tell me, I will revert it on 2.6.33,
> so that I can reproduce the bug you are facing on my board, and
> hopefully what happens with the Adeos patch.
>
>

[-- Attachment #2: Type: text/html, Size: 10728 bytes --]

Re: [Xenomai-help] Adeos patch prevents IRQ 384 (MMC Chip Detect) on omap-2.6.33

[Gilles Chanteperdrix]

Bob Feretich wrote:
>   I have started a new thread with a name that better describes the 
> failure I am seeing. This may or may not be the reason I was seeing root 
> file system mount hang on omap-2.6.31 (previous thread).

Ok. In the case where you have Adeos without Xenomai, do you have
CONFIG_IPIPE enabled, if yes, then please verify that when CONFIG_IPIPE
is disabled, you return in the same situation as without the I-pipe
patch. Please also try enabling CONFIG_IPIPE and only removing the
commit which "fixes" the spurious irqs.


-- 
					    Gilles.

Re: [Xenomai-help] Adeos patch prevents IRQ 384 (MMC Chip Detect) on omap-2.6.33

[Gilles Chanteperdrix]

Gilles Chanteperdrix wrote:
> Bob Feretich wrote:
>>   I have started a new thread with a name that better describes the 
>> failure I am seeing. This may or may not be the reason I was seeing root 
>> file system mount hang on omap-2.6.31 (previous thread).
> 
> Ok. In the case where you have Adeos without Xenomai, do you have
> CONFIG_IPIPE enabled, if yes, then please verify that when CONFIG_IPIPE
> is disabled, you return in the same situation as without the I-pipe
> patch. Please also try enabling CONFIG_IPIPE and only removing the
> commit which "fixes" the spurious irqs.

To clarify my suggestions: I think the "fix" for spurious irqs may in
fact paper over the real problem of twl4030 irqs with the Adeos patch. I
simply did not spend to much sweat on it, because the twl4030 irqs code
look a lot like an hacky UFO which is going to disappear thanks to
threaded interrupts. But obviously, that is not going to happen for
2.6.31 or 2.6.33.

Anyway, I am going to test 2.6.33 without I-pipe on my side to see if I
get the interrupts and I can reproduce your issue.

-- 
					    Gilles.

Re: [Xenomai-help] Adeos patch prevents IRQ 384 (MMC Chip Detect) on omap-2.6.33

[Bob Feretich]

[-- Attachment #1: Type: text/plain, Size: 1253 bytes --]

  Let me make sure I understand.
The most recent report from me contained console logs of two boots.
The first was 2.6.33 with no Adeos patch applied.
The second was 2.6.33 with the Adeos patch and Xenomai enabled 
(CONFIG_IPIPE=y) and CONFIG_XENOMAI=y).

You want me to perform to tests:

   1. 2.6.33 with the Adeos patch applied, but .config edited to turn
      off CONFIG_IPIPE and CONFIG_XENOMAI.
   2. Assuming test #1 passes the interrupts successfully, 2.6.33 with
      the Adeos patch applied, CONFIG_IPIPE=y, CONFIG_XENOMAI off, and
      revert the change to drivers/i2c/busses/i2c-omap.c.

Is that correct?

Regards,
Bob Feretich


On 7/24/2010 5:42 AM, Gilles Chanteperdrix wrote:
> Bob Feretich wrote:
>>    I have started a new thread with a name that better describes the
>> failure I am seeing. This may or may not be the reason I was seeing root
>> file system mount hang on omap-2.6.31 (previous thread).
> Ok. In the case where you have Adeos without Xenomai, do you have
> CONFIG_IPIPE enabled, if yes, then please verify that when CONFIG_IPIPE
> is disabled, you return in the same situation as without the I-pipe
> patch. Please also try enabling CONFIG_IPIPE and only removing the
> commit which "fixes" the spurious irqs.
>
>

[-- Attachment #2: Type: text/html, Size: 1844 bytes --]

Re: [Xenomai-help] Adeos patch prevents IRQ 384 (MMC Chip Detect) on omap-2.6.33

[Gilles Chanteperdrix]

Bob Feretich wrote:
>   Let me make sure I understand.
> The most recent report from me contained console logs of two boots.
> The first was 2.6.33 with no Adeos patch applied.
> The second was 2.6.33 with the Adeos patch and Xenomai enabled 
> (CONFIG_IPIPE=y) and CONFIG_XENOMAI=y).
> 
> You want me to perform to tests:
> 
>    1. 2.6.33 with the Adeos patch applied, but .config edited to turn
>       off CONFIG_IPIPE and CONFIG_XENOMAI.

That is, if when you tested the kernel patched with Adeos you never
turned CONFIG_IPIPE off.

>    2. Assuming test #1 passes the interrupts successfully, 2.6.33 with
>       the Adeos patch applied, CONFIG_IPIPE=y, CONFIG_XENOMAI off, and
>       revert the change to drivers/i2c/busses/i2c-omap.c.
> 
> Is that correct?

Yep.


-- 
					    Gilles.

Re: [Xenomai-help] Adeos patch prevents IRQ 384 (MMC Chip Detect) on omap-2.6.33

[Bob Feretich]

[-- Attachment #1: Type: text/plain, Size: 25841 bytes --]

  Test 1 results:
With the Adeos patch installed, but Adeos disabled, the system ran 
normally. IRQ 384s were presented and serviced.  (The SD card removal 
amd insertion was handled correctly.)

Texas Instruments X-Loader 1.4.2 (Feb 19 2009 - 12:01:24)
Reading boot sector
Loading u-boot.bin from mmc


U-Boot 2009.06-rc2 (Nov 02 2009 - 23:57:20)

OMAP3530-GP ES3.0, CPU-OPP2 L3-165MHz
OMAP3 Beagle board + LPDDR/NAND
DRAM:  256 MB
NAND:  256 MiB
In:    serial
Out:   serial
Err:   serial
Board revision C
Die ID #317000030000000004013f8a1701a01b
Hit any key to stop autoboot:  0
OMAP3 beagleboard.org # setenv bootargs 'console=ttyS2,115200n8 
ip=192.168.1.81:192.168.1.80:192.168.1.1:255.25
5.255.0:beagleboard:eth0:off root=/dev/nfs rw 
nfsroot=192.168.1.80:/home/Bob/NFSROOT,nolock,rsize=1024,wsize=10
24 rootwait'
OMAP3 beagleboard.org # boot
mmc1 is available
reading uImage

1902408 bytes read
## Booting kernel from Legacy Image at 80300000 ...
    Image Name:   Angstrom/2.6.33/beagleboard
    Image Type:   ARM Linux Kernel Image (uncompressed)
    Data Size:    1902344 Bytes =  1.8 MB
    Load Address: 80008000
    Entry Point:  80008000
    Verifying Checksum ... OK
    Loading Kernel Image ... OK
OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.
Linux version 2.6.33 (Bob@domain.hid) (gcc version 4.3.3 (GCC) ) #2 
Sat Jul 24 16:32:00 PDT 2010
CPU: ARMv7 Processor [411fc083] revision 3 (ARMv7), cr=10c53c7f
CPU: VIPT nonaliasing data cache, VIPT nonaliasing instruction cache
Machine: OMAP3 Beagle Board
Memory policy: ECC disabled, Data cache writeback
OMAP3430/3530 ES3.0 (l2cache iva sgx neon isp )
SRAM: Mapped pa 0x40200000 to va 0xfe400000 size: 0x100000
Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 65024
Kernel command line: console=ttyS2,115200n8 
ip=192.168.1.81:192.168.1.80:192.168.1.1:255.255.255.0:beagleboard:
eth0:off root=/dev/nfs rw 
nfsroot=192.168.1.80:/home/Bob/NFSROOT,nolock,rsize=1024,wsize=1024 rootwait
PID hash table entries: 1024 (order: 0, 4096 bytes)
Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
Memory: 128MB 128MB = 256MB total
Memory: 255872KB available (3292K code, 286K data, 120K init, 0K highmem)
Hierarchical RCU implementation.
RCU-based detection of stalled CPUs is enabled.
NR_IRQS:402
Clocking rate (Crystal/Core/MPU): 26.0/332/500 MHz
Reprogramming SDRC clock to 332000000 Hz
GPMC revision 5.0
IRQ: Found an INTC at 0xfa200000 (revision 4.0) with 96 interrupts
Total of 96 interrupts on 1 active controller
OMAP GPIO hardware version 2.5
OMAP clockevent source: GPTIMER1 at 13000000 Hz
Console: colour dummy device 80x30
Calibrating delay loop... 498.07 BogoMIPS (lpj=2490368)
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
devtmpfs: initialized
regulator: core version 0.5
NET: Registered protocol family 16
Found NAND on CS0
Registering NAND on CS0
OMAP DMA hardware revision 4.0
bio: create slab <bio-0> at 0
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
i2c_omap i2c_omap.1: bus 1 rev3.12 at 2600 kHz
twl4030: PIH (irq 7) chaining IRQs 368..375
twl4030: power (irq 373) chaining IRQs 376..383
twl4030: gpio (irq 368) chaining IRQs 384..401
regulator: VUSB1V5: 1500 mV normal standby
regulator: VUSB1V8: 1800 mV normal standby
regulator: VUSB3V1: 3100 mV normal standby
twl4030_usb twl4030_usb: Initialized TWL4030 USB module
regulator: VMMC1: 1850 <--> 3150 mV at 3000 mV normal standby
regulator: VDAC: 1800 mV normal standby
regulator: VDVI: 1800 mV normal standby
regulator: VSIM: 1800 <--> 3000 mV at 1800 mV normal standby
i2c_omap i2c_omap.3: bus 3 rev3.12 at 100 kHz
Switching to clocksource gp timer
musb_hdrc: version 6.0, musb-dma, otg (peripheral+host), debug=0
musb_hdrc: USB OTG mode controller at fa0ab000 using DMA, IRQ 92
NET: Registered protocol family 2
IP route cache hash table entries: 2048 (order: 1, 8192 bytes)
TCP established hash table entries: 8192 (order: 4, 65536 bytes)
TCP bind hash table entries: 8192 (order: 3, 32768 bytes)
TCP: Hash tables configured (established 8192 bind 8192)
TCP reno registered
UDP hash table entries: 256 (order: 0, 4096 bytes)
UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
NET: Registered protocol family 1
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
VFS: Disk quotas dquot_6.5.2
Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
JFFS2 version 2.2. (NAND) �© 2001-2006 Red Hat, Inc.
msgmni has been set to 500
alg: No test for stdrng (krng)
Block layer SCSI generic (bsg) driver version 0.4 loaded (major 253)
io scheduler noop registered
io scheduler deadline registered
io scheduler cfq registered (default)
Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
serial8250.0: ttyS0 at MMIO 0x4806a000 (irq = 72) is a ST16654
serial8250.1: ttyS1 at MMIO 0x4806c000 (irq = 73) is a ST16654
serial8250.2: ttyS2 at MMIO 0x49020000 (irq = 74) is a ST16654
console [ttyS2] enabled
brd: module loaded
loop: module loaded
usbcore: registered new interface driver asix
usbcore: registered new interface driver cdc_ether
usbcore: registered new interface driver net1080
usbcore: registered new interface driver cdc_subset
usbcore: registered new interface driver zaurus
usbmon: debugfs is not available
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
ehci-omap ehci-omap.0: OMAP-EHCI Host Controller
ehci-omap ehci-omap.0: new USB bus registered, assigned bus number 1
ehci-omap ehci-omap.0: irq 77, io mem 0x48064800
ehci-omap ehci-omap.0: USB 2.0 started, EHCI 1.00
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 3 ports detected
twl_rtc twl_rtc: rtc core: registered twl_rtc as rtc0
twl_rtc twl_rtc: Power up reset detected.
twl_rtc twl_rtc: Enabling TWL-RTC.
i2c /dev entries driver
TCP cubic registered
NET: Registered protocol family 17
NET: Registered protocol family 15
Power Management for TI OMAP3.
VFP support v0.3: implementor 41 architecture 3 part 30 variant c rev 1
regulator_init_complete: incomplete constraints, leaving VDVI on
regulator_init_complete: incomplete constraints, leaving VDAC on
twl_rtc twl_rtc: setting system clock to 2000-01-01 00:00:00 UTC (946684800)
usb 1-2: new high speed USB device using ehci-omap and address 2
mmc0: new high speed SDHC card at address 1234
mmcblk0: mmc0:1234 SA04G 3.68 GiB
  mmcblk0: p1 p2
eth0: register 'asix' at usb-ehci-omap.0-2, ASIX AX88772 USB 2.0 
Ethernet, 00:50:b6:05:d2:0c
eth0: link down
eth0: link up, 100Mbps, half-duplex, lpa 0x40A1
IP-Config: Complete:
      device=eth0, addr=192.168.1.81, mask=255.255.255.0, gw=192.168.1.1,
      host=beagleboard, domain=, nis-domain=(none),
      bootserver=192.168.1.80, rootserver=192.168.1.80, rootpath=
Looking up port of RPC 100003/2 on 192.168.1.80
Looking up port of RPC 100005/1 on 192.168.1.80
VFS: Mounted root (nfs filesystem) on device 0:13.
devtmpfs: mounted
Freeing init memory: 120K
INIT: version 2.86 booting
Please wait: booting...
Starting udev
EXT2-fs (mmcblk0p2): warning: mounting ext3 filesystem as ext2
Remounting root file system...
Caching udev devnodes
Populating dev cache
root: mount: mounting rootfs on / failed: No such file or directory
NOT configuring network interfaces: / is an NFS mount
Tue May 18 20:58:00 UTC 2010
Starting to configure packages...
Nothing to be done
Finished to configure packages.
INIT: Entering runlevel: 5
Starting Dropbear SSH server: dropbear.
Starting syslogd/klogd: done

.-------.
|       |                  .-.
|   |   |-----.-----.-----.| |   .----..-----.-----.
|       |     | __  |  ---'| '--.|  .-'|     |     |
|   |   |  |  |     |---  ||  --'|  |  |  '  | | | |
'---'---'--'--'--.  |-----''----''--'  '-----'-'-'-'
                 -'  |
                 '---'

The Angstrom Distribution beagleboard ttyS2

Angstrom 2010.4-test-20100518 beagleboard ttyS2

beagleboard login: root
root@domain.hid:~# /proc/interrupts
-sh: /proc/interrupts: Permission denied
root@domain.hid:~# cat /proc/interrupts
            CPU0
   7:          0        INTC  TWL4030-PIH
  11:          0        INTC  prcm
  12:        198        INTC  DMA
  37:       2267        INTC  gp timer
  56:        318        INTC  i2c_omap
  61:          0        INTC  i2c_omap
  72:          1        INTC  serial idle
  73:          1        INTC  serial idle
  74:        177        INTC  serial idle, serial
  77:      11313        INTC  ehci_hcd:usb1
  83:        126        INTC  mmc0
  92:          0        INTC  musb_hdrc
  93:          0        INTC  musb_hdrc
378:          0     twl4030  twl4030_usb
379:          0     twl4030  rtc0
384:          0     twl4030  mmc0
Err:          0
root@domain.hid:~# df
Filesystem           1K-blocks      Used Available Use% Mounted on
/dev/root             15868228   8775884   6931324  56% /
devtmpfs                128088       132    127956   0% /dev
none                    128088       132    127956   0% /dev
/dev/mmcblk0p1          197676      2075    195602   1% /media/mmcblk0p1
/dev/mmcblk0p2         3605300     72764   3349396   2% /media/mmcblk0p2
tmpfs                   128088        16    128072   0% /var/volatile
tmpfs                   128088         0    128088   0% /dev/shm
tmpfs                   128088         0    128088   0% /media/ram
root@domain.hid:~# umount /dev/mmcblk0p1
root@domain.hid:~# umount /dev/mmcblk0p2
root@domain.hid:~# df
Filesystem           1K-blocks      Used Available Use% Mounted on
/dev/root             15868228   8775884   6931324  56% /
devtmpfs                128088       132    127956   0% /dev
none                    128088       132    127956   0% /dev
tmpfs                   128088        16    128072   0% /var/volatile
tmpfs                   128088         0    128088   0% /dev/shm
tmpfs                   128088         0    128088   0% /media/ram

***** removed SD card   **************************************************

root@domain.hid:~# mmc0: card 1234 removed
root@domain.hid:~# cat /proc/interrupts
            CPU0
   7:          1        INTC  TWL4030-PIH
  11:          0        INTC  prcm
  12:        537        INTC  DMA
  37:       3789        INTC  gp timer
  56:        338        INTC  i2c_omap
  61:          0        INTC  i2c_omap
  72:          1        INTC  serial idle
  73:          1        INTC  serial idle
  74:        311        INTC  serial idle, serial
  77:      13030        INTC  ehci_hcd:usb1
  83:        192        INTC  mmc0
  92:          0        INTC  musb_hdrc
  93:          0        INTC  musb_hdrc
378:          0     twl4030  twl4030_usb
379:          0     twl4030  rtc0
384:          1     twl4030  mmc0
Err:          0

*************** inserted SD card  ***********************

root@domain.hid:~# mmc0: new high speed SDHC card at address 1234
mmcblk0: mmc0:1234 SA04G 3.68 GiB
  mmcblk0: p1 p2
EXT2-fs (mmcblk0p2): warning: mounting ext3 filesystem as ext2

root@domain.hid:~# cat /proc/interrupts
            CPU0
   7:          2        INTC  TWL4030-PIH
  11:          0        INTC  prcm
  12:        684        INTC  DMA
  37:       4292        INTC  gp timer
  56:        366        INTC  i2c_omap
  61:          0        INTC  i2c_omap
  72:          1        INTC  serial idle
  73:          1        INTC  serial idle
  74:        391        INTC  serial idle, serial
  77:      14060        INTC  ehci_hcd:usb1
  83:        312        INTC  mmc0
  92:          0        INTC  musb_hdrc
  93:          0        INTC  musb_hdrc
378:          0     twl4030  twl4030_usb
379:          0     twl4030  rtc0
384:          2     twl4030  mmc0
Err:          0
root@domain.hid:~# df
Filesystem           1K-blocks      Used Available Use% Mounted on
/dev/root             15868228   8775884   6931324  56% /
devtmpfs                128088       132    127956   0% /dev
none                    128088       132    127956   0% /dev
tmpfs                   128088        16    128072   0% /var/volatile
tmpfs                   128088         0    128088   0% /dev/shm
tmpfs                   128088         0    128088   0% /media/ram
/dev/mmcblk0p1          197676      2075    195602   1% /media/mmcblk0p1
/dev/mmcblk0p2         3605300     72764   3349396   2% /media/mmcblk0p2
root@domain.hid:~#

Test 2 results:
With the Adeos patch installed,  Adeos enabled, Xenomai disabled, the 
spurious irpt patch reverted....
The system ran normally, until an IRQ 384 occurred. Then continuous 
spurious interrupts occurred.
Texas Instruments X-Loader 1.4.2 (Feb 19 2009 - 12:01:24)
Reading boot sector
Loading u-boot.bin from mmc


U-Boot 2009.06-rc2 (Nov 02 2009 - 23:57:20)

OMAP3530-GP ES3.0, CPU-OPP2 L3-165MHz
OMAP3 Beagle board + LPDDR/NAND
DRAM:  256 MB
NAND:  256 MiB
In:    serial
Out:   serial
Err:   serial
Board revision C
Die ID #317000030000000004013f8a1701a01b
Hit any key to stop autoboot:  0
mmc1 is available
reading uImage

1942588 bytes read
## Booting kernel from Legacy Image at 80300000 ...
    Image Name:   Angstrom/2.6.33/beagleboard
    Image Type:   ARM Linux Kernel Image (uncompressed)
    Data Size:    1942524 Bytes =  1.9 MB
    Load Address: 80008000
    Entry Point:  80008000
    Verifying Checksum ... OK
    Loading Kernel Image ... OK
OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.
Linux version 2.6.33 (Bob@domain.hid) (gcc version 4.3.3 (GCC) ) #3 
Sat Jul 24 19:40:30 PDT 2010
CPU: ARMv7 Processor [411fc083] revision 3 (ARMv7), cr=10c53c7f
CPU: VIPT nonaliasing data cache, VIPT nonaliasing instruction cache
Machine: OMAP3 Beagle Board
Memory policy: ECC disabled, Data cache writeback
OMAP3430/3530 ES3.0 (l2cache iva sgx neon isp )
SRAM: Mapped pa 0x40200000 to va 0xfe400000 size: 0x100000
Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 65024
Kernel command line: console=ttyS2,115200n8 
ip=192.168.1.81:192.168.1.80:192.168.1.1:255.255.255.0:beagleboard:
eth0:off root=/dev/nfs rw 
nfsroot=192.168.1.80:/home/Bob/NFSROOT,nolock,rsize=1024,wsize=1024 rootwait
PID hash table entries: 1024 (order: 0, 4096 bytes)
Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
Memory: 128MB 128MB = 256MB total
Memory: 255744KB available (3360K code, 341K data, 132K init, 0K highmem)
Hierarchical RCU implementation.
RCU-based detection of stalled CPUs is enabled.
NR_IRQS:402
Clocking rate (Crystal/Core/MPU): 26.0/332/500 MHz
Reprogramming SDRC clock to 332000000 Hz
GPMC revision 5.0
IRQ: Found an INTC at 0xfa200000 (revision 4.0) with 96 interrupts
Total of 96 interrupts on 1 active controller
OMAP GPIO hardware version 2.5
OMAP clockevent source: GPTIMER1 at 13000000 Hz
I-pipe 1.16-01: pipeline enabled.
Console: colour dummy device 80x30
Calibrating delay loop... 498.07 BogoMIPS (lpj=2490368)
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
devtmpfs: initialized
regulator: core version 0.5
NET: Registered protocol family 16
Found NAND on CS0
Registering NAND on CS0
OMAP DMA hardware revision 4.0
bio: create slab <bio-0> at 0
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
i2c_omap i2c_omap.1: bus 1 rev3.12 at 2600 kHz
twl4030: PIH (irq 7) chaining IRQs 368..375
twl4030: power (irq 373) chaining IRQs 376..383
twl4030: gpio (irq 368) chaining IRQs 384..401
regulator: VUSB1V5: 1500 mV normal standby
regulator: VUSB1V8: 1800 mV normal standby
regulator: VUSB3V1: 3100 mV normal standby
twl4030_usb twl4030_usb: Initialized TWL4030 USB module
regulator: VMMC1: 1850 <--> 3150 mV at 3000 mV normal standby
regulator: VDAC: 1800 mV normal standby
regulator: VDVI: 1800 mV normal standby
regulator: VSIM: 1800 <--> 3000 mV at 1800 mV normal standby
i2c_omap i2c_omap.3: bus 3 rev3.12 at 100 kHz
Switching to clocksource gp timer
musb_hdrc: version 6.0, musb-dma, otg (peripheral+host), debug=0
musb_hdrc: USB OTG mode controller at fa0ab000 using DMA, IRQ 92
NET: Registered protocol family 2
IP route cache hash table entries: 2048 (order: 1, 8192 bytes)
TCP established hash table entries: 8192 (order: 4, 65536 bytes)
TCP bind hash table entries: 8192 (order: 3, 32768 bytes)
TCP: Hash tables configured (established 8192 bind 8192)
TCP reno registered
UDP hash table entries: 256 (order: 0, 4096 bytes)
UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
NET: Registered protocol family 1
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
VFS: Disk quotas dquot_6.5.2
Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
JFFS2 version 2.2. (NAND) �© 2001-2006 Red Hat, Inc.
msgmni has been set to 499
alg: No test for stdrng (krng)
Block layer SCSI generic (bsg) driver version 0.4 loaded (major 253)
io scheduler noop registered
io scheduler deadline registered
io scheduler cfq registered (default)
Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
serial8250.0: ttyS0 at MMIO 0x4806a000 (irq = 72) is a ST16654
serial8250.1: ttyS1 at MMIO 0x4806c000 (irq = 73) is a ST16654
serial8250.2: ttyS2 at MMIO 0x49020000 (irq = 74) is a ST16654
console [ttyS2] enabled
brd: module loaded
loop: module loaded
usbcore: registered new interface driver asix
usbcore: registered new interface driver cdc_ether
usbcore: registered new interface driver net1080
usbcore: registered new interface driver cdc_subset
usbcore: registered new interface driver zaurus
usbmon: debugfs is not available
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
ehci-omap ehci-omap.0: OMAP-EHCI Host Controller
ehci-omap ehci-omap.0: new USB bus registered, assigned bus number 1
ehci-omap ehci-omap.0: irq 77, io mem 0x48064800
ehci-omap ehci-omap.0: USB 2.0 started, EHCI 1.00
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 3 ports detected
twl_rtc twl_rtc: rtc core: registered twl_rtc as rtc0
twl_rtc twl_rtc: Power up reset detected.
twl_rtc twl_rtc: Enabling TWL-RTC.
i2c /dev entries driver
TCP cubic registered
NET: Registered protocol family 17
NET: Registered protocol family 15
Power Management for TI OMAP3.
VFP support v0.3: implementor 41 architecture 3 part 30 variant c rev 1
regulator_init_complete: incomplete constraints, leaving VDVI on
regulator_init_complete: incomplete constraints, leaving VDAC on
twl_rtc twl_rtc: setting system clock to 2000-01-01 00:00:00 UTC (946684800)
usb 1-2: new high speed USB device using ehci-omap and address 2
mmc0: new high speed SDHC card at address 1234
mmcblk0: mmc0:1234 SA04G 3.68 GiB
  mmcblk0: p1 p2
eth0: register 'asix' at usb-ehci-omap.0-2, ASIX AX88772 USB 2.0 
Ethernet, 00:50:b6:05:d2:0c
eth0: link down
eth0: link up, 100Mbps, half-duplex, lpa 0x40A1
IP-Config: Complete:
      device=eth0, addr=192.168.1.81, mask=255.255.255.0, gw=192.168.1.1,
      host=beagleboard, domain=, nis-domain=(none),
      bootserver=192.168.1.80, rootserver=192.168.1.80, rootpath=
Looking up port of RPC 100003/2 on 192.168.1.80
Looking up port of RPC 100005/1 on 192.168.1.80
VFS: Mounted root (nfs filesystem) on device 0:13.
devtmpfs: mounted
Freeing init memory: 132K
INIT: version 2.86 booting
Please wait: booting...
Starting udev
udev: starting version 151

udevadm settle - timeout of 3 seconds reached, the event queue contains:
   /sys/devices/platform/ehci-omap.0/usb1/1-2/1-2:1.0/net/eth0 (326)
   
/sys/devices/platform/mmci-omap-hs.0/mmc_host/mmc0/mmc0:1234/block/mmcblk0 
(347)
   
/sys/devices/platform/mmci-omap-hs.0/mmc_host/mmc0/mmc0:1234/block/mmcblk0/mmcblk0p1 
(348)
   
/sys/devices/platform/mmci-omap-hs.0/mmc_host/mmc0/mmc0:1234/block/mmcblk0/mmcblk0p2 
(349)
Remounting root file system...
Caching udev devnodes
Populating dev cachemv: cannot rename '/tmp/uname': No such file or 
directory
EXT2-fs (mmcblk0p2): warning: mounting ext3 filesystem as ext2
root: mount: mounting rootfs on / failed: No such file or directory
NOT configuring network interfaces: / is an NFS mount
Tue May 18 20:58:00 UTC 2010
Starting to configure packages...
Nothing to be done
Finished to configure packages.
INIT: Entering runlevel: 5
Starting Dropbear SSH server: dropbear.
Starting syslogd/klogd: done

.-------.
|       |                  .-.
|   |   |-----.-----.-----.| |   .----..-----.-----.
|       |     | __  |  ---'| '--.|  .-'|     |     |
|   |   |  |  |     |---  ||  --'|  |  |  '  | | | |
'---'---'--'--'--.  |-----''----''--'  '-----'-'-'-'
                 -'  |
                 '---'

The Angstrom Distribution beagleboard ttyS2

Angstrom 2010.4-test-20100518 beagleboard ttyS2

beagleboard login: root
root@domain.hid:~# cat /proc/interrupts
            CPU0
   7:          0        INTC  TWL4030-PIH
  11:          0        INTC  prcm
  12:        517        INTC  DMA
  37:       1062        INTC  gp timer
  56:        318        INTC  i2c_omap
  61:          0        INTC  i2c_omap
  72:          1        INTC  serial idle
  73:          1        INTC  serial idle
  74:        117        INTC  serial idle, serial
  77:      12033        INTC  ehci_hcd:usb1
  83:        171        INTC  mmc0
  92:          0        INTC  musb_hdrc
  93:          0        INTC  musb_hdrc
378:          0     twl4030  twl4030_usb
379:          0     twl4030  rtc0
384:          0     twl4030  mmc0
Err:          0
root@domain.hid:~# df
Filesystem           1K-blocks      Used Available Use% Mounted on
/dev/root             15868228   8775276   6931932  56% /
devtmpfs                128024       128    127896   0% /dev
none                    128024       128    127896   0% /dev
/dev/mmcblk0p1          197676      2114    195562   1% /media/mmcblk0p1
tmpfs                   128024        16    128008   0% /var/volatile
tmpfs                   128024         0    128024   0% /dev/shm
tmpfs                   128024         0    128024   0% /media/ram
/dev/mmcblk0p2         3605300     72764   3349396   2% /media/mmcblk0p2
root@domain.hid:~# umount /dev/mmcblk0p1
root@domain.hid:~# umount /dev/mmcblk0p2
root@domain.hid:~#
root@domain.hid:~# *********    # remove sd card ####   
***********************
root@domain.hid:~#
root@domain.hid:~# cat /proc/interrupts
            CPU0
   7:      32919        INTC  TWL4030-PIH
  11:          0        INTC  prcm
  12:        835        INTC  DMA
  37:       1703        INTC  gp timer
  56:      99075        INTC  i2c_omap
  61:          0        INTC  i2c_omap
  72:          1        INTC  serial idle
  73:          1        INTC  serial idle
  74:        252        INTC  serial idle, serial
  77:      12455        INTC  ehci_hcd:usb1
  83:        233        INTC  mmc0
  92:          0        INTC  musb_hdrc
  93:          0        INTC  musb_hdrc
378:          0     twl4030  twl4030_usb
379:          0     twl4030  rtc0
384:          0     twl4030  mmc0
Err:          0
root@domain.hid:~# cat /proc/interrupts
            CPU0
   7:      61279        INTC  TWL4030-PIH
  11:          0        INTC  prcm
  12:        835        INTC  DMA
  37:       1989        INTC  gp timer
  56:     184159        INTC  i2c_omap
  61:          0        INTC  i2c_omap
  72:          1        INTC  serial idle
  73:          1        INTC  serial idle
  74:        279        INTC  serial idle, serial
  77:      12507        INTC  ehci_hcd:usb1
  83:        233        INTC  mmc0
  92:          0        INTC  musb_hdrc
  93:          0        INTC  musb_hdrc
378:          0     twl4030  twl4030_usb
379:          0     twl4030  rtc0
384:          0     twl4030  mmc0
Err:          0
root@domain.hid irq 95: 0xffffffdf, please flush posted write 
for irq 56
Spurious irq 95: 0xffffffdf, please flush posted write for irq 56
Spurious irq 95: 0xffffffdf, please flush posted write for irq 56
Spurious irq 95: 0xffffffdf, please flush posted write for irq 56
Spurious irq 95: 0xffffffdf, please flush posted write for irq 56
Spurious irq 95: 0xffffffdf, please flush posted write for irq 56
Spurious irq 95: 0xffffffdf, please flush posted write for irq 56
... snipped ... About 1023 spurious irpt msgs occurred.

The beginning of the spurious irpt messages was not consistent. They 
usually started occuring soon, but not immediately after the SD card was 
removed. As you can see above, I was able to enter a couple commands 
before the interrupts began. Sometimes the messages occurred before the 
removal of the SD card. I think that any kind of i2c probed level 2 
interrupt triggers the problem.

I was fast enough to display /proc/interrupts after I pulled out the SD 
card (above) and befre the spurrious irpts occurred. The IRQ 384 irpt is 
not shown  in /proc/interrupts and no "removed" message occurred. 
Without the Adeos patch (or with CONFIG_IPIPE disabled), the removel 
mesage was immediate.

Regards,
Bob Feretich











On 7/24/2010 11:57 AM, Gilles Chanteperdrix wrote:
> Bob Feretich wrote:
>>    Let me make sure I understand.
>> The most recent report from me contained console logs of two boots.
>> The first was 2.6.33 with no Adeos patch applied.
>> The second was 2.6.33 with the Adeos patch and Xenomai enabled
>> (CONFIG_IPIPE=y) and CONFIG_XENOMAI=y).
>>
>> You want me to perform to tests:
>>
>>     1. 2.6.33 with the Adeos patch applied, but .config edited to turn
>>        off CONFIG_IPIPE and CONFIG_XENOMAI.
> That is, if when you tested the kernel patched with Adeos you never
> turned CONFIG_IPIPE off.
>
>>     2. Assuming test #1 passes the interrupts successfully, 2.6.33 with
>>        the Adeos patch applied, CONFIG_IPIPE=y, CONFIG_XENOMAI off, and
>>        revert the change to drivers/i2c/busses/i2c-omap.c.
>>
>> Is that correct?
> Yep.
>
>

[-- Attachment #2: Type: text/html, Size: 37207 bytes --]

Re: [Xenomai-help] Adeos patch prevents IRQ 384 (MMC Chip Detect) on omap-2.6.33

[Gilles Chanteperdrix]

Bob Feretich wrote:
>   Test 1 results:
> With the Adeos patch installed, but Adeos disabled, the system ran 
> normally. IRQ 384s were presented and serviced.  (The SD card removal 
> amd insertion was handled correctly.)
> 

That is reassuring.


> (...)
> Test 2 results:
> With the Adeos patch installed,  Adeos enabled, Xenomai disabled, the 
> spurious irpt patch reverted....
> The system ran normally, until an IRQ 384 occurred. Then continuous 
> spurious interrupts occurred.

Ok. So, we have a real issue, which the "fix" was just papering over.
Now, we just have to understand what happens. Thanks.

Note that the board still works when it displays the "spurious
interrupts" messages, only the serial console is rendered unusable by
the messages.

-- 
					    Gilles.

Re: [Xenomai-help] Adeos patch prevents IRQ 384 (MMC Chip Detect) on omap-2.6.33

[Gilles Chanteperdrix]

Bob Feretich wrote:
>   Test 1 results:
> With the Adeos patch installed, but Adeos disabled, the system ran 
> normally. IRQ 384s were presented and serviced.  (The SD card removal 
> amd insertion was handled correctly.)

Ok. Could you try the following patch? It fixes the "always growing PIH 
interrupt count" number here, and now I have some twl4030_usb 
interrupts. However, I could not test the SD card insertion/removal, 
because I am working on the board remotely.

diff --git a/drivers/i2c/busses/i2c-omap.c b/drivers/i2c/busses/i2c-omap.c
index 8d608a1..0037e31 100644
--- a/drivers/i2c/busses/i2c-omap.c
+++ b/drivers/i2c/busses/i2c-omap.c
@@ -478,10 +478,6 @@ static int omap_i2c_xfer_msg(struct i2c_adapter *adap,
 	if (msg->len == 0)
 		return -EINVAL;
 
-#ifdef CONFIG_IPIPE
-	disable_irq(dev->irq);
-#endif /* CONFIG_IPIPE */
-
 	omap_i2c_write_reg(dev, OMAP_I2C_SA_REG, msg->addr);
 
 	/* REVISIT: Could the STB bit of I2C_CON be used with probing? */
@@ -525,9 +521,6 @@ static int omap_i2c_xfer_msg(struct i2c_adapter *adap,
 
 			/* Let the user know if i2c is in a bad state */
 			if (time_after(jiffies, delay)) {
-#ifdef CONFIG_IPIPE
-				enable_irq(dev->irq);
-#endif /* CONFIG_IPIPE */
 				dev_err(dev->dev, "controller timed out "
 				"waiting for start condition to finish\n");
 				return -ETIMEDOUT;
@@ -539,9 +532,6 @@ static int omap_i2c_xfer_msg(struct i2c_adapter *adap,
 		w &= ~OMAP_I2C_CON_STT;
 		omap_i2c_write_reg(dev, OMAP_I2C_CON_REG, w);
 	}
-#ifdef CONFIG_IPIPE
-	enable_irq(dev->irq);
-#endif /* CONFIG_IPIPE */
 
 	/*
 	 * REVISIT: We should abort the transfer on signals, but the bus goes
diff --git a/drivers/mfd/twl4030-irq.c b/drivers/mfd/twl4030-irq.c
index 9df9a5a..fb4b9f2 100644
--- a/drivers/mfd/twl4030-irq.c
+++ b/drivers/mfd/twl4030-irq.c
@@ -332,7 +332,7 @@ static int twl4030_irq_thread(void *data)
 					note_interrupt(module_irq, d,
 							IRQ_NONE);
 				else
-					d->handle_irq(module_irq, d);
+					ipipe_handle_irq_cond(module_irq);
 			}
 		}
 		local_irq_enable();

-- 
					    Gilles.

Re: [Xenomai-help] Adeos patch prevents IRQ 384 (MMC Chip Detect) on omap-2.6.33 - working now

[Bob Feretich]

[-- Attachment #1: Type: text/plain, Size: 38554 bytes --]

  I applied the below patches to the 2.6.33 BeagleBoard system, they WORKED.
Then I edited the 2.6.31 kernel to reflect the same patches, it WORKED too!

Below are the console logs.

2.6.33 with Xenomai enabled...
Texas Instruments X-Loader 1.4.2 (Feb 19 2009 - 12:01:24)
Reading boot sector
Loading u-boot.bin from mmc


U-Boot 2009.06-rc2 (Nov 02 2009 - 23:57:20)

OMAP3530-GP ES3.0, CPU-OPP2 L3-165MHz
OMAP3 Beagle board + LPDDR/NAND
DRAM:  256 MB
NAND:  256 MiB
In:    serial
Out:   serial
Err:   serial
Board revision C
Die ID #317000030000000004013f8a1701a01b
Hit any key to stop autoboot:  0
mmc1 is available
reading uImage

2053552 bytes read
## Booting kernel from Legacy Image at 80300000 ...
    Image Name:   Angstrom/2.6.33/beagleboard
    Image Type:   ARM Linux Kernel Image (uncompressed)
    Data Size:    2053488 Bytes =  2 MB
    Load Address: 80008000
    Entry Point:  80008000
    Verifying Checksum ... OK
    Loading Kernel Image ... OK
OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.
Linux version 2.6.33 (Bob@domain.hid) (gcc version 4.3.3 (GCC) ) #3 
Sun Jul 25 14:20:13 PDT 2010
CPU: ARMv7 Processor [411fc083] revision 3 (ARMv7), cr=10c53c7f
CPU: VIPT nonaliasing data cache, VIPT nonaliasing instruction cache
Machine: OMAP3 Beagle Board
Memory policy: ECC disabled, Data cache writeback
OMAP3430/3530 ES3.0 (l2cache iva sgx neon isp )
SRAM: Mapped pa 0x40200000 to va 0xfe400000 size: 0x100000
Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 65024
Kernel command line: console=ttyS2,115200n8 
ip=192.168.1.81:192.168.1.80:192.168.1.1:255.255.255.0:beagleboard:et
h0:off root=/dev/nfs rw 
nfsroot=192.168.1.80:/home/Bob/NFSROOT,nolock,rsize=1024,wsize=1024 rootwait
PID hash table entries: 1024 (order: 0, 4096 bytes)
Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
Memory: 128MB 128MB = 256MB total
Memory: 255360KB available (3592K code, 435K data, 132K init, 0K highmem)
Hierarchical RCU implementation.
RCU-based detection of stalled CPUs is enabled.
NR_IRQS:402
Clocking rate (Crystal/Core/MPU): 26.0/332/500 MHz
Reprogramming SDRC clock to 332000000 Hz
GPMC revision 5.0
IRQ: Found an INTC at 0xfa200000 (revision 4.0) with 96 interrupts
Total of 96 interrupts on 1 active controller
OMAP GPIO hardware version 2.5
OMAP clockevent source: GPTIMER1 at 13000000 Hz
I-pipe 1.16-01: pipeline enabled.
Console: colour dummy device 80x30
Calibrating delay loop... 498.07 BogoMIPS (lpj=2490368)
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
devtmpfs: initialized
regulator: core version 0.5
NET: Registered protocol family 16
Found NAND on CS0
Registering NAND on CS0
OMAP DMA hardware revision 4.0
bio: create slab <bio-0> at 0
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
i2c_omap i2c_omap.1: bus 1 rev3.12 at 2600 kHz
twl4030: PIH (irq 7) chaining IRQs 368..375
twl4030: power (irq 373) chaining IRQs 376..383
twl4030: gpio (irq 368) chaining IRQs 384..401
regulator: VUSB1V5: 1500 mV normal standby
regulator: VUSB1V8: 1800 mV normal standby
regulator: VUSB3V1: 3100 mV normal standby
twl4030_usb twl4030_usb: Initialized TWL4030 USB module
regulator: VMMC1: 1850 <--> 3150 mV at 3000 mV normal standby
regulator: VDAC: 1800 mV normal standby
regulator: VDVI: 1800 mV normal standby
regulator: VSIM: 1800 <--> 3000 mV at 1800 mV normal standby
i2c_omap i2c_omap.3: bus 3 rev3.12 at 100 kHz
Switching to clocksource gp timer
musb_hdrc: version 6.0, musb-dma, otg (peripheral+host), debug=0
musb_hdrc: USB OTG mode controller at fa0ab000 using DMA, IRQ 92
NET: Registered protocol family 2
IP route cache hash table entries: 2048 (order: 1, 8192 bytes)
TCP established hash table entries: 8192 (order: 4, 65536 bytes)
TCP bind hash table entries: 8192 (order: 3, 32768 bytes)
TCP: Hash tables configured (established 8192 bind 8192)
TCP reno registered
UDP hash table entries: 256 (order: 0, 4096 bytes)
UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
NET: Registered protocol family 1
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
I-pipe: Domain Xenomai registered.
Xenomai: hal/arm started.
Xenomai: scheduling class idle registered.
Xenomai: scheduling class rt registered.
Xenomai: real-time nucleus v2.5.3 (Hordes Of Locusts) loaded.
Xenomai: starting native API services.
Xenomai: starting POSIX services.
Xenomai: starting RTDM services.
VFS: Disk quotas dquot_6.5.2
Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
JFFS2 version 2.2. (NAND) �© 2001-2006 Red Hat, Inc.
msgmni has been set to 499
alg: No test for stdrng (krng)
Block layer SCSI generic (bsg) driver version 0.4 loaded (major 253)
io scheduler noop registered
io scheduler deadline registered
io scheduler cfq registered (default)
Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
serial8250.0: ttyS0 at MMIO 0x4806a000 (irq = 72) is a ST16654
serial8250.1: ttyS1 at MMIO 0x4806c000 (irq = 73) is a ST16654
serial8250.2: ttyS2 at MMIO 0x49020000 (irq = 74) is a ST16654
console [ttyS2] enabled
brd: module loaded
loop: module loaded
usbcore: registered new interface driver asix
usbcore: registered new interface driver cdc_ether
usbcore: registered new interface driver net1080
usbcore: registered new interface driver cdc_subset
usbcore: registered new interface driver zaurus
usbmon: debugfs is not available
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
ehci-omap ehci-omap.0: OMAP-EHCI Host Controller
ehci-omap ehci-omap.0: new USB bus registered, assigned bus number 1
ehci-omap ehci-omap.0: irq 77, io mem 0x48064800
ehci-omap ehci-omap.0: USB 2.0 started, EHCI 1.00
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 3 ports detected
i2c /dev entries driver
TCP cubic registered
NET: Registered protocol family 17
NET: Registered protocol family 15
Power Management for TI OMAP3.
VFP support v0.3: implementor 41 architecture 3 part 30 variant c rev 1
regulator_init_complete: incomplete constraints, leaving VDVI on
regulator_init_complete: incomplete constraints, leaving VDAC on
drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
usb 1-2: new high speed USB device using ehci-omap and address 2
mmc0: new high speed SDHC card at address 1234
mmcblk0: mmc0:1234 SA04G 3.68 GiB
  mmcblk0: p1 p2
eth0: register 'asix' at usb-ehci-omap.0-2, ASIX AX88772 USB 2.0 
Ethernet, 00:50:b6:05:d2:0c
eth0: link down
eth0: link up, 100Mbps, half-duplex, lpa 0x40A1
IP-Config: Complete:
      device=eth0, addr=192.168.1.81, mask=255.255.255.0, gw=192.168.1.1,
      host=beagleboard, domain=, nis-domain=(none),
      bootserver=192.168.1.80, rootserver=192.168.1.80, rootpath=
Looking up port of RPC 100003/2 on 192.168.1.80
Looking up port of RPC 100005/1 on 192.168.1.80
VFS: Mounted root (nfs filesystem) on device 0:13.
devtmpfs: mounted
Freeing init memory: 132K
INIT: version 2.86 booting
Please wait: booting...
Starting udev
udev: starting version 151

udevadm settle - timeout of 3 seconds reached, the event queue contains:
   /sys/devices/platform/ehci-omap.0/usb1/1-2/1-2:1.0/net/eth0 (369)
   
/sys/devices/platform/mmci-omap-hs.0/mmc_host/mmc0/mmc0:1234/block/mmcblk0 
(389)
   
/sys/devices/platform/mmci-omap-hs.0/mmc_host/mmc0/mmc0:1234/block/mmcblk0/mmcblk0p1 
(390)
   
/sys/devices/platform/mmci-omap-hs.0/mmc_host/mmc0/mmc0:1234/block/mmcblk0/mmcblk0p2 
(391)
Remounting root file system...
Caching udev devnodes
Populating dev cachemv: cannot rename '/tmp/uname': No such file or 
directory
EXT2-fs (mmcblk0p2): warning: mounting ext3 filesystem as ext2
EXT2-fs (mmcblk0p2): warning: mounting unchecked fs, running e2fsck is 
recommended
root: mount: mounting rootfs on / failed: No such file or directory
NOT configuring network interfaces: / is an NFS mount
hwclock: can't open '/dev/misc/rtc': No such file or directory
Tue May 18 20:58:00 UTC 2010
hwclock: can't open '/dev/misc/rtc': No such file or directory
Starting to configure packages...
Nothing to be done
Finished to configure packages.
INIT: Entering runlevel: 5
Starting Dropbear SSH server: dropbear.
Starting syslogd/klogd: done

.-------.
|       |                  .-.
|   |   |-----.-----.-----.| |   .----..-----.-----.
|       |     | __  |  ---'| '--.|  .-'|     |     |
|   |   |  |  |     |---  ||  --'|  |  |  '  | | | |
'---'---'--'--'--.  |-----''----''--'  '-----'-'-'-'
                 -'  |
                 '---'

The Angstrom Distribution beagleboard ttyS2

Angstrom 2010.4-test-20100518 beagleboard ttyS2

beagleboard login: root
root@domain.hid:~# ls /proc
1              22             9              irq            self
10             28             buddyinfo      kallsyms       slabinfo
11             29             bus            kmsg           softirqs
12             3              cmdline        kpagecount     stat
13             4              cpu            kpageflags     swaps
130            5              cpuinfo        loadavg        sys
131            52             crypto         locks          sysrq-trigger
14             6              devices        meminfo        sysvipc
15             626            diskstats      misc           timer_list
16             629            driver         modules        tty
17             631            execdomains    mounts         uptime
18             633            filesystems    mtd            version
19             634            fs             net            vmallocinfo
190            635            interrupts     pagetypeinfo   vmstat
2              637            iomem          partitions     xenomai
20             7              ioports        sched_debug    zoneinfo
21             8              ipipe          scsi
root@domain.hid:~# cat /proc/interrupts
            CPU0
   7:          0        INTC  TWL4030-PIH
  11:          0        INTC  prcm
  12:        444        INTC  DMA
  37:       1232        INTC  gp timer
  56:        262        INTC  i2c_omap
  61:          0        INTC  i2c_omap
  72:          1        INTC  serial idle
  73:          1        INTC  serial idle
  74:        175        INTC  serial idle, serial
  77:      12663        INTC  ehci_hcd:usb1
  83:        146        INTC  mmc0
  92:          0        INTC  musb_hdrc
  93:          0        INTC  musb_hdrc
378:          0     twl4030  twl4030_usb
384:          0     twl4030  mmc0
Err:          0
root@domain.hid:~# df
Filesystem           1K-blocks      Used Available Use% Mounted on
/dev/root             15868228   8776716   6930492  56% /
devtmpfs                127860       128    127732   0% /dev
none                    127860       128    127732   0% /dev
/dev/mmcblk0p1          197676      2222    195454   1% /media/mmcblk0p1
/dev/mmcblk0p2         3605300     72764   3349396   2% /media/mmcblk0p2
tmpfs                   127860        16    127844   0% /var/volatile
tmpfs                   127860         0    127860   0% /dev/shm
tmpfs                   127860         0    127860   0% /media/ram
root@domain.hid:~#
root@domain.hid:~# umount /dev/mmcblk0p1
root@domain.hid:~# umount /dev/mmcblk0p2
root@domain.hid:~#
root@domain.hid:~# # Remove SD Card
root@domain.hid:~#
root@domain.hid:~# mmc0: card 1234 removed

root@domain.hid:~# cat /proc/interrupts
            CPU0
   7:          1        INTC  TWL4030-PIH
  11:          0        INTC  prcm
  12:        752        INTC  DMA
  37:       1909        INTC  gp timer
  56:        283        INTC  i2c_omap
  61:          0        INTC  i2c_omap
  72:          1        INTC  serial idle
  73:          1        INTC  serial idle
  74:        335        INTC  serial idle, serial
  77:      13622        INTC  ehci_hcd:usb1
  83:        217        INTC  mmc0
  92:          0        INTC  musb_hdrc
  93:          0        INTC  musb_hdrc
378:          0     twl4030  twl4030_usb
384:          1     twl4030  mmc0
Err:          0
root@domain.hid:~# df
Filesystem           1K-blocks      Used Available Use% Mounted on
/dev/root             15868228   8776716   6930492  56% /
devtmpfs                127860       116    127744   0% /dev
none                    127860       116    127744   0% /dev
tmpfs                   127860        16    127844   0% /var/volatile
tmpfs                   127860         0    127860   0% /dev/shm
tmpfs                   127860         0    127860   0% /media/ram
root@domain.hid:~#
root@domain.hid:~#  # insert SD card
root@domain.hid:~#
root@domain.hid:~# mmc0: new high speed SDHC card at address 1234
mmcblk0: mmc0:1234 SA04G 3.68 GiB
  mmcblk0: p1 p2
EXT2-fs (mmcblk0p2): warning: mounting ext3 filesystem as ext2
EXT2-fs (mmcblk0p2): warning: mounting unchecked fs, running e2fsck is 
recommended

root@domain.hid:~# cat /proc/interrupts
            CPU0
   7:          2        INTC  TWL4030-PIH
  11:          0        INTC  prcm
  12:        900        INTC  DMA
  37:       2471        INTC  gp timer
  56:        311        INTC  i2c_omap
  61:          0        INTC  i2c_omap
  72:          1        INTC  serial idle
  73:          1        INTC  serial idle
  74:        456        INTC  serial idle, serial
  77:      14699        INTC  ehci_hcd:usb1
  83:        330        INTC  mmc0
  92:          0        INTC  musb_hdrc
  93:          0        INTC  musb_hdrc
378:          0     twl4030  twl4030_usb
384:          2     twl4030  mmc0
Err:          0
root@domain.hid:~# df
Filesystem           1K-blocks      Used Available Use% Mounted on
/dev/root             15868228   8776716   6930492  56% /
devtmpfs                127860       128    127732   0% /dev
none                    127860       128    127732   0% /dev
tmpfs                   127860        16    127844   0% /var/volatile
tmpfs                   127860         0    127860   0% /dev/shm
tmpfs                   127860         0    127860   0% /media/ram
/dev/mmcblk0p1          197676      2222    195454   1% /media/mmcblk0p1
/dev/mmcblk0p2         3605300     72764   3349396   2% /media/mmcblk0p2
root@domain.hid:~# cat /proc/xenomai
cat: read error: Is a directory
root@domain.hid:~# cat /proc/ipipe
cat: read error: Is a directory
root@domain.hid:~# ls /proc/ipipe
Linux    Xenomai  version
root@domain.hid:~# ls /proc/ipipe/Xenomai
/proc/ipipe/Xenomai
root@domain.hid:~# cat /proc/ipipe/Xenomai
        +----- Handling ([A]ccepted, [G]rabbed, [W]ired, [D]iscarded)
        |+---- Sticky
        ||+--- Locked
        |||+-- Exclusive
        ||||+- Virtual
[IRQ]  |||||
   37:  W..X.
  418:  W...V
[Domain info]
id=0x58454e4f
priority=topmost
root@domain.hid:~# ls /proc/xenomai
acct          heap          registry      stat          version
apc           interfaces    rtdm          timebases
faults        irq           sched         timer
hal           latency       schedclasses  timerstat
root@domain.hid:~# cat /proc/xenomai/irq
IRQ         CPU0
  37:        3903         [timer]
418:           0         [virtual]
root@domain.hid:~#

2.6.31 with Xenomai enabled (booted both from NFS (below) and the 
SD-card, both worked)
Texas Instruments X-Loader 1.4.2 (Feb 19 2009 - 12:01:24)
Reading boot sector
Loading u-boot.bin from mmc


U-Boot 2009.06-rc2 (Nov 02 2009 - 23:57:20)

OMAP3530-GP ES3.0, CPU-OPP2 L3-165MHz
OMAP3 Beagle board + LPDDR/NAND
DRAM:  256 MB
NAND:  256 MiB
In:    serial
Out:   serial
Err:   serial
Board revision C
Die ID #317000030000000004013f8a1701a01b
Hit any key to stop autoboot:  0
mmc1 is available
reading uImage

1902512 bytes read
## Booting kernel from Legacy Image at 80300000 ...
    Image Name:   Angstrom/2.6.33/beagleboard
    Image Type:   ARM Linux Kernel Image (uncompressed)
    Data Size:    1902448 Bytes =  1.8 MB
    Load Address: 80008000
    Entry Point:  80008000
    Verifying Checksum ... OK
    Loading Kernel Image ... OK
OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.
Linux version 2.6.33 (rhino@domain.hid) (gcc version 4.3.3 (GCC) ) #2 
Sun Jul 25 14:45:37 PDT 2010
CPU: ARMv7 Processor [411fc083] revision 3 (ARMv7), cr=10c53c7f
CPU: VIPT nonaliasing data cache, VIPT nonaliasing instruction cache
Machine: OMAP3 Beagle Board
Memory policy: ECC disabled, Data cache writeback
OMAP3430/3530 ES3.0 (l2cache iva sgx neon isp )
SRAM: Mapped pa 0x40200000 to va 0xfe400000 size: 0x100000
Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 65024
Kernel command line: console=ttyS2,115200n8 
ip=192.168.1.81:192.168.1.80:192.168.1.1:255.255.255.0:beagleboard:et
h0:off root=/dev/nfs rw 
nfsroot=192.168.1.80:/home/Bob/NFSROOT,nolock,rsize=1024,wsize=1024 rootwait
PID hash table entries: 1024 (order: 0, 4096 bytes)
Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
Memory: 128MB 128MB = 256MB total
Memory: 255872KB available (3284K code, 285K data, 128K init, 0K highmem)
Hierarchical RCU implementation.
RCU-based detection of stalled CPUs is enabled.
NR_IRQS:402
Clocking rate (Crystal/Core/MPU): 26.0/332/500 MHz
Reprogramming SDRC clock to 332000000 Hz
GPMC revision 5.0
IRQ: Found an INTC at 0xfa200000 (revision 4.0) with 96 interrupts
Total of 96 interrupts on 1 active controller
OMAP GPIO hardware version 2.5
OMAP clockevent source: GPTIMER1 at 13000000 Hz
Console: colour dummy device 80x30
Calibrating delay loop... 498.07 BogoMIPS (lpj=2490368)
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
devtmpfs: initialized
regulator: core version 0.5
NET: Registered protocol family 16
Found NAND on CS0
Registering NAND on CS0
OMAP DMA hardware revision 4.0
bio: create slab <bio-0> at 0
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
i2c_omap i2c_omap.1: bus 1 rev3.12 at 2600 kHz
twl4030: PIH (irq 7) chaining IRQs 368..375
twl4030: power (irq 373) chaining IRQs 376..383
twl4030: gpio (irq 368) chaining IRQs 384..401
regulator: VUSB1V5: 1500 mV normal standby
regulator: VUSB1V8: 1800 mV normal standby
regulator: VUSB3V1: 3100 mV normal standby
twl4030_usb twl4030_usb: Initialized TWL4030 USB module
regulator: VMMC1: 1850 <--> 3150 mV at 3000 mV normal standby
regulator: VDAC: 1800 mV normal standby
regulator: VDVI: 1800 mV normal standby
regulator: VSIM: 1800 <--> 3000 mV at 1800 mV normal standby
i2c_omap i2c_omap.3: bus 3 rev3.12 at 100 kHz
Switching to clocksource gp timer
musb_hdrc: version 6.0, musb-dma, otg (peripheral+host), debug=0
musb_hdrc: USB OTG mode controller at fa0ab000 using DMA, IRQ 92
NET: Registered protocol family 2
IP route cache hash table entries: 2048 (order: 1, 8192 bytes)
TCP established hash table entries: 8192 (order: 4, 65536 bytes)
TCP bind hash table entries: 8192 (order: 3, 32768 bytes)
TCP: Hash tables configured (established 8192 bind 8192)
TCP reno registered
UDP hash table entries: 256 (order: 0, 4096 bytes)
UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
NET: Registered protocol family 1
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
VFS: Disk quotas dquot_6.5.2
Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
JFFS2 version 2.2. (NAND) �© 2001-2006 Red Hat, Inc.
msgmni has been set to 500
alg: No test for stdrng (krng)
Block layer SCSI generic (bsg) driver version 0.4 loaded (major 253)
io scheduler noop registered
io scheduler deadline registered
io scheduler cfq registered (default)
Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
serial8250.0: ttyS0 at MMIO 0x4806a000 (irq = 72) is a ST16654
serial8250.1: ttyS1 at MMIO 0x4806c000 (irq = 73) is a ST16654
serial8250.2: ttyS2 at MMIO 0x49020000 (irq = 74) is a ST16654
console [ttyS2] enabled
brd: module loaded
loop: module loaded
usbcore: registered new interface driver asix
usbcore: registered new interface driver cdc_ether
usbcore: registered new interface driver net1080
usbcore: registered new interface driver cdc_subset
usbcore: registered new interface driver zaurus
usbmon: debugfs is not available
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
ehci-omap ehci-omap.0: OMAP-EHCI Host Controller
ehci-omap ehci-omap.0: new USB bus registered, assigned bus number 1
ehci-omap ehci-omap.0: irq 77, io mem 0x48064800
ehci-omap ehci-omap.0: USB 2.0 started, EHCI 1.00
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 3 ports detected
twl_rtc twl_rtc: rtc core: registered twl_rtc as rtc0
twl_rtc twl_rtc: Power up reset detected.
twl_rtc twl_rtc: Enabling TWL-RTC.
i2c /dev entries driver
TCP cubic registered
NET: Registered protocol family 17
Power Management for TI OMAP3.
VFP support v0.3: implementor 41 architecture 3 part 30 variant c rev 1
regulator_init_complete: incomplete constraints, leaving VDVI on
regulator_init_complete: incomplete constraints, leaving VDAC on
twl_rtc twl_rtc: setting system clock to 2000-01-01 00:00:00 UTC (946684800)
usb 1-2: new high speed USB device using ehci-omap and address 2
mmc0: new high speed SDHC card at address 71df
mmcblk0: mmc0:71df SD04G 3.69 GiB
  mmcblk0: p1 p2
eth0: register 'asix' at usb-ehci-omap.0-2, ASIX AX88772 USB 2.0 
Ethernet, 00:50:b6:05:d2:0c
eth0: link down
eth0: link up, 100Mbps, half-duplex, lpa 0x40A1
IP-Config: Complete:
      device=eth0, addr=192.168.1.81, mask=255.255.255.0, gw=192.168.1.1,
      host=beagleboard, domain=, nis-domain=(none),
      bootserver=192.168.1.80, rootserver=192.168.1.80, rootpath=
Looking up port of RPC 100003/2 on 192.168.1.80
Looking up port of RPC 100005/1 on 192.168.1.80
VFS: Mounted root (nfs filesystem) on device 0:13.
devtmpfs: mounted
Freeing init memory: 128K
INIT: version 2.86 booting
Please wait: booting...
Starting udev
EXT2-fs (mmcblk0p2): error: couldn't mount because of unsupported 
optional features (4)
kjournald starting.  Commit interval 5 seconds
EXT3-fs (mmcblk0p2): using internal journal
EXT3-fs (mmcblk0p2): recovery complete
EXT3-fs (mmcblk0p2): mounted filesystem with writeback data mode
Remounting root file system...
Caching udev devnodes
Populating dev cache
root: mount: mounting rootfs on / failed: No such file or directory
NOT configuring network interfaces: / is an NFS mount
Tue May 18 20:58:00 UTC 2010
Starting to configure packages...
Nothing to be done
Finished to configure packages.
INIT: Entering runlevel: 5
Starting Dropbear SSH server: dropbear.
Starting syslogd/klogd: done


Texas Instruments X-Loader 1.4.2 (Feb 19 2009 - 12:01:24)
Reading boot sector
Loading u-boot.bin from mmc


U-Boot 2009.06-rc2 (Nov 02 2009 - 23:57:20)

OMAP3530-GP ES3.0, CPU-OPP2 L3-165MHz
OMAP3 Beagle board + LPDDR/NAND
DRAM:  256 MB
NAND:  256 MiB
In:    serial
Out:   serial
Err:   serial
Board revision C
Die ID #317000030000000004013f8a1701a01b
Hit any key to stop autoboot:  0
mmc1 is available
reading uImage

2020284 bytes read
## Booting kernel from Legacy Image at 80300000 ...
    Image Name:   Angstrom/2.6.31/beagleboard
    Image Type:   ARM Linux Kernel Image (uncompressed)
    Data Size:    2020220 Bytes =  1.9 MB
    Load Address: 80008000
    Entry Point:  80008000
    Verifying Checksum ... OK
    Loading Kernel Image ... OK
OK

Starting kernel ...

Uncompressing 
Linux..............................................................................................
................................... done, booting the kernel.
Linux version 2.6.31-omap1 (Bob@domain.hid) (gcc version 4.3.3 (GCC) ) 
#1 Sun Jul 25 16:58:55 PDT 2010
CPU: ARMv7 Processor [411fc083] revision 3 (ARMv7), cr=10c53c7f
CPU: VIPT nonaliasing data cache, VIPT nonaliasing instruction cache
Machine: OMAP3 Beagle Board
Memory policy: ECC disabled, Data cache writeback
OMAP3430 ES3.0
SRAM: Mapped pa 0x40200000 to va 0xe3000000 size: 0x100000
Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 65024
Kernel command line: console=ttyS2,115200n8 
ip=192.168.1.81:192.168.1.80:192.168.1.1:255.255.255.0:beagleboard:et
h0:off root=/dev/nfs rw 
nfsroot=192.168.1.80:/home/Bob/NFSROOT,nolock,rsize=1024,wsize=1024 rootwait
PID hash table entries: 1024 (order: 10, 4096 bytes)
Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
Memory: 128MB 128MB = 256MB total
Memory: 255488KB available (3548K code, 412K data, 136K init, 0K highmem)
NR_IRQS:402
Clocking rate (Crystal/Core/MPU): 26.0/332/500 MHz
Reprogramming SDRC clock to 332000000 Hz
GPMC revision 5.0
IRQ: Found an INTC at 0xd8200000 (revision 4.0) with 96 interrupts
Total of 96 interrupts on 1 active controller
OMAP34xx GPIO hardware version 2.5
OMAP clockevent source: GPTIMER1 at 13000000 Hz
I-pipe 1.16-01: pipeline enabled.
Console: colour dummy device 80x30
Calibrating delay loop... 498.07 BogoMIPS (lpj=2490368)
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
regulator: core version 0.5
NET: Registered protocol family 16
Found NAND on CS0
Registering NAND on CS0
OMAP DMA hardware revision 4.0
bio: create slab <bio-0> at 0
i2c_omap i2c_omap.1: bus 1 rev3.12 at 2600 kHz
twl4030: PIH (irq 7) chaining IRQs 368..375
twl4030: power (irq 373) chaining IRQs 376..383
twl4030: gpio (irq 368) chaining IRQs 384..401
regulator: VMMC1: 1850 <--> 3150 mV normal standby
regulator: VDAC: 1800 mV normal standby
regulator: VUSB1V5: 1500 mV normal standby
regulator: VUSB1V8: 1800 mV normal standby
regulator: VUSB3V1: 3100 mV normal standby
regulator: VPLL2: 1800 mV normal standby
regulator: VSIM: 1800 <--> 3000 mV normal standby
i2c_omap i2c_omap.3: bus 3 rev3.12 at 100 kHz
SCSI subsystem initialized
twl4030_usb twl4030_usb: Initialized TWL4030 USB module
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
musb_hdrc: version 6.0, musb-dma, otg (peripheral+host), debug=0
musb_hdrc: USB OTG mode controller at d80ab000 using DMA, IRQ 92
NET: Registered protocol family 2
IP route cache hash table entries: 2048 (order: 1, 8192 bytes)
TCP established hash table entries: 8192 (order: 4, 65536 bytes)
TCP bind hash table entries: 8192 (order: 3, 32768 bytes)
TCP: Hash tables configured (established 8192 bind 8192)
TCP reno registered
NET: Registered protocol family 1
I-pipe: Domain Xenomai registered.
Xenomai: hal/arm started.
Xenomai: scheduling class idle registered.
Xenomai: scheduling class rt registered.
Xenomai: real-time nucleus v2.5.3 (Hordes Of Locusts) loaded.
Xenomai: starting native API services.
Xenomai: starting POSIX services.
Xenomai: starting RTDM services.
VFS: Disk quotas dquot_6.5.2
Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
JFFS2 version 2.2. (NAND) �© 2001-2006 Red Hat, Inc.
msgmni has been set to 499
alg: No test for stdrng (krng)
Block layer SCSI generic (bsg) driver version 0.4 loaded (major 253)
io scheduler noop registered
io scheduler anticipatory registered (default)
io scheduler deadline registered
io scheduler cfq registered
Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
serial8250.0: ttyS0 at MMIO 0x4806a000 (irq = 72) is a ST16654
serial8250.1: ttyS1 at MMIO 0x4806c000 (irq = 73) is a ST16654
serial8250.2: ttyS2 at MMIO 0x49020000 (irq = 74) is a ST16654
console [ttyS2] enabled
brd: module loaded
loop: module loaded
i2c /dev entries driver
usbcore: registered new interface driver asix
usbcore: registered new interface driver cdc_ether
usbcore: registered new interface driver net1080
usbcore: registered new interface driver cdc_subset
usbcore: registered new interface driver zaurus
usbmon: debugfs is not available
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
ehci-omap ehci-omap.0: OMAP-EHCI Host Controller
ehci-omap ehci-omap.0: new USB bus registered, assigned bus number 1
ehci-omap ehci-omap.0: irq 77, io mem 0x48064800
ehci-omap ehci-omap.0: USB 2.0 started, EHCI 1.00
usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb1: Product: OMAP-EHCI Host Controller
usb usb1: Manufacturer: Linux 2.6.31-omap1 ehci_hcd
usb usb1: SerialNumber: ehci-omap.0
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 3 ports detected
g_ether gadget: using random self ethernet address
g_ether gadget: using random host ethernet address
usb0: MAC 36:3c:3a:f5:b5:ed
usb0: HOST MAC ce:32:fc:bb:54:f2
g_ether gadget: Ethernet Gadget, version: Memorial Day 2008
g_ether gadget: g_ether ready
musb_hdrc musb_hdrc: MUSB HDRC host driver
musb_hdrc musb_hdrc: new USB bus registered, assigned bus number 2
usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb2: Product: MUSB HDRC host driver
usb usb2: Manufacturer: Linux 2.6.31-omap1 musb-hcd
usb usb2: SerialNumber: musb_hdrc
usb usb2: configuration #1 chosen from 1 choice
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 1 port detected
mmci-omap-hs mmci-omap-hs.0: Failed to get debounce clock
TCP cubic registered
NET: Registered protocol family 17
NET: Registered protocol family 15
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
Power Management for TI OMAP3.
VFP support v0.3: implementor 41 architecture 3 part 30 variant c rev 1
regulator_init_complete: incomplete constraints, leaving VDVI on
regulator_init_complete: incomplete constraints, leaving VDAC on
drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
usb 1-2: new high speed USB device using ehci-omap and address 2
mmc0: new high speed SD card at address dd7b
mmcblk0: mmc0:dd7b SD02G 1.87 GiB
  mmcblk0: p1 p2
usb 1-2: New USB device found, idVendor=0b95, idProduct=7720
usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
usb 1-2: Product: AX88772
usb 1-2: Manufacturer: ASIX Elec. Corp.
usb 1-2: SerialNumber: 000001
usb 1-2: configuration #1 chosen from 1 choice
eth0: register 'asix' at usb-ehci-omap.0-2, ASIX AX88772 USB 2.0 
Ethernet, 00:50:b6:05:d2:0c
eth0: link down
eth0: link up, 100Mbps, half-duplex, lpa 0x40A1
IP-Config: Complete:
      device=eth0, addr=192.168.1.81, mask=255.255.255.0, gw=192.168.1.1,
      host=beagleboard, domain=, nis-domain=(none),
      bootserver=192.168.1.80, rootserver=192.168.1.80, rootpath=
Looking up port of RPC 100003/2 on 192.168.1.80
Looking up port of RPC 100005/1 on 192.168.1.80
VFS: Mounted root (nfs filesystem) on device 0:13.
Freeing init memory: 136K
INIT: version 2.86 booting
Please wait: booting...
Starting udev
EXT2-fs warning (device mmcblk0p2): ext2_fill_super: mounting ext3 
filesystem as ext2
Remounting root file system...
Caching udev devnodes
Populating dev cache
root: mount: mounting rootfs on / failed: No such file or directory
NOT configuring network interfaces: / is an NFS mount
hwclock: can't open '/dev/misc/rtc': No such file or directory
Tue May 18 20:58:00 UTC 2010
hwclock: can't open '/dev/misc/rtc': No such file or directory
Configuring update-modules.
Starting to configure packages...
Nothing to be done
Finished to configure packages.
INIT: Entering runlevel: 5
Creating Dropbear SSH server RSA host key.
Will output 1024 bit rsa secret key to '/etc/dropbear/dropbear_rsa_host_key'
Generating key, this may take a while...
Public key portion is:
ssh-rsa 
AAAAB3NzaC1yc2EAAAADAQABAAAAgwCyuGR5NlHYDfmcD6+zGcZ6PKDReZKrofcLvBt3gMLNTnH55vAvOf+xvuWsPQCjBjEs/6EqSV1z/
CvhafTDQcEHvyPf6NRLAdeYF8IT8JIwZQZXUOVazcY0uL3xsfBeGKOdt9XKTc4JOD/xrZhFixKETXKC1ZY0CLA7h+su1N6NufHH 
root@domain.hid
ard
Fingerprint: md5 87:48:4b:38:af:ed:85:7f:0f:c3:49:17:96:1a:14:6d
Starting Dropbear SSH server: dropbear.
Starting syslogd/klogd: done

.-------.
|       |                  .-.
|   |   |-----.-----.-----.| |   .----..-----.-----.
|       |     | __  |  ---'| '--.|  .-'|     |     |
|   |   |  |  |     |---  ||  --'|  |  |  '  | | | |
'---'---'--'--'--.  |-----''----''--'  '-----'-'-'-'
                 -'  |
                 '---'

The Angstrom Distribution beagleboard ttyS2

Angstrom 2010.4-test-20100518 beagleboard ttyS2

beagleboard login: root
root@domain.hid:~# df
Filesystem           1K-blocks      Used Available Use% Mounted on
/dev/root             15868228   8777056   6930152  56% /
none                    127896       132    127764   0% /dev
/dev/mmcblk0p1          197676      2190    195487   1% /media/mmcblk0p1
/dev/mmcblk0p2         1731460     35396   1608112   2% /media/mmcblk0p2
tmpfs                   127896        16    127880   0% /var/volatile
tmpfs                   127896         0    127896   0% /dev/shm
tmpfs                   127896         0    127896   0% /media/ram
root@domain.hid:~# cat /proc/interrupts
            CPU0
   7:          2        INTC  TWL4030-PIH
  11:          0        INTC  prcm
  12:       3238        INTC  DMA
  37:       1833        INTC  gp timer
  56:        273        INTC  i2c_omap
  61:          0        INTC  i2c_omap
  72:          1        INTC  serial idle
  73:          1        INTC  serial idle
  74:        188        INTC  serial idle, serial
  77:      13354        INTC  ehci_hcd:usb1
  83:       6343        INTC  mmc0
  92:          1        INTC  musb_hdrc
  93:          0        INTC  musb_hdrc
378:          2     twl4030  twl4030_usb
384:          0     twl4030  mmc0
Err:          0
root@domain.hid:~# umount /dev/mmcblk0p1
root@domain.hid:~# umount /dev/mmcblk0p2
root@domain.hid:~#
root@domain.hid:~# # removing SD card
root@domain.hid:~#
root@domain.hid:~# mmc0: card dd7b removed

root@domain.hid:~# cat /proc/interrupts
            CPU0
   7:          3        INTC  TWL4030-PIH
  11:          0        INTC  prcm
  12:       3245        INTC  DMA
  37:       2575        INTC  gp timer
  56:        294        INTC  i2c_omap
  61:          0        INTC  i2c_omap
  72:          1        INTC  serial idle
  73:          1        INTC  serial idle
  74:        321        INTC  serial idle, serial
  77:      14305        INTC  ehci_hcd:usb1
  83:       6599        INTC  mmc0
  92:          1        INTC  musb_hdrc
  93:          0        INTC  musb_hdrc
378:          2     twl4030  twl4030_usb
384:          1     twl4030  mmc0
Err:          0
root@domain.hid:~# df
Filesystem           1K-blocks      Used Available Use% Mounted on
/dev/root             15868228   8777056   6930152  56% /
none                    127896       120    127776   0% /dev
tmpfs                   127896        16    127880   0% /var/volatile
tmpfs                   127896         0    127896   0% /dev/shm
tmpfs                   127896         0    127896   0% /media/ram
root@domain.hid:~#
root@domain.hid:~# # inserting SD card
root@domain.hid:~#
root@domain.hid:~# mmc0: new high speed SD card at address dd7b
mmcblk0: mmc0:dd7b SD02G 1.87 GiB
  mmcblk0: p1 p2
EXT2-fs warning (device mmcblk0p2): ext2_fill_super: mounting ext3 
filesystem as ext2

root@domain.hid:~# df
Filesystem           1K-blocks      Used Available Use% Mounted on
/dev/root             15868228   8777056   6930152  56% /
none                    127896       132    127764   0% /dev
tmpfs                   127896        16    127880   0% /var/volatile
tmpfs                   127896         0    127896   0% /dev/shm
tmpfs                   127896         0    127896   0% /media/ram
/dev/mmcblk0p2         1731460     35396   1608112   2% /media/mmcblk0p2
/dev/mmcblk0p1          197676      2190    195487   1% /media/mmcblk0p1
root@domain.hid:~# cat /proc/interrupts
            CPU0
   7:          4        INTC  TWL4030-PIH
  11:          0        INTC  prcm
  12:       6482        INTC  DMA
  37:       3246        INTC  gp timer
  56:        317        INTC  i2c_omap
  61:          0        INTC  i2c_omap
  72:          1        INTC  serial idle
  73:          1        INTC  serial idle
  74:        463        INTC  serial idle, serial
  77:      15483        INTC  ehci_hcd:usb1
  83:      12938        INTC  mmc0
  92:          1        INTC  musb_hdrc
  93:          0        INTC  musb_hdrc
378:          2     twl4030  twl4030_usb
384:          2     twl4030  mmc0
Err:          0

Note that twl_4030_usb interrupts are being passed too.
Thanks Gilles. Great job!
Regards,
Bob feretich

On 7/25/2010 2:24 AM, Gilles Chanteperdrix wrote:
> Bob Feretich wrote:
>>    Test 1 results:
>> With the Adeos patch installed, but Adeos disabled, the system ran
>> normally. IRQ 384s were presented and serviced.  (The SD card removal
>> amd insertion was handled correctly.)
> Ok. Could you try the following patch? It fixes the "always growing PIH
> interrupt count" number here, and now I have some twl4030_usb
> interrupts. However, I could not test the SD card insertion/removal,
> because I am working on the board remotely.
>
> diff --git a/drivers/i2c/busses/i2c-omap.c b/drivers/i2c/busses/i2c-omap.c
> index 8d608a1..0037e31 100644
> --- a/drivers/i2c/busses/i2c-omap.c
> +++ b/drivers/i2c/busses/i2c-omap.c
> @@ -478,10 +478,6 @@ static int omap_i2c_xfer_msg(struct i2c_adapter *adap,
>   	if (msg->len == 0)
>   		return -EINVAL;
>
> -#ifdef CONFIG_IPIPE
> -	disable_irq(dev->irq);
> -#endif /* CONFIG_IPIPE */
> -
>   	omap_i2c_write_reg(dev, OMAP_I2C_SA_REG, msg->addr);
>
>   	/* REVISIT: Could the STB bit of I2C_CON be used with probing? */
> @@ -525,9 +521,6 @@ static int omap_i2c_xfer_msg(struct i2c_adapter *adap,
>
>   			/* Let the user know if i2c is in a bad state */
>   			if (time_after(jiffies, delay)) {
> -#ifdef CONFIG_IPIPE
> -				enable_irq(dev->irq);
> -#endif /* CONFIG_IPIPE */
>   				dev_err(dev->dev, "controller timed out "
>   				"waiting for start condition to finish\n");
>   				return -ETIMEDOUT;
> @@ -539,9 +532,6 @@ static int omap_i2c_xfer_msg(struct i2c_adapter *adap,
>   		w&= ~OMAP_I2C_CON_STT;
>   		omap_i2c_write_reg(dev, OMAP_I2C_CON_REG, w);
>   	}
> -#ifdef CONFIG_IPIPE
> -	enable_irq(dev->irq);
> -#endif /* CONFIG_IPIPE */
>
>   	/*
>   	 * REVISIT: We should abort the transfer on signals, but the bus goes
> diff --git a/drivers/mfd/twl4030-irq.c b/drivers/mfd/twl4030-irq.c
> index 9df9a5a..fb4b9f2 100644
> --- a/drivers/mfd/twl4030-irq.c
> +++ b/drivers/mfd/twl4030-irq.c
> @@ -332,7 +332,7 @@ static int twl4030_irq_thread(void *data)
>   					note_interrupt(module_irq, d,
>   							IRQ_NONE);
>   				else
> -					d->handle_irq(module_irq, d);
> +					ipipe_handle_irq_cond(module_irq);
>   			}
>   		}
>   		local_irq_enable();
>

[-- Attachment #2: Type: text/html, Size: 54525 bytes --]

Re: [Xenomai-help] Adeos patch prevents IRQ 384 (MMC Chip Detect) on omap-2.6.33 - working now

[Gilles Chanteperdrix]

Bob Feretich wrote:
>    I applied the below patches to the 2.6.33 BeagleBoard system, they
> WORKED.
> Then I edited the 2.6.31 kernel to reflect the same patches, it WORKED too!

At last! Thanks for the good news.

-- 
					    Gilles.