Public bug reported:
This started to happen only with newer kernel versions. The WiFi was
previously absolutely solid. When the WiFi connection drops, there are
clear kernel error messages:
Apr 08 22:39:29 konstantin kernel: iwl3945 :02:00.0: Queue 4 stuck for 2048
ms.
Apr 08 22:39:30 kons
Public bug reported:
Here documents from the command line with tabs are not handled
correctly. Here is a transcript showing the problem - there is a tab in
front of "This is indented" in the file:
dzu@zarniwoop:~$ cat tab-test
#!/bin/bash
cat < This is unindented
> This is indented
> STOP
This
Hi Bill,
as far as I can see, this is not a systemd but a Ubuntu problem. My
Debian machines enter rescue mode just fine with systemd. Youncan
circumvent this by talking to systemd directly as described in my blog
post http://blog.lazy-evaluation.net/posts/linux/ubuntu-16-04-entering-
recovery.htm
Public bug reported:
Typing "systemctl rescue" in a running system brings down the system and
prompts
Welcome to rescue mode! After logging in, type "journalctl -xb" to view
system logs, "systemctl reboot" to reboot, "systemctl default" or ^D to
boot into default mode.
Press Enter for maintenance
One more info - after making the journal persistent, this is the end of
the journal for the session ending with the hang:
Feb 04 16:22:00 harry systemd[1]: Stopped ACPI Events Check.
Feb 04 16:22:00 harry systemd[1]: Stopped target Sockets.
Feb 04 16:22:00 harry systemd[1]: Closed UUID daemon
** Attachment added: "Journal for rescue session"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1662137/+attachment/4813978/+files/journalctl-b-1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/b
Public bug reported:
Selecting "Rescue" shell from the "Advanced options" menu in grub enters
the "friendly-recovery" service and allows to drop into a root shell.
After ~120 seconds, systemd sees a timeout and starts another "friendly-
recovery" whiptail process. This and the running shell now c
** Attachment added: "Output of "systemd-analyze blame" for the session after
the rescue session"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1662137/+attachment/4813979/+files/systemd-analyze-blame
--
You received this bug notification because you are a member of Ubuntu
Bugs, whi
I also do see this flaky behaviour of rescue mode. The new bug report
includes some more information:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1662137
Apparently on my machine systemd runs into a timeout waiting for swap-
or non-root partitions.
Unfortunately, entering rescue mode f
Public bug reported:
Serving NFS filesystems for my embedded board through UDP crashes with
this kernel reliably. Downgrading to the -50 kernel solves the problem.
Here is one backtrace collected just now:
Oct 22 18:22:04 harry kernel: [ 91.718996] BUG: unable to handle kernel NULL
pointer d
** Changed in: linux-lts-utopic (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1494492
Title:
package linux-image-3.16.0-49-generic (not installed) failed to
Upgrading to the -52 kernel version solves the problem.
** Changed in: linux-lts-utopic (Ubuntu)
Status: New => 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/1509010
Title:
NFS
Hi JC,
the output of the "df" command that you attached to the bug clearly
shows that /boot has no free space left:
Dateisystem 1K-blocks Benutzt Verfügbar Verw% Eingehängt auf
[...]
/dev/sda1 240972 236687 0 100% /boot
You should check /boot. Yo
13 matches
Mail list logo
