[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#923021: marked as done (Kernel oops using Buster Alpha 5 armhf installer onto ClearFog Base)

Your message dated Tue, 04 Feb 2020 22:54:56 -0700
with message-id <ff97297b823f4d5240ab0caae74f048c@lixil.net>
and subject line Resolved in buster release images
has caused the Debian Bug report #923021,
regarding Kernel oops using Buster Alpha 5 armhf installer onto ClearFog Base
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
923021: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923021
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: installation-reports

Boot method: microSD card
Image version: http://ftp.debian.org/debian/dists/testing/main/installer-armhf/current/images/hd-media/hd-media.tar.gz 
Date: 2019-02-22T20:57:53-07:00

Machine: ClearFog Base
Processor: Marvell ARMADA A388 ARM A9
Memory: 1GB
Partitions: single ext4 partition, primary part 1

Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot:           [O]
Detect network card:    [E]
Configure network:      [ ]
Detect CD:              [O]
Load installer modules: [O]
Detect hard drives:     [O]
Partition hard drives:  [ ]
Install base system:    [ ]
Clock/timezone setup:   [ ]
User/password setup:    [ ]
Install tasks:          [ ]
Install boot loader:    [ ]
Overall install:        [ ]

Comments/Problems:
I encounter a consistent kernel oops when trying to install Debian onto a SolidRun ClearFog Base device. I previously attempted installation using the Buster Alpha 4 version of the installer, and have just retested using Alpha 5 version and get the same result. This particular device is using a self-compiled U-Boot version based on upstream sources at v2018.11.
To prepare the installation media, I downloaded the armhf hd-media archive [1], and then unpacked the contents into a single ext4 partition on a micro SD card. I then copied the armhf netinst ISO image to the root of the filesystem.
The installer boots successfully, goes through the language selection and location prompts, then proceeds to mount the mmcblk0 device, find the ISO image, and cycles through "Loading additional components". When it completes component loading, it proceed to detecting network devices, at which point I get a kernel oops dump like the one below. The installation happens via serial (USB FTDI) connection, so I apologize for the corruption in the capture of the message.
[ 68.717677] Unable to handle kernel paging request at virtual address 00002680 
[   68.725981] pgd = (ptrval)
[   68.730086] [00002680] *pgd=00000000
[   68.735082] Internal error: Oops: 5 [#1] SMP ARM
[ 68.741086] Modules linked in: marvell mvmdio(+) mvneta(+) mvneta_bm phylink sfp mdio_i2c nls_utf8 dm_mod loop isofs vfat fat ext4 crc16 mbcache jbd2 crc32c_generic fscrypto usb_storage sd_mod gpio_pca953x ehci_orion ahci_mve bu ehci_hcd libahci_platform libahci sdhci_pxav3 xhci_plat_hcd xhci_hcd sdhci_pltfm libata sdhci scsi_mod usbcore i2c_mv64xxx [ 68.772053] CPU: 0 PID: 13 Comm: kworker/0:1 Not tainted 4.19.0-1-armmp #1 Debian 4.19.12-1 
[   68.780422] Hardware name: Marvell Armada 380/385 (Device Tree)
[ 68.786370] Workqueue: events_power_efficient phylink_resolve [phylink] 
[   68.793033] PC is at mvneta_port_down+0x20/0x1a0 [mvneta]
[   68.798454] LR is at mvneta_mac_link_down+0x24/0x90 [mvneta]
[   68.804125] pc : [<bf51b2ec>]    lr : [<bf51b490>]    psr: 600b0013
[   68.810406] sp : ee96be60  ip : ee96be88  fp : ee96be84
[   68.815641] r10: 00000000  r9 : eef1c99c  r8 : eef1c900
[ 68.820876] r7 : eef1c960 r6 : ede82000 r5 : 00000002 r4 : ede82580 [ 68.827417] r3 : 00002680 r2 : 00000004 r1 : 00000002 r0 : ede82580 [ 68.833959] Flags: nZCv IRQs on FIQs on Mode SVC_32 ISA ARM Segment none 
[   68.841109] Control: 10c5387d  Table: 0fe9804a  DAC: 00000051
[   68.846867] Process kworker/0:1 (pid: 13, stack limit = 0x(ptrval))
[   68.853147] Stack: (0xee96be60 to 0xee96c000)
[ 68.857514] be60: ede82000 00000002 ede82000 eef1c960 eef1c900 eef1c99c ee96bea4 ee96be88 [ 68.865711] be80: bf51b490 bf51b2d8 eef1c998 c1105dcc ede82000 eef1c960 ee96befc ee96bea8 [ 68.873908] bea0: bf507000 bf51b478 c0aeb1e8 c037bc10 00000001 00000000 ee96bee4 ee96bec8 [ 68.882104] bec0: c04f637c c050ebdc 00000000 2e6b8000 c1018c40 4bd6f77b ee8d6180 eef1c998 [ 68.890301] bee0: ee8d6180 ef6d0840 ef6d3f00 00000000 ee96bf34 ee96bf00 c036c090 bf506eac [ 68.898497] bf00: 00000008 ef6d0858 c1104d00 ee8d6180 ee8d6194 ef6d0840 00000008 ef6d0858 [ 68.906695] bf20: c1104d00 ef6d0840 ee96bf74 ee96bf38 c036d0a4 c036bed4 ee8f6e40 c0c7436c [ 68.914891] bf40: c11f1428 ffffe000 c0372638 ee8f6600 ee8f6e40 00000000 ee96a000 ee8d6180 [ 68.923088] bf60: c036d044 ee957e74 ee96bfac ee96bf78 c0372b58 c036d050 ee8f661c ee8f661c [ 68.931285] bf80: ee96bfac ee8f6e40 c03729ec 00000000 00000000 00000000 00000000 00000000 [ 68.939482] bfa0: 00000000 ee96bfb0 c03010e8 c03729f8 00000000 00000000 00000000 00000000 [ 68.947678] bfc0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 [ 68.955875] bfe0: 00000000 00000000 00000000 00000000 00000013 00000000 00000000 00000000 [ 68.964102] [<bf51b2ec>] (mvneta_port_down [mvneta]) from [<bf51b490>] (mvneta_mac_link_down+0x24/0x90 [mvneta] ) ┌─────────────────────┤ Detecting network hardware ├──────────────────────┐ [ │ │ (phylink_resolve+0x160/0x2dc [phylin k]│ 0% │ [ │ │ cess_one_work+0x1c8/0x4a4) [ │ Detecting hardware, please wait... │ d+0x60/0x544) [ │ │ x174) [ └─────────────────────────────────────────────────────────────────────────┘ 2c) 
[
[ 69.021770] bfa0: 00000000 00000000 00000000 00000000 [ 69.029967] bfc0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 [ 69.038163] bfe0: 00000000 00000000 00000000 00000000 00000013 00000000 
[   69.044794] Code: e8bd4000 e5903014 e1a04000 e2833d9a (e5933000)
                [   69.050969] ---[ end trace e4a3242ef46025d6 ]---
[1] http://ftp.debian.org/debian/dists/testing/main/installer-armhf/current/images/hd-media/hd-media.tar.gz
[2] https://cdimage.debian.org/cdimage/buster_di_alpha5/armhf/iso-cd/debian-buster-DI-alpha5-armhf-netinst.iso
--- End Message ---
--- Begin Message --- In retesting this recently with Buster 10.2 armhf images (using the hd-media package from /debian/dists/buster/main/installer-armhf/20190702+deb10u2/images/hd-media/), the reported issue is no longer encountered, and installation completes successfully on a ClearFog Base. 

Joel

--- End Message ---
Reply to: