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

Bug#515201: marked as done (linux-image: sata drive connected via marvell controller crashes)

Your message dated Tue, 31 May 2011 05:37:13 +0100
with message-id <1306816633.4277.113.camel@localhost>
and subject line Re: Bug#515201: linux-image: sata drive connected via marvell controller crashes
has caused the Debian Bug report #515201,
regarding linux-image: sata drive connected via marvell controller crashes
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.)


-- 
515201: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=515201
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: linux-image
Severity: important

i have ASUS M2N32 WS Professionall mainboard with latest BIOS revision 2001.
it has two controllers for sata:
- standard (nvidia)
- marvell

and also i have two sata II disks:
 1 - with Debian 32-bit, kernel 2.6.26-1-686-bigmem - plugged in standard sata
 2 - with Debian 64-bit, kernel 2.6.26-1-amd64 - plugged in marvell sata

the standard sata controller works fine, but i have problems with the marvell.

* when booting disk 1 (disk 2 is connected to marvell controller) system does
not boot up correctly. it holds-on - see photo:

http://develop.euroimpex.pl/~marek/boot/dsc00226.jpg

last few lines of long display in a loop if waiting longer..

* when booting disk 1, with disk 2 unplugged, system starts fine ofcourse,
but when plugin disk 2 to marvell (when system is on), the message
'Disabling IRQ #16' appears in console and system hangs-up.

* i tried also bootup from disk 2 (marvell controller), the grub started,
kernel started to doing it's job, but it crashed - see photo:

http://develop.euroimpex.pl/~marek/boot/dsc00227.jpg

maybe i am doing something wrong? maybe my mainboard has a bug, or maybe
it's something wrong in kernel? or maybe i have badly configured IRQs in the 
BIOS? - not sure

cheers.



-- System Information:
Debian Release: 5.0
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)

Kernel: Linux 2.6.26-1-686-bigmem (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

--- End Message ---
--- Begin Message --- 
On Sun, 2010-05-02 at 20:49 +0200, Moritz Muehlenhoff wrote:
> On Mon, Nov 02, 2009 at 09:55:21PM +0100, Marek Poks wrote:
> > 
> > 
> > On 11/01/2009 01:40 AM, Ben Hutchings wrote:
> > >On Sat, 2009-10-31 at 20:30 +0100, Mark Poks wrote:
> > >[...]
> > >>I have latest lenny amd64 version (release 5.0.3 as i remember). it is
> > >>provided with kernel 2.6.26-19lenny1. marvell still does not work.
> > >
> > >OK, noted.
> > >
> > >>in few days i will test it with kernel 2.6.30-8~bpo50+1.
> > >
> > >Please do.
> > >
> > >Ben.
> > >
> > with kernel 2.6.30-8~bpo50+1 it still does not boot. it loops same
> > messages when trying to communicate device.
> 
> Hi,
> The next release of Debian (6.0, code name Squeeze) will be based
> on 2.6.32. Please test the current 2.6.32 from unstable/testing and tell
> us whether the problem persists. If so, we should report it upstream
> to the kernel.org developers.
> 
> The 2.6.32 kernel is available from packages.debian.org and can
> be installed in both Debian stable, testing and unstable
> installations.

Closing due to lack of response.

If you can reproduce this using a current kernel version, please let us
know.  I'm sorry I didn't progress this further when you reported
against Linux 2.6.30.  Unfortunately we have an overwhelming number of
open bug reports.

Ben.

-- 
Ben Hutchings
Once a job is fouled up, anything done to improve it makes it worse.

Attachment: signature.asc
Description: This is a digitally signed message part


--- End Message ---
Reply to: