FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Debian > Debian Kernel

 
 
LinkBack Thread Tools
 
Old 10-31-2009, 11:37 PM
Ben Hutchings
 
Default Bug#515201: linux-image: sata drive connected via marvell controller crashes

-------- Forwarded Message --------
From: Mark Poks <markpoks@gmail.com>
To: Ben Hutchings <ben@decadent.org.uk>
Subject: Re: linux-image: sata drive connected via marvell controller crashes
Date: Sat, 31 Oct 2009 20:30:28 +0100


On 10/25/2009 04:52 PM, Ben Hutchings wrote:
> On Sat, 2009-02-14 at 19:35 +0100, Mark Poks wrote:
>
>> Package: linux-image
>> Severity: important
>>
>
> I'm sorry for the delay in answering your bug report.
>
>
>> 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
>>
>
> IRQ configuration should be automatic, the exception being when there is
> a BIOS bug that we need to override.
>
> I believe that this was fixed in linux-2.6 version 2.6.26-14, which was
> included in stable update 5.0.1. Please can you report whether this bug
> is now fixed?
>
> Ben.
>
>

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. in
few days i will test it with kernel 2.6.30-8~bpo50+1.

Mark.




--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
 
Old 05-02-2010, 06:49 PM
Moritz Muehlenhoff
 
Default Bug#515201: linux-image: sata drive connected via marvell controller crashes

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.

Thanks,
Moritz



--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20100502184940.GA6477@galadriel.inutil.org">http://lists.debian.org/20100502184940.GA6477@galadriel.inutil.org
 
Old 06-19-2011, 04:29 AM
Jonathan Nieder
 
Default Bug#515201: linux-image: sata drive connected via marvell controller crashes

found 515201 linux-2.6/2.6.30-8~bpo50+1
found 515201 linux-2.6/2.6.32-34squeeze1
quit

Hi Eduardo,

egross@bol.com.br wrote:

