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

Bug#707588: marked as done (md crash on DNS-323 (armel/orion5x))

Your message dated Sat, 24 Apr 2021 08:20:15 -0700 (PDT)
with message-id <6084372f.1c69fb81.64e42.88c1@mx.google.com>
and subject line Closing this bug (BTS maintenance for src:linux bugs)
has caused the Debian Bug report #707588,
regarding md crash on DNS-323 (armel/orion5x)
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.)


-- 
707588: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=707588
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: src:linux
Version: 3.2.41-2
Severity: normal
Tags: upstream

Dear Maintainer,

Upgraded to wheezy on a DNS-323. The upgrade worked more or 
less flawless in term of userpace. Unfortunately the wheezy
kernel crashes as mdadm starts assembling my raid1 array. 
If found that out by removing the HDDs form the DNS-323 and solely
booting from a USB stick. Hotplugging the HDDs still worked but
mdmadm-startall afterwards crashed the system. Downgrading to 2.6.32-5
resolved the issue.


** Model information
Processor	: Feroceon rev 0 (v5l)
Hardware	: D-Link DNS-323
Revision	: 0000

** PCI devices:
not available

** USB devices:
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 0781:5406 SanDisk Corp. Cruzer Micro U3


-- System Information:
Debian Release: 7.0
  APT prefers stable
  APT policy: (500, 'stable'), (500, 'oldstable')
Architecture: armel (armv5tel)

Kernel: Linux 2.6.32-5-orion5x
Locale: LANG=de_DE@euro, LC_CTYPE=de_DE@euro (charmap=ISO-8859-15)
Shell: /bin/sh linked to /bin/dash

Versions of packages linux-image-3.2.0-4-orion5x depends on:
ii  debconf [debconf-2.0]                   1.5.49
ii  initramfs-tools [linux-initramfs-tool]  0.109.1
ii  kmod                                    9-3
ii  linux-base                              3.5
ii  module-init-tools                       9-3

Versions of packages linux-image-3.2.0-4-orion5x recommends:
ii  firmware-linux-free  3.2
ii  uboot-mkimage        2012.04.01-2

Versions of packages linux-image-3.2.0-4-orion5x suggests:
pn  debian-kernel-handbook  <none>
pn  fdutils                 <none>
pn  linux-doc-3.2           <none>

Versions of packages linux-image-3.2.0-4-orion5x 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 excluded

--- End Message ---
--- Begin Message --- 
Hi

This bug was filed for a very old kernel or the bug is old itself
without resolution.

If you can reproduce it with

- the current version in unstable/testing
- the latest kernel from backports

please reopen the bug, see https://www.debian.org/Bugs/server-control
for details.

Regards,
Salvatore

--- End Message ---
Reply to: