I have posted that to linux-ppp mailing list, but
no answer for 2 weeks now..
so here again:
I cannot get ppp working with 2.6.0-test kernels (test1, test3, test4)
I am using the ppp-2.4.1 package
Kernel config:
CONFIG_PPP=m
# CONFIG_PPP_MULTILINK is not set
# CONFIG_PPP_FILTER is not set
CONFIG_PPP_ASYNC=m
CONFIG_PPP_SYNC_TTY=m
CONFIG_PPP_DEFLATE=m
CONFIG_PPP_BSDCOMP=m
# CONFIG_PPPOE is not set
and here comes the Oops when i want to start 'pppd':
PPP generic driver version 2.4.2
devfs_mk_cdev: could not append to parent for ppp
failed to register PPP device (-17)
Unable to handle kernel paging request at virtual address d1964580
printing eip:
c015bbb9
*pde = 013d0067
*pte = 00000000
Oops: 0000 [#1]
CPU: 0
EIP: 0060:[<c015bbb9>] Not tainted
EFLAGS: 00010202
EIP is at cdev_get+0x29/0xc0
eax: c6de8000 ebx: d1964580 ecx: 0000006c edx: c015ba90
esi: 00000001 edi: cb8c6f40 ebp: 00006c00 esp: c6de9eb4
ds: 007b es: 007b ss: 0068
Process pppd (pid: 3323, threadinfo=c6de8000 task=c725c680)
Stack: c03aa4f0 cc280ec0 00006c00 00000000 c015ba9f cb8c6f40 c0275a0a
00006c00
cb8c6f40 00000000 c6de8000 c6de8000 cb8c6f40 c015ba80 000000ff
c6de8000
00000000 00000000 00000000 c015b882 cffe1c00 00006c00 c6de9f10
00000000
Call Trace:
[<c015ba9f>] exact_lock+0xf/0x20
[<c0275a0a>] kobj_lookup+0x11a/0x210
[<c015ba80>] exact_match+0x0/0x10
[<c015b882>] chrdev_open+0x192/0x210
[<c01b2140>] devfs_open+0x0/0x110
[<c01b2232>] devfs_open+0xf2/0x110
[<c015146a>] dentry_open+0x14a/0x220
[<c0151318>] filp_open+0x68/0x70
[<c01517bb>] sys_open+0x5b/0x90
[<c01091db>] syscall_call+0x7/0xb
Code: 83 3b 02 0f 84 7d 00 00 00 ff 83 00 01 00 00 b8 00 e0 ff ff
<6>note: pppd[3323] exited with preempt_count 1
bad: scheduling while atomic!
Call Trace:
[<c011a15a>] schedule+0x3ba/0x3c0
[<c0142f33>] unmap_page_range+0x43/0x70
[<c0143128>] unmap_vmas+0x1c8/0x220
[<c0146e6b>] exit_mmap+0x7b/0x190
[<c011bb25>] mmput+0x65/0xc0
[<c011f910>] do_exit+0x120/0x3d0
[<c010a27c>] die+0xec/0xf0
[<c01188aa>] do_page_fault+0x14a/0x453
[<c012c744>] queue_work+0x84/0xa0
[<c012c6b1>] call_usermodehelper+0x101/0x110
[<c012c540>] __call_usermodehelper+0x0/0x70
[<c0118760>] do_page_fault+0x0/0x453
[<c0109c05>] error_code+0x2d/0x38
[<c015ba90>] exact_lock+0x0/0x20
[<c015bbb9>] cdev_get+0x29/0xc0
[<c015ba9f>] exact_lock+0xf/0x20
[<c0275a0a>] kobj_lookup+0x11a/0x210
[<c015ba80>] exact_match+0x0/0x10
[<c015b882>] chrdev_open+0x192/0x210
[<c01b2140>] devfs_open+0x0/0x110
[<c01b2232>] devfs_open+0xf2/0x110
[<c015146a>] dentry_open+0x14a/0x220
[<c0151318>] filp_open+0x68/0x70
[<c01517bb>] sys_open+0x5b/0x90
[<c01091db>] syscall_call+0x7/0xb
what is wrong here?
Florian Zimmermann <[email protected]> wrote:
>
> I have posted that to linux-ppp mailing list, but
> no answer for 2 weeks now..
Slack Australians.
> and here comes the Oops when i want to start 'pppd':
>
> PPP generic driver version 2.4.2
> devfs_mk_cdev: could not append to parent for ppp
> failed to register PPP device (-17)
_devfs_append_entry("ppp") returns -EEXIST.
> Unable to handle kernel paging request at virtual address d1964580
> EIP is at cdev_get+0x29/0xc0
Then it looks like someone didn't handle the error right.
Please:
a) send your full .config
b) describe the exact sequence of steps which is required to make this
happen, starting from a machine reboot.
Does a simple "modprobe ppp" fail?
On Thu, 2003-09-04 at 23:38, Andrew Morton wrote:
> Florian Zimmermann <[email protected]> wrote:
> > and here comes the Oops when i want to start 'pppd':
> >
> > PPP generic driver version 2.4.2
> > devfs_mk_cdev: could not append to parent for ppp
> > failed to register PPP device (-17)
>
> _devfs_append_entry("ppp") returns -EEXIST.
>
> > Unable to handle kernel paging request at virtual address d1964580
> > EIP is at cdev_get+0x29/0xc0
>
> Then it looks like someone didn't handle the error right.
>
> Please:
>
> a) send your full .config
>
> b) describe the exact sequence of steps which is required to make this
> happen, starting from a machine reboot.
>
> Does a simple "modprobe ppp" fail?
.config file attached. this is linux-2.6.0-test4:
after boot devfs got registered, no ppp module is loaded yet.
then i can do this:
# modprobe ppp_generic
FATAL: Error inserting ppp_generic
(/lib/modules/2.6.0-test4/kernel/drivers/net/ppp_generic.ko): Device or
resource busy
kernel > PPP generic driver version 2.4.2
kernel > devfs_mk_cdev: could not append to parent for ppp
kernel > failed to register PPP device (-17)
# modprobe ppp_async
WARNING: Error inserting ppp_generic
(/lib/modules/2.6.0-test4/kernel/drivers/net/ppp_generic.ko): Device or
resource busy
FATAL: Error inserting ppp_async
(/lib/modules/2.6.0-test4/kernel/drivers/net/ppp_async.ko): Unknown
symbol in module, or unknown parameter (see dmesg)
kernel > PPP generic driver version 2.4.2
kernel > failed to register PPP device (-16)
kernel > ppp_async: Unknown symbol ppp_channel_index
kernel > ppp_async: Unknown symbol ppp_register_channel
kernel > ppp_async: Unknown symbol ppp_input
kernel > ppp_async: Unknown symbol ppp_input_error
kernel > ppp_async: Unknown symbol ppp_output_wakeup
kernel > ppp_async: Unknown symbol ppp_unregister_channel
kernel > ppp_async: Unknown symbol ppp_unit_number
# pppd
Unable to handle kernel paging request at virtual address d19fa300
printing eip:
c01853b8
*pde = 0f956067
*pte = 00000000
Oops: 0000 [#1]
CPU: 0
EIP: 0060:[<c01853b8>] Not tainted
EFLAGS: 00010202
EIP is at cdev_get+0x28/0xb0
eax: c5b20000 ebx: d19fa300 ecx: 0000006c edx: c01852a0
esi: 00000001 edi: cce31c4c ebp: c5b21e78 esp: c5b21e68
ds: 007b es: 007b ss: 0068
Process pppd (pid: 3155, threadinfo=c5b20000 task=c6150000)
Stack: c0197033 ccb78864 00006c00 00000000 c5b21e84 c01852b1 cce31c4c
c5b21ebc
c02d6038 00006c00 cce31c4c 00000282 c5b20000 c5b20000 cce31c4c
c0185290
000000ff 6c006040 c5b20000 00000000 ffffffed c5b21ef8 c0184cd6
cffcb004
Call Trace:
[<c0197033>] dput+0x23/0x680
[<c01852b1>] exact_lock+0x11/0x20
[<c02d6038>] kobj_lookup+0x128/0x220
[<c0185290>] exact_match+0x0/0x10
[<c0184cd6>] chrdev_open+0x446/0x610
[<c01573bc>] kmem_cache_alloc+0x14c/0x1c0
[<c01f9e1f>] devfs_open+0x24f/0x270
[<c0174f11>] dentry_open+0x151/0x220
[<c0174db6>] filp_open+0x66/0x70
[<c01755d3>] sys_open+0x53/0x90
[<c010a3ab>] syscall_call+0x7/0xb
Code: 83 3b 02 74 7a ff 83 00 01 00 00 b8 00 e0 ff ff 21 e0 ff 48
<6>note: pppd[3155] exited with preempt_count 1
bad: scheduling while atomic!
Call Trace:
[<c0120304>] schedule+0x6e4/0x6f0
[<c015f8d1>] unmap_page_range+0x41/0x70
[<c015fb1e>] unmap_vmas+0x21e/0x350
[<c016562b>] exit_mmap+0xcb/0x2c0
[<c0123896>] mmput+0xb6/0x140
[<c0129dc2>] do_exit+0x282/0x900
[<c010b57c>] die+0x21c/0x220
[<c011dbcc>] do_page_fault+0x15c/0x4ca
[<c01519a9>] buffered_rmqueue+0xc9/0x280
[<c011ef88>] kernel_map_pages+0x28/0x60
[<c0151e5f>] __alloc_pages+0x2ff/0x360
[<c011da70>] do_page_fault+0x0/0x4ca
[<c010add5>] error_code+0x2d/0x38
[<c01852a0>] exact_lock+0x0/0x20
[<c01853b8>] cdev_get+0x28/0xb0
[<c0197033>] dput+0x23/0x680
[<c01852b1>] exact_lock+0x11/0x20
[<c02d6038>] kobj_lookup+0x128/0x220
[<c0185290>] exact_match+0x0/0x10
[<c0184cd6>] chrdev_open+0x446/0x610
[<c01573bc>] kmem_cache_alloc+0x14c/0x1c0
[<c01f9e1f>] devfs_open+0x24f/0x270
[<c0174f11>] dentry_open+0x151/0x220
[<c0174db6>] filp_open+0x66/0x70
[<c01755d3>] sys_open+0x53/0x90
[<c010a3ab>] syscall_call+0x7/0xb
Unable to handle kernel paging request at virtual address d19fa300
printing eip:
c01853b8
*pde = 0f956067
*pte = 00000000
Oops: 0000 [#2]
CPU: 0
EIP: 0060:[<c01853b8>] Not tainted
EFLAGS: 00010202
EIP is at cdev_get+0x28/0xb0
eax: c6186000 ebx: d19fa300 ecx: 0000006c edx: c01852a0
esi: 00000001 edi: cce31c4c ebp: c6187e78 esp: c6187e68
ds: 007b es: 007b ss: 0068
Process pppd (pid: 3158, threadinfo=c6186000 task=c615e000)
Stack: c0197033 ccb78864 00006c00 00000000 c6187e84 c01852b1 cce31c4c
c6187ebc
c02d6038 00006c00 cce31c4c 00000282 c6186000 c6186000 cce31c4c
c0185290
000000ff 6c006040 c6186000 00000000 ffffffed c6187ef8 c0184cd6
cffcb004
Call Trace:
[<c0197033>] dput+0x23/0x680
[<c01852b1>] exact_lock+0x11/0x20
[<c02d6038>] kobj_lookup+0x128/0x220
[<c0185290>] exact_match+0x0/0x10
[<c0184cd6>] chrdev_open+0x446/0x610
[<c01573bc>] kmem_cache_alloc+0x14c/0x1c0
[<c01f9e1f>] devfs_open+0x24f/0x270
[<c0174f11>] dentry_open+0x151/0x220
[<c0174db6>] filp_open+0x66/0x70
[<c01755d3>] sys_open+0x53/0x90
[<c010a3ab>] syscall_call+0x7/0xb
Code: 83 3b 02 74 7a ff 83 00 01 00 00 b8 00 e0 ff ff 21 e0 ff 48
<6>note: pppd[3158] exited with preempt_count 1
bad: scheduling while atomic!
Call Trace:
[<c0120304>] schedule+0x6e4/0x6f0
[<c015f8d1>] unmap_page_range+0x41/0x70
[<c015fb1e>] unmap_vmas+0x21e/0x350
[<c016562b>] exit_mmap+0xcb/0x2c0
[<c0123896>] mmput+0xb6/0x140
[<c0129dc2>] do_exit+0x282/0x900
[<c010b57c>] die+0x21c/0x220
[<c011dbcc>] do_page_fault+0x15c/0x4ca
[<c01519a9>] buffered_rmqueue+0xc9/0x280
[<c01ba7ae>] proc_alloc_inode+0x1e/0x80
[<c011ef88>] kernel_map_pages+0x28/0x60
[<c0151e5f>] __alloc_pages+0x2ff/0x360
[<c011da70>] do_page_fault+0x0/0x4ca
[<c010add5>] error_code+0x2d/0x38
[<c01852a0>] exact_lock+0x0/0x20
[<c01853b8>] cdev_get+0x28/0xb0
[<c0197033>] dput+0x23/0x680
[<c01852b1>] exact_lock+0x11/0x20
[<c02d6038>] kobj_lookup+0x128/0x220
[<c0185290>] exact_match+0x0/0x10
[<c0184cd6>] chrdev_open+0x446/0x610
[<c01573bc>] kmem_cache_alloc+0x14c/0x1c0
[<c01f9e1f>] devfs_open+0x24f/0x270
[<c0174f11>] dentry_open+0x151/0x220
[<c0174db6>] filp_open+0x66/0x70
[<c01755d3>] sys_open+0x53/0x90
[<c010a3ab>] syscall_call+0x7/0xb
--
Florian Zimmermann <[email protected]>
On Thu, Sep 04, 2003 at 11:30:59PM +0200, Florian Zimmermann wrote:
> I have posted that to linux-ppp mailing list, but
> no answer for 2 weeks now..
This should fix the oops, but the failure is still strange.
do you already have a ppp device in /dev before loading the module?
On Fri, 2003-09-05 at 09:41, Christoph Hellwig wrote:
> On Thu, Sep 04, 2003 at 11:30:59PM +0200, Florian Zimmermann wrote:
> > I have posted that to linux-ppp mailing list, but
> > no answer for 2 weeks now..
>
> This should fix the oops, but the failure is still strange.
^^^^^ what? where? when?
In case you attached a patch, please resend - there was no
attachement :)
>
> do you already have a ppp device in /dev before loading the module?
the module is never loaded btw, but before i try to load the
module the /device is already there:
crw-r--r-- 1 root root 108, 0 Sep 5 2003 /dev/ppp
> This should fix the oops, but the failure is still strange.
>
> do you already have a ppp device in /dev before loading the module?
Yeah, I posted this problem a few weeks ago but never had an answer. I
worked around it. I do have a /dev/ppp already in there but get the
exact same oops when attempting to run pppd without my patch and while using
devfs
--
Matthew Harrell Never raise your hand to your
Bit Twiddlers, Inc. children - it leaves your
[email protected] midsection unprotected.
linux-2.6.0-test5: exactly same error path
ppp does _not_ work... :((
On Fri, 2003-09-05 at 08:34, Florian Zimmermann wrote:
> On Thu, 2003-09-04 at 23:38, Andrew Morton wrote:
> > Florian Zimmermann <[email protected]> wrote:
> > > and here comes the Oops when i want to start 'pppd':
> > >
> > > PPP generic driver version 2.4.2
> > > devfs_mk_cdev: could not append to parent for ppp
> > > failed to register PPP device (-17)
> >
> > _devfs_append_entry("ppp") returns -EEXIST.
> >
> > > Unable to handle kernel paging request at virtual address d1964580
> > > EIP is at cdev_get+0x29/0xc0
> >
> > Then it looks like someone didn't handle the error right.
> >
> > Please:
> >
> > a) send your full .config
> >
> > b) describe the exact sequence of steps which is required to make this
> > happen, starting from a machine reboot.
> >
> > Does a simple "modprobe ppp" fail?
>
> .config file attached. this is linux-2.6.0-test4:
>
> after boot devfs got registered, no ppp module is loaded yet.
> then i can do this:
>
> # modprobe ppp_generic
> FATAL: Error inserting ppp_generic
> (/lib/modules/2.6.0-test4/kernel/drivers/net/ppp_generic.ko): Device or
> resource busy
>
> kernel > PPP generic driver version 2.4.2
> kernel > devfs_mk_cdev: could not append to parent for ppp
> kernel > failed to register PPP device (-17)
>
> # modprobe ppp_async
> WARNING: Error inserting ppp_generic
> (/lib/modules/2.6.0-test4/kernel/drivers/net/ppp_generic.ko): Device or
> resource busy
> FATAL: Error inserting ppp_async
> (/lib/modules/2.6.0-test4/kernel/drivers/net/ppp_async.ko): Unknown
> symbol in module, or unknown parameter (see dmesg)
>
> kernel > PPP generic driver version 2.4.2
> kernel > failed to register PPP device (-16)
> kernel > ppp_async: Unknown symbol ppp_channel_index
> kernel > ppp_async: Unknown symbol ppp_register_channel
> kernel > ppp_async: Unknown symbol ppp_input
> kernel > ppp_async: Unknown symbol ppp_input_error
> kernel > ppp_async: Unknown symbol ppp_output_wakeup
> kernel > ppp_async: Unknown symbol ppp_unregister_channel
> kernel > ppp_async: Unknown symbol ppp_unit_number
>
> # pppd
> Unable to handle kernel paging request at virtual address d19fa300
> printing eip:
> c01853b8
> *pde = 0f956067
> *pte = 00000000
> Oops: 0000 [#1]
> CPU: 0
> EIP: 0060:[<c01853b8>] Not tainted
> EFLAGS: 00010202
> EIP is at cdev_get+0x28/0xb0
> eax: c5b20000 ebx: d19fa300 ecx: 0000006c edx: c01852a0
> esi: 00000001 edi: cce31c4c ebp: c5b21e78 esp: c5b21e68
> ds: 007b es: 007b ss: 0068
> Process pppd (pid: 3155, threadinfo=c5b20000 task=c6150000)
> Stack: c0197033 ccb78864 00006c00 00000000 c5b21e84 c01852b1 cce31c4c
> c5b21ebc
> c02d6038 00006c00 cce31c4c 00000282 c5b20000 c5b20000 cce31c4c
> c0185290
> 000000ff 6c006040 c5b20000 00000000 ffffffed c5b21ef8 c0184cd6
> cffcb004
> Call Trace:
> [<c0197033>] dput+0x23/0x680
> [<c01852b1>] exact_lock+0x11/0x20
> [<c02d6038>] kobj_lookup+0x128/0x220
> [<c0185290>] exact_match+0x0/0x10
> [<c0184cd6>] chrdev_open+0x446/0x610
> [<c01573bc>] kmem_cache_alloc+0x14c/0x1c0
> [<c01f9e1f>] devfs_open+0x24f/0x270
> [<c0174f11>] dentry_open+0x151/0x220
> [<c0174db6>] filp_open+0x66/0x70
> [<c01755d3>] sys_open+0x53/0x90
> [<c010a3ab>] syscall_call+0x7/0xb
>
> Code: 83 3b 02 74 7a ff 83 00 01 00 00 b8 00 e0 ff ff 21 e0 ff 48
> <6>note: pppd[3155] exited with preempt_count 1
> bad: scheduling while atomic!
> Call Trace:
> [<c0120304>] schedule+0x6e4/0x6f0
> [<c015f8d1>] unmap_page_range+0x41/0x70
> [<c015fb1e>] unmap_vmas+0x21e/0x350
> [<c016562b>] exit_mmap+0xcb/0x2c0
> [<c0123896>] mmput+0xb6/0x140
> [<c0129dc2>] do_exit+0x282/0x900
> [<c010b57c>] die+0x21c/0x220
> [<c011dbcc>] do_page_fault+0x15c/0x4ca
> [<c01519a9>] buffered_rmqueue+0xc9/0x280
> [<c011ef88>] kernel_map_pages+0x28/0x60
> [<c0151e5f>] __alloc_pages+0x2ff/0x360
> [<c011da70>] do_page_fault+0x0/0x4ca
> [<c010add5>] error_code+0x2d/0x38
> [<c01852a0>] exact_lock+0x0/0x20
> [<c01853b8>] cdev_get+0x28/0xb0
> [<c0197033>] dput+0x23/0x680
> [<c01852b1>] exact_lock+0x11/0x20
> [<c02d6038>] kobj_lookup+0x128/0x220
> [<c0185290>] exact_match+0x0/0x10
> [<c0184cd6>] chrdev_open+0x446/0x610
> [<c01573bc>] kmem_cache_alloc+0x14c/0x1c0
> [<c01f9e1f>] devfs_open+0x24f/0x270
> [<c0174f11>] dentry_open+0x151/0x220
> [<c0174db6>] filp_open+0x66/0x70
> [<c01755d3>] sys_open+0x53/0x90
> [<c010a3ab>] syscall_call+0x7/0xb
>
> Unable to handle kernel paging request at virtual address d19fa300
> printing eip:
> c01853b8
> *pde = 0f956067
> *pte = 00000000
> Oops: 0000 [#2]
> CPU: 0
> EIP: 0060:[<c01853b8>] Not tainted
> EFLAGS: 00010202
> EIP is at cdev_get+0x28/0xb0
> eax: c6186000 ebx: d19fa300 ecx: 0000006c edx: c01852a0
> esi: 00000001 edi: cce31c4c ebp: c6187e78 esp: c6187e68
> ds: 007b es: 007b ss: 0068
> Process pppd (pid: 3158, threadinfo=c6186000 task=c615e000)
> Stack: c0197033 ccb78864 00006c00 00000000 c6187e84 c01852b1 cce31c4c
> c6187ebc
> c02d6038 00006c00 cce31c4c 00000282 c6186000 c6186000 cce31c4c
> c0185290
> 000000ff 6c006040 c6186000 00000000 ffffffed c6187ef8 c0184cd6
> cffcb004
> Call Trace:
> [<c0197033>] dput+0x23/0x680
> [<c01852b1>] exact_lock+0x11/0x20
> [<c02d6038>] kobj_lookup+0x128/0x220
> [<c0185290>] exact_match+0x0/0x10
> [<c0184cd6>] chrdev_open+0x446/0x610
> [<c01573bc>] kmem_cache_alloc+0x14c/0x1c0
> [<c01f9e1f>] devfs_open+0x24f/0x270
> [<c0174f11>] dentry_open+0x151/0x220
> [<c0174db6>] filp_open+0x66/0x70
> [<c01755d3>] sys_open+0x53/0x90
> [<c010a3ab>] syscall_call+0x7/0xb
>
> Code: 83 3b 02 74 7a ff 83 00 01 00 00 b8 00 e0 ff ff 21 e0 ff 48
> <6>note: pppd[3158] exited with preempt_count 1
> bad: scheduling while atomic!
> Call Trace:
> [<c0120304>] schedule+0x6e4/0x6f0
> [<c015f8d1>] unmap_page_range+0x41/0x70
> [<c015fb1e>] unmap_vmas+0x21e/0x350
> [<c016562b>] exit_mmap+0xcb/0x2c0
> [<c0123896>] mmput+0xb6/0x140
> [<c0129dc2>] do_exit+0x282/0x900
> [<c010b57c>] die+0x21c/0x220
> [<c011dbcc>] do_page_fault+0x15c/0x4ca
> [<c01519a9>] buffered_rmqueue+0xc9/0x280
> [<c01ba7ae>] proc_alloc_inode+0x1e/0x80
> [<c011ef88>] kernel_map_pages+0x28/0x60
> [<c0151e5f>] __alloc_pages+0x2ff/0x360
> [<c011da70>] do_page_fault+0x0/0x4ca
> [<c010add5>] error_code+0x2d/0x38
> [<c01852a0>] exact_lock+0x0/0x20
> [<c01853b8>] cdev_get+0x28/0xb0
> [<c0197033>] dput+0x23/0x680
> [<c01852b1>] exact_lock+0x11/0x20
> [<c02d6038>] kobj_lookup+0x128/0x220
> [<c0185290>] exact_match+0x0/0x10
> [<c0184cd6>] chrdev_open+0x446/0x610
> [<c01573bc>] kmem_cache_alloc+0x14c/0x1c0
> [<c01f9e1f>] devfs_open+0x24f/0x270
> [<c0174f11>] dentry_open+0x151/0x220
> [<c0174db6>] filp_open+0x66/0x70
> [<c01755d3>] sys_open+0x53/0x90
> [<c010a3ab>] syscall_call+0x7/0xb
--
Florian Zimmermann <[email protected]>