Messages in this thread |  | | Subject | Re: [RFC] [PATCH] Net device error logging (revised) | From | Valdis.Kletnieks@vt ... | Date | Sat, 24 May 2003 04:05:41 -0400 |
| |
On Fri, 23 May 2003 23:21:24 PDT, Jim Keniston said:
> - With Steve Hemminger's creation of the "net" device class a few days > ago, the network device's interface name is now sufficient to find the > information about the underlying device in sysfs (even without running > ethtool). So these macros no longer log the device's driver name and > bus ID.
Is something *else* logging the driver name and bus ID?
Just because an interface is called 'eth2' when the message is logged doesn't mean it's still eth2 when you actually *read* the message. And no, you *can't* rely on finding the "renaming bus-ID to ethN" message in the logs - if the system is unstable the last bit of local logging may go bye-bye if not synced, and messages about network hardware problems are *very* prone to not making it to the syslog server (I wonder why? ;).
Been there, done that, it's not fun. Almost swapped out the wrong eth1 a *second* time before realizing what was really going on... [unhandled content-type:application/pgp-signature] |  |