---------- Forwarded Message ---------- With (smb)mount with codepage=iso8859-1 I could also reproduce this error, see the kernel message below. So, for the case of wrong codepage selection, it is definitely a bug. I wonder, if Brad's situation/problem is the same. Ralf. Mar 18 15:35:20 trine kernel: Unable to handle kernel paging request at virtual address d0000000 Mar 18 15:35:20 trine kernel: printing eip: Mar 18 15:35:20 trine kernel: d4d9ea40 Mar 18 15:35:20 trine kernel: *pde = 00000000 Mar 18 15:35:20 trine kernel: Oops: 0000 Mar 18 15:35:20 trine kernel: CPU: 0 Mar 18 15:35:20 trine kernel: EIP: 0010:[<d4d9ea40>] Tainted: GF Mar 18 15:35:20 trine kernel: EFLAGS: 00010293 Mar 18 15:35:20 trine kernel: eax: b0a09517 ebx: eafae199 ecx: f72da3fd edx: 89b9b76b Mar 18 15:35:20 trine kernel: esi: d0000000 edi: c4b81e2c ebp: c4b81ec0 esp: c4b81dec Mar 18 15:35:20 trine kernel: ds: 0018 es: 0018 ss: 0018 Mar 18 15:35:20 trine kernel: Process ls (pid: 21491, stackpage=c4b81000) Mar 18 15:35:20 trine kernel: Stack: 00000000 00000000 00000000 c7ac0560 c4fe00c0 a4558b43 000194ec a04589f8 Mar 18 15:35:20 trine kernel: 00000000 00000000 c49e6000 000000cb 00000000 ffffffea 00000001 000000cd Mar 18 15:35:20 trine kernel: c4b81e90 00000000 d4db851c c013e600 c72da000 d4d9d2e1 c7a7cce0 c4b81fa0 Mar 18 15:35:20 trine kernel: Call Trace: [filldir64+0/352] [<d4d9d2e1>] [filldir64+0/352] [<d4d9e235>] [filldir64+0/352] Mar 18 15:35:20 trine kernel: Call Trace: [<c013e600>] [<d4d9d2e1>] [<c013e600>] [<d4d9e235>] [<c013e600>] Mar 18 15:35:20 trine kernel: [vfs_readdir+96/144] [filldir64+0/352] [sys_getdents64+79/188] [filldir64+0/352] [system_call+51/56] Mar 18 15:35:20 trine kernel: [<c013e100>] [<c013e600>] [<c013e7af>] [<c013e600>] [<c0106eab>] Mar 18 15:35:20 trine kernel: Mar 18 15:35:20 trine kernel: Code: 0f b6 06 49 46 89 c2 c1 e8 04 c1 e2 04 8d 14 1a 01 c2 83 f9 ------------------------------------------------------- Oooooops, wrong kernel. Now the smbfs error with kernel-2.4.18.6mdk-1-1mdk: (BTW, if someone out there has got some spare time, he could explain me, why scsi_mod appeared in that log. I'm a kernel dummy ,-) Mar 18 16:00:54 trine kernel: Unable to handle kernel paging request at virtual address d0000000 Mar 18 16:00:54 trine kernel: printing eip: Mar 18 16:00:54 trine kernel: d4dd3c34 Mar 18 16:00:54 trine kernel: *pde = 00000000 Mar 18 16:00:54 trine kernel: Oops: 0000 Mar 18 16:00:54 trine kernel: CPU: 0 Mar 18 16:00:54 trine kernel: EIP: 0010:[scsi_mod:scsi_hosts_R75915793+38400760/31452492] Tainted: GF Mar 18 16:00:54 trine kernel: EIP: 0010:[<d4dd3c34>] Tainted: GF Mar 18 16:00:54 trine kernel: EFLAGS: 00010246 Mar 18 16:00:54 trine kernel: eax: 00000000 ebx: c12a2d8d ecx: fd8b43fd edx: 85ec8fc7 Mar 18 16:00:54 trine kernel: esi: d0000000 edi: cdac3e28 ebp: cdac3ebc esp: cdac3de8 Mar 18 16:00:54 trine kernel: ds: 0018 es: 0018 ss: 0018 Mar 18 16:00:54 trine kernel: Process ls (pid: 3278, stackpage=cdac3000) Mar 18 16:00:55 trine kernel: Stack: 00000000 00000000 00000000 cd8c18e0 cf2f0460 a4558b43 0000ad38 a04589f8 Mar 18 16:00:55 trine kernel: 00000000 00000000 cd793000 000000cb 00000000 ffffffea 00000001 000000cd Mar 18 16:00:55 trine kernel: cdac3e8c 00000000 d4de951c cdde29c0 cd8b4000 d4dd2461 cdde29c0 cdac3fa0 Mar 18 16:00:55 trine kernel: Call Trace: [scsi_mod:scsi_hosts_R75915793+38394661/31458591] [filldir64+0/352] [scsi_mod:scsi_hosts_R75915793+38398741/31454511] [filldir64+0/352] [vfs_readdir+96/144] Mar 18 16:00:55 trine kernel: Call Trace: [<d4dd2461>] [<c0141b90>] [<d4dd3451>] [<c0141b90>] [<c0141690>] Mar 18 16:00:55 trine kernel: [filldir64+0/352] [sys_getdents64+79/185] [filldir64+0/352] [sys_swapoff+369/640] [system_call+51/64] Mar 18 16:00:55 trine kernel: [<c0141b90>] [<c0141d3f>] [<c0141b90>] [<c0130001>] [<c0106f23>] Mar 18 16:00:55 trine kernel: Mar 18 16:00:55 trine kernel: Code: 8a 06 89 c2 c1 e8 04 c1 e2 04 49 46 8d 14 1a 01 c2 83 f9 ff
