l4-hackers

l4-hackers@os.inf.tu-dresden.de

2827 discussions

re: Your Account info.
by zbwa＠mailcity.com 20 Dec '98

20 Dec '98

ADULTS ONLY! Looking for the hottest ADULT ACTION? Looking for the net's youngest women? <a href="http://209.67.19.98/girlsgirlsgirls1/index.html">CLICK HERE</a> to enter http://209.67.19.98/girlsgirlsgirls1/index.html Only $3.95 to Join ! Live Voyeur Feeds 1000's of Hot Young Teen Pix Updated every 2 weeks Live Sex Feeds with Chat 6 Live Teen Girl Strip Tease Feeds Live Nude Chat with Sound using Real Player Full Length Porno Movies with Sound in Vivo and Real Player Format Masturbation Video's of our hottest young models and there favorite vibrators. Bio's on all the girls Email all the models and tell them you fantasies and get a personal reply ! <a href="http://209.67.19.98/girlsgirlsgirls1/index.html">CLICK HERE</a> to enter http://209.67.19.98/girlsgirlsgirls1/index.html

1 0

Between our..
by Pete 12 Dec '98

12 Dec '98

NO TRICKS - IT'S FREE! Process all major credit cards on your web site. NO MONTHLY COSTS, NO TRANSACTION FEES. CHECK IT OUT. You get: - Virtual Terminal for phone/fax/mail orders - Email receipt - Recurring billing feature - Password generation for membership sites - Automatic batch closing - Address Verification Service (AVS) - Backoffice to access account history - Remote mode - Interface for all major shopping carts - Installation included For our free information package just reply to: mailto:ccard1@eastmail.com?subject=more_info If you are interested in becoming an authorized agent please reply to: mailto:ccard1@eastmail.com?subject=agent If you wish to be removed from our mailing list please reply to: mailto:gran6@edmail.com?subject=remove

1 0

Re: L4-Linux 0.5.1 failed to boot...
by Michael Hohmuth 12 Dec '98

12 Dec '98

OKUJI Yoshinori <okuji(a)kuicr.kyoto-u.ac.jp> writes: > I tried new snapshot, 0.5.1, but I couldn't boot it. After L4-Linux > bootstrap, it couldn't detect my NE2000-compatible card and it > couldn't accept input from keyboard. The "login: " prompt appeared, > but I could do nothing, because console and network didn't work. My > CPU is AMD K6, but I don't think it is the source. My system is based > on Slackware-3.5.0, and is it possible that it may influece L4-Linux? Did this work before? One thing which won't work is loading original Linux kernel modules into L4Linux. From Linux' perspective, L4Linux is a different architecture, and modules have to be recompiled for L4Linux. Did you try loading the NE2000 driver as an original Linux kernel module? In this case, I recommend you compile the driver into your L4Linux kernel (or as an L4Linux module). Michael PS: Next week I'll be on vacation, and I won't answer my email. I'll try to catch up afterwards, so please keep sending in bug reports. They're appreciated a lot! -- hohmuth(a)innocent.com, hohmuth(a)inf.tu-dresden.de http://home.pages.de/~hohmuth/

2 1

Re: some bugs
by Michael Hohmuth 11 Dec '98

11 Dec '98

Sed, thanks for your report! I'll to reproduce the problem when I return from my vacation in ten days. roux(a)ecoledoc.lip6.fr (Cedric ROUX) writes: [...] > When i run it under fiasco, it runs a little, then it blocks, so i press > ctrl+c, that nornmally should end up the program and give me back the > shell, but not, it just continues a little more, and stops again, and so on > until the end of the program. > Then i see a lot of "Aiee: scheduling in interrupt 00422ba (activ 10000)" > with sometimes a 0 in place of the 10000. This looks like a scheduling problem in Fiasco: An interrupt thread is still active while the Linux scheduling code is run. This should not happen because interrupt threads have a higher priority and never block. Interesting. [...] > Third, but it was before patch3, > i ran through my hd, making ls, cat, rm and so on, and at one time, > after a ls, and before the result being displayed, i receive this message > "page fault in signal handler". Maybe patch3 fixes that, huh ? Maybe yes, but I'm not sure. > And last, i normally have shift+page-up to see last lines, but it does > not works under fiasco (maybe kernel 2.0.21 doesn't handle it anyway). > Little problem, but problem. This doesn't work because hardware scrolling is disabled in L4Linux. We did this because L4Linux shares the console's video memory with Fiasco/L4 and potentially other L4 tasks. > I soon gonna be able to debug with a second machine, so my next reports > will be better. That's cool! Michael -- hohmuth(a)innocent.com, hohmuth(a)inf.tu-dresden.de http://home.pages.de/~hohmuth/

1 0

some bugs
by roux＠ecoledoc.lip6.fr 11 Dec '98

11 Dec '98

Hello FIASCO people, here are some more bugs (yes, it is possible :)). First of all, when you press shift+print-screen (or control+print-screen, don't remember what bugs), everything blocks with a message that i forgot to write or that i've lost (i am in exams, my brain becomes a little strange, i forget things). If one could tried it to see if it happens on others machines. Note: it was before i applied path3 and patch4, so maybe it solves the problem. It might be a sigfault in a cli section, but nothing is sure. Second, i could run koules with svgalib !! but, a program of mine don't work. If someone could try it to see if it's my machine or what ? available at : http://www.ecoledoc.lip6.fr/~roux/demo/lost.tar.gz and a binary is provided at : http://www.ecoledoc.lip6.fr/~roux/demo/lost If you could try it with a clean linux to see what should be the correct behavior, then try it with fiasco. It's just a poor animation with some sound (maybe sound is necessary for it to behave bad, don't know). When i run it under fiasco, it runs a little, then it blocks, so i press ctrl+c, that nornmally should end up the program and give me back the shell, but not, it just continues a little more, and stops again, and so on until the end of the program. Then i see a lot of "Aiee: scheduling in interrupt 00422ba (activ 10000)" with sometimes a 0 in place of the 10000. This works too with patch3, i don't have put patch4, but don't think it is relevent. And when i press Esc, it simply reboots. Third, but it was before patch3, i ran through my hd, making ls, cat, rm and so on, and at one time, after a ls, and before the result being displayed, i receive this message "page fault in signal handler". Maybe patch3 fixes that, huh ? And last, i normally have shift+page-up to see last lines, but it does not works under fiasco (maybe kernel 2.0.21 doesn't handle it anyway). Little problem, but problem. I soon gonna be able to debug with a second machine, so my next reports will be better. See you, Sed.

1 0

L4-Linux 0.5.1 failed to boot...
by OKUJI Yoshinori 11 Dec '98

11 Dec '98

Hello. I tried new snapshot, 0.5.1, but I couldn't boot it. After L4-Linux bootstrap, it couldn't detect my NE2000-compatible card and it couldn't accept input from keyboard. The "login: " prompt appeared, but I could do nothing, because console and network didn't work. My CPU is AMD K6, but I don't think it is the source. My system is based on Slackware-3.5.0, and is it possible that it may influece L4-Linux? Thanks, OKUJI ---------------------------------------------------------------------- ~o o~ OKUJI Yoshinori <okuji(a)kuicr.kyoto-u.ac.jp> s ) http://duff.kuicr.kyoto-u.ac.jp/~okuji (check "okuji.asc" !)

1 0

Re: l4-linux booted ! [patch3]
by Michael Hohmuth 10 Dec '98

10 Dec '98

Harald Fritzsche <Harald.Fritzsche(a)mpd.de> writes: > i have tried the patch also. Thanks for trying it! > It seems, that l4linux-2.0.21 is more stable than before. > Also the module package seems to work (dummy.o ne.o and related). That means > in my case that these modules are autoloaded (ping works). But i haven´t a > real network. > > Occasianally the system does not reached the login, unfortunatly i have no > copy of the given message (probably rcv fault, during /sbin/init). If you get a message, it would be interesting to know what it says exactly. > Other times the reboot command causes a seg fault (null pointer > derefenrence) after the message "Send all processes kill sig" (This is > reported earlier). I haven't ever seen this. Do you get a register/stack dump from L4Linux? In this case it should be possible to find the location of the page fault (with System.map and disassembly output ("objdump -ld vmlinux")). Michael -- hohmuth(a)innocent.com, hohmuth(a)inf.tu-dresden.de http://home.pages.de/~hohmuth/

2 1

Re: page size assertion
by Eiji Ota 09 Dec '98

09 Dec '98

Michael-san, > Please try the patch appended below. > > I still would like to know which program triggers this problem as I > have not been able to reproduce it. Even after applying it, the same trouble happened. As my trial, I commented out that assertion in space.cc and the system seemed to work at that time.... However, I missed the important point, which I didn't know until that time. I used i486 PC-note(old, old note PC) and I set -nopentium to rmgr, it worked... i486 doesn't support a large page, does it ? oh, I'm sorry that you worry about a funny thing and I appreciate your advice because I thought you forgot this. Regards, Eiji Ota PS. Another funny thing. After removing the assertion, it worked even on i486. It might happen to work at that time...

1 0

New Fiasco snapshot
by Michael Hohmuth 07 Dec '98

07 Dec '98

I have released a new Fiasco snapshot (0.5.1, dated 981207) which has integrated all patches which have been posted to this mailing list. New snapshots of the support stuff also have been uploaded, including a new grub-ext2fs-floppy.gz (which doesn't any longer contain a confusing menu.lst file, and which is capable of loading gzip'd files and uncompressing them on the fly). I have changed the directory naming scheme in the tar files: They now all unpack into a directory called "l4", and not any longer "l4-<date>". This should make it easier to update only a part of the whole distribution in the future. Michael -- hohmuth(a)innocent.com, hohmuth(a)sax.de http://www.sax.de/~hohmuth/

1 0

Re: l4-linux booted !
by Michael Hohmuth 06 Dec '98

06 Dec '98

roux(a)ecoledoc.lip6.fr (Cedric ROUX) writes: > Then, another time, the boot process blocks with this time the message : > ipc.cc:169 : failed assertion `! in_sender_list()' Attached below are some Fiasco patches which should help. This problem was a symptom of a familiar problem: Code which disables interrupts to protect a critical region trapped into a page fault which subsequently enabled interrupts again. We now protect against this problem by pre-installing all pages required for the operation in a safe way before the actual critical region starts. Ugly synchronization problems like this have been one of the main reasons to try to get rid of disabling interrupts altogether. However, the occasional "cli" instruction is still lurking in the code, waiting to be replaced with better mechanisms (like non-blocking synchronization). The patch also includes a fix which enhances compatibility with Jochen's L4 so that L4Linux can handle segmentation faults better. Michael -- hohmuth(a)innocent.com, hohmuth(a)inf.tu-dresden.de http://home.pages.de/~hohmuth/

2 1

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

1999

1998

l4-hackers