I can compile ac-5 fine but when trying to boot I get the following
error:
kernel BUG at ide-cd.c:790!
invalid operand: 0000
I am running 2.4.19pre3 without a problem. I didn't have a way (as far
as I know) to get the full panic output but I can copy by hand and post
here if needed.
Have a good one,
Steve
On 21 Mar 2002, Stephen Williams wrote:
> I can compile ac-5 fine but when trying to boot I get the following
> error:
>
> kernel BUG at ide-cd.c:790!
> invalid operand: 0000
>
> I am running 2.4.19pre3 without a problem. I didn't have a way (as far
> as I know) to get the full panic output but I can copy by hand and post
> here if needed.
>
> Have a good one,
> Steve
It is a BUG() check to see if there are cases where the interrupt handler
is being set (re armed) while it is currently set for another event.
if (HWGROUP(drive)->handler != NULL)
BUG();
ide_set_handler(drive, handler, timeout, expirey);
If we are reloading the handler but it was set but something else , never
called during a completion, and/or is dangling. It is a typo my bad :-(
Edit and change it from "==" to "!="
Apology for the typo folks.
Cheers,
Andre Hedrick
LAD Storage Consulting Group
On Thu, Mar 21, 2002 at 09:23:36PM -0800, Andre Hedrick wrote:
> It is a BUG() check to see if there are cases where the interrupt handler
> is being set (re armed) while it is currently set for another event.
>
> if (HWGROUP(drive)->handler != NULL)
> BUG();
> ide_set_handler(drive, handler, timeout, expirey);
>
> If we are reloading the handler but it was set but something else , never
> called during a completion, and/or is dangling. It is a typo my bad :-(
>
> Edit and change it from "==" to "!="
Now I'm confused. Should that be != to ==? :) And every instance I find?
--
SOCCER PLAYER IN GENITAL-BITING SCANDAL --- "It was something between
friends that I thought would have no importance until this morning when
I got up and saw all the commotion in the news," Gallardo told a news
conference. "It stunned me."
Reyes told Marca that he had "felt a slight pinch."
-- http://www.azcentral.com/offbeat/articles/1129soccer29-ON.html
NO, just that one line 790
Cheers,
Andre Hedrick
LAD Storage Consulting Group
On Fri, 22 Mar 2002, CaT wrote:
> On Thu, Mar 21, 2002 at 09:23:36PM -0800, Andre Hedrick wrote:
> > It is a BUG() check to see if there are cases where the interrupt handler
> > is being set (re armed) while it is currently set for another event.
> >
> > if (HWGROUP(drive)->handler != NULL)
> > BUG();
> > ide_set_handler(drive, handler, timeout, expirey);
> >
> > If we are reloading the handler but it was set but something else , never
> > called during a completion, and/or is dangling. It is a typo my bad :-(
> >
> > Edit and change it from "==" to "!="
>
> Now I'm confused. Should that be != to ==? :) And every instance I find?
>
> --
> SOCCER PLAYER IN GENITAL-BITING SCANDAL --- "It was something between
> friends that I thought would have no importance until this morning when
> I got up and saw all the commotion in the news," Gallardo told a news
> conference. "It stunned me."
> Reyes told Marca that he had "felt a slight pinch."
> -- http://www.azcentral.com/offbeat/articles/1129soccer29-ON.html
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to [email protected]
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
On Thu, Mar 21, 2002 at 09:23:36PM -0800, Andre Hedrick wrote:
> if (HWGROUP(drive)->handler != NULL)
> Edit and change it from "==" to "!="
What's wrong with this picture 8-)
--
| Dave Jones. http://www.codemonkey.org.uk
| SuSE Labs
Worked like a champ, thank's Andre!
Steve
From: Andre Hedrick [mailto:[email protected]]
Sent: Thursday, March 21, 2002 11:24 PM
To: Stephen Williams
Cc: [email protected]
Subject: Re: Linux-2.4.19pre3-ac5
On 21 Mar 2002, Stephen Williams wrote:
> I can compile ac-5 fine but when trying to boot I get the following
> error:
>
> kernel BUG at ide-cd.c:790!
> invalid operand: 0000
>
> I am running 2.4.19pre3 without a problem. I didn't have a way (as
far
> as I know) to get the full panic output but I can copy by hand and
post
> here if needed.
>
> Have a good one,
> Steve
It is a BUG() check to see if there are cases where the interrupt
handler
is being set (re armed) while it is currently set for another event.
if (HWGROUP(drive)->handler != NULL)
BUG();
ide_set_handler(drive, handler, timeout, expirey);
If we are reloading the handler but it was set but something else ,
never
called during a completion, and/or is dangling. It is a typo my bad :-(
Edit and change it from "==" to "!="
Apology for the typo folks.
Cheers,
Andre Hedrick
LAD Storage Consulting Group