On Sun, 2003-09-14 at 11:17, Collins Richey wrote: > On Sun, 14 Sep 2003 00:27:24 -0400 > Chris I <[EMAIL PROTECTED]> wrote: > > > On 2003.09.13 13:19, Collins Richey wrote: > > > I'm currently running gnome 2.2.3 on linux kernel 2.6-test5. I have > > > emerged the gnome-audion package as well as the standard gnome set. > > > I'm > > > using OSS emulation on 2.6 because the alsa modules for my car > > > (ES1371) > > > do not work. Sound works just fine for me with XMMS, RealPlayer, > > > etc., > > > but the gnome system sounds do not work. Mixer settings are all > > > unmuted. When I go to gnome system events and play one of the > > > standard > > > sound .wav files, I get no error indication but no sound. > > > > > > Any help would be appreciated. > > > > Have you enabled sound server startup in the control-center? > > > > Yes. Here's more info. I just discovered that each time I push play in the > control-center dialog, I get the following (to me somewhat meaningless Call Trace in > /var/log/messages: > > Sep 14 08:39:59 richeypc3 kernel: Call Trace: > Sep 14 08:39:59 richeypc3 kernel: [__might_sleep+95/112] __might_sleep+0x5f/0x7 > 0 > Sep 14 08:39:59 richeypc3 kernel: [<c0118f9f>] __might_sleep+0x5f/0x70 > Sep 14 08:39:59 richeypc3 kernel: [__alloc_pages+801/816] __alloc_pages+0x321/0 > x330 > Sep 14 08:39:59 richeypc3 kernel: [<c0137361>] __alloc_pages+0x321/0x330 > Sep 14 08:39:59 richeypc3 kernel: [__alloc_pages+141/816] __alloc_pages+0x8d/0x > 330 > Sep 14 08:39:59 richeypc3 kernel: [<c01370cd>] __alloc_pages+0x8d/0x330 > Sep 14 08:39:59 richeypc3 kernel: [pte_alloc_one+26/80] pte_alloc_one+0x1a/0x50 > Sep 14 08:39:59 richeypc3 kernel: [<c0115e7a>] pte_alloc_one+0x1a/0x50 > Sep 14 08:39:59 richeypc3 kernel: [pte_alloc_map+64/192] pte_alloc_map+0x40/0xc > 0 > Sep 14 08:39:59 richeypc3 kernel: [<c013ee40>] pte_alloc_map+0x40/0xc0 > Sep 14 08:39:59 richeypc3 kernel: [remap_page_range+180/464] remap_page_range+0 > xb4/0x1d0 > Sep 14 08:39:59 richeypc3 kernel: [<c013fe64>] remap_page_range+0xb4/0x1d0 > Sep 14 08:39:59 richeypc3 kernel: [_end+541716521/1067432924] nv_kern_mmap+0x31 > 4/0x367 [nvidia] > Sep 14 08:39:59 richeypc3 kernel: [<e0aa144d>] nv_kern_mmap+0x314/0x367 [nvidia > ] > Sep 14 08:39:59 richeypc3 kernel: [do_mmap_pgoff+784/1696] do_mmap_pgoff+0x310/ > 0x6a0 > Sep 14 08:39:59 richeypc3 kernel: [<c0142540>] do_mmap_pgoff+0x310/0x6a0 > Sep 14 08:39:59 richeypc3 kernel: [sys_mmap2+155/224] sys_mmap2+0x9b/0xe0 > Sep 14 08:39:59 richeypc3 kernel: [<c010f59b>] sys_mmap2+0x9b/0xe0 > Sep 14 08:39:59 richeypc3 kernel: [syscall_call+7/11] syscall_call+0x7/0xb > Sep 14 08:39:59 richeypc3 kernel: [<c010943b>] syscall_call+0x7/0xb > Sep 14 08:39:59 richeypc3 kernel: > > So, could this be a 2.6.test? kernel problem? Odds are good that you have the many debugging options turned on. That one appears to be from Debug memory allocations (CONFIG_DEBUG_SLAB), Page alloc debugging (CONFIG_DEBUG_PAGEALLOC), or Sleep-inside-spinlock checking (CONFIG_DEBUG_SPINLOCK_SLEEP).
Do not report these to the kernel developers because they will tell you to contact nvidia (and maybe a few other colorful things as well). These are errors in the nvidia binary drivers ( note the "Sep 14 08:39:59 richeypc3 kernel: [<e0aa144d>] nv_kern_mmap+0x314/0x367 [nvidia]" bit). If you are recieving similar messages on a non-tainted kernel, feel free to drop an email to [EMAIL PROTECTED] -- Owen Ford <[EMAIL PROTECTED]>
signature.asc
Description: This is a digitally signed message part