Prev: Info
Next: [PATCH 7/9] USB: serial: fix missing locking on fifo in write callback
From: Dieter Ries on 18 Mar 2010 03:10
On Thu, Mar 18, 2010 at 08:41:28AM +0300, Michael Tokarev wrote:
> Dieter Ries wrote:
> > On Wed, Mar 17, 2010 at 11:02:40PM +0100, Alexander Graf wrote:
> []
> >> Are you 100% sure you don't have vmware, virtualbox, parallels, whatever running in parallel on that machine?
> >
> > Definitely. I have virtualbox installed, but haven't used it in months.
> > The others I don't use at all, so they are not installed either.
>
> Dieter, we've talked with you on IRC yesterday...

Yes, I remember.

> Can you take a look at what's in the startup script sequence on
> your machine, and what modules are loaded which may be related?
> What I'm trying to say: I don't know how virtualbox works, but it
> may come with a kernel module or a bootup script that touches SVM
> settings.

I checked it again: I don't even have the virtualbox modules installed
for this kernel, I cannot modprobe them.

lsmod is here:
before modprobe kvm_amd
Module Size Used by
snd_pcm_oss 33062 0
snd_mixer_oss 13798 1 snd_pcm_oss
snd_seq_oss 23963 0
snd_seq_midi_event 5684 1 snd_seq_oss
snd_seq 44953 4 snd_seq_oss,snd_seq_midi_event
snd_seq_device 5481 2 snd_seq_oss,snd_seq
nvidia 9613596 40
snd_hda_codec_realtek 264327 1
snd_hda_intel 20099 4
snd_hda_codec 57443 2 snd_hda_codec_realtek,snd_hda_intel
snd_hwdep 5642 1 snd_hda_codec
snd_pcm 68342 4 snd_pcm_oss,snd_hda_intel,snd_hda_codec
snd_timer 17426 3 snd_seq,snd_pcm
snd 52486 17
snd_pcm_oss,snd_mixer_oss,snd_seq_oss,snd_seq,snd_seq_device,snd_hda_codec_realtek,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_pcm,snd_timer
soundcore 6287 1 snd
snd_page_alloc 7029 2 snd_hda_intel,snd_pcm
i2c_core 18944 1 nvidia

after:
Module Size Used by
kvm_amd 32387 0
kvm 249238 1 kvm_amd
snd_pcm_oss 33062 0
snd_mixer_oss 13798 1 snd_pcm_oss
snd_seq_oss 23963 0
snd_seq_midi_event 5684 1 snd_seq_oss
snd_seq 44953 4 snd_seq_oss,snd_seq_midi_event
snd_seq_device 5481 2 snd_seq_oss,snd_seq
nvidia 9613596 40
snd_hda_codec_realtek 264327 1
snd_hda_intel 20099 4
snd_hda_codec 57443 2 snd_hda_codec_realtek,snd_hda_intel
snd_hwdep 5642 1 snd_hda_codec
snd_pcm 68342 4 snd_pcm_oss,snd_hda_intel,snd_hda_codec
snd_timer 17426 3 snd_seq,snd_pcm
snd 52486 17
snd_pcm_oss,snd_mixer_oss,snd_seq_oss,snd_seq,snd_seq_device,snd_hda_codec_realtek,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_pcm,snd_timer
soundcore 6287 1 snd
snd_page_alloc 7029 2 snd_hda_intel,snd_pcm
i2c_core 18944 1 nvidia


This is a gentoo box, and there are no services started which are
related to virtualization. No autoloaded modules or anything. Just
standard desktop stuff + lvm and raid.

Runlevel: boot
hwclock [ started ]
modules [ started ]
lvm [ started ]
device-mapper [ started ]
fsck [ started ]
root [ started ]
mtab [ started ]
hostname [ started ]
localmount [ started ]
sysctl [ started ]
bootmisc [ started ]
sysklogd [ started ]
urandom [ started ]
termencoding [ started ]
consolefont [ started ]
net.lo [ started ]
staticroute [ started ]
mdadm [ started ]
swap [ started ]
acpid [ started ]
procfs [ started ]
keymaps [ started ]

