[prev in list] [next in list] [prev in thread] [next in thread] 

List:       linux-scsi
Subject:    Re: Bug report
From:       Alan Cox <alan () lxorguk ! ukuu ! org ! uk>
Date:       1999-12-29 22:14:40
[Download RAW message or body]

>    scheduling_in_interrupt:
>            printk("Scheduling in interrupt\n");
>            *(int *)0 = 0;
>            return;
>    }
> 
> It seems like the problem is that schedule() is called during an
> interrupt. Now how would this ever happen?
> 

This normally comes from a device driver bug. The backtrace in this case can
be very important as you should see

	schedule
	some_func
	some_func
	driver_func
	driver_func
	irq entry point

down the stack

>  #undef __FD_SETSIZE
> -#define __FD_SETSIZE	1024
> +#define __FD_SETSIZE	4096

These are bad things to play with in the kernel. You can get stack overruns
and very weird traces from messing with them. Later 2.2.x has no silly limits


-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.rutgers.edu

[prev in list] [next in list] [prev in thread] [next in thread]