From: "Alessandro Suardi" <alessandro.suardi@gmail.com>
To: "Alan Cox" <alan@lxorguk.ukuu.org.uk>
Cc: "Meelis Roos" <mroos@linux.ee>,
"Linux Kernel list" <linux-kernel@vger.kernel.org>
Subject: Re: ata4294967295: failed to start port (errno=-19)
Date: Thu, 29 Nov 2007 21:06:12 +0100 [thread overview]
Message-ID: <5a4c581d0711291206x5d92c166iba4e4b6d336643dc@mail.gmail.com> (raw)
In-Reply-To: <20071128200716.14eccfdd@the-village.bc.nu>
On Nov 28, 2007 9:07 PM, Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:
> > This message comes from 2.6.24-rc3 + todays git, version
> > a531a141089714efe39eca89593524fdf05104f2. I did grep the logs and found
> > that it first appeared in 2.6.24-rc1 (+ some git mayve) on Nov 3.
> > I used 2.6.23 before that and it did not show this message.
>
> Can you stick a stack trace in at that point ? That would help diagnose
> it a great deal quicker.
I've also been seeing this for a while on my Dell Latitude D610,
but stuff just works, so... I'm overloaded at this time, if nobody
gets there first I'll give a go at tracing this next week.
--alessandro
"Damaged people are dangerous. They know they can survive."
(Anna Barton/Juliette Binoche, 'Damage')
next prev parent reply other threads:[~2007-11-29 20:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-28 17:59 Meelis Roos
2007-11-28 20:07 ` Alan Cox
2007-11-29 20:06 ` Alessandro Suardi [this message]
2007-11-30 7:15 ` Craig Schlenter
2007-11-30 12:34 ` Meelis Roos
2007-11-30 15:23 ` [PATCH] libata: Fix early use of port printk. (Was Re: ata4294967295: failed to start port (errno=-19)) Alan Cox
2007-12-01 18:25 ` Meelis Roos
2007-12-01 22:45 ` Jeff Garzik
2007-11-30 21:58 ` ata4294967295: failed to start port (errno=-19) Alessandro Suardi
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=5a4c581d0711291206x5d92c166iba4e4b6d336643dc@mail.gmail.com \
--to=alessandro.suardi@gmail.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=mroos@linux.ee \
/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®