modules is empty.

And additionally after boot:

Runlevel: default
sysklogd [ started ]
dbus [ started ]
hald [ started ]
xdm [ started ]
preload [ started ]
udev-postmount [ started ]
ntpd [ started ]
alsasound [ started ]
avahi-daemon [ started ]
cupsd [ started ]
sshd [ started ]
local [ started ]
Dynamic Runlevel: hotplugged
net.eth1 [ started ]
Dynamic Runlevel: needed
udev-mount [ started ]
sysfs [ started ]

> /mjt

cu
Dieter

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
From: Dieter Ries on 18 Mar 2010 03:20
On Wed, Mar 17, 2010 at 11:47:14PM +0100, Alexander Graf wrote:
> It looks like one of your CPUs has EFER_SVME enabled on bootup already. I'm not aware of code clearing EFER, so if there's garbage in there on boot it stays there.
>
> Could you please add the current CPU number to your printk? I bet it's always the same one.

[ 1300.393635] efer on CPU1 is d01
[ 1300.393638] efer on CPU3 is d01
[ 1300.393641] efer on CPU2 is d01
[ 1300.393643] EFER_SVME is 1000
[ 1300.393645] EFER_SVME is 1000
[ 1300.393646] EFER_SVME is 1000
[ 1300.393650] efer on CPU0 is 1d01
[ 1300.393652] EFER_SVME is 1000
[ 1300.393653] kvm: enabling virtualization on CPU0 failed


> If that's the case I'd say you have a broken BIOS or bootloader.

You are right, it seems to be always cpu0. I'll check my BIOS and flash
a newer version if available.

>
> Alex

cu
Dieter


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
From: Alexander Graf on 18 Mar 2010 03:20

On 18.03.2010, at 08:11, Dieter Ries wrote:

> On Wed, Mar 17, 2010 at 11:47:14PM +0100, Alexander Graf wrote:
>> It looks like one of your CPUs has EFER_SVME enabled on bootup already. I'm not aware of code clearing EFER, so if there's garbage in there on boot it stays there.
>>
>> Could you please add the current CPU number to your printk? I bet it's always the same one.
>
> [ 1300.393635] efer on CPU1 is d01
> [ 1300.393638] efer on CPU3 is d01
> [ 1300.393641] efer on CPU2 is d01
> [ 1300.393643] EFER_SVME is 1000
> [ 1300.393645] EFER_SVME is 1000
> [ 1300.393646] EFER_SVME is 1000
> [ 1300.393650] efer on CPU0 is 1d01
> [ 1300.393652] EFER_SVME is 1000
> [ 1300.393653] kvm: enabling virtualization on CPU0 failed
>
>
>> If that's the case I'd say you have a broken BIOS or bootloader.
>
> You are right, it seems to be always cpu0. I'll check my BIOS and flash
> a newer version if available.

Please do. If that doesn't help ping me again. I'll write up a quirk patch then.


Alex--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
From: Dieter Ries on 18 Mar 2010 22:30
On Thu, Mar 18, 2010 at 08:17:01AM +0100, Alexander Graf wrote:
> On 18.03.2010, at 08:11, Dieter Ries wrote:
> > You are right, it seems to be always cpu0. I'll check my BIOS and flash
> > a newer version if available.
>
> Please do. If that doesn't help ping me again. I'll write up a quirk patch then.

It seems you were right, I flashed the BIOS to the latest version and
now it is working.

So thanks everybody, and sorry for the inconvenience.

> Alex

cu
Dieter

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
First  |  Prev  | 
Pages: 1 2
Prev: Info
Next: [PATCH 7/9] USB: serial: fix missing locking on fifo in write callback