Patch submitted on kernel-team list. Trusty-Wily all appear affected.
** Also affects: linux-lts-utopic (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
User reported hotfixed kernel resolved the deadlock issue. Looking at
how many kernel versions are affected now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1527062
Title:
XFS Deadlock on 4.2+
** Description changed:
[Impact]
- * An XFS Deadlock situation is possible on 4.2..4.4rc1^ and newer
- kernels.
+ * An XFS Deadlock situation is possible on kernels older than 4.4rc1^
- * Hung tasks have stack traces similar to
+ * Hung tasks have stack traces similar to
[
Verified.. Looks good.
chiluk@rotom:~/bugs/⟫ ./runcrash 00092116-dump.201511300126
crash 7.0.3
Copyright (C) 2002-2013 Red Hat, Inc.
Copyright (C) 2004, 2005, 2006, 2010 IBM Corporation
Copyright (C) 1999-2006 Hewlett-Packard Co
Copyright (C) 2005, 2006, 2011, 2012 Fujitsu Limited
Copyright
Per apw's request I signed and uploaded all packages to
http://people.canonical.com/~chiluk/lp1523606/
I also added dep3 header information.
For ease of review I attached the updated xenial debdiff here, and
deleted all old debdiffs.
** Patch removed: "lp1523606.trusty.debdiff"
** Affects: linux (Ubuntu)
Importance: High
Assignee: Dave Chiluk (chiluk)
Status: In Progress
** Affects: linux-lts-wily (Ubuntu)
Importance: High
Assignee: Dave Chiluk (chiluk)
Status: In Progress
** Tags: sts
** Also affects: linux-lts-wily (Ubuntu)
Importance: Un
** Description changed:
[Impact]
- * Crash prints
+ * Crash prints
"crash: page excluded: kernel virtual address: 8808595a type:
"fill_task_struct" "
- on 4.2 and newer levels of the kernel.
+ on dumps for 4.2 and newer levels of the kernel.
[Test Case]
** Description changed:
[Impact]
* Crash prints
"crash: page excluded: kernel virtual address: 8808595a type:
"fill_task_struct" "
on dumps for 4.2 and newer levels of the kernel.
+ * This is related to variable task_struct_size being variable on 4.2 and
newer
wily and xenial are currently at the same revision so this patch should
work on both.
** Patch added: "lp1523606.wily.debdiff"
https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1523606/+attachment/4535329/+files/lp1523606.wily.debdiff
--
You received this bug notification because you are
** Patch added: "lp1523606.vivid.debdiff"
https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1523606/+attachment/4535327/+files/lp1523606.vivid.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Well that's supremely disappointing. I'll see what I can do.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1347788
Title:
find crashed when current working directory is not readable and -exec
or
I'll do the ports for vivid, wily, and xenial once I get a chance as
well.
** Changed in: crash (Ubuntu)
Assignee: (unassigned) => Dave Chiluk (chiluk)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.
I installed phonon4qt5-backend-gstreamer on my wily machine, and it did
not seem to fix the issue. I need to double check, but it might be
missing the KDE package that provides the sound files as well.
--
You received this bug notification because you are a member of Kubuntu
Bugs, which is
Public bug reported:
[Impact]
* Crash prints
"crash: page excluded: kernel virtual address: 8808595a type:
"fill_task_struct" "
on 4.2 and newer levels of the kernel.
[Test Case]
An example of the issue.
$ crash ddeb/usr/lib/debug/boot/vmlinux-4.2.0-18-generic
** Changed in: multipath-tools (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to multipath-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1520192
Title:
multipath-tools from Precise should
** Changed in: findutils (Ubuntu Xenial)
Assignee: Dave Chiluk (chiluk) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1347788
Title:
find crashed when current working direct
Talked to Pitti during the last foundations meeting. He mentioned
possibly doing a merge of findutils 4.5.14-3 from debian-experitmental
to xenial. That should contain fix required to resolve this bug.
** Changed in: findutils (Ubuntu Xenial)
Assignee: (unassigned) => Martin Pitt (pitti)
Solution, packaged up and tested.
** Patch added: "lp1523606.trusty.debdiff"
https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1523606/+attachment/4531073/+files/lp1523606.trusty.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Changed in: multipath-tools (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1520192
Title:
multipath-tools from Precise should have been fixed together
** Patch removed: "Fix total-unprocessed testcase"
https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1432871/+attachment/4529108/+files/lp1432871_ftbfs_trusty.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Patch
Successful test build here -
https://launchpad.net/~chiluk/+archive/ubuntu/1432871/+build/8386436
** Patch added: "lp1432871_ftbfs_trusty.debdiff"
https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1432871/+attachment/4529111/+files/lp1432871_ftbfs_trusty.debdiff
--
You
So after far too many builds with additional debug output, I realized
that df itself was functioning exactly like the upstream version of df.
However, it turns out the testcase was updated between 8.21 and 8.23.
Updating the total-unprocessed testcase resolves the ftbfs.
It should be noted that
Verified df has been fixed. yay.
** Tags removed: verification-needed
** Tags added: verification-done verification-done-trusty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1432871
Title:
`df`
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1481490
Title:
Add sfc to nic-modules udeb
To manage notifications about this
So the regression I discovered was actually just behavior change. Due
to the change to /proc/self/mountinfo the filesystem type is now more
explicit. In this case that means that nfs mounts are now labeled nfs4.
Additionally I discovered that the test that is now failing was
previously being
Fix ftbfs on tests/df/total-unprocessed.sh
Apparently the buildds are running with a slightly different environment
than my local build machine which is causing this test to fail due to
smart quotes in the set LANG. Explicitly setting LANG=C appears to
resolve this.
** Patch added:
** Patch removed: "fixftbfs.debdiff"
https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1432871/+attachment/4520226/+files/fixftbfs.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Alright so even though the buildds seem to be getting false failures, I
did find a regression in the recent build. I'm going to work through
that, and possibly open up a new bug for it, at least for vivid, wily,
and xenial.
--
You received this bug notification because you are a member of
I also reviewed the upstream patch that purports to resolve the issue
(7dc7006). This fix is contained within the 4.5.9 and newer versions of
findutils. That's where the good news ends. The code portion of that
single commit is 817 lines long. It doesn't apply cleanly, and it
appears to have
I opened
https://savannah.gnu.org/bugs/index.php?46438
against upstream findutils to see if we can't get them to to a blessed release
of 4.5 of findutils.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: findutils (Ubuntu)
Assignee: (unassigned) => Dave Chiluk (chiluk)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1347788
Title:
find crashed when current working direct
** Changed in: findutils (Ubuntu)
Importance: Undecided => Low
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1347788
Title:
find crashed when current working directory is not readable and -exec
Subscribing sponsors and sru team, as both are still necessary for
Trusty.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1432871
Title:
`df` shows bind mounts instead of real mounts.
To manage
Thanks ruddk, it was a pleasure. We will let this bake in -proposed for
a few weeks, and then barring any unforeseen issues it will get promoted
to -updates.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Thanks a ton mterry!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1432871
Title:
`df` shows bind mounts instead of real mounts.
To manage notifications about this bug go to:
** Description changed:
[Impact]
* Programs accessing nfsv4 mounts will hang on request_key interface
with nfs4 + sec=sys with old nfsv4 hosts. Kernel is waiting on
usermodehelper provided by keyutils.
* INFO: task ls:2101 blocked for more than 120 seconds.
Not tainted
** Tags removed: verification-needed
** Tags added: verification-done-vivid verification-done-wily
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1432871
Title:
`df` shows bind mounts instead of
Here's the debdiff for trusty. The provenance of the patches are
included in the header of the debian/patches. I've tested this patch on
machines with the above issue as well as machines with varying
configurations of disk mounts, and remote mounts even.
** Patch added: "trusty.debdiff"
*** This bug is a duplicate of bug 1509120 ***
https://bugs.launchpad.net/bugs/1509120
This looks like a duplicate of
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1509120 .
The workaround is to install the keyutils package.
The fix will be to add keyutils to the Requires line for
** Tags added: verification-done-utopic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1481490
Title:
Add sfc to nic-modules udeb
To manage notifications about this bug go to:
** Changed in: debian-installer (Ubuntu Trusty)
Status: Fix Released => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1481490
Title:
Add sfc to nic-modules udeb
To manage
** Description changed:
[Impact]
- * Programs accessing nfsv4 mounts will hang on request_key interface
+ * Programs accessing nfsv4 mounts will hang on request_key interface
with nfs4 + sec=sys with old nfsv4 hosts. Kernel is waiting on
usermodehelper provided by keyutils.
- *
Yeah, I think so, if you are "creative" enough to put your accounting on
your nfs mount, and then have your nfs service fail, you should expect
your machine to stop functioning. Otherwise it could be a potential
accounting/security hole.
--
You received this bug notification because you are a
** Tags added: sts
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1509120
Title:
Process accounting deadlock with idmapd callout when writing to NFSv4
mount
To manage notifications about this bug
** Changed in: nfs-utils (Ubuntu)
Assignee: (unassigned) => Dave Chiluk (chiluk)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1509120
Title:
Process accounting deadlock with idmapd call
I verified that keyutils is already included in vivid+ in order to fix
1449074. So this shouldn't be too much of an issue to fix in trusty as
well.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Description changed:
+ [Impact]
+
+ * Programs accessing nfsv4 mounts will hang on request_key interface
+ with nfs4 + sec=sys with old nfsv4 hosts. Kernel is waiting on
+ usermodehelper provided by keyutils.
+
+ * INFO: task ls:2101 blocked for more than 120 seconds.
+ Not tainted
Add keyutils to Depends: for nfs-common
** Patch added: "lp1509120.trusty.debdiff"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1509120/+attachment/4512348/+files/lp1509120.trusty.debdiff
** Changed in: nfs-utils (Ubuntu)
Importance: Undecided => Medium
** Changed in: linux
** Changed in: linux (Ubuntu)
Assignee: Chris J Arges (arges) => Dave Chiluk (chiluk)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1509120
Title:
Process accounting deadlock with idm
I created a centos 6 nfsv4 server, and went through the above recreate
procedure with a trusty guest, and could successfully mount, and do file
operations with accton. However after a few minutes, the console hung,
and most tasks reported the following stack traces in /var/log/kern.log
INFO:
Is this testcase reproducible using an nfs server with a recent kernel?
Lots of improvements have been made to NFS in the many years since
2.6.32, including some concurrency improvements.
Thanks,
Dave.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I also completed the same test as Chris above, without failure. I was
using Ubuntu trusty+3.13 as the server and Trusty +3.19 as the guest.
At the moment I don't see any reason to assume that there is anything
power specific in this issue, so I attempted on purely x86_64 hardware.
Also can we
My apologies, I just noticed the deadlock on the mutex comment. Is this
reproducible with the upstream kernel on the client?
We provide mainline kernel builds for testing of this nature using our mainline
build repositories.
http://kernel.ubuntu.com/~kernel-ppa/mainline/
Also keep in mind,
So I did some more searching on this including running an tcpdump in my
environment, and it appears as if idmapd is not making any requests for
me. Hence the reason we aren't hitting the deadlock. Did you do
anything specific in the area of getting idmapd up and configured?
--
You received
In case anyone is wondering. The patch does not cleanly apply against
Trusty, and I'm working on a backport/appropriate cherrypick.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1432871
Title:
** Changed in: linux (Ubuntu Trusty)
Assignee: (unassigned) => Dave Chiluk (chiluk)
** Changed in: linux (Ubuntu Utopic)
Assignee: (unassigned) => Dave Chiluk (chiluk)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@Andrei Demin,
Have you opened a separate case for Samsung drives + RAID 0 + trim =
corruption? If so what is that bug number?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1338706
Title:
Samsung
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1247888
Title:
bip crash with "FATAL: Failed assetion in src/irc.c(2447): n
To manage notifications about this bug go
** Changed in: coreutils (Ubuntu Vivid)
Status: New => In Progress
** Changed in: coreutils (Ubuntu Trusty)
Status: New => In Progress
** Changed in: coreutils (Ubuntu Wily)
Status: Fix Released => Fix Committed
--
You received this bug notification because you are a
** Changed in: coreutils (Ubuntu Wily)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1432871
Title:
`df` shows bind mounts instead of real mounts.
To
Public bug reported:
quassel can't play audio notifications in wily.
As of quassel-client 0.12.2-0ubuntu1, the quassel client does not play
sound notifications when highlighted messages are received.
** Affects: quassel (Ubuntu)
Importance: Undecided
Status: New
--
You received
** Changed in: coreutils (Ubuntu Vivid)
Assignee: (unassigned) => Dave Chiluk (chiluk)
** Changed in: coreutils (Ubuntu Trusty)
Assignee: (unassigned) => Dave Chiluk (chiluk)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
@mrobinson-o The trusty image with the Utopic image is waiting on a new
build and test cycle of the utopic kernel before those images can be
built. It is in process. We were able to simply rebuild the images for
3.13 and 3.19 as the sfc driver was already available in those kernels.
--
You
** Tags removed: verification-needed-trusty
** Tags added: verification-done-trusty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1497048
Title:
Trusty - Null pointer dereference at
An external user reported that this, resolved their issue. So I'm
marking this verification-done-trusty. Unfortunately there is no easy
way to reproduce this.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Thanks for spinning the new install images. I have confirmed that the
3.13.0-65 kernel netboot install worked without a hich. However I do
not have sfc hardware to test with.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This same patch applies cleanly to both wily and vivid, but it has wily
in the changelog.
** Patch added: "lp1432871.wily.debdiff"
https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1432871/+attachment/4482367/+files/lp1432871.wily.debdiff
--
You received this bug notification because
** Description changed:
[Impact]
* df displays bind mounts instead of "real" mounts if the bind mount is
mounted to a shorter directory.
* justification - This is a change of behavior from precise
* Explanation - This patch checks to see if the source directory of a
mount
In order to solve this issue, I have written patches and got them integrated
upstream.
gnulib commit:
http://git.savannah.gnu.org/gitweb/?p=gnulib.git;a=commit;h=c6148bca89e9465fd6ba3a10d273ec4cb58c2dbe
and
coreutils commit:
** Description changed:
[Impact]
* df displays bind mounts instead of "real" mounts if the bind mount is
mounted to a shorter directory.
* justification - When trusty moved to using /proc/mounts this changed
behavior from precise. Additionally it doesn't make sense that a bind
** Changed in: coreutils (Ubuntu)
Status: Incomplete => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1432871
Title:
`df` shows bind mounts instead of real mounts.
To manage
** Changed in: linux-lts-utopic (Ubuntu)
Status: Invalid => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1481490
Title:
Add sfc to nic-modules udeb
To manage notifications
** Tags added: sts
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1481490
Title:
Add sfc to nic-modules udeb
To manage notifications about this bug go to:
** Also affects: debian-installer (Ubuntu)
Importance: Undecided
Status: New
** Changed in: debian-installer (Ubuntu Trusty)
Status: New => In Progress
** Changed in: debian-installer (Ubuntu Trusty)
Assignee: (unassigned) => Mathieu Trudel-Lapierre (mathieu-tl)
--
You
Status: New => In Progress
** Changed in: debian-installer (Ubuntu Vivid)
Assignee: (unassigned) => Dave Chiluk (chiluk)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1481490
Title:
** Changed in: linux (Ubuntu Trusty)
Assignee: (unassigned) => Dave Chiluk (chiluk)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1497048
Title:
Trusty - Null pointer derefere
** Changed in: linux (Ubuntu)
Status: Incomplete => In Progress
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1497048
Title:
** Patch removed: "lp1432871.trusty.debdiff"
https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1432871/+attachment/4447737/+files/lp1432871.trusty.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: linux (Ubuntu)
Assignee: Dave Chiluk (chiluk) => Jay Vosburgh (jvosburgh)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1463911
Title:
IPV6 fragmentation and mtu is
** Description changed:
- A user has reported to us the following crash stack trace.
+ [Impact]
-
_
- [415165.417433] BUG: unable to handle kernel NULL pointer dereference at
00a3
+ * With
)
Importance: Undecided
Assignee: Dave Chiluk (chiluk)
Status: New
** Tags: sts
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1497048
Title:
Trusty - Null pointer dereference
For those seeing this issue after 3.13.0-33.58, please ensure that the
virtual machine's host kernel is running 3.13.0-33.58 or newer. The VM
kernel itself does not matter.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
) => Dave Chiluk (chiluk)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1463911
Title:
IPV6 fragmentation and mtu issue
To manage notifications about this bug go to:
https://bugs.launchpad.net/neut
** Tags added: sts
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1463911
Title:
IPV6 fragmentation and mtu issue
To manage notifications about this bug go to:
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1463911
Title:
IPV6 fragmentation and mtu issue
To manage notifications
I have a new fix for this that I will attempt to upstream. I will
submit it again once it gets accepted upstream.
** Changed in: coreutils (Ubuntu)
Status: Won't Fix = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Fixed version and added origin information to debdiff.
** Patch removed: lp1432871.trusty.debdiff
https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1432871/+attachment/4351938/+files/lp1432871.trusty.debdiff
** Patch added: lp1432871.trusty.debdiff
** Description changed:
[Impact]
- * df displays bind mounts instead of real mounts if the bind mount is
+ * df displays bind mounts instead of real mounts if the bind mount is
mounted to a shorter directory.
- * justification - This is a change of behavior from precise
+ *
On 08/12/2015 03:59 AM, Andrei Demin wrote:
Seems Samsung fixed this bug in kernel
(https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=f3f5da624e0a891c34d8cd513c57f1d9b0c7dadc)
and blacklist is no longer needed. Maybe we should remove blacklist and
apply this patch
Reinstalling the nvidia-346 package seems to have remedied my issues.
Looks like a package simply was not updated properly or some
configuration file got screwed up.
** Changed in: linux (Ubuntu)
Status: Confirmed = Invalid
--
You received this bug notification because you are a member
All logs above are from a boot of 3.13.0-59. As the machine is not very
useful without a window manager. Virtual terminals do work though with
3.13.0-62
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Removing the nvidia drivers and bbswitch allowed my computer to boot to
Xorg again.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1482920
Title:
Lightdm and xorg fail to start console shows
*** This bug is a duplicate of bug 1465706 ***
https://bugs.launchpad.net/bugs/1465706
** This bug has been marked a duplicate of bug 1465706
SRU: New upstream releases of nvidia for 14.04.3
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
*** This bug is a duplicate of bug 1465706 ***
https://bugs.launchpad.net/bugs/1465706
** This bug has been marked a duplicate of bug 1465706
SRU: New upstream releases of nvidia for 14.04.3
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
After the recent update, I can confirm that bumblee broke for me as
well. I had the same plymouth goes to black screen problem.
As a shot in the dark *(and me not trusting my installation), I removed
bbswitch and all nvidia related packages, and then installed nvidia-346.
The 3.13.0-62 kernel
I should have said. I did however notice that this new driver does not
build against the OLDER kernels.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1465706
Title:
SRU: New upstream releases of
Public bug reported:
Lightdm and xorg fail to start console shows
[drm:intel_dp_start_link_train] *ERROR* too many voltage retries, give up.
The above error may be a red-herring as it appears in boots of 3.13.0-59 albeit
less frequently, and definitely not as the last message.
The issue
Public bug reported:
3.13.0-61 has broken wifi, and display locked at 800x600. 3.13.0-59
works fine. Each was tested with the identical userspace, simply
rebooted into the newer kernel.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-59-generic 3.13.0-59.98
Confirmed that wifi does work in 3.13.0-62, but x is even more broken
there.
** Summary changed:
- 3.13.0-61 has broken wifi, and display locked at 800x600
+ 3.13.0-61 display locked at 800x600 with i915
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
This may be related to bug 1482920.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1482923
Title:
3.13.0-61 display locked at 800x600 with i915
To manage notifications about this bug go to:
401 - 500 of 1000 matches
Mail list logo
