lkml.org 
[lkml]   [2005]   [Jul]   [6]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: OOPS in 2.6.13-rc1-mm1 -- EIP is at sysfs_release+0x49/0xb0
    Miles Lane <miles.lane@gmail.com> wrote:
    >
    > mtrr: base(0xe8020000) is not aligned on a size(0x3c0000) boundary
    > [drm:drm_unlock] *ERROR* Process 4470 using kernel context 0
    > mtrr: 0xe8000000,0x8000000 overlaps existing 0xe8000000,0x1000000
    > Unable to handle kernel paging request at virtual address 5f78735f
    > printing eip:
    > c01abbf9
    > *pde = 00000000
    > Oops: 0002 [#1]
    > PREEMPT
    > Modules linked in: pcmcia container ipv6 af_packet ohci1394
    > yenta_socket rsrc_nonstatic pcmcia_core ipw2200 ieee80211
    > ieee80211_crypt 8139too mii snd_intel8x0 snd_ac97_codec snd_pcm_oss
    > snd_mixer_oss snd_pcm snd_timer snd soundcore snd_page_alloc ehci_hcd
    > uhci_hcd usbcore rtc nls_cp437 sbp2 scsi_mod ieee1394 psmouse ide_cd
    > cdrom
    > CPU: 0
    > EIP: 0060:[<c01abbf9>] Not tainted VLI
    > EFLAGS: 00010246 (2.6.13-rc1-mm1)
    > EIP is at sysfs_release+0x49/0xb0
    > eax: 5f78725f ebx: 5f78725f ecx: 00000001 edx: f7662000
    > esi: c19520a4 edi: f70b8a80 ebp: f7663f3c esp: f7663f2c
    > ds: 007b es: 007b ss: 0068
    > Process hald (pid: 4736, threadinfo=f7662000 task=f7c97a80)
    > Stack: c19520a4 00000010 f70d2d80 f7703174 f7663f68 c0169a5a f7703174 f70d2d80
    > 00000000 00000000 c1894180 f7715c8c f70d2d80 c1bcd900 00000000 f7663f78
    > c016985a f70d2d80 f70d2d80 f7663f94 c0167dcb f70d2d80 c1bcd900 00000010
    > Call Trace:
    > [<c010415f>] show_stack+0x7f/0xa0
    > [<c0104314>] show_registers+0x164/0x1d0
    > [<c010452d>] die+0xed/0x180
    > [<c0119314>] do_page_fault+0x344/0x68d
    > [<c0103d6f>] error_code+0x4f/0x54
    > [<c0169a5a>] __fput+0x1da/0x1f0
    > [<c016985a>] fput+0x2a/0x50
    > [<c0167dcb>] filp_close+0x4b/0x80
    > [<c0167e7a>] sys_close+0x7a/0xb0
    > [<c010326b>] sysenter_past_esp+0x54/0x75

    It's irritating that when some driver screws up its sysfs handling, the
    trace leaves no indication which driver it was.

    One thing you could do is to disable `hald' (what is that anyway?) by
    renaming it and try to get the system to boot. Then run `hald' by hand,
    under strace, work out which sysfs file it was trying to close.
    -
    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/

    \
     
     \ /
      Last update: 2005-07-07 00:48    [W:0.023 / U:89.984 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site