From: "Dan Noé" <dpn@isomerica.net>
To: Stefan Richter <stefanr@s5r6.in-berlin.de>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
krh@redhat.com, linux1394-devel@lists.sourceforge.net
Subject: Re: 2.6.25-git16 -- BUG: unable to handle kernel NULL pointer dereference at 00000000 -- IP: [<c02dd5d5>] fw_show_drv_device_ids+0xd9/0xee
Date: Thu, 01 May 2008 10:37:21 -0400 [thread overview]
Message-ID: <4819D5A1.6080204@isomerica.net> (raw)
In-Reply-To: <4819C941.6030209@s5r6.in-berlin.de>
Stefan Richter wrote:
> I could look into keeping those messages down to only a single one per
> attempt to fetch the so-called configuration ROM of an added node.
Seems like this is ideal.
> (The ROM CRC error warning has been added in 2.6.22. Before Linux
> 2.6.22, the ROM CRC errors were silently accepted. The new alternative
> firewire drivers also do not warn about ROM CRC errors... yet...)
I like to be warned about things, even if there isn't anything I can
really do about it (fix my IEEE 1394 ROM CRC? :) But there doesn't seem
to be any point to repeating the message.
Do the repeats come because it prints each time the config ROM is accessed?
Cheers,
Dan
--
/--------------- - - - - - -
| Dan Noé
| http://isomerica.net/~dpn/
next prev parent reply other threads:[~2008-05-01 14:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-01 0:29 Miles Lane
2008-05-01 8:43 ` Stefan Richter
2008-05-01 13:08 ` Miles Lane
2008-05-01 13:44 ` Stefan Richter
2008-05-01 14:37 ` Dan Noé [this message]
2008-05-01 15:05 ` Stefan Richter
2008-05-02 18:14 ` [PATCH] ieee1394: reduce log noise about config ROM CRC errors Stefan Richter
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=4819D5A1.6080204@isomerica.net \
--to=dpn@isomerica.net \
--cc=krh@redhat.com \
--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®