[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: dik_show_code: what is it??



Some more info:

Jul  7 20:05:39 fogarty kernel: Unable to load interpreter  
Jul  7 20:05:40 fogarty kernel: Unable to handle kernel paging
request at virtual address 0000000000000000  
Jul  7 20:05:40 fogarty kernel: modprobe(15431): Oops -1  
Jul  7 20:05:40 fogarty kernel: pc = [<0000000000000000>]  ra =
[<0000000000000000>]  ps = 0000  
Jul  7 20:05:40 fogarty kernel: r0 = 0000000000000000  r1 =
0000000000000000  r2 = 0000000000000000  
Jul  7 20:05:40 fogarty kernel: r3 = 0000000000000000  r4 =
0000000000000000  r5 = 0000000000000000  
Jul  7 20:05:40 fogarty kernel: r6 = 0000000000000000  r7 =
0000000000000000  r8 = 0000000000000000  
Jul  7 20:05:40 fogarty kernel: r9 = 0000000000000400  r10=
fffffc0000e63cb0  r11= fffffc00004567d0  
Jul  7 20:05:40 fogarty kernel: r12= fffffc00005fc620  r13=
fffffc000029f840  r14= 0000000000010000  
Jul  7 20:05:40 fogarty kernel: r15= fffffc00001a5040  
Jul  7 20:05:40 fogarty kernel: r16= 0000000000000000  r17=
0000000000000000  r18= 0000000000000000  
Jul  7 20:05:40 fogarty kernel: r19= 0000000000000000  r20=
0000000000000000  r21= 0000000000000000  
Jul  7 20:05:40 fogarty kernel: r22= 0000000000000000  r23=
0000000000000000  r24= 0000000000000000  
Jul  7 20:05:40 fogarty kernel: r25= 0000000000000000  r27=
0000000000000000  r28= 0000000000000000  
Jul  7 20:05:40 fogarty kernel: gp = 0000000000000000  sp =
fffffc00013e7b50  
Jul  7 20:05:40 fogarty kernel: Code: 00000000  00001111  00003238
modprobe: Exception at [dik_show_code+68/192] (fffffc00003110a8)

my kernel is 2.2.11-rth1, with devfs99.3, raid0145-2.2.6,
quota-fix-2.2.8-1.diff, nfsd-2.2.7-3.patch and
nfsd-2.2.7-lockd.patch.

The oops seems to happens just after cdrecord opens /dev/sg/c0b0t3u0.
This sets off a modprobe (cause of devfs) for what module i don't
know - maybe none, which causes the segfault in dik_show_code. 

The oops isn't fatal at all. It happens consistently when i run
cdrecord. The machine works fine apart that.

Any ideas? Also, can i comment out the body of dik_show_code as a
stopgap?

thanks,

Paul Jakma.

On Wed, 7 Jul 1999, Paul Jakma wrote:

  I have the following symbols in the System.map's of my alpha kernels:
  
  [root@fogarty /boot]# grep dik_show System.map-2.2.11 
  fffffc0000310ea0 t dik_show_regs
  fffffc0000311060 t dik_show_code
  fffffc0000311120 t dik_show_trace
  
  They're not in any of my i386 kernels. What are they, and do they
  have be compiled in? Cause cdrecord triggers an Oops in them whenever
  i run it.
  
  ta,
  

-- 
Paul Jakma
paul@clubi.ie	http://hibernia.clubi.ie
PGP5 key: http://www.clubi.ie/jakma/publickey.txt
-------------------------------------------
Fortune:
If Patrick Henry thought that taxation without representation was bad,
he should see how bad it is with representation.



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index] []