Bug#717470: linux-image-3.10-1-kirkwood: Soft lockup in orion_nand booting on dreamplug

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

Bug#717470: linux-image-3.10-1-kirkwood: Soft lockup in orion_nand booting on dreamplug

Devin Carraway
Package: src:linux
Version: 3.10.1-1
Severity: normal

linux-image-3.10-1-kirkwood (also reproduced with 3.9-1-kirkwood) cannot boot
on a dreamplug; the boot hangs and the watchdog fires while down in
orion_nand code, which so far as I know is not even applicable to this
hardware.

Boot was off USB w/ root on eSATA, device flash was no longer involved.

-- Package-specific info:
** Kernel log: boot messages should be attached

** Model information
Processor : Feroceon 88FR131 rev 1 (v5l)
Hardware : Marvell GuruPlug Reference Board
Revision : 0000

** PCI devices:

** USB devices:
Bus 001 Device 002: ID 1a40:0101 Terminus Technology Inc. 4-Port HUB
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 003: ID 05e3:0726 Genesys Logic, Inc. SD Card Reader
Bus 001 Device 004: ID 0409:0059 NEC Corp. HighSpeed Hub
Bus 001 Device 005: ID 0d8c:000c C-Media Electronics, Inc. Audio Adapter
Bus 001 Device 006: ID 1058:1003 Western Digital Technologies, Inc. Elements 1000 GB
Bus 001 Device 007: ID 1058:1003 Western Digital Technologies, Inc. Elements 1000 GB


-- System Information:
Debian Release: jessie/sid
  APT prefers testing
  APT policy: (990, 'testing'), (300, 'unstable')
Architecture: armel (armv5tel)

Kernel: Linux 3.4.5 (PREEMPT)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash

Versions of packages linux-image-3.10-1-kirkwood depends on:
ii  debconf [debconf-2.0]                   1.5.50
ii  initramfs-tools [linux-initramfs-tool]  0.113
ii  kmod                                    9-3
ii  linux-base                              3.5
ii  module-init-tools                       9-3

Versions of packages linux-image-3.10-1-kirkwood recommends:
ii  firmware-linux-free  3.2
ii  uboot-mkimage        2012.04.01-2

Versions of packages linux-image-3.10-1-kirkwood suggests:
pn  debian-kernel-handbook  <none>
pn  fdutils                 <none>
pn  linux-doc-3.10          <none>

Versions of packages linux-image-3.10-1-kirkwood is related to:
pn  firmware-atheros        <none>
pn  firmware-bnx2           <none>
pn  firmware-bnx2x          <none>
pn  firmware-brcm80211      <none>
pn  firmware-intelwimax     <none>
pn  firmware-ipw2x00        <none>
pn  firmware-ivtv           <none>
pn  firmware-iwlwifi        <none>
pn  firmware-libertas       <none>
pn  firmware-linux          <none>
pn  firmware-linux-nonfree  <none>
pn  firmware-myricom        <none>
pn  firmware-netxen         <none>
pn  firmware-qlogic         <none>
pn  firmware-ralink         <none>
pn  firmware-realtek        <none>
pn  xen-hypervisor          <none>

-- debconf information:
  linux-image-3.10-1-kirkwood/postinst/depmod-error-initrd-3.10-1-kirkwood: false
* linux-image-3.10-1-kirkwood/postinst/missing-firmware-3.10-1-kirkwood:
  linux-image-3.10-1-kirkwood/prerm/removing-running-kernel-3.10-1-kirkwood: true
  linux-image-3.10-1-kirkwood/postinst/ignoring-ramdisk:

boot-3.10-1-kirkwood (17K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Bug#717470: linux-image-3.10-1-kirkwood: Soft lockup in orion_nand booting on dreamplug

Martin Michlmayr
* Devin Carraway <[hidden email]> [2013-07-20 23:44]:
> linux-image-3.10-1-kirkwood (also reproduced with 3.9-1-kirkwood) cannot boot
> on a dreamplug; the boot hangs and the watchdog fires while down in
> orion_nand code, which so far as I know is not even applicable to this
> hardware.

* Seb35 <[hidden email]> [2014-03-10 20:15]:
> I experienced this bug in Debian 7 Wheezy with the Linux kernels
> 2.6.32-5-kirkwood, 3.2.0-4-kirkwood, and 3.12-0.bpo.1-kirkwood on a
> DreamPlug model 003-DS2001 (Feroceon 88FR131 rev 1 (v5l)). This was resolved
> by compiling Linux (3.2.0-4-kirkwood) without the CONFIG_MTD_NAND_ORION
> option.

Has this been fixed or is that still an issue?

--
Martin Michlmayr
https://www.cyrius.com/