--- Day changed --- Log opened Sun Jul 09 23:59:02 2006 01:55 -!- Le_Vert_ [~Le_Vert__@le-vert.net] has joined #uml 02:03 -!- Le_Vert__ [~Le_Vert__@le-vert.net] has quit [Ping timeout: 480 seconds] 03:11 -!- dominik [~dominik@62.99.199.140] has joined #uml 03:35 -!- pjb [~pjb@thalassa.informatimago.com] has quit [Read error: Connection reset by peer] 03:59 -!- pjb [~pjb@thalassa.informatimago.com] has joined #uml 04:39 -!- sandrosh [~c06ac502@mail.thegrebs.com] has joined #uml 05:18 -!- dominik [~dominik@62.99.199.140] has quit [Remote host closed the connection] 05:32 -!- sandrosh [~c06ac502@mail.thegrebs.com] has quit [Quit: http://thegrebs.com/oftc/ (EOF)] 05:43 -!- sandrosh [~c06ac502@mail.thegrebs.com] has joined #uml 05:44 < sandrosh> hello! 05:44 < sandrosh> anyone has a clue why this happens? 05:44 < sandrosh> Checking for the skas3 patch in the host: - /proc/mm...found - PTRACE_FAULTINFO...not found - PTRACE_LDT...foundUML running in SKAS0 mode 05:45 < sandrosh> they should either be found all the three or none of them 05:45 < sandrosh> a little bit after, in fact, everything crashes after some OOPS 05:45 < sandrosh> VFS: Mounted root (ext3 filesystem) readonly.Kernel panic - not syncing: map_stub_pages : /proc/mm map for code failed, err = 22 05:46 < sandrosh> on the bottom of the stackdump there is60287dc8: [<600143e0>] new_thread_handler+0xf1/0x127 07:11 -!- FireEgl [Atlantica@Atlantica.US] has quit [Ping timeout: 480 seconds] 07:12 -!- trash [trash@databerlin.org] has quit [Ping timeout: 480 seconds] 07:12 -!- trash [trash@databerlin.org] has joined #uml 07:22 -!- FireEgl [Atlantica@Atlantica.US.TO] has joined #uml 08:01 < dgraves> sandrosh: the first happens because you are not running in skas 3 mode. did you apply the whole skas3 patch to your host? 08:14 < sandrosh> dgraves: yes 08:15 < sandrosh> and it works if i compile with SUBARCH=i386 08:15 < sandrosh> there must be a bug in SUBARCH=x86_64 08:15 < sandrosh> the patch i am referring to is... 08:15 < sandrosh> (bitte warten...) 08:16 < sandrosh> 2.6.16-bs2 i believe 08:19 < dgraves> bitte warten = hold on? 08:19 < sandrosh> yep 08:19 < dgraves> just a bit? 08:19 < dgraves> whee! my wife would be proud of me. :) 08:19 < sandrosh> no, it should be "please wait" 08:19 < sandrosh> is she german? 08:19 < sandrosh> anyway i'm italian :) 08:20 < dgraves> 100%, apparently. not that she grew up there. ;_P 08:20 < sandrosh> lol 08:20 < dgraves> she just took a lot of courses, and they speak it in her family. 08:20 < dgraves> go figure. 08:20 < sandrosh> sorry. go figure what? 08:20 < sandrosh> your wife and her family life? 08:21 < dgraves> wait. the bs2 patch wasn't supposed to be applied to the host, was it? 08:21 < sandrosh> let me check 08:21 < dgraves> nah, just go figure that she's never been to germany even though she's 100%. 08:22 < sandrosh> it's a guest patch, so it's fine 08:22 < dgraves> okay. and what patch did you apply to the host? 08:23 < sandrosh> -skas3-v9-pre9 08:24 < dgraves> hrm. i haven't done 9 yet. 08:24 < sandrosh> precisely: skas-2.6.16-v9-pre9/ 08:24 < sandrosh> dgraves: have you got an x86_64 ? 08:25 < dgraves> no, not that either. :) 08:25 < dgraves> jdike should be on in.. oh, 2 hours or so. 08:25 < dgraves> you should probably ask him. 08:27 < sandrosh> sure, i'll wait 08:28 < sandrosh> it's always good if i can help a little bit by pointing out there might be a bug, even though i am interested in having i386 guests and they simply work for me =) 09:45 -!- FireEgl [Atlantica@Atlantica.US.TO] has quit [Ping timeout: 480 seconds] 09:53 -!- jdike [~jdike@pool-71-248-190-113.bstnma.fios.verizon.net] has joined #uml 09:53 < jdike> Hi guys 09:54 < dgraves> morning jdike. 09:54 < dgraves> sandrosh has a question. :) 09:55 < jdike> Uh oh 10:10 < dgraves> actually, he was just theorizing that skas3 was broken on x86_64. 10:11 < dgraves> Checking for the skas3 patch in the host: - /proc/mm...found - PTRACE_FAULTINFO...not found - PTRACE_LDT...foundUML running in SKAS0 mode 10:11 < dgraves> they should either be found all the three or none of them 10:11 < dgraves> a little bit after, in fact, everything crashes after some OOPS 10:11 < dgraves> VFS: Mounted root (ext3 filesystem) readonly.Kernel panic - not syncing: map_stub_pages : /proc/mm map for code failed, err = 22 10:11 < dgraves> on the bottom of the stackdump there is60287dc8: [<600143e0>] new_thread_handler+0xf1/0x127 10:12 -!- hfb [~hfb@75.4.220.175] has quit [Quit: Leaving] 10:24 < sandrosh> hello there 10:24 < dgraves> hi again. 10:25 < sandrosh> sorry, was discussing about yesterday's match =) 10:26 < sandrosh> catched up 10:27 < sandrosh> jdike: if i compile for i386 (yes, i could easily do that with ARCH=um and SUBARCH=i386, restarting from defconfig again) then i've got three "found" in a line 10:27 < sandrosh> and i am still choosing Opteron as my host processor type 10:39 < sandrosh> the wierd thing is now that with some filesystems it hangs if in skas3 mode 10:39 < sandrosh> in skas0 it doesn't hang 10:39 < sandrosh> and with other filesystems it doesn't hang in skas3 mode either 10:40 < sandrosh> for example busybox32-root_fs from nagafix works like a charm 10:41 < sandrosh> Gentoo-2006.0-x86-root_fs just works in skas0 10:41 -!- FireEgl [Atlantica@Atlantica.US] has joined #uml 11:01 -!- tyler [~tyler@86.220.210.199] has joined #uml 11:18 -!- hfb [~hfb@71.106.220.165] has joined #uml 11:26 -!- sandrosh [~c06ac502@mail.thegrebs.com] has quit [Quit: http://thegrebs.com/oftc/ (Ping timeout)] 11:39 -!- Cowboy_ [482f3d6060@68.183.193.73] has joined #uml 12:51 -!- tyler [~tyler@86.220.210.199] has quit [Ping timeout: 480 seconds] 13:09 -!- tyler [~tyler@86.220.230.100] has joined #uml 13:27 -!- trampled [slegge@fatboy.ethernet.org] has joined #uml 13:42 -!- Le_Vert__ [~Le_Vert__@le-vert.net] has joined #uml 13:49 -!- Le_Vert_ [~Le_Vert__@le-vert.net] has quit [Ping timeout: 480 seconds] 14:08 -!- Le_Vert_ [~Le_Vert__@le-vert.net] has joined #uml 14:10 < fo0bar> 10:53:09 up 14666 days, 14:55, 1 user, load average: 2.00, 2.29, 2.66 14:11 < kokoko1> OMG 14:11 < kokoko1> what is this? 14:11 < fo0bar> I seem to remember somebody talking about this... 2.6.17 kernel... is there a fix? 14:11 < dgraves> fo0bar: reboot your machine more often? 14:11 < fo0bar> dgraves: :) 14:12 < fo0bar> I believe I brought this instance up friday 14:12 < fo0bar> (two of them actuall, both have the problem) 14:12 < dgraves> then quick, submit your wormhole code! 14:15 < kokoko1> dgraves, yo 14:16 -!- Le_Vert__ [~Le_Vert__@le-vert.net] has quit [Ping timeout: 480 seconds] 14:24 -!- tyler [~tyler@86.220.230.100] has quit [Read error: Connection reset by peer] 14:25 -!- tyler [~tyler@86.220.230.100] has joined #uml 14:35 < jdike> fo0bar, that' 14:36 < jdike> 's fixed in 2.6.17.1 14:40 < fo0bar> jdike: hmm, I compiled it against debian's 2.6.17-2 sources, which, according to the changelog, include 2.6.17.1 14:40 * fo0bar digs 14:40 < fo0bar> thanks 14:40 -!- tyler [~tyler@86.220.230.100] has quit [Read error: Connection reset by peer] 14:40 < jdike> there should be a one-line unsigned -> signed patch in there 14:40 -!- tyler [~tyler@86.220.230.100] has joined #uml 14:42 < fo0bar> ... all I see in kernel.org's .1 is a 1-line SCTP fix 14:43 < fo0bar> ahh, it's .2 14:54 < jdike> whoops, OK 15:00 < dgraves> yo kokoko1 15:00 < dgraves> ::LOL:: 15:00 < dgraves> amazing what happens when you go negative. ;) 15:03 -!- tyler [~tyler@86.220.230.100] has quit [Ping timeout: 480 seconds] 15:49 -!- kos_tom [~thomas@82.237.107.242] has joined #uml 15:51 -!- Le_Vert__ [~Le_Vert__@le-vert.net] has joined #uml 15:58 -!- Le_Vert_ [~Le_Vert__@le-vert.net] has quit [Ping timeout: 480 seconds] 16:49 -!- Le_Vert_ [~Le_Vert__@le-vert.net] has joined #uml 16:56 -!- Le_Vert__ [~Le_Vert__@le-vert.net] has quit [Ping timeout: 480 seconds] 18:08 -!- kos_tom [~thomas@82.237.107.242] has quit [Read error: Connection reset by peer] 18:41 * trampled wishes they all could be california girls 19:04 * dgraves hums along. 19:07 -!- Le_Vert__ [~Le_Vert__@le-vert.net] has joined #uml 19:14 -!- Le_Vert_ [~Le_Vert__@le-vert.net] has quit [Ping timeout: 480 seconds] 19:16 -!- Le_Vert_ [~Le_Vert__@le-vert.net] has joined #uml 19:22 -!- Le_Vert [~Le_Vert__@le-vert.net] has joined #uml 19:23 -!- Le_Vert__ [~Le_Vert__@le-vert.net] has quit [Ping timeout: 480 seconds] 19:29 -!- Le_Vert_ [~Le_Vert__@le-vert.net] has quit [Ping timeout: 480 seconds] 19:32 < fo0bar> 16:32:22 up 52 min, 1 user, load average: 2.01, 2.39, 2.58 19:33 < fo0bar> what the... I added the uptime fix patch, and one of the 2 2.6.17 instances is fine now... but the other has a base load of 2.00, and rwhod is still out of control 19:39 < fo0bar> the times between the two are also off by about 5 minutes (they're both on the same host) 19:39 < fo0bar> grrr 19:46 -!- Cowboy_ [482f3d6060@68.183.193.73] has quit [Ping timeout: 480 seconds] 19:47 -!- hfb [~hfb@71.106.220.165] has quit [Quit: Leaving] 19:48 -!- Cowboy_ [62efb2499a@68.183.193.73] has joined #uml 19:50 -!- Le_Vert__ [~Le_Vert__@le-vert.net] has joined #uml 19:57 -!- Le_Vert [~Le_Vert__@le-vert.net] has quit [Ping timeout: 480 seconds] 20:29 -!- Le_Vert [~Le_Vert__@le-vert.net] has joined #uml 20:32 -!- Le_Vert__ [~Le_Vert__@le-vert.net] has quit [Ping timeout: 480 seconds] 21:02 -!- Cowboy_ [62efb2499a@68.183.193.73] has quit [Ping timeout: 480 seconds] 21:10 -!- Cowboy_ [f7ee7183e3@68.183.193.73] has joined #uml 21:11 -!- jdike [~jdike@pool-71-248-190-113.bstnma.fios.verizon.net] has quit [Quit: Leaving] 21:12 -!- hfb [~hfb@75.4.220.175] has joined #uml 23:57 -!- Cowboy_ [f7ee7183e3@68.183.193.73] has left #uml [Client exiting] --- Log closed Mon Jul 10 23:59:00 2006