@sfc Could you explain a little more how exactly to use the dkms.conf
file? Should I put the file in the same ampe_stor directory?
--
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/1730152
This fails with kernels as old as 4.4.0-101-generic and earlier too, so
I don't think this is a kernel regression. I believe it's an issue with
xfsprogs. For example, xfsprogs-4.14.0 can create an xfs file system on
a file based system where as 4.3.0+nmu1ubuntu1.1 cannot:
Same issue affects me after updating to kernel 4.13.0-31.
Resuming starts but after a few seconds screen goes dark and nothing can
be done except forcing off the laptop.
Also found "Hibernation image not present or could not be loaded" in
kernel log.
--
You received this bug notification
http://people.canonical.com/~khfeng/lp1744712/
seems to be working fine, did couple of sleep/resume cycles with no
issues
--
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/1744712
Title:
** Also affects: ndiswrapper (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/1742474
Title:
Bad return status for module build on
As reported upstream, when I used the drm-tip kernel I didn't see the FIFO
error message in the logs again (but still had random power downs).
I'm running the mainline kernel 4.15.0-041500rc8-generic and also don't see any
of the described issues anymore (although I still have 1-2 random
This does not look like an ecryptfs issue, it's mkfs.xfs breaking with
an -EINVAL on a file based file system:
dd if=/dev/zero of=foo bs=1M count=1024
sudo mkfs.xfs -f foo
meta-data=fooisize=512agcount=4, agsize=64000 blks
= sectsz=512
** Merge proposal linked:
https://code.launchpad.net/~juliank/ubuntu/+source/multipath-tools/+git/multipath-tools/+merge/336526
--
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/1673350
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1745118/+attachment/5042212/+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/1745118
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1745118/+attachment/5042216/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1745118/+attachment/5042210/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1745118/+attachment/5042217/+files/ProcModules.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1745118/+attachment/5042219/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1745118/+attachment/5042214/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1745118/+attachment/5042215/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "JournalErrors.txt"
https://bugs.launchpad.net/bugs/1745118/+attachment/5042211/+files/JournalErrors.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1745118/+attachment/5042218/+files/UdevDb.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1745118/+attachment/5042213/+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/1745118
apport information
** Tags added: apport-collected
** Description changed:
Some SRU testing node cannot boot with the latest 32bit 4.13 linux-hwe
kernel.
Take node "fozzie"(Dell PowerEdge R320) for example, it works with
4.13.0-21.24~16.04.1 but not 4.13.0-25 / 4.13.0-26 / 4.13.0-31
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
** Tags added: kernel-bug-exists-upstream
--
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/1744379
Title:
I tried kernel 4.15.0-rc9 and had the same kind of hard lockup. The
system wouldn't react to mouse or keypresses after some idle time. The
log is attached (the kernel was upgraded on Jan 24-th). There are many
errors about soft lockups in the log, although the backtraces are
different from 4.13.
Is it possible that the lockups are caused by the buggy microcode update
from Intel? Did Canonical revert the microcode update?
--
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/1744379
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:
apport-collect 1745123
and then change the status of the bug to 'Confirmed'.
If, due to the
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:
apport-collect 1745118
and then change the status of the bug to 'Confirmed'.
If, due to the
Public bug reported:
Elasticsearch 2.4.6 can't start since new kernel upgrade
(4.13.0-31-generic #34~16.04.1-Ubuntu)
Kernel log contains :
[ 4308.595429] Oops: 0010 [#37] SMP NOPTI
[ 4308.595430] Modules linked in: btrfs xor raid6_pq ufs qnx4 hfsplus hfs minix
ntfs msdos jfs xfs libcrc32c bnep
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:
apport-collect 1745119
and then change the status of the bug to 'Confirmed'.
If, due to the
** Summary changed:
- Unable to boot with i386 4.13.0-25 / 4.13.0-26 / 4.13.0-31 kernel on Xenial
+ Unable to boot with i386 4.13.0-25 / 4.13.0-26 / 4.13.0-31 kernel on Xenial /
Artful
** Package changed: linux-hwe-edge (Ubuntu) => linux (Ubuntu)
** Description changed:
Some SRU testing
Public bug reported:
Hibernate process seems work and laptop (acer aspire v5-571G) shuts down
But then laptop doesn't turn on. Blank screen and you must to force shut down
with power button.
You must start system with another kernel.
I had the same problem with 4.13.0-26
** Affects: linux
After installing the proposed kernel:
sudo update-grub
[sudo] csola48 jelszava:
GRUB beállítófájl előállítása…
Figyelem: A GRUB_TIMEOUT beállítása egy nem nulla értékre, ha a beállított
GRUB_HIDDEN_TIMEOUT többé nem támogatott.
Megtalált linux lemezkép: /boot/vmlinuz-4.10.0-42-generic
Megtalált
Sorry this missed ...
With this option, the kernel 3 will not start, but the displayed text
will appear: grub_efi_secure_boot
--
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/1744979
You have been subscribed to a public bug:
Some SRU testing node cannot boot with the latest 32bit 4.13 linux-hwe
kernel.
Take node "fozzie"(Dell PowerEdge R320) for example, it works with
4.13.0-21.24~16.04.1 but not 4.13.0-25 / 4.13.0-26 / 4.13.0-31 kernel on
Xenial.
>From the BMC console, I
Please try this Linux kernel,
http://people.canonical.com/~khfeng/lp1745032/
--
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/1745032
Title:
AC adapter status not detected on Asus ZenBook
Hi there. I can confirm this problem still exists in newest kernels and
with the latest intel drivers as of today:
Jan 19 16:05:19 osd9 kernel: [511271.581413] i40e :02:00.1: TX driver issue
detected, PF reset issued
Jan 19 16:09:08 osd9 kernel: [511500.919380] i40e :02:00.0: TX driver
Since this bug appeared when I upgraded from zesty to artful, I reverted to
4.10.0-37 (the last kernel I had in zesty) and it had been rock-solid (it
becomes unresponsive from time to time but it recovers in a few seconds).
With each kernel upgrade I try the new one but the problem is still
/boot/grub/grub.cfg
#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#
### BEGIN /etc/grub.d/00_header ###
if [ -s $prefix/grubenv ]; then
set have_grubenv=true
load_env
fi
if [ "${next_entry}"
Also see
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1270676/comments/80
to install it with DKMS.
--
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/1730152
Title:
Internal microsd
You could try this driver: https://github.com/josch09/ampe_stor. From
the code, it seems supporting AU6601, AU6621, and AU6625, but it's not
working on my envy 13 ad110tu (AU6625). It can detect the card, and get
the capacity, but then many errors will occur and finally the reader
dies. Maybe it
** 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/1744979
Title:
grub_efi_secure_boot signal at the beginning of the
101 - 138 of 138 matches
Mail list logo
