> Can you say whether it's the second problem that was breaking the desktop
> coming up on login? IOW, I observed two problems. One was a freeze during
> the boot process, and the other was a freeze during the login process
> (although the latter wasn't a total freeze, as ssh still worked).
As
Thanks for the extra details Seth.
Can you say whether it's the second problem that was breaking the desktop
coming up on login? IOW, I observed two problems. One was a freeze during
the boot process, and the other was a freeze during the login process
(although the latter wasn't a total
On Sep 29, 2016, at 03:20 AM, Joseph Salisbury wrote:
>I built the next test kernel, up to the following commit:
>1eccfa090eaea22558570054bbdc147817e1df5e
201609282035 boots, does not give me a desktop, and I see the crash in the
syslog.
--
You received this bug notification because you are a
On Sep 28, 2016, at 11:06 PM, Joseph Salisbury wrote:
>I built the next test kernel, up to the following commit:
>97433ea4fda62349bfa42089455593cbcb57e06c
201609281855 boots and gives me a desktop. No crash in usercopy.c found in
syslog.
--
You received this bug notification because you are a
On Sep 28, 2016, at 02:39 PM, Joseph Salisbury wrote:
>It looks like we'll have to perform a second bisect, but also reverting
>commit 2deb4be2 between each step.
Just to follow up, I was able to eventually gain a desktop with the rc1 kernel
and the bad commit reverted. My current plan is to
On Sep 27, 2016, at 11:12 PM, Joseph Salisbury wrote:
>I built a mainline kenel with commit
>2deb4be28077638591fe5fc593b7f8aabc140f42 reverted.
>
>Can you test this kernel to see if it also has the new desktop issue?
That one gets a little farther but ultimately doesn't give me a desktop
either.
On Sep 27, 2016, at 09:15 PM, Joseph Salisbury wrote:
>Can you see if this kernel resolves this bug?
Almost! As mentioned in IRC, it boots but login doesn't give me a
desktop.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
On Sep 27, 2016, at 08:28 PM, Joseph Salisbury wrote:
>The bisect reported the following as the first bad commit:
>
>commit 2deb4be28077638591fe5fc593b7f8aabc140f42
>Author: Andy Lutomirski
>Date: Thu Jul 14 13:22:55 2016 -0700
>
>x86/dumpstack: When OOPSing, rewind the
On Sep 27, 2016, at 03:32 PM, Joseph Salisbury wrote:
>I built the next test kernel, up to the following commit:
>0f657262d5f99ad86b9a63fb5dcd29036c2ed916
Thanks. 201609271113 does *not* boot.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
On Sep 26, 2016, at 11:36 PM, Joseph Salisbury wrote:
>I built the next test kernel, up to the following commit:
>5048c2af078d5976895d521262a8802ea791f3b0
#201609261917 boots!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
On Sep 26, 2016, at 10:52 PM, Joseph Salisbury wrote:
>I built the next test kernel, up to the following commit:
>52770c37db2c0ee5585dae2de3d19c8453f1e8dc
This one boots!
linux-image-4.7.0-040700-generic_4.7.0-040700.201609261819_amd64.deb
--
You received this bug notification because you are
On Sep 26, 2016, at 06:18 PM, Joseph Salisbury wrote:
>v4.5: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.5-wily/
>v4.6: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.6-yakkety/
>v4.7: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.7/
All of these kernels (amd64, generic) boot
On Sep 26, 2016, at 12:48 PM, Leann Ogasawara wrote:
>Could you re-test with the 4.8.0-17.19 kernel we have in ppa:canonical-
>kernel-team/unstable
Unfortunately this kernel also fails to completely boot. The last things I
see in the console are
[ OK ] Started Login Service.
[ 36.445144]
13 matches
Mail list logo