Messages in this thread |  | | From | Keith Owens <> | Subject | Re: new aic7xxx oopses with AHA2940 | Date | Sun, 27 May 2001 12:32:20 +1000 |
| |
On Sun, 27 May 2001 04:21:30 +0200, Marc Schiffbauer <marc.schiffbauer@links2linux.de> wrote: >* Keith Owens schrieb am 27.05.01 um 03:07 Uhr: >> Since you are failing during modprobe, creating /var/log/ksymoops is a >> good idea, man insmod, see KSYMOOPS ASSISTANCE. Reproduce the >> problem to get a clean oops trace then run it through ksymoops, using >> the saved module data in /var/log/ksymoops. > >OK. Now I cut out the Oops out of my /var/log/messages, then did > >cat aic7xxx.oops | ksymoops -k /var/log/ksymoops/20010527040453.ksyms -l >/var/log/ksymoops/20010527040453.modules > trace1
That one was no good. Because modprobe failed, the data in /var/log/ksymoops did not get updated.
>and another run with default options: >ksymoops 0.7c on i686 2.4.5. Options used
You should be running ksymoops 2.4.x with 2.4 kernels,from ftp://ftp.<country>.kernel.org/pub/linux/utils/kernel/ksymoops/v2.4
>>>EIP; e0a7b3a7 <[aic7xxx]ahc_match_scb+17/c0> <===== >Trace; e0a7b79d <[aic7xxx]ahc_search_qinfifo+14d/6b0> >Trace; e0a7c226 <[aic7xxx]ahc_abort_scbs+66/300>
That trace looks good, now it is up to the aic7xxx maintainer to fix the problem.
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
|  |