l4-hackers Digest, Vol 53, Issue 22
丁莹
dingy09 at gmail.com
Wed Sep 19 16:11:53 CEST 2007
2007/9/19, l4-hackers-request at os.inf.tu-dresden.de <
l4-hackers-request at os.inf.tu-dresden.de>:
>
> Send l4-hackers mailing list submissions to
> l4-hackers at os.inf.tu-dresden.de
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers
> or, via email, send a message with subject or body 'help' to
> l4-hackers-request at os.inf.tu-dresden.de
>
> You can reach the person managing the list at
> l4-hackers-owner at os.inf.tu-dresden.de
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of l4-hackers digest..."
>
>
> Today's Topics:
>
> 1. Re: The ultimate HOW-TO (Adam Lackorzynski)
> 2. Re: l4linux starting problem (Adam Lackorzynski)
> 3. Re: the problems of l4linux (Adam Lackorzynski)
> 4. Re: the problems of l4linux (chenggh)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Wed, 19 Sep 2007 00:11:06 +0200
> From: Adam Lackorzynski <adam at os.inf.tu-dresden.de>
> Subject: Re: The ultimate HOW-TO
> To: l4-hackers at os.inf.tu-dresden.de
> Message-ID: <20070918221106.GD19315 at os.inf.tu-dresden.de>
> Content-Type: text/plain; charset=iso-8859-1
>
>
> On Tue Sep 18, 2007 at 08:05:18 -0700, ComputerScienceStudent wrote:
> >
> > Maybe this is the longest email you'll receive, but I would give you all
> the
> > possible informations.
> > There are three sections:
> > - THE MAKE ERRORS
> > - L4LINUX CONFIGURATION
> > - HARDWARE INFO.
>
> Ok, looks like you took your Linux configuration from your host (or the
> configuration system did so). Please use the default configuration
> coming with L4Linux by starting with 'make x86-native_defconfig'. And
> then those errors won't occur.
>
>
>
> Adam
> --
> Adam adam at os.inf.tu-dresden.de
> Lackorzynski http://os.inf.tu-dresden.de/~adam/
>
>
>
> ------------------------------
>
> Message: 2
> Date: Wed, 19 Sep 2007 00:17:25 +0200
> From: Adam Lackorzynski <adam at os.inf.tu-dresden.de>
> Subject: Re: l4linux starting problem
> To: l4-hackers at os.inf.tu-dresden.de
> Message-ID: <20070918221725.GE19315 at os.inf.tu-dresden.de>
> Content-Type: text/plain; charset=iso-8859-1
>
>
> On Tue Sep 18, 2007 at 17:34:07 +0800, ???? wrote:
> > l4lx | l4lx_irq_dev_startup_hw: Starting IRQ thread for IRQ 14.
> > l4lx | l4lx_thread_create: Created thread 0f.0a (IRQ14)
> > l4lx | l4lx_irq_dev_startup_hw: Starting IRQ thread for IRQ 15.
> > l4lx | l4lx_thread_create: Created thread 0f.0b (IRQ15)
> > l4lx | l4lx_irq_dev_startup_hw: Starting IRQ thread for IRQ 11.
> > l4lx | l4lx_thread_create: Created thread 0f.0c (IRQ11)
> > l4lx | l4lx_irq_dev_startup_hw: Starting IRQ thread for IRQ 12.
> > l4lx | acquire_irq: Error attaching to IRQ 12
> > l4lx | l4lx_thread_create: Created thread 0f.0d (IRQ12)
> > l4lx | l4lx_irq_dev_startup_hw: Starting IRQ thread for IRQ 1.
> > l4lx | acquire_irq: Error attaching to IRQ 1
> > l4lx | l4lx_thread_create: Created thread 0f.0e (IRQ1)
> >
> > And the dope when starting after following message then dead.
> >
> > Checking non-root filesystems:
> > fsck 1.39 (29-May-2006)
> > /dev/hda10:clean, 135991/667808 files,510175/1333387 blocks
> > Mounting non-root local filesystems:
> > kjournald starting. Commit interval 5 seconds
> > EXT3 FS on hda10, internal journal
> > EXT3-fs: mounted filesystem with ordered data mode.
> > /dev/hda10 on /home type ext3(rw)
> > Using /etc/random-seed to initialize /dev/urandom.
> >
> > How can I solve this problem?Anybody who knows please help me,Thanks!
>
> Well, userland starts, can't be too bad. Is that Ubuntu? Does a login
> prompt appear when you press Enter a bit?
> I wonder how the bootup looks like on native Linux (with X disabled).
>
> No,I use the slackware 12.0,the l4linux system dead when output above
> message,so when press enter there is no response,the native Linux when
> bootup after this will indicate message: INIT:enter runlevel 3.
Best Regards!
Adam
> --
> Adam adam at os.inf.tu-dresden.de
> Lackorzynski http://os.inf.tu-dresden.de/~adam/
>
>
>
> ------------------------------
>
> Message: 3
> Date: Wed, 19 Sep 2007 00:19:29 +0200
> From: Adam Lackorzynski <adam at os.inf.tu-dresden.de>
> Subject: Re: the problems of l4linux
> To: l4-hackers at os.inf.tu-dresden.de
> Message-ID: <20070918221929.GF19315 at os.inf.tu-dresden.de>
> Content-Type: text/plain; charset=iso-8859-1
>
>
> On Tue Sep 18, 2007 at 22:02:16 +0000, chenggh wrote:
> > Hi:
> > I boot l4dope with l4linux. The dope seems ok but l4linux doesn't
> start
> > completely. I am not sure whether it is l4 problem or linux problem.
> Please
> > help me.
> >
> > The l4 boot log
> > l4dope | Frame buffer base: 0x4000000
> > l4dope | Resolution: 1024x768x16
> > l4dope | Bytes per scanline: 2048
> > l4dope | Current video mode is 1024x768 red=11:5 green=5:6 blue=0:5
> res=0:0
> > l4lx | ======> L4Linux 2.6 starting... <========
> > l4lx | Linux version 2.6.22-l4 (root at darkstar) (gcc version 4.1.2) #1
> Tue
> > Se
> > l4lx : p 18 16:36:23 CST 2007
> > l4lx | Binary name: vmlinuz
> > l4lx | Kernel command line (5 args): earlyprintk=yes video=l4fb
> init=1
> > mem=6
> > l4lx : 4M root=/dev/hda2
> > l4lx | Image: 00400000 - 007a3000 [3724 KiB].
> > l4lx | Areas: Text: 00400000 - 006ad000
> [2740k | Initdata:
> > 006cc000 - 00700000 [208kB]
> > l4lx | BSS: 00702000 - 007a0f00 [635kB]
> > l4lx | l4lx_thread_create: Created thread 10.03 (tamer0)
> > l4lx | Tamer0 is 10.03
> > l4lx | Using tamed mode.
> > l4lx | Connecting to l4io server.
> > l4lx | l4env_linux_startup thread 4.
> > l4lx | l4lx_thread_create: Created thread 10.04 (cpu0)
> > l4lx | main thread will be 10.04
> > l4lx | l4env_register_pointer_section: addr = 00400000 size = 3149824
> > l4lx | sec-w-init: virt: 0x00400000 to 0x00700fff [3076 KiB]
> > l4lx | Noncontiguous region for sec-w-init
> > l4lx | sec-w-init: Number of physical regions: 3, 3149824 Bytes
> > l4lx | sec-w-init: 1: Phys: 0x0108a000 to 0x01218000,
> Size: 1630208
> > l4lx | sec-w-init: 2: Phys: 0x01419000 to 0x01500000, Size:
> 946176
> > l4lx | sec-w-ini startup message.
> > l4lx | Main thread running, waiting...
> > l4lx | setup_l4env_memory: Forcing superpages for main memory
> > l4lx | Main memory size: 64MB
> > l4lx | Got 2048kB of ISA DMA memory.
> > l4lx | ISA DMA memory: virt: 0x00800000 to 0x009fffff [2048 KiB]
> > l4lx | ISA DMA memory: Number of physical regions: 1, 2097152 Bytes
> > l4lx | ISA DMA memory: 1: Phys: 0x0043a000 to 0x0063a000,
> Size: 2097152
> > l4lx | Main memory: virt: 0x00c00000 to 0x04bfffff [65536 KiB]
> > l4lx | Main memory: Number of physical regions: 1, 67108864 Bytes
> > l4lx | Main memory: 1: Phys: 0x08c00000 to 0x0cc00000, Size:
> 67108864
> > l4lx | Filling lower ptabs...
> > l4lx | Done (1594 entries).
> > l4lx | l4lx_thread_create: Created thread 10.05 (timer.i0)
> > l4lx | Jumpinl4lx | idler0d_create: Created threadl4lx |
> Startil4dope
> > | SharedMem(allo0
> > l4lx | l4lx_thread_create: Created thread 10.08 (DOpE refresher)
> > l4lx | l4lx_thread_create: Created thread 10.09 (L4DOpEinput)
> > l4lx | l4lx_iRQ 17.
> > l4lx |startup_hw: Starting IRQ16)
> > l4lx | l4lx_irq_dev_startup_hw: Starting IRQ thread for IRQ 15.
> > l4lx | l4lx_thread_create: Created thread 10.0c (IRQ15)
> > l4lx | l4lx_irq_dev_startup_hw: Starting IRQ thread for IRQ 14.
> > l4lx tup_hw: Starting IRQ thread for IRQ 13.
> > l4lx | l4lx_ting IRQ thread for IRQ 12.
> > l4lx | acquire_irq: Error attaching to IRQ 12
> > l4lx | l4lx_thread_create: Created thread 10.0f (IRQ12)
> > l4lx | l4lx_irq_dev_startup_hw: Starting IRQ thread for IRQ 11.
> > l4lx | l4lx_thread_create: Created thread 10.10 (IRQ11)
> > l4lx | l4lx_irq_dev_startp_hw: Starting IRQ thread |
> > l4lx_irq_dev_startup_hw: Starting IRQ thread for IRQ 9.
> > l4lx | l4lx_thread_create: Created thread 10.12 (IRQ9)
> > l4lx | l4lx_irq_dev_startup_hw: Starting IRQ thread for IRQ 8.
> > l4lx | l4lx_thread_create: Created thread 10.13 (IRQ8)
> > l4lx | l4lx_irq_dev_startup_hw: Starting IRQ thread for IRQ 7.
> > l4lx | l4lx_thread_create: Created thread 10.14 (IRQ7)
> > l4lx | l4lx_irq_dev_startup_hw: Starting thread for IRQ 6.
> > l4lx | l4lx_thread_create: Created thread 10.15 (IRQ6)
> > l4lx | l4lx_irq_dev_startup_hw: Starting IRQ thread for IRQ 5.
> > l4lx | l4lx_thread_create: Created thread 10.16 (IRQ5)
> > l4lx | l4lx_irq_dev_startup_hw: Starting IRQ thread for IRQ 4.
> > l4lx | l4lx_thread_create: Created thread 10.17 (IRQ4)
> > l4lx | l4lx_irq_dev_startup_hw: Starting IRQ thread for IRQ 3.
> > l4lx | l4lx_irq_dev_startup_hw: Starting IRQ thread for IRQ 2.
> > l4lx | acquire_irq: Error attaching to IRQ 2
> > l4lx | l4lx_thread_create: Created thread 10.19 (IRQ2)
> > l4lx | l4lx_irq_dev_startup_hw: Starting IRQ thread for IRQ 1.
> > l4lx | acquire_irq: Error attaching to IRQ 1
> >
> > I don't know what these information stands for. Are all the
> necessary
> > interrupt threads ok? Or some of them is not ok.
>
> Seems ok. Some IRQ probing, 1, 2 and 12 are not allowed which is
> perfectly ok.
>
> > the linux boot log
> > ??????
> > EXTS FS on hda3, internal journal
> > EXT-fs: mounted filesystem with orderred data mode
> > /dev/hda3 on /home type ext3 (rw)
> > using /ect/random-seed to initialize /dev/urandom
> >
> > The linux could stop here even I wait lot of time. It doesn't go
> on.
>
> Looks the same as the other mail. Enter helps? Actually, what do you
> expect to see? :)
>
>
>
> Adam
> --
> Adam adam at os.inf.tu-dresden.de
> Lackorzynski http://os.inf.tu-dresden.de/~adam/
>
>
>
> ------------------------------
>
> Message: 4
> Date: Wed, 19 Sep 2007 09:01:38 +0000
> From: chenggh <chenggh04 at st.lzu.edu.cn>
> Subject: Re: the problems of l4linux
> To: l4-hackers at os.inf.tu-dresden.de
> Message-ID: <390158225.18632 at st.lzu.edu.cn>
> Content-Type: text/plain; charset="iso-8859-1"
>
> > Looks the same as the other mail. Enter helps? Actually, what do you
> > expect to see? :)
> Thanks.
> I also read another mail with the same situation. I use Slackware
> 12.0 not
> Ubuntu because in Ubuntu there is a glibc bug which has been existed at
> least
> for more than half year - "undefined reference to __stack_chk_fail". This
> bug
> has been reported many times and has committed to the Ubuntu Bug
> List. But
> bug is as before.
> The first question:
> the l4 boot log is like this:
> l4lx | l4lx_thread_create: Created thread 10.16 (IRQ5)
> l4lx | l4lx_irq_dev_startup_hw: Starting IRQ thread for IRQ 4.
> l4lx | l4lx_thread_create: Created thread 10.17 (IRQ4)
> l4lx | l4lx_irq_dev_startup_hw: Starting IRQ thread for IRQ 3.
> l4lx | l4lx_irq_dev_startup_hw: Starting IRQ thread for IRQ 2.
> l4lx | acquire_irq: Error attaching to IRQ 2
> l4lx | l4lx_thread_create: Created thread 10.19 (IRQ2)
> l4lx | l4lx_irq_dev_startup_hw: Starting IRQ thread for IRQ 1.
> l4lx | acquire_irq: Error attaching to IRQ 1
> It seems that when attaching IRQ1, IRQ2, IRQ9, IRQ12 there are
> some errors
> like "acquire_irq: Error attaching to IRQ x". But later attaching IRQ is
> ok.
> What is the matter? IRQ1 and IRQ12 are related with keyboard and monse,
> IRQ2
> is related with cascade, IRQ9 is about acpi. I have removed these drivers
> from linux. why is it also like this?
>
>
> The second problem is:
> The Linux booting stops at /ect/random-seed to initialize
> /dev/urandom and
> there is no login interface. I have checked the normal linux booting and
> after the using /ect/random-seed to initialize /dev/urandom the linux will
> finish booting kernel, enter the linux user space "INIT: Entering init X".
> So I think it is still the problem of l4linux kernel not the
> special linux
> distribution. Is it right?
> Thank you very much.
> Cheng
> Guanghui
>
>
>
> ------------------------------
>
> _______________________________________________
> l4-hackers mailing list
> l4-hackers at os.inf.tu-dresden.de
> http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers
>
>
> End of l4-hackers Digest, Vol 53, Issue 22
> ******************************************
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://os.inf.tu-dresden.de/pipermail/l4-hackers/attachments/20070919/f6550502/attachment.html>
More information about the l4-hackers
mailing list