From: "Michael T. Babcock" <mbabcock@fibrespeed.net>
To: linux-kernel@vger.kernel.org
Subject: Unknown error (please help direct it)
Date: Thu, 2 Jan 2003 10:24:38 -0500 [thread overview]
Message-ID: <20030102152438.GB12769@godzilla.fibrespeed.net> (raw)
I have this in my logs from yesterday, with no clear indication as to
what subsystem it relates to. Please help me direct this to the appropriate
persons (and CC me, if possible, in any replies). There are no kernel messages
for several minutes before or after these lines.
13:50:28 vpn kernel: Flags; bus-master 1, dirty 2677573(5) current 2677
13:50:28 vpn kernel: Transmit list 00000000 vs. c57ad340.
13:50:28 vpn kernel: 0: @c57ad200 length 800005ea status 000105ea
13:50:28 vpn kernel: 1: @c57ad240 length 800003b2 status 000103b2
13:50:28 vpn kernel: 2: @c57ad280 length 800005ea status 000105ea
13:50:28 vpn kernel: 3: @c57ad2c0 length 800005ea status 000105ea
13:50:28 vpn kernel: 4: @c57ad300 length 800005ea status 800105ea
13:50:28 vpn kernel: 5: @c57ad340 length 800003b2 status 000103b2
13:50:28 vpn kernel: 6: @c57ad380 length 800005ea status 000105ea
13:50:28 vpn kernel: 7: @c57ad3c0 length 800005ea status 000105ea
13:50:28 vpn kernel: 8: @c57ad400 length 800005ea status 000105ea
13:50:28 vpn kernel: 9: @c57ad440 length 800005ea status 000105ea
13:50:28 vpn kernel: 10: @c57ad480 length 800005ea status 000105ea
13:50:28 vpn kernel: 11: @c57ad4c0 length 800003b2 status 000103b2
13:50:28 vpn kernel: 12: @c57ad500 length 800005ea status 000105ea
13:50:28 vpn kernel: 13: @c57ad540 length 800005ea status 000105ea
13:50:28 vpn kernel: 14: @c57ad580 length 800005ea status 000105ea
13:50:28 vpn kernel: 15: @c57ad5c0 length 800005ea status 000105ea
--
Michael T. Babcock
CTO, FibreSpeed Ltd. (Hosting, Security, Consultation, Database, etc)
http://www.fibrespeed.net/~mbabcock/
next reply other threads:[~2003-01-02 14:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-02 15:24 Michael T. Babcock [this message]
2003-01-02 15:52 ` Sam Ravnborg
2003-01-02 22:18 ` Krzysztof Halasa
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=20030102152438.GB12769@godzilla.fibrespeed.net \
--to=mbabcock@fibrespeed.net \
--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
all inboxes | Powered by JetHome®