mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Andrew Paprocki" <andrew@ishiboo.com>
To: "Stefan Richter" <stefanr@s5r6.in-berlin.de>
Cc: "Adrian Bunk" <bunk@stusta.de>,
	linux-kernel@vger.kernel.org,
	linux1394-devel@lists.sourceforge.net
Subject: Re: 2.6 git kernel reporting bug in knodemgrd_0 during boot
Date: Sun, 29 Oct 2006 18:49:41 -0500	[thread overview]
Message-ID: <76366b180610291549p1d4aecf1p2e0480b3c841b66c@mail.gmail.com> (raw)
In-Reply-To: <454538AA.9000104@s5r6.in-berlin.de>

> > 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

      reply	other threads:[~2006-10-29 23:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-29 21:41 Andrew Paprocki
2006-10-29 22:38 ` Adrian Bunk
2006-10-29 23:09   ` Stefan Richter
2006-10-29 23:26     ` Stefan Richter
2006-10-29 23:49       ` Andrew Paprocki [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=76366b180610291549p1d4aecf1p2e0480b3c841b66c@mail.gmail.com \
    --to=andrew@ishiboo.com \
    --cc=bunk@stusta.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux1394-devel@lists.sourceforge.net \
    --cc=stefanr@s5r6.in-berlin.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®