Re: [gentoo-user] Re: Re: DMA not working (2.4.22 and 2.6.1)

[Daniel Drake]

Richard Revis wrote:
Are you using 80-conductor or 40-conductor IDE cables?
Not sure.
Doesn't really matter, if it works on 1 kernel it should work on the other.

[EMAIL PROTECTED] peu $ lspci
00:11.1 IDE interface: VIA Technologies, Inc. 
VT82C586A/B/VT82C686/A/B/VT8233/A/C/VT8235 PIPC Bus Master IDE (rev 06)
Your IDE driver should be VIA82CXXX then.
Are you sure you have the VIA support compiled in? Your dmesg suggests otherwise.
For example, in the source code of the VIA82CXXX driver (in 2.6.1-mm1) I can see:

        /*
         * Print the boot message.
         */
        pci_read_config_byte(isa, PCI_REVISION_ID, &t);
        printk(KERN_INFO "VP_IDE: VIA %s (rev %02x) IDE %s "
                "controller on pci%s\n",
                via_config->name, t,
                via_dma[via_config->flags & VIA_UDMA],
                pci_name(dev));
You should see a message on bootup (in your dmesg) giving some basic info 
about your IDE controller. More notably, everything that the VIA82CXXX driver 
prints starts with "VP_IDE" and I see nothing like that in your dmesg.

Linux version 2.6.1-rc3-gentoo ([EMAIL PROTECTED]) (gcc version 3.2.3 20030422 (Gentoo Linux 1.4 3.2.3-r3, propolice)) #4 Mon Jan 12 21:56:56 GMT 2004
The date there indicates when the kernel was compiled, so that should be able 
to confirm that you are booting the kernel that you think you are!
Just to confirm, you are definately mounting /boot before copying the new 
kernel over? Checking that grub points to the right kernel bzImage? Running 
"/sbin/lilo" if you use lilo?




Debug: sleeping function called from invalid context at mm/slab.c:1856
in_atomic():1, irqs_disabled():0
Call Trace:
 [<c011d26b>] __might_sleep+0xab/0xd0
 [<c013f395>] kmem_cache_alloc+0x65/0x70
 [<c014dd91>] __get_vm_area+0x21/0x100
 [<c014dea3>] get_vm_area+0x33/0x40
 [<c011a603>] __ioremap+0xb3/0x100
 [<c011a679>] ioremap_nocache+0x29/0xb0
 [<e1ae936e>] os_map_kernel_space+0x68/0x6c [nvidia]
 [<e1afb967>] __nvsym00568+0x1f/0x2c [nvidia]
 [<e1afda86>] __nvsym00775+0x6e/0xe0 [nvidia]
 [<e1afdb16>] __nvsym00781+0x1e/0x190 [nvidia]
 [<e1aff59c>] rm_init_adapter+0xc/0x10 [nvidia]
 [<e1ae5dd2>] nv_kern_open+0xf5/0x232 [nvidia]
 [<c015caa0>] chrdev_open+0xc0/0x1d0
 [<c01b8b4b>] devfs_open+0xeb/0x110
 [<c0152972>] dentry_open+0x112/0x180
 [<c0152856>] filp_open+0x66/0x70
 [<c0152c53>] sys_open+0x53/0x90
 [<c010b45b>] syscall_call+0x7/0xb
<truncated here>
Offtopic, thats not looking too good. Looks like the nvidia module is causing 
some problems. Do you see this much? Which version of nvidia-driver are you 
running?

Daniel

--
[EMAIL PROTECTED] mailing list