I got an kernel oops over night.
Created attachment 35421 [details]
kernel oops trace
Seems a device bug; can you attach the output of lsmod so I can narrow the list
of suspects ?
Created attachment 35445 [details]
I think we found the cause; seems there's a nice race in the bdput function
versus opening of a new device.
Side question: is there a specific reason you're using e100 instead of eepro100
eepro100 doesn't work on my Intel STL2 MB.