> The following link (http://wiki.debian.org/pata_marvell) deals with
> the issue in debian lenny. I tried it and it works also with my
> squeeze kernel, 2.6.32-5-amd64.

Interesting. For reference, that page suggests:

1. Enable the Marvell controller in the BIOS.
2. Disable the pata_marvell module, by putting a .conf file with

install pata_marvell /bin/true

in /etc/modprobe.d.
3. Pass the marvell_enable=1 parameter to the ahci module, by putting
a .conf file with

options ahci marvell_enable=1

in /etc/modprobe.d.

and regenerating the initramfs. Do you know whether it is (2) or (3)
that causes your system to boot correctly?

The photos from Mark's original report are (understandably) no longer
online. Could you describe the messages from bootup, for example by
taking a new photo?

If you have time for it, it would also be nice to try a 3.0 release
candidate from experimental and see if that changes anything (it
probably won't, but it's good to check).

https://bugzilla.kernel.org/show_bug.cgi?id=12075 upstream has some
pointers.

Thanks much.
Jonathan



--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20110619042950.GB12195@elie">http://lists.debian.org/20110619042950.GB12195@elie
 
Old 06-19-2011, 10:51 AM
Jonathan Nieder
 
Default Bug#515201: linux-image: sata drive connected via marvell controller crashes

Hi,

mark poks wrote:

> unfortunatelly i have no longer mainboard with marvell controller (in fact i
> have, but it lays somewhere unplugged), so i can't make new foto.
> but i will try to find that removed foto - maybe it's still in a backup
> (i'll let you know if found)....

No problem. Eduardo seems to be experiencing the same problem, so
hopefully we will have more data soon.

Sorry this has been sitting for so long.



--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20110619105146.GB19963@elie">http://lists.debian.org/20110619105146.GB19963@elie
 
Old 06-19-2011, 09:57 PM
Jonathan Nieder
 
Default Bug#515201: linux-image: sata drive connected via marvell controller crashes

tags 515201 + upstream
quit

(cc-ing the bug log)
egross@bol.com.br wrote:

> I booted with the initrd (2.6.32-5-amd64) which came with the last
> update of squeeze, in order to copy the error messages, and now it
> boots correctly with my marvel external sata connected! So, the
> problem is not with the initrd. Only putting the commands suggested
> by that site in modprobe.d solve the problem.
>
> Trying to get the previous error messages, I removed the suggested
> commands in modprobe.d/. Removing only the second (options ahci
> marvell_enable=1), the error on boot occurs again:
>
> xxxxx
> "[ 11.516226] ata6.01: failed to IDENTIFY (I/O error, err_mask=0x4)
> [ 16.556015] ata6: link is slow to respond, please be patient (ready=0)
> [ 21.540016] ata6: device not ready (errno=-16), forcing hardreset
> [ 26.848015] ata6: link is slow to respond, please be patient (ready=0)
> [ 31.552016] ata6: SRST failed (errno=-16)
> [ 36.861014] ata6: link is slow to respond, please be patient (ready=0)
> [ 41.564018] ata6: SRST failed (errno=-16)
> [ 46.872017] ata6: link is slow to respond, please be patient (ready=0)
> [ 76.612017] ata6: SRST failed (errno=-16)
> [ 81.640014] ata6: SRST failed (errno=-16)
> [ 81.640087] ata6: reset failed, giving up
> [ 86.680014] ata6: link is slow to respond, please be patient (ready=0)
> [ 91.664017] ata6: device not ready (errno=-16), forcing hardreset
> [ 91.664096] ata6: soft resetting link
> [ 96.972016] ata6: link is slow to respond, please be patient (ready=0)
> [ 101.676016] ata6: SRST failed (errno=-16)
> [ 101.676092] ata6: soft resetting link
> [ 106.988014] ata6: link is slow to respond, please be patient (ready=0)
> [ 111.692013] ata6: SRST failed (errno=-16)
> [ 111.692088] ata6: soft resetting link
> [ 117.004011] ata6: link is slow to respond, please be patient (ready=0)
> [ 146.744017] ata6: SRST failed (errno=-16)
> [ 146.744094] ata6: soft resetting link
> [ 151.772016] ata6: SRST failed (errno=-16)
> [ 151.772089] ata6: reset failed, giving up
> [ 151.772161] ata6: EH complete"
> xxxxxxx
>
> After these error messages, boot continues, but it takes a very long
> time.
>
> Then I changed the archive in modprobe.d, and removed only the first
> suggested entry (install pata_marvell /bin/true). Now, the pc boots
> normally.
>
> I cannot say if this occurs because the other command has already
> been entered before, once I only did what the consulted site
> suggested, without a clear knowledge about what the commands mean in
> detail. Anyway, now only the second command is needed in an archive
> in the directory modprobe.d in order to all work well - boot does
> not fail and the external drive connected to sata controller works
> perfectly. So, the main command seems to be "options ahci
> marvell_enable=1".

Thanks for checking. So it seems the fundamental thing is to teach
Linux to automatically detect when the ahci driver can be used,
instead of requiring it to be specified on the module command line.

The source (drivers/ata/ahci.c) says:

/* The AHCI driver can only drive the SATA ports, the PATA driver
can drive them all so if both drivers are selected make sure
AHCI stays out of the way */

Yuck! I guess one way to move forward would be to teach the AHCI
driver to drive the PATA ports, or to detect if anything is connected
to the PATA ports and only engage this safety in that case.

In any event, I think this is ready to be passed upstream. Could you
report it at bugzilla.kernel.org, Product IO/Storage, Component Serial
ATA and send us the bug number for tracking? Thanks much.



--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20110619215754.GD23893@elie">http://lists.debian.org/20110619215754.GD23893@elie
 
Old 06-19-2011, 11:35 PM
Jonathan Nieder
 
Default Bug#515201: linux-image: sata drive connected via marvell controller crashes

Hi Eduardo,

egross@bol.com.br wrote:

> I am pleased to help with this. But I never reported something like
> that. If I copy our messages and send them to people at
> bugzilla.kernel.org would that be okay? Because I do not know
> programming language, and your formulation may be better understood
> than any try I would make in reproducing it.

Ah, sorry for the lack of clarity. I would suggest describing the
symptoms (attaching a full dmesg if possible) and saying something
like "see http://bugs.debian.org/515201 for some armchair analysis" at
the end.

To summarize, as far as I can tell:

- this is a bug in the "pata_marvell" driver

- the "ahci" driver also knows how to work with these controllers,
and a good workaround for systems with no PATA drives is to ask
that driver to claim the device, using the marvell_enable option

- the "ahci" driver seems to be better maintained, which is why I
suggested that enhancing it to completely supersede pata_marvell
might be a good way to go. Of course, another possibility is to
fix pata_marvell. Upstream will know what to do.

Cheers,
Jonathan



--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20110619233530.GI23893@elie">http://lists.debian.org/20110619233530.GI23893@elie
 
Old 06-20-2011, 08:29 PM
Jonathan Nieder
 
Default Bug#515201: linux-image: sata drive connected via marvell controller crashes

forwarded 515201 https://bugzilla.kernel.org/show_bug.cgi?id=12075
quit

egross@bol.com.br wrote:

> I put a message on bugzilla.kernel.org, on bug report 12075. I found
> two reports on Marvell sata controllers, and chose the most recent
> one, in spite of the fact that it deals with 6145 controller, while
> mine is a 6121. But, as I understand, the issue is the same.

Thanks, Eduardo. Marking accordingly.



--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20110620202900.GA32275@elie">http://lists.debian.org/20110620202900.GA32275@elie
 

Thread Tools




All times are GMT. The time now is 09:57 PM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org