Skip to contentSkip to conversation

linux-2.6.0-test5-mm1

DISCUSSION Voicu Liviu 3 participants 5 messages Sep 12, 2003 Driver core

lore
Share & tools
lore
#0 lore raw

This happens after I load alsa modules on boot..............

<from_dmesg>

Freeing unused kernel memory: 308k freed
Adding 313228k swap on /dev/hda6. Priority:-1 extents:1
PCI: Found IRQ 5 for device 0000:00:09.0
PCI: Sharing IRQ 5 with 0000:00:04.2

Unable to handle kernel paging request at virtual address ffffffef
 printing eip:
c01df3c0
*pde = 00001067
*pte = 00000000
Oops: 0000 [#1]
CPU:    0
EIP:    0060:[<c01df3c0>]    Not tainted
EFLAGS: 00010282

EIP is at atomic_dec_and_lock+0x10/0x60
eax: ffffffef ebx: ffffffef ecx: ffffffef edx: 00000000
esi: cffe5680 edi: c03312e4 ebp: d092fec8 esp: cf96feb0
ds: 007b es: 007b ss: 0068
Process modprobe (pid: 2596, threadinfo=cf96e000 task=cf971940)

Stack: ffffffef cffe5680 c0169b30 ffffffef c032c690 ffffffef cffe5680 c03312e4
       c0187e45 ffffffef 000041ed c0187da0 d092fee0 00000000 c0187eb6 
d092fee0
       cffe5680 d092fee4 00000000 d092fee0 c01dc86f d092fee0 d092fee0 
c0331348
Call Trace:
 [<c0169b30>] dput+0x30/0x220
 [<c0187e45>] create_dir+0x85/0x90
 [<c0187da0>] init_dir+0x0/0x20
 [<c0187eb6>] sysfs_create_dir+0x36/0x80
 [<c01dc86f>] create_dir+0x1f/0x50
 [<c01dca17>] kobject_add+0x97/0x110
 [<c01dcab3>] kobject_register+0x23/0x60
 [<c023c72a>] bus_add_driver+0x4a/0xa0
 [<c023cbbf>] driver_register+0x2f/0x40
 [<c01e5550>] pci_register_driver+0x60/0x90
 [<d0915809>] alsa_card_ens137x_init+0x19/0x5b [snd_ens1370]
 [<c013361c>] sys_init_module+0x12c/0x250
 [<c010934b>] syscall_call+0x7/0xb

Code: 8b 31 89 f2 4a 74 11 89 f0 f0 0f b1 11 31 db 39 f0 75 ed 89
 blk: queue c13d8200, I/O limit 4095Mb (mask 0xffffffff)

eth0: link up, 10Mbps, half-duplex, lpa 0x0000
liviu@starshooter liviu $

</from_dmesg>

Liviu

#1 lore raw
Quoted 10 lines · Voicu Liviu

This happens after I load alsa modules on boot..............

<from_dmesg>

Freeing unused kernel memory: 308k freed
Adding 313228k swap on /dev/hda6. Priority:-1 extents:1
PCI: Found IRQ 5 for device 0000:00:09.0
PCI: Sharing IRQ 5 with 0000:00:04.2

Unable to handle kernel paging request at virtual address ffffffef
fs/sysfs/dir.c renamed from fs/sysfs/dir.c~sysfs-create_dir-oops-fix +4 -3
diff -puN fs/sysfs/dir.c~sysfs-create_dir-oops-fix fs/sysfs/dir.c
@@ -24,10 +24,11 @@ static int init_dir(struct inode * inode
 static struct dentry * 
 create_dir(struct kobject * k, struct dentry * p, const char * n)
 {
-	struct dentry * dentry;
+	struct dentry *dentry, *ret;
 
 	down(&p->d_inode->i_sem);
 	dentry = sysfs_get_dentry(p,n);
+	ret = dentry;
 	if (!IS_ERR(dentry)) {
 		int error = sysfs_create(dentry,
 					 S_IFDIR| S_IRWXU | S_IRUGO | S_IXUGO,
@@ -36,11 +37,11 @@ create_dir(struct kobject * k, struct de
 			dentry->d_fsdata = k;
 			p->d_inode->i_nlink++;
 		} else
-			dentry = ERR_PTR(error);
+			ret = ERR_PTR(error);
 		dput(dentry);
 	}
 	up(&p->d_inode->i_sem);
-	return dentry;
+	return ret;
 }
 
 

_

#2 lore raw

Thank you, I have found the problem, my sound card is Ensoniq ES1371 so the module should be snd_ens1371 but I used to load by mistake snd_ens1370 so I got the OOPS all the time, I fixed the alsa-config and now all works. Liviu

Quoted 51 lines · On Fri, 12 Sep 2003 11:24:36 -0700 Andrew Morton <[email protected]> wrote:
Quoted 10 lines · Voicu Liviu

This happens after I load alsa modules on boot..............

<from_dmesg>

Freeing unused kernel memory: 308k freed
Adding 313228k swap on /dev/hda6. Priority:-1 extents:1
PCI: Found IRQ 5 for device 0000:00:09.0
PCI: Sharing IRQ 5 with 0000:00:04.2

Unable to handle kernel paging request at virtual address ffffffef

diff -puN fs/sysfs/dir.c~sysfs-create_dir-oops-fix fs/sysfs/dir.c

fs/sysfs/dir.c renamed from fs/sysfs/dir.c~sysfs-create_dir-oops-fix +4 -3
@@ -24,10 +24,11 @@ static int init_dir(struct inode * inode
 static struct dentry * 
 create_dir(struct kobject * k, struct dentry * p, const char * n)
 {
-	struct dentry * dentry;
+	struct dentry *dentry, *ret;
 
 	down(&p->d_inode->i_sem);
 	dentry = sysfs_get_dentry(p,n);
+	ret = dentry;
 	if (!IS_ERR(dentry)) {
 		int error = sysfs_create(dentry,
 					 S_IFDIR| S_IRWXU | S_IRUGO | S_IXUGO,
@@ -36,11 +37,11 @@ create_dir(struct kobject * k, struct de
 			dentry->d_fsdata = k;
 			p->d_inode->i_nlink++;
 		} else
-			dentry = ERR_PTR(error);
+			ret = ERR_PTR(error);
 		dput(dentry);
 	}
 	up(&p->d_inode->i_sem);
-	return dentry;
+	return ret;
 }
 
 

_

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

Signature · 16 lines
Liviu Voicu
Assistant Programmer and network support
Computation Center, Mount Scopus
Hebrew University of Jerusalem
Tel: 972(2)-5881253
E-mail: "Liviu Voicu"<[email protected]>

/**
 * cat /usr/src/linux/arch/i386/boot/bzImage > /dev/dsp
 * ( and the voice of God will be heard! )
 *
 */

Click here to see my GPG signature:
----------------------------------
	http://search.keyserver.net:11371/pks/lookup?template=netensearch%2Cnetennomatch%2Cnetenerror&search=pacman%40mscc.huji.ac.il&op=vindex&fingerprint=on&submit=Get+List
#3 lore raw
Quoted 1 line · Voicu Liviu

Thank you, I have found the problem, my sound card is Ensoniq ES1371 so

the module should be snd_ens1371 but I used to load by mistake snd_ens1370 so I got the OOPS all the time, I fixed the alsa-config and now all works.

Quoted 1 line

Liviu

Please try snd_ens1370 with the patch Andrew posted and see if it still oopses. We need to know if it fixes the problem you are having, even if you were using the wrong driver for your hardware.

#4 lore raw
Quoted 10 lines · Mike Fedyk
Quoted 1 line · Voicu Liviu

Thank you, I have found the problem, my sound card is Ensoniq ES1371 so

the module should be snd_ens1371 but I used to load by mistake snd_ens1370 so I got the OOPS all the time, I fixed the alsa-config and now all works.

Quoted 1 line

Liviu

Please try snd_ens1370 with the patch Andrew posted and see if it still oopses. We need to know if it fixes the problem you are having, even if you were using the wrong driver for your hardware.

No further testing is needed thanks. Both bugs have been found.