Bug#680629: amd64-microcode: microcode: CPU0: update failed for patch_level=0x010000db

2012-07-07 Thread j...@jppozzi.dyndns.org
Hello,

I restart the machine on a older kernel : 3.2.0-3-amd64
and it works  after "modprobe microcode"

Linux version 3.2.0-3-amd64 (Debian 3.2.21-3)
(debian-ker...@lists.debian.org) (gcc version 4.6.3 (Debian 4.6.3-8) )
#1 SMP Thu Jun 28 09:07:26 UTC 2012

grep microcode kern.log
... microcode: CPU0: patch_level=0x01c6
... microcode: CPU0: new patch_level=0x01db
... microcode: CPU1: patch_level=0x01c6
... microcode: CPU1: new patch_level=0x01db
... microcode: CPU2: patch_level=0x01c6
... microcode: CPU2: new patch_level=0x01db
... microcode: CPU3: patch_level=0x01c6
... microcode: CPU3: new patch_level=0x01db
... microcode: Microcode Update Driver: v2.00
, Peter Oruba

Should be related to kernel version, will try with other versions.

Regards,

JP P




-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org



Bug#680629: closed by Henrique de Moraes Holschuh (Re: Bug#680629: amd64-microcode: microcode: CPU0: update failed for patch_level=0x010000db)

2012-07-07 Thread j...@jppozzi.dyndns.org
Hello,

OK to close the bug, I had another try with a 3.4.4 kernel and it works.
Will load the last kernel verson and have a try.

Regards

JP P




-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org



Bug#641098: VM does not launch

2012-07-14 Thread j...@jppozzi.dyndns.org
Le jeudi 12 juillet 2012 à 11:26 -0600, Ian Campbell a écrit :
> Hi JP,
> 
> Wheezy currently has a 3.2 kernel -- does this still happen with this?
> 
> If yes then I expect the xend.log (rater than the libvirt log) would be
> the place to look for clues.
> 
> Ian.
> 
> 
Hello Ian,

That nasty bug does not exists any more with 3.2, 3.3, 3.4 and even
3.5-rc6 (I try it yesterday). I try all newer kernels without any
problem. I think it was only a 3.1 related bug.
With all newer kernels all VMs are starting as usual.

Regards

JP P


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org



Bug#623491: wicd-daemon: Can't install through dpkg

2011-04-20 Thread j...@jppozzi.dyndns.org
Package: wicd-daemon
Version: 1.7.0+ds1-6
Severity: grave
Tags: d-i
Justification: renders package unusable

Hello,
I can't install through dpkg, terminal trace follows :

dpkg -i wicd-daemon_1.7.0+ds1-6_all.deb
(Reading database ... 154087 files and directories currently installed.)
Unpacking wicd-daemon (from wicd-daemon_1.7.0+ds1-6_all.deb) ...
dpkg: error processing wicd-daemon_1.7.0+ds1-6_all.deb (--install):
 unable to open '/usr/share/locale/fr/LC_MESSAGES/wicd.mo.dpkg-new': No such
file or directory
Processing triggers for man-db ...
Errors were encountered while processing:
 wicd-daemon_1.7.0+ds1-6_all.deb


Regards

JP P



-- System Information:
Debian Release: 6.0.1
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 2.6.36.2 (SMP w/2 CPU cores; PREEMPT)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org