public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Troels Walsted Hansen" <troels@thule.no>
To: "Andrew Morton" <andrewm@uow.edu.au>
Cc: linux-kernel@vger.kernel.org
Subject: RE: [PATCH] klogd busy loop on zero byte (output from 3c59x driver)
Date: Thu, 11 Jan 2001 15:06:20 +0100	[thread overview]
Message-ID: <CKECLHEEHJOPHGPCOCKPGECDCCAA.troels@thule.no> (raw)
In-Reply-To: <3A5DA113.DC8DB21C@uow.edu.au>

> Yep.  %02x%02x it now is.

I suppose it might be worthwhile to search the kernel sources for other
instances of printk("%c"), there's no telling when all distributions will be
up to date with new sysklogd releases...

> The code in question was snitched from pcmcia-cs's 3c575_cb.c, and
> I assume David would have heard if it was busting klogd.  Maybe
> there's a klogd version problem, or maybe your NIC's EEPROM is hosed?

I believe I have the latest version of klogd...

My NIC is a 3Com PCI 3c556 Laptop Tornado, in a Dell Latitude C600 laptop.
The driver reports the product code as "00" and the rev as "00.0", the date
however is "03-01-00" which sounds fairly reasonable (although the laptop is
brand new).

Needless to say, it also works fine, otherwise I would probably have
attacked the driver first...

--
Troels Walsted Hansen
troels@thule.no

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

  reply	other threads:[~2001-01-11 14:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-11  8:48 [PATCH] klogd busy loop on zero byte (output from 3c59x driver) Troels Walsted Hansen
2001-01-11 11:41 ` Manfred
2001-01-11 12:03 ` Andrew Morton
2001-01-11 14:06   ` Troels Walsted Hansen [this message]
2001-01-11 17:30   ` David Hinds

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=CKECLHEEHJOPHGPCOCKPGECDCCAA.troels@thule.no \
    --to=troels@thule.no \
    --cc=andrewm@uow.edu.au \
    --cc=linux-kernel@vger.kernel.org \
    /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