fault-injection-developer Mailing List for Fault Injection Test Harness (Page 2)
Status: Alpha
Brought to you by:
rustyl
Menu
▾
▴
fault-injection-developer — Developer discussions about creating a fault injection test harness.
You can subscribe to this list here.
| 2002 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(1) |
Jul
|
Aug
(13) |
Sep
(2) |
Oct
(49) |
Nov
(69) |
Dec
(70) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2003 |
Jan
(64) |
Feb
(41) |
Mar
(25) |
Apr
(18) |
May
(5) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2004 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2006 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(3) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2007 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2008 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
(1) |
Nov
|
Dec
|
| 2009 |
Jan
(1) |
Feb
(2) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2011 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
|
Dec
|
| 2014 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
(1) |
Dec
|
| 2015 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(2) |
| 2016 |
Jan
(2) |
Feb
(5) |
Mar
(2) |
Apr
(1) |
May
(1) |
Jun
(1) |
Jul
(2) |
Aug
(1) |
Sep
|
Oct
|
Nov
|
Dec
|
| 2017 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(4) |
Nov
|
Dec
|
|
From: Wang, S. <sta...@in...> - 2003-04-17 06:23:50
|
sorry for the typo :)
Kevin will add irq interceptor support next week.
Regards,
Stan
-----Original Message-----
From: arun [mailto:ar...@np...]
Sent: 2003-04-17 14:18
To: Wang, Stanley
Cc: SourceforgeFI mail list (E-mail); Gao, Kevin
Subject: [Fault-injection-developer] Re: IRQ interceptor
Hi Stan,
Thanks a bunch , I could generate interrupts with the help of workaround sent by you ( There's a
typo in the commands u sent, "cat" should be replaced with "echo").
Thanks
-arun
Wang, Stanley wrote:
Hi, Arun
It is a little bit complex to use irq interceptor :(
The ficl doesn't support irq interceptor right now. Hence you must
the fault set by hands. Following is a simple example, you can learn
how to use it by read fi_irq.c. (Kevin will add irq interceptor support
ASAP.)
example:
add fault set
$ cat "add $irq_num $dev_name $spurious_hertz $delay_hertz $delay_time" > /sys/fi/interceptors/irq/ctl
del fault set
$ cat "del" > /sys/fi/interceptors/irq/ctl
Hope it clarifies.
Stan
-----Original Message-----
From: arun [ mailto:ar...@np...]
Sent: 2003-04-16 13:51
To: Wang, Stanley
Cc: SourceforgeFI mail list (E-mail); Gao, Kevin
Subject: IRQ interceptor
Hi Stanley/Kevin,
The fith_utility/ficl_cmd.c doesnt seems to handle IRQ interceptor. It only handle the "Trigger"
and for the rest errors are popped up.
I tried the below which was from the fith_manual from CVS directory (might be old and obselete)
irq.fsml:
<?xml version="1.0" encoding="UTF-8" ?>
<!-- $Id: fith.texi,v 1.12 2002/06/03 07:45:22 stanley Exp $ -->
<!-- irq is the interrupt vector you want to intercept -->
<!-- devname is the device's name that be used in request_irq() -->
<!-- spurious_hertz="10" means one spurious IRQ is generated -->
<!-- per 10 timer clicks -->
<!-- delay_hertz="10" means delay one IRQ per 10 times -->
<!-- delay_time="3" means the IRQ will be delayed 3 timer clicks -->
<fake_irq irq="4"
modname=”fith_dummy”
devname="dummy"
spurious_hertz="10"
delay_hertz="10"
delay_time="3"
/>
[root@xcast1hclt-ntl test]# ficl -i irq1.fsml
Inserting irq1.fsml into fi_dm...
Document of the wrong type, FSML Namespace not found!
Can not parser out faultset from this file.
But this fsml file could be inserted using ficl command.
I guess the IRQ interceptor should be given inside the TRIGGER tag... I tried
that, but in vain (The ficl_cmd.c handles only the parameters for the PF interceptor)
I tried to "bk pull" to get the latest "fith tool", but there was no updation.... I just
want to clarify whether there is a workaround for this or I should update the ficl_cmd.c to
handle the IRQ interceptor parsing... Please pass on any document (if available) about
this...
Thanks
-arun
|
|
From: arun <ar...@np...> - 2003-04-17 06:20:28
|
Hi Stan, Thanks a bunch , I could generate interrupts with the help of workaround sent by you ( There's a typo in the commands u sent, "cat" should be replaced with "echo"). Thanks -arun Wang, Stanley wrote: > Hi, Arun > It is a little bit complex to use irq interceptor :( > The ficl doesn't support irq interceptor right now. Hence you must > the fault set by hands. Following is a simple example, you can learn > how to use it by read fi_irq.c. (Kevin will add irq interceptor support > ASAP.) > example: > add fault set > $ cat "add $irq_num $dev_name $spurious_hertz $delay_hertz $delay_time" > /sys/fi/interceptors/irq/ctl > del fault set > $ cat "del" > /sys/fi/interceptors/irq/ctl > Hope it clarifies. > Stan > > -----Original Message----- > From: arun [mailto:ar...@np...] > Sent: 2003-04-16 13:51 > To: Wang, Stanley > Cc: SourceforgeFI mail list (E-mail); Gao, Kevin > Subject: IRQ interceptor > > Hi Stanley/Kevin, > The fith_utility/ficl_cmd.c doesnt seems to handle IRQ > interceptor. It only handle the "Trigger" > and for the rest errors are popped up. > I tried the below which was from the fith_manual from CVS > directory (might be old and obselete) > > irq.fsml: > <?xml version="1.0" encoding="UTF-8" ?> > <!-- $Id: fith.texi,v 1.12 2002/06/03 07:45:22 stanley Exp $ --> > <!-- irq is the interrupt vector you want to intercept --> > > <!-- devname is the device's name that be used in request_irq() --> > > <!-- spurious_hertz="10" means one spurious IRQ is generated --> > <!-- per 10 timer clicks --> > <!-- delay_hertz="10" means delay one IRQ per 10 times --> > <!-- delay_time="3" means the IRQ will be delayed 3 timer clicks --> > <fake_irq irq="4" > modname=”fith_dummy” > devname="dummy" > spurious_hertz="10" > delay_hertz="10" > delay_time="3" > /> > > [root@xcast1hclt-ntl test]# ficl -i irq1.fsml > Inserting irq1.fsml into fi_dm... > Document of the wrong type, FSML Namespace not found! > Can not parser out faultset from this file. > > > But this fsml file could be inserted using ficl command. > > I guess the IRQ interceptor should be given inside the TRIGGER > tag... I tried > that, but in vain (The ficl_cmd.c handles only the parameters for > the PF interceptor) > > I tried to "bk pull" to get the latest "fith tool", but there was > no updation.... I just > want to clarify whether there is a workaround for this or I should > update the ficl_cmd.c to > handle the IRQ interceptor parsing... Please pass on any document > (if available) about > this... > > Thanks > -arun > |
|
From: Wang, S. <sta...@in...> - 2003-04-16 06:44:12
|
Hi, Arun
It is a little bit complex to use irq interceptor :(
The ficl doesn't support irq interceptor right now. Hence you must
the fault set by hands. Following is a simple example, you can learn
how to use it by read fi_irq.c. (Kevin will add irq interceptor support
ASAP.)
example:
add fault set
$ cat "add $irq_num $dev_name $spurious_hertz $delay_hertz $delay_time" > /sys/fi/interceptors/irq/ctl
del fault set
$ cat "del" > /sys/fi/interceptors/irq/ctl
Hope it clarifies.
Stan
-----Original Message-----
From: arun [mailto:ar...@np...]
Sent: 2003-04-16 13:51
To: Wang, Stanley
Cc: SourceforgeFI mail list (E-mail); Gao, Kevin
Subject: IRQ interceptor
Hi Stanley/Kevin,
The fith_utility/ficl_cmd.c doesnt seems to handle IRQ interceptor. It only handle the "Trigger"
and for the rest errors are popped up.
I tried the below which was from the fith_manual from CVS directory (might be old and obselete)
irq.fsml:
<?xml version="1.0" encoding="UTF-8" ?>
<!-- $Id: fith.texi,v 1.12 2002/06/03 07:45:22 stanley Exp $ -->
<!-- irq is the interrupt vector you want to intercept -->
<!-- devname is the device's name that be used in request_irq() -->
<!-- spurious_hertz="10" means one spurious IRQ is generated -->
<!-- per 10 timer clicks -->
<!-- delay_hertz="10" means delay one IRQ per 10 times -->
<!-- delay_time="3" means the IRQ will be delayed 3 timer clicks -->
<fake_irq irq="4"
modname=”fith_dummy”
devname="dummy"
spurious_hertz="10"
delay_hertz="10"
delay_time="3"
/>
[root@xcast1hclt-ntl test]# ficl -i irq1.fsml
Inserting irq1.fsml into fi_dm...
Document of the wrong type, FSML Namespace not found!
Can not parser out faultset from this file.
But this fsml file could be inserted using ficl command.
I guess the IRQ interceptor should be given inside the TRIGGER tag... I tried
that, but in vain (The ficl_cmd.c handles only the parameters for the PF interceptor)
I tried to "bk pull" to get the latest "fith tool", but there was no updation.... I just
want to clarify whether there is a workaround for this or I should update the ficl_cmd.c to
handle the IRQ interceptor parsing... Please pass on any document (if available) about
this...
Thanks
-arun
|
|
From: arun <ar...@np...> - 2003-04-16 05:53:09
|
Hi Stanley/Kevin, The fith_utility/ficl_cmd.c doesnt seems to handle IRQ interceptor. It only handle the "Trigger" and for the rest errors are popped up. I tried the below which was from the fith_manual from CVS directory (might be old and obselete) irq.fsml: <?xml version="1.0" encoding="UTF-8" ?> <!-- $Id: fith.texi,v 1.12 2002/06/03 07:45:22 stanley Exp $ --> <!-- irq is the interrupt vector you want to intercept --> <!-- devname is the device's name that be used in request_irq() --> <!-- spurious_hertz="10" means one spurious IRQ is generated --> <!-- per 10 timer clicks --> <!-- delay_hertz="10" means delay one IRQ per 10 times --> <!-- delay_time="3" means the IRQ will be delayed 3 timer clicks --> <fake_irq irq="4" modname=”fith_dummy” devname="dummy" spurious_hertz="10" delay_hertz="10" delay_time="3" /> [root@xcast1hclt-ntl test]# ficl -i irq1.fsml Inserting irq1.fsml into fi_dm... Document of the wrong type, FSML Namespace not found! Can not parser out faultset from this file. But this fsml file could be inserted using ficl command. I guess the IRQ interceptor should be given inside the TRIGGER tag... I tried that, but in vain (The ficl_cmd.c handles only the parameters for the PF interceptor) I tried to "bk pull" to get the latest "fith tool", but there was no updation.... I just want to clarify whether there is a workaround for this or I should update the ficl_cmd.c to handle the IRQ interceptor parsing... Please pass on any document (if available) about this... Thanks -arun |
|
From: Wang, S. <sta...@in...> - 2003-04-10 09:54:01
|
There is another way to capture the pci configuration access indeed. We can capture the sequential access to 0xcf8 and 0xcfc instead of place a probe in the kernel. You can get the example @ http://easynews.dl.sourceforge.net/sourceforge/fault-injection/mock_e100.tgz Best Regards, Stan > -----Original Message----- > From: Fumitake ABE [mailto:ab...@jp...] > Sent: 2003-04-10 17:28 > To: fau...@li... > Subject: [Fault-injection-developer] [RFC][PATCH] PCI > configuration interceptor patch (ficl, fsml) > > > Dear All: > > This mail appends two files: a test faultset file (pcitest.fsml) and > a patch to ficl implementing a function to use a pci configuration > access interceptor (ficl_pci.patch). > > Pci configuration access interceptor can be used by the following: > 1. apply patches to kernel and ficl > 2. install the kernel, modules and ficl > 3. attach kprobe to a pci configuration access > (ficl -p /boot/System.map,/usr/src/linux/vmlinux) > 4. add a trigger (ficl -i pcitest.fsml) > 5. access a pci configuration register (e.g. lspci -xx) > > Ficl needs a System.map path and a unzipped kernel file path for > attaching kprobe to a pci configuration interceptor. I think that it > may be ugly, but I couldn't come up with a better idea than it. > Please comment. > > Sincerely, > > Fumitake ABE > ab...@jp... > |
|
From: Fumitake A. <ab...@jp...> - 2003-04-10 09:28:00
|
Dear All: This mail appends two files: a test faultset file (pcitest.fsml) and a patch to ficl implementing a function to use a pci configuration access interceptor (ficl_pci.patch). Pci configuration access interceptor can be used by the following: 1. apply patches to kernel and ficl 2. install the kernel, modules and ficl 3. attach kprobe to a pci configuration access (ficl -p /boot/System.map,/usr/src/linux/vmlinux) 4. add a trigger (ficl -i pcitest.fsml) 5. access a pci configuration register (e.g. lspci -xx) Ficl needs a System.map path and a unzipped kernel file path for attaching kprobe to a pci configuration interceptor. I think that it may be ugly, but I couldn't come up with a better idea than it. Please comment. Sincerely, Fumitake ABE ab...@jp... |
|
From: Fumitake A. <ab...@jp...> - 2003-04-10 09:27:35
|
Dear All:
Hello. My name is Fumitake ABE. I'm co-worker of Yasunori Goto.
Please forgive him for not writing in a long time.
We have implemented a pci configuration interceptor. We try to attach
kprobe to wrappers for all pci configuration access functions. And more
specifically, the address attached kprobe is as follows:
[drivers/pci/access.c]
22 #define PCI_OP_READ(size,type,len) \
23 int pci_bus_read_config_##size \
24 (struct pci_bus *bus, unsigned int devfn, int pos, type *value) \
25 { \
26 int res; \
27 unsigned long flags; \
28 u32 data = 0; \
29 if (PCI_##size##_BAD) return PCIBIOS_BAD_REGISTER_NUMBER; \
30 spin_lock_irqsave(&pci_lock, flags); \
31 res = bus->ops->read(bus, devfn, pos, len, &data); \
kprobe =>
32 *value = (type)data; \
33 spin_unlock_irqrestore(&pci_lock, flags); \
34 return res; \
35 }
36
37 #define PCI_OP_WRITE(size,type,len) \
38 int pci_bus_write_config_##size \
39 (struct pci_bus *bus, unsigned int devfn, int pos, type value) \
40 { \
41 int res; \
42 unsigned long flags; \
43 if (PCI_##size##_BAD) return PCIBIOS_BAD_REGISTER_NUMBER; \
44 spin_lock_irqsave(&pci_lock, flags); \
kprobe =>
45 res = bus->ops->write(bus, devfn, pos, len, value); \
46 spin_unlock_irqrestore(&pci_lock, flags); \
47 return res; \
48 }
I send another mail written how to use and attached utility patch. Please read
also it.
Regards,
Fumitake ABE
ab...@jp...
===
diff -urN linux-2.5.58-fith/arch/i386/Kconfig linux-2.5.58-fith-pci/arch/i386/Kconfig
--- linux-2.5.58-fith/arch/i386/Kconfig 2003-04-07 10:27:21.000000000 +0900
+++ linux-2.5.58-fith-pci/arch/i386/Kconfig 2003-04-07 10:29:13.000000000 +0900
@@ -1656,6 +1656,12 @@
If in doubt, say N.
+config FI_PCI
+ tristate "Fault injection PCI Interceptor (EXPERIMENTAL)"
+ depends on FI
+ help
+ This component adds the ability for Fault Injection to intercept
+ PCI Configuration register access.
config FI_INTERNEL_TESTING
bool "Fault Injection Internel Test Components (EXPERIMENTAL)"
diff -urN linux-2.5.58-fith/drivers/fi/fi_core.c linux-2.5.58-fith-pci/drivers/fi/fi_core.c
--- linux-2.5.58-fith/drivers/fi/fi_core.c 2003-04-07 10:27:17.000000000 +0900
+++ linux-2.5.58-fith-pci/drivers/fi/fi_core.c 2003-04-07 10:29:05.000000000 +0900
@@ -132,6 +132,7 @@
static struct trigger_attribute trigger_attr_operand;
static struct trigger_attribute trigger_attr_count;
static struct trigger_attribute trigger_attr_intcpt;
+static struct trigger_attribute trigger_attr_pci;
static inline void create_trigger_files(struct trigger *t)
{
@@ -147,6 +148,7 @@
sysfs_create_file(&t->kobj, &trigger_attr_operand.attr);
sysfs_create_file(&t->kobj, &trigger_attr_count.attr);
sysfs_create_file(&t->kobj, &trigger_attr_intcpt.attr);
+ sysfs_create_file(&t->kobj, &trigger_attr_pci.attr);
}
static inline void remove_trigger_files(struct trigger *t)
@@ -163,6 +165,7 @@
sysfs_remove_file(&t->kobj, &trigger_attr_operand.attr);
sysfs_remove_file(&t->kobj, &trigger_attr_count.attr);
sysfs_remove_file(&t->kobj, &trigger_attr_intcpt.attr);
+ sysfs_remove_file(&t->kobj, &trigger_attr_pci.attr);
}
static inline void unarm_trigger(struct trigger *t)
@@ -213,6 +216,10 @@
n->hertz = t->hertz;
n->opcode = t->opcode;
n->operand = t->operand;
+ n->pci.bus = t->pci.bus;
+ n->pci.slot = t->pci.slot;
+ n->pci.func = t->pci.func;
+ n->pci.reg_no = t->pci.reg_no;
atomic_set(&n->count, 0);
if (kobject_register(&n->kobj)) {
@@ -524,6 +531,20 @@
.show = trigger_opcode_read,
};
+static ssize_t trigger_pci_read(struct trigger * p, char * page)
+{
+ dbg("pci.bus = %#x, pci.slot = %#x, pci.func = %#x, pci.reg_no = %#x",
+ p->pci.bus, p->pci.slot, p->pci.func, p->pci.reg_no);
+ return sprintf(page,
+ "pci.bus = %#x, pci.slot = %#x, pci.func = %#x, pci.reg_no = %#x\n",
+ p->pci.bus, p->pci.slot, p->pci.func, p->pci.reg_no);
+}
+
+static struct trigger_attribute trigger_attr_pci = {
+ .attr = { .name = "pci", .mode = S_IRUGO },
+ .show = trigger_pci_read,
+};
+
static ssize_t trigger_operand_read(struct trigger * p, char * page)
{
dbg("operand = %i", p->operand);
@@ -553,9 +574,9 @@
int ret = 0;
struct trigger tmp;
- /* 3 4 5 6 7 8 9 10 11 12 13 14 16 17 */
- /* ctl nm ic wa wb bm mn mx sk st pt hz oc oa */
- num = sscanf( page, "%15s %s %s %lx %x %x %i %i %i %i %x %i %i %x",
+ /* 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20*/
+ /* ctl nm ic wa wb bm mn mx sk st pt hz bs sl fc rn oc oa*/
+ num = sscanf( page, "%15s %s %s %lx %x %x %i %i %i %i %x %i %x %x %x %x %i %x",
ctl, /* 3 */
tmp.kobj.name, /* 4 */
intcpt, /* 5 */
@@ -568,15 +589,20 @@
&tmp.stop, /* 12 */
&tmp.protection, /* 13 */
&tmp.hertz, /* 14 */
- (int *)&tmp.opcode, /* 15 */
- &tmp.operand); /* 16 */
+ &tmp.pci.bus, /* 15 */
+ &tmp.pci.slot, /* 16 */
+ &tmp.pci.func, /* 17 */
+ &tmp.pci.reg_no, /* 18 */
+ (int *)&tmp.opcode, /* 19 */
+ &tmp.operand); /* 20 */
+
if (!num) {
err("Invalid command format, translated no commands");
ret = -EINVAL;
goto Done;
}
- if (!strcmp(ctl,"add") && num == 14) {
+ if (!strcmp(ctl,"add") && (num == 18)) {
dbg("intcpt = '%s'", intcpt);
ret = add_trigger(&tmp, intcpt);
} else if (!strcmp(ctl,"del") && num == 2) {
diff -urN linux-2.5.58-fith/drivers/fi/interceptors/Makefile linux-2.5.58-fith-pci/drivers/fi/interceptors/Makefile
--- linux-2.5.58-fith/drivers/fi/interceptors/Makefile 2003-04-07 10:27:17.000000000 +0900
+++ linux-2.5.58-fith-pci/drivers/fi/interceptors/Makefile 2003-04-07 10:29:05.000000000 +0900
@@ -7,3 +7,4 @@
obj-$(CONFIG_FI_IRQ) += fi_irq.o
obj-$(CONFIG_FI_DBP) += dbp/
obj-$(CONFIG_FI_PF) += pf/
+obj-$(CONFIG_FI_PCI) += pci/
diff -urN linux-2.5.58-fith/drivers/fi/interceptors/pci/Makefile linux-2.5.58-fith-pci/drivers/fi/interceptors/pci/Makefile
--- linux-2.5.58-fith/drivers/fi/interceptors/pci/Makefile 1970-01-01 09:00:00.000000000 +0900
+++ linux-2.5.58-fith-pci/drivers/fi/interceptors/pci/Makefile 2003-04-07 10:29:05.000000000 +0900
@@ -0,0 +1,9 @@
+#
+# Makefile for the linux kernel.
+#
+export-objs = fi_pci.o
+
+obj-$(CONFIG_FI_PCI) += fi_pci.o
+
+
+EXTRA_AFLAGS := -traditional
diff -urN linux-2.5.58-fith/drivers/fi/interceptors/pci/fi_pci.c linux-2.5.58-fith-pci/drivers/fi/interceptors/pci/fi_pci.c
--- linux-2.5.58-fith/drivers/fi/interceptors/pci/fi_pci.c 1970-01-01 09:00:00.000000000 +0900
+++ linux-2.5.58-fith-pci/drivers/fi/interceptors/pci/fi_pci.c 2003-04-07 10:29:05.000000000 +0900
@@ -0,0 +1,387 @@
+/*
+ * fi_pci.c - pci configuration register access interceptor
+ *
+ * Copyright (C) FUJITSU LIMITED, 2003
+ *
+ * This program is free software; you can redistribute it and/or modify
+ * it under the terms of the GNU General Public License as published by
+ * the Free Software Foundation; either version 2 of the License, or
+ * (at your option) any later version.
+ *
+ * This program is distributed in the hope that it will be useful,
+ * but WITHOUT ANY WARRANTY; without even the implied warranty of
+ * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
+ * GNU General Public License for more details.
+ *
+ * You should have received a copy of the GNU General Public License
+ * along with this program; if not, write to the Free Software
+ * Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
+ */
+
+#include <linux/config.h>
+#include <linux/version.h>
+#include <linux/init.h>
+#include <linux/module.h>
+#include <linux/types.h>
+#include <linux/errno.h>
+#include <asm/processor.h>
+#include <linux/pci.h>
+#include <linux/list.h>
+#include <linux/kprobes.h>
+
+#include <linux/fi.h>
+
+#define PP_READ 0
+#define PP_WRITE 1
+
+/* write == 1 : read == 0 : others == -1 */
+#define PCIITC_WR_CHK(type) (type&0x10) ? 1 : (type&0x08) ? 0 : -1
+
+struct corrupt {
+ unsigned long *preg;
+ unsigned long mask;
+};
+
+struct pci_conf_access {
+ struct list_head list;
+ struct trigger *trigger;
+ unsigned int bus;
+ unsigned int slot;
+ unsigned int func;
+ unsigned int reg_no;
+ unsigned int type;
+};
+
+struct inst_pci {
+ struct list_head list;
+ struct kprobe kpb;
+ int write;
+};
+
+static DECLARE_MUTEX(pci_sem);
+static LIST_HEAD(pci_conf_acc_head);
+static LIST_HEAD(inst_pci_head);
+static struct interceptor pci_interceptor;
+
+/*
+ * Find inst_pci by addr
+ */
+static inline struct inst_pci *
+find_inst_by_addr(void *addr)
+{
+ struct inst_pci *inst;
+
+ list_for_each_entry(inst, &inst_pci_head, list) {
+ if(inst->kpb.addr == (kprobe_opcode_t *)addr) {
+ return inst;
+ }
+ }
+ return 0;
+}
+
+/*
+ * Arm trigger
+ */
+static int
+pciitc_arm(struct trigger *t)
+{
+ struct pci_conf_access *pca;
+
+ if( !is_PCI(t->wp.type) ) {
+ err("Isn't PCI configuration register access");
+ return -EINVAL;
+ }
+ if( t->pci.bus > 255 ) {
+ err("invalid bus number - %d", t->pci.bus);
+ return -EINVAL;
+ }
+ if( t->pci.slot > 31 ) {
+ err("invalid device number - %d", t->pci.slot);
+ return -EINVAL;
+ }
+ if( t->pci.func > 7 ) {
+ err("invalid function number - %d", t->pci.func);
+ return -EINVAL;
+ }
+ if( t->pci.reg_no > 255 ) {
+ err("invalid register address - %d", t->pci.reg_no);
+ return -EINVAL;
+ }
+
+ list_for_each_entry( pca, &pci_conf_acc_head, list ) {
+ if( pca->bus == t->pci.bus && pca->slot == t->pci.slot &&
+ pca->func == t->pci.func && pca->reg_no == t->pci.reg_no &&
+ pca->type == t->wp.type) {
+ err("same attribute already exists");
+ return -EINVAL;
+ }
+ }
+
+ pca = (struct pci_conf_access *)kmalloc(sizeof(struct pci_conf_access), GFP_KERNEL);
+ if(!pca) {
+ err("Allocate memory failed");
+ return -ENOMEM;
+ }
+
+ pca->bus = t->pci.bus;
+ pca->slot = t->pci.slot;
+ pca->func = t->pci.func;
+ pca->reg_no = t->pci.reg_no;
+
+ pca->type = t->wp.type;
+
+ pca->trigger = t;
+
+ list_add(&pca->list, &pci_conf_acc_head);
+
+ return 0;
+}
+
+/*
+ * Disarm trigger
+ */
+void
+pciitc_disarm(struct trigger *t)
+{
+ struct pci_conf_access *pca;
+
+ list_for_each_entry( pca, &pci_conf_acc_head, list ) {
+ if( pca->bus == t->pci.bus && pca->slot == t->pci.slot &&
+ pca->func == t->pci.func && pca->reg_no == t->pci.reg_no &&
+ pca->type == t->wp.type ) {
+ list_del(&pca->list);
+ kfree(pca);
+ }
+ }
+}
+
+/*
+ * Corrupt - called by fi_execute_trigger
+ */
+void
+pciitc_corrupt(__u32 dirty, void *data)
+{
+ unsigned long mask = ((struct corrupt *)data)->mask;
+ *(((struct corrupt *)data)->preg) &= ~mask;
+ *(((struct corrupt *)data)->preg) |= (dirty&mask);
+ dbg("corrupt data to:%#lX", dirty&mask);
+ return;
+}
+
+/*
+ * Handler
+ */
+void
+pciitc_pre_handler(struct kprobe *kprobe, struct pt_regs *regs)
+{
+ int len;
+ int bus;
+ int slot;
+ int func;
+ int reg_no;
+ unsigned int origin;
+ struct corrupt crpt;
+ struct pci_conf_access *pca;
+ struct inst_pci *inst;
+ struct pci_bus *pbus;
+
+ pbus = *(struct pci_bus **)(®s->esp);
+
+ bus = pbus->number;
+ slot = PCI_SLOT(*(unsigned int *)(®s->esp+1));
+ func = PCI_FUNC(*(unsigned int *)(®s->esp+1));
+ reg_no = *(int *)(®s->esp+2);
+ len = *(int *)(®s->esp+3);
+
+ /* dbg("[%02x:%02x.%02x] %02x - %d", bus, slot, func, reg_no, len); */
+
+ inst = find_inst_by_addr(kprobe->addr);
+ if(!inst) {
+ goto exit;
+ }
+
+ list_for_each_entry( pca, &pci_conf_acc_head, list ) {
+ if( pca->bus == bus && pca->slot == slot &&
+ pca->func == func && pca->reg_no == reg_no &&
+ (PCIITC_WR_CHK(pca->type)) == inst->write ) {
+ break;
+ }
+ }
+
+ if(&pca->list == &pci_conf_acc_head) goto exit;
+
+ switch(len) {
+ case 1:
+ crpt.mask = 0xFF;
+ break;
+ case 2:
+ crpt.mask = 0xFFFF;
+ break;
+ case 4:
+ crpt.mask = 0xFFFFFFFF;
+ break;
+ default:
+ err("Wrong length - %d", len);
+ goto exit;
+ }
+
+ crpt.preg = *(unsigned long **)(®s->esp+4);
+ origin = **(unsigned int **)(®s->esp+4) & crpt.mask;
+
+ fi_execute_trigger( pca->trigger, &pci_interceptor, origin, len, inst->write, &crpt );
+
+ exit:
+ return;
+}
+
+/*
+ * set kprobes
+ */
+int
+pciitc_insert(const char *page)
+{
+ char tmp[16];
+ int num=0;
+ int write=-1;
+ unsigned long addr=0;
+ struct inst_pci *inst;
+
+ num = sscanf(page, "%15s %i %lx", tmp, &write, &addr);
+ if (num != 3) {
+ err("Invalid command format, translated no commands");
+ return -EINVAL;
+ }
+ if (write!=PP_WRITE && write!=PP_READ) {
+ err("Invalid command format, not evaluate write/read");
+ return -EINVAL;
+ }
+
+ inst = (struct inst_pci *)kmalloc(sizeof(struct inst_pci *), GFP_KERNEL);
+ if(!inst) {
+ err("Allocate memory failed");
+ return -ENOMEM;
+ }
+
+ inst->kpb.addr = (kprobe_opcode_t *)addr;
+ inst->kpb.pre_handler = pciitc_pre_handler;
+ inst->kpb.post_handler = NULL;
+ inst->kpb.fault_handler = NULL;
+
+ if( register_kprobe(&inst->kpb) < 0 ) {
+ kfree(inst);
+ err("register_kprobe failed");
+ return -EINVAL;
+ }
+
+ inst->write = write;
+
+ list_add(&inst->list, &inst_pci_head);
+ return 0;
+}
+
+/*
+ * unset kprobes
+ */
+void
+pciitc_delete(void)
+{
+ struct inst_pci *inst;
+
+ while(!list_empty(&inst_pci_head)) {
+ inst = list_entry(inst_pci_head.next, struct inst_pci, list);
+ list_del(&inst->list);
+ unregister_kprobe(&inst->kpb);
+ kfree(inst);
+ }
+}
+
+/*
+ * show : cat /sys/fi/interceptor/pci/ctl
+ */
+static ssize_t
+ctl_show(struct interceptor *p, char *page)
+{
+ return 0;
+}
+
+/*
+ * store : echo "..." > /sys/fi/interceptor/pci/ctl
+ */
+static ssize_t
+ctl_store(struct interceptor *p, const char *page, size_t count)
+{
+ char ctl[16];
+ int num;
+ int error = 0;
+
+ num = sscanf(page, "%15s", ctl);
+
+ if(!num) {
+ err("Invalid command format, translated no commands");
+ error = -EINVAL;
+ return error;
+ }
+
+ down(&pci_sem);
+ if(!strncmp(ctl, "add", 3)) {
+ error = pciitc_insert(page);
+ } else if(!strncmp(ctl, "clear", 5)) {
+ pciitc_delete();
+ } else {
+ err("Unknown command %s", page);
+ error = -EINVAL;
+ }
+ up(&pci_sem);
+
+ return error ? error : count;
+}
+
+static struct interceptor_attribute attr_ctl = {
+ .attr = { .name = "ctl", .mode = 0644 },
+ .show = ctl_show,
+ .store = ctl_store
+};
+
+static struct interceptor pci_interceptor = {
+ .kobj = { .name = "pci" },
+ .arm = pciitc_arm,
+ .disarm = pciitc_disarm,
+ .corrupt = pciitc_corrupt
+};
+
+/*
+ * module init
+ */
+static int __init
+pciitc_start(void)
+{
+ if(fi_register_interceptor(&pci_interceptor)) {
+ dbg("Failed to register DBP Interceptor");
+ return -EINVAL;
+ }
+
+ sysfs_create_file(&pci_interceptor.kobj, &attr_ctl.attr);
+
+ EXPORT_NO_SYMBOLS;
+
+ return 0;
+}
+
+/*
+ * module exit
+ */
+static void __exit
+pciitc_stop(void)
+{
+ pciitc_delete();
+ sysfs_remove_file(&pci_interceptor.kobj, &attr_ctl.attr);
+ fi_unregister_interceptor(&pci_interceptor);
+ return;
+}
+
+module_init(pciitc_start);
+module_exit(pciitc_stop);
+
+MODULE_AUTHOR("Yasunori GOTO");
+MODULE_DESCRIPTION("PCI conf interceptor for FI.");
+MODULE_LICENSE("GPL");
diff -urN linux-2.5.58-fith/include/linux/fi.h linux-2.5.58-fith-pci/include/linux/fi.h
--- linux-2.5.58-fith/include/linux/fi.h 2003-04-07 10:27:19.000000000 +0900
+++ linux-2.5.58-fith-pci/include/linux/fi.h 2003-04-07 10:29:08.000000000 +0900
@@ -11,6 +11,7 @@
#define FI_WPTYPE_READ 8
#define FI_WPTYPE_WRITE 16
#define FI_WPTYPE_EXEC 32
+#define FI_WPTYPE_PCI 64
#define FI_WPTYPE_LEN_MASK 3
#define FI_WPTYPE_ALL_MASK ( FI_WPTYPE_MMIO \
@@ -34,6 +35,16 @@
unsigned int type;
};
+/**
+ * define pci configuration register access structure.
+ */
+struct pci_conf_reg {
+ int bus;
+ int slot;
+ int func;
+ int reg_no;
+};
+
#define WP_LEN(wp) (1<<((unsigned long)(wp.type)&3))
typedef enum
{
@@ -76,6 +87,10 @@
struct list_head cs_list;
struct interceptor *intcpt;
atomic_t count;
+
+ /* pci configuration register */
+ struct pci_conf_reg pci;
+
/* opaque data struct for register */
void *data;
struct kobject kobj;
@@ -152,6 +167,7 @@
inline static int is_read(int type) { return (type&0x08)?1:0; };
inline static int is_write(int type) { return (type&0x10)?1:0; };
inline static int is_execute(int type) { return (type&0x20)?1:0; };
+inline static int is_PCI(int type) { return (type&0x40)?1:0; };
inline static int access_len(int type) { return 1UL<<(type&0x03);};
#endif /* _FAULT_INJECTION_H */
|
|
From: Gao, K. <kev...@in...> - 2003-04-10 00:59:01
|
OK, here is the description of most important e100 test codes.
chg_tcb_co_00 //Set both 'c' and 'ok' bit of TCB to 0
//when driver reads SCB status register.
chg_tcb_co_01 //Set 'c' bit to 0, and 'ok' bit to 1
//when driver reads SCB status register.
chg_tcb_co_10 //Set 'c' bit to 1, and 'ok' bit to 0
//when driver reads SCB status register.
chg_tcb_u //Set 'u' bit of TCB to 1, when driver reads
//SCB status register.
link-down.fsml //Simulate plug in and out network cable.
set_tcb_co_01 //Set 'c' bit to 0, and 'ok' bit to 1 when driver=20
//writes CU_RESUME to SCB command register.
set_tcb_co_10 //Set 'c' bit to 1, and 'ok' bit to 0 when driver
//writes CU_RESUME to SCB command register.
set_tcb_co_11 //Set both 'c' and 'ok' bit of TCB to 1 when
//driver writes CU_RESUME to SCB command register.
set_tcb_i //Set 'i' bit of TCB to 1 when driver writes
//CU_RESUME to SCB command register.
set_tcb_u //Set 'u' bit of TCB to 1 when driver writes
//CU_RESUME to SCB command register.
set_rfd_align //Set 'align' bit of RFD to 1 when driver reads
//SCB status register. (A receve package int is received)
set_rfd_co_00 //Set both 'c' and 'ok' bit of RFD to 0 when
//driver reads SCB status register.
set_rfd_co_01 //Set 'c' to 0, and 'ok' to 1 when driver reads
//SCB status register.
set_rfd_co_10 //Set 'c' to 1, and 'ok' to 0 when driver reads
//SCB status register.
set_rfd_crc //Set 'crc' bit of RFD to 1 when driver reads=20
//SCB status register.
set_rfd_fts //Set 'Frame too short' bit of RFD to 1 when
//driver reads SCB status register.
set_rfd_roob //Set 'Ran out of buffer space' bit of RFD to 1
//when driver reads SCB status register.
set_rfd_s //Set 's' bit of RFD to 1 when driver reads SCB
//status register.
Other test suite is only capture and change CSR register, they
are very simple.
Thanks
-Kevin
-----Original Message-----
From: arun [mailto:ar...@np...]=20
Sent: 2003?4?9? 11:21
To: Gao, Kevin
Cc: fau...@li...
Subject: Re: [Fault-injection-developer] fith
Hi Kevin,=20
Trying to identify test cases which can be tested using the fith =
tool... It will be=20
helpful as a reference , if there is a descriptive test cases written =
for e100 driver=20
(for wich the scripts are available in fault_set/e100 dir)... If any =
such test-case=20
document is available, please pass on...=20
Thanks=20
-arun=20
"Gao, Kevin" wrote:=20
Hi Arun, I want to know whether you do the following task before =
using ficl tools. 1. mount the sysfs to directory "/sys" 2. Before =
you run "ficl -i scb_cu_resume.fsml " The scb_cu_resume.ko should be =
inserted which contains the codesegment used by test fsml file.-Kevin =
-----Original Message-----=20
From: Arun Prasad [mailto:ar...@ne...]=20
Sent: 2003?3?20? 15:03=20
To: Gao, Kevin=20
Cc: fau...@li...=20
Subject: Re: [Fault-injection-developer] fith=20
=20
Hi Kevin,=20
I got some problems when I use the FICL command to insert the fsml =
script... Below I have pasted the info about it...=20
=20
Did the following fix to compile the FITH_UTILITY....=20
ficl/Makefile:=20
<<LDFLAGS =3D=20
>> LDFLAGS =3D$(AM_LDFLAGS)=20
Without the above fix, bfd is not linked and was getting link errors=20
ficl_cmd.c:=20
696 // dirp =3D opendir(TRIGGER_PATH); (commented this line)=20
697 struct dirent *dp;=20
698 int fd =3D 0;=20
699 char cmd[128];=20
700=20
701 dirp =3D opendir(TRIGGER_PATH); (Added this line)=20
********************************************************=20
The Below is the error I get when trying to insert the fsml script using =
ficl command according to your instructions in the previous mail....=20
[root@xcast1hclt-ntl e100]# lsmod=20
Module Size Used by=20
e100 60900 0=20
fi_pf 4672 0=20
fi_core 6176 1 fi_pf=20
eepro100 21964 1=20
mii 2592 1 eepro100=20
autofs 8960 0=20
parport_pc 19620 0 [unsafe]=20
parport 23296 1 parport_pc,[unsafe]=20
[root@xcast1hclt-ntl e100]# uname -a=20
Linux xcast1hclt-ntl.co.in 2.5.63 #5 Thu Mar 20 11:52:09 IST 2003 i686 =
unknown=20
[root@xcast1hclt-ntl e100]# pwd=20
/home/arun/bkt/fith/fith_test/fault_set/e100=20
[root@xcast1hclt-ntl e100]# ficl -i scb_cu_resume.fsml=20
Inserting scb_cu_resume.fsml into fi_dm...=20
Can not open /sys/fi/trigger/ctl.=20
Can not open /sys/fi/code_segment/scb_cu_resume/ctl.=20
=20
=20
Thanks again=20
-arun=20
=20
=20
=20
"Gao, Kevin" wrote:=20
The tree linux-2.5 is out of date.=20
So please dowload the newest tree at=20
http://fau...@fa.../2.5-fi-extern=20
The new tree includes all interceptors.=20
The usage of FITH_TOOL is as follow.=20
We still use tools "ficl"=20
You can use parameters as follow:=20
--attach, -a <modname,file_path>=20
attach a module into dbp.=20
--detach, -d=20
detach all modules that attached to dbp.=20
--insert, -i <file.fsml>=20
insert a faultset written in file.fsml into FITH.=20
--remove, -r {file.fsml|all}=20
remove the faultset written in file.fsml or all faultset.=20
--help, -h=20
help information.=20
thanks=20
-Kevin=20
-----Original Message-----=20
From: Arun Prasad [mailto:ar...@ne...]=20
Sent: 2003?3?18? 17:17=20
To: fau...@li...=20
Subject: [Fault-injection-developer] fith=20
Hi All,=20
To use the fith tool, downloaded the Bitkeeper tool and=20
cloned the=20
below repositories...=20
* fith-tool=20
* linux-2.5=20
both from fault-injection project.=20
Now I have to compile and load the "linux-2.5" (above) and=20
install=20
"fith-tool" on it... Is my assumption right... Because I=20
could see=20
"2.5-kprobes" in the list of repositories which is again a=20
kernel tree....=20
It will be helpful if we know the significance of each=20
repository..=20
Please clarify this....=20
Is there any upto date manual to describe the ficl commands=20
and for=20
general usage of the tool....=20
Thanks=20
-arun=20
-------------------------------------------------------=20
This SF.net email is sponsored by: Does your code think in ink?=20
You could win a Tablet PC. Get a free Tablet PC hat just for playing.=20
What are you waiting for?=20
http://ads.sourceforge.net/cgi-bin/redirect.pl?micr5043en=20
_______________________________________________=20
Fault-injection-developer mailing list=20
Fau...@li...=20
https://lists.sourceforge.net/lists/listinfo/fault-injection-developer=20
-------------------------------------------------------=20
This SF.net email is sponsored by: Does your code think in ink?=20
You could win a Tablet PC. Get a free Tablet PC hat just for playing.=20
What are you waiting for?=20
http://ads.sourceforge.net/cgi-bin/redirect.pl?micr5043en=20
_______________________________________________=20
Fault-injection-developer mailing list=20
Fau...@li...=20
https://lists.sourceforge.net/lists/listinfo/fault-injection-developer
|
|
From: arun <ar...@np...> - 2003-04-09 03:23:16
|
Hi Kevin,
Trying to identify test cases which can be tested using the fith
tool... It will be
helpful as a reference , if there is a descriptive test cases written
for e100 driver
(for wich the scripts are available in fault_set/e100 dir)... If any
such test-case
document is available, please pass on...
Thanks
-arun
"Gao, Kevin" wrote:
> Hi Arun, I want to know whether you do the following task before
> using ficl tools. 1. mount the sysfs to directory "/sys" 2.
> Before you run "ficl -i scb_cu_resume.fsml " The scb_cu_resume.ko
> should be inserted which contains the codesegment used by test fsml
> file.-Kevin
>
> -----Original Message-----
> From: Arun Prasad [mailto:ar...@ne...]
> Sent: 2003?3?20? 15:03
> To: Gao, Kevin
> Cc: fau...@li...
> Subject: Re: [Fault-injection-developer] fith
>
> Hi Kevin,
> I got some problems when I use the FICL command to
> insert the fsml script... Below I have pasted the info
> about it...
>
>
> Did the following fix to compile the FITH_UTILITY....
>
> ficl/Makefile:
> <<LDFLAGS =
> >> LDFLAGS =$(AM_LDFLAGS)
> Without the above fix, bfd is not linked and was getting
> link errors
>
> ficl_cmd.c:
> 696 // dirp = opendir(TRIGGER_PATH); (commented this
> line)
> 697 struct dirent *dp;
> 698 int fd = 0;
> 699 char cmd[128];
> 700
> 701 dirp = opendir(TRIGGER_PATH); (Added this line)
>
> ********************************************************
>
> The Below is the error I get when trying to insert the fsml
> script using ficl command according to your instructions in
> the previous mail....
>
> [root@xcast1hclt-ntl e100]# lsmod
> Module Size Used by
> e100 60900 0
> fi_pf 4672 0
> fi_core 6176 1 fi_pf
> eepro100 21964 1
> mii 2592 1 eepro100
> autofs 8960 0
> parport_pc 19620 0 [unsafe]
> parport 23296 1 parport_pc,[unsafe]
>
> [root@xcast1hclt-ntl e100]# uname -a
> Linux xcast1hclt-ntl.co.in 2.5.63 #5 Thu Mar 20 11:52:09 IST
> 2003 i686 unknown
>
> [root@xcast1hclt-ntl e100]# pwd
> /home/arun/bkt/fith/fith_test/fault_set/e100
>
> [root@xcast1hclt-ntl e100]# ficl -i scb_cu_resume.fsml
> Inserting scb_cu_resume.fsml into fi_dm...
> Can not open /sys/fi/trigger/ctl.
> Can not open /sys/fi/code_segment/scb_cu_resume/ctl.
>
>
>
> Thanks again
> -arun
>
>
>
>
> "Gao, Kevin" wrote:
>
> > The tree linux-2.5 is out of date.
> > So please dowload the newest tree at
> > http://fault-injection@fault-injecti
> > n.bkbits.net/2.5-fi-extern
> > The new tree includes all interceptors.
> >
> > The usage of FITH_TOOL is as follow.
> >
> > We still use tools "ficl"
> > You can use parameters as follow:
> >
> > --attach, -a <modname,file_path>
> > attach a module into dbp.
> > --detach, -d
> > detach all modules that attached to dbp.
> > --insert, -i <file.fsml>
> > insert a faultset written in file.fsml into FITH.
> > --remove, -r {file.fsml|all}
> > remove the faultset written in file.fsml or all
> > faultset.
> > --help, -h
> > help information.
> >
> > thanks
> > -Kevin
> >
> > -----Original Message-----
> > From: Arun Prasad [mailto:ar...@ne...]
> > Sent: 2003?3?18? 17:17
> > To: fau...@li...
> > Subject: [Fault-injection-developer] fith
> >
> > Hi All,
> > To use the fith tool, downloaded the Bitkeeper tool
> > and
> > cloned the
> > below repositories...
> > * fith-tool
> > * linux-2.5
> > both from fault-injection project.
> >
> > Now I have to compile and load the "linux-2.5" (above) and
> >
> > install
> > "fith-tool" on it... Is my assumption right... Because I
> > could see
> > "2.5-kprobes" in the list of repositories which is again a
> >
> > kernel tree....
> > It will be helpful if we know the significance of each
> > repository..
> >
> > Please clarify this....
> >
> > Is there any upto date manual to describe the ficl
> > commands
> > and for
> > general usage of the tool....
> >
> > Thanks
> > -arun
> >
> > -------------------------------------------------------
> > This SF.net email is sponsored by: Does your code think in
> > ink?
> > You could win a Tablet PC. Get a free Tablet PC hat just
> > for playing.
> > What are you waiting for?
> > http://ads.sourceforge.net/cgi-bin/redirect.pl?micr5043en
> > _______________________________________________
> > Fault-injection-developer mailing list
> > Fau...@li...
> > https://lists.sourceforge.net/lists/listinfo/fa
> > lt-injection-developer
> >
> > -------------------------------------------------------
> > This SF.net email is sponsored by: Does your code think in
> > ink?
> > You could win a Tablet PC. Get a free Tablet PC hat just
> > for playing.
> > What are you waiting for?
> > http://ads.sourceforge.net/cgi-bin/redirect.pl?micr5043en
> > _______________________________________________
> > Fault-injection-developer mailing list
> > Fau...@li...
> > https://lists.sourceforge.net/lists/listinfo/fa
> > lt-injection-developer
>
|
|
From: Arun P. <ar...@ne...> - 2003-03-20 15:11:13
|
Hi Kevin,
Mounting sysfs solved the problem... Thanks a bunch for ur help..
Thanks
-arun
"Gao, Kevin" wrote:
> Hi Arun, I want to know whether you do the following task before
> using ficl tools. 1. mount the sysfs to directory "/sys" 2.
> Before you run "ficl -i scb_cu_resume.fsml " The scb_cu_resume.ko
> should be inserted which contains the codesegment used by test fsml
> file.-Kevin
>
> -----Original Message-----
> From: Arun Prasad [mailto:ar...@ne...]
> Sent: 2003?3?20? 15:03
> To: Gao, Kevin
> Cc: fau...@li...
> Subject: Re: [Fault-injection-developer] fith
>
> Hi Kevin,
> I got some problems when I use the FICL command to
> insert the fsml script... Below I have pasted the info
> about it...
>
>
> Did the following fix to compile the FITH_UTILITY....
>
> ficl/Makefile:
> <<LDFLAGS =
> >> LDFLAGS =$(AM_LDFLAGS)
> Without the above fix, bfd is not linked and was getting
> link errors
>
> ficl_cmd.c:
> 696 // dirp = opendir(TRIGGER_PATH); (commented this
> line)
> 697 struct dirent *dp;
> 698 int fd = 0;
> 699 char cmd[128];
> 700
> 701 dirp = opendir(TRIGGER_PATH); (Added this line)
>
> ********************************************************
>
> The Below is the error I get when trying to insert the fsml
> script using ficl command according to your instructions in
> the previous mail....
>
> [root@xcast1hclt-ntl e100]# lsmod
> Module Size Used by
> e100 60900 0
> fi_pf 4672 0
> fi_core 6176 1 fi_pf
> eepro100 21964 1
> mii 2592 1 eepro100
> autofs 8960 0
> parport_pc 19620 0 [unsafe]
> parport 23296 1 parport_pc,[unsafe]
>
> [root@xcast1hclt-ntl e100]# uname -a
> Linux xcast1hclt-ntl.co.in 2.5.63 #5 Thu Mar 20 11:52:09 IST
> 2003 i686 unknown
>
> [root@xcast1hclt-ntl e100]# pwd
> /home/arun/bkt/fith/fith_test/fault_set/e100
>
> [root@xcast1hclt-ntl e100]# ficl -i scb_cu_resume.fsml
> Inserting scb_cu_resume.fsml into fi_dm...
> Can not open /sys/fi/trigger/ctl.
> Can not open /sys/fi/code_segment/scb_cu_resume/ctl.
>
>
>
> Thanks again
> -arun
>
>
>
>
> "Gao, Kevin" wrote:
>
> > The tree linux-2.5 is out of date.
> > So please dowload the newest tree at
> > http://fault-injection@fault-injecti
> > n.bkbits.net/2.5-fi-extern
> > The new tree includes all interceptors.
> >
> > The usage of FITH_TOOL is as follow.
> >
> > We still use tools "ficl"
> > You can use parameters as follow:
> >
> > --attach, -a <modname,file_path>
> > attach a module into dbp.
> > --detach, -d
> > detach all modules that attached to dbp.
> > --insert, -i <file.fsml>
> > insert a faultset written in file.fsml into FITH.
> > --remove, -r {file.fsml|all}
> > remove the faultset written in file.fsml or all
> > faultset.
> > --help, -h
> > help information.
> >
> > thanks
> > -Kevin
> >
> > -----Original Message-----
> > From: Arun Prasad [mailto:ar...@ne...]
> > Sent: 2003?3?18? 17:17
> > To: fau...@li...
> > Subject: [Fault-injection-developer] fith
> >
> > Hi All,
> > To use the fith tool, downloaded the Bitkeeper tool
> > and
> > cloned the
> > below repositories...
> > * fith-tool
> > * linux-2.5
> > both from fault-injection project.
> >
> > Now I have to compile and load the "linux-2.5" (above) and
> >
> > install
> > "fith-tool" on it... Is my assumption right... Because I
> > could see
> > "2.5-kprobes" in the list of repositories which is again a
> >
> > kernel tree....
> > It will be helpful if we know the significance of each
> > repository..
> >
> > Please clarify this....
> >
> > Is there any upto date manual to describe the ficl
> > commands
> > and for
> > general usage of the tool....
> >
> > Thanks
> > -arun
> >
> > -------------------------------------------------------
> > This SF.net email is sponsored by: Does your code think in
> > ink?
> > You could win a Tablet PC. Get a free Tablet PC hat just
> > for playing.
> > What are you waiting for?
> > http://ads.sourceforge.net/cgi-bin/redirect.pl?micr5043en
> > _______________________________________________
> > Fault-injection-developer mailing list
> > Fau...@li...
> > https://lists.sourceforge.net/lists/listinfo/fa
> > lt-injection-developer
> >
> > -------------------------------------------------------
> > This SF.net email is sponsored by: Does your code think in
> > ink?
> > You could win a Tablet PC. Get a free Tablet PC hat just
> > for playing.
> > What are you waiting for?
> > http://ads.sourceforge.net/cgi-bin/redirect.pl?micr5043en
> > _______________________________________________
> > Fault-injection-developer mailing list
> > Fau...@li...
> > https://lists.sourceforge.net/lists/listinfo/fa
> > lt-injection-developer
>
|
|
From: Gao, K. <kev...@in...> - 2003-03-20 07:10:15
|
Hi Arun,
I want to know whether you do the following task before using ficl
tools.
1. mount the sysfs to directory "/sys"
2. Before you run "ficl -i scb_cu_resume.fsml "
The scb_cu_resume.ko should be inserted which contains the codesegment
used by test fsml file.
-Kevin
-----Original Message-----
From: Arun Prasad [mailto:ar...@ne...]
Sent: 2003?3?20? 15:03
To: Gao, Kevin
Cc: fau...@li...
Subject: Re: [Fault-injection-developer] fith
Hi Kevin,
I got some problems when I use the FICL command to insert the fsml
script... Below I have pasted the info about it...
Did the following fix to compile the FITH_UTILITY....
ficl/Makefile:
<<LDFLAGS =
>> LDFLAGS =$(AM_LDFLAGS)
Without the above fix, bfd is not linked and was getting link errors
ficl_cmd.c:
696 // dirp = opendir(TRIGGER_PATH); (commented this line)
697 struct dirent *dp;
698 int fd = 0;
699 char cmd[128];
700
701 dirp = opendir(TRIGGER_PATH); (Added this line)
********************************************************
The Below is the error I get when trying to insert the fsml script using
ficl command according to your instructions in the previous mail....
[root@xcast1hclt-ntl e100]# lsmod
Module Size Used by
e100 60900 0
fi_pf 4672 0
fi_core 6176 1 fi_pf
eepro100 21964 1
mii 2592 1 eepro100
autofs 8960 0
parport_pc 19620 0 [unsafe]
parport 23296 1 parport_pc,[unsafe]
[root@xcast1hclt-ntl e100]# uname -a
Linux xcast1hclt-ntl.co.in 2.5.63 #5 Thu Mar 20 11:52:09 IST 2003 i686
unknown
[root@xcast1hclt-ntl e100]# pwd
/home/arun/bkt/fith/fith_test/fault_set/e100
[root@xcast1hclt-ntl e100]# ficl -i scb_cu_resume.fsml
Inserting scb_cu_resume.fsml into fi_dm...
Can not open /sys/fi/trigger/ctl.
Can not open /sys/fi/code_segment/scb_cu_resume/ctl.
Thanks again
-arun
"Gao, Kevin" wrote:
The tree linux-2.5 is out of date.
So please dowload the newest tree at
http://fau...@fa.../2.5-fi-extern
<http://fau...@fa.../2.5-fi-extern>
The new tree includes all interceptors.
The usage of FITH_TOOL is as follow.
We still use tools "ficl"
You can use parameters as follow:
--attach, -a <modname,file_path>
attach a module into dbp.
--detach, -d
detach all modules that attached to dbp.
--insert, -i <file.fsml>
insert a faultset written in file.fsml into FITH.
--remove, -r {file.fsml|all}
remove the faultset written in file.fsml or all faultset.
--help, -h
help information.
thanks
-Kevin
-----Original Message-----
From: Arun Prasad [mailto:ar...@ne...
<mailto:ar...@ne...> ]
Sent: 2003?3?18? 17:17
To: fau...@li...
Subject: [Fault-injection-developer] fith
Hi All,
To use the fith tool, downloaded the Bitkeeper tool and
cloned the
below repositories...
* fith-tool
* linux-2.5
both from fault-injection project.
Now I have to compile and load the "linux-2.5" (above) and
install
"fith-tool" on it... Is my assumption right... Because I
could see
"2.5-kprobes" in the list of repositories which is again a
kernel tree....
It will be helpful if we know the significance of each
repository..
Please clarify this....
Is there any upto date manual to describe the ficl commands
and for
general usage of the tool....
Thanks
-arun
-------------------------------------------------------
This SF.net email is sponsored by: Does your code think in ink?
You could win a Tablet PC. Get a free Tablet PC hat just for playing.
What are you waiting for?
http://ads.sourceforge.net/cgi-bin/redirect.pl?micr5043en
<http://ads.sourceforge.net/cgi-bin/redirect.pl?micr5043en>
_______________________________________________
Fault-injection-developer mailing list
Fau...@li...
https://lists.sourceforge.net/lists/listinfo/fault-injection-developer
<https://lists.sourceforge.net/lists/listinfo/fault-injection-developer>
-------------------------------------------------------
This SF.net email is sponsored by: Does your code think in ink?
You could win a Tablet PC. Get a free Tablet PC hat just for playing.
What are you waiting for?
http://ads.sourceforge.net/cgi-bin/redirect.pl?micr5043en
<http://ads.sourceforge.net/cgi-bin/redirect.pl?micr5043en>
_______________________________________________
Fault-injection-developer mailing list
Fau...@li...
https://lists.sourceforge.net/lists/listinfo/fault-injection-developer
<https://lists.sourceforge.net/lists/listinfo/fault-injection-developer>
|
|
From: Arun P. <ar...@ne...> - 2003-03-20 07:00:37
|
Hi Kevin,
I got some problems when I use the FICL command to insert the fsml
script... Below I have pasted the info about it...
Did the following fix to compile the FITH_UTILITY....
ficl/Makefile:
<<LDFLAGS =
>> LDFLAGS =$(AM_LDFLAGS)
Without the above fix, bfd is not linked and was getting link errors
ficl_cmd.c:
696 // dirp = opendir(TRIGGER_PATH); (commented this line)
697 struct dirent *dp;
698 int fd = 0;
699 char cmd[128];
700
701 dirp = opendir(TRIGGER_PATH); (Added this line)
********************************************************
The Below is the error I get when trying to insert the fsml script using ficl
command according to your instructions in the previous mail....
[root@xcast1hclt-ntl e100]# lsmod
Module Size Used by
e100 60900 0
fi_pf 4672 0
fi_core 6176 1 fi_pf
eepro100 21964 1
mii 2592 1 eepro100
autofs 8960 0
parport_pc 19620 0 [unsafe]
parport 23296 1 parport_pc,[unsafe]
[root@xcast1hclt-ntl e100]# uname -a
Linux xcast1hclt-ntl.co.in 2.5.63 #5 Thu Mar 20 11:52:09 IST 2003 i686 unknown
[root@xcast1hclt-ntl e100]# pwd
/home/arun/bkt/fith/fith_test/fault_set/e100
[root@xcast1hclt-ntl e100]# ficl -i scb_cu_resume.fsml
Inserting scb_cu_resume.fsml into fi_dm...
Can not open /sys/fi/trigger/ctl.
Can not open /sys/fi/code_segment/scb_cu_resume/ctl.
Thanks again
-arun
"Gao, Kevin" wrote:
> The tree linux-2.5 is out of date.
> So please dowload the newest tree at
> http://fau...@fa.../2.5-fi-extern
> The new tree includes all interceptors.
>
> The usage of FITH_TOOL is as follow.
>
> We still use tools "ficl"
> You can use parameters as follow:
>
> --attach, -a <modname,file_path>
> attach a module into dbp.
> --detach, -d
> detach all modules that attached to dbp.
> --insert, -i <file.fsml>
> insert a faultset written in file.fsml into FITH.
> --remove, -r {file.fsml|all}
> remove the faultset written in file.fsml or all faultset.
> --help, -h
> help information.
>
> thanks
> -Kevin
>
> -----Original Message-----
> From: Arun Prasad [mailto:ar...@ne...]
> Sent: 2003?3?18? 17:17
> To: fau...@li...
> Subject: [Fault-injection-developer] fith
>
> Hi All,
> To use the fith tool, downloaded the Bitkeeper tool and
> cloned the
> below repositories...
> * fith-tool
> * linux-2.5
> both from fault-injection project.
>
> Now I have to compile and load the "linux-2.5" (above) and
> install
> "fith-tool" on it... Is my assumption right... Because I
> could see
> "2.5-kprobes" in the list of repositories which is again a
> kernel tree....
> It will be helpful if we know the significance of each
> repository..
>
> Please clarify this....
>
> Is there any upto date manual to describe the ficl commands
> and for
> general usage of the tool....
>
> Thanks
> -arun
>
> -------------------------------------------------------
> This SF.net email is sponsored by: Does your code think in ink?
> You could win a Tablet PC. Get a free Tablet PC hat just for playing.
> What are you waiting for?
> http://ads.sourceforge.net/cgi-bin/redirect.pl?micr5043en
> _______________________________________________
> Fault-injection-developer mailing list
> Fau...@li...
> https://lists.sourceforge.net/lists/listinfo/fault-injection-developer
>
> -------------------------------------------------------
> This SF.net email is sponsored by: Does your code think in ink?
> You could win a Tablet PC. Get a free Tablet PC hat just for playing.
> What are you waiting for?
> http://ads.sourceforge.net/cgi-bin/redirect.pl?micr5043en
> _______________________________________________
> Fault-injection-developer mailing list
> Fau...@li...
> https://lists.sourceforge.net/lists/listinfo/fault-injection-developer
|
|
From: Arun P. <ar...@ne...> - 2003-03-20 06:49:26
|
Hi Stan,
The below fix solved the kernel crash.. Now I can boot with 2.5.63....
thanks....
-arun
"Wang, Stanley" wrote:
> Could you identify the piece of codes (or module?) that caused your kernel
> panic?And you could recomple your kernel with:#
> # Kernel hacking
> #
> CONFIG_DEBUG_KERNEL=y
> CONFIG_KPROBES=y
> CONFIG_DEBUGREG=y
> CONFIG_KWATCH=y
> CONFIG_KMMIO=y
> CONFIG_KIRQ=y
> CONFIG_FI=y
> CONFIG_FI_DEBUG=y
>
> ONFIG_FI_SAMPLE_CODESEGMENT=m
> ~~~
> CONFIG_FI_PF=y
> CONFIG_FI_DR=m
> CONFIG_FI_DBP=y
> CONFIG_FI_IRQ=y
> CONFIG_FI_INTERNEL_TESTING=y
>
> ONFIG_FI_MOCK_INTERCEPTOR=m
> ~~~
>
> ONFIG_FI_MOCK_CODESEGMENT=m
> ~~~
> CONFIG_FI_TEST=m ~~Not sure, Just have a
> try.Regards,Stan
>
> -----Original Message-----
> From: Arun Prasad [mailto:ar...@ne...]
> Sent: 2003-03-20 11:39
> To: Gao, Kevin
> Cc: fau...@li...
> Subject: Re: [Fault-injection-developer] fith
>
> Hi Kevin,
> I have attatched the ".config" file.... The below are the
> commands used to compile and load the new kernel
>
> cd 2.5-linux-fi-extern
> make mrproper
> make menuconfig
> make dep
> make bzImage
> make modules
> make modules_install
> Configured lilo.conf
> lilo
>
>
> Thanks
> -arun
>
> "Gao, Kevin" wrote:
>
> > Could you please send us your kernel config information,so that
> > we can track what happens to your kernel.Thanks -Kevin
> >
> > -----Original Message-----
> > From: Arun Prasad [mailto:ar...@ne...]
> > Sent: 2003?3?19? 17:06
> > To: Gao, Kevin
> > Cc: fau...@li...
> > Subject: Re: [Fault-injection-developer] fith
> > Hi Kevin/All,
> > I downloaded 2.5-fi-extern from Bk... Compiled the
> > kernel and while booting with this new kernel, I got
> > the below panic...
> >
> > Mount-cache hash table entries: 512 (order: 0, 4096)
> > invalid operand: 0000
> > CPU: 0
> > EIP: 0060:[<C01214F2>] Not tainted
> > EFLAGS: 00010286
> > .................................
> > ..........................
> > ....................
> > ..............
> > <0> Kernel panic: Attempted to kill the idle task!
> > In Idle task -not syncing
> >
> >
> > Does somebody has faced this?? Any workaround for this
> > ??
> >
> > Thanks
> > -arun
> >
> >
> >
> > "Gao, Kevin" wrote:
> >
> > > Hi Arun,
> > >
> > > The example for e100 test cases is as folloow:
> > >
> > > insert module : fi_core, fi_pf, e100,
> > > # cd ./fith-tool/fith_test/fault_set/e100
> > > #make
> > > # insmod scb_cu_resume.ko
> > > # ficl -i scb_cu_resume.fsml (You should change
> > > the "base" parameter to
> > > your own bar address
> > > of e100).
> > > # /etc/init.d/network start
> > >
> > > Now use command dmesg to see the log info or see the
> > > message in
> > > /var/log/messages.
> > >
> > > -Kevin
> > >
> > > -----Original Message-----
> > > From: Arun Prasad [mailto:ar...@ne...]
> > > Sent: 2003?3?18? 18:12
> > > To: Gao, Kevin
> > > Cc: fau...@li...
> > > Subject: Re: [Fault-injection-developer] fith
> > >
> > > Hi Kevin,
> > > Thanks for the response... Iam in the process of
> > > downloading the
> > > 2.5-fi-extern from BK.
> > > The fault injection test cases for e100 is present
> > > along with the fith
> > > utility...That seems to be a good reference for me to
> > > start writing test
> > > cases for giga-bit ethernet card (which Iam trying to
> > > do...)... But just the
> > > fsml and the code_segments are provided for e100... I
> > > couldnt see the
> > > scripts
> > > to use them (like the demo at fith_test dir) . Is
> > > that possible to include
> > > the
> > > scripts also in the repository??
> > >
> > > Thanks
> > > -arun
> > >
> > > "Gao, Kevin" wrote:
> > >
> > > > The tree linux-2.5 is out of date.
> > > > So please dowload the newest tree at
> > > >
> > > http://fau...@fa.../2.5-fi-extern
> > >
> > > > The new tree includes all interceptors.
> > > >
> > > > The usage of FITH_TOOL is as follow.
> > > >
> > > > We still use tools "ficl"
> > > > You can use parameters as follow:
> > > >
> > > > --attach, -a <modname,file_path>
> > > > attach a module into dbp.
> > > > --detach, -d
> > > > detach all modules that attached to dbp.
> > > > --insert, -i <file.fsml>
> > > > insert a faultset written in file.fsml into
> > > FITH.
> > > > --remove, -r {file.fsml|all}
> > > > remove the faultset written in file.fsml or
> > > all faultset.
> > > > --help, -h
> > > > help information.
> > > >
> > > > thanks
> > > > -Kevin
> > > >
> > > > -----Original Message-----
> > > > From: Arun Prasad [mailto:ar...@ne...]
> > > > Sent: 2003?3?18? 17:17
> > > > To: fau...@li...
> > >
> > > > Subject: [Fault-injection-developer] fith
> > > >
> > > > Hi All,
> > > > To use the fith tool, downloaded the Bitkeeper
> > > tool and
> > > > cloned the
> > > > below repositories...
> > > > * fith-tool
> > > > * linux-2.5
> > > > both from fault-injection project.
> > > >
> > > > Now I have to compile and load the "linux-2.5"
> > > (above) and
> > > > install
> > > > "fith-tool" on it... Is my assumption right...
> > > Because I
> > > > could see
> > > > "2.5-kprobes" in the list of repositories which is
> > > again a
> > > > kernel tree....
> > > > It will be helpful if we know the significance of
> > > each
> > > > repository..
> > > >
> > > > Please clarify this....
> > > >
> > > > Is there any upto date manual to describe the ficl
> > > commands
> > > > and for
> > > > general usage of the tool....
> > > >
> > > > Thanks
> > > > -arun
> > > >
> > > >
> > > -------------------------------------------------------
> > >
> > > > This SF.net email is sponsored by: Does your code
> > > think in ink?
> > > > You could win a Tablet PC. Get a free Tablet PC hat
> > > just for playing.
> > > > What are you waiting for?
> > > >
> > > http://ads.sourceforge.net/cgi-bin/redirect.pl?micr5043en
> > >
> > > > _______________________________________________
> > > > Fault-injection-developer mailing list
> > > > Fau...@li...
> > > >
> > > https://lists.sourceforge.net/lists/listinfo/fault-injection-developer
> > >
> > > >
> > > >
> > > -------------------------------------------------------
> > >
> > > > This SF.net email is sponsored by: Does your code
> > > think in ink?
> > > > You could win a Tablet PC. Get a free Tablet PC hat
> > > just for playing.
> > > > What are you waiting for?
> > > >
> > > http://ads.sourceforge.net/cgi-bin/redirect.pl?micr5043en
> > >
> > > > _______________________________________________
> > > > Fault-injection-developer mailing list
> > > > Fau...@li...
> > > >
> > > https://lists.sourceforge.net/lists/listinfo/fault-injection-developer
> > >
> > > -------------------------------------------------------
> > >
> > > This SF.net email is sponsored by: Does your code
> > > think in ink?
> > > You could win a Tablet PC. Get a free Tablet PC hat
> > > just for playing.
> > > What are you waiting for?
> > > http://ads.sourceforge.ne
> > > /cgi-bin/redirect.pl?micr5043en
> > > _______________________________________________
> > > Fault-injection-developer mailing list
> > > Fau...@li...
> > > https://lists.sourceforge.net/lists/listinfo/fa
> > > lt-injection-developer
> >
|
|
From: Wang, S. <sta...@in...> - 2003-03-20 03:58:53
|
Could you identify the piece of codes (or module?) that caused your kernel
panic?
And you could recomple your kernel with:
#
# Kernel hacking
#
CONFIG_DEBUG_KERNEL=y
CONFIG_KPROBES=y
CONFIG_DEBUGREG=y
CONFIG_KWATCH=y
CONFIG_KMMIO=y
CONFIG_KIRQ=y
CONFIG_FI=y
CONFIG_FI_DEBUG=y
CONFIG_FI_SAMPLE_CODESEGMENT=m
~~~
CONFIG_FI_PF=y
CONFIG_FI_DR=m
CONFIG_FI_DBP=y
CONFIG_FI_IRQ=y
CONFIG_FI_INTERNEL_TESTING=y
CONFIG_FI_MOCK_INTERCEPTOR=m
~~~
CONFIG_FI_MOCK_CODESEGMENT=m
~~~
CONFIG_FI_TEST=m
~~
Not sure, Just have a try.
Regards,
Stan
-----Original Message-----
From: Arun Prasad [mailto:ar...@ne...]
Sent: 2003-03-20 11:39
To: Gao, Kevin
Cc: fau...@li...
Subject: Re: [Fault-injection-developer] fith
Hi Kevin,
I have attatched the ".config" file.... The below are the commands used
to compile and load the new kernel
cd 2.5-linux-fi-extern
make mrproper
make menuconfig
make dep
make bzImage
make modules
make modules_install
Configured lilo.conf
lilo
Thanks
-arun
"Gao, Kevin" wrote:
Could you please send us your kernel config information,so that we can
track what happens to your kernel.Thanks -Kevin
-----Original Message-----
From: Arun Prasad [ mailto:ar...@ne...
<mailto:ar...@ne...> ]
Sent: 2003?3?19? 17:06
To: Gao, Kevin
Cc: fau...@li...
Subject: Re: [Fault-injection-developer] fith
Hi Kevin/All,
I downloaded 2.5-fi-extern from Bk... Compiled the kernel and while
booting with this new kernel, I got the below panic...
Mount-cache hash table entries: 512 (order: 0, 4096)
invalid operand: 0000
CPU: 0
EIP: 0060:[<C01214F2>] Not tainted
EFLAGS: 00010286
.................................
..........................
....................
..............
<0> Kernel panic: Attempted to kill the idle task!
In Idle task -not syncing
Does somebody has faced this?? Any workaround for this ??
Thanks
-arun
"Gao, Kevin" wrote:
Hi Arun,
The example for e100 test cases is as folloow:
insert module : fi_core, fi_pf, e100,
# cd ./fith-tool/fith_test/fault_set/e100
#make
# insmod scb_cu_resume.ko
# ficl -i scb_cu_resume.fsml (You should change the "base" parameter to
your own bar address of e100).
# /etc/init.d/network start
Now use command dmesg to see the log info or see the message in
/var/log/messages.
-Kevin
-----Original Message-----
From: Arun Prasad [ mailto:ar...@ne...
<mailto:ar...@ne...> ]
Sent: 2003?3?18? 18:12
To: Gao, Kevin
Cc: fau...@li...
Subject: Re: [Fault-injection-developer] fith
Hi Kevin,
Thanks for the response... Iam in the process of downloading the
2.5-fi-extern from BK.
The fault injection test cases for e100 is present along with the fith
utility...That seems to be a good reference for me to start writing test
cases for giga-bit ethernet card (which Iam trying to do...)... But just the
fsml and the code_segments are provided for e100... I couldnt see the
scripts
to use them (like the demo at fith_test dir) . Is that possible to include
the
scripts also in the repository??
Thanks
-arun
"Gao, Kevin" wrote:
> The tree linux-2.5 is out of date.
> So please dowload the newest tree at
> http://fau...@fa.../2.5-fi-extern
<http://fau...@fa.../2.5-fi-extern>
> The new tree includes all interceptors.
>
> The usage of FITH_TOOL is as follow.
>
> We still use tools "ficl"
> You can use parameters as follow:
>
> --attach, -a <modname,file_path>
> attach a module into dbp.
> --detach, -d
> detach all modules that attached to dbp.
> --insert, -i <file.fsml>
> insert a faultset written in file.fsml into FITH.
> --remove, -r {file.fsml|all}
> remove the faultset written in file.fsml or all faultset.
> --help, -h
> help information.
>
> thanks
> -Kevin
>
> -----Original Message-----
> From: Arun Prasad [ mailto:ar...@ne...
<mailto:ar...@ne...> ]
> Sent: 2003?3?18? 17:17
> To: fau...@li...
> Subject: [Fault-injection-developer] fith
>
> Hi All,
> To use the fith tool, downloaded the Bitkeeper tool and
> cloned the
> below repositories...
> * fith-tool
> * linux-2.5
> both from fault-injection project.
>
> Now I have to compile and load the "linux-2.5" (above) and
> install
> "fith-tool" on it... Is my assumption right... Because I
> could see
> "2.5-kprobes" in the list of repositories which is again a
> kernel tree....
> It will be helpful if we know the significance of each
> repository..
>
> Please clarify this....
>
> Is there any upto date manual to describe the ficl commands
> and for
> general usage of the tool....
>
> Thanks
> -arun
>
> -------------------------------------------------------
> This SF.net email is sponsored by: Does your code think in ink?
> You could win a Tablet PC. Get a free Tablet PC hat just for playing.
> What are you waiting for?
> http://ads.sourceforge.net/cgi-bin/redirect.pl?micr5043en
<http://ads.sourceforge.net/cgi-bin/redirect.pl?micr5043en>
> _______________________________________________
> Fault-injection-developer mailing list
> Fau...@li...
> https://lists.sourceforge.net/lists/listinfo/fault-injection-developer
<https://lists.sourceforge.net/lists/listinfo/fault-injection-developer>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: Does your code think in ink?
> You could win a Tablet PC. Get a free Tablet PC hat just for playing.
> What are you waiting for?
> http://ads.sourceforge.net/cgi-bin/redirect.pl?micr5043en
<http://ads.sourceforge.net/cgi-bin/redirect.pl?micr5043en>
> _______________________________________________
> Fault-injection-developer mailing list
> Fau...@li...
> https://lists.sourceforge.net/lists/listinfo/fault-injection-developer
<https://lists.sourceforge.net/lists/listinfo/fault-injection-developer>
-------------------------------------------------------
This SF.net email is sponsored by: Does your code think in ink?
You could win a Tablet PC. Get a free Tablet PC hat just for playing.
What are you waiting for?
http://ads.sourceforge.net/cgi-bin/redirect.pl?micr5043en
<http://ads.sourceforge.net/cgi-bin/redirect.pl?micr5043en>
_______________________________________________
Fault-injection-developer mailing list
Fau...@li...
https://lists.sourceforge.net/lists/listinfo/fault-injection-developer
<https://lists.sourceforge.net/lists/listinfo/fault-injection-developer>
|
|
From: Arun P. <ar...@ne...> - 2003-03-20 03:36:10
|
# # Automatically generated make config: don't edit # CONFIG_X86=y CONFIG_MMU=y CONFIG_SWAP=y CONFIG_UID16=y CONFIG_GENERIC_ISA_DMA=y # # Code maturity level options # CONFIG_EXPERIMENTAL=y # # General setup # CONFIG_SYSVIPC=y CONFIG_BSD_PROCESS_ACCT=y CONFIG_SYSCTL=y CONFIG_LOG_BUF_SHIFT=14 # # Loadable module support # CONFIG_MODULES=y CONFIG_MODULE_UNLOAD=y CONFIG_MODULE_FORCE_UNLOAD=y CONFIG_OBSOLETE_MODPARM=y # CONFIG_MODVERSIONS is not set CONFIG_KMOD=y # # Processor type and features # CONFIG_X86_PC=y # 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_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_MPENTIUM4 is not set # CONFIG_MK6 is not set # CONFIG_MK7 is not set # CONFIG_MK8 is not set # CONFIG_MELAN 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_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_HUGETLB_PAGE is not set # CONFIG_SMP is not set # CONFIG_PREEMPT is not set # CONFIG_X86_UP_APIC is not set CONFIG_X86_TSC=y CONFIG_X86_MCE=y # CONFIG_X86_MCE_NONFATAL is not set CONFIG_TOSHIBA=m CONFIG_I8K=m CONFIG_MICROCODE=m CONFIG_X86_MSR=m CONFIG_X86_CPUID=m # CONFIG_EDD is not set # 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 # # Power management options (ACPI, APM) # CONFIG_PM=y # CONFIG_SOFTWARE_SUSPEND is not set # # ACPI Support # # CONFIG_ACPI is not set CONFIG_APM=y # 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=y # CONFIG_APM_ALLOW_INTS is not set # CONFIG_APM_REAL_MODE_POWER_OFF is not set # # CPU Frequency scaling # # CONFIG_CPU_FREQ is not set # # Bus options (PCI, PCMCIA, EISA, MCA, ISA) # CONFIG_PCI=y # CONFIG_PCI_GOBIOS is not set # CONFIG_PCI_GODIRECT is not set CONFIG_PCI_GOANY=y CONFIG_PCI_BIOS=y CONFIG_PCI_DIRECT=y # CONFIG_SCx200 is not set # CONFIG_PCI_LEGACY_PROC is not set CONFIG_PCI_NAMES=y CONFIG_ISA=y CONFIG_EISA=y CONFIG_EISA_PCI_EISA=y CONFIG_EISA_VIRTUAL_ROOT=y CONFIG_EISA_NAMES=y # CONFIG_MCA is not set CONFIG_HOTPLUG=y # # PCMCIA/CardBus support # CONFIG_PCMCIA=m CONFIG_CARDBUS=y CONFIG_I82092=m CONFIG_I82365=m CONFIG_TCIC=m # # PCI Hotplug Support # # CONFIG_HOTPLUG_PCI is not set # # Executable file formats # CONFIG_KCORE_ELF=y # CONFIG_KCORE_AOUT is not set CONFIG_BINFMT_AOUT=m CONFIG_BINFMT_ELF=y CONFIG_BINFMT_MISC=m # # Memory Technology Devices (MTD) # # CONFIG_MTD is not set # # Parallel port support # CONFIG_PARPORT=m CONFIG_PARPORT_PC=m # CONFIG_PARPORT_PC_FIFO is not set # CONFIG_PARPORT_PC_SUPERIO is not set CONFIG_PARPORT_PC_PCMCIA=m # CONFIG_PARPORT_OTHER is not set CONFIG_PARPORT_1284=y # # Plug and Play support # CONFIG_PNP=y # CONFIG_PNP_NAMES is not set # CONFIG_PNP_CARD is not set # CONFIG_PNP_DEBUG is not set # # Protocols # # CONFIG_PNPBIOS is not set # # Block devices # CONFIG_BLK_DEV_FD=y CONFIG_BLK_DEV_XD=m CONFIG_PARIDE=m CONFIG_PARIDE_PARPORT=m # # Parallel IDE high-level drivers # CONFIG_PARIDE_PD=m CONFIG_PARIDE_PCD=m CONFIG_PARIDE_PF=m CONFIG_PARIDE_PT=m CONFIG_PARIDE_PG=m # # Parallel IDE protocol modules # CONFIG_PARIDE_ATEN=m CONFIG_PARIDE_BPCK=m CONFIG_PARIDE_BPCK6=m CONFIG_PARIDE_COMM=m CONFIG_PARIDE_DSTR=m CONFIG_PARIDE_FIT2=m CONFIG_PARIDE_FIT3=m CONFIG_PARIDE_EPAT=m CONFIG_PARIDE_EPATC8=y CONFIG_PARIDE_EPIA=m CONFIG_PARIDE_FRIQ=m CONFIG_PARIDE_FRPW=m CONFIG_PARIDE_KBIC=m CONFIG_PARIDE_KTTI=m CONFIG_PARIDE_ON20=m CONFIG_PARIDE_ON26=m CONFIG_BLK_CPQ_DA=m CONFIG_BLK_CPQ_CISS_DA=m CONFIG_BLK_DEV_DAC960=m # CONFIG_BLK_DEV_UMEM is not set CONFIG_BLK_DEV_LOOP=m CONFIG_BLK_DEV_NBD=m CONFIG_BLK_DEV_RAM=y CONFIG_BLK_DEV_RAM_SIZE=4096 CONFIG_BLK_DEV_INITRD=y # CONFIG_LBD is not set # # ATA/ATAPI/MFM/RLL device support # CONFIG_IDE=y # # IDE, ATA and ATAPI Block devices # CONFIG_BLK_DEV_IDE=y # # Please see Documentation/ide.txt for help/info on IDE drives # # CONFIG_BLK_DEV_HD_IDE is not set # CONFIG_BLK_DEV_HD is not set CONFIG_BLK_DEV_IDEDISK=y CONFIG_IDEDISK_MULTI_MODE=y # CONFIG_IDEDISK_STROKE is not set CONFIG_BLK_DEV_IDECS=m CONFIG_BLK_DEV_IDECD=m CONFIG_BLK_DEV_IDEFLOPPY=y # CONFIG_IDE_TASK_IOCTL is not set # # IDE chipset support/bugfixes # CONFIG_BLK_DEV_CMD640=y # CONFIG_BLK_DEV_CMD640_ENHANCED is not set # CONFIG_BLK_DEV_IDEPNP is not set CONFIG_BLK_DEV_IDEPCI=y # CONFIG_BLK_DEV_GENERIC is not set CONFIG_IDEPCI_SHARE_IRQ=y CONFIG_BLK_DEV_IDEDMA_PCI=y # CONFIG_BLK_DEV_IDE_TCQ is not set # CONFIG_BLK_DEV_OFFBOARD is not set # CONFIG_BLK_DEV_IDEDMA_FORCED is not set CONFIG_IDEDMA_PCI_AUTO=y # CONFIG_IDEDMA_ONLYDISK is not set CONFIG_BLK_DEV_IDEDMA=y # CONFIG_IDEDMA_PCI_WIP is not set CONFIG_BLK_DEV_ADMA=y CONFIG_BLK_DEV_AEC62XX=y CONFIG_BLK_DEV_ALI15X3=y # CONFIG_WDC_ALI15X3 is not set CONFIG_BLK_DEV_AMD74XX=y CONFIG_BLK_DEV_CMD64X=y # CONFIG_BLK_DEV_TRIFLEX is not set CONFIG_BLK_DEV_CY82C693=y # CONFIG_BLK_DEV_CS5520 is not set CONFIG_BLK_DEV_HPT34X=y CONFIG_BLK_DEV_HPT366=y # CONFIG_BLK_DEV_SC1200 is not set CONFIG_BLK_DEV_PIIX=y # CONFIG_BLK_DEV_NS87415 is not set # CONFIG_BLK_DEV_OPTI621 is not set # CONFIG_BLK_DEV_PDC202XX_OLD is not set # CONFIG_BLK_DEV_PDC202XX_NEW is not set CONFIG_BLK_DEV_RZ1000=y CONFIG_BLK_DEV_SVWKS=y # CONFIG_BLK_DEV_SIIMAGE is not set CONFIG_BLK_DEV_SIS5513=y CONFIG_BLK_DEV_SLC90E66=y # CONFIG_BLK_DEV_TRM290 is not set CONFIG_BLK_DEV_VIA82CXXX=y # CONFIG_IDE_CHIPSETS is not set CONFIG_IDEDMA_AUTO=y # CONFIG_IDEDMA_IVB is not set CONFIG_BLK_DEV_IDE_MODES=y # # SCSI device support # # CONFIG_SCSI is not set # # Old CD-ROM drivers (not SCSI, not IDE) # # CONFIG_CD_NO_IDESCSI is not set # # Multi-device support (RAID and LVM) # CONFIG_MD=y CONFIG_BLK_DEV_MD=y CONFIG_MD_LINEAR=m CONFIG_MD_RAID0=m CONFIG_MD_RAID1=m CONFIG_MD_RAID5=m CONFIG_MD_MULTIPATH=m # CONFIG_BLK_DEV_DM is not set # # Fusion MPT device support # # # IEEE 1394 (FireWire) support (EXPERIMENTAL) # CONFIG_IEEE1394=m # # Subsystem Options # # CONFIG_IEEE1394_VERBOSEDEBUG is not set # CONFIG_IEEE1394_OUI_DB is not set # # Device Drivers # # CONFIG_IEEE1394_PCILYNX is not set # CONFIG_IEEE1394_OHCI1394 is not set # # Protocol Drivers # # CONFIG_IEEE1394_ETH1394 is not set CONFIG_IEEE1394_RAWIO=m # CONFIG_IEEE1394_CMP is not set # # I2O device support # CONFIG_I2O=m CONFIG_I2O_PCI=m CONFIG_I2O_BLOCK=m CONFIG_I2O_PROC=m # # Networking support # CONFIG_NET=y # # Networking options # CONFIG_PACKET=y CONFIG_PACKET_MMAP=y CONFIG_NETLINK_DEV=y CONFIG_NETFILTER=y # CONFIG_NETFILTER_DEBUG is not set CONFIG_FILTER=y CONFIG_UNIX=y # CONFIG_NET_KEY is not set CONFIG_INET=y CONFIG_IP_MULTICAST=y CONFIG_IP_ADVANCED_ROUTER=y CONFIG_IP_MULTIPLE_TABLES=y CONFIG_IP_ROUTE_FWMARK=y CONFIG_IP_ROUTE_NAT=y CONFIG_IP_ROUTE_MULTIPATH=y CONFIG_IP_ROUTE_TOS=y CONFIG_IP_ROUTE_VERBOSE=y CONFIG_IP_ROUTE_LARGE_TABLES=y # CONFIG_IP_PNP is not set CONFIG_NET_IPIP=m CONFIG_NET_IPGRE=m CONFIG_NET_IPGRE_BROADCAST=y CONFIG_IP_MROUTE=y CONFIG_IP_PIMSM_V1=y CONFIG_IP_PIMSM_V2=y # CONFIG_ARPD is not set # CONFIG_INET_ECN is not set CONFIG_SYN_COOKIES=y # CONFIG_INET_AH is not set # CONFIG_INET_ESP is not set # CONFIG_XFRM_USER is not set # # IP: Netfilter Configuration # CONFIG_IP_NF_CONNTRACK=m CONFIG_IP_NF_FTP=m CONFIG_IP_NF_IRC=m CONFIG_IP_NF_QUEUE=m CONFIG_IP_NF_IPTABLES=m CONFIG_IP_NF_MATCH_LIMIT=m CONFIG_IP_NF_MATCH_MAC=m # CONFIG_IP_NF_MATCH_PKTTYPE is not set CONFIG_IP_NF_MATCH_MARK=m CONFIG_IP_NF_MATCH_MULTIPORT=m CONFIG_IP_NF_MATCH_TOS=m # CONFIG_IP_NF_MATCH_ECN is not set # CONFIG_IP_NF_MATCH_DSCP is not set # CONFIG_IP_NF_MATCH_AH_ESP is not set CONFIG_IP_NF_MATCH_LENGTH=m CONFIG_IP_NF_MATCH_TTL=m CONFIG_IP_NF_MATCH_TCPMSS=m # CONFIG_IP_NF_MATCH_HELPER is not set CONFIG_IP_NF_MATCH_STATE=m # CONFIG_IP_NF_MATCH_CONNTRACK is not set CONFIG_IP_NF_MATCH_UNCLEAN=m CONFIG_IP_NF_MATCH_OWNER=m # CONFIG_IP_NF_MATCH_PHYSDEV is not set CONFIG_IP_NF_FILTER=m CONFIG_IP_NF_TARGET_REJECT=m CONFIG_IP_NF_TARGET_MIRROR=m CONFIG_IP_NF_NAT=m CONFIG_IP_NF_NAT_NEEDED=y CONFIG_IP_NF_TARGET_MASQUERADE=m CONFIG_IP_NF_TARGET_REDIRECT=m # CONFIG_IP_NF_NAT_LOCAL is not set CONFIG_IP_NF_NAT_SNMP_BASIC=m CONFIG_IP_NF_NAT_IRC=m CONFIG_IP_NF_NAT_FTP=m CONFIG_IP_NF_MANGLE=m CONFIG_IP_NF_TARGET_TOS=m # CONFIG_IP_NF_TARGET_ECN is not set # CONFIG_IP_NF_TARGET_DSCP is not set CONFIG_IP_NF_TARGET_MARK=m CONFIG_IP_NF_TARGET_LOG=m # CONFIG_IP_NF_TARGET_ULOG is not set CONFIG_IP_NF_TARGET_TCPMSS=m # CONFIG_IP_NF_ARPTABLES is not set CONFIG_IP_NF_COMPAT_IPCHAINS=m CONFIG_IP_NF_COMPAT_IPFWADM=m CONFIG_IPV6=m # CONFIG_IPV6_PRIVACY is not set # # IPv6: Netfilter Configuration # # CONFIG_IP6_NF_QUEUE is not set CONFIG_IP6_NF_IPTABLES=m CONFIG_IP6_NF_MATCH_LIMIT=m CONFIG_IP6_NF_MATCH_MAC=m CONFIG_IP6_NF_MATCH_MULTIPORT=m CONFIG_IP6_NF_MATCH_OWNER=m CONFIG_IP6_NF_MATCH_MARK=m # CONFIG_IP6_NF_MATCH_LENGTH is not set # CONFIG_IP6_NF_MATCH_EUI64 is not set CONFIG_IP6_NF_FILTER=m CONFIG_IP6_NF_TARGET_LOG=m CONFIG_IP6_NF_MANGLE=m CONFIG_IP6_NF_TARGET_MARK=m # # SCTP Configuration (EXPERIMENTAL) # CONFIG_IPV6_SCTP__=m # CONFIG_IP_SCTP is not set # CONFIG_ATM is not set CONFIG_VLAN_8021Q=m # CONFIG_LLC is not set CONFIG_DECNET=m CONFIG_DECNET_SIOCGIFCONF=y CONFIG_DECNET_ROUTER=y CONFIG_DECNET_ROUTE_FWMARK=y CONFIG_BRIDGE=m # CONFIG_BRIDGE_NF_EBTABLES is not set # CONFIG_X25 is not set # CONFIG_LAPB is not set # CONFIG_NET_DIVERT is not set # CONFIG_ECONET is not set CONFIG_WAN_ROUTER=m # CONFIG_NET_FASTROUTE is not set # CONFIG_NET_HW_FLOWCONTROL is not set # # QoS and/or fair queueing # CONFIG_NET_SCHED=y CONFIG_NET_SCH_CBQ=m # CONFIG_NET_SCH_HTB is not set CONFIG_NET_SCH_CSZ=m CONFIG_NET_SCH_PRIO=m CONFIG_NET_SCH_RED=m CONFIG_NET_SCH_SFQ=m CONFIG_NET_SCH_TEQL=m CONFIG_NET_SCH_TBF=m CONFIG_NET_SCH_GRED=m CONFIG_NET_SCH_DSMARK=m CONFIG_NET_SCH_INGRESS=m CONFIG_NET_QOS=y CONFIG_NET_ESTIMATOR=y CONFIG_NET_CLS=y CONFIG_NET_CLS_TCINDEX=m CONFIG_NET_CLS_ROUTE4=m CONFIG_NET_CLS_ROUTE=y CONFIG_NET_CLS_FW=m CONFIG_NET_CLS_U32=m CONFIG_NET_CLS_RSVP=m CONFIG_NET_CLS_RSVP6=m CONFIG_NET_CLS_POLICE=y # # Network testing # # CONFIG_NET_PKTGEN is not set CONFIG_NETDEVICES=y # # ARCnet devices # # CONFIG_ARCNET is not set CONFIG_DUMMY=m CONFIG_BONDING=m CONFIG_EQUALIZER=m CONFIG_TUN=m CONFIG_ETHERTAP=m # # Ethernet (10 or 100Mbit) # CONFIG_NET_ETHERNET=y # CONFIG_MII is not set CONFIG_HAPPYMEAL=m CONFIG_SUNGEM=m CONFIG_NET_VENDOR_3COM=y CONFIG_EL1=m CONFIG_EL2=m CONFIG_ELPLUS=m CONFIG_EL16=m CONFIG_EL3=m CONFIG_3C515=m CONFIG_VORTEX=m # CONFIG_TYPHOON is not set CONFIG_LANCE=m CONFIG_NET_VENDOR_SMC=y CONFIG_WD80x3=m CONFIG_ULTRA=m CONFIG_ULTRA32=m CONFIG_SMC9194=m CONFIG_NET_VENDOR_RACAL=y CONFIG_NI5010=m CONFIG_NI52=m CONFIG_NI65=m # # Tulip family network device support # # CONFIG_NET_TULIP is not set CONFIG_AT1700=m CONFIG_DEPCA=m CONFIG_HP100=m CONFIG_NET_ISA=y CONFIG_E2100=m CONFIG_EWRK3=m CONFIG_EEXPRESS=m CONFIG_EEXPRESS_PRO=m CONFIG_HPLAN_PLUS=m CONFIG_HPLAN=m CONFIG_LP486E=m CONFIG_ETH16I=m CONFIG_NE2000=m # CONFIG_ZNET is not set CONFIG_NET_PCI=y CONFIG_PCNET32=m # CONFIG_AMD8111_ETH is not set CONFIG_ADAPTEC_STARFIRE=m # CONFIG_ADAPTEC_STARFIRE_NAPI is not set CONFIG_AC3200=m CONFIG_APRICOT=m # CONFIG_B44 is not set CONFIG_CS89x0=m CONFIG_DGRS=m CONFIG_EEPRO100=m # CONFIG_EEPRO100_PIO is not set # CONFIG_E100 is not set CONFIG_LNE390=m # CONFIG_FEALNX is not set CONFIG_NATSEMI=m CONFIG_NE2K_PCI=m CONFIG_NE3210=m CONFIG_ES3210=m CONFIG_8139CP=m CONFIG_8139TOO=m # CONFIG_8139TOO_PIO is not set # CONFIG_8139TOO_TUNE_TWISTER is not set CONFIG_8139TOO_8129=y # CONFIG_8139_OLD_RX_RESET is not set CONFIG_SIS900=m CONFIG_EPIC100=m CONFIG_SUNDANCE=m # CONFIG_SUNDANCE_MMIO is not set CONFIG_TLAN=m CONFIG_VIA_RHINE=m # CONFIG_VIA_RHINE_MMIO is not set CONFIG_NET_POCKET=y CONFIG_ATP=m CONFIG_DE600=m CONFIG_DE620=m # # Ethernet (1000 Mbit) # CONFIG_ACENIC=m # CONFIG_ACENIC_OMIT_TIGON_I is not set CONFIG_DL2K=m # CONFIG_E1000 is not set CONFIG_NS83820=m CONFIG_HAMACHI=m CONFIG_YELLOWFIN=m # CONFIG_R8169 is not set CONFIG_SK98LIN=m CONFIG_TIGON3=m CONFIG_FDDI=y # CONFIG_DEFXX is not set CONFIG_SKFP=m # CONFIG_HIPPI is not set CONFIG_PLIP=m CONFIG_PPP=m CONFIG_PPP_MULTILINK=y CONFIG_PPP_FILTER=y CONFIG_PPP_ASYNC=m CONFIG_PPP_SYNC_TTY=m CONFIG_PPP_DEFLATE=m # CONFIG_PPP_BSDCOMP is not set # CONFIG_PPPOE is not set CONFIG_SLIP=m CONFIG_SLIP_COMPRESSED=y CONFIG_SLIP_SMART=y CONFIG_SLIP_MODE_SLIP6=y # # Wireless LAN (non-hamradio) # CONFIG_NET_RADIO=y # # Obsolete Wireless cards support (pre-802.11) # CONFIG_STRIP=m CONFIG_ARLAN=m CONFIG_WAVELAN=m CONFIG_PCMCIA_WAVELAN=m CONFIG_PCMCIA_NETWAVE=m # # Wireless 802.11 Frequency Hopping cards support # CONFIG_PCMCIA_RAYCS=m # # Wireless 802.11b ISA/PCI cards support # CONFIG_AIRO=m CONFIG_HERMES=m CONFIG_PLX_HERMES=m # CONFIG_PCI_HERMES is not set # # Wireless 802.11b Pcmcia/Cardbus cards support # CONFIG_PCMCIA_HERMES=m CONFIG_AIRO_CS=m CONFIG_NET_WIRELESS=y # # Token Ring devices (depends on LLC=y) # # CONFIG_RCPCI is not set CONFIG_SHAPER=m # # Wan interfaces # # CONFIG_WAN is not set # # PCMCIA network device support # CONFIG_NET_PCMCIA=y CONFIG_PCMCIA_3C589=m CONFIG_PCMCIA_3C574=m CONFIG_PCMCIA_FMVJ18X=m CONFIG_PCMCIA_PCNET=m CONFIG_PCMCIA_NMCLAN=m CONFIG_PCMCIA_SMC91C92=m CONFIG_PCMCIA_XIRC2PS=m CONFIG_PCMCIA_AXNET=m # # Amateur Radio support # # CONFIG_HAMRADIO is not set # # IrDA (infrared) support # CONFIG_IRDA=m # # IrDA protocols # CONFIG_IRLAN=m CONFIG_IRNET=m CONFIG_IRCOMM=m CONFIG_IRDA_ULTRA=y # # IrDA options # CONFIG_IRDA_CACHE_LAST_LSAP=y CONFIG_IRDA_FAST_RR=y # CONFIG_IRDA_DEBUG is not set # # Infrared-port device drivers # # # SIR device drivers # CONFIG_IRTTY_SIR=m # # Dongle support # CONFIG_DONGLE=y CONFIG_ESI_DONGLE=m CONFIG_ACTISYS_DONGLE=m CONFIG_TEKRAM_DONGLE=m # # Old SIR device drivers # # CONFIG_IRTTY_OLD is not set CONFIG_IRPORT_SIR=m # # Old Serial dongle support # # CONFIG_DONGLE_OLD is not set # # FIR device drivers # CONFIG_USB_IRDA=m CONFIG_NSC_FIR=m CONFIG_WINBOND_FIR=m # CONFIG_TOSHIBA_OLD is not set CONFIG_TOSHIBA_FIR=m CONFIG_SMC_IRCC_FIR=m CONFIG_ALI_FIR=m # CONFIG_VLSI_FIR is not set # # ISDN subsystem # # CONFIG_ISDN_BOOL is not set # # Telephony Support # # CONFIG_PHONE is not set # # Input device support # CONFIG_INPUT=y # # Userland interfaces # CONFIG_INPUT_MOUSEDEV=m CONFIG_INPUT_MOUSEDEV_PSAUX=y CONFIG_INPUT_MOUSEDEV_SCREEN_X=1024 CONFIG_INPUT_MOUSEDEV_SCREEN_Y=768 CONFIG_INPUT_JOYDEV=m # CONFIG_INPUT_TSDEV is not set CONFIG_INPUT_EVDEV=m # CONFIG_INPUT_EVBUG is not set # # Input I/O drivers # # CONFIG_GAMEPORT is not set CONFIG_SOUND_GAMEPORT=y CONFIG_SERIO=y CONFIG_SERIO_I8042=y CONFIG_SERIO_SERPORT=y # CONFIG_SERIO_CT82C710 is not set # CONFIG_SERIO_PARKBD is not set # # Input Device Drivers # CONFIG_INPUT_KEYBOARD=y CONFIG_KEYBOARD_ATKBD=y # CONFIG_KEYBOARD_SUNKBD is not set # CONFIG_KEYBOARD_XTKBD is not set # CONFIG_KEYBOARD_NEWTON is not set CONFIG_INPUT_MOUSE=y CONFIG_MOUSE_PS2=y # CONFIG_MOUSE_SERIAL is not set # CONFIG_MOUSE_INPORT is not set # CONFIG_MOUSE_LOGIBM is not set # CONFIG_MOUSE_PC110PAD is not set # CONFIG_INPUT_JOYSTICK is not set # CONFIG_INPUT_TOUCHSCREEN is not set # CONFIG_INPUT_MISC is not set # # Character devices # CONFIG_VT=y CONFIG_VT_CONSOLE=y CONFIG_HW_CONSOLE=y CONFIG_SERIAL_NONSTANDARD=y CONFIG_COMPUTONE=m CONFIG_ROCKETPORT=m CONFIG_CYCLADES=m # CONFIG_CYZ_INTR is not set CONFIG_DIGIEPCA=m # CONFIG_ESPSERIAL is not set CONFIG_MOXA_INTELLIO=m CONFIG_MOXA_SMARTIO=m # CONFIG_ISI is not set CONFIG_SYNCLINK=m # CONFIG_SYNCLINKMP is not set CONFIG_N_HDLC=m # CONFIG_RISCOM8 is not set # CONFIG_SPECIALIX is not set CONFIG_SX=m # CONFIG_RIO is not set CONFIG_STALDRV=y CONFIG_STALLION=m CONFIG_ISTALLION=m # # Serial drivers # # CONFIG_SERIAL_8250 is not set # # Non-8250 serial port support # CONFIG_UNIX98_PTYS=y CONFIG_UNIX98_PTY_COUNT=2048 CONFIG_PRINTER=m CONFIG_LP_CONSOLE=y CONFIG_PPDEV=m # CONFIG_TIPAR is not set # # I2C support # CONFIG_I2C=m CONFIG_I2C_ALGOBIT=m CONFIG_I2C_PHILIPSPAR=m CONFIG_I2C_ELV=m CONFIG_I2C_VELLEMAN=m # CONFIG_SCx200_ACB is not set CONFIG_I2C_ALGOPCF=m CONFIG_I2C_ELEKTOR=m CONFIG_I2C_CHARDEV=m CONFIG_I2C_PROC=m # # I2C Hardware Sensors Mainboard support # # CONFIG_I2C_AMD756 is not set # CONFIG_I2C_AMD8111 is not set # # I2C Hardware Sensors Chip support # # CONFIG_SENSORS_ADM1021 is not set # CONFIG_SENSORS_LM75 is not set # # Mice # CONFIG_BUSMOUSE=m # CONFIG_QIC02_TAPE is not set # # IPMI # # CONFIG_IPMI_HANDLER is not set # # Watchdog Cards # CONFIG_WATCHDOG=y # CONFIG_WATCHDOG_NOWAYOUT is not set CONFIG_SOFT_WATCHDOG=m CONFIG_WDT=m CONFIG_WDTPCI=m # CONFIG_WDT_501 is not set CONFIG_PCWATCHDOG=m CONFIG_ACQUIRE_WDT=m CONFIG_ADVANTECH_WDT=m CONFIG_EUROTECH_WDT=m CONFIG_IB700_WDT=m CONFIG_I810_TCO=m # CONFIG_MIXCOMWD is not set # CONFIG_SCx200_WDT is not set # CONFIG_60XX_WDT is not set CONFIG_W83877F_WDT=m CONFIG_MACHZ_WDT=m # CONFIG_SC520_WDT is not set # CONFIG_AMD7XX_TCO is not set # CONFIG_ALIM7101_WDT is not set # CONFIG_SC1200_WDT is not set # CONFIG_WAFER_WDT is not set # CONFIG_CPU5_WDT is not set CONFIG_INTEL_RNG=m CONFIG_AMD_RNG=m CONFIG_NVRAM=m CONFIG_RTC=y CONFIG_DTLK=m CONFIG_R3964=m # CONFIG_APPLICOM is not set CONFIG_SONYPI=m # # Ftape, the floppy tape device driver # CONFIG_FTAPE=m CONFIG_ZFTAPE=m CONFIG_ZFT_DFLT_BLK_SZ=10240 # # The compressor will be built as a module only! # CONFIG_ZFT_COMPRESSOR=m CONFIG_FT_NR_BUFFERS=3 # CONFIG_FT_PROC_FS is not set CONFIG_FT_NORMAL_DEBUG=y # CONFIG_FT_FULL_DEBUG is not set # CONFIG_FT_NO_TRACE is not set # CONFIG_FT_NO_TRACE_AT_ALL is not set # # Hardware configuration # CONFIG_FT_STD_FDC=y # CONFIG_FT_MACH2 is not set # CONFIG_FT_PROBE_FC10 is not set # CONFIG_FT_ALT_FDC is not set CONFIG_FT_FDC_THR=8 CONFIG_FT_FDC_MAX_RATE=2000 CONFIG_FT_ALPHA_CLOCK=0 CONFIG_AGP=m # CONFIG_AGP3 is not set CONFIG_AGP_INTEL=m CONFIG_AGP_VIA=m CONFIG_AGP_AMD=m CONFIG_AGP_SIS=m CONFIG_AGP_ALI=m CONFIG_AGP_SWORKS=m # CONFIG_AGP_AMD_8151 is not set CONFIG_DRM=y # CONFIG_DRM_TDFX is not set CONFIG_DRM_R128=m CONFIG_DRM_RADEON=m CONFIG_DRM_I810=m CONFIG_DRM_I830=m CONFIG_DRM_MGA=m # # PCMCIA character devices # # CONFIG_SYNCLINK_CS is not set CONFIG_MWAVE=m # CONFIG_RAW_DRIVER is not set # CONFIG_HANGCHECK_TIMER is not set # # Multimedia devices # CONFIG_VIDEO_DEV=m # # Video For Linux # CONFIG_VIDEO_PROC_FS=y # # Video Adapters # # CONFIG_VIDEO_PMS is not set # CONFIG_VIDEO_BWQCAM is not set # CONFIG_VIDEO_CQCAM is not set # CONFIG_VIDEO_W9966 is not set # CONFIG_VIDEO_CPIA is not set # CONFIG_VIDEO_SAA5249 is not set # CONFIG_TUNER_3036 is not set # CONFIG_VIDEO_STRADIS is not set # CONFIG_VIDEO_ZORAN is not set # CONFIG_VIDEO_ZR36120 is not set CONFIG_VIDEO_MEYE=m # CONFIG_VIDEO_SAA7134 is not set # # Radio Adapters # CONFIG_RADIO_CADET=m CONFIG_RADIO_RTRACK=m CONFIG_RADIO_RTRACK2=m CONFIG_RADIO_AZTECH=m CONFIG_RADIO_GEMTEK=m CONFIG_RADIO_GEMTEK_PCI=m CONFIG_RADIO_MAXIRADIO=m CONFIG_RADIO_MAESTRO=m CONFIG_RADIO_SF16FMI=m CONFIG_RADIO_TERRATEC=m CONFIG_RADIO_TRUST=m CONFIG_RADIO_TYPHOON=m CONFIG_RADIO_TYPHOON_PROC_FS=y CONFIG_RADIO_ZOLTRIX=m # # Digital Video Broadcasting Devices # # CONFIG_DVB is not set # # File systems # CONFIG_QUOTA=y # CONFIG_QFMT_V1 is not set # CONFIG_QFMT_V2 is not set CONFIG_QUOTACTL=y CONFIG_AUTOFS_FS=m CONFIG_AUTOFS4_FS=m CONFIG_REISERFS_FS=m # CONFIG_REISERFS_CHECK is not set CONFIG_REISERFS_PROC_INFO=y # CONFIG_ADFS_FS is not set # CONFIG_AFFS_FS is not set CONFIG_HFS_FS=m # CONFIG_BEFS_FS is not set CONFIG_BFS_FS=m CONFIG_EXT3_FS=m CONFIG_EXT3_FS_XATTR=y # CONFIG_EXT3_FS_POSIX_ACL is not set CONFIG_JBD=y # CONFIG_JBD_DEBUG is not set CONFIG_FAT_FS=m CONFIG_MSDOS_FS=m CONFIG_VFAT_FS=m # CONFIG_EFS_FS is not set CONFIG_CRAMFS=m CONFIG_TMPFS=y CONFIG_RAMFS=y CONFIG_ISO9660_FS=y CONFIG_JOLIET=y CONFIG_ZISOFS=y CONFIG_JFS_FS=m # CONFIG_JFS_POSIX_ACL is not set CONFIG_JFS_DEBUG=y # CONFIG_JFS_STATISTICS is not set CONFIG_MINIX_FS=m CONFIG_VXFS_FS=m # CONFIG_NTFS_FS is not set # CONFIG_HPFS_FS is not set CONFIG_PROC_FS=y # CONFIG_DEVFS_FS is not set CONFIG_DEVPTS_FS=y # CONFIG_QNX4FS_FS is not set CONFIG_ROMFS_FS=m CONFIG_EXT2_FS=y # CONFIG_EXT2_FS_XATTR is not set CONFIG_SYSV_FS=m CONFIG_UDF_FS=m CONFIG_UFS_FS=m # CONFIG_UFS_FS_WRITE is not set # CONFIG_XFS_FS is not set # # Network File Systems # # CONFIG_CODA_FS is not set # CONFIG_INTERMEZZO_FS is not set CONFIG_NFS_FS=m CONFIG_NFS_V3=y # CONFIG_NFS_V4 is not set CONFIG_NFSD=m CONFIG_NFSD_V3=y # CONFIG_NFSD_V4 is not set # CONFIG_NFSD_TCP is not set CONFIG_SUNRPC=m # CONFIG_SUNRPC_GSS is not set CONFIG_LOCKD=m CONFIG_LOCKD_V4=y CONFIG_EXPORTFS=m # CONFIG_CIFS is not set CONFIG_SMB_FS=m # CONFIG_SMB_NLS_DEFAULT is not set CONFIG_NCP_FS=m CONFIG_NCPFS_PACKET_SIGNING=y CONFIG_NCPFS_IOCTL_LOCKING=y CONFIG_NCPFS_STRONG=y CONFIG_NCPFS_NFS_NS=y CONFIG_NCPFS_OS2_NS=y CONFIG_NCPFS_SMALLDOS=y CONFIG_NCPFS_NLS=y CONFIG_NCPFS_EXTRAS=y # CONFIG_AFS_FS is not set CONFIG_ZISOFS_FS=y CONFIG_FS_MBCACHE=y # # Partition Types # CONFIG_PARTITION_ADVANCED=y # CONFIG_ACORN_PARTITION is not set CONFIG_OSF_PARTITION=y # CONFIG_AMIGA_PARTITION is not set # CONFIG_ATARI_PARTITION is not set CONFIG_MAC_PARTITION=y CONFIG_MSDOS_PARTITION=y CONFIG_BSD_DISKLABEL=y CONFIG_MINIX_SUBPARTITION=y CONFIG_SOLARIS_X86_PARTITION=y CONFIG_UNIXWARE_DISKLABEL=y # CONFIG_LDM_PARTITION is not set CONFIG_SGI_PARTITION=y # CONFIG_ULTRIX_PARTITION is not set CONFIG_SUN_PARTITION=y # CONFIG_EFI_PARTITION is not set CONFIG_SMB_NLS=y CONFIG_NLS=y # # Native Language Support # CONFIG_NLS_DEFAULT="iso8859-1" CONFIG_NLS_CODEPAGE_437=m CONFIG_NLS_CODEPAGE_737=m CONFIG_NLS_CODEPAGE_775=m CONFIG_NLS_CODEPAGE_850=m CONFIG_NLS_CODEPAGE_852=m CONFIG_NLS_CODEPAGE_855=m CONFIG_NLS_CODEPAGE_857=m CONFIG_NLS_CODEPAGE_860=m CONFIG_NLS_CODEPAGE_861=m CONFIG_NLS_CODEPAGE_862=m CONFIG_NLS_CODEPAGE_863=m CONFIG_NLS_CODEPAGE_864=m CONFIG_NLS_CODEPAGE_865=m CONFIG_NLS_CODEPAGE_866=m CONFIG_NLS_CODEPAGE_869=m CONFIG_NLS_CODEPAGE_936=m CONFIG_NLS_CODEPAGE_950=m CONFIG_NLS_CODEPAGE_932=m CONFIG_NLS_CODEPAGE_949=m CONFIG_NLS_CODEPAGE_874=m CONFIG_NLS_ISO8859_8=m CONFIG_NLS_CODEPAGE_1250=m CONFIG_NLS_CODEPAGE_1251=m CONFIG_NLS_ISO8859_1=m CONFIG_NLS_ISO8859_2=m CONFIG_NLS_ISO8859_3=m CONFIG_NLS_ISO8859_4=m CONFIG_NLS_ISO8859_5=m CONFIG_NLS_ISO8859_6=m CONFIG_NLS_ISO8859_7=m CONFIG_NLS_ISO8859_9=m CONFIG_NLS_ISO8859_13=m CONFIG_NLS_ISO8859_14=m CONFIG_NLS_ISO8859_15=m CONFIG_NLS_KOI8_R=m CONFIG_NLS_KOI8_U=m CONFIG_NLS_UTF8=m # # Graphics support # # CONFIG_FB is not set CONFIG_VIDEO_SELECT=y # # Console display driver support # CONFIG_VGA_CONSOLE=y CONFIG_MDA_CONSOLE=m CONFIG_DUMMY_CONSOLE=y # # Sound # # CONFIG_SOUND is not set # # USB support # CONFIG_USB=m # CONFIG_USB_DEBUG is not set # # Miscellaneous USB options # CONFIG_USB_DEVICEFS=y # CONFIG_USB_BANDWIDTH is not set # CONFIG_USB_DYNAMIC_MINORS is not set # # USB Host Controller Drivers # CONFIG_USB_EHCI_HCD=m # CONFIG_USB_OHCI_HCD is not set # CONFIG_USB_UHCI_HCD is not set # # USB Device Class drivers # # CONFIG_USB_BLUETOOTH_TTY is not set CONFIG_USB_ACM=m CONFIG_USB_PRINTER=m # # SCSI support is needed for USB Storage # # # USB Human Interface Devices (HID) # CONFIG_USB_HID=m # CONFIG_USB_HIDINPUT is not set # CONFIG_USB_HIDDEV is not set # # USB HID Boot Protocol drivers # # CONFIG_USB_KBD is not set # CONFIG_USB_MOUSE is not set CONFIG_USB_AIPTEK=m CONFIG_USB_WACOM=m # CONFIG_USB_KBTAB is not set # CONFIG_USB_POWERMATE is not set # CONFIG_USB_XPAD is not set # # USB Imaging devices # CONFIG_USB_MDC800=m CONFIG_USB_SCANNER=m # # USB Multimedia devices # CONFIG_USB_DABUSB=m CONFIG_USB_VICAM=m CONFIG_USB_DSBR=m CONFIG_USB_IBMCAM=m # CONFIG_USB_KONICAWC is not set CONFIG_USB_OV511=m CONFIG_USB_PWC=m CONFIG_USB_SE401=m CONFIG_USB_STV680=m # # USB Network adaptors # CONFIG_USB_CATC=m CONFIG_USB_CDCETHER=m CONFIG_USB_KAWETH=m CONFIG_USB_PEGASUS=m # CONFIG_USB_RTL8150 is not set CONFIG_USB_USBNET=m # # USB port drivers # CONFIG_USB_USS720=m # # USB Serial Converter support # CONFIG_USB_SERIAL=m CONFIG_USB_SERIAL_GENERIC=y CONFIG_USB_SERIAL_BELKIN=m CONFIG_USB_SERIAL_WHITEHEAT=m CONFIG_USB_SERIAL_DIGI_ACCELEPORT=m CONFIG_USB_SERIAL_EMPEG=m CONFIG_USB_SERIAL_FTDI_SIO=m CONFIG_USB_SERIAL_VISOR=m CONFIG_USB_SERIAL_IPAQ=m CONFIG_USB_SERIAL_IR=m CONFIG_USB_SERIAL_EDGEPORT=m # CONFIG_USB_SERIAL_EDGEPORT_TI is not set CONFIG_USB_SERIAL_KEYSPAN_PDA=m CONFIG_USB_SERIAL_KEYSPAN=m # CONFIG_USB_SERIAL_KEYSPAN_MPR is not set # CONFIG_USB_SERIAL_KEYSPAN_USA28 is not set # CONFIG_USB_SERIAL_KEYSPAN_USA28X is not set CONFIG_USB_SERIAL_KEYSPAN_USA28XA=y CONFIG_USB_SERIAL_KEYSPAN_USA28XB=y # CONFIG_USB_SERIAL_KEYSPAN_USA19 is not set # CONFIG_USB_SERIAL_KEYSPAN_USA18X is not set # CONFIG_USB_SERIAL_KEYSPAN_USA19W is not set # CONFIG_USB_SERIAL_KEYSPAN_USA19QW is not set # CONFIG_USB_SERIAL_KEYSPAN_USA19QI is not set # CONFIG_USB_SERIAL_KEYSPAN_USA49W is not set # CONFIG_USB_SERIAL_KEYSPAN_USA49WLC is not set CONFIG_USB_SERIAL_KLSI=m # CONFIG_USB_SERIAL_KOBIL_SCT is not set CONFIG_USB_SERIAL_MCT_U232=m CONFIG_USB_SERIAL_PL2303=m # CONFIG_USB_SERIAL_SAFE is not set CONFIG_USB_SERIAL_CYBERJACK=m CONFIG_USB_SERIAL_XIRCOM=m CONFIG_USB_SERIAL_OMNINET=m CONFIG_USB_EZUSB=y # # USB Miscellaneous drivers # # CONFIG_USB_TIGL is not set CONFIG_USB_AUERSWALD=m CONFIG_USB_RIO500=m # CONFIG_USB_BRLVGER is not set # CONFIG_USB_LCD is not set # CONFIG_USB_TEST is not set # # Bluetooth support # # CONFIG_BT is not set # # Profiling support # # CONFIG_PROFILING is not set # # Kernel hacking # CONFIG_DEBUG_KERNEL=y CONFIG_KPROBES=y CONFIG_DEBUGREG=y CONFIG_KWATCH=y CONFIG_KMMIO=y CONFIG_KIRQ=y CONFIG_FI=y CONFIG_FI_DEBUG=y CONFIG_FI_SAMPLE_CODESEGMENT=y CONFIG_FI_PF=y CONFIG_FI_DR=m CONFIG_FI_DBP=y CONFIG_FI_IRQ=y CONFIG_FI_INTERNEL_TESTING=y CONFIG_FI_MOCK_INTERCEPTOR=y CONFIG_FI_MOCK_CODESEGMENT=y CONFIG_FI_TEST=m CONFIG_DEBUG_STACKOVERFLOW=y CONFIG_DEBUG_SLAB=y CONFIG_DEBUG_IOVIRT=y CONFIG_MAGIC_SYSRQ=y # CONFIG_DEBUG_SPINLOCK is not set # CONFIG_DEBUG_HIGHMEM is not set CONFIG_KALLSYMS=y # CONFIG_DEBUG_SPINLOCK_SLEEP is not set # CONFIG_FRAME_POINTER is not set # # Security options # # CONFIG_SECURITY is not set # # Cryptographic options # # CONFIG_CRYPTO is not set # # Library routines # CONFIG_CRC32=y CONFIG_ZLIB_INFLATE=y CONFIG_ZLIB_DEFLATE=m CONFIG_X86_BIOS_REBOOT=y |
|
From: Gao, K. <kev...@in...> - 2003-03-20 00:41:20
|
Could you please send us your kernel config information,
so that we can track what happens to your kernel.
Thanks
-Kevin
-----Original Message-----
From: Arun Prasad [mailto:ar...@ne...]
Sent: 2003?3?19? 17:06
To: Gao, Kevin
Cc: fau...@li...
Subject: Re: [Fault-injection-developer] fith
Hi Kevin/All,
I downloaded 2.5-fi-extern from Bk... Compiled the kernel and while
booting with this new kernel, I got the below panic...
Mount-cache hash table entries: 512 (order: 0, 4096)
invalid operand: 0000
CPU: 0
EIP: 0060:[<C01214F2>] Not tainted
EFLAGS: 00010286
.................................
..........................
....................
..............
<0> Kernel panic: Attempted to kill the idle task!
In Idle task -not syncing
Does somebody has faced this?? Any workaround for this ??
Thanks
-arun
"Gao, Kevin" wrote:
Hi Arun,
The example for e100 test cases is as folloow:
insert module : fi_core, fi_pf, e100,
# cd ./fith-tool/fith_test/fault_set/e100
#make
# insmod scb_cu_resume.ko
# ficl -i scb_cu_resume.fsml (You should change the "base" parameter to
your own bar address of e100).
# /etc/init.d/network start
Now use command dmesg to see the log info or see the message in
/var/log/messages.
-Kevin
-----Original Message-----
From: Arun Prasad [mailto:ar...@ne...
<mailto:ar...@ne...> ]
Sent: 2003?3?18? 18:12
To: Gao, Kevin
Cc: fau...@li...
Subject: Re: [Fault-injection-developer] fith
Hi Kevin,
Thanks for the response... Iam in the process of downloading the
2.5-fi-extern from BK.
The fault injection test cases for e100 is present along with the fith
utility...That seems to be a good reference for me to start writing test
cases for giga-bit ethernet card (which Iam trying to do...)... But just the
fsml and the code_segments are provided for e100... I couldnt see the
scripts
to use them (like the demo at fith_test dir) . Is that possible to include
the
scripts also in the repository??
Thanks
-arun
"Gao, Kevin" wrote:
> The tree linux-2.5 is out of date.
> So please dowload the newest tree at
> http://fau...@fa.../2.5-fi-extern
<http://fau...@fa.../2.5-fi-extern>
> The new tree includes all interceptors.
>
> The usage of FITH_TOOL is as follow.
>
> We still use tools "ficl"
> You can use parameters as follow:
>
> --attach, -a <modname,file_path>
> attach a module into dbp.
> --detach, -d
> detach all modules that attached to dbp.
> --insert, -i <file.fsml>
> insert a faultset written in file.fsml into FITH.
> --remove, -r {file.fsml|all}
> remove the faultset written in file.fsml or all faultset.
> --help, -h
> help information.
>
> thanks
> -Kevin
>
> -----Original Message-----
> From: Arun Prasad [mailto:ar...@ne...
<mailto:ar...@ne...> ]
> Sent: 2003?3?18? 17:17
> To: fau...@li...
> Subject: [Fault-injection-developer] fith
>
> Hi All,
> To use the fith tool, downloaded the Bitkeeper tool and
> cloned the
> below repositories...
> * fith-tool
> * linux-2.5
> both from fault-injection project.
>
> Now I have to compile and load the "linux-2.5" (above) and
> install
> "fith-tool" on it... Is my assumption right... Because I
> could see
> "2.5-kprobes" in the list of repositories which is again a
> kernel tree....
> It will be helpful if we know the significance of each
> repository..
>
> Please clarify this....
>
> Is there any upto date manual to describe the ficl commands
> and for
> general usage of the tool....
>
> Thanks
> -arun
>
> -------------------------------------------------------
> This SF.net email is sponsored by: Does your code think in ink?
> You could win a Tablet PC. Get a free Tablet PC hat just for playing.
> What are you waiting for?
> http://ads.sourceforge.net/cgi-bin/redirect.pl?micr5043en
<http://ads.sourceforge.net/cgi-bin/redirect.pl?micr5043en>
> _______________________________________________
> Fault-injection-developer mailing list
> Fau...@li...
> https://lists.sourceforge.net/lists/listinfo/fault-injection-developer
<https://lists.sourceforge.net/lists/listinfo/fault-injection-developer>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: Does your code think in ink?
> You could win a Tablet PC. Get a free Tablet PC hat just for playing.
> What are you waiting for?
> http://ads.sourceforge.net/cgi-bin/redirect.pl?micr5043en
<http://ads.sourceforge.net/cgi-bin/redirect.pl?micr5043en>
> _______________________________________________
> Fault-injection-developer mailing list
> Fau...@li...
> https://lists.sourceforge.net/lists/listinfo/fault-injection-developer
<https://lists.sourceforge.net/lists/listinfo/fault-injection-developer>
-------------------------------------------------------
This SF.net email is sponsored by: Does your code think in ink?
You could win a Tablet PC. Get a free Tablet PC hat just for playing.
What are you waiting for?
http://ads.sourceforge.net/cgi-bin/redirect.pl?micr5043en
<http://ads.sourceforge.net/cgi-bin/redirect.pl?micr5043en>
_______________________________________________
Fault-injection-developer mailing list
Fau...@li...
https://lists.sourceforge.net/lists/listinfo/fault-injection-developer
<https://lists.sourceforge.net/lists/listinfo/fault-injection-developer>
|
|
From: Arun P. <ar...@ne...> - 2003-03-19 09:03:14
|
Hi Kevin/All,
I downloaded 2.5-fi-extern from Bk... Compiled the kernel and while booting
with this new kernel, I got the below panic...
Mount-cache hash table entries: 512 (order: 0, 4096)
invalid operand: 0000
CPU: 0
EIP: 0060:[<C01214F2>] Not tainted
EFLAGS: 00010286
.................................
..........................
....................
..............
<0> Kernel panic: Attempted to kill the idle task!
In Idle task -not syncing
Does somebody has faced this?? Any workaround for this ??
Thanks
-arun
"Gao, Kevin" wrote:
> Hi Arun,
>
> The example for e100 test cases is as folloow:
>
> insert module : fi_core, fi_pf, e100,
> # cd ./fith-tool/fith_test/fault_set/e100
> #make
> # insmod scb_cu_resume.ko
> # ficl -i scb_cu_resume.fsml (You should change the "base" parameter to
> your own bar address of e100).
> # /etc/init.d/network start
>
> Now use command dmesg to see the log info or see the message in
> /var/log/messages.
>
> -Kevin
>
> -----Original Message-----
> From: Arun Prasad [mailto:ar...@ne...]
> Sent: 2003?3?18? 18:12
> To: Gao, Kevin
> Cc: fau...@li...
> Subject: Re: [Fault-injection-developer] fith
>
> Hi Kevin,
> Thanks for the response... Iam in the process of downloading the
> 2.5-fi-extern from BK.
> The fault injection test cases for e100 is present along with the fith
> utility...That seems to be a good reference for me to start writing test
> cases for giga-bit ethernet card (which Iam trying to do...)... But just the
> fsml and the code_segments are provided for e100... I couldnt see the
> scripts
> to use them (like the demo at fith_test dir) . Is that possible to include
> the
> scripts also in the repository??
>
> Thanks
> -arun
>
> "Gao, Kevin" wrote:
>
> > The tree linux-2.5 is out of date.
> > So please dowload the newest tree at
> > http://fau...@fa.../2.5-fi-extern
> > The new tree includes all interceptors.
> >
> > The usage of FITH_TOOL is as follow.
> >
> > We still use tools "ficl"
> > You can use parameters as follow:
> >
> > --attach, -a <modname,file_path>
> > attach a module into dbp.
> > --detach, -d
> > detach all modules that attached to dbp.
> > --insert, -i <file.fsml>
> > insert a faultset written in file.fsml into FITH.
> > --remove, -r {file.fsml|all}
> > remove the faultset written in file.fsml or all faultset.
> > --help, -h
> > help information.
> >
> > thanks
> > -Kevin
> >
> > -----Original Message-----
> > From: Arun Prasad [mailto:ar...@ne...]
> > Sent: 2003?3?18? 17:17
> > To: fau...@li...
> > Subject: [Fault-injection-developer] fith
> >
> > Hi All,
> > To use the fith tool, downloaded the Bitkeeper tool and
> > cloned the
> > below repositories...
> > * fith-tool
> > * linux-2.5
> > both from fault-injection project.
> >
> > Now I have to compile and load the "linux-2.5" (above) and
> > install
> > "fith-tool" on it... Is my assumption right... Because I
> > could see
> > "2.5-kprobes" in the list of repositories which is again a
> > kernel tree....
> > It will be helpful if we know the significance of each
> > repository..
> >
> > Please clarify this....
> >
> > Is there any upto date manual to describe the ficl commands
> > and for
> > general usage of the tool....
> >
> > Thanks
> > -arun
> >
> > -------------------------------------------------------
> > This SF.net email is sponsored by: Does your code think in ink?
> > You could win a Tablet PC. Get a free Tablet PC hat just for playing.
> > What are you waiting for?
> > http://ads.sourceforge.net/cgi-bin/redirect.pl?micr5043en
> > _______________________________________________
> > Fault-injection-developer mailing list
> > Fau...@li...
> > https://lists.sourceforge.net/lists/listinfo/fault-injection-developer
> >
> > -------------------------------------------------------
> > This SF.net email is sponsored by: Does your code think in ink?
> > You could win a Tablet PC. Get a free Tablet PC hat just for playing.
> > What are you waiting for?
> > http://ads.sourceforge.net/cgi-bin/redirect.pl?micr5043en
> > _______________________________________________
> > Fault-injection-developer mailing list
> > Fau...@li...
> > https://lists.sourceforge.net/lists/listinfo/fault-injection-developer
>
> -------------------------------------------------------
> This SF.net email is sponsored by: Does your code think in ink?
> You could win a Tablet PC. Get a free Tablet PC hat just for playing.
> What are you waiting for?
> http://ads.sourceforge.net/cgi-bin/redirect.pl?micr5043en
> _______________________________________________
> Fault-injection-developer mailing list
> Fau...@li...
> https://lists.sourceforge.net/lists/listinfo/fault-injection-developer
|
|
From: Gao, K. <kev...@in...> - 2003-03-18 14:54:58
|
Hi Arun,
The example for e100 test cases is as folloow:
insert module : fi_core, fi_pf, e100,
# cd ./fith-tool/fith_test/fault_set/e100
#make
# insmod scb_cu_resume.ko
# ficl -i scb_cu_resume.fsml (You should change the "base" parameter to
your own bar address of e100).
# /etc/init.d/network start
Now use command dmesg to see the log info or see the message in
/var/log/messages.
-Kevin
-----Original Message-----
From: Arun Prasad [mailto:ar...@ne...]
Sent: 2003?3?18? 18:12
To: Gao, Kevin
Cc: fau...@li...
Subject: Re: [Fault-injection-developer] fith
Hi Kevin,
Thanks for the response... Iam in the process of downloading the
2.5-fi-extern from BK.
The fault injection test cases for e100 is present along with the fith
utility...That seems to be a good reference for me to start writing test
cases for giga-bit ethernet card (which Iam trying to do...)... But just the
fsml and the code_segments are provided for e100... I couldnt see the
scripts
to use them (like the demo at fith_test dir) . Is that possible to include
the
scripts also in the repository??
Thanks
-arun
"Gao, Kevin" wrote:
> The tree linux-2.5 is out of date.
> So please dowload the newest tree at
> http://fau...@fa.../2.5-fi-extern
> The new tree includes all interceptors.
>
> The usage of FITH_TOOL is as follow.
>
> We still use tools "ficl"
> You can use parameters as follow:
>
> --attach, -a <modname,file_path>
> attach a module into dbp.
> --detach, -d
> detach all modules that attached to dbp.
> --insert, -i <file.fsml>
> insert a faultset written in file.fsml into FITH.
> --remove, -r {file.fsml|all}
> remove the faultset written in file.fsml or all faultset.
> --help, -h
> help information.
>
> thanks
> -Kevin
>
> -----Original Message-----
> From: Arun Prasad [mailto:ar...@ne...]
> Sent: 2003?3?18? 17:17
> To: fau...@li...
> Subject: [Fault-injection-developer] fith
>
> Hi All,
> To use the fith tool, downloaded the Bitkeeper tool and
> cloned the
> below repositories...
> * fith-tool
> * linux-2.5
> both from fault-injection project.
>
> Now I have to compile and load the "linux-2.5" (above) and
> install
> "fith-tool" on it... Is my assumption right... Because I
> could see
> "2.5-kprobes" in the list of repositories which is again a
> kernel tree....
> It will be helpful if we know the significance of each
> repository..
>
> Please clarify this....
>
> Is there any upto date manual to describe the ficl commands
> and for
> general usage of the tool....
>
> Thanks
> -arun
>
> -------------------------------------------------------
> This SF.net email is sponsored by: Does your code think in ink?
> You could win a Tablet PC. Get a free Tablet PC hat just for playing.
> What are you waiting for?
> http://ads.sourceforge.net/cgi-bin/redirect.pl?micr5043en
> _______________________________________________
> Fault-injection-developer mailing list
> Fau...@li...
> https://lists.sourceforge.net/lists/listinfo/fault-injection-developer
>
> -------------------------------------------------------
> This SF.net email is sponsored by: Does your code think in ink?
> You could win a Tablet PC. Get a free Tablet PC hat just for playing.
> What are you waiting for?
> http://ads.sourceforge.net/cgi-bin/redirect.pl?micr5043en
> _______________________________________________
> Fault-injection-developer mailing list
> Fau...@li...
> https://lists.sourceforge.net/lists/listinfo/fault-injection-developer
|
|
From: Arun P. <ar...@ne...> - 2003-03-18 10:09:31
|
Hi Kevin,
Thanks for the response... Iam in the process of downloading the
2.5-fi-extern from BK.
The fault injection test cases for e100 is present along with the fith
utility...That seems to be a good reference for me to start writing test
cases for giga-bit ethernet card (which Iam trying to do...)... But just the
fsml and the code_segments are provided for e100... I couldnt see the scripts
to use them (like the demo at fith_test dir) . Is that possible to include the
scripts also in the repository??
Thanks
-arun
"Gao, Kevin" wrote:
> The tree linux-2.5 is out of date.
> So please dowload the newest tree at
> http://fau...@fa.../2.5-fi-extern
> The new tree includes all interceptors.
>
> The usage of FITH_TOOL is as follow.
>
> We still use tools "ficl"
> You can use parameters as follow:
>
> --attach, -a <modname,file_path>
> attach a module into dbp.
> --detach, -d
> detach all modules that attached to dbp.
> --insert, -i <file.fsml>
> insert a faultset written in file.fsml into FITH.
> --remove, -r {file.fsml|all}
> remove the faultset written in file.fsml or all faultset.
> --help, -h
> help information.
>
> thanks
> -Kevin
>
> -----Original Message-----
> From: Arun Prasad [mailto:ar...@ne...]
> Sent: 2003?3?18? 17:17
> To: fau...@li...
> Subject: [Fault-injection-developer] fith
>
> Hi All,
> To use the fith tool, downloaded the Bitkeeper tool and
> cloned the
> below repositories...
> * fith-tool
> * linux-2.5
> both from fault-injection project.
>
> Now I have to compile and load the "linux-2.5" (above) and
> install
> "fith-tool" on it... Is my assumption right... Because I
> could see
> "2.5-kprobes" in the list of repositories which is again a
> kernel tree....
> It will be helpful if we know the significance of each
> repository..
>
> Please clarify this....
>
> Is there any upto date manual to describe the ficl commands
> and for
> general usage of the tool....
>
> Thanks
> -arun
>
> -------------------------------------------------------
> This SF.net email is sponsored by: Does your code think in ink?
> You could win a Tablet PC. Get a free Tablet PC hat just for playing.
> What are you waiting for?
> http://ads.sourceforge.net/cgi-bin/redirect.pl?micr5043en
> _______________________________________________
> Fault-injection-developer mailing list
> Fau...@li...
> https://lists.sourceforge.net/lists/listinfo/fault-injection-developer
>
> -------------------------------------------------------
> This SF.net email is sponsored by: Does your code think in ink?
> You could win a Tablet PC. Get a free Tablet PC hat just for playing.
> What are you waiting for?
> http://ads.sourceforge.net/cgi-bin/redirect.pl?micr5043en
> _______________________________________________
> Fault-injection-developer mailing list
> Fau...@li...
> https://lists.sourceforge.net/lists/listinfo/fault-injection-developer
|
|
From: Gao, K. <kev...@in...> - 2003-03-18 09:29:25
|
The tree linux-2.5 is out of date.
So please dowload the newest tree at
http://fau...@fa.../2.5-fi-extern
The new tree includes all interceptors.
The usage of FITH_TOOL is as follow.
We still use tools "ficl"
You can use parameters as follow:
--attach, -a <modname,file_path>
attach a module into dbp.
--detach, -d
detach all modules that attached to dbp.
--insert, -i <file.fsml>
insert a faultset written in file.fsml into FITH.
--remove, -r {file.fsml|all}
remove the faultset written in file.fsml or all faultset.
--help, -h
help information.
thanks
-Kevin
-----Original Message-----
From: Arun Prasad [mailto:ar...@ne...]
Sent: 2003?3?18? 17:17
To: fau...@li...
Subject: [Fault-injection-developer] fith
Hi All,
To use the fith tool, downloaded the Bitkeeper tool and
cloned the
below repositories...
* fith-tool
* linux-2.5
both from fault-injection project.
Now I have to compile and load the "linux-2.5" (above) and
install
"fith-tool" on it... Is my assumption right... Because I
could see
"2.5-kprobes" in the list of repositories which is again a
kernel tree....
It will be helpful if we know the significance of each
repository..
Please clarify this....
Is there any upto date manual to describe the ficl commands
and for
general usage of the tool....
Thanks
-arun
-------------------------------------------------------
This SF.net email is sponsored by: Does your code think in ink?
You could win a Tablet PC. Get a free Tablet PC hat just for playing.
What are you waiting for?
http://ads.sourceforge.net/cgi-bin/redirect.pl?micr5043en
_______________________________________________
Fault-injection-developer mailing list
Fau...@li...
https://lists.sourceforge.net/lists/listinfo/fault-injection-developer
|
|
From: Arun P. <ar...@ne...> - 2003-03-18 09:14:52
|
Hi All,
To use the fith tool, downloaded the Bitkeeper tool and
cloned the
below repositories...
* fith-tool
* linux-2.5
both from fault-injection project.
Now I have to compile and load the "linux-2.5" (above) and
install
"fith-tool" on it... Is my assumption right... Because I
could see
"2.5-kprobes" in the list of repositories which is again a
kernel tree....
It will be helpful if we know the significance of each
repository..
Please clarify this....
Is there any upto date manual to describe the ficl commands
and for
general usage of the tool....
Thanks
-arun
|
|
From: Arun P. <ar...@ne...> - 2003-03-14 04:39:52
|
|
From: Stanley W. <sta...@li...> - 2003-03-11 08:44:15
|
On Tue, 11 Mar 2003, Greg KH wrote: > On Tue, Mar 11, 2003 at 04:22:40PM +0800, Stanley Wang wrote: > > On Mon, 10 Mar 2003, Greg KH wrote: > > > > > On Fri, Mar 07, 2003 at 12:05:45PM +0800, Stanley Wang wrote: > > > > I've completed a mock e100 CPCI peripheral board based on FITH > > > > project(http://fault-injection.sourceforge.net/). It would intercept all > > > > pci config access and could be used to test CPCI hotswap driver without real > > > > hardware support. > > > > > > You say, "Could be used". Does that mean you have used it in such a > > > manner? And does that mean that other pci hotplug drivers could be > > > tested with a modification of this framework? > > Certainly. I could use it to trigger an insertion/extraction event at any time. > > You could also list this mock peripheral board by "lspci" after it was inserted. > > I just implement the HotSwap part of the mock peripheral board, and you could > > let it be any device you want. > > Ah, very nice. > > > This simulator is based on FITH. FITH provides ability to intercept and > > inject faults into any PIO/MMIO access or IRQ handler. Hence we could emulate a > > real device easily by intercept serval PIO/MMIO/IRQ. > > That's pretty cool. We could create up some virtual USB controllers, > which control virtual USB devices, to really beat on the USB stack for > example, right? Sure. > Are there any groups writing these kinds of "fake device" drivers? I think FITH's team may do this. FITH's team leader is Louis Zhuang(lou...@in...) Best Regards, Stan -- Opinions expressed are those of the author and do not represent Intel Corporation |
|
From: Louis Z. <lou...@li...> - 2003-03-11 08:40:43
|
Dear Greg, You can find all these stuffs in our BK tree. And more, you can download Stanley's mock e100 in our home page. If you'd like to do, we can help you to write mock USB controller ;-) On Tue, 2003-03-11 at 16:25, Greg KH wrote: > That's pretty cool. We could create up some virtual USB controllers, > which control virtual USB devices, to really beat on the USB stack for > example, right? > > Are there any groups writing these kinds of "fake device" drivers? > > thanks, -- Yours truly, Louis Zhuang --------------- Fault Injection Test Harness Project BK tree: http://fault-injection.bkbits.net/linux-2.5 Home Page: http://sf.net/projects/fault-injection |
|
From: Greg KH <gr...@kr...> - 2003-03-11 08:35:39
|
On Tue, Mar 11, 2003 at 04:22:40PM +0800, Stanley Wang wrote: > On Mon, 10 Mar 2003, Greg KH wrote: > > > On Fri, Mar 07, 2003 at 12:05:45PM +0800, Stanley Wang wrote: > > > I've completed a mock e100 CPCI peripheral board based on FITH > > > project(http://fault-injection.sourceforge.net/). It would intercept all > > > pci config access and could be used to test CPCI hotswap driver without real > > > hardware support. > > > > You say, "Could be used". Does that mean you have used it in such a > > manner? And does that mean that other pci hotplug drivers could be > > tested with a modification of this framework? > Certainly. I could use it to trigger an insertion/extraction event at any time. > You could also list this mock peripheral board by "lspci" after it was inserted. > I just implement the HotSwap part of the mock peripheral board, and you could > let it be any device you want. Ah, very nice. > This simulator is based on FITH. FITH provides ability to intercept and > inject faults into any PIO/MMIO access or IRQ handler. Hence we could emulate a > real device easily by intercept serval PIO/MMIO/IRQ. That's pretty cool. We could create up some virtual USB controllers, which control virtual USB devices, to really beat on the USB stack for example, right? Are there any groups writing these kinds of "fake device" drivers? thanks, greg k-h |
25 messages has been excluded from this view by a project administrator.
