Bug 549011

Summary:	pppd problem after update from Fedora 11 to 12
Product:	[Fedora] Fedora	Reporter:	Mirko Fluher <mir>
Component:	ppp	Assignee:	Jiri Skala <jskala>
Status:	CLOSED INSUFFICIENT_DATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	urgent	Docs Contact:
Priority:	low
Version:	12	CC:	aglotov, jskala
Target Milestone:	---
Target Release:	---
Hardware:	i386
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2010-06-30 12:51:01 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Mirko Fluher 2009-12-19 22:39:10 UTC

Following an upgrade from Fedora 11 to Fedora 12, I have a severe problem with pppd. I call it in a script:

exec sudo /usr/sbin/pppd nodefaultroute noauth nodetach ms-dns 192.168.1.254 192.168.2.21:192.168.2.11

and I get the following fatal error:

Dec 18 17:04:08 pax pppd[4942]: pppd 2.4.4 started by Pxxx, uid 0
Dec 18 17:04:46 pax pppd[4942]: Couldn't get channel number: Invalid argument
Dec 18 17:04:46 pax pppd[4942]: Exit.
Dec 18 17:04:46 pax init: ttyS0 main process ended, respawning

The above call works fine with Fedora 11 and has worked with Fedora10 and previous versions, but not with Fedora12 with latest updates.

Comment 1 Jiri Skala 2010-03-01 14:48:56 UTC

This is strange. It's looks like issue in ppp kernel module. The correct startup should look like this:

Feb 28 21:49:52 localhost pppd[7147]: pppd 2.4.4 started by root, uid 0
Feb 28 21:49:52 localhost pppd[7147]: Using interface ppp0
Feb 28 21:49:52 localhost pppd[7147]: Connect: ppp0 <--> /dev/ttyACM0
...

Yours failure is messaged when fails inquiry to kernel.
Please, could you check lsmod if there is ppp module and devices /dev/ppp*? Which kernel do you use?

It could be a corruption during migrating F11->f12.

Thanks, Jiri

Comment 2 Jiri Skala 2010-05-27 07:29:39 UTC

There is no answer to comment #1. Well, another question is:

do you still observe this issue?

"Couldn't get channel..." means inability to open an instance of /dev/ppp ...