[Touch-packages] [Bug 1633776] [NEW] Crash due to SATA 3 issue in Skylake chip
Public bug reported: Minor bug - I have an annoying work around ASRock Z170 Extreme7+ Mboard has 10 SATA 3 ports off 2 controller chips CPU is Skylake 6700. One SATA chip does 6 ports in pairs which also serve as either SATA Express or M.2 drive controllers. these are SATA 3-0 to SATA 3-5, other has 4 SATA ports. System worked in Win 7, but when booting to Kubuntu 16.10 it kept coming crashing during boot with an error of 'Unable to initiate SATA child Parent inactive.' I tried every possible combination, and eventually got the system to load by placing an Optical drive as SAT 3-0, and writing off one of the SATA Express links. Once I got it going I started adding drives back in one at a time, and hit the same problem when I got to the first SATA port on the 2nd chip, and optical drive plugged in there soon fixed that. Another issue was I couldn't create an M.2 drive as the system drive while there was a hard drive connected to the system. Cut it back to just the optical and the M.2 and it let me use the M.2 as the system drive. System now working with SATA 3-0 as optical, SATA 3-1 as 2TB HDD, SATA 3-2/3 as 500GB M.2, SATA 3 -4/5 as 500GB M.2, SATA 3A-0 as optical, SATA 3A-2 as 2TB HDD. Tested, as soon as I move an optical from the first SATA port for the chip I get the error message during the boot-up and it doesn't load. Switch back and it loads OK. I've a work around, but it costs me a SATA Express line. However, you may see others with Skylake chips havign the same issue. I suspect it's an issue with the package checking the hardware during the boot-up, but don't know enough to say for sure. ** Affects: apport (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1633776 Title: Crash due to SATA 3 issue in Skylake chip Status in apport package in Ubuntu: New Bug description: Minor bug - I have an annoying work around ASRock Z170 Extreme7+ Mboard has 10 SATA 3 ports off 2 controller chips CPU is Skylake 6700. One SATA chip does 6 ports in pairs which also serve as either SATA Express or M.2 drive controllers. these are SATA 3-0 to SATA 3-5, other has 4 SATA ports. System worked in Win 7, but when booting to Kubuntu 16.10 it kept coming crashing during boot with an error of 'Unable to initiate SATA child Parent inactive.' I tried every possible combination, and eventually got the system to load by placing an Optical drive as SAT 3-0, and writing off one of the SATA Express links. Once I got it going I started adding drives back in one at a time, and hit the same problem when I got to the first SATA port on the 2nd chip, and optical drive plugged in there soon fixed that. Another issue was I couldn't create an M.2 drive as the system drive while there was a hard drive connected to the system. Cut it back to just the optical and the M.2 and it let me use the M.2 as the system drive. System now working with SATA 3-0 as optical, SATA 3-1 as 2TB HDD, SATA 3-2/3 as 500GB M.2, SATA 3 -4/5 as 500GB M.2, SATA 3A-0 as optical, SATA 3A-2 as 2TB HDD. Tested, as soon as I move an optical from the first SATA port for the chip I get the error message during the boot- up and it doesn't load. Switch back and it loads OK. I've a work around, but it costs me a SATA Express line. However, you may see others with Skylake chips havign the same issue. I suspect it's an issue with the package checking the hardware during the boot-up, but don't know enough to say for sure. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1633776/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1359439] Re: [ 7.287663] systemd-logind[1057]: Failed to start unit user@126.service: Unknown unit: user@126.service
I have the same problem as described initially (as the title of this bug report) after a clean install of Ubuntu Server 14.10. I used sudo -i t become the root and then ran the following command: * apt-get install systemd-sysv After rebooting and logging in, I did not have the message/problem appear. When I input ps -p 1 -o comm= systemd is returned. * I am pretty sure that I saw upstart being removed. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd-shim in Ubuntu. https://bugs.launchpad.net/bugs/1359439 Title: [7.287663] systemd-logind[1057]: Failed to start unit user@126.service: Unknown unit: user@126.service Status in systemd-shim package in Ubuntu: In Progress Status in systemd-shim package in Debian: New Bug description: [7.287663] systemd-logind[1057]: Failed to start unit user@126.service: Unknown unit: user@126.service [7.287677] systemd-logind[1057]: Failed to start user service: Unknown unit: user@126.service [7.293871] systemd-logind[1057]: New session c1 of user lightdm. [7.293902] systemd-logind[1057]: Linked /tmp/.X11-unix/X0 to /run/user/126/X11-display. [7.363706] ip_tables: (C) 2000-2006 Netfilter Core Team [7.421846] nf_conntrack version 0.5.0 (16384 buckets, 65536 max) [7.484529] IPv6: ADDRCONF(NETDEV_UP): virbr0: link is not ready [9.903052] wlan0: authenticate with c8:d7:19:22:21:ec [9.912429] wlan0: send auth to c8:d7:19:22:21:ec (try 1/3) [9.920181] wlan0: authenticated [9.924352] wlan0: associate with c8:d7:19:22:21:ec (try 1/3) [9.925709] wlan0: RX AssocResp from c8:d7:19:22:21:ec (capab=0x11 status=0 aid=2) [9.927753] wlan0: associated [9.927800] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready [ 12.677104] systemd-logind[1057]: Failed to abandon scope session-c1.scope [ 12.677122] systemd-logind[1057]: Failed to abandon session scope: No such interface 'org.freedesktop.systemd1.Scope' on object at path /org/freedesktop/systemd1/unit/session_2dc1_2escope [ 12.683902] systemd-logind[1057]: Failed to start unit user@1000.service: Unknown unit: user@1000.service [ 12.683912] systemd-logind[1057]: Failed to start user service: Unknown unit: user@1000.service [ 12.685157] systemd-logind[1057]: New session c2 of user caravena. [ 12.685190] systemd-logind[1057]: Linked /tmp/.X11-unix/X0 to /run/user/1000/X11-display. [ 234.494462] systemd-logind[1057]: Failed to abandon scope session-c2.scope [ 234.494478] systemd-logind[1057]: Failed to abandon session scope: No such interface 'org.freedesktop.systemd1.Scope' on object at path /org/freedesktop/systemd1/unit/session_2dc2_2escope [ 235.514349] systemd-logind[1057]: New session c3 of user lightdm. [ 244.245908] systemd-logind[1057]: Failed to abandon scope session-c3.scope [ 244.245923] systemd-logind[1057]: Failed to abandon session scope: No such interface 'org.freedesktop.systemd1.Scope' on object at path /org/freedesktop/systemd1/unit/session_2dc3_2escope ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: systemd 208-7ubuntu4 [modified: usr/share/dbus-1/system-services/org.freedesktop.systemd1.service] ProcVersionSignature: Ubuntu 3.16.0-9.14-generic 3.16.1 Uname: Linux 3.16.0-9-generic x86_64 ApportVersion: 2.14.6-0ubuntu2 Architecture: amd64 CurrentDesktop: LXDE Date: Wed Aug 20 18:26:06 2014 InstallationDate: Installed on 2014-04-27 (115 days ago) InstallationMedia: Ubuntu-GNOME 14.04 LTS Trusty Tahr - Release amd64 (20140416.2) SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd-shim/+bug/1359439/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
