Re: solution to printk() blocking interrupts?

Hello, I wrote:

  Not sure if Stephen was the right person to CC, including Matt now...

quoted

quoted

quoted

What controls this? "carrier detect appears untrustworthy, waiting 4 seconds"
Get that fixed and this patch could be useful,

quoted

quoted

Does the driver properly uses netif_carrier_on/off to signal the
system when the link is up/down ?

quoted

 Implementing the poll_controller() method in the network driver is usually

quoted

  Looks like the answer is "no"...

  Hm... it uses phylib, so probably it does that. That message and a 4 s pause appears if the carrier is seen in <10 ms after opening the device.

   Oops, not 10 -- 100 ms (HZ / 10).

Maybe this threshold needs to be changed?

   Seems like too much indeed.

WBR, Sergei