From: Andrew Morton <akpm@osdl.org>
To: bernd-schubert@gmx.de
Cc: bernd.schubert@pci.uni-heidelberg.de,
James.Bottomley@steeleye.com, linux-kernel@vger.kernel.org,
linux-scsi@vger.kernel.org, Jeff Garzik <jgarzik@pobox.com>
Subject: Re: a couple of oopses with 2.6.14
Date: Fri, 10 Feb 2006 11:29:58 -0800 [thread overview]
Message-ID: <20060210112958.025a7bfb.akpm@osdl.org> (raw)
In-Reply-To: <200602101924.45467.bernd.schubert@pci.uni-heidelberg.de>
Bernd Schubert <bernd.schubert@pci.uni-heidelberg.de> wrote:
>
> > Can you test 2.6.15?
>
> Yes, 2.6.15.3 works, no oopses.
Some progress.
> Only this information
>
> [4294743.341000] scsi0 : ata_piix
> [4294743.514000] ATA: abnormal status 0x7F on port 0xE407
>
> I can't test if sata works, there's just nothing connected.
Has this machine's sata support ever worked? If so, in which kernel?
(Apologies if you've already described this).
> Btw, the printk timing information seem to be uninitalized, is this by
> intentention or is it a bug?
It's expected. We use a very raw, low-level funtion for the printk
timestamping because we don't want to be taking locks from within printk.
The timestamping is mainly for working out the time duration between
printk's, rather than for absolute time.
next prev parent reply other threads:[~2006-02-10 19:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-09 18:34 a couple of oopses with 2.6.14 Bernd Schubert
2006-02-09 23:27 ` Andrew Morton
2006-02-09 23:27 ` Andrew Morton
2006-02-09 23:41 ` James Bottomley
2006-02-10 0:32 ` Bernd Schubert
2006-02-10 0:32 ` Bernd Schubert
2006-02-10 18:24 ` Bernd Schubert
2006-02-10 18:24 ` Bernd Schubert
2006-02-10 19:29 ` Andrew Morton [this message]
2006-02-10 19:51 ` Bernd Schubert
2006-02-10 19:51 ` Bernd Schubert
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=20060210112958.025a7bfb.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=James.Bottomley@steeleye.com \
--cc=bernd-schubert@gmx.de \
--cc=bernd.schubert@pci.uni-heidelberg.de \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@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.