:: What were you doing when this happened?
I don't know, to be honest. Looks like it might have happened at boot-up, as
the entries are intertwined with the network card and parallel port ones:
parport0: assign_addrs: aa5500ff(38)
xfs_create looping, dir ino 0x40089, ino 0x4c240, ide0(3,7)
Linux Tulip driver version 0.9.14e (April 20, 2001)
tulip0: EEPROM default media type Autosense.
tulip0: Index #0 - Media MII (#11) described by a 21142 MII PHY (3) block.
00:12.0: MII transceiver #1 config 3000 status 782d advertising 01e1.
eth0: Digital DS21143 Tulip rev 65 at 0xec00, 00:C0:F0:4C:DD:DB, IRQ 18.
xfs_create looping, dir ino 0x40089, ino 0x4c241, ide0(3,7)
xfs_create looping, dir ino 0x140081, ino 0x14008d, ide0(3,7)
eth0: Setting full-duplex based on MII#1 link partner capability of 45e1.
xfs_create looping, dir ino 0x140081, ino 0x14008e, ide0(3,7)
xfs_create looping, dir ino 0x40089, ino 0x4c243, ide0(3,7)
xfs_create looping, dir ino 0x40089, ino 0x4c244, ide0(3,7)
xfs_create looping, dir ino 0x40089, ino 0x4c247, ide0(3,7)
xfs_create looping, dir ino 0x40089, ino 0x4c248, ide0(3,7)
xfs_create looping, dir ino 0x40089, ino 0x4c249, ide0(3,7)
xfs_create looping, dir ino 0x40089, ino 0x4c24a, ide0(3,7)
xfs_create looping, dir ino 0x140081, ino 0x140094, ide0(3,7)
xfs_create looping, dir ino 0x40089, ino 0x4c254, ide0(3,7)
-- Juha
|