On Tue, 5 Dec 2000 18:40:00 -0500 , Boerner, Brian <[EMAIL PROTECTED]> wrote:
> I get another oops. I'm not very efficient at reading these messages. To bad
> the oops-tracing.txt file isn't in a little more detail. It seems you have
> to be quite knowledgeable of the inner workings of the Linux
You folks seem to be interested in this, so I thought I might bother for a
bit of follow up.
I would like to start off by thanking each of you for responding. I guess I
got into the 2.4 game a bit late and haven't been on linux-kernel in quite a
while. If anyone has any ideas on what I'm doing wr
Keith Owens wrote:
>
> On Mon, 4 Dec 2000 17:31:04 -0500 ,
> "Boerner, Brian" <[EMAIL PROTECTED]> wrote:
> >The driver
> >is generating a segmentation fault and produces and oops. I have included
> >Code: 00 00 00 00 00 00 00 00 b8 00 00 00 83 ec 34 68 00 2c 82 c8
>
> That code looks bad. I sus
Andi Kleen writes:
> On Mon, Dec 04, 2000 at 05:31:04PM -0500, Boerner, Brian wrote:
> > EIP:0010:[]
Note the value of EIP, and compare it with the structure size of
"struct module".
> > Code: 00 00 00 00 00 00 00 00 b8 00 00 00 83 ec 34 68 00 2c 82 c8
> ^^^
>...
On Mon, 4 Dec 2000 17:31:04 -0500 ,
"Boerner, Brian" <[EMAIL PROTECTED]> wrote:
>The driver
>is generating a segmentation fault and produces and oops. I have included
>Code: 00 00 00 00 00 00 00 00 b8 00 00 00 83 ec 34 68 00 2c 82 c8
That code looks bad. I suspect you are using an old modutils
On Mon, Dec 04, 2000 at 05:31:04PM -0500, Boerner, Brian wrote:
> EIP:0010:[]
> Using defaults from ksymoops -t elf32-i386 -a i386
> EFLAGS: 00010286
> eax: 0025 ebx: c881c000 ecx: edx:
^
> esi: 0001 edi: ebp: c88296a0 esp: c6b51e74
Many of you, specifically customers of Dell Computer have been asking about
the aacraid driver and the 2.4.0 kernel. Development is underway, however I
have run into a stumbling block and am not sure how to proceed. The driver
is generating a segmentation fault and produces and oops. I have includ
7 matches
Mail list logo
