qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: J M Cerqueira Esteves <jmce@artenumerica.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] -kernel-kqemu issue? hwclock w/ libc6-i686: segmentation fault on reboot
Date: Sun, 20 Aug 2006 00:25:20 +0100	[thread overview]
Message-ID: <44E79DE0.3080203@artenumerica.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 398 bytes --]

I submited the attached report to the Debian bug tracking system,
but just now I noticed that that segfault of hwclock with libc6-i686 (in
a guest Debian testing system) only occurs if the virtual machine
is started with -kernel-kqemu.  Could this be related to some kqemu bug?

Best regards
                              J Esteves

-- 
+351 939838775   Skype:jmcerqueira   http://del.icio.us/jmce

[-- Attachment #2: util-linux: hwclock w/ libc6-i686: segmentation fault on reboot --]
[-- Type: message/rfc822, Size: 3165 bytes --]

From: J M Cerqueira Esteves <jmce@artenumerica.com>
To: Debian Bug Tracking System <submit@bugs.debian.org>
Subject: util-linux: hwclock w/ libc6-i686: segmentation fault on reboot
Date: Sat, 19 Aug 2006 23:40:37 +0100
Message-ID: <20060819224037.3583.91229.reportbug@arneb.ur.artenumerica.net>

Package: util-linux
Version: 2.12r-10
Severity: normal


Additional system information:  This occurred inside a QEMU virtual machine
running Debian testing (etch) i386, under the following

 QEMU HOST SETUP:
   host CPU: AMD Athlon 64 3500+
   host operating system: Ubuntu 6.06 LTS,
        kernel: Ubuntu 2.6.15-26-amd64-k8
   kqemu: 1.3.0pre9
   QEMU: 0.8.2, configured with -cc=gcc-3.4 --enable-alsa
         invoked with 
            qemu-system-x86_64 ... -kernel-kqemu ...

In the Debian etch guest system, When libc6-i686 is installed 
hwclock segfaults on reboots:
  /etc/rc6.d/K25hwclock.sh: line 58:  3584 Segmentation fault   /sbin/hwclock --systohc $GMT $HWCLOCKPARS $BADYEAR 

This does not occur when libc6-i686 is not installed.

-- System Information:
Debian Release: testing/unstable
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.16-2-k7
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)

Versions of packages util-linux depends on:
ii  libc6                         2.3.6-15   GNU C Library: Shared libraries
ii  libncurses5                   5.5-2      Shared libraries for terminal hand
ii  libslang2                     2.0.6-2    The S-Lang programming library - r
ii  libuuid1                      1.39-1     universally unique id library
ii  lsb-base                      3.1-10     Linux Standard Base 3.1 init scrip
ii  zlib1g                        1:1.2.3-13 compression library - runtime

util-linux recommends no packages.

-- no debconf information


             reply	other threads:[~2006-08-19 23:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-19 23:25 J M Cerqueira Esteves [this message]
2006-08-20 14:01 ` [Qemu-devel] -kernel-kqemu issue? hwclock w/ libc6-i686: segmentation fault on reboot Paul Brook
2006-08-20 15:33   ` [Qemu-devel] Asking about testing new added device Tieu Ma Dau

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=44E79DE0.3080203@artenumerica.com \
    --to=jmce@artenumerica.com \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).