linux-um archives
 help / color / mirror / Atom feed
From: Michael Richardson <mcr@sandelman.ca>
To: user-mode-linux-devel@lists.sourceforge.net
Subject: [uml-devel] problems with ifup-a on etch compiled kernels
Date: Sun, 05 Nov 2006 16:29:39 -0800	[thread overview]
Message-ID: <eilvlj$b5r$1@sea.gmane.org> (raw)

I don't know whether to blame a recent update to debian testing from stable --- likely it would be a glibc issue, but...
I did run into the _syscall0() problem after that, and I found that I could get around it by appropriately #define 
_KERNEL prior to #include <linux/unistd.h>. What I don't get about the remark of Paolo is that _syscall0() is a userland 
thing, not a kernel thing.

I.e. any user program should be able to use _syscall() to get an open coded call to the kernel.

Anyway, my problem: 2.6.15, 2.6.17.13 (both patched as above), and 2.6.19-rc3 all fail during ifup -a:

+ echo -n 'Configuring network interfaces: '
Configuring network interfaces: + ifup -a
BUG: soft lockup detected on CPU#0!
083bf9f0:  [<080632a2>] dump_stack+0x22/0x30
083bfa08:  [<080a25c4>] softlockup_tick+0x84/0xa0
083bfa20:  [<0808ca32>] run_local_timers+0x12/0x20
083bfa28:  [<0808c796>] update_process_times+0x36/0x90
083bfa48:  [<080636fc>] timer_handler+0x3c/0x70
083bfa64:  [<080798f9>] sig_handler_common_skas+0xa9/0x100
083bfa88:  [<08075413>] real_alarm_handler+0x23/0x60
083bfaa0:  [<080754a2>] alarm_handler+0x52/0x70
083bfabc:  [<08077eda>] hard_handler+0x1a/0x20
083bfacc:  [<ffffe420>] _etext+0xf7df5404/0x0
083bfe14:  [<081a3431>] inet_ioctl+0x61/0xa0
083bfe2c:  [<081525a4>] sock_ioctl+0x144/0x2b0
083bfe60:  [<080d022f>] do_ioctl+0x5f/0x70
083bfe80:  [<080d04e2>] vfs_ioctl+0x62/0x2d0
083bfebc:  [<080d0791>] sys_ioctl+0x41/0x70
083bfee4:  [<08065a83>] handle_syscall+0xd3/0xe0
083bff54:  [<0807897a>] handle_trap+0x2a/0x130
083bff7c:  [<08079074>] userspace+0x1c4/0x220
083bffd4:  [<0806569e>] fork_handler+0x9e/0xb0
083bfffc:  [<00000000>] _sinittext+0xf7fb7000/0x20

If I boot with "linux emergency" login to the single user shell and run "ifup -a", everything is fine.

This is on my laptop running 2.6.17.4 as the host kernel, not under XenU as I previously had
been posting about.

(I'm in an airport lounge at Chicago)


-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel

             reply	other threads:[~2006-11-06  0:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-06  0:29 Michael Richardson [this message]
2006-11-06 21:44 ` [uml-devel] problems with ifup-a on etch compiled kernels Michael Richardson
2006-11-06 22:01   ` Michael Richardson
2006-11-07 19:32     ` Michael Richardson
2006-11-08 18:10   ` Jeff Dike
2006-11-08 23:04     ` Michael Richardson
2006-11-13 21:21     ` Michael Richardson

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='eilvlj$b5r$1@sea.gmane.org' \
    --to=mcr@sandelman.ca \
    --cc=user-mode-linux-devel@lists.sourceforge.net \
    /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