Hi Ben,
On Sat, Dec 27, 2014 at 03:15:52PM +0100, Ben Hutchings wrote:
> Never mind, I've seen your later message with a complete log and I will
> reply to that.
I haven't heard back from you, but in the meantime reformatted the
machine from i386 (i686) to amd64, but also upgraded to testing, an
On Sat, 2014-12-27 at 15:13 +0100, Ben Hutchings wrote:
> On Sat, 2014-12-27 at 11:20 +, Toni Mueller wrote:
> [...]
> > I am confused because the output is really not that much more verbose
> > than the screnshots, but here you are:
> >
> >
> > [ 22.224014] INFO: rcu_sched self-detected st
On Sat, 2014-12-27 at 11:20 +, Toni Mueller wrote:
[...]
> I am confused because the output is really not that much more verbose
> than the screnshots, but here you are:
>
>
> [ 22.224014] INFO: rcu_sched self-detected stall on CPU { 1} (t=5251
> jiffies g=-153 c=-154 q=307)
What happene
Hi Ben,
possibly unrelated, but neither the kernels of the Ubuntu installers for
12.04 and 14.04, nor the kernel for Fedora 21 installer, even boot on my
VM. I reckoned that you might be interested, being a kernel hacker.
CentOS 6.5 or OpenBSD 5.6 don't have a problem, though.
Kind regards,
--
Hi Ben,
I tweaked it a bit, and now I get much more telling messages:
[0.00] Initializing cgroup subsys cpuset
[0.00] Initializing cgroup subsys cpu
[0.00] Initializing cgroup subsys cpuacct
[0.00] Linux version 3.16.0-0.bpo.4-686-pae
(debian-ker...@lists.debia
Hi Ben,
On Sat, Dec 27, 2014 at 02:39:06AM +0100, Ben Hutchings wrote:
> 1, Enable an emulated serial port for the VM, with output going to a
> file.
I modified the VM to have:
> 2. Enable a serial console on the kernel command line.
I added thi
On Tue, 2014-12-09 at 22:51 +, Toni Mueller wrote:
>
>
> Hi Ben,
>
> On Tue, Dec 09, 2014 at 06:11:09PM +, Ben Hutchings wrote:
> > Also, this is assigned to linux-image-3.16-0.bpo.3-686-pae but the
> > screenshot you attached shows that package being newly installed.
> > Therefore it is
Hi Ben,
On Tue, Dec 09, 2014 at 06:11:09PM +, Ben Hutchings wrote:
> Also, this is assigned to linux-image-3.16-0.bpo.3-686-pae but the
> screenshot you attached shows that package being newly installed.
> Therefore it is not the kernel you were running at the time you first
> saw this prob
Control: retitle -1 VM becomes unresponsive - soft lockup, RCU stall
Control: severity -1 important
Control: reassign -1 src:linux
Control: tag -1 moreinfo
On Tue, 2014-12-09 at 14:53 +, Toni Mueller wrote:
> severity 771661 grave
> thanks
Sorry, no, you've only seen one broken VM.
Also, th
severity 771661 grave
thanks
Hi,
I guess the same would apply to #771602, but I would like to not go
the extra five miles to reproduce it there. In any case, a kernel
that maxes out the CPU immediately after start while doing nothing
is not entirely production quality (although I have very go
10 matches
Mail list logo
