Thank you for your reply!
I did the BIOS upgrade. I'll force an empty battery occurence, and check
what Ubuntu says upon boot afterwards.
sander@HPtje:~$ sudo dmidecode -s bios-version sudo dmidecode -s
bios-release-date
68SRR Ver. F.41
05/22/2013
sander@HPtje:~$
--
You received this bug
Update:
Still happens with that BIOS.
[Hewlett-Packard HP ProBook 4530s] suspend/resume failure
sander@HPtje:~$ sudo dmidecode -s bios-version sudo dmidecode -s
bios-release-date
68SRR Ver. F.41
05/22/2013
sander@HPtje:~$
--
You received this bug notification because you are a member of
OK: I just installed 12.04.3 (32-bit, not 64-bit, if that matters) on
the same machine. Fully updated.
I'll force the empty-battery and see what happens afterwards.
sander@sander12043:~$ uname -a
Linux sander12043 3.8.0-29-generic #42~precise1-Ubuntu SMP Wed Aug 14 15:31:16
UTC 2013 i686 i686
An interesting result:
With 13.10, when I close the laptop lid and remove the power cable, after one
night the battery will be empty and upon a fresh, powered boot I will get the
crash reported here.
With 12.04.3, with the closed lid removed power cable, after one night the
laptop could just
In a new setup (Sitecom router, no more Zyxel) and Ubuntu 13.10, I still
have the same problem via Wifi:
[ 1782.075212] IPv6: wlan0: IPv6 duplicate address
2001:abc:1234:b45d:1af4:6aff:fe9c:ced4 detected!
[ 1813.616483] IPv6: wlan0: IPv6 duplicate address
2001:abc:1234:b45d:1af4:6aff:fe9c:ced4
Public bug reported:
Just started Ubuntu 13.10 and got this error.
ProblemType: KernelOops
DistroRelease: Ubuntu 13.10
Package: linux-image-3.10.0-6-generic 3.10.0-6.17
ProcVersionSignature: Ubuntu 3.10.0-6.17-generic 3.10.3
Uname: Linux 3.10.0-6-generic i686
Annotation: This occured during a
I still get apportcheckresume crash reports on my fully updated system.
$ uname -a
Linux R540 3.8.0-25-generic #37-Ubuntu SMP Thu Jun 6 20:47:07 UTC 2013 x86_64
x86_64 x86_64 GNU/Linux
So ... not solved.
--
You received this bug notification because you are a member of Kernel
Packages, which
I can't; too difficult for me. Sorry.
Close this bug report if you want to.
--
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/1285304
Title:
NETDEV WATCHDOG: eth0 (sky2): transmit queue 0
In the meantime, I decided 14.04 was unusable.for me.
So I've done a fresh install of Vivid (15.04-to-be) daily version. That has
linux kernel 3.18, right? In one hour of usage, I've not seen the error message
in dmesg.
TBC
--
You received this bug notification because you are a member of
Public bug reported:
On my HP Stream 13 laptop with Ubuntu 14.04 LTS (fully updated) I
sometimes (once an hour?) get the error below in dmesg. It has to do
with the eMMC / eMMC reader. There is no other flash device (like a USB
key) installed or in use.
Yesterday the file system turned
@myself:
It was a noob thing indeed:
I had
linux-headers-3.19.0-031900rc7-generic_3.19.0-031900rc7.201502020035_amd64.deb
linux-image-3.19.0-031900rc7-generic_3.19.0-031900rc7.201502020035_amd64.deb
and needed the all.deb file too:
FWIW: the Read-only file system error occured again. See below.
Nothing special in dmesg nor /var/log/syslog
sander@superstream:~$ pwd
/home/sander
sander@superstream:~$ touch blabla
touch: cannot touch ‘blabla’: Read-only file system
sander@superstream:~$ mount
/dev/mmcblk0p5 on / type ext4
I logged off, restarted, and the Ubuntu boot GUI says / needs to be
fixed (I pressed F) and /tmp is not (yet) ready. I did get a Ubuntu
brown screen, but no login. I'm typing this in some 'other' OS.
I'll see if I can boot into Ubuntu with another boot.
--
You received this bug notification
Happens on my system too. I did a fresh install of Vivid daily two days
ago (Feb 3), did a update/upgrade today (Feb 5), and after the reboot
dmesg shows:
[ 11.252422] [ cut here ]
[ 11.252475] kernel BUG at /build/buildd/linux-3.18.0/mm/slub.c:3334!
[ 11.252526]
I've installed v3.19-rc7-vivid (thus now running
3.19.0-031900rc7-generic) and the dmesg message is gone now. Good!
FWIW: with
linux-headers-3.19.0-031900rc7-generic_3.19.0-031900rc7.201502020035_amd64.deb
linux-image-3.19.0-031900rc7-generic_3.19.0-031900rc7.201502020035_amd64.deb
I did
sudo
Second reboot worked. I did some extensive disk writing (around 1GB),
got the read-only problem, and dmesg says:
[ 962.226687] sdhci: Timeout waiting for Buffer Read Ready interrupt during
tuning procedure, falling back to fixed sampling clock
[ 972.262988] mmc0: Timeout waiting for hardware
Solved by installing the kernel from http://kernel.ubuntu.com/~kernel-
ppa/mainline/daily/2015-02-10-vivid/ leading to 3.19.0-999-generic
#201502092105
According to https://bugzilla.kernel.org/show_bug.cgi?id=92981 the
kernel on http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.19-vivid/ was
built
After 24 hours of use, still no slub.c error message in dmesg.
$ dmesg | grep -i slub
[0.00] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
[0.00] Linux version 3.18.0-13-generic (root@gloin) (gcc version
4.9.2 (Ubuntu 4.9.2-10ubuntu5) ) #14 SMP Tue Feb 17 11:13:29
Running 3.19.0-994-generic #201502112105 from http://kernel.ubuntu.com
/~kernel-ppa/mainline/drm-intel-nightly/2015-02-12-vivid/ and now dmesg
shows a warning in a different line of intel_display.c:
[ 2702.807816] WARNING: CPU: 0 PID: 3 at
Thanks! I'll do that tonight.
Question: should I install all four debs, so also the linux-image-extra?
--
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/1418286
Title:
kernel BUG at
Ouch, it's still there in 3.18.0-13-generic:
sander@superstreamer:~$ uname -a
Linux superstreamer 3.18.0-13-generic #14-Ubuntu SMP Fri Feb 6 09:55:14 UTC
2015 x86_64 x86_64 x86_64 GNU/Linux
sander@superstreamer:~$
sander@superstreamer:~$ dmesg | grep -i slub
[0.00] SLUB: HWalign=64,
OK, now running that new kernel. Well, at least I think it is, but it
says:
$ uname -a
Linux superstreamer 3.18.0-13-generic #14-Ubuntu SMP Fri Feb 6 09:55:14 UTC
2015 x86_64 x86_64 x86_64 GNU/Linux
Made on Feb 6? Can that be right? There was no sign of
3.18.0-13.14~lp1418286v1 in my Grub menu,
Thanks.
Current situtation:
sander@superstreamer:~$ uptime dmesg | grep -i -e Linux version -e slub
22:22:32 up 2:59, 1 user, load average: 1,74, 0,90, 0,70
[0.00] Linux version 3.18.0-13-generic (buildd@komainu) (gcc version
4.9.2 (Ubuntu 4.9.2-10ubuntu5) ) #14-Ubuntu SMP Fri Feb
Rebooted, and same result
sander@superstreamer:~$ uname -a
Linux superstreamer 3.18.0-13-generic #14-Ubuntu SMP Fri Feb 6 09:55:14 UTC
2015 x86_64 x86_64 x86_64 GNU/Linux
sander@superstreamer:~$
sander@superstreamer:~$ dpkg -l | grep -e linux-image- -e ^|
|
After the autoremove purge, reboot into 3.19, and a fresh install of
your kernel debs, things look better:
sander@superstreamer:~$ dmesg | grep -i -e Linux version -e slub
[0.00] Linux version 3.18.0-13-generic (root@gloin) (gcc version 4.9.2
(Ubuntu 4.9.2-10ubuntu5) ) #14 SMP Tue Feb
FWIW:
I also installed the lowlatency version of kernel 3.19, and that dmesg
doesn't show the lines Request for unknown module key 'Magrathea:
Glacier signing key:
sander@superstreamer:~$ uname -a
Linux superstreamer 3.19.0-031900-lowlatency #201502091451 SMP PREEMPT Mon Feb
9 14:58:45 UTC 2015
I just installed kernel 3.19 on vivid (source: http://kernel.ubuntu.com
/~kernel-ppa/mainline/v3.19-vivid/), and dmesg shows 129 lines with
Request for unknown module key 'Magrathea: Glacier signing key:
007271576a09d86ef244371b0633e47abb75b89d' err -11
So ... is this a regression bug? Or
Public bug reported:
Running Vivid with kernel 3.19 (debs from http://kernel.ubuntu.com
/~kernel-ppa/mainline/v3.19-vivid/), I get the warning below in dmesg.
I can't use ubuntu-bug linux because I get It appears you are
currently running a mainline kernel. It would be better to report this
bug
** Attachment added: lspci-vnvn.log
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1420290/+attachment/4316320/+files/lspci-vnvn.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
These seem the same bug reports on Redhat, since january
https://bugzilla.redhat.com/show_bug.cgi?id=1190511
https://bugzilla.redhat.com/show_bug.cgi?id=1181071
https://bugzilla.redhat.com/show_bug.cgi?id=1184161
https://bugzilla.redhat.com/show_bug.cgi?id=1183209
** Bug watch added: Red Hat
FWIW:
I'm now running the latest 3.18 (3.18.0-13-generic) which arrived today
(Feb 10), and no more slub.c messages in dmesg.
So ... was it solved in 3.18.0-13-generic?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
full dmesg
** Attachment added: dmesg-3.18.0-13-generic.txt
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1418286/+attachment/4319682/+files/dmesg-3.18.0-13-generic.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
I never close the lid immediately after booting, so in my case that
cannot have been the cause.
So far I have not found a correlation between the intel drm flip error
and things I did. Sometimes the error occurs after an hour, sometimes
not for two days. Now it is even 5 days ago:
$ cat
The error occured twice in the last 24 hours:
$ cat /var/log/kern.log | grep -i flip
Mar 2 23:13:04 superstreamer kernel: [ 3283.556389] WARNING: CPU: 0 PID: 0 at
/home/kernel/COD/linux/drivers/gpu/drm/i915/intel_display.c:9698
intel_check_page_flip+0xe6/0xf0 [i915]()
Mar 2 23:13:04
FWIW: I searched for [drm:intel_pipe_update_end [i915]] *ERROR* Atomic
update failure on pipe A (start=76355 end=76356) and found this source
code on http://lists.freedesktop.org/archives/intel-
gfx/2014-February/040161.html doing the Atomic update failure on pipe:
115 static void
FWIW: 12 seconds before the described problem, there is this line in
dmesg:
[drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe
A (start=76355 end=76356)
which I can't find on Google.
More from dmesg:
$ dmesg | grep Linux version
[0.00] Linux version
drm.debug=0xe added kernel command line:
$ dmesg | head
[0.00] Initializing cgroup subsys cpuset
[0.00] Initializing cgroup subsys cpu
[0.00] Initializing cgroup subsys cpuacct
[0.00] Linux version 3.19.0-16-generic (buildd@komainu) (gcc version
4.9.2 (Ubuntu
The attachment contains the complete dmesg with drm turned on.
Snippet from around the flip message:
[ 7538.988560] [drm:valleyview_update_wm] Setting FIFO watermarks - A:
plane=111, cursor=2, B: plane=2, cursor=2, SR: plane=60, cursor=2
[ 7538.988565] [drm:intel_set_memory_cxsr] memory
dmesg with drm-debu and flip switch problem
** Attachment added: dmesg with drm-debu and flip switch problem
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1420290/+attachment/4396622/+files/dmesg.with-flip-problem-and-drm-debug.txt
--
You received this bug notification because you
Public bug reported:
Just a warning, but maybe to useful to report what dmesg is telling me:
[ 4653.114802] sdhci: Timeout waiting for Buffer Read Ready interrupt during
tuning procedure, falling back to fixed sampling clock
[ 4653.116957] [ cut here ]
[ 4653.116995]
Thanks.
Full computer name: HP Stream 13, HP 13-c000nd-N2840 aka HP 13-c000nd.
There is no sticker on the computer, but an imprint saying Model
13-c000nd. Is that enough information?
There is no Memtest86+ in the Grub boot menu and I can't add it, so I ran
Memtst86+ (V6.0.0 Free) from a USB
Ouch. I had looked for a BIOS upgrade, but I had not been able to find
it. Thank you for your work.
I just upgraded to F.06 (now: DMI: Hewlett-Packard HP Stream Notebook
PC 13/802A, BIOS F.06 01/06/2015), and I'll monitor the effect.
Thanks again.
--
You received this bug notification because
Public bug reported:
The below logging is shown in dmesg. I'm not sure if it's a
kernel/software or a hardware problem.
[za apr 4 13:07:54 2015] ACPI Error: [PMIN] Namespace lookup failure,
AE_NOT_FOUND (20141107/psargs-359)
[za apr 4 13:07:54 2015] ACPI Error: Method parse/execution failed
Still (again?) happening with 3.19.0-12-generic
[ 5578.584172] [ cut here ]
[ 5578.584230] WARNING: CPU: 0 PID: 15321 at
/build/buildd/linux-3.19.0/drivers/gpu/drm/i915/intel_display.c:9713
intel_check_page_flip+0xda/0xf0 [i915]()
[ 5578.584233] Kicking stuck page flip:
Public bug reported:
[1.904158] kernel: [ cut here ]
[1.904159] kernel: i915 :00:02.0: drm_WARN_ON(val == 0x)
[1.904176] kernel: WARNING: CPU: 3 PID: 328 at
drivers/gpu/drm/i915/display/intel_tc.c:761 intel_tc_port_init+0x1c4/0x1d0
[i915]
[
Public bug reported:
Unstable Wifi
Sometimes most Wifi AP's (including my own) or not seen
dmesg filled with
[di feb 15 06:44:54 2022] rtw_8821ce :01:00.0: failed to send h2c command
[di feb 15 06:44:54 2022] rtw_8821ce :01:00.0: failed to send h2c command
[di feb 15 06:44:54 2022]
Still there in current Ubuntu 22.04 (fresh install, fully updated)
--
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/1960893
Title:
i915 gives trace in dmesg
Status in linux package in
Ah, it seems to happen after a fresh boot too: the login is there, mouse
is working, but keyboard not. It takes 20 - 30 seconds before keyboard
is working.
Snippet from dmesg (leaving out wlo1 stuff):
...
[di mei 31 20:09:47 2022] skl_hda_dsp_generic skl_hda_dsp_generic:
Public bug reported:
Fresh install of Ubuntu 22.04, fully updated, no changes or configuration at
all.
Newish HP laptop (so recent hardware)
Problem: After resuming from suspend, the laptop's keyboard is not
working for about 30 seconds (the laptop's touchpad is working at once).
Looking at
Interesting ... triggered by "[ 0.278602] i8042: PNP: PS/2 appears to
have AUX port disabled, if this is incorrect please boot with
i8042.nopnp", I just tried i8042.nopnp as only option in GRUB, and that
works too: keyboard works immediatly.
And that message was already in the first dmesg ... so
That second paragraph should read:
And that message was already in the first dmesg ... so the i8042 driver
already KNEW something was fishy, and hinted what I should do ... ?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
Only i8042.direct ... not good. Keyboard not working for x seconds
Only i8042.dumbkbd ... yes, works! Keyboard working immediatly.
So my /etc/default/grub now contains:
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash i8042.dumbkbd"
And stuff from dmesg:
sander@zwart2204:~$ sudo dmesg | grep i8042
[
Thanks for replying.
See included dmesg. I generated it with the following command ...
hopefully OK
sudo dmesg -T > dmesg_after_suspend_and_resume.txt
Snippet from dmesg:
[wo jun 1 11:38:40 2022] i8042: [28649] 65 -> i8042 (parameter)
[wo jun 1 11:38:40 2022] i8042: [28649] ab <- i8042
I tried "i8042.noaux=1", but no change: after boot and after resume:
touchpad works immediatly, but keyboard takes 25-45 seconds.
dmesg included
** Attachment added: "dmesg "i8042.noaux=1""
Ah, SOLVED, like this:
Triggered by your remarks, I found
https://unix.stackexchange.com/a/656183, which says:
RUB_CMDLINE_LINUX_DEFAULT="atkbd.reset i8042.reset i8042.nomux quiet splash".
If this doesn't work, follow the same process but try
GRUB_CMDLINE_LINUX_DEFAULT="i8042.direct
Out of curiosity:
The manual work (adding the line to GRUB): is that how it should be, or
a bug (something Ubuntu should take care of)?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Oct 25 18:27:53 ubuntu kernel: [ 4406.926779] Unable to handle kernel paging
request at virtual address ff983a94d92e
Oct 25 18:27:53 ubuntu kernel: [ 4406.955407] Oops [#2]
Oct 25 18:27:53 ubuntu kernel: [ 4406.978035] Modules linked in: tls(+) sr9700
dm9601 usbnet input_leds joydev
Public bug reported:
Hardware: Licheee RV Dock RISC-V Allwinner D1. Has been rockstable for
months with an image from Armbian person
Followed https://wiki.ubuntu.com/RISC-V/LicheeRV . After "sudo apt-get
install licheerv-rtl8723ds-dkms" (but without reboot), I got segfaults
for normal commands
apport says the below ...
$ apport-collect 1994490
Package linux-meta-allwinner-5.17 not installed and no hook available, ignoring
*** Updating problem report
No additional information collected.
Press any key to continue...
No pending crash reports. Try --help for more information.
--
You
File attached: syslog from around the Oops-es
ubuntu@ubuntu:/var/log$ cat syslog | grep Oops
Oct 25 18:27:24 ubuntu kernel: [ 4377.869176] Oops [#1]
Oct 25 18:27:53 ubuntu kernel: [ 4406.955407] Oops [#2]
Oct 25 18:27:57 ubuntu kernel: [ 4411.224132] Oops [#3]
Oct 25 18:28:06 ubuntu kernel: [
The segfault only happened with a fresh Ubuntu's LicheeRV image, written
to a separate SD-card.
The Armbian-like image was on another sd-card, not in the Lichee.
I will repeat the Ubuntu's LicheeRV image writing & boot & wifi-install
procedure to see if I can reproduce the problem (or that it
So I repeated the setup sequence ... and no segfaults. All is working
without any problems.
So ... close as a fluke?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta-allwinner-5.17 in Ubuntu.
62 matches
Mail list logo
