Messages in this thread | | | From | (Paul Gortmaker) | Subject | Re: Hard Lockup on 2.1.106 (bogus uart401 base) | Date | Tue, 16 Jun 1998 02:34:35 +1000 (EST) |
| |
> > applied 2.1.106ac1, played a sound file and got: > > Too much work in interrupt on uart401 (0x6E756F53). UART jabbering?? > > Ok that means the sound completion causes the sb uart401 chip to flag > an interrupt request and the uart401 interrupt routine to get called. > > You've also caught the real bug - the hex value in brackets is the I/O > port it thinks the uart401 is at. This indicates that the dev_id passed > was wrong. Now I can go see why
Wheee. Surprised it didn't grenade in a more spectacular fashion :)
If the problem isnt obvious then perhaps something like:
typedef struct uart401_devc {
+ int magic; int base; int irq; int *osp;
and associated checks will be worthwhile?
Paul.
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu
| |