Re: 2.6 git kernel reporting bug in knodemgrd_0 during boot

[Andrew Paprocki]

> > Andrew, what was the last kernel which didn't log this?

I was previously using a stock Debian snapshot from 2006-10-11 which
comes with the 2.6.17 kernel standard (vmlinuz-2.6.17-2-486 is what it
installs).
I had already rebuilt the 2.6.17 source that comes with that install,
tweaking the configuration for the VIA motherboard and it did not
report any problems. Last night I just git'd the latest 2.6 source and
copied the same .config from the previous kernel over, and answered
any new questions that popped up during make config for the newer
source.

> And did you change any of the IEEE1394 options in the kernel configuration?

I copied the .config from the working kernel over, and I don't believe
I changed anything from the working 2.6.17 configuration. These are
the options currently set:

# grep IEEE .config
# CONFIG_IEEE80211 is not set
# IEEE 1394 (FireWire) support
CONFIG_IEEE1394=y
# CONFIG_IEEE1394_VERBOSEDEBUG is not set
CONFIG_IEEE1394_OUI_DB=y
CONFIG_IEEE1394_EXTRA_CONFIG_ROMS=y
CONFIG_IEEE1394_CONFIG_ROM_IP1394=y
# CONFIG_IEEE1394_EXPORT_FULL_API is not set
# CONFIG_IEEE1394_PCILYNX is not set
CONFIG_IEEE1394_OHCI1394=y
# CONFIG_IEEE1394_VIDEO1394 is not set
CONFIG_IEEE1394_SBP2=y
CONFIG_IEEE1394_SBP2_PHYS_DMA=y
# CONFIG_IEEE1394_ETH1394 is not set
# CONFIG_IEEE1394_DV1394 is not set
# CONFIG_IEEE1394_RAWIO is not set

-Andrew
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/