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

Bug#438337: marked as done (linux-source-2.6.18.dfsg.1-12etch2: Megaraid Legacy driver stopped working with IntelSRCU42x.)

Your message dated Fri, 2 Oct 2009 00:16:41 +0200
with message-id <20091001221641.GA9602@galadriel.inutil.org>
and subject line Re: Megaraid boot failure
has caused the Debian Bug report #438337,
regarding linux-source-2.6.18.dfsg.1-12etch2: Megaraid Legacy driver stopped working with IntelSRCU42x.
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.)


-- 
438337: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=438337
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: linux-source-2.6.18.dfsg.1-12etch2
Version: linux-source-2.6.18
Severity: normal



-- System Information:
Debian Release: 4.0
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-tcc
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)

After upgrading from sarge kernel-source-2.6.8 package to etch
linux-source-2.6.18, the Megaraid Legacy driver (known as megaraid in
kernel 2.6.8) stopped working. The RAID controller in use by the machine
is an Intel SRCU42x.

During the first machine boot with the new kernel, we got a kernel panic
stating the impossibility to mount the root partition.

The driver version included in the 2.6.8 linux kernel sources is the
2.00.3, while the version included in the 2.6.18 linux kernel sources is
the 2.00.4.

--- End Message ---
--- Begin Message --- 
On Wed, Nov 12, 2008 at 11:01:02PM +0100, Moritz Muehlenhoff wrote:
> On Thu, Apr 17, 2008 at 10:03:54PM +1200, Steven Jones wrote:
> > Hi,
> >
> > Unable to install Debian 4.0r3 as there is a lock up during hardware  
> > detection, would seem to be around the raid module.
> >
> > Installed 3.1 which went fine, upgraded to 4.0r3 using apt-get update ;  
> > apt-get -y dist-upgrade, went fine.
> >
> > Attempted to install a 2.6.18-6 kernel and the megaraid-mbox module  
> > enters a 300sec loop....so this bug is still outstanding.
> 
> Does this error still occur with more recent kernel versions?
> 
> If you're running Etch, could you try to reproduce this bug
> with the 2.6.24 based kernel added in 4.0r4?
> http://packages.qa.debian.org/l/linux-2.6.24.html

No further feedback, closing the bug. Please reopen if anyone can
reproduce the problem with a recent kernel.

Cheers,
        Moritz

--- End Message ---
Reply to: