Actually looking at the patch (shrink_dcache_for_umount) this might not
be the whole problem but may be just related. The problem I am having is
while the system is still running, and cache growing huge, not while
umounting.
--
You received this bug notification because you are a member of Kernel
The last time I got it to hang long enough to produce a backtrace it
showed:
[1560556.660010] INFO: task vgs:3103183 blocked for more than 1105 seconds.
[1560556.660012] Tainted: G U OE 5.4.0-40-lowlatency
#44-Ubuntu
[1560556.660013] "echo 0 > /proc/sys/kernel/hung_task_timeout_
It appears Red Hat fixed this problem with a kernel patch in RHEL 7.5
that was not upstreamed.
https://access.redhat.com/errata/RHSA-2018:1062
BZ - 1471875 - soft lockups during unmount when dentry cache is very
large
https://bugzilla.redhat.com/show_bug.cgi?id=1471875
** Bug watch added: Red H
I haven't verified if this actually fixes the problem but it seems to
make a huge difference in 'free' memory as shown by 'free'.
I had already closed my VMs by the time I tried this so haven't verified
if it stops the long freezes yet.
totalusedfree shared buf
I have this problem as well on Cinnamon, so it doesn't appear to be
specific to KDE. It stalls often and frequently over 15-30 seconds at a
time for no apparent reason. But the swapping to disk may be a clue.
I see this on 5.4.0-40 and have also tried with the lowlatency version
of the kernel and
Alex, you should probably file a new upstream bug about the issue if you
can reproduce it on the upstream 4.11 version. I no longer have a Cherry
Trail system so can't do it myself.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
Kai-Heng,
Yes, but with ASPM disabled unfortunately even ASPT doesn't help enough.
:-(
--
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/1682711
Title:
PCIe ASPM disabled even when enabled
I sent a follow up email to Lenovo but don't expect to hear back from
them until sometime after next Monday.
--
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/1682711
Title:
PCIe ASPM disab
Talking to Matthew Garrett on irc he said that he thinks this may only
be fixable via an UEFI change.
04:33 < ccheney> anyone know if it is possible to change a setting in LnkCap on
a pci device? My pcie ports apparently have 'ASPM not supported' set and I need
to turn it on somehow
04:33 < cche
Public bug reported:
This is somewhat similar in issue to lp#1377596.
I have a "Lenovo ThinkCentre m900 Tiny" with an "Intel 600p" NVMe drive
in it.
As far as I can tell from dissembling the FADT PCIe ASPM is not set to
disabled but the ports are not enabled in UEFI during boot.
I also notice t
The setpci commands I used modified the LnkCtl option but not the LnkCap
values. I'm not sure but suspect that the LnkCap values are what are
causing the problem.
--
LnkCap: Port #17, Speed 8GT/s, Width x4, ASPM not supported, Exit Latency L0s
<1us, L1 <16us
ClockPM- Surprise- LLActRep+
I'm closing this bug as after rebooting onto current linux
4.4.0-43-generic the problem went away.
** Changed in: linux (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https:/
blockdev also reports the wrong value:
# blockdev --getsz /dev/sdd1
32787056
strace shows that fstat() reports the wrong value.
9175 02:20:07.714355 open("/dev/sdd1", O_RDONLY) = 3
9175 02:20:07.714387 uname({sysname="Linux", nodename="desktop-clc",
release="4.4.0-38-generic", version="#57-Ub
Taking the first sector output and decoding it shows:
00 - 00 01 01 - 0c - 3f a0 00 - 00 08 00 00 - 00 00 10 00
00 - 00 81 01 - 83 - 3f 20 00 - 00 08 10 00 - 00 00 10 00
00 - 00 01 01 - 83 - 3f 20 00 - 00 08 20 00 - 00 00 20 00
00 - 00 01 01 - 83 - 3f e0 3f - 00 08 40 00 - 00 f8 79 03
Which looks
Public bug reported:
For some reason Linux (dd/mkfs.vfat/mkfs.ext4) treats the first
partition of my sdcard as 16GB regardless of what fdisk says it should
be. dd sees the other partitions as the correct size.
Also if I run mkfs.vfat on the first partition it is treated as a fuse
filesystem when
I dug around and found upstream kernel bzs related to this issue:
https://bugzilla.kernel.org/show_bug.cgi?id=150481
https://bugzilla.kernel.org/show_bug.cgi?id=155241
** Bug watch added: Linux Kernel Bug Tracker #150481
http://bugzilla.kernel.org/show_bug.cgi?id=150481
** Bug watch added: L
As noted at the link the code is known wrong for CHT but may have
further bugs:
https://bugzilla.kernel.org/show_bug.cgi?id=150481#c1
--
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/1625440
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1625440/+attachment/4744502/+files/UdevDb.txt
--
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/1625440
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1625440/+attachment/4744499/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/b
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1625440/+attachment/4744497/+files/Lspci.txt
--
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/1625440
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1625440/+attachment/4744500/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1625440/+attachment/4744494/+files/CRDA.txt
--
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/1625440
Ti
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1625440/+attachment/4744498/+files/Lsusb.txt
--
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/1625440
apport information
** Tags added: apport-collected yakkety
** Description changed:
kernel crash on boot rendering sdio wifi and bluetooth from operating on
Nexbox T9 (Intel x5-z8300), works fine under Windows 10. It happens on
both 16.04 and 16.10 with kernel 4.4.0 and on kernel 4.8.0-rc4
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1625440/+attachment/4744495/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1625440/+attachment/4744503/+files/WifiSyslog.txt
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages,
apport information
** Attachment added: "JournalErrors.txt"
https://bugs.launchpad.net/bugs/1625440/+attachment/4744496/+files/JournalErrors.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.n
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1625440/+attachment/4744501/+files/ProcModules.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/b
Fedora 25 alpha kernel (4.8-rc4) output looks effectively the same:
[ 20.811692] i2c_designware 808622C1:06: I2C bus managed by PUNIT
[ 20.912602] i2c_designware 808622C1:06: punit semaphore timed out, resetting
[ 20.912723] i2c_designware 808622C1:06: PUNIT SEM: 2
[ 20.912803] ---
Public bug reported:
kernel crash on boot rendering sdio wifi and bluetooth from operating on
Nexbox T9 (Intel x5-z8300), works fine under Windows 10. It happens on
both 16.04 and 16.10 with kernel 4.4.0 and on kernel 4.8.0-rc4 on Fedora
25 alpha. The acpi errors don't show up in the 4.8.0 kernel
I'm seeing what appears to be the same bug on linux 3.17.0-031700rc6
from:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.17-rc6-utopic/
Plugging the same devices (HD / wacom tablet) into the on chipset Intel
USB2 controller works fine.
--
[ 156.603076] usb 10-2: new high-speed USB device nu
Looking at LP #1215098 and the libimobiledevice website it appears there
is likely some bugs still in 1.1.5 that are affecting some systems. Some
users on that bug thread can use iPhone 5S just fine but it doesn't work
on mine. The libimobiledevice page seems to indicate the old 1.1.5
release shoul
I think the trust prompt issue may have been fixed with a newer release
of iOS 7. I no longer see it on 7.0.4 either. However I still can't
access my iPhone 5S, I get the following error box instead:
"
Unable to mount (iPhone name)
Unhandled Lockdown error (-3)
"
--
You received this bug notifi
** Description changed:
After resuming from suspend, a Marvel 88E8055 (wired NIC) will fail to
detect carrier (link is permanently down). Reloading the sky2 module
does not help - the module will fail to initialize the hardware and the
eth0 interfaces is gone until reboot.
The suspend
I should also note that this appears to affect more than just Linux. I
had originally thought that Windows 7 somehow broke my nic because I
temporarily loaded it on the box to update firmware on some of my other
devices. The nic would not work after suspend on Windows 7 either even
with the current
I just realized something I changed on my system when I reconfigured it
which turns out to have allowed the nic to work previously. I disabled
an extra sata controller on the system which I wasn't using anymore and
then the nic would no longer work. I enabled it again and it works now,
lol.
This d
Is there any progress on this bug? I am seeing the same thing on my
system with up to date 13.04 after having recently reinstalled it. It
had been working for 7 years (!) before this problem finally cropped up.
I'm guessing if it is timing related perhaps the slight reconfiguration
is what exposed
37 matches
Mail list logo
