network down after 'dkms status' command

Jeff Ewing jewing at
Tue Sep 8 20:21:23 CDT 2009

> >
> > Wondering if this is a possible fix (by upgrading to thelatest version):
> >
> >;a=commit;h=fa830463d5341e38f4a50f35b5dbef773ade1a09
> Possible. In this case, it was the 'dkms install' command that invoked
> udevtrigger, not 'dkms status'.  'dkms install' may have updated the
> kernel module for the currently running kernel, and then udevtrigger
> would have tried to load any new modules (not necessarily just the one
> you installed with the 'dkms install' command).  But it should not have
> affected the system if the module was already loaded...
> Matt Domsch

My collegue brought down another system last week, with yum upgrade,
trying to upgrade the megaraid SAS from 3.16 to the recommended 3.21.
Kernel version and network drivers are not being changed.

We will be the same upgrade, but with DKMS 2.1.0 on a dev system today.

Thank you.
Jeff Ewing

More information about the Linux-PowerEdge mailing list