Back to Home / #uml / 2007 / 07 / Prev Day | Next Day
#uml IRC Logs for 2007-07-31

---Logopened Tue Jul 31 00:00:11 2007
00:49|-|balbir [~balbir@122.167.2.53] has joined #uml
02:06|-|Netsplit synthon.oftc.net <-> cation.oftc.net quits: kybe_, Urgleflogue, krau, baroni, peterz, SNy, apic, weasel, Hunger, balbir, (+1 more, use /NETSPLIT to show all of them)
02:07|-|Netsplit over, joins: Hunger, Urgleflogue, balbir, krau, baroni, alb, kybe_, weasel, SNy, peterz (+1 more)
04:29|-|krau [~cktakahas@200.184.118.132] has quit [Ping timeout: 480 seconds]
06:01|-|tyler [~tyler@adsl196-1-187-206-196.adsl196-6.iam.net.ma] has joined #uml
06:23|-|tyler_ [~tyler@adsl196-1-187-206-196.adsl196-6.iam.net.ma] has joined #uml
06:24|-|tyler [~tyler@adsl196-1-187-206-196.adsl196-6.iam.net.ma] has quit [Ping timeout: 480 seconds]
06:44|-|tyler_ [~tyler@adsl196-1-187-206-196.adsl196-6.iam.net.ma] has quit [Ping timeout: 480 seconds]
06:44|-|tyler [~tyler@adsl196-1-187-206-196.adsl196-6.iam.net.ma] has joined #uml
06:45|-|dgraves [~agraves@inet-nc01-o.oracle.com] has quit [Ping timeout: 480 seconds]
06:53|-|krau [~cktakahas@200.184.118.132] has joined #uml
07:38|-|krau [~cktakahas@200.184.118.132] has quit [Quit: Varei!!!]
07:51|-|tyler [~tyler@adsl196-1-187-206-196.adsl196-6.iam.net.ma] has quit [Remote host closed the connection]
07:57|-|krau [~cktakahas@200.184.118.132] has joined #uml
07:57|-|kokoko1 [~Slacker@203.148.65.8] has joined #uml
08:20|-|baroni [~baroni@tera.lsi.usp.br] has quit [Remote host closed the connection]
08:27|-|baroni [~baroni@tera.lsi.usp.br] has joined #uml
09:19|-|tyler [~tyler@adsl196-1-187-206-196.adsl196-6.iam.net.ma] has joined #uml
09:35|-|dang [~dang@209.45.199.2] has joined #uml
09:38|-|tyler [~tyler@adsl196-1-187-206-196.adsl196-6.iam.net.ma] has quit [Remote host closed the connection]
09:42|-|tyler [~tyler@adsl196-1-187-206-196.adsl196-6.iam.net.ma] has joined #uml
10:27|-|jdike [~jdike@pool-96-233-58-249.bstnma.fios.verizon.net] has joined #uml
10:27<jdike>Hi guys
10:28<peterz>hey Jeff
10:30|-|ram [~ram@pool-71-245-108-202.ptldor.fios.verizon.net] has joined #uml
11:23|-|the_hydra [~the_hydra@125.164.99.90] has joined #uml
11:49|-|tyler [~tyler@adsl196-1-187-206-196.adsl196-6.iam.net.ma] has quit [Ping timeout: 480 seconds]
11:59|-|the_hydra [~the_hydra@125.164.99.90] has quit [Ping timeout: 480 seconds]
12:03|-|tyler [~tyler@adsl196-1-187-206-196.adsl196-6.iam.net.ma] has joined #uml
12:23|-|tyler [~tyler@adsl196-1-187-206-196.adsl196-6.iam.net.ma] has quit [Ping timeout: 480 seconds]
12:38|-|tyler [~tyler@adsl196-1-187-206-196.adsl196-6.iam.net.ma] has joined #uml
12:46|-|krau [~cktakahas@200.184.118.132] has quit [Quit: Varei!!!]
12:53|-|krau [~cktakahas@200.184.118.132] has joined #uml
13:15|-|mgross [~mgross@jffwpr01.jf.intel.com] has joined #uml
13:17|-|mgross [~mgross@jffwpr01.jf.intel.com] has quit []
13:17|-|mgross [~mgross@jffwpr01.jf.intel.com] has joined #uml
13:24|-|ram [~ram@pool-71-245-108-202.ptldor.fios.verizon.net] has quit [Ping timeout: 480 seconds]
13:31|-|horst [~horst@a89-182-24-223.net-htp.de] has joined #uml
13:36|-|ram [~ram@bi01p1.co.us.ibm.com] has joined #uml
13:50|-|tyler [~tyler@adsl196-1-187-206-196.adsl196-6.iam.net.ma] has quit [Remote host closed the connection]
15:09|-|baroni [~baroni@tera.lsi.usp.br] has quit [Remote host closed the connection]
15:17<kokoko1>hi guys
15:18<kokoko1>guru around?
15:18<kokoko1>jdike, its fine to use kernel 2.6.21.4 for UML even tho its bit old?
15:19<kokoko1>i am going to update the kernel on all UML which currently running 2.6.17.11 to 2.6.21.4 which has been tested on a uml which was crashing randomly before and not its been up from last 33 days
15:22<kokoko1>Two Hosts (not uml) are running 2.6.20-skas3-v9-pre9 and one is running 2.6.17.9-skas3-v9-pre9
15:23<kokoko1>I thinks it will not be a problem to run newer kernel (2.6.21.4) for UMLs?
15:24<kokoko1>s/not its been/now its been
15:28<kokoko1>Or you want me to go for 2.6.22 for host and uml ? :-s
15:29<kokoko1>I duno how are the skas3 things with 2.6.22 at host side.
15:34<jdike>2.6.21 should be good
15:35<kokoko1>right, what you suggest for host ? may i intact the host kernel or also do the 2.6.21 ?
15:36<kokoko1>specially 2.6.17.9-skas3-v9-pre9 is kinda scary
15:38<jdike>the host doesn't matter so much
15:38<jdike>whatever you're comfortable with
15:38<jdike>except that if it's Fedora, make sure that PTRACE_SYSEMU is working
15:40<kokoko1>jdike, yes all of them hosts + umls are fedora but atm we do not got any problem
15:40<jdike>OK
15:40<jdike>UML will complain if SYSEMU isn't working, and not use it
15:40<jdike>it'll still work, but be somewhat slower
15:43<kokoko1>Right i do not want my uml to run slower, so how to make sure that SYSEMU is working its uml or host side?
15:43<jdike>host side
15:44<jdike>UML will say this
15:44<jdike>Checking syscall emulation patch for ptrace...OK
15:44<jdike>Checking advanced syscall emulation patch for ptrace...OK
15:44<jdike>if everything's OK
15:45<kokoko1>ok anything later in uml logs?
15:45<jdike>if SYSEMU is broken, it will be something like
15:45<jdike>"check_sysemu got system call number %d, "
15:45<jdike> "expected %d..."
15:45<jdike>or
15:46<jdike>"check_sysemu : failed to modify system call "
15:46<jdike> "return"
15:47<kokoko1>you mean during uml startup right?
15:48<kokoko1>our 'umlrun' script do not show any thing but just counts from 1... to 20 or 30 when we launch uml, wonders how i'll confirm this
15:49<kokoko1>i thinks i better first launch it using ./linux away?
15:49<jdike>yup
15:49<kokoko1>okay thanks guru :)
15:49<kokoko1>i'll let you know if uml complains for SYSEMU or not
15:50<kokoko1>its kinda late for me will do it later.
15:57<kokoko1>wonders when RH + fedora dumping xen :)
15:57<kokoko1>xen kinda scary tho
15:57<kokoko1>wondering*
16:00<kokoko1>gtg
16:00[~]kokoko1 disappears
16:26|-|Netsplit resistance.oftc.net <-> cation.oftc.net quits: ram, Hunger, balbir, alb
16:26|-|Netsplit over, joins: Hunger, Urgleflogue, ram, horst, balbir, alb, kybe_, weasel, SNy, peterz (+1 more)
16:31|-|mgross [~mgross@jffwpr01.jf.intel.com] has quit [Quit: Leaving]
16:32|-|krau [~cktakahas@200.184.118.132] has quit [Ping timeout: 480 seconds]
17:00|-|dang [~dang@209.45.199.2] has quit [Quit: Leaving.]
17:09|-|jjkola [~jjkola@dsl-olubrasgw1-fe56fb00-241.dhcp.inet.fi] has joined #uml
17:10<jjkola>hmm, I'm getting segmentation faults when running guest 2.6.22 from host 2.6.23-rc1-git9-skas3
17:11<jjkola>it's failing at switch_mm_skas()
17:14<jdike>stack trace?
17:14<jdike>(BTW, never got gdb to show me the top of the stack of your last core)
17:14<jdike>it ran out of memory
17:16<jjkola>oh
17:16<jjkola>stack trace: http://rafb.net/p/EXDJ5d52.html
17:16<jdike>in gdb
17:17<jjkola>yes
17:17<jdike>printf "%s", log_buf
17:17<jjkola>I have to write that command?
17:17<jdike>yup
17:17<jjkola>ok
17:18<jdike>just want to see the panic message
17:18<jjkola>errno = 22
17:19<jjkola>or do you want the whole message?
17:19<jdike>that's fine
17:19<jdike>EINVAL
17:20<jjkola>meaning?
17:20<jdike>not sure
17:20<jdike>reproducable?
17:20<jjkola>yep, every time I try to boot umls I get this
17:20<jdike>since when?
17:21<jjkola>when using host kernel 2.6.23-rc1-git9-skas3
17:22<jdike>given that, I'd guess something broke the skas patch
17:22<jjkola>I applied that 2.6.22 unofficial patch with hand applied parts
17:24<jjkola>wait a minute, did I apply all the rejected parts...
17:24<jjkola>hmm, I'll have to check that
17:26<jjkola>ok, I had applied them
17:27<jjkola>so it wasn't that
17:33|-|horst [~horst@a89-182-24-223.net-htp.de] has quit [Remote host closed the connection]
17:48<jjkola>I'm checking if 2.6.23-rc1-git9 host has same problem, if not then we can be sure it's skas related
18:00|-|dang [~dang@nemesis.fprintf.net] has joined #uml
18:19|-|mgross [~mgross@jffwpr03.jf.intel.com] has joined #uml
18:19|-|mgross [~mgross@jffwpr03.jf.intel.com] has quit []
18:40|-|jjkola1 [~jjkola@dsl-olubrasgw1-fe56fb00-241.dhcp.inet.fi] has joined #uml
18:43|-|jjkola changed nick to Guest522
18:43|-|jjkola1 changed nick to jjkola
18:45|-|Guest522 [~jjkola@dsl-olubrasgw1-fe56fb00-241.dhcp.inet.fi] has quit [Ping timeout: 480 seconds]
18:45<jjkola>without skas patch the uml did start
18:47<jjkola>so it's either guest or host skas code which is at fault, I think so
19:31|-|jdike [~jdike@pool-96-233-58-249.bstnma.fios.verizon.net] has quit [Quit: Leaving]
20:14|-|dang [~dang@nemesis.fprintf.net] has quit [Quit: Leaving.]
20:38|-|ram [~ram@bi01p1.co.us.ibm.com] has quit [Ping timeout: 480 seconds]
20:43|-|kokoko1 [~Slacker@203.148.65.8] has quit [Ping timeout: 480 seconds]
20:59|-|jjkola [~jjkola@dsl-olubrasgw1-fe56fb00-241.dhcp.inet.fi] has left #uml [So Long, and Thanks for All the Fish!]
21:14|-|baroni [~baroni@bd21254a.virtua.com.br] has joined #uml
22:59|-|VS_ChanLog [~stats@ns.theshore.net] has left #uml [Rotating Logs]
22:59|-|VS_ChanLog [~stats@ns.theshore.net] has joined #uml
---Logclosed Wed Aug 01 00:00:42 2007