Kernel 3.5 ‘hang’ on the Dreamplug..
Been trying the ‘released’ version of kernel 3.5 on my Dreamplug, and at first the hang appeared to be due to the fact that 3.5 didn’t detect the Marvell Orion USB controller, but now there is another problem (see Update below..):
‘Good’ boot (3.4.5):
mv_xor mv_xor.3: Marvell XOR: ( xor fill cpy )Serial: 8250/16550 driver, 2 ports, IRQ sharing disabled
serial8250.0: ttyS0 at MMIO 0xf1012000 (irq = 33) is a 16550A
console [ttyS0] enabled
brd: module loaded
loop: module loaded
ehci_hcd: USB 2.0 ‘Enhanced’ Host Controller (EHCI) Driver
orion-ehci orion-ehci.0: Marvell Orion EHCI
orion-ehci orion-ehci.0: new USB bus registered, assigned bus number 1
orion-ehci orion-ehci.0: irq 19, io mem 0xf1050000
orion-ehci orion-ehci.0: USB 2.0 started, EHCI 1.00
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 1 port detected
Initializing USB Mass Storage driver…
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
usbcore: registered new interface driver ums-datafab
usbcore: registered new interface driver ums-freecom
usbcore: registered new interface driver ums-jumpshot
mousedev: PS/2 mouse device common for all mice
rtc-mv rtc-mv: rtc core: registered rtc-mv as rtc0
i2c /dev entries driver
sdhci: Secure Digital Host Controller Interface driver
sdhci: Copyright(c) Pierre Ossman
mmc0: mvsdio driver initialized, lacking card detect (fall back to polling)
sdhci-pltfm: SDHCI platform and OF driver helper
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
oprofile: hardware counters not available
oprofile: using timer interrupt.
TCP: cubic registered
NET: Registered protocol family 17
lib80211: common routines for IEEE802.11 drivers
Registering the dns_resolver key type
rtc-mv rtc-mv: setting system clock to 2012-07-30 18:21:13 UTC (1343672473)
Waiting 10sec before mounting root device…
mmc0: new high speed SDIO card at address 0001
usb 1-1: new high-speed USB device number 2 using orion-ehci
hub 1-1:1.0: USB hub found
hub 1-1:1.0: 4 ports detected
usb 1-1.1: new high-speed USB device number 3 using orion-ehci
………… boot continues successfully ……………
‘Bad boot (3.5.0)
mv_xor mv_xor.3: Marvell XOR: ( xor fill cpy )Serial: 8250/16550 driver, 2 ports, IRQ sharing disabled
serial8250.0: ttyS0 at MMIO 0xf1012000 (irq = 33) is a 16550A
console [ttyS0] enabled
brd: module loaded
loop: module loaded
ehci_hcd: USB 2.0 ‘Enhanced’ Host Controller (EHCI) Driver
ohci_hcd: USB 1.1 ‘Open’ Host Controller (OHCI) Driver
Initializing USB Mass Storage driver…
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
mousedev: PS/2 mouse device common for all mice
rtc-mv rtc-mv: rtc core: registered rtc-mv as rtc0
i2c /dev entries driver
sdhci: Secure Digital Host Controller Interface driver
sdhci: Copyright(c) Pierre Ossman
mmc0: mvsdio driver initialized, lacking card detect (fall back to polling)
sdhci-pltfm: SDHCI platform and OF driver helper
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
oprofile: hardware counters not available
oprofile: using timer interrupt.
TCP: cubic registered
NET: Registered protocol family 17
lib80211: common routines for IEEE802.11 drivers
Key type dns_resolver registered
rtc-mv rtc-mv: setting system clock to 2012-07-30 18:27:10 UTC (1343672830)<<<< HANG >>>>
Update: Fixed the orion-ehci detection, but still doesn’t boot.. Back to the drawing board..
ehci_hcd: USB 2.0 ‘Enhanced’ Host Controller (EHCI) Driverorion-ehci orion-ehci.0: Marvell Orion EHCI
orion-ehci orion-ehci.0: new USB bus registered, assigned bus number 1
orion-ehci orion-ehci.0: irq 19, io mem 0xf1050000
orion-ehci orion-ehci.0: USB 2.0 started, EHCI 1.00
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 1 port detected
Initializing USB Mass Storage driver…
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
usbcore: registered new interface driver ums-datafab
usbcore: registered new interface driver ums-freecom
usbcore: registered new interface driver ums-jumpshot
mousedev: PS/2 mouse device common for all mice
rtc-mv rtc-mv: rtc core: registered rtc-mv as rtc0
i2c /dev entries driver
sdhci: Secure Digital Host Controller Interface driver
sdhci: Copyright(c) Pierre Ossman
mmc0: mvsdio driver initialized, lacking card detect (fall back to polling)
sdhci-pltfm: SDHCI platform and OF driver helper
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
oprofile: hardware counters not available
oprofile: using timer interrupt.
TCP: cubic registered
NET: Registered protocol family 17
lib80211: common routines for IEEE802.11 drivers
Key type dns_resolver registered
rtc-mv rtc-mv: setting system clock to 2012-07-30 22:16:57 UTC (1343686617)
<< HANG >>
Have you found a workaround for this? I have the same problem on a sheevaplug. It hangs after
[ 14.527572] rtc-mv rtc-mv: setting system clock to 2012-09-22 08:02:14 UTC (1348300934)
After I found 3.6-rcX kernels booted OK, I just started using these, and they all boot – and run – with no apparent problem. I will be upgrading the Dreamplug to 3.6-rc7 shortly.. I used the same .config as I had for the 3.5 kernel, which ‘hung’.. I had previously found, when upgrading from the earlier to the later 3.x kernels, that you had to have the ’embedded system’ config options enabled, or the system would hang..