From: Michael Richardson <mcr@sandelman.ottawa.on.ca>
To: Jeff Dike <jdike@addtoit.com>
Cc: user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] problems with ifup-a on etch compiled kernels
Date: Wed, 08 Nov 2006 15:04:00 -0800 [thread overview]
Message-ID: <10570.1163027040@sandelman.ottawa.on.ca> (raw)
In-Reply-To: Message from Jeff Dike <jdike@addtoit.com> of "Wed, 08 Nov 2006 13:10:25 EST." <20061108181025.GC5698@ccure.user-mode-linux.org>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
>>>>> "Jeff" == Jeff Dike <jdike@addtoit.com> writes:
Jeff> On Mon, Nov 06, 2006 at 01:44:56PM -0800, Michael Richardson
Jeff> wrote:
>> I've tracked this down to a number of places. It looks like the
>> ifa->ifa_dev is not valid when the notification chain is called:
Jeff> Can you tell me how to reproduce this, or send me a filesystem
Jeff> on which this happens?
Unfortunately, I'm unable to determine what the key element is.
It fails on my laptop, running identical user-mode-linux code and file
system that works on two devel machine I have. My laptop is is
etch+2.6.17.4, (but I went back a 2.6.12.3 kernel I had, and it still
failed). It works on a debian sarge+2.4.30 kernel, and a debian
sarge+2.6.18.16 system.
I copied my / (not /usr) to the 2.6.18.16, setup a chroot, etc. and
ran the binaries compiled on my laptop against the file system there. No
fault.
My laptop while at IETF has a public IP, so if you want I could make
you an account...
- --
] Bear: "Me, I'm just the shape of a bear." | firewalls [
] Michael Richardson, Xelerance Corporation, Ottawa, ON |net architect[
] mcr@xelerance.com http://www.sandelman.ottawa.on.ca/mcr/ |device driver[
] panic("Just another Debian GNU/Linux using, kernel hacking, security guy"); [
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
Comment: Finger me for keys
iQEVAwUBRVJiXYCLcPvd0N1lAQI2pAgAlKjw0034ueE0cP2h4BfXZuJoMDrIplh5
OPUxX/KR7rFSTkSwxgHLYdxJrb/7WanRf72kfU+8FZVZRxs/GDMwYClHnCPW1ufs
IlrarkhKjTZVotE4Xt3CJGGqcjN5eyTDsWzikKDg0Gpkdn8icvZ/qVBFXsbygsMC
cEuPhkytPuPzhhxd4nfs0gW7MYtgkapPajJ/Vi0ADo3umMn4q1mpK3+zhnAm5ilB
frEfZVsojSsL9rmxllf3R05YfOCuDdN4CSAPBsijOZ2wtiR03dGY6aQ+dX1MGMQL
z1SniQSh39cKae/YVHw/pK9amt4iUe1JjrxCB+1wt1XupHzrxODEtA==
=iKlS
-----END PGP SIGNATURE-----
-------------------------------------------------------------------------
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
next prev parent reply other threads:[~2006-11-08 23:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-06 0:29 [uml-devel] problems with ifup-a on etch compiled kernels Michael Richardson
2006-11-06 21:44 ` 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 [this message]
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=10570.1163027040@sandelman.ottawa.on.ca \
--to=mcr@sandelman.ottawa.on.ca \
--cc=jdike@addtoit.com \
--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