From: Nick Warne <nick@ukfsn.org>
To: Jon Masters <jonathan@jonmasters.org>
Cc: linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org,
Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
Subject: Re: Peculiar out-of-sync boot log lines
Date: Thu, 29 Nov 2007 20:03:32 +0000 [thread overview]
Message-ID: <20071129200332.2130298b@linuxamd.linicks.net> (raw)
In-Reply-To: <1196365871.6473.107.camel@perihelion>
Hi Jon,
On Thu, 29 Nov 2007 14:51:11 -0500
Jon Masters <jonathan@jonmasters.org> wrote:
>
> On Thu, 2007-11-29 at 19:37 +0000, Nick Warne wrote:
> > Hi all,
> >
> > 2.6.23.9
> >
> > I have noticed after applying Bart's patch to word93 blacklist my
> > new DVD drive:
> >
> > http://lkml.org/lkml/2007/10/23/475
> >
> > I see now in logs (look at the hdd line:
> >
> > [dmesg]
> > hdc: 39876480 sectors (20416 MB) w/2048KiB Cache, CHS=39560/16/63,
> > UDMA(66)
> > hdc: cache flushes not supported
> > hdc: hdc1
> > hdd: ATAPI 48X DVD-ROM DVD-R-RAM CD-R/RW drive, 2048kB Cache<7>hdd:
> > skipping word 93 validity check
> > , UDMA(66)
> > Uniform CD-ROM driver Revision: 3.20
>
> Only very early in boot are you guaranteed for things to execute
> sequentially, and for logs to look nice and pretty.
>
Yes, but where does the <7> come from?
Nick
--
Free Software Foundation Associate Member 5508
next prev parent reply other threads:[~2007-11-29 20:03 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-29 19:37 Peculiar out-of-sync boot log lines Nick Warne
2007-11-29 19:51 ` Jon Masters
2007-11-29 20:03 ` Nick Warne [this message]
2007-11-29 20:13 ` Joe Perches
2007-11-29 20:12 ` Mark Lord
2007-12-01 21:59 ` Bartlomiej Zolnierkiewicz
2007-12-01 23:14 ` Randy Dunlap
2007-12-02 18:30 ` Bartlomiej Zolnierkiewicz
2007-12-07 16:34 ` Sergei Shtylyov
2007-12-09 15:44 ` Bartlomiej Zolnierkiewicz
2007-12-23 17:30 ` Nick Warne
2007-12-02 17:31 ` Nick Warne
2007-12-02 18:34 ` Bartlomiej Zolnierkiewicz
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=20071129200332.2130298b@linuxamd.linicks.net \
--to=nick@ukfsn.org \
--cc=bzolnier@gmail.com \
--cc=jonathan@jonmasters.org \
--cc=linux-ide@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.