Driver Problems? Questions? Issues?
Put OSR's experience to work for you! Contact us for assistance with:
  • Creating the right design for your requirements
  • Reviewing your existing driver code
  • Analyzing driver reliability/performance issues
  • Custom training mixed with consulting and focused directly on your specific areas of interest/concern.
Check us out. OSR, the Windows driver experts.

Monthly Seminars at OSR Headquarters

East Coast USA
Windows Internals and SW Drivers, Dulles (Sterling) VA, 13 November 2017

Kernel Debugging & Crash Analysis for Windows, Nashua (Amherst) NH, 4 December 2017

Writing WDF Drivers I: Core Concepts, Nashua (Amherst) NH, 8 January 2018

WDF Drivers II: Advanced Implementation Techniques, Nashua (Amherst) NH, 15 January 2018


Go Back   OSR Online Lists > ntdev
Welcome, Guest
You must login to post to this list
  Message 1 of 8  
15 Jul 17 04:40
prabhakar vinayagam
xxxxxx@gmail.com
Join Date: 29 Jan 2016
Posts To This List: 102
when enable "c" states , COM port were not worked at high baudrate

Hi all, When i disable the "c" states in bios side , com port detected the "receive buffer overrun " in windows 10. When i enable the "c" states in bios side, cpu is not enter into acpi c states if the com port used high baudrate to do data transfer in windows 10 where it used the inbox driver. It uses the pnpo500 pnp pc device. How i can fix this issue in windows sample driver 10 of serenum to check the driver enter into acpi c states to fix it were working in high baudrate ? when i check in PassMark where com port detected the receive buffer overrun. Could you please help on this issue to fix in windows sample driver for serial port. Regards, Prabhakar V
  Message 2 of 8  
16 Jul 17 17:33
Pavel A
xxxxxx@fastmail.fm
Join Date: 21 Jul 2008
Posts To This List: 2401
when enable "c" states , COM port were not worked at high baudrate

Maybe this is because PassMark does not support very high speed serial ports well. Look for more specialized benchmark for serial I/O. Good design of the driver probably can help too, because C states interfere with latency of interrupt handling. A custom driver for your device can do interrupt moderation or even disable C states on the CPU it runs on. Be creative, try to think out of the box :) -- pa
  Message 3 of 8  
16 Jul 17 20:50
Peter Viscarola (OSR)
xxxxxx@osr.com
Join Date:
Posts To This List: 5949
List Moderator
when enable "c" states , COM port were not worked at high baudrate

Didn't we already see this post... like, last week? Peter OSR @OSRDrivers
  Message 4 of 8  
17 Jul 17 02:35
prabhakar vinayagam
xxxxxx@gmail.com
Join Date: 29 Jan 2016
Posts To This List: 102
when enable "c" states , COM port were not worked at high baudrate

when enable "c" states , COM port were not worked at high baudrate [Peter ]Didn't we already see this post... like, last week?' [Prabhakar] yes i have posted already but i need to see that when we enable the c states in bios side , it were working for high baudrate. What will be the impact when we enable the c states it doesn't work for high baudrate in windows 10 where showing receive buffer overrun in inbox driver. What will be imapct when we enable the c states it doesnt work ? What i have to do in windows sample driver code and fix this error? if we disbale it is working for high baudrate in passmark tool.
  Message 5 of 8  
17 Jul 17 02:47
Tim Roberts
xxxxxx@probo.com
Join Date: 28 Jan 2005
Posts To This List: 11654
when enable "c" states , COM port were not worked at high baudrate

On Jul 16, 2017, at 11:35 PM, xxxxx@gmail.com xxxxx@lists.osr.com wrote: > > when enable "c" states , COM port were not worked at high baudrate > [Peter ]Didn't we already see this post... like, last week?' > [Prabhakar] yes i have posted already but i need to see that when we enable the c states in bios side , it were working for high baudrate. > > What will be the impact when we enable the c states it doesn't work for high baudrate in windows 10 where showing receive buffer overrun in inbox driver. > > What will be imapct when we enable the c states it doesnt work ? > What i have to do in windows sample driver code and fix this error? > if we disbale it is working for high baudrate in passmark tool. What are you expecting here? The answers are not going to change. As I have tried to tell you in public and in private, there is no magic answer here. The slowed down CPU can't get around to service your interrupt before the hardware FIFO fills. So, you either turn off the use of C states, you change the level at which you get the interrupt, or you configure a larger buffer. That's it. There are no other choices. That means you need to know your hardware, to know how the FIFOs are configured. I don't think you know that yet. — Tim Roberts, xxxxx@probo.com Providenza & Boekelheide, Inc.
  Message 6 of 8  
07 Aug 17 03:36
prabhakar vinayagam
xxxxxx@gmail.com
Join Date: 29 Jan 2016
Posts To This List: 102
when enable "c" states , COM port were not worked at high baudrate

Hi Tim, Is there any option to disable the c states in Driver side when we enable the BIOS c state. Is there any api to read the configuration value of BIOS chnanged of c states. Regards, Prabhakar V
  Message 7 of 8  
07 Aug 17 21:28
Tim Roberts
xxxxxx@probo.com
Join Date: 28 Jan 2005
Posts To This List: 11654
when enable "c" states , COM port were not worked at high baudrate

xxxxx@gmail.com xxxxx@lists.osr.com wrote: > Is there any option to disable the c states in Driver side when we enable the BIOS c state. Have you searched for this? I found a couple of articles that talk about potential methods of altering the power behavior. HOWEVER, you are looking in the wrong direction. Your hardware and driver ought to be able to handle this. Have you done any experiments with the FIFO levels, as I mentioned? -- Tim Roberts, xxxxx@probo.com Providenza & Boekelheide, Inc.
  Message 8 of 8  
08 Aug 17 18:34
anton bassov
xxxxxx@hotmail.com
Join Date: 16 Jul 2006
Posts To This List: 4398
when enable "c" states , COM port were not worked at high baudrate

> What are you expecting here? The answers are not going to change. ..... > That means you need to know your hardware, to know how the FIFOs are configured. > I don't think you know that yet. Well, we were all inexperienced once, right. Therefore, "please guide the OP in the same" and explain to him (2^(N!))! times why "ports were not worked" (in fact, I don't know what the argument to the above function may be like in this context - if it is 2 this function evaluates just to 24, which is , apparently, insufficient, but at 3 it already grows to the factorial of 64, which is, probably, a way too much even by your standards) .... Anton Bassov
Posting Rules  
You may not post new threads
You may not post replies
You may not post attachments
You must login to OSR Online AND be a member of the ntdev list to be able to post.

All times are GMT -5. The time now is 03:10.


Copyright ©2015, OSR Open Systems Resources, Inc.
Based on vBulletin Copyright ©2000 - 2005, Jelsoft Enterprises Ltd.
Modified under license