Yep, got the same issue on trusty.
The last thing on the console I see is setting up libc6:amd64 and then it
changes into a black screen with a blinking cursor.
When I boot by adding text to grub I see a kernel panic which I am unable to
capture in a log file.
--
You received this bug
My system, 64-bit Trusty, also got this bug when running 'sudo dpkg --configure
-a'.
Alas, there are no log entries for this panic.
Please, take a look at the attachments and initctl list output below:
user-03-709@709-3:~$ initctl list
indicator-application start/running, process 2626
@Aurel - please raise a new bug by running ubuntu-bug upstart as this
will attach all relevant information to the bug to allow us to
investigate the problem. Thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@alien: Please raise a new bug with full details - take a picture of the
screen showing these messages if possible and attach to the bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1120660
Title:
Almost every update now on Ubuntu 13.10 gives kernel panic during update.
Message like kernel panic ... something about ..init..
next line drm_kms_helper: panic occurred, switching back to text console
lenovo g575. i386
--
You received this bug notification because you are a member of Ubuntu
@Rafal - yes, the problem has been fixed in Ubuntu. Are you sure you are
specifying the --no-log option correctly (two leading dashes)? The
problem that was fixed relates directly to logging and that option
disables logging entirely.
If you still have a problem, please do the following:
1)
Has this been fixed? I seem to be affected by this bug, yet I cannot
update upstart to the newest version, as it triggers kernel panic when
it's configured. I also cannot boot up with the --no-log option, because
this causes a kernel panic immediately when the system begins to boot. I
would
** Changed in: upstart
Status: Confirmed = Fix Released
** Changed in: upstart (Ubuntu)
Status: Confirmed = 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/1120660
Title:
** Branch linked: lp:upstart
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1120660
Title:
Kernel Panic when running 'sudo dpkg --configure -a' ?
To manage notifications about this bug go to:
I have the same problem.
I have my /var/log/ folder in a tmpfs filesystem and the dpkg
--configure -a and I have a script to create the default /var/log and
/var/cache folders. The folder /var/log/upstart exists.
Please, can you explain me where I need to add the --no-log option?
Thanks :)
--
@Lito
in the grub boot screen (if you don't see it, press shift right after bios,
sometimes you need to try several times as for me it doesn't always works and
it just boots right away)
use the 2nd entry (advanced i think it is called)
than highlight the first entry and hit e to edit
there you
Ok, it's the same line that I can edit in /etc/default/grub?
GRUB_CMDLINE_LINUX_DEFAULT=quiet splash elevator=deadline
to
GRUB_CMDLINE_LINUX_DEFAULT=quiet splash elevator=deadline --no-log
Thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Me too am affected by this bug. after the last raring upgrade, the process is
terminated with the message:
E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to
correct the problem.
After running the command offered, I came across the bug 'kernel panics'
see the attached
Rainer - thanks for reporting this bug.
Please could those affected by this bug comment on whether:
- /var/log/upstart/ exists and is writeable
- their disks are full ('df -h')
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
... also, if you can recreate the problem via 'sudo telinit u', please
can you run the following command (does not need to be run as root) and
append the details to this bug:
initctl list
Thanks
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
here is the results of the following command
philuser@meghost:~$ ls -la /var/log/upstart/
total 380
drwxr-xr-x 1 root root 3774 févr. 11 09:19 .
drwxr-xr-x 1 root root 1270 févr. 11 10:36 ..
-rw-r- 1 root root 81 févr. 6 22:14 alsa-restore.log.1.gz
-rw-r- 1 root root 81 févr. 5
@philuser - thanks, but pleaes can you run 'initctl list' on a system
that exhibits the bug when 'sudo telinit u' is run?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1120660
Title:
Kernel Panic
All my command were made for the system affected by the bug, that after
reboot because the bug completely freezes the computer.
I am a dipose perform other test, if you want.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
'sudo telinit u' crash immediaty the PC.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1120660
Title:
Kernel Panic when running 'sudo dpkg --configure -a' ?
To manage notifications about this bug
'sudo telinit u' command crashes the pc with the symptom already
described, then it is no longer possible to switch from another order
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1120660
Title:
To chime in myself and give a differential diagnosis ...
I don’t have /var/log/upstart because /var/log is a tmpfs. Do I have to
create this subfolder?
Here’s the output from my PC:
towolf@ovo:~$ initctl list
avahi-daemon start/running, process 845
mountall-net stop/waiting
@Tobias - thanks for confirming. It seems this bug relates to directory
/var/log/upstart/ not existing (it will have been auto-created on a
default system).
So, one way to work around this issue is to simply create the directory:
$ sudo mkdir -p /var/log/upstart
(This avoids having to modify
James, I cannot confitm that this fixes the issue.
Manually creating it with mkdir /var/log/upstart and doing telinit u
still panicked the kernel.
Then I put mkdir /var/log/upstart into /etc/rc.local and it still
panicked after a reboot.
Is it that the creation happens too late?
--
You
** Changed in: upstart (Ubuntu)
Importance: Undecided = High
** Changed in: upstart (Ubuntu)
Assignee: (unassigned) = James Hunt (jamesodhunt)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I am now able to reproduce this issue.
The simplest way to work around this issue until we release an update is
to boot with '--no-log' to stop Upstart logging any job output.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Also affects: upstart
Importance: Undecided
Status: New
** Changed in: upstart
Importance: Undecided = High
** Changed in: upstart
Status: New = Confirmed
** Changed in: upstart
Assignee: (unassigned) = James Hunt (jamesodhunt)
--
You received this bug notification
Right... it work for me
Thank
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1120660
Title:
Kernel Panic when running 'sudo dpkg --configure -a' ?
To manage notifications about this bug go to:
workaround with --no-log worked
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1120660
Title:
Kernel Panic when running 'sudo dpkg --configure -a' ?
To manage notifications about this bug go to:
I get this too and have narrowed it down to the re-exec of upstart in
some packages dpkg postinst scripts.
To trigger the panic you can just run sudo telinit u
When I removed the Upstart rexec lines from libc6 and libjson0 postinst
the dpkg configure went through.
** Package changed: linux
Ok, just now tried to click on software updater from the Unity
launcher, an I got a kernel panic right away. :(
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1120660
Title:
Kernel Panic when
To catch the kernel panic message, I ran apt-get update apt-get dist-
upgrade from the command-line. Please see screenshot attached. I can
reproduce this every time.
** Attachment added: 2013-02-09 16.51.06.jpg
I guess it comes down to lib6c:i386. I believe I need this to run
Crossover and Skype and whatnot...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1120660
Title:
Kernel Panic when running 'sudo
32 matches
Mail list logo
