Strange behaviour of ahci driver (intel 82801 Mobile SATA Controller)

Bug #1376661 reported by Kick In on 2014-10-02
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)

Bug Description


I have a MSI GS60E Ghost Pro laptop. It is quite complex:

2 SSD in raid 0 (intel Raid)
1 HDD standard SATA
2 Gpus (intel and nvidia)

I was trying to upgrade my trusty to utopic.

On trusty if I remember well there was no way to have a functionnal intel raid disks. I had to delete the raid an go to 2 separate disks to take advantage of the SSD (involved reinstalling secondary OS used for gaming).

Legacy boot:
On utopic, I can now use it but the name of the device is still strange (don't know if it is expected, but on other scsi harware I had I always had standard names /dev/sdx...):

/dev/mapper/isw_ihbcddegh_SSD, where SSD is the name given at raid creation of the volume.

Despite of this device I still have access to bare device /dev/sda, /dev/sdb, with the added bonus of being able to destroy the raid on it if we let the default /dev/sda for grub install of utopic desktop (destroyed at the end of install).

At install time we see /dev/mapper/isw_.... /dev/sda /dev/sdb and /dev/sdc, but it is readable on legacy installer even if not ideal.

UEFI boot:
If we boot on UEFI, it is more complex, as grub is not able to find the windows bootmanager for unknown reason (maybe not related).

Don't know if I need to put it somewhere else, but at the install selection of disks and partitions, it is also a bit confusing as it show two devices for the raid /dev/mapper/isw_.... each with the copy of the partitions (split the raid) plus bare devices, /dev/sda, /dev/sdb. I don't remember, if I saw partitions on the bare devices equaly.

I can make some undestructive tests for you (had hard time at making a working install on this machine). If really needed, I can switch to work on an other laptop, and go for destructive tests.

You can find some hardware infos about the config there, setup, etc:
ApportVersion: 2.14.7-0ubuntu2
Architecture: amd64
 /dev/snd/controlC0: kick 3322 F.... pulseaudio
 /dev/snd/controlC2: kick 3322 F.... pulseaudio
 /dev/snd/controlC1: kick 3322 F.... pulseaudio
CurrentDesktop: Unity
DistroRelease: Ubuntu 14.10
HibernationDevice: RESUME=UUID=46a8dc48-0696-4cc1-9ba5-6718ccae8802
InstallationDate: Installed on 2014-10-01 (0 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140923)
MachineType: Micro-Star International Co., Ltd. GS60 2PE
Package: linux (not installed)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-17-generic root=UUID=71fadb93-5ab3-4fab-98d7-e558816e33a0 ro quiet splash blacklist=nouveau
ProcVersionSignature: Ubuntu 3.16.0-17.23-generic 3.16.3
 linux-restricted-modules-3.16.0-17-generic N/A
 linux-backports-modules-3.16.0-17-generic N/A
 linux-firmware 1.134
Tags: utopic
Uname: Linux 3.16.0-17-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True 08/16/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: E16H2IMS.10B
dmi.board.asset.tag: To be filled by O.E.M. MS-16H2
dmi.board.vendor: Micro-Star International Co., Ltd.
dmi.board.version: REV:0.B
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE16H2IMS.10B:bd08/16/2014:svnMicro-StarInternationalCo.,Ltd.:pnGS602PE:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16H2:rvrREV0.B:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: GS60 2PE
dmi.product.version: REV:1.0
dmi.sys.vendor: Micro-Star International Co., Ltd.

Kick In (kick-d) on 2014-10-02
description: updated
Kick In (kick-d) on 2014-10-02
description: updated
description: updated
Kick In (kick-d) on 2014-10-02
affects: linux-ports-meta (Ubuntu) → linux (Ubuntu)

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1376661

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete
Kick In (kick-d) wrote : AlsaInfo.txt

apport information

tags: added: apport-collected utopic
description: updated

apport information

Kick In (kick-d) wrote : CRDA.txt

apport information

apport information

Kick In (kick-d) wrote : IwConfig.txt

apport information

Kick In (kick-d) wrote : Lspci.txt

apport information

Kick In (kick-d) wrote : Lsusb.txt

apport information

apport information

apport information

apport information

apport information

apport information

Kick In (kick-d) wrote : RfKill.txt

apport information

Kick In (kick-d) wrote : UdevDb.txt

apport information

Kick In (kick-d) wrote : UdevLog.txt

apport information

apport information

Joseph Salisbury (jsalisbury) wrote :

Would it be possible for you to test the latest upstream kernel? Refer to . Please test the latest v3.17 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.


Changed in linux (Ubuntu):
importance: Undecided → Medium
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers