2004-01-28 13:59:48

by Oliver Feiler

[permalink] [raw]
Subject: 2.6.1-rc2 + aha152x still oopses

Hi,

this is related to my post from Jan 7th, see
http://lkml.org/lkml/2004/1/6/202.

The Oops in the aha152x driver was supposed to be fixed in 2.6.1-rc1 from what
I was told. I've been running 2.6.1-rc2 and indeed it didn't happen with that
kernel. Today however I got a slightly different oops with the same kernel. I
didn't see any changes to the driver since 2.6.1-rc2 so I didn't upgrade
(takes a long time to compile on a 486).

I got two oopses which I attached to this mail. After that the system needed
to be resetted. Is this a new problem or did I just miss changes to the
driver and it is already fixed in 2.6.2-rc2?

Bye,
Oliver

--
Oliver Feiler <kiza@(kcore.de|lionking.org|gmx[pro].net)>


Attachments:
(No filename) (714.00 B)
ksymoops (6.52 kB)
Download all attachments

2004-01-29 21:01:38

by Randy.Dunlap

[permalink] [raw]
Subject: Re: 2.6.1-rc2 + aha152x still oopses

Hi,

The aha152x maintainer (Juergen E. Fischer) has already replied:

No, that was an other bug. Try attached patch. I already submitted it
to Andrew Morton and expect it to appear in 2.6.2.



On Thu, 29 Jan 2004 21:06:16 +0100 (CET) Guennadi Liakhovetski <[email protected]> wrote:

| I am forwarding your email to linux-scsi. Besides, there has been some
| fixes merged recently in 2.6.2-rcX, try the latest available. However, not
| sure if your specific problem has been fixed there.
|
| Guennadi
|
| On Wed, 28 Jan 2004, Oliver Feiler wrote:
|
| > Hi,
| >
| > this is related to my post from Jan 7th, see
| > http://lkml.org/lkml/2004/1/6/202.
| >
| > The Oops in the aha152x driver was supposed to be fixed in 2.6.1-rc1 from what
| > I was told. I've been running 2.6.1-rc2 and indeed it didn't happen with that
| > kernel. Today however I got a slightly different oops with the same kernel. I
| > didn't see any changes to the driver since 2.6.1-rc2 so I didn't upgrade
| > (takes a long time to compile on a 486).
| >
| > I got two oopses which I attached to this mail. After that the system needed
| > to be resetted. Is this a new problem or did I just miss changes to the
| > driver and it is already fixed in 2.6.2-rc2?
| >
| > Bye,
| > Oliver
| >
| > --
| > Oliver Feiler <kiza@(kcore.de|lionking.org|gmx[pro].net)>
| >
|
| ---
| Guennadi Liakhovetski

--
~Randy
kernel-janitors project: http://janitor.kernelnewbies.org/

2004-01-29 20:52:44

by Guennadi Liakhovetski

[permalink] [raw]
Subject: Re: 2.6.1-rc2 + aha152x still oopses

I am forwarding your email to linux-scsi. Besides, there has been some
fixes merged recently in 2.6.2-rcX, try the latest available. However, not
sure if your specific problem has been fixed there.

Guennadi

On Wed, 28 Jan 2004, Oliver Feiler wrote:

> Hi,
>
> this is related to my post from Jan 7th, see
> http://lkml.org/lkml/2004/1/6/202.
>
> The Oops in the aha152x driver was supposed to be fixed in 2.6.1-rc1 from what
> I was told. I've been running 2.6.1-rc2 and indeed it didn't happen with that
> kernel. Today however I got a slightly different oops with the same kernel. I
> didn't see any changes to the driver since 2.6.1-rc2 so I didn't upgrade
> (takes a long time to compile on a 486).
>
> I got two oopses which I attached to this mail. After that the system needed
> to be resetted. Is this a new problem or did I just miss changes to the
> driver and it is already fixed in 2.6.2-rc2?
>
> Bye,
> Oliver
>
> --
> Oliver Feiler <kiza@(kcore.de|lionking.org|gmx[pro].net)>
>

---
Guennadi Liakhovetski


2004-01-29 21:26:07

by Oliver Feiler

[permalink] [raw]
Subject: Re: 2.6.1-rc2 + aha152x still oopses

On Thursday 29 January 2004 21:56, Randy.Dunlap wrote:
> Hi,
>
> The aha152x maintainer (Juergen E. Fischer) has already replied:
>
> No, that was an other bug. Try attached patch. I already submitted it
> to Andrew Morton and expect it to appear in 2.6.2.

Yes, I got a couple of patches from J?rgen and that fixed the Oops. The driver
works just fine now for me.

Bye,
Oliver

--
Oliver Feiler <kiza@(kcore.de|lionking.org|gmx[pro].net)>