← Back to team overview

kernel-packages team mailing list archive

[Bug 1376661] Missing required logs.

 

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

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1376661

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

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  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:

  http://paste.ubuntu.com/8478288/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1376661/+subscriptions