Re: Testing Boot Sequence

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Actually by testing boot sequence i mean correctness of state of the M/c after boot up.So consequently correctness of boot up operations.

Thanks,
Abhish


--- On Tue, 13/1/09, Peter Teoh <htmldeveloper@xxxxxxxxx> wrote:

> From: Peter Teoh <htmldeveloper@xxxxxxxxx>
> Subject: Re: Testing Boot Sequence
> To: abhish_agr@xxxxxxxxxxx
> Cc: "Erik Mouw" <mouw@xxxxxxxxxxxx>, kernelnewbies@xxxxxxxxxxxx
> Date: Tuesday, 13 January, 2009, 2:17 PM
> may be u have used the term wrongly....but my new
> understanding is
> that u want to verify correctness of bootup operations,
> something like
> that of TPM hardware.
> 
> On Tue, Jan 13, 2009 at 1:23 PM, abhish agarwal
> <abhish_agr@xxxxxxxxxxx> wrote:
> >
> > Hi,
> >
> > Sorry to all for Ccing particular emailid's.
> >
> > Boot sequence i have drawn is as follows::
> >
> > 1)  BIOS loades a small program which further loades
> boot program.
> >
> >
> >
> > 2)  boot---->loading
> kernel-------------->countdown can be interrupted(set of
> commands are available including loading a different
> kernel)------>boot command------->initializes
> CPU(including run time stack and virtual memory mapping)---|
> >                                  |
> >                                  |
> >                                  |
> >      
> -------------------------------------------------------
> >       |                                               
>       |
> >
> > M/c Dependent functions                               
>  M/C Independent functions
> > |                                                     
>    |
> > |---1)Mutexes                                         
>    |
> > |                                                     
>    |--1)Mounting Root File system
> > |---2)Virtual memory table                            
>    |
> > |                                                     
>    |--2)Initialize different DS
> > |---3)Configuring I/O Devices                         
>    |
> >
> >              |                                        
>  |
> >              |                                        
>  |
> >              
> ------------------------------------------
> >                                 |
> >                        System processes are made
> runnable
> >                                 |
> >                        User processes are brought into
> memory
> >
> >
> > Now to make sure that every thing is fine after boot
> up what all thing can i test?? One thing i mentioned in my
> previous mail is about dmesg o/p for any knd of warning or
> error during boot up. Apart from that what all i can test.
> >
> > Thanks
> > Abhish
> >
> > --- On Tue, 13/1/09, Erik Mouw
> <mouw@xxxxxxxxxxxx> wrote:
> >
> >> From: Erik Mouw <mouw@xxxxxxxxxxxx>
> >> Subject: Re: Testing Boot Sequence
> >> To: "abhish agarwal"
> <abhish_agr@xxxxxxxxxxx>
> >> Cc: "Kernelnewbies"
> <kernelnewbies@xxxxxxxxxxxx>
> >> Date: Tuesday, 13 January, 2009, 12:13 AM
> >> On Sun, 11 Jan 2009 17:59:17 +0530 (IST) abhish
> agarwal
> >> <abhish_agr@xxxxxxxxxxx> wrote:
> >> > I was trying to create set of testcases for
> boot
> >> sequence.But i am little bit confused how to
> start.what i
> >> have thought till now is first i will test dmesg
> output to
> >> make sure there is no error and failure,and also
> through rc
> >> script i find out what all files and directories
> are created
> >> during startup.What other things can i do please
> give me
> >> some input.
> >>
> >> For starters you could tell us what exactly you
> would try
> >> to test.
> >> "Testing boot sequence" is quite a broad
> thing.
> >>
> >> Oh, and just send your message to the list.
> Randomly
> >> CC'ing subscribers
> >> isn't any faster, just more annoying for those
> >> subscribers.
> >>
> >>
> 
> some ideas here:
> 
> 
> a.   verification means comparing with some predetermined /
> precalculated value.   So possibly if u stored checksums
> for important
> files/directories like /boot directory, and put this
> verification/self-correction early enough into the kernel
> codes,
> possibly u can do BOTH verification + self-correction at
> the same
> time....in case filesystem got corrupted.
> 
> b.   hardware verification?   this is hard....
> 
> c.   one area is in resume time - after resuming from
> hibernation
> mode, need to go through all the hardware initialization
> (already
> done) + verification (not sure if it is done, and how).
> 
> d.   many verification, can be done at the userspace level.
>   so
> possibly u should spawn a userspace process to continue the
> system
> verification beyond booting up.
> 
> e.   post process startup verification - ensuring all the
> necessary
> processes are started up.   but then this becomes more like
> a system
> management tool?
> 
> 
> -- 
> Regards,
> Peter Teoh


      Get rid of Add-Ons in your email ID. Get yourname@xxxxxxxxxxxxxxx Sign up now! http://in.promos.yahoo.com/address


--
To unsubscribe from this list: send an email with
"unsubscribe kernelnewbies" to ecartis@xxxxxxxxxxxx
Please read the FAQ at http://kernelnewbies.org/FAQ



[Index of Archives]     [Newbies FAQ]     [Linux Kernel Mentors]     [Linux Kernel Development]     [IETF Annouce]     [Git]     [Networking]     [Security]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux SCSI]     [Linux ACPI]
  Powered by Linux