Messages in this thread | | | From | (Alan Cox) | Subject | Re: 2.0.34 Kernel panics / Problems | Date | Tue, 9 Jun 1998 13:19:09 +0100 (BST) |
| |
> CPU: 0 > EIP: 0010:[ip_alias:ip_alias_print_1+-56889/44]
Basically it jumped to fishkill
> EFLAGS: 00010006 > eax: 39393939 ebx: 00000000 ecx: 00000008 edx: 00000018 ^^^^^^^^^^^^^^ ascii '9999'
> Call Trace: [do_fast_IRQ+42/76] [fast_IRQ10_interrupt+65/112] [ext2_match+95/100] [ext2_find_entry+459/716] [ext2_lookup+343/368] [ext2_lookup+256/368] [lookup+222/248] > [_namei+90/228] [namei+48/72] [sys_access+104/176] [system_call+85/124] > Code: 83 78 0c 00 74 09 50 8b 40 24 ff d0 83 c4 04 43 39 1d d0 d1
Looking at stl_intr() in stallion.c would imply stl_brds[i] or stl_brds[i]->intr was an invalid pointer. (Had it crashed in the actual ->intr routine then stl_intr should have been in the call trace). stl_brds[i] and stl_brds[i]->intr appear to be initialised one and then left alone implying something scribbled 9999 over the structure
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu
| |