Re: setitimer shows different between amd64 and ia32

On Sun, Jul 24, 2011 at 09:09:55PM -0700, Dave Hylands wrote: > Hi Adam, > > On Sun, Jul 24, 2011 at 8:10 PM, Adam Lee wrote: > > Hi, all > > > > I'm working on a test which invoking setitimer(), and it hang in > > ia32 and ppc, but passed in amd64, could you guys give some help? > > > > 1, I kno

Re: Interesting case while taking Ramdump of Linux kernel based device

Hi sandeep! On 7/25/11, sandeep kumar wrote: > Hi all, > In Android target mobiles there is a facility called "Ramdump", where the > entire Ram image is copied to a file > as the kernel goes to panic. > > Ramdump is implemented like this > 1) As the panic() function is called target will be reset

Re: Interesting case while taking Ramdump of Linux kernel based device

Hi sandeep, On Sun, Jul 24, 2011 at 9:18 PM, sandeep kumar wrote: > Hi all, > In Android target mobiles there is a facility called "Ramdump", where the > entire Ram image is copied to a file > as the kernel goes to panic. > > Ramdump is implemented like this > 1) As the panic() function is called

Interesting case while taking Ramdump of Linux kernel based device

Hi all, In Android target mobiles there is a facility called "Ramdump", where the entire Ram image is copied to a file as the kernel goes to panic. Ramdump is implemented like this 1) As the panic() function is called target will be reset. 2) Bootloader boots up in specific mode, where it enables

Re: setitimer shows different between amd64 and ia32

Hi Adam, On Sun, Jul 24, 2011 at 8:10 PM, Adam Lee wrote: > Hi, all > > I'm working on a test which invoking setitimer(), and it hang in > ia32 and ppc, but passed in amd64, could you guys give some help? > > 1, I know the 'value.it_interval.tv_usec' is too short, but why amd64 > passed? > > 2, I

Re: setitimer shows different between amd64 and ia32

Hi On Mon, Jul 25, 2011 at 03:10, Adam Lee wrote: > Hi, all > > I'm working on a test which invoking setitimer(), and it hang in > ia32 and ppc, but passed in amd64, could you guys give some help? > > 1, I know the 'value.it_interval.tv_usec' is too short, but why amd64 > passed? All of my a

Re: regarding do_IRQ()

Hi... On Sun, Jul 24, 2011 at 11:48, santhosh kumars wrote: .. > Here is my question  like ,If do_IRQ()  disables the interrupt > delivery on the line(I am assuming it disables the interrupt delivery > to all other processors on that line),then what about the other > devices which are sharin

setitimer shows different between amd64 and ia32

Hi, all I'm working on a test which invoking setitimer(), and it hang in ia32 and ppc, but passed in amd64, could you guys give some help? 1, I know the 'value.it_interval.tv_usec' is too short, but why amd64 passed? 2, If I switch clock source from "tsc" to "hpet" on ia32, it passed. 3, I comp

regarding do_IRQ()

Hi I am reading robertlove implementing interrupt handlers. When interrupt comes, the processor immediately stops what it is doing, disables the interrupt system (I am assuming disables all local interrupts of that processor)and jumps to the initial entry point where it calls do_IRQ(). do_IRQ() ack

"echo c > /proc/sysrq-trigger" is hung in fedora14 guest os.

Hi, I am running Fedora14 in "Virtualbox 4.0.8". The host OS is Windows-XP. I configured kdump, kexec & crash as per instruction in Fedora-14-Deployment_Guide. The system gets hung and crash file is not generated after running the command "echo c > /proc/sysrq-trigger". -