[PATCH] sh64 (kernel/process.c): procfs_failure && create_proc*
description:
audit return code of create_proc_* function is a entry in janitors
TODO list. Audit this return and printk() when it fails, can spam a lot
system without compiled proc support. So this patch can audit return
code by means of procfs_failure().
Signed-off-by: Christophe Lucas <[EMAIL PROTECTED]>
diff -urpNX dontdiff linux-2.6.13-rc4-mm1.orig/arch/sh64/kernel/process.c
linux-2.6.13-rc4-mm1/arch/sh64/kernel/process.c
--- linux-2.6.13-rc4-mm1.orig/arch/sh64/kernel/process.c2005-07-29
00:44:44.0 +0200
+++ linux-2.6.13-rc4-mm1/arch/sh64/kernel/process.c 2005-08-03
12:42:07.0 +0200
@@ -953,8 +953,11 @@ asids_proc_info(char *buf, char **start,
static int __init register_proc_asids(void)
{
- create_proc_read_entry("asids", 0, NULL, asids_proc_info, NULL);
- return 0;
+ struct proc_dir_entry* ent;
+ ent = create_proc_read_entry("asids", 0, NULL, asids_proc_info, NULL);
+ if (!ent)
+ procfs_failure("process: Unable to create asids /proc
entry.\n");
+ return 0;
}
__initcall(register_proc_asids);
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[PATCH] sh64 (mm/fault.c): procfs_failure && create_proc*
description:
audit return code of create_proc_* function is a entry in janitors
TODO list. Audit this return and printk() when it fails, can spam a lot
system without compiled proc support. So this patch can audit return
code by means of procfs_failure().
Signed-off-by: Christophe Lucas <[EMAIL PROTECTED]>
diff -urpNX dontdiff linux-2.6.13-rc4-mm1.orig/arch/sh64/mm/fault.c
linux-2.6.13-rc4-mm1/arch/sh64/mm/fault.c
--- linux-2.6.13-rc4-mm1.orig/arch/sh64/mm/fault.c 2005-07-29
00:44:44.0 +0200
+++ linux-2.6.13-rc4-mm1/arch/sh64/mm/fault.c 2005-08-03 12:35:19.0
+0200
@@ -592,8 +592,11 @@ tlb_proc_info(char *buf, char **start, o
static int __init register_proc_tlb(void)
{
- create_proc_read_entry("tlb", 0, NULL, tlb_proc_info, NULL);
- return 0;
+ struct proc_dir_entry* ent;
+ ent = create_proc_read_entry("tlb", 0, NULL, tlb_proc_info, NULL);
+ if (!ent)
+ procfs_failure("fault.c: Unable to create tlb /proc entry.\n");
+ return 0;
}
__initcall(register_proc_tlb);
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[PATCH] sh64 (mm/ioremap.c): procfs_failure && create_proc*
description:
audit return code of create_proc_* function is a entry in janitors
TODO list. Audit this return and printk() when it fails, can spam a lot
system without compiled proc support. So this patch can audit return
code by means of procfs_failure().
Signed-off-by: Christophe Lucas <[EMAIL PROTECTED]>
diff -urpNX dontdiff linux-2.6.13-rc4-mm1.orig/arch/sh64/mm/ioremap.c
linux-2.6.13-rc4-mm1/arch/sh64/mm/ioremap.c
--- linux-2.6.13-rc4-mm1.orig/arch/sh64/mm/ioremap.c2005-07-29
00:44:44.0 +0200
+++ linux-2.6.13-rc4-mm1/arch/sh64/mm/ioremap.c 2005-08-03 12:41:14.0
+0200
@@ -460,9 +460,11 @@ ioremap_proc_info(char *buf, char **star
static int __init register_proc_onchip(void)
{
-#ifdef CONFIG_PROC_FS
- create_proc_read_entry("io_map",0,0, ioremap_proc_info, &shmedia_iomap);
-#endif
+ struct proc_dir_entry* ent;
+ ent = create_proc_read_entry("io_map",0,0,
+ ioremap_proc_info, &shmedia_iomap);
+ if (!ent)
+ procfs_failure("ioremap.c: Unable to create /proc entry.\n");
return 0;
}
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[PATCH][RFC] procfs_failure && possible uses
description:
audit return code of create_proc_* function is a entry in janitors
TODO list. Audit this return and printk() when it fails, spams log of
system without compiled proc support. So this patch can correct it.
Signed-off-by: Christophe Lucas <[EMAIL PROTECTED]>
arch/arm/kernel/apm.c |7 ---
arch/arm/kernel/ecard.c | 12 ++--
include/linux/proc_fs.h |5 +
3 files changed, 19 insertions(+), 5 deletions(-)
Index: linux-2.6.13-rc3-mm2/include/linux/proc_fs.h
===
--- linux-2.6.13-rc3-mm2.orig/include/linux/proc_fs.h
+++ linux-2.6.13-rc3-mm2/include/linux/proc_fs.h
@@ -83,6 +83,9 @@ struct vmcore {
#ifdef CONFIG_PROC_FS
+#define procfs_failure(fmt,arg...) \
+ printk(KERN_WARNING fmt,##arg)
+
extern struct proc_dir_entry proc_root;
extern struct proc_dir_entry *proc_root_fs;
extern struct proc_dir_entry *proc_net;
@@ -198,6 +201,8 @@ static inline void proc_net_remove(const
#else
+#define procfs_failure(fmt,arg...) do { } while(0)
+
#define proc_root_driver NULL
#define proc_net NULL
#define proc_bus NULL
Index: linux-2.6.13-rc3-mm2/arch/arm/kernel/ecard.c
===
--- linux-2.6.13-rc3-mm2.orig/arch/arm/kernel/ecard.c
+++ linux-2.6.13-rc3-mm2/arch/arm/kernel/ecard.c
@@ -776,9 +776,17 @@ static struct proc_dir_entry *proc_bus_e
static void ecard_proc_init(void)
{
+ struct proc_dir_entry *proc_entry;
+
proc_bus_ecard_dir = proc_mkdir("ecard", proc_bus);
- create_proc_info_entry("devices", 0, proc_bus_ecard_dir,
- get_ecard_dev_info);
+ if (!proc_bus_ecard_dir)
+ procfs_failure("ecard: Unable to create proc dir entry.\n");
+ else {
+ proc_entry = create_proc_info_entry("devices", 0,
+ proc_bus_ecard_dir, get_ecard_dev_info);
+ if (!proc_entry)
+ procfs_failure("ecard: Unable to create proc entry.\n");
+ }
}
#define ec_set_resource(ec,nr,st,sz) \
Index: linux-2.6.13-rc3-mm2/arch/arm/kernel/apm.c
===
--- linux-2.6.13-rc3-mm2.orig/arch/arm/kernel/apm.c
+++ linux-2.6.13-rc3-mm2/arch/arm/kernel/apm.c
@@ -515,6 +515,7 @@ static int kapmd(void *arg)
static int __init apm_init(void)
{
int ret;
+ struct proc_dir_entry *proc_entry;
if (apm_disabled) {
printk(KERN_NOTICE "apm: disabled on user request.\n");
@@ -534,9 +535,9 @@ static int __init apm_init(void)
return ret;
}
-#ifdef CONFIG_PROC_FS
- create_proc_info_entry("apm", 0, NULL, apm_get_info);
-#endif
+ proc_entry = create_proc_info_entry("apm", 0, NULL, apm_get_info);
+ if (!proc_entry)
+ procfs_failure("apm: Unable to create apm proc entry.\n");
ret = misc_register(&apm_device);
if (ret != 0) {
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
ChangeLog-2.4.30
Is this normal ;-) ChangeLog-2.4.30 is not found on www.kernel.org ? http://www.kernel.org/pub/linux/kernel/v2.4/ChangeLog-2.4.30 Have a nice day, ~Christophe PS: Please CC me :) - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
2.6.11 compilation problem.
Hi, Sorry if I waste your time, but I would recompile my kernel with this version, and when it was time to DRM, compilation dead. Perhaps I say mistakes, but it seems drivers/char/drm/gamma.h is not present, which is needed by other parts such as gamma_drv.c Perhaps, it is my .config which is faulty :-( if it is : sorry. ~Christophe # # Automatically generated make config: don't edit # CONFIG_X86=y CONFIG_MMU=y CONFIG_UID16=y CONFIG_GENERIC_ISA_DMA=y # # Code maturity level options # CONFIG_EXPERIMENTAL=y # CONFIG_CLEAN_COMPILE is not set CONFIG_BROKEN=y CONFIG_BROKEN_ON_SMP=y # # General setup # CONFIG_SWAP=y CONFIG_SYSVIPC=y CONFIG_POSIX_MQUEUE=y CONFIG_BSD_PROCESS_ACCT=y # CONFIG_BSD_PROCESS_ACCT_V3 is not set CONFIG_SYSCTL=y # CONFIG_AUDIT is not set CONFIG_LOG_BUF_SHIFT=14 CONFIG_HOTPLUG=y # CONFIG_IKCONFIG is not set CONFIG_EMBEDDED=y CONFIG_KALLSYMS=y # CONFIG_KALLSYMS_ALL is not set # CONFIG_KALLSYMS_EXTRA_PASS is not set CONFIG_FUTEX=y CONFIG_EPOLL=y CONFIG_IOSCHED_NOOP=y CONFIG_IOSCHED_AS=y CONFIG_IOSCHED_DEADLINE=y CONFIG_IOSCHED_CFQ=y # CONFIG_CC_OPTIMIZE_FOR_SIZE is not set # # Loadable module support # CONFIG_MODULES=y CONFIG_MODULE_UNLOAD=y CONFIG_MODULE_FORCE_UNLOAD=y CONFIG_OBSOLETE_MODPARM=y CONFIG_MODVERSIONS=y CONFIG_KMOD=y # # Processor type and features # CONFIG_X86_PC=y # CONFIG_X86_ELAN is not set # CONFIG_X86_VOYAGER is not set # CONFIG_X86_NUMAQ is not set # CONFIG_X86_SUMMIT is not set # CONFIG_X86_BIGSMP is not set # CONFIG_X86_VISWS is not set # CONFIG_X86_GENERICARCH is not set # CONFIG_X86_ES7000 is not set # CONFIG_M386 is not set # CONFIG_M486 is not set # CONFIG_M586 is not set # CONFIG_M586TSC is not set # CONFIG_M586MMX is not set CONFIG_M686=y # CONFIG_MPENTIUMII is not set # CONFIG_MPENTIUMIII is not set # CONFIG_MPENTIUMM is not set # CONFIG_MPENTIUM4 is not set # CONFIG_MK6 is not set # CONFIG_MK7 is not set # CONFIG_MK8 is not set # CONFIG_MCRUSOE is not set # CONFIG_MWINCHIPC6 is not set # CONFIG_MWINCHIP2 is not set # CONFIG_MWINCHIP3D is not set # CONFIG_MCYRIXIII is not set # CONFIG_MVIAC3_2 is not set # CONFIG_X86_GENERIC is not set # CONFIG_X86_EMU486 is not set CONFIG_X86_CMPXCHG=y CONFIG_X86_XADD=y CONFIG_X86_L1_CACHE_SHIFT=5 CONFIG_RWSEM_XCHGADD_ALGORITHM=y CONFIG_X86_PPRO_FENCE=y CONFIG_X86_WP_WORKS_OK=y CONFIG_X86_INVLPG=y CONFIG_X86_BSWAP=y CONFIG_X86_POPAD_OK=y CONFIG_X86_GOOD_APIC=y CONFIG_X86_USE_PPRO_CHECKSUM=y CONFIG_HPET_TIMER=y # CONFIG_SMP is not set CONFIG_PREEMPT=y CONFIG_X86_UP_APIC=y CONFIG_X86_UP_IOAPIC=y CONFIG_X86_LOCAL_APIC=y CONFIG_X86_IO_APIC=y CONFIG_X86_TSC=y CONFIG_X86_MCE=y CONFIG_X86_MCE_NONFATAL=m CONFIG_X86_MCE_P4THERMAL=y CONFIG_TOSHIBA=m CONFIG_I8K=m CONFIG_MICROCODE=m CONFIG_X86_MSR=m CONFIG_X86_CPUID=m # # Firmware Drivers # CONFIG_EDD=m # CONFIG_NOHIGHMEM is not set CONFIG_HIGHMEM4G=y # CONFIG_HIGHMEM64G is not set CONFIG_HIGHMEM=y # CONFIG_HIGHPTE is not set # CONFIG_MATH_EMULATION is not set CONFIG_MTRR=y # CONFIG_EFI is not set CONFIG_HAVE_DEC_LOCK=y # CONFIG_REGPARM is not set # # Power management options (ACPI, APM) # CONFIG_PM=y # CONFIG_SOFTWARE_SUSPEND is not set # CONFIG_PM_DISK is not set # # ACPI (Advanced Configuration and Power Interface) Support # CONFIG_ACPI=y CONFIG_ACPI_BOOT=y CONFIG_ACPI_INTERPRETER=y CONFIG_ACPI_SLEEP=y CONFIG_ACPI_SLEEP_PROC_FS=y CONFIG_ACPI_AC=m CONFIG_ACPI_BATTERY=m CONFIG_ACPI_BUTTON=m CONFIG_ACPI_FAN=m CONFIG_ACPI_PROCESSOR=m CONFIG_ACPI_THERMAL=m CONFIG_ACPI_ASUS=m CONFIG_ACPI_TOSHIBA=m # CONFIG_ACPI_DEBUG is not set CONFIG_ACPI_BUS=y CONFIG_ACPI_EC=y CONFIG_ACPI_POWER=y CONFIG_ACPI_PCI=y CONFIG_ACPI_SYSTEM=y CONFIG_X86_PM_TIMER=y # # APM (Advanced Power Management) BIOS Support # CONFIG_APM=m # CONFIG_APM_IGNORE_USER_SUSPEND is not set # CONFIG_APM_DO_ENABLE is not set # CONFIG_APM_CPU_IDLE is not set # CONFIG_APM_DISPLAY_BLANK is not set # CONFIG_APM_RTC_IS_GMT is not set # CONFIG_APM_ALLOW_INTS is not set # CONFIG_APM_REAL_MODE_POWER_OFF is not set # # CPU Frequency scaling # CONFIG_CPU_FREQ=y CONFIG_CPU_FREQ_PROC_INTF=m CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE=y # CONFIG_CPU_FREQ_DEFAULT_GOV_USERSPACE is not set CONFIG_CPU_FREQ_GOV_PERFORMANCE=y CONFIG_CPU_FREQ_GOV_POWERSAVE=m CONFIG_CPU_FREQ_GOV_USERSPACE=m # CONFIG_CPU_FREQ_24_API is not set CONFIG_CPU_FREQ_TABLE=m # # CPUFreq processor drivers # CONFIG_X86_ACPI_CPUFREQ=m # CONFIG_X86_ACPI_CPUFREQ_PROC_INTF is not set CONFIG_X86_POWERNOW_K6=m CONFIG_X86_POWERNOW_K7=m CONFIG_X86_POWERNOW_K8=m CONFIG_X86_GX_SUSPMOD=m CONFIG_X86_SPEEDSTEP_CENTRINO=m CONFIG_X86_SPEEDSTEP_CENTRINO_TABLE=y CONFIG_X86_SPEEDSTEP_CENTRINO_ACPI=y CONFIG_X86_SPEEDSTEP_ICH=m CONFIG_X86_SPEEDSTEP_SMI=m CONFIG_X86_P4_CLOCKMOD=m CONFIG_X86_SPEEDSTEP_LIB=m CONFIG_X86_SPEEDSTEP_RELAXED_CAP_CHECK=y CONFIG_X86_LONGRUN=m CONFIG_X86_LONGHAUL=m # # Bus options (PCI, PCMCIA, EISA, MCA, ISA) # CONFIG_PCI=y # CONFIG_PCI_GOBIOS is not set # CONFIG_PCI_GOMMCONFIG is not set # CONFIG_PCI_GODIRECT is not set CONFIG_PCI_GOANY=y CONFIG_PCI_BIOS=y CONFIG_
Re: UserMode bug in 2.6.11-rc5? autolearn=disabled version=3.0.2
Kristian Sørensen ([EMAIL PROTECTED]) wrote: > On Wednesday 02 March 2005 19:42, Jeff Dike wrote: > > [EMAIL PROTECTED] said: > > > Hey! Thanks - that fixed the problem! :-D > > > > Didn't you say this this setup worked with 2.6.10? That's why I didn't > > suggest staring at /etc/inittab. > Yes - it works fine with 2.6.10. Does anyone of you know why/where the change > was? For my part, I have made this changes on a 2.6.9 kernel to make it work about this problem. ~Christophe - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: UserMode bug in 2.6.11-rc5? autolearn=disabled version=3.0.2
Kristian Sørensen ([EMAIL PROTECTED]) wrote: > On Wednesday 02 March 2005 14:59, Kristian Sørensen wrote: > > On Wednesday 02 March 2005 14:45, Christophe Lucas wrote: > > > Kristian Sørensen ([EMAIL PROTECTED]) wrote: > > > > Hi! > > > > > > > > I've just tried usermode Linux with a 2.6.11-rc5 kernel. My kernel > > > > boots, but when the shell is to be spawned it freezes: > > > > > > > > INIT: Entering runlevel: 2 > > > > Starting system log daemon: syslogd. > > > > Starting kernel log daemon: klogd. > > > > Starting internet superserver: inetd. > > > > Starting deferred execution scheduler: atd. > > > > Starting periodic command scheduler: cron. > > > > INIT: Id "0" respawning too fast: disabled for 5 minutes > > > > INIT: Id "1" respawning too fast: disabled for 5 minutes > > > > INIT: Id "2" respawning too fast: disabled for 5 minutes > > > > INIT: Id "c" respawning too fast: disabled for 5 minutes > > > > INIT: no more processes left in this runlevel > > > > > > > > > > > > I've attached the .config for both 2.6.10 (working perfectly) and the > > > > one for 2.6.11-rc5. The root filesystem this: > > > > http://prdownloads.sourceforge.net/user-mode-linux/Debian-3.0r0.ext2.bz > > > >2 > > > > > > Hi, > > > > > > What do you have in your /etc/inittab of your root_fs ? > > > I think you sould replace tty0 by vc/0 such as. > > > > > > I have had this on a kernel 2.6.10 and debian-3.1 root_fs. > > > > > > ~Christophe > > > > Hey! Thanks - that fixed the problem! :-D > Damn :-( Now the terminal is ready - but the passwords is not reconized (both > in 2.6.10 and 2.6.11-rc5) :-/ /etc/passwd and /etc/shadow is not initialized, more precisely you don't have the rigth password. You can have a debian-3.1 root_fs on http://titux.homeunix.org/~clucas/uml/ But I think we will go on this topic out of this mailing list. -- ~Christophe - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: UserMode bug in 2.6.11-rc5?
Kristian Sørensen ([EMAIL PROTECTED]) wrote: > Hi! > > I've just tried usermode Linux with a 2.6.11-rc5 kernel. My kernel boots, but > when the shell is to be spawned it freezes: > > INIT: Entering runlevel: 2 > Starting system log daemon: syslogd. > Starting kernel log daemon: klogd. > Starting internet superserver: inetd. > Starting deferred execution scheduler: atd. > Starting periodic command scheduler: cron. > INIT: Id "0" respawning too fast: disabled for 5 minutes > INIT: Id "1" respawning too fast: disabled for 5 minutes > INIT: Id "2" respawning too fast: disabled for 5 minutes > INIT: Id "c" respawning too fast: disabled for 5 minutes > INIT: no more processes left in this runlevel > > > I've attached the .config for both 2.6.10 (working perfectly) and the one for > 2.6.11-rc5. The root filesystem this: > http://prdownloads.sourceforge.net/user-mode-linux/Debian-3.0r0.ext2.bz2 Hi, What do you have in your /etc/inittab of your root_fs ? I think you sould replace tty0 by vc/0 such as. I have had this on a kernel 2.6.10 and debian-3.1 root_fs. ~Christophe - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
[OOPS] 2.6.9
Hi, Here is an oops which have been occured around 3, 4 time in a week. I know that, perhaps the reason of this crash have been tracked and killed in 2.6.10, and near 2.6.11. But if it could help, I enclosed oops and ksymoops files. I can put on net all information about the computer on which this oops appeared. Have a good day :) -- Christophe ksymoops 2.4.9 on i686 2.6.9. Options used -v /usr/src/linux-2.6.9/vmlinux (specified) -K (specified) -l /proc/modules (default) -o /lib/modules/2.6.9/ (default) -M (specified) No modules in ksyms, skipping objects No ksyms, skipping lsmod EIP: 0060:[] Not Tainted Using defaults from ksymoops -t elf32-i386 -a i386 EFLAGS: 00010097 (2.6.9) eax: 3e03a64b ebx: 3b9b7640 ecx: c914cea0 edx: d755df64 esi: d755c000 edi: 3e06637b ebp: d755df64 esp: d755df54 ds: 007b es: 007b ss: 0068 c01203eb 0001 c012085f d755df64 c914cea0 c9145e00 d755dfc4 0001 c033c0a8 000a c0302800 c011c6fd c033c0a8 0046 c029b510 c011c736 d755c000 c0106e2d c0302800 0001 c029b510 b707c480 Call Trace: [] update_wall_time+0xb/0x40 [] do_timer+0xdf/0xf0 [] __do_softirq+0x7d/0x90 [] do_softirq+0x26/0x30 [] do_IRQ+0xfd/0x130 [] common_interrupt+0x18/0x20 Code: 24 10 89 41 04 8b 44 24 0c 89 4c 24 10 89 02 89 50 04 89 5f 08 89 5b 04 90 8b 4d 00 39 e9 74 41 8b 51 04 8b 01 8b 79 10 8b 59 14 <89> 50 04 89 02 c7 41 04 00 02 20 00 c7 01 00 01 10 00 c7 41 18 >>EIP; c0120662<= >>eax; 3e03a64b <__crc_scsi_cmd_ioctl+60d98/48514c> >>ebx; 3b9b7640 <__crc_skb_iter_next+9334/568bc3> >>ecx; c914cea0 <__crc_elv_add_request+495a4c/5724c0> >>edx; d755df64 <__crc_blkdev_scsi_issue_flush_fn+15993c/2ba9fb> >>esi; d755c000 <__crc_blkdev_scsi_issue_flush_fn+1579d8/2ba9fb> >>edi; 3e06637b <__crc_scsi_cmd_ioctl+8cac8/48514c> >>ebp; d755df64 <__crc_blkdev_scsi_issue_flush_fn+15993c/2ba9fb> >>esp; d755df54 <__crc_blkdev_scsi_issue_flush_fn+15992c/2ba9fb> Trace; c01203eb Trace; c012085f Trace; c011c6fd <__do_softirq+7d/90> Trace; c011c736 Trace; c0106e2d Trace; c0104b88 Code; c0120637 <_EIP>: Code; c0120637 0: 24 10 and$0x10,%al Code; c0120639 2: 89 41 04 mov%eax,0x4(%ecx) Code; c012063c 5: 8b 44 24 0c mov0xc(%esp),%eax Code; c0120640 9: 89 4c 24 10 mov%ecx,0x10(%esp) Code; c0120644 d: 89 02 mov%eax,(%edx) Code; c0120646 f: 89 50 04 mov%edx,0x4(%eax) Code; c0120649 12: 89 5f 08 mov%ebx,0x8(%edi) Code; c012064c 15: 89 5b 04 mov%ebx,0x4(%ebx) Code; c012064f 18: 90nop Code; c0120650 19: 8b 4d 00 mov0x0(%ebp),%ecx Code; c0120653 1c: 39 e9 cmp%ebp,%ecx Code; c0120655 1e: 74 41 je 61 <_EIP+0x61> Code; c0120657 20: 8b 51 04 mov0x4(%ecx),%edx Code; c012065a 23: 8b 01 mov(%ecx),%eax Code; c012065c 25: 8b 79 10 mov0x10(%ecx),%edi Code; c012065f 28: 8b 59 14 mov0x14(%ecx),%ebx Code; c0120662<= 2b: 89 50 04 mov%edx,0x4(%eax) <= Code; c0120665 2e: 89 02 mov%eax,(%edx) Code; c0120667 30: c7 41 04 00 02 20 00 movl $0x200200,0x4(%ecx) Code; c012066e 37: c7 01 00 01 10 00 movl $0x100100,(%ecx) Code; c0120674 3d: c7.byte 0xc7 Code; c0120675 3e: 41inc%ecx Code; c0120676 3f: 18.byte 0x18 CPU:0 EIP: 0060:[] Not Tainted EFLAGS: 00010097 (2.6.9) EIP is at run_timer_softirq+0xa2/0x1b0 eax: 3e03a64b ebx: 3b9b7640 ecx: c914cea0 edx: d755df64 esi: d755c000 edi: 3e06637b ebp: d755df64 esp: d755df54 ds: 007b es: 007b ss: 0068 process setiathome (pid=8548, threadinfo=d755c000, task=d3206aa0) Stack: c01203eb 0001 c012085f d755df64 c914cea0 c9145e00 d755dfc4 0001 c033c0a8 000a c0302800 c011c6fd c033c0a8 0046 c029b510 c011c736 d755c000 c0106e2d c0302800 0001 c029b510 b707c480 Call Trace: [] update_wall_time+0xb/0x40 [] do_timer+0xdf/0xf0 [] __do_softirq+0x7d/0x90 [] do_softirq+0x26/0x30 [] do_IRQ+0xfd/0x130 [] common_interrupt+0x18/0x20 Code: 24 10 89 41 04 8b 44 24 0c 89 4c 24 10 89 02 89 50 04 89 5f 08 89 5b 04 90 8b 4d 00 39 e9 74 41 8b 51 04 8b 01 8b 79 10 8b 59 14 <89> 50 04 89 02 c7 41 04 00 02 20 00 c7 01 00 01 10 00 c7 41 18
