2.6.9: serial_core: uart_open
The uart_open code loops waiting for CD to be asserted (whenever CLOCAL is not set). The bottom of the loop contains the following code:
up(&state->sem);schedule();down(&state->sem);
if( signal_pending(current) )
break;
When I issue an open("/dev/ttyS1", O_RDWR) from a terminal session on the console, the system seems to come to a stop in this loop until the process is killed. I suspect that the scheduler is choosing this process to run again because of an elevated console priority of some sort.
Is there a kernel mechanism to put a process to sleep until awakened by an event to replace this looping behaviour?
Thanks, karl malbrain, malbrain-at-yahoo-dot-com
Quoted 9 lines · karl malbrain
The
uart_opencode loops waiting for CD to be asserted (whenever CLOCAL is not set). The bottom of the loop contains the following code:
up(&state->sem);schedule();down(&state->sem);
if( signal_pending(current) )
break;
This does cause the process to sleep - in an interruptible wait.
Please give more details about the problem you're seeing. Have you tried getting a process listing from a different virtual console, xterm or whatever you normally use? What does that say?
Signature · 3 lines
Russell King Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/ maintainer of: 2.6 Serial core
-----Original Message-----
From: Russell King
Sent: Tuesday, July 12, 2005 2:04 PM
To: karl malbrain
Cc: [email protected]
Subject: Re: 2.6.9: serial_core: uart_open
Quoted 9 lines · karl malbrain
The
uart_opencode loops waiting for CD to be asserted (whenever CLOCAL is not set). The bottom of the loop contains the following code:
up(&state->sem);schedule();down(&state->sem);
if( signal_pending(current) )
break;
This does cause the process to sleep - in an interruptible wait.
Please give more details about the problem you're seeing. Have you tried getting a process listing from a different virtual console, xterm or whatever you normally use? What does that say?
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of: 2.6 Serial core
Sorry, but I cannot get anything else to run. I can barely get XWindows to kill the process.
What prevents schedule() from returning to the current process w/o any delay?
Thanks, karl m