lkml.org 
[lkml]   [1998]   [Dec]   [18]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: "Aiee: scheduling in interrupt 00111dd2" problem
Am I right to say that the locking structures are mainly used to prevent
race conditions. Why does the kernel hang when some of these are broken?

8-) CCFoo

On Thu, 17 Dec 1998, Rik van Riel wrote:

> On Thu, 17 Dec 1998, Foo Chun Choong wrote:
>
> > After modifying some networking code in Linux 2.0.34, I
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> > occasionally get this message "Aiee: scheduling in interrupt
> > 00111dd2" and then the kernel hangs. What are the possible causes
> > of this problem, and what are the ways to solve this problem?
>
> Well, I guess you already gave the answer :))
>
> You probably broke some locking structures or something
> like that -- it's very well possible that 2.0.36 has the
> stuff you 'fixed' included in a proper way -- you might
> want to check that out.
>
> As you've experienced yourself, kernel code can be very
> complex -- not something to do a quick hack on as an
> already-busy sysadmin or whatever...
>
> cheers,
>
> Rik -- the flu hits, the flu hits, the flu hits -- MORE
> +-------------------------------------------------------------------+
> | Linux memory management tour guide. H.H.vanRiel@phys.uu.nl |
> | Scouting Vries cubscout leader. http://www.phys.uu.nl/~riel/ |
> +-------------------------------------------------------------------+
>
>



-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 13:46    [from the cache]
©2003-2014 Jasper Spaans. Advertise on this site