Hi. Jon Smirl wrote: I can't reproduce this, but I think I found the bug from inspection. In the vesafb detection code a pointer wasn't set to NULL correctly. I checked a fix into CVS. Let me know if that didn't fix it. Yes, it fixed that particular problem, but after rmmoding and modprobing about 3 times, there's another: [drm] Debug messages ON PCI: Unable to reserve mem region #1:[EMAIL PROTECTED] for device 0000:01:00.0 PCI: Unable to reserve mem region #1:[EMAIL PROTECTED] for device 0000:01:00.0 [drm:drm_probe] [drm:viadrv_ctxbitmap_next] drm_ctxbitmap_next bit : 0 [drm:viadrv_ctxbitmap_init] drm_ctxbitmap_init : 0 [drm:viadrv_stub_register] [drm:viadrv_stub_register] calling inter_module_register [drm:viadrv_stub_getminor] info count increased 1 [drm:drm_hotplug] [drm] Initialized via 1.4.0 20040819 on minor 0: VIA Technologies, Inc. VT8623 [ Apollo CLE266] integrated CastleRock graphics [drm] Used old pci detect: framebuffer loaded [drm:drm_exit] [drm:drm_cleanup] [drm:viadrv_takedown] [drm:viadrv_stub_unregister] 0 [drm:drm_hotplug] [drm:viadrv_stub_putminor] unregistering inter_module [drm:drm_cleanup] minor 0 unregistered [drm:drm_cleanup] mtrr_del=2 [drm] Module unloaded [drm] Debug messages ON Unable to handle kernel paging request at virtual address 49544365 printing eip: c01c8788 *pde = 00000000 Oops: 0000 [#1] CPU: 0 EIP: 0060:[<c01c8788>] Tainted: GF VLI EFLAGS: 00010213 EIP is at pci_get_subsys+0x38/0xf0 eax: 00007361 ebx: 49544341 ecx: 00000000 edx: 49544341 esi: 00001106 edi: 00000000 ebp: c9865f80 esp: c9865f74 ds: 007b es: 007b ss: 0068 Process modprobe (pid: 3743, threadinfo=c9864000 task=d9d139c0) Stack: e0873920 00000000 e0873920 c9865fa8 e0878097 00001106 00003022 ffffffff ffffffff 00000000 c0327830 e0873b80 c0327818 c9865fbc c013668f 40194008 0805c180 0805c318 c9864000 c010b017 40194008 00015b1a 0805c180 0805c180 Call Trace: [<e0878097>] via_swap_count+0x1e57/0x1f35 [via] [<c013668f>] sys_init_module+0xdf/0x1b0 [<c010b017>] syscall_call+0x7/0xb Code: 8b 75 08 8b 7d 18 f7 40 14 00 ff ff 00 0f 85 a3 00 00 00 85 ff 0f 84 90 00 00 00 8b 17 85 d2 74 72 81 fa 28 e0 32 c0 75 1d eb 68 <66> 8b 42 24 25 ff ff 00 00 39 f0 74 15 8b 12 85 d2 74 55 81 fa This is with latest CVS, without patch applied. Doesn't appear before the patch. BTW, these two messages didn't appear before your patch PCI: Unable to reserve mem region #1:[EMAIL PROTECTED] for device 0000:01:00.0 PCI: Unable to reserve mem region #1:[EMAIL PROTECTED] for device 0000:01:00.0 Are they an indication of something bad? Also the problem / fix I posted earlier that DRM refuses to install the IRQ handler unless DRIVER_HAS_DMA is defined I think needs fixing. DMA-less drivers could have other useful IRQs. /Thomas --- Thomas Hellstrom <[EMAIL PROTECTED]> wrote:Jon Smirl wrote:What is the stack trace?<Modprobing via>===== Jon Smirl [EMAIL PROTECTED] __________________________________ Do you Yahoo!? Yahoo! Mail - 50x more storage than other providers! http://promotions.yahoo.com/new_mail ------------------------------------------------------- This SF.Net email is sponsored by BEA Weblogic Workshop FREE Java Enterprise J2EE developer tools! Get your free copy of BEA WebLogic Workshop 8.1 today. http://ads.osdn.com/?ad_id=5047&alloc_id=10808&op=click -- _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel |
- Re: Kernel oops after drmfntbl-0-0-2-200... Ian Romanick
- Re: Kernel oops after drmfntbl-0-0-2-200... Sam Ravnborg
- Re: Kernel oops after drmfntbl-0-0-2-200... Ian Romanick
- Re: Kernel oops after drmfntbl-0-0-2-200... Sam Ravnborg
- Re: Kernel oops after drmfntbl-0-0-2-200... Ian Romanick
- Re: Kernel oops after drmfntbl-0-0-2-200... Sam Ravnborg
- Re: Kernel oops after drmfntbl-0-0-2-200... Jeff Garzik
- Re: Kernel oops after drmfntbl-0-0-2-200... Dave Airlie
- drm_core and versioning Jon Smirl
- Re: Kernel oops after drmfntbl-0-0-2-20040824-merge Jon Smirl
- Re: Kernel oops after drmfntbl-0-0-2-20040824-merge Thomas Hellström
- Re: Kernel oops after drmfntbl-0-0-2-20040824-me... Jon Smirl
- Re: Kernel oops after drmfntbl-0-0-2-2004082... Thomas Hellström