Back to Home / #uml / 2007 / 08 / Prev Day | Next Day
#uml IRC Logs for 2007-08-22

---Logopened Wed Aug 22 00:00:11 2007
00:45|-|balbir [~balbir@122.167.95.137] has quit [Ping timeout: 480 seconds]
00:46|-|darious12 [~darius@87.203.158.152] has joined #uml
02:12|-|rasix [~jeruk@167.205.33.253] has joined #uml
02:15|-|balbir [~balbir@59.145.136.1] has joined #uml
02:37|-|rasix [~jeruk@167.205.33.253] has left #uml [Leaving]
02:43|-|ram [~ram@pool-71-245-102-10.ptldor.fios.verizon.net] has quit [Ping timeout: 480 seconds]
02:53|-|ram [~ram@pool-71-117-247-229.ptldor.fios.verizon.net] has joined #uml
02:59|-|darious12_ [~darius@85.72.119.249] has joined #uml
03:03|-|aroscha [~aroscha@212.154.128.222] has joined #uml
03:03|-|darious12 [~darius@87.203.158.152] has quit [Ping timeout: 480 seconds]
03:17|-|aroscha [~aroscha@212.154.128.222] has quit [Ping timeout: 480 seconds]
03:43|-|horst [~horst@a89-182-149-186.net-htp.de] has joined #uml
04:06|-|darious12__ [~darius@athedsl-303154.home.otenet.gr] has joined #uml
04:10|-|darious12_ [~darius@85.72.119.249] has quit [Ping timeout: 480 seconds]
04:48|-|aroscha [~aroscha@nat.2day.kz] has joined #uml
05:00|-|aroscha [~aroscha@nat.2day.kz] has quit [Read error: Connection reset by peer]
05:01|-|_horst [~horst@a89-182-29-145.net-htp.de] has joined #uml
05:03|-|aroscha [~aroscha@nat.2day.kz] has joined #uml
05:06|-|horst [~horst@a89-182-149-186.net-htp.de] has quit [Ping timeout: 480 seconds]
05:13|-|_horst [~horst@a89-182-29-145.net-htp.de] has quit [Remote host closed the connection]
05:23|-|aroscha_ [~aroscha@nat.2day.kz] has joined #uml
05:23|-|aroscha [~aroscha@nat.2day.kz] has quit [Read error: Connection reset by peer]
05:28|-|aroscha [~aroscha@nat.2day.kz] has joined #uml
05:28|-|aroscha_ [~aroscha@nat.2day.kz] has quit [Read error: Connection reset by peer]
05:39|-|tyler [~tyler@adsl196-162-187-217-196.adsl196-14.iam.net.ma] has joined #uml
05:48|-|aroscha_ [~aroscha@nat.2day.kz] has joined #uml
05:48|-|aroscha [~aroscha@nat.2day.kz] has quit [Read error: Connection reset by peer]
06:01|-|aroscha [~aroscha@nat.2day.kz] has joined #uml
06:01|-|aroscha_ [~aroscha@nat.2day.kz] has quit [Read error: Connection reset by peer]
06:07|-|aroscha [~aroscha@nat.2day.kz] has quit [Read error: Connection reset by peer]
06:10|-|aroscha [~aroscha@nat.2day.kz] has joined #uml
06:20|-|tyler [~tyler@adsl196-162-187-217-196.adsl196-14.iam.net.ma] has quit [Read error: Connection reset by peer]
06:24|-|tyler [~tyler@adsl196-162-187-217-196.adsl196-14.iam.net.ma] has joined #uml
06:30|-|tyler [~tyler@adsl196-162-187-217-196.adsl196-14.iam.net.ma] has quit [Read error: Connection reset by peer]
06:34|-|tyler [~tyler@adsl196-162-187-217-196.adsl196-14.iam.net.ma] has joined #uml
06:50|-|aroscha [~aroscha@nat.2day.kz] has quit [Ping timeout: 480 seconds]
06:53|-|aroscha [~aroscha@nat.2day.kz] has joined #uml
07:45|-|da-x [karrde@bzq-88-155-223-135.red.bezeqint.net] has quit [Ping timeout: 480 seconds]
07:54|-|da-x [karrde@bzq-88-155-179-48.red.bezeqint.net] has joined #uml
08:05|-|tyler [~tyler@adsl196-162-187-217-196.adsl196-14.iam.net.ma] has quit [Remote host closed the connection]
08:12|-|aroscha_ [~aroscha@nat.2day.kz] has joined #uml
08:14|-|darious12__ [~darius@athedsl-303154.home.otenet.gr] has quit [Quit: Konversation terminated!]
08:19|-|aroscha [~aroscha@nat.2day.kz] has quit [Ping timeout: 480 seconds]
08:40|-|dang [~dang@nemesis.fprintf.net] has quit [Quit: Leaving.]
08:58|-|dang [~dang@aa-redwall.nexthop.com] has joined #uml
09:27|-|aroscha [~aroscha@nat.2day.kz] has joined #uml
09:27|-|balbir [~balbir@59.145.136.1] has quit [Ping timeout: 480 seconds]
09:34|-|aroscha_ [~aroscha@nat.2day.kz] has quit [Ping timeout: 480 seconds]
10:13|-|aroscha_ [~aroscha@nat.2day.kz] has joined #uml
10:19|-|aroscha [~aroscha@nat.2day.kz] has quit [Ping timeout: 480 seconds]
10:19|-|aroscha_ [~aroscha@nat.2day.kz] has quit [Read error: Connection reset by peer]
10:19|-|aroscha [~aroscha@nat.2day.kz] has joined #uml
10:23<kokoko1>Anyone using skas-2.6.20-v9-pre9.patch.bz2 with 2.6.21 ?
10:23<kokoko1>I just patched .21 it give no Failed
10:24<kokoko1>I wonders if its wise to reboot this remote host into 2.6.21 patched with skas-2.6.20-v9-pre9 ? :)
10:24<caker>heh
10:24<caker>if you can get it to patch successfully, I'd think you'd be ok
10:24<caker>but YMMV
10:25<kokoko1>Right the skas patched giving Failed with 2.6.22
10:26<caker>!kernel
10:26<linbot>caker: The latest stable kernel is 2.6.22.4; the latest snapshot of the stable kernel is 2.6.23-rc3-git5; the latest beta kernel is 2.6.23-rc3-mm1.
10:26<kokoko1>cool yeah i did tried the patch with 2.6.22.4 but no luck
10:26<kokoko1>Recently this host of ours giving lot of problem went into unresponsive then we have to powercycle it
10:27<kokoko1>all UML on it giving no response i wonders what happened it was working fine from a while.
10:27<kokoko1>caker, only once before rebooting it i found these in messages logs wana see ?
10:28<caker>sure
10:28<kokoko1>http://rafb.net/p/8pdBa172.nln.html
10:28|-|jdike [~jdike@pool-71-248-190-161.bstnma.fios.verizon.net] has joined #uml
10:28<jdike>Hi guys
10:28<kokoko1>This is the only log i have
10:28<caker>hello
10:29<kokoko1>hiya jdike
10:29<kokoko1>nothing in logs else and this didn't appear again even the machine again gone into the coma
10:30<caker>kokoko1: long shot, but have you tested the ram (memtest)?
10:30<jdike>still trying to figure out the page ref thing?
10:30<kokoko1>caker, nope didn't
10:30<caker>http://rafb.net/p/8pdBa172.nln.html <-- this thing
10:30<caker>kokoko1: that's 2.6.20.x, right?
10:30<jdike>yeah
10:30<kokoko1>caker, yes
10:31<caker>hmm
10:31<jdike>kokoko1, what did you change right before this started?
10:31[~]caker runs 2.6.20.x as well
10:31<kokoko1>2.6.20-skas3-v9-pre9
10:31<kokoko1>jdike, hmm nothing but yes i did updated UML kernels
10:31<jdike>from what to what?
10:32<jdike>maybe UML started exercising a host bug
10:32<kokoko1>from 2.6.17.x to 2.6.21.4
10:32<jdike>big jump
10:32<caker>-um
10:32|-|tyler [~tyler@adsl196-225-187-217-196.adsl196-14.iam.net.ma] has joined #uml
10:32<kokoko1>jdike, you want me to compile 2.6.21 with skas3 which i have already started compiling
10:33<jdike>dunno
10:33<kokoko1>imean on actual host
10:33<jdike>how often does it happen?
10:34<kokoko1>from last sunday it gone into coma condition three times
10:34<kokoko1>2 times it was within an 2 or 3 hours
10:34<jdike>how hard is it for you to change UML versions?
10:35<jdike>and how much scope do you have to experiment?
10:38<kokoko1>changing uml kernel version is no problem i can do it fast
10:38<kokoko1>i am not very lucky with experiment remotely :)
10:38<kokoko1>this host is only running 3 uml
10:39<jdike>probably the best way to narrow down what's happening is to bisect it
10:40<jdike>get a git tree, tell it that 2.6.17 is good, 2.6.21 is bad, and have it give you a UML in between that you can test
10:40<jdike>tell it whether that one is good or bad, and repeat until you're down to a single commit
10:41<jdike>then we can stare at that commit and see how it might be affecting the host
10:52|-|aroscha_ [~aroscha@nat.2day.kz] has joined #uml
10:52|-|aroscha [~aroscha@nat.2day.kz] has quit [Read error: Connection reset by peer]
11:01<kokoko1>heh, brb in a while not getting this :)
11:25|-|aroscha_ [~aroscha@nat.2day.kz] has quit [Quit: aroscha_]
11:39|-|tyler [~tyler@adsl196-225-187-217-196.adsl196-14.iam.net.ma] has quit [Read error: Connection reset by peer]
11:41|-|tyler [~tyler@adsl196-225-187-217-196.adsl196-14.iam.net.ma] has joined #uml
11:57|-|quasisane [~sanep@c-76-118-191-64.hsd1.nh.comcast.net] has joined #uml
11:58|-|balbir [~balbir@122.167.95.137] has joined #uml
12:02<kokoko1>jdike, you do not want me to update the host kernel which causing problem?
12:02<kokoko1>How about giving a try to 2.6.21 with skas3, i am just few minutes away to reboot the host into it :)
12:03<jdike>Go ahead
12:03<kokoko1>Right, btw 2.6.21-uml is working find on other 2 hosts and we do not have any problem there.
12:04<jdike>However, what reason do you have to switch host versions, except "maybe it's fixed on a newer kernel", which is fine
12:04<kokoko1>I have update all uml versions to 2.6.21
12:04<jdike>but if it's not, what do you do?
12:05<kokoko1>That's a difficult questions thats why i am here to get free support for uml :)
12:06<jdike>There are two things you can do in order to chase this in an organized way
12:06<jdike>1 - bisect UML to figure out what it's doing differently and see if that suggests anything about what broke on the host
12:07<jdike>2 - bisect the host and see which commit breaks things
12:07<jdike>1 is quicker, but less direct
12:07<jdike>2 is slower, but will pin down what happened to the host
12:12<kokoko1>right
12:13<kokoko1>lets go for for the actaul host kernel
12:13<kokoko1>make modules_install under way
12:14<kokoko1>damn this host hosting our mail server on uml
12:14<kokoko1>programmers will bitch on me if match do not boot into new kernel
12:14<kokoko1>s/match/machine
12:15<kokoko1>anyhow i have no other option this machine is making lota trouble already
12:15|-||Blaisor| [~kvirc@85-18-251-172.ip.fastwebnet.it] has joined #uml
12:17<jdike>Hey!
12:17<jdike>long time no see
12:18<jdike>kokoko1, the other thing about option 2 is that you need to find a good host kernel
12:18<jdike>with option 1, you already have the two endpoints
12:19<kokoko1>jdike, so basicaly you want me to go for kernel between 2.6.17 and 2.6.21
12:19<kokoko1>for uml
12:19<jdike>yeah
12:20<jdike>not 2.6.17.x and 2.6.21.x
12:20[~]kokoko1 ponders
12:20<kokoko1>how about 2.6.20 for uml
12:20<kokoko1>i am ready to give it a go on umls
12:21<|Blaisor|>Hi Jeff
12:21<|Blaisor|>(but going away now :-( )
12:21<kokoko1>It this the nice guy were maintaining the skas patches before ? :)
12:21<|Blaisor|>Yes
12:22<|Blaisor|>it was me
12:22<kokoko1>Nice to meet ya
12:22<|Blaisor|>nice to meet you too,
12:22<|Blaisor|>but I must go
12:22<kokoko1>Okay catch you later
12:22<jdike>later
12:23<jdike>kokoko1, get a git tree and let git-bisect make decisions for you
12:23<kokoko1>jdike, how to ask the git tree for good kernel :)
12:23<kokoko1>git-bisect?
12:24<jdike>read http://groups.google.com/group/fa.linux.kernel/browse_thread/thread/af2a2d1151270a01/cdcaf2d55bb2f5e2?lnk=st&q=Linus+git-bisect+good&rnum=2&hl=en#cdcaf2d55bb2f5e2
12:26<kokoko1>but jdike i can't test that much :(
12:27<kokoko1>to get a "good" kernel
12:27<jdike>it'll take maybe 10-15 reboots to narrow it down
12:28<jdike>and you're not looking for a good kernel
12:28<kokoko1>But still I can't do that much reboots to these uml all of them in use for production
12:28<jdike>you're looking for the boundary between good and bad
12:28<jdike>in that case, bisect UML
12:29<kokoko1>jdike, quick try let me first boot into 2.6.21 at host, if it still going into koma then we will come to uml
12:29<kokoko1>what you say?
12:29<jdike>another alternative is to boot 2.6.22 on the host and if it's bad, complain to LKML and see if anyone knows what's happening
12:30<kokoko1>jdike, skas works with 2.6.22?
12:31<jdike>IIRC, jjkola had problems with it
12:31<kokoko1>okay then i am not going to touch it untill someone here booted it with skas3 :)
12:31<jdike>but you don't need it for testing
12:32|-||Blaisor| [~kvirc@85-18-251-172.ip.fastwebnet.it] has quit [Ping timeout: 480 seconds]
12:34<kokoko1>jeff why skas stopped at skas3-v9-pre9 from very long.
12:36<jdike>ask BB
12:36<jdike>except he just left :-)
12:38<kokoko1>heh
12:38<kokoko1>i tho its you maintaining skas now
12:52|-|kos_tom [~thomas@humanoidz.org] has joined #uml
12:52<dgraves>boot more times!
13:12|-|jiayingz [~jiayingz@207.47.98.129.static.nextweb.net] has quit [Quit: Leaving]
13:19|-|kokoko1 [~Slacker@203.148.65.8] has quit [Quit: Leaving]
13:21|-|tyler [~tyler@adsl196-225-187-217-196.adsl196-14.iam.net.ma] has quit [Remote host closed the connection]
13:31|-|kokoko1 [~Slacker@203.148.65.8] has joined #uml
14:03|-|kos_tom [~thomas@humanoidz.org] has quit [Quit: I like core dumps]
14:12|-|ram [~ram@pool-71-117-247-229.ptldor.fios.verizon.net] has quit [Ping timeout: 480 seconds]
14:35|-|ram [~ram@pool-71-117-247-229.ptldor.fios.verizon.net] has joined #uml
15:51<kokoko1>jdike, I have rebooted the host into 2.6.21-skas3-v9-pre9, i'll let you know if this could fix the instability problem
15:51<jdike>ok
16:08<dgraves>if it does, i'm installing 2.6.21.-skas3-v9-pre9. I'm seriously instabile.
16:08<dgraves>jdike: when is pre9 going to be skas3-v9?
16:09<dgraves>its been pre for years now.
16:09<jdike>ask BB
16:09<dgraves>::LOL::
16:09<dgraves>right. ;)
16:11<kokoko1>hehe
16:11<kokoko1>look like we have to live with -pre9
16:12|-|horst [~horst@a89-182-135-73.net-htp.de] has joined #uml
16:22|-|kybe__ [~kyrre@legolas.iu.hio.no] has joined #uml
16:22|-|kybe [~kyrre@legolas.iu.hio.no] has quit [Read error: Connection reset by peer]
17:09|-|dang [~dang@aa-redwall.nexthop.com] has quit [Quit: Leaving.]
17:59|-|horst [~horst@a89-182-135-73.net-htp.de] has quit [Remote host closed the connection]
18:17|-|jdike [~jdike@pool-71-248-190-161.bstnma.fios.verizon.net] has quit [Quit: Leaving]
18:32|-|da-x [karrde@bzq-88-155-179-48.red.bezeqint.net] has quit [Ping timeout: 480 seconds]
18:42|-|da-x [karrde@bzq-79-179-115-44.red.bezeqint.net] has joined #uml
19:01|-|kokoko1 [~Slacker@203.148.65.8] has quit [Ping timeout: 480 seconds]
21:26|-|silug [~steve@ppp-70-225-35-206.dsl.covlil.ameritech.net] has quit [Ping timeout: 480 seconds]
22:59|-|VS_ChanLog [~stats@ns.theshore.net] has left #uml [Rotating Logs]
22:59|-|VS_ChanLog [~stats@ns.theshore.net] has joined #uml
23:17|-|silug [~steve@ppp-70-225-34-108.dsl.covlil.ameritech.net] has joined #uml
---Logclosed Thu Aug 23 00:00:22 2007