linux-kernel - mvsas determines most often an incorrect phy addr of 0 while attaching phy to port (Was: ERROR: Unidentified device type 0)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Sun, 07 Dec 2008 00:01:25 +0100
From:	Reinhard Nissl <rnissl@....de>
To:	linux-kernel@...r.kernel.org
CC:	kewei@...vell.com
Subject: mvsas determines most often an incorrect phy addr of 0 while attaching
 phy to port (Was: ERROR: Unidentified device type 0)

Hi,

I've meanwhile investigated this issue a little bit further and
changed the subject accordingly.

Reinhard Nissl schrieb:

> I've got the ASUS P6T WS Professional mainboard including Marvell
> 88SE6320 SAS controller and attached a single Seagate 10k6 SAS
> harddrive to the first SAS port.
> 
> Installation of openSUSE 11.1rc1 went well but after rebooting,
> the harddrive doesn't get found. When the initrd script loads the
> mvsas module, the following output appears on screen:
> 
> sas: phy-10:1 added to port-10:0, phy_mask:0x2 (             0)
> ERROR: Unidentified device type 0
> 
> I first tried to install openSUSE 11.0 but the installer didn't
> find the harddrive. If I recall correctly, it was for the same
> reason as it is now when trying to boot the 11.1rc1 system.

This was not completely correct. I forgot that the 11.0 installer
saw the drive at least once. And my investigations today showed
that the 11.1rc1 installer / rescue system can run into the same
error. But most often they see the drive (sometimes only after a
power cycle) while initrd didn't succeed at all (looks like a
timing issue).

> So I think, there exists already a fix for this issue, as the
> 11.1rc1 installer sees the drive, which is still missing in the
> initrd environment.
> 
> I really would like to help solving this issue, but I need a
> pointer where and how to start digging. I've started a openSUSE
> bug (https://bugzilla.novell.com/show_bug.cgi?id=450302, Bug
> 450302 - mvsas doesn't find SAS drive anymore after installation)
> almost a week ago but didn't get much help there.

Some more findings:
After the rescue system booted successfully and detected the
drive, I tried to unload mvsas. modprobe -r mvsas didn't succeed
as the module was still in use, but lsmod didn't report any user.
So I've unloaded mvsas with rmmod -f mvsas which succeeded. After
that, modprobe mvsas was loading the module successfully again
but the above error appeared. I've put up a loop with modprobe -r
/ modprobe but it never succeeded to detect the drive anymore.

My plans for the next days are to attach a SATA drive to one of
the south bridge SATA ports, install an openSUSE system there
which I will use to investigate this issue further, i. e. setup a
build environment to be able to compile the module, activate (and
possibly add additional) debug output and load the module without
having to reboot.

I really hope that someone will drop me some lines to guide me in
investigating this issue. Thanks in advance.

Bye.
-- 
Dipl.-Inform. (FH) Reinhard Nissl
mailto:rnissl@....de
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/