Bug#410066: gcc-4.1: inconsistency of char signedness between different platforms
Package: gcc-4.1
Version: 4.1.1-21
Severity: normal
Hi,
The following code produce different outputs on x86 platform and powerpc
platform:
~$ cat a.c
#include
int main (void)
{
char ch [2] = { 127, 180 };
signed char sch [2] = { 127, 180 };
unsigned uch [2] = { 127, 180 };
printf ("char: %d %d\n", ch[0], ch[1]);
printf ("signed char: %d %d\n", sch[0], sch[1]);
printf ("unsigned char: %d %d\n", uch[0], uch[1]);
};
x86 or x64 platform, it outputs:
~$ ./a.out
char: 127 -76
signed char: 127 -76
unsigned char: 127 180
powerpc platform, it outputs:
~$ ./a.out
char: 127 180
signed char: 127 -76
unsigned char: 127 180
a.c is compiled by `gcc a.c`
I found this problem when checking the fcitx crash problem on ppc
platform. After a deep digging, I found the problem was caused by the
default signedness of char.
After adding `signed` to force the compiler use the singed char, fcitx
works well on ppc.
I found the fcitx crashing prolem on ppc more than 3 months ago. I
had no time to report it till today. So this problem has been there for
more than 3 months.
I'm not quite sure if the debian building system is using gcc-4.1. But
apprently this problem exists in the gcc which debian building system
is using.
There may be other packages affected by this problem.
Best Regards,
Bin Tian
-- System Information:
Debian Release: 4.0
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-3-amd64
Locale: LANG=zh_CN, LC_CTYPE=zh_CN (charmap=GB2312)
Versions of packages gcc-4.1 depends on:
ii binutils2.17-3 The GNU assembler, linker and bina
ii cpp-4.1 4.1.1-21 The GNU C preprocessor
ii gcc-4.1-base4.1.1-21 The GNU Compiler Collection (base
ii libc6 2.3.6.ds1-10 GNU C Library: Shared libraries
ii libgcc1 1:4.1.1-21 GCC support library
ii libssp0 4.1.1-21 GCC stack smashing protection libr
Versions of packages gcc-4.1 recommends:
ii libc6-dev 2.3.6.ds1-10 GNU C Library: Development Librari
pn libmudflap0-dev(no description available)
-- no debconf information
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#409999: fcitx crash when using wubi input method on powerpc platform
410066 is closed. The following is the explanation I got
quote,
This is allowed by the C standard; the signedness of char is
implementation-defined. Moreover, we cannot change it, since that
would break the ABI. So this is not a bug.
unquote,
Due to the reason explained, fcitx should be patched.
Bin Tian
Bin Tian wrote:
> I got the acknowledgement. The reference is bug#410066
>
> Bin Tian
>
> Bin Tian wrote:
>> I found the problem. gcc-4.1 under ppc behaves differently for the
>> default signedness of char. I have already reported this bug to
>> [EMAIL PROTECTED] of debian, but I havn't got the reply of BTS at the
>> moment. So I can't give you the reference now.
>>
>> The following codes describe the problem clearly.
>>
>> ~$ cat a.c
>>
>> #include
>> int main (void)
>> {
>> char ch [2] = { 127, 180 };
>> signed char sch [2] = { 127, 180 };
>> unsigned uch [2] = { 127, 180 };
>>
>> printf ("char: %d %d\n", ch[0], ch[1]);
>> printf ("signed char: %d %d\n", sch[0], sch[1]);
>> printf ("unsigned char: %d %d\n", uch[0], uch[1]);
>> };
>>
>> x86 or x64 platform, it outputs:
>> ~$ ./a.out
>> char: 127 -76
>> signed char: 127 -76
>> unsigned char: 127 180
>>
>> powerpc platform, it outputs:
>> ~$ ./a.out
>> char: 127 180
>> signed char: 127 -76
>> unsigned char: 127 180
>>
>> For a work around, I changed the definition/declaration of CalHZIndex
>> in src/tools.h and src/tools.c.
>> The modified version of CalHZIndex is int CalHZIndex (signed char
>> *strHZ);
>> Then fcitx works well as before.
>>
>> Thanks a lot for your kindly support!
>>
>> Best Regards,
>> Bin Tian
>>
>>
>> Guanghui Yu wrote:
>>> Thanks ;)
>>>
>>> On 2/7/07, Bin Tian <[EMAIL PROTECTED]> wrote:
>>>>
>>>> I will try to make a debug version tonight. I have no time to find
>>>> out the
>>>> reason in office.
>>>> Further information may be available tomorrow morning.
>>>>
>>>> Bin Tian
>>>>
>>>>
>>>> Guanghui Yu wrote:
>>>> Have no idea now. I don't have ibook for testing. :( I am checking the
>>>> difference between 3.1.1 and 3.4. Do you try other Wubi tables?
>>>>
>>>> On 2/7/07, Bin Tian <[EMAIL PROTECTED]> wrote:
>>>>
>>>>
>>>> It doesn't work. I think changing int to size_t has no effect,
>>>> because my
>>>> notepad is not ppc64.
>>>>
>>>>
>>>> Guanghui Yu wrote:
>>>> Hi
>>>> I make a patch, could you try again?
>>>>
>>>> On 2/7/07, Bin Tian <[EMAIL PROTECTED]> wrote:
>>>>
>>>>
>>>> I saw improvements in the new version. But I can input only one
>>>> chinese
>>>> character.
>>>> fcitx will crash after the second character inputed. Backtrace is
>>>> attached
>>>> as fellow:
>>>>
>>>> Program received signal SIGSEGV, Segmentation fault.
>>>> 0x1001a1f8 in TableCreatePhraseCode (strHZ=0x7f8d7260 "要要") at
>>>> table.c:1974
>>>> 1974 strNewPhraseCode[i1] =
>>>> recTemp->strCode[table[iTableIMIndex].rule[i].rule[i1].iIndex
>>>> - 1];
>>>> (gdb) p recTemp
>>>> $1 = (RECORD *) 0x10b
>>>> (gdb) p *recTemp
>>>> Cannot access memory at address 0x10b
>>>> (gdb)
>>>>
>>>> Best Regards,
>>>> Bin Tian
>>>>
>>>>
>>>>
>>>> Guanghui Yu wrote:
>>>> Hi
>>>> I uploaded a new version to
>>>> http://people.debian.org/~ygh/temp/.
>>>> Could you help me try this version on your powerbook? You need build
>>>> it first. According to the upstream changelog, the input method table
>>>> issue has been fixed.
>>>>
>>>>
>>>> On 2/7/07, Bin Tian <[EMAIL PROTECTED]> wrote:
>>>>
>>>>
>>>>
>>>> I tried but it doesn't work.
>>>>
>>>> Backtrace of fcitx is attached as bellow. It may be helpful.
>>>>
>>>> Best Regards
>>>> Bin Tian.
>>>>
>>>> ~$ gdb -p 4821
>>>> GNU gdb 6.4.90-debian
>>>> Copyright (C) 2006 Free Software Foundation, Inc.
>>>> GDB is free software,
Bug#387558: subversion: svnadmin help broken
Package: subversion Version: 1.4.0-2 Severity: normal When I run svnadmin help in shell, it told me that svnadmin: Bad database version: compiled with 4.4.20, running against 4.3.29 -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.16-2-em64t-p4-smp Locale: LANG=zh_CN, LC_CTYPE=zh_CN (charmap=GB2312) Versions of packages subversion depends on: ii libapr0 2.0.55-4.1 the Apache Portable Runtime ii libc62.3.6.ds1-4 GNU C Library: Shared libraries ii libsvn0 1.4.0-2 Shared libraries used by Subversio subversion recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#388352: xen-hypervisor-3.0-unstable-1-amd64: veth0 is missing
Package: xen-hypervisor-3.0-unstable-1-amd64 Version: 3.0-unstable+hg11292-2 Severity: important My server is a dell 2950 server. Before the dom0 rebooting bug ocurred, xen was well even for hvm domU. By now i have tried xen-hypervisor-3.0-amd64 (3.0.2+hg9697-2) and xen-hypervisor-3.0-unstable-1-amd64 (3.0-unstable+hg11292-2), but both of them are unusable for me. for xen-hypervisor-3.0-amd64: The vnc server won't start and the hvm domU won't boot and blocks in 'b' state. The domU with modified kernel boots ok. When I run xm, there is a warning which says there is no xen utils with version 3.0.2-3-1 installed, and falling back to xen-default. for xen-hypervisor-3.0-unstable-1-amd64: If I choose the linux-image-2.6.16-2-xen-em64t-p4 as the dom0 kernel, the rebooting bug appears. If I choose the linux-image-2.6.17-2-amd64 as the dom0 kernel, I can enter the box. But when I run /etc/xen/scripts/network-bridge start, it told me that: Link veth0 is missing. This may be because you have reached the limit of the number of interfaces that the loopback driver supports. If the loopback driver is a module, you may raise this limit by passing it as a parameter (nloopbacks=); if the driver is compiled statically into the kernel, then you may set the parameter using loopback.nloopbacks= on the domain 0 kernel command line. The following is FYI dell-2950:~# uname -a Linux dell-2950 2.6.17-2-xen-amd64 #1 SMP Wed Sep 13 18:35:45 CEST 2006 x86_64 GNU/Linux dell-2950:~# xm list Name ID Mem(MiB) VCPUs State Time(s) Domain-0 0 1883 8 r-42.9 dell-2950:~# ifconfig -a | egrep "veth|vif" dell-2950:~# dpkg -l | grep 'xen-' ii linux-image-2.6-xen-em64t-p42.6.16+0.2 Linuxkernel 2.6 image on Intel em64t P4 mac ii linux-image-2.6.16-2-xen-em64t-p4 2.6.16-18 Linuxkernel 2.6.16 image on Intel em64t P4 ii linux-image-2.6.17-2-xen-amd64 2.6.17-9 Linux2.6.17 image on AMD64 ii linux-modules-2.6.16-2-xen-em64t-p4 2.6.16-18 Linuxkernel modules 2.6.16 image on Intel e ii linux-modules-2.6.17-2-xen-amd642.6.17-9 Linux2.6.17 modules on AMD64 ii xen-hypervisor-3.0-unstable-1-amd64 3.0-unstable+hg11292-2 The XenHypervisor on AMD64 ii xen-ioemu-3.0-unstable 3.0-unstable+hg11292-2 XENadministrative tools ii xen-linux-system-2.6.17-2-xen-amd64 2.6.17-9 XENsystem with Linux 2.6.17 image on AMD64 ii xen-utils-3.0-unstable-13.0-unstable+hg11292-2 XENadministrative tools ii xen-utils-common3.0+hg11292-2 XENadministrative tools - common files I think it's not a nlookbacks problem, because everything is the default installation. And before installing xen unstable, I purged the installed xen-hyphervisor-3.0-amd64 packages. Best regards, Bin Tian -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.17-2-xen-amd64 Locale: LANG=zh_CN, LC_CTYPE=zh_CN (charmap=GB2312) Versions of packages xen-hypervisor-3.0-unstable-1-amd64 depends on: ii xen-utils-3.0-uns 3.0-unstable+hg11292-2 XEN administrative tools xen-hypervisor-3.0-unstable-1-amd64 recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#388352: something to correct
Sorry for giving some wrong information. The version of xen-hypervisor-3.0-amd64 I installed is 3.0.2-3-hg9762-1, not 3.0.2-hg9697-2. Bin Tian -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#388352: still exists in xen-common 3.0+hg11624-1
The following is FYI. [EMAIL PROTECTED]:~$ uname -a Linux dell-2950 2.6.17-2-xen-amd64 #1 SMP Wed Sep 13 18:35:45 CEST 2006 x86_64 GNU/Linux [EMAIL PROTECTED]:~$ dpkg -l | grep xen- ii linux-image-2.6.17-2-xen-amd64 2.6.17-9 Linux 2.6.17 image on AMD64 ii linux-modules-2.6.17-2-xen-amd64 2.6.17-9 Linux 2.6.17 modules on AMD64 ii xen-hypervisor-3.0-unstable-1-amd64 3.0-unstable+hg11561-1 The Xen Hypervisor on AMD64 ii xen-ioemu-3.0-unstable 3.0-unstable+hg11561-1 XEN administrative tools ii xen-linux-system-2.6.17-2-xen-amd64 2.6.17-9 XEN system with Linux 2.6.17 image on AMD64 ii xen-utils-3.0-unstable-1 3.0-unstable+hg11561-1 XEN administrative tools ii xen-utils-common 3.0+hg11624-1 XEN administrative tools - common files [EMAIL PROTECTED]:~$ /sbin/ifconfig -a | egrep "veth|vif" [EMAIL PROTECTED]:~$ Best regards, Bin Tian Debian Bug Tracking System wrote: > This is an automatic notification regarding your Bug report > #388352: xen-hypervisor-3.0-unstable-1-amd64: veth0 is missing, > which was filed against the xen-hypervisor-3.0-unstable-1-amd64 package. > > It has been closed by Bastian Blank <[EMAIL PROTECTED]>. > > Their explanation is attached below. If this explanation is > unsatisfactory and you have not received a better one in a separate > message then please contact Bastian Blank <[EMAIL PROTECTED]> by replying > to this email. > > Debian bug tracking system administrator > (administrator, Debian Bugs database) > > > > > > Subject: > Bug#388352: fixed in xen-common 3.0+hg11624-1 > From: > Bastian Blank <[EMAIL PROTECTED]> > Date: > Wed, 27 Sep 2006 02:32:09 -0700 > To: > [EMAIL PROTECTED] > > To: > [EMAIL PROTECTED] > > > Source: xen-common > Source-Version: 3.0+hg11624-1 > > We believe that the bug you reported is fixed in the latest version of > xen-common, which is due to be installed in the Debian FTP archive: > > xen-common_3.0+hg11624-1.diff.gz > to pool/main/x/xen-common/xen-common_3.0+hg11624-1.diff.gz > xen-common_3.0+hg11624-1.dsc > to pool/main/x/xen-common/xen-common_3.0+hg11624-1.dsc > xen-common_3.0+hg11624.orig.tar.gz > to pool/main/x/xen-common/xen-common_3.0+hg11624.orig.tar.gz > xen-utils-common_3.0+hg11624-1_all.deb > to pool/main/x/xen-common/xen-utils-common_3.0+hg11624-1_all.deb > > > > A summary of the changes between this version and the previous one is > attached. > > Thank you for reporting the bug, which will now be closed. If you > have further comments please address them to [EMAIL PROTECTED], > and the maintainer will reopen the bug report if appropriate. > > Debian distribution maintenance software > pp. > Bastian Blank <[EMAIL PROTECTED]> (supplier of updated xen-common package) > > (This message was generated automatically at their request; if you > believe that there is a problem with it please contact the archive > administrators by mailing [EMAIL PROTECTED]) > > > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Format: 1.7 > Date: Wed, 27 Sep 2006 09:15:40 + > Source: xen-common > Binary: xen-utils-common > Architecture: source all > Version: 3.0+hg11624-1 > Distribution: unstable > Urgency: medium > Maintainer: Debian Xen Team <[EMAIL PROTECTED]> > Changed-By: Bastian Blank <[EMAIL PROTECTED]> > Description: > xen-utils-common - XEN administrative tools - common files > Closes: 388352 > Changes: > xen-common (3.0+hg11624-1) unstable; urgency=medium > . >* New upstream snapshot. >* Load netloop module if necessary. (closes: #388352) >* Set urgency to medium. > Files: > e475ea27df27211baf3ae9ce254d9bc2 792 admin optional > xen-common_3.0+hg11624-1.dsc > 23ba3ea1644517699e25939f64d3d6b4 77505 admin optional > xen-common_3.0+hg11624.orig.tar.gz > fdbdbfcea22292a1c92e0891ab9e029f 13966 admin optional > xen-common_3.0+hg11624-1.diff.gz > 5f5e6e3dd325f5ea0bc00446de386b61 43074 admin optional > xen-utils-common_3.0+hg11624-1_all.deb > > -BEGIN PGP SIGNATURE- > Version: GnuPG v1.4.5 (GNU/Linux) > > iEYEARECAAYFAkUaQd0ACgkQLkAIIn9ODhExJQCfcfBbg5lFJLrqZFbzrZUBv0Rr > UGwAn1mJ7j7biT2XaSjZKRJ875BxdWxl > =65t1 > -END PGP SIGNATURE- > > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#389836: xen-hypervisor-3.0-unstable-1-amd64: HVM domU won't start
Package: xen-hypervisor-3.0-unstable-1-amd64
Version: 3.0-unstable+hg11561-1
Severity: important
The HVM domU won't start. The following is the config (comments
stripped).
begin
import os, re
arch = os.uname()[4]
if re.search('64', arch):
arch_libdir = 'lib64'
else:
arch_libdir = 'lib'
kernel = "/usr/lib/xen-3.0-unstable-1/boot/hvmloader"
builder='hvm'
memory = 512
name = "PlanetLab"
vcpus=2
vif = [ 'type=ioemu, mac=00:16:3E:00:10:22, bridge=xenbr0' ]
disk = [ 'file:/small/xen-disks/debian/debian.img,ioemu:hda,w',
'file:/small/xen-disks/debian/swap.img,ioemu:hdb,w' ]
device_model = '/usr/' + arch_libdir + '/xen/bin/qemu-dm'
cdrom='/home/sparrow/PlanetLab-BootCD-3.3.iso'
fda='/home/sparrow/boot'
boot='d'
device_model = '/usr/' + arch_libdir + '/xen/bin/qemu-dm'
sdl=0
vnc=1
stdvga=0
serial='pty'
-end-
dell-2950:~# xm list
Name ID Mem(MiB) VCPUs State Time(s)
Domain-0 0 1024 8 r-46.0
PlanetLab 2 512 1 -- 0.0
dell-2950:~# netstat -na --inet | grep LISTEN
tcp0 0 127.0.0.1:2402 0.0.0.0:* LISTEN
tcp0 0 127.0.0.1:3306 0.0.0.0:* LISTEN
tcp0 0 0.0.0.0:21 0.0.0.0:* LISTEN
You can see that none of vncserver ports is in listening state.
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing')
Architecture: amd64 (x86_64)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.17-2-xen-amd64
Locale: LANG=zh_CN, LC_CTYPE=zh_CN (charmap=GB2312)
Versions of packages xen-hypervisor-3.0-unstable-1-amd64 depends on:
ii xen-utils-3.0-uns 3.0-unstable+hg11561-1 XEN administrative tools
xen-hypervisor-3.0-unstable-1-amd64 recommends no packages.
-- no debconf information
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#389836: xend.log
The
xend.log may be helpful.
Best regards,
Bin Tian
Debian Bug Tracking System wrote:
Thank you for the problem report you have sent regarding Debian.
This is an automatically generated reply, to let you know your message has
been received. It is being forwarded to the package maintainers and other
interested parties for their attention; they will reply in due course.
Your message has been sent to the package maintainer(s):
Debian Xen Team <[EMAIL PROTECTED]>
If you wish to submit further information on your problem, please send
it to [EMAIL PROTECTED] (and *not* to
[EMAIL PROTECTED]).
If you have filed this report in error and wish to close it, please
send mail to [EMAIL PROTECTED] with an explanation
why the bug report should be closed.
Please do not reply to the address at the top of this message,
unless you wish to report a problem with the Bug-tracking system.
Debian bug tracking system administrator
(administrator, Debian Bugs database)
[2006-09-28 08:56:26 xend 4431] INFO (__init__:1072) Xend Daemon started
[2006-09-28 08:56:26 xend 4431] INFO (__init__:1072) Xend changeset: Thu Sep 21
17:56:14 2006 +0100 .
[2006-09-28 08:56:26 xend.XendDomainInfo 4431] DEBUG (__init__:1072)
XendDomainInfo.recreate({'paused': 0, 'cpu_time': 19408338149L, 'ssidref': 0,
'handle': [0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0], 'shutdown_reason':
0, 'dying': 0, 'dom': 0, 'mem_kb': 1927320, 'maxmem_kb': 17179869180,
'max_vcpu_id': 7, 'crashed': 0, 'running': 1, 'shutdown': 0, 'online_vcpus': 8,
'blocked': 0})
[2006-09-28 08:56:26 xend.XendDomainInfo 4431] INFO (__init__:1072) Recreating
domain 0, UUID ----.
[2006-09-28 08:56:27 xend.XendDomainInfo 4431] WARNING (__init__:1072) No vm
path in store for existing domain 0
[2006-09-28 08:56:27 xend.XendDomainInfo 4431] DEBUG (__init__:1072) Storing VM
details: {'shadow_memory': '0', 'uuid': '----',
'on_reboot': 'restart', 'on_poweroff': 'destroy', 'name': 'Domain-0',
'xend/restart_count': '0', 'vcpus': '8', 'vcpu_avail': '255', 'memory': '1883',
'on_crash': 'restart', 'maxmem': '1883'}
[2006-09-28 08:56:27 xend.XendDomainInfo 4431] DEBUG (__init__:1072) Storing
domain details: {'cpu/1/availability': 'online', 'cpu/3/availability':
'online', 'name': 'Domain-0', 'console/limit': '1048576', 'cpu/2/availability':
'online', 'vm': '/vm/----', 'domid': '0',
'cpu/7/availability': 'online', 'cpu/0/availability': 'online',
'memory/target': '1928192', 'cpu/5/availability': 'online',
'cpu/6/availability': 'online', 'cpu/4/availability': 'online'}
[2006-09-28 08:56:27 xend 4431] DEBUG (__init__:1072) number of vcpus to use is 0
[2006-09-28 08:56:27 xend.XendDomainInfo 4431] DEBUG (__init__:1072)
XendDomainInfo.handleShutdownWatch
[2006-09-28 08:57:49 xend.XendDomainInfo 4431] DEBUG (__init__:1072) Setting
memory target of domain Domain-0 (0) to 1024 MiB.
[2006-09-28 08:58:18 xend.util.security 4922] INFO (__init__:1072) Resource
label file not found.
[2006-09-28 08:58:18 xend.util.security 4922] INFO (__init__:1072) Resource
label file not found.
[2006-09-28 08:58:18 xend.XendDomainInfo 4431] DEBUG (__init__:1072)
XendDomainInfo.create(['vm', ['name', 'PlanetLab'], ['memory', 512], ['vcpus',
2], ['image', ['hvm', ['kernel', '/usr/lib/xen-3.0.2-1/boot/hvmloader'],
['vcpus', 2], ['boot', 'd'], ['fda', '/home/sparrow/boot'], ['serial', 'pty'],
['vnc', 1], ['vncunused', 1], ['xauthority', '/root/.Xauthority'],
['device_model', '/usr/lib64/xen/bin/qemu-dm']]], ['device', ['vbd', ['uname',
'file:/small/xen-disks/debian/debian.img'], ['dev', 'ioemu:hda'], ['mode',
'w']]], ['device', ['vbd', ['uname', 'file:/small/xen-disks/debian/swap.img'],
['dev', 'ioemu:hdb'], ['mode', 'w']]], ['device', ['vif', ['bridge', 'xenbr0'],
['mac', '00:16:3E:00:10:22'], ['type', 'ioemu&#x
Bug#389836: [Pkg-xen-devel] Bug#389836: xen-hypervisor-3.0-unstable-1-amd64: HVM domU won't start
Thanks for your quick response. The package xen-utils-common is already 3.0+hg11624-1. And I make some correction in the dom config according to the example, but the domU still cann't start. I checked the log in /var/log/xen/. No error in xend.log, but qemu-dm.log tell me that: domid: 3 qemu: the number of cpus is 2 /etc/xen/qemu-ifup: could not launch network script Could not initialize device 'tap' And the file with name 'qemu-ifup' is not in /etc/xen/ but in /etc/xen/scripts dell-2950:/usr/lib/xen-ioemu-3.0-unstable/bin# strings qemu-dm | grep qemu-ifup /etc/xen/qemu-ifup I think that qemu-dm should be patched. Best regards, Bin Tian Bastian Blank wrote: On Thu, Sep 28, 2006 at 09:26:06AM +0800, Bin Tian wrote: The HVM domU won't start. The following is the config (comments stripped). Please check for the existance of /usr/lib64/xen/bin/qemu-dm which you defined as device_model. After that upgrade to xen-utils-common 3.0+hg11624-1 and check /usr/share/doc/xen-utils-common/examples/xmexample.hvm.gz. Bastian
Bug#389836: [Pkg-xen-devel] Bug#389836: xen-hypervisor-3.0-unstable-1-amd64: HVM domU won't start
I find that the qemu-ifup is very simple, so I make a copy of qemu-ifup in /etc/xen/ directory. This time, the domU started and I saw the boot screen of BIOS in vncviewer. But the BIOS said: CDROM boot failure code: 0002 Boot from CD-Rom failed. FATAL: Could not read from the boot disk. I'm sure that the iso file is well. And I tried to start another domU which runs windows, and got the same result: CDROM boot failure. regards, Bin Tian. Bin Tian wrote: Thanks for your quick response. The package xen-utils-common is already 3.0+hg11624-1. And I make some correction in the dom config according to the example, but the domU still cann't start. I checked the log in /var/log/xen/. No error in xend.log, but qemu-dm.log tell me that: domid: 3 qemu: the number of cpus is 2 /etc/xen/qemu-ifup: could not launch network script Could not initialize device 'tap' And the file with name 'qemu-ifup' is not in /etc/xen/ but in /etc/xen/scripts dell-2950:/usr/lib/xen-ioemu-3.0-unstable/bin# strings qemu-dm | grep qemu-ifup /etc/xen/qemu-ifup I think that qemu-dm should be patched. Best regards, Bin Tian Bastian Blank wrote: On Thu, Sep 28, 2006 at 09:26:06AM +0800, Bin Tian wrote: The HVM domU won't start. The following is the config (comments stripped). Please check for the existance of /usr/lib64/xen/bin/qemu-dm which you defined as device_model. After that upgrade to xen-utils-common 3.0+hg11624-1 and check /usr/share/doc/xen-utils-common/examples/xmexample.hvm.gz. Bastian
Bug#389836: [Pkg-xen-devel] Bug#389836: xen-hypervisor-3.0-unstable-1-amd64: HVM domU won't start
Bastian Blank wrote:
On Thu, Sep 28, 2006 at 02:51:48PM +0800, Bin Tian wrote:
I find that the qemu-ifup is very simple, so I make a copy of qemu-ifup
in /etc/xen/ directory. This time, the domU started and I saw the boot
screen of BIOS in vncviewer. But the BIOS said:
CDROM boot failure code: 0002
Boot from CD-Rom failed.
FATAL: Could not read from the boot disk.
Please provide your _fixed_ version of the config. According to the
template I shown you, the fda and cdrom parameters are not longer
available.
Bastian
# -*- mode: python; -*-
#
# Python configuration setup for 'xm create'.
# This script sets the parameters used when a domain is created using 'xm
create'.
# You use a separate script for each domain you want to create, or
# you can set the parameters for the domain on the xm command line.
#
#import os, re
#arch = os.uname()[4]
#if re.search('64', arch):
#arch_libdir = 'lib64'
#else:
#arch_libdir = 'lib'
#
# Kernel image file.
kernel = "hvmloader"
# The domain build function. HVM domain uses 'hvm'.
builder='hvm'
# Initial memory allocation (in megabytes) for the new domain.
memory = 512
# A name for your domain. All domains must have different names.
name = "PlanetLab"
#-
# the number of cpus guest platform has, default=1
vcpus=2
# enable/disable HVM guest PAE, default=0 (disabled)
#pae=0
# enable/disable HVM guest ACPI, default=0 (disabled)
#acpi=0
# enable/disable HVM guest APIC, default=0 (disabled)
#apic=0
# List of which CPUS this domain is allowed to use, default Xen picks
#cpus = "" # leave to Xen to pick
#cpus = "0"# all vcpus run on CPU0
#cpus = "0-3,5,^1" # run on cpus 0,2,3,5
# Optionally define mac and/or bridge for the network interfaces.
# Random MACs are assigned if not given.
#vif = [ 'type=ioemu, mac=00:16:3e:00:00:11, bridge=xenbr0' ]
# type=ioemu specify the NIC is an ioemu device not netfront
vif = [ 'type=ioemu, mac=00:16:3E:00:10:22, bridge=xenbr0' ]
#
# Define the disk devices you want the domain to have access to, and
# what you want them accessible as.
# Each disk entry is of the form phy:UNAME,DEV,MODE
# where UNAME is the device, DEV is the device name the domain will see,
# and MODE is r for read-only, w for read-write.
#disk = [ 'phy:hda1,hda1,r' ]
disk = [
'file:/small/xen-disks/debian/debian.img,ioemu:hda,w','file:/small/xen-disks/debian/swap.img,ioemu:hdb,w'
]
#
# Configure the behaviour when a domain exits. There are three 'reasons'
# for a domain to stop: poweroff, reboot, and crash. For each of these you
# may specify:
#
# "destroy",meaning that the domain is cleaned up as normal;
# "restart",meaning that a new domain is started in place of the old
# one;
# "preserve", meaning that no clean-up is done until the domain is
# manually destroyed (using xm destroy, for example); or
# "rename-restart", meaning that the old domain is not cleaned up, but is
# renamed and a new domain started in its place.
#
# The default is
#
# on_poweroff = 'destroy'
# on_reboot = 'restart'
# on_crash= 'restart'
#
# For backwards compatibility we also support the deprecated option restart
#
# restart = 'onreboot' means on_poweroff = 'destroy'
#on_reboot = 'restart'
#on_crash= 'destroy'
#
# restart = 'always' means on_poweroff = 'restart'
#on_reboot = 'restart'
#on_crash= 'restart'
#
# restart = 'never'means on_poweroff = 'destroy'
#on_reboot = 'destroy'
#on_crash= 'destroy'
#on_poweroff = 'destroy'
#on_reboot = 'restart'
#on_crash= 'restart'
#
# New stuff
device_model = 'qemu-dm'
#/usr/' + arch_libdir + '/xen/bin/qemu-dm'
#-
# Disk image for
cdrom='/home/sparrow/PlanetLab-BootCD-3.3.i
Bug#389836: [Pkg-xen-devel] Bug#389836: xen-hypervisor-3.0-unstable-1-amd64: HVM domU won't start
I found the right syntax of HVM cdrom/floppy configuration in xensource list. You can find it in the thread http://lists.xensource.com/archives/html/xen-devel/2006-08/msg00369.html It should be written as following. disk = [ 'file:/small/xen-disks/debian/debian.img,hda,w','file:/small/xen-disks/ debian/swap.img,hdb,w','file:/home/sparrow/PlanetLab-BootCD-3.3.iso,hdc:cdrom,r' ,'file:/home/sparrow/boot,fda:floppy,r' ] My HVM domU works again. Thanks a lot! ;) Best regards, BinTian Bastian Blank wrote: On Thu, Sep 28, 2006 at 02:51:48PM +0800, Bin Tian wrote: I find that the qemu-ifup is very simple, so I make a copy of qemu-ifup in /etc/xen/ directory. This time, the domU started and I saw the boot screen of BIOS in vncviewer. But the BIOS said: CDROM boot failure code: 0002 Boot from CD-Rom failed. FATAL: Could not read from the boot disk. Please provide your _fixed_ version of the config. According to the template I shown you, the fda and cdrom parameters are not longer available. Bastian
Bug#418012: libsnmp9: Too noisy when parsing counter64 on x64 system
Package: libsnmp9
Version: 5.2.3-7
Severity: normal
On AMD64 system, when parsing a counter64 variable, it will output
something like that:
truncating unsigned value to 32 bits (6)
truncating unsigned value to 32 bits (6)
truncating unsigned value to 32 bits (6)
truncating unsigned value to 32 bits (6)
truncating unsigned value to 32 bits (6)
truncating unsigned value to 32 bits (6)
On 32bit systems you couldn't see these messages. And these messages
should be suppressed.
A patch is available as following:
--- net-snmp-5.2.3/snmplib/asn1.c 2005-10-12 18:28:37.0 +0800
+++ net-snmp-5.2.3.new/snmplib/asn1.c 2007-04-06 14:48:00.0 +0800
@@ -211,22 +211,17 @@
# define CHECK_OVERFLOW_S(x,y)
# define CHECK_OVERFLOW_U(x,y)
#else
-# define CHECK_OVERFLOW_S(x,y) do { int trunc = 0; \
+# define CHECK_OVERFLOW_S(x,y) do {\
if (x > INT32_MAX) {\
-trunc = 1; \
x &= 0x;\
} else if (x < INT32_MIN) { \
-trunc = 1; \
x = 0 - (x & 0x); \
} \
-if (trunc) \
-snmp_log(LOG_ERR,"truncating signed value to 32 bits (%d)\n",y); \
} while(0)
# define CHECK_OVERFLOW_U(x,y) do {\
if (x > UINT32_MAX) { \
x &= 0x;\
-snmp_log(LOG_ERR,"truncating unsigned value to 32 bits (%d)\n",y);
\
} \
} while(0)
#endif
-- System Information:
Debian Release: 4.0
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-4-amd64
Locale: LANG=zh_CN, LC_CTYPE=zh_CN (charmap=GB2312)
Versions of packages libsnmp9 depends on:
ii libc6 2.3.6.ds1-13 GNU C Library: Shared libraries
ii libsensors3 1:2.10.1-3 library to read temperature/voltag
ii libsnmp-base5.2.3-7 NET SNMP (Simple Network Managemen
ii libssl0.9.8 0.9.8c-4 SSL shared libraries
ii libwrap07.6.dbs-13 Wietse Venema's TCP wrappers libra
libsnmp9 recommends no packages.
-- no debconf information
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#409999: fcitx crash when using wubi input method on powerpc platform
Package: fcitx Version: 1:3.4-1 Severity: grave Justification: renders package unusable Hi, I'm using debian on my iBook-G4. fcitx is alwasy crashing when using wubi input method even if I install a new debian box. The pinyin input method is ok. When I switch to wubi input method, any keyboard stike will casue fcitx crashed. The problem exists for more than 3 months, and I have to downgrade fcitx to sarge version. If you needs more information, please let me know. Best Regards Bin Tian -- System Information: Debian Release: 4.0 APT prefers testing APT policy: (500, 'testing') Architecture: powerpc (ppc) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-3-powerpc Locale: LANG=zh_CN, LC_CTYPE=zh_CN (charmap=GB2312) Versions of packages fcitx depends on: ii libc6 2.3.6.ds1-10 GNU C Library: Shared libraries ii libfontconfig1 2.4.2-1 generic font configuration library ii libx11-62:1.0.3-5X11 client-side library ii libxft2 2.1.8.2-8FreeType-based font drawing librar ii libxpm4 1:3.5.5-2X11 pixmap library Versions of packages fcitx recommends: pn im-switch (no description available) pn ttf-arphic-gbsn00lp | ttf-arp (no description available) -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#409999: fcitx crash when using wubi input method on powerpc platform
I checked the bugs list of fcitx. The removal of ~/.fcitx directory which mentioned in bug #392740 doesn't work. Best regards Bin Tian Bin Tian wrote: Package: fcitx Version: 1:3.4-1 Severity: grave Justification: renders package unusable Hi, I'm using debian on my iBook-G4. fcitx is alwasy crashing when using wubi input method even if I install a new debian box. The pinyin input method is ok. When I switch to wubi input method, any keyboard stike will casue fcitx crashed. The problem exists for more than 3 months, and I have to downgrade fcitx to sarge version. If you needs more information, please let me know. Best Regards Bin Tian -- System Information: Debian Release: 4.0 APT prefers testing APT policy: (500, 'testing') Architecture: powerpc (ppc) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-3-powerpc Locale: LANG=zh_CN, LC_CTYPE=zh_CN (charmap=GB2312) Versions of packages fcitx depends on: ii libc6 2.3.6.ds1-10 GNU C Library: Shared libraries ii libfontconfig1 2.4.2-1 generic font configuration library ii libx11-62:1.0.3-5X11 client-side library ii libxft2 2.1.8.2-8FreeType-based font drawing librar ii libxpm4 1:3.5.5-2X11 pixmap library Versions of packages fcitx recommends: pn im-switch (no description available) pn ttf-arphic-gbsn00lp | ttf-arp (no description available) -- no debconf information
Bug#409999: fcitx crash when using wubi input method on powerpc platform
fcitx on debian amd64 is ok. Bin Tian wrote: I checked the bugs list of fcitx. The removal of ~/.fcitx directory which mentioned in bug #392740 doesn't work. Best regards Bin Tian Bin Tian wrote: Package: fcitx Version: 1:3.4-1 Severity: grave Justification: renders package unusable Hi, I'm using debian on my iBook-G4. fcitx is alwasy crashing when using wubi input method even if I install a new debian box. The pinyin input method is ok. When I switch to wubi input method, any keyboard stike will casue fcitx crashed. The problem exists for more than 3 months, and I have to downgrade fcitx to sarge version. If you needs more information, please let me know. Best Regards Bin Tian -- System Information: Debian Release: 4.0 APT prefers testing APT policy: (500, 'testing') Architecture: powerpc (ppc) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-3-powerpc Locale: LANG=zh_CN, LC_CTYPE=zh_CN (charmap=GB2312) Versions of packages fcitx depends on: ii libc6 2.3.6.ds1-10 GNU C Library: Shared libraries ii libfontconfig1 2.4.2-1 generic font configuration library ii libx11-62:1.0.3-5X11 client-side library ii libxft2 2.1.8.2-8FreeType-based font drawing librar ii libxpm4 1:3.5.5-2X11 pixmap library Versions of packages fcitx recommends: pn im-switch (no description available) pn ttf-arphic-gbsn00lp | ttf-arp (no description available) -- no debconf information
Bug#409999: fcitx crash when using wubi input method on powerpc platform
I tried but it doesn't work. Backtrace of fcitx is attached as bellow. It may be helpful. Best Regards Bin Tian. ~$ gdb -p 4821 GNU gdb 6.4.90-debian Copyright (C) 2006 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "powerpc-linux-gnu". Attaching to process 4821 Reading symbols from /usr/bin/fcitx...(no debugging symbols found)...done. Using host libthread_db library "/lib/tls/libthread_db.so.1". Reading symbols from /usr/lib/libXpm.so.4...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libXpm.so.4 Reading symbols from /usr/lib/libXft.so.2...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libXft.so.2 Reading symbols from /usr/lib/libfontconfig.so.1... (no debugging symbols found)...done. Loaded symbols for /usr/lib/libfontconfig.so.1 Reading symbols from /usr/lib/libX11.so.6...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libX11.so.6 Reading symbols from /lib/tls/libc.so.6...(no debugging symbols found)...done. Loaded symbols for /lib/tls/libc.so.6 Reading symbols from /usr/lib/libfreetype.so.6... (no debugging symbols found)...done. Loaded symbols for /usr/lib/libfreetype.so.6 Reading symbols from /usr/lib/libz.so.1...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libz.so.1 Reading symbols from /usr/lib/libXrender.so.1...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libXrender.so.1 Reading symbols from /usr/lib/libexpat.so.1... (no debugging symbols found)...done. Loaded symbols for /usr/lib/libexpat.so.1 Reading symbols from /usr/lib/libXau.so.6...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libXau.so.6 Reading symbols from /usr/lib/libXdmcp.so.6...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libXdmcp.so.6 Reading symbols from /lib/tls/libdl.so.2... (no debugging symbols found)...done. Loaded symbols for /lib/tls/libdl.so.2 Reading symbols from /lib/ld.so.1...(no debugging symbols found)...done. Loaded symbols for /lib/ld.so.1 Reading symbols from /usr/lib/gconv/GB18030.so...(no debugging symbols found)...done. Loaded symbols for /usr/lib/gconv/GB18030.so Reading symbols from /usr/lib/libXcursor.so.1... (no debugging symbols found)...done. Loaded symbols for /usr/lib/libXcursor.so.1 Reading symbols from /usr/lib/libXfixes.so.3...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libXfixes.so.3 (no debugging symbols found) 0x0fd83318 in poll () from /lib/tls/libc.so.6 (gdb) c Continuing. Program received signal SIGSEGV, Segmentation fault. 0x1001cf10 in ?? () (gdb) bt #0 0x1001cf10 in ?? () #1 0x1001cf0c in ?? () #2 0x1001d814 in ?? () #3 0x10005160 in ?? () #4 0x1001fdec in ?? () #5 0x1002bb08 in ?? () #6 0x1002c71c in ?? () #7 0x10025a80 in ?? () #8 0x0fe46858 in XFilterEvent () from /usr/lib/libX11.so.6 #9 0x10007a98 in ?? () #10 0x0fcca994 in __libc_init_first () from /lib/tls/libc.so.6 #11 0x0fcca994 in __libc_init_first () from /lib/tls/libc.so.6 #12 0x0fcca994 in __libc_init_first () from /lib/tls/libc.so.6 Previous frame inner to this frame (corrupt stack?) (gdb) Guanghui Yu wrote: Hi Did you use the wbx.mb? Could you try regenerate the wbx.mb on powerbook using "mb2txt" and "txt2mb" commands? On 2/7/07, Bin Tian <[EMAIL PROTECTED]> wrote: fcitx on debian amd64 is ok. Bin Tian wrote: I checked the bugs list of fcitx. The removal of ~/.fcitx directory which mentioned in bug #392740 doesn't work. Best regards Bin Tian Bin Tian wrote: Package: fcitx Version: 1:3.4-1 Severity: grave Justification: renders package unusable Hi, I'm using debian on my iBook-G4. fcitx is alwasy crashing when using wubi input method even if I install a new debian box. The pinyin input method is ok. When I switch to wubi input method, any keyboard stike will casue fcitx crashed. The problem exists for more than 3 months, and I have to downgrade fcitx to sarge version. If you needs more information, please let me know. Best Regards Bin Tian -- System Information: Debian Release: 4.0 APT prefers testing APT policy: (500, 'testing') Architecture: powerpc (ppc) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-3-powerpc Locale: LANG=zh_CN, LC_CTYPE=zh_CN (charmap=GB2312) Versions of packages fcitx depends on: ii libc6 2.3.6.ds1-10 GNU C Library: Shared libraries ii libfontconfig1 2.4.2-1 generic font configuration library ii libx11-6 2:1.0.3-5 X11 client-side library ii libxft2 2.1.8.2-8 FreeType-based font drawing librar ii libxpm4 1:3.5.5-2 X11 pixmap library Versions of packages fcitx
