Thread: [Fault-injection-developer] RE: e100 frame reception test result draft.
Status: Alpha
Brought to you by:
rustyl
Menu
▾
▴
fault-injection-developer
|
From: Wang, S. <sta...@in...> - 2003-02-19 09:38:05
|
=20 -----Original Message----- From: Gao, Kevin=20 Sent: 2003-02-19 17:01 To: Zhuang, Louis; Wang, Frank; Wang, Stanley Subject: e100 frame reception test result draft. E100 frame reception test has been done, the result draft is as follow: any comment? :) =20 -Kevin =20 1. Set =A1=AES=A1=AF bit of RFD which is under received when driver = reads the SCB status register. Driver always send a RU_START command.=20 =20 OK. The e100 driver checks the hardware status and reacts properly :) =20 2. Set =A1=AES=A1=AF bit of RFD which has been received when driver = reads the SCB status register. Driver ignores the operation.=20 =20 OK. The 'S' bit is set by driver and read by hardware. Hence the driver doesn't care it.=20 <?xml:namespace prefix =3D o ns =3D = "urn:schemas-microsoft-com:office:office" /> 3. Set both =A1=AEC=A1=AF and =A1=AEOK=A1=AF bit of RFD to zero = when driver reads the SCB status register, the network cannot start, and driver will hanged, = a timeout will throw out.=20 If the 'C' bit equals zero, the driver will treat this rfd as an = incomplete packet and just wait untile 'C' equals one.=20 =20 4. Set =A1=AEC=A1=AF bit of RFD to 0, and set =A1=AEOK=A1=AF bit of = RFD to 1 when driver reads the SCB status register, the result is the same as process 2.=20 =20 process 2 or 3 ? =20 =20 5. Set =A1=AEC=A1=AF bit of RFD to 1, and set =A1=AEOK=A1=AF bit of = RFD to 0 when driver reads the SCB status register, the result is the same as process 2.=20 =20 process 2 or 3 ?=20 =20 6. Set =A1=AECRC=A1=AF bit of RFD to 1 when driver reads the SCB = status register, the driver ignores this operation.=20 =20 The driver should check this bit. =20 =20 7. Set =A1=AEAlignment error=A1=AF bit of RFD to 1 when driver = reads the SCB status register, the driver ignores this operation.=20 =20 The driver should check this bit.=20 =20 8. Set =A1=AERun out of buffer=A1=AF bit of RFD to 1 when driver = reads the SCB status register, the driver ignores this operation. =20 The driver should check this bit. 9. Set =A1=AEFrame too short=A1=AF bit of RFD to 1 when driver = reads the SCB status register, the driver ignores this operation. The driver should check this bit. =20 =20 =20 |
|
From: Rusty L. <ru...@li...> - 2003-02-19 16:22:18
|
Kevin,
Could you publish a test plan with detailed test procedures for
recreating your e100 test cases. For the purposes of the fault
injection project, it is actually more valuable to see a practical
example of how to utilize the fault injection features to perform useful
device driver testing then it is to publish the results of testing. =20
(Don't get me wrong, test results are a good thing, especially if you
find a reproducible bug.)
--rustyl
On Wed, 2003-02-19 at 01:35, Wang, Stanley wrote:
> =20
>=20
> -----Original Message-----
> From: Gao, Kevin=20
> Sent: 2003-02-19 17:01
> To: Zhuang, Louis; Wang, Frank; Wang, Stanley
> Subject: e100 frame reception test result draft.
>=20
>=20
> E100 frame reception test has been done, the result draft is as follow:
>=20
> any comment? :)
>=20
> =20
>=20
> -Kevin
>=20
> =20
>=20
> 1. Set =E2=80=98S=E2=80=99 bit of RFD which is under received when dr=
iver reads the
> SCB status register. Driver always send a RU_START command.=20
>=20
> =20
>=20
> OK. The e100 driver checks the hardware status and reacts properly :)
>=20
> =20
>=20
> 2. Set =E2=80=98S=E2=80=99 bit of RFD which has been received when dr=
iver reads the
> SCB status register. Driver ignores the operation.=20
>=20
> =20
>=20
> OK. The 'S' bit is set by driver and read by hardware. Hence the driver
> doesn't care it.=20
>=20
> <?xml:namespace prefix =3D o ns =3D "urn:schemas-microsoft-com:office:off=
ice" />
>=20
>=20
> 3. Set both =E2=80=98C=E2=80=99 and =E2=80=98OK=E2=80=99 bit of RFD t=
o zero when driver reads the
> SCB status register, the network cannot start, and driver will hanged, a
> timeout will throw out.=20
>=20
> If the 'C' bit equals zero, the driver will treat this rfd as an incomple=
te
> packet and just wait untile 'C' equals one.=20
>=20
> =20
>=20
> 4. Set =E2=80=98C=E2=80=99 bit of RFD to 0, and set =E2=80=98OK=E2=80=
=99 bit of RFD to 1 when driver
> reads the SCB status register, the result is the same as process 2.=20
>=20
> =20
>=20
> process 2 or 3 ?
>=20
> =20
>=20
> =20
>=20
> 5. Set =E2=80=98C=E2=80=99 bit of RFD to 1, and set =E2=80=98OK=E2=80=
=99 bit of RFD to 0 when driver
> reads the SCB status register, the result is the same as process 2.=20
>=20
> =20
>=20
> process 2 or 3 ?=20
>=20
> =20
>=20
> 6. Set =E2=80=98CRC=E2=80=99 bit of RFD to 1 when driver reads the SC=
B status
> register, the driver ignores this operation.=20
>=20
> =20
>=20
> The driver should check this bit.
>=20
> =20
>=20
> =20
>=20
> 7. Set =E2=80=98Alignment error=E2=80=99 bit of RFD to 1 when driver =
reads the SCB
> status register, the driver ignores this operation.=20
>=20
> =20
>=20
> The driver should check this bit.=20
>=20
> =20
>=20
> 8. Set =E2=80=98Run out of buffer=E2=80=99 bit of RFD to 1 when drive=
r reads the SCB
> status register, the driver ignores this operation.
>=20
> =20
>=20
> The driver should check this bit.
>=20
> 9. Set =E2=80=98Frame too short=E2=80=99 bit of RFD to 1 when driver =
reads the SCB
> status register, the driver ignores this operation.
>=20
> The driver should check this bit.
> =20
> =20
> =20
>=20
|
|
From: Mark H. <ma...@os...> - 2003-02-19 16:28:11
|
On Tue, 2003-02-18 at 16:12, Rusty Lynch wrote: > Kevin, >=20 > Could you publish a test plan with detailed test procedures for > recreating your e100 test cases. For the purposes of the fault > injection project, it is actually more valuable to see a practical > example of how to utilize the fault injection features to perform usefu= l > device driver testing then it is to publish the results of testing. =20 If that includes the code too, that would be great. I'm interested in seeing how a test of a driver is implemented. Mark. >=20 > (Don't get me wrong, test results are a good thing, especially if you > find a reproducible bug.) >=20 > --rustyl >=20 > On Wed, 2003-02-19 at 01:35, Wang, Stanley wrote: > > =20 > >=20 > > -----Original Message----- > > From: Gao, Kevin=20 > > Sent: 2003-02-19 17:01 > > To: Zhuang, Louis; Wang, Frank; Wang, Stanley > > Subject: e100 frame reception test result draft. > >=20 > >=20 > > E100 frame reception test has been done, the result draft is as follo= w: > >=20 > > any comment? :) > >=20 > > =20 > >=20 > > -Kevin > >=20 > > =20 > >=20 > > 1. Set =91S=92 bit of RFD which is under received when driver rea= ds the > > SCB status register. Driver always send a RU_START command.=20 > >=20 > > =20 > >=20 > > OK. The e100 driver checks the hardware status and reacts properly := ) > >=20 > > =20 > >=20 > > 2. Set =91S=92 bit of RFD which has been received when driver rea= ds the > > SCB status register. Driver ignores the operation.=20 > >=20 > > =20 > >=20 > > OK. The 'S' bit is set by driver and read by hardware. Hence the driv= er > > doesn't care it.=20 > >=20 > > <?xml:namespace prefix =3D o ns =3D "urn:schemas-microsoft-com:office= :office" /> > >=20 > >=20 > > 3. Set both =91C=92 and =91OK=92 bit of RFD to zero when driver r= eads the > > SCB status register, the network cannot start, and driver will hanged= , a > > timeout will throw out.=20 > >=20 > > If the 'C' bit equals zero, the driver will treat this rfd as an inco= mplete > > packet and just wait untile 'C' equals one.=20 > >=20 > > =20 > >=20 > > 4. Set =91C=92 bit of RFD to 0, and set =91OK=92 bit of RFD to 1 = when driver > > reads the SCB status register, the result is the same as process 2.=20 > >=20 > > =20 > >=20 > > process 2 or 3 ? > >=20 > > =20 > >=20 > > =20 > >=20 > > 5. Set =91C=92 bit of RFD to 1, and set =91OK=92 bit of RFD to 0 = when driver > > reads the SCB status register, the result is the same as process 2.=20 > >=20 > > =20 > >=20 > > process 2 or 3 ?=20 > >=20 > > =20 > >=20 > > 6. Set =91CRC=92 bit of RFD to 1 when driver reads the SCB status > > register, the driver ignores this operation.=20 > >=20 > > =20 > >=20 > > The driver should check this bit. > >=20 > > =20 > >=20 > > =20 > >=20 > > 7. Set =91Alignment error=92 bit of RFD to 1 when driver reads th= e SCB > > status register, the driver ignores this operation.=20 > >=20 > > =20 > >=20 > > The driver should check this bit.=20 > >=20 > > =20 > >=20 > > 8. Set =91Run out of buffer=92 bit of RFD to 1 when driver reads = the SCB > > status register, the driver ignores this operation. > >=20 > > =20 > >=20 > > The driver should check this bit. > >=20 > > 9. Set =91Frame too short=92 bit of RFD to 1 when driver reads th= e SCB > > status register, the driver ignores this operation. > >=20 > > The driver should check this bit. > > =20 > > =20 > > =20 > >=20 >=20 >=20 >=20 >=20 > ------------------------------------------------------- > This SF.net email is sponsored by: SlickEdit Inc. Develop an edge. > The most comprehensive and flexible code editor you can use. > Code faster. C/C++, C#, Java, HTML, XML, many more. FREE 30-Day Trial. > www.slickedit.com/sourceforge > _______________________________________________ > Fault-injection-developer mailing list > Fau...@li... > https://lists.sourceforge.net/lists/listinfo/fault-injection-developer --=20 Mark Haverkamp <ma...@os...> |
|
From: Rusty L. <ru...@li...> - 2003-02-19 16:40:26
|
On Wed, 2003-02-19 at 08:26, Mark Haverkamp wrote: > On Tue, 2003-02-18 at 16:12, Rusty Lynch wrote: > > Kevin, > > > > Could you publish a test plan with detailed test procedures for > > recreating your e100 test cases. For the purposes of the fault > > injection project, it is actually more valuable to see a practical > > example of how to utilize the fault injection features to perform useful > > device driver testing then it is to publish the results of testing. > > If that includes the code too, that would be great. I'm interested in > seeing how a test of a driver is implemented. > > Mark. > Ah, yes. Code is a must, even if it is a shell script that is reading/writing to sysfs files. As a mater of fact, lets aim for all test cases to be suitable for inclusion into LTP (http://ltp.sourceforge.net) which has some not so strict guidelines for how to create a test case. --rustyl |
|
From: Louis Z. <lou...@li...> - 2003-02-20 00:25:58
|
On Thu, 2003-02-20 at 00:26, Mark Haverkamp wrote: > If that includes the code too, that would be great. I'm interested in > seeing how a test of a driver is implemented. As you wish, test code are there (and simple). ;-) - Louis |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X