Public bug reported:
I have a Yoga 900-13ISK and a Thinkpad T470s. Both have had working
screen rotation in the past. However, I noticed today while supporting a
user in #ubuntu, neither do now. No icon in the Gnome menu and:
# G_MESSAGES_DEBUG=all iio-sensor-proxy
** (process:14877): DEBUG: 12:
Right, I understand fully what the bot is asking for, but it's not
exactly relevant here. We are seeing (on at least two systems) a lack of
IIO device discovery. If I modprobe all the iio modules, I do get a
/sys/bus/iio, but no devices in it. So it feels like something is
missing, but I don't know
I just tried booting into 4.15.0-20 as the release pocket has it still
and it also failed to work. So now I'm wondering if/when it did work. I
will try and narrow it down in the next few days.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed t
I don't see any fundamental issue with providing a NET_WAIT_TIME
variable (probably should be namespaced to KDUMP_) in the kdump config
file, but:
1) this seems like a hack to work around slow hardware, right?
2) it can't be automatically deduced, afaict. Or do you want to have 30s
delays (potent
I believe this request should be routed to the kernel team (setting of a
kernel default value for POWER systems)?
--
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/1680349
Title:
Ubuntu 17.
How is this supposed to work generally. On DLPAR, kdump needs to be
reloaded -- does that the mean the kdump.service should be watching for
dlpar events?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchp
$ syncpackage -b 1706946 -s rbalint -f crash
syncpackage: Source crash -> artful/Proposed: current version 7.1.8-1ubuntu2,
new version 7.1.9-1
syncpackage: New changes:
crash (7.1.9-1) unstable; urgency=medium
* Patch from Balint Reczey : Build crash on all Linux
architectures (Closes: #763
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
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/1687273
Title:
Shared folder randomly not mounted
Status in ci
*** This bug is a duplicate of bug 1612627 ***
https://bugs.launchpad.net/bugs/1612627
** This bug has been marked a duplicate of bug 1612627
iscsitarget-dkms 1.4.20.3+svn499-0ubuntu2.1 fails to build on
linux-generic-lts-xenial kernel
--
You received this bug notification because you ar
Err, apologies Joe, it does seem like upon more careful reading of the
bug report, the second mentioned commit (comment #18) specifically
introduced the regression? That seems unlikely at best given it's
contents, rights? That is, if the divisor was zero after that commit, it
was zero before it, to
@Joe, based upon the identified commit, I wonder if it would be worth
testing backports of follow-on fixes specifically for that commit?
http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=b5d5f27d938fb6fc8d3202704e699d2694a02da6
http://git.kernel.org/cgit/linux/kernel/git/to
Couple of thoughts, which we probably should get IBM's advice on:
I believe this is using: crashkernel=384M-:128M
128M reserved seems too small for so much memory, tbh.
Also, I see that all the CPUs are on in the crashkernel, when
realistically only 1 CPU is needed (and there have been issues in
On 07.04.2016 [17:18:58 -], Dave Chiluk wrote:
> According to
> https://wiki.ubuntu.com/ppc64el/Recommendations#Crash_Kernel_recommendations
>
> it looks like the following should be used.
> crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M
>
> These should be made
On 08.04.2016 [11:04:47 -], Louis Bouchard wrote:
> Hello,
>
> Regarding nr_cpus=1, the equivalent maxcpus=1 is set in the kexec
> command (at least on default installs) :
Yep, you're right, sorry!
> Maybe disabling SMP alltogether by setting maxcpus=0 could be considered
> but that shouldn'
On 12.04.2016 [18:51:36 -], Dave Chiluk wrote:
> I received another update from the end user.
> "A fresh 14.04.4 DVD Ubuntu install with updates (3.16.0-69 kernel) in a
> diskful setup (no NFS, no aufs, 1T swap disk) also fails to kdump, either
> hangs or OOMS."
>
> My understanding is t
On 12.04.2016 [19:53:57 -], Dave Chiluk wrote:
> I can confirm that the following settings for crashkernel on powernv result
> in the following console log.
> crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M
If I read that correctly, it failed to kdump at all? Can y
On 12.04.2016 [21:13:40 -], Dave Chiluk wrote:
> With
> ubuntu@modoc:~$ cat /proc/cmdline
> root=/dev/mapper/mpath0-part2 ro console=hvc0
> crashkernel=2G-4G:320M@32M,4G-32G:512M@32M,32G-64G:1024M@32M,64G-128G:2048M@32M,128G-:4096M@32M
>
> I get the following console log
> [ 191.833046] Sys
On 13.04.2016 [23:44:39 -], Dave Chiluk wrote:
> So it looks like this crashkernel argument is not resulting in any reserved
> memory.
> The correct crashkernel argument should look like this.
> crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M@32M
>
> Additionally m
Hi Tim,
Note that the referenced commit only makes it so that if you don't back
a PowerKVM guest with hugepages, hugepages do not (falsely) appear to be
supported. In such an environment the message referenced in this bug
report will still be displayed as it should -- hugepages aren't
supported in
I verified that the performance is the equivalent of upstream with
3.13.0-32-generic. There is still work to be done upstream but this gets
us quite a bit further.
** Tags removed: verification-needed-trusty
** Tags added: verification-done-trusty
--
You received this bug notification because yo
I verified that the performance is the equivalent of upstream with
3.13.0-32-generic. There is still work to be done upstream but this gets
us quite a bit further.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bu
Breno,
Was your test done with a cgmanager with the -M flag passed?
--
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/1392176
Title:
mounts cgroups unconditionally which causes undesired e
Serge,
That should only be true for unified hierarchy. In legacy hierarchy,
effective_cpus follows cpus, I think?
--
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/1392176
Title:
mounts cg
Not sure if this will really help here, but I have a D3100 and I was
able to drive two monitors using
http://www.displaylink.com/downloads/ubuntu on 16.04. 16.10 again breaks
it since the out-of-tree driver doesn't build against the later kernels
(or so it seems). I wonder if this is something wort
Re-tested in 16.10, and the displaylink driver does work, but is much
much laggier than in 16.04. Not yet had a chance to debug that.
--
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/1376771
It seems like 14.04.0/1's kernel would still need this backport -- 3.13
base and the upstream fix went into 3.14.
** Also affects: linux (Ubuntu Trusty)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscri
@chih: Was helping a user in #ubuntu today with the same device ID
(413c:8143). But I think I'm a bit confused by this, I'm looking at the
upstream source and I see:
$ grep 413c drivers/bluetooth/btusb.c
{ USB_DEVICE(0x413c, 0x8197) },
{ USB_DEVICE(0x413c, 0x8126), .driver_info =
To clarify to everyone possibly affected by this bug, and in reviewing
the thread @Henrik provided, it seems like the upstream community
(linux-uvc) has reviewed the patch and asked for some modifications
(April 27, 2016). So that is why the patch has not made its way into
Ubuntu kernels yet, as it
Public bug reported:
xenial daily ISO successfully installs using the same method on the same
system, but yakkety reports:
Sep 27 21:13:14 cdrom-detect: Searching for Ubuntu installation media...
Sep 27 21:13:18 cdrom-detect: Devices: ''
Sep 27 21:13:23 cdrom-detect: Devices: ''
Sep 27 21:13:24 k
I'm not able to run apport-collect from the installer shell.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
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/1628284
Ti
uname -a from the installer shell:
Linux (none) 4.8.0-17-generic #19-Ubuntu SMP Sun Sep 25 05:58:36 UTC
2016 ppc64 GNU/Linux
We blocked release of the powerpc iso for beta2 because of this bug in
#ubuntu-release, so there is no beta-2 image :)
For the net boot iso, (maybe because of the virtuali
Hi Tim,
Discussed this with Josh Powers and it seems at least this particular
issue is now fixed, sorry for the delay on my end.
-Nish
** Changed in: linux (Ubuntu Yakkety)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Kernel
Packa
32 matches
Mail list logo
