Re: debugging lack of link events

Quoting Dan Williams <dcbw redhat com>:

I'm looking at this too, my e1000 driver seems to take a _really_ long
time to notify the netlink socket that the device has changed status
(like 20s or so?).  That's not cool.  I'm attempting to distill a
testcase that I could send to kernel people, you might be able to use it
too to narrow the causes down.

Well, I do see the kernel log message almost immediately. I haven't looked into
the kernel code-path between the link-up printk() and the netlink message.

Anyways, I need to leave for dinner -- I should be back in several hours to
follow up.



      Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory
      Member, MIT Student Information Processing Board  (SIPB)
      URL:    PP-ASEL-IA     N1NWH
      warlord MIT EDU                        PGP key available

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]