public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Michal Piotrowski <michal.k.k.piotrowski@gmail.com>
To: linux-scsi@vger.kernel.org
Subject: Fwd: Fw: [OOPS] 2.6.13-mm2 scsi, sata, ich5
Date: Mon, 12 Sep 2005 11:38:42 +0200	[thread overview]
Message-ID: <6bffcb0e05091202382d2493c@mail.gmail.com> (raw)
In-Reply-To: <6bffcb0e05091202296a07f1ad@mail.gmail.com>

---------- Forwarded message ----------
From: Michal Piotrowski <michal.k.k.piotrowski@gmail.com>
Date: 12-Sep-2005 11:29
Subject: Re: Fw: [OOPS] 2.6.13-mm2 scsi, sata, ich5
To: Andrew Morton <akpm@osdl.org>
Cc: LKML <linux-kernel@vger.kernel.org>


Hi,

On 12/09/05, Andrew Morton <akpm@osdl.org> wrote:
>
> This is a strange trace.   I assume one of the WARN_ON()s in
> kref_put() has triggered and there's stack stuff missing.   Or
> Maybe it's an oops under scsi_end_request(), but the oops trace doesn't
> use show_trace(), whcih that output is from.   But if it's not
> an oops, why is the Code: dump there.
>
> Head spins.   Michal, can you try to gather another trace?   Is there
> info missing from this one?
>
> (It's quite possibly a scsi thing rather than a sata thing, btw).
>

The oops always hapen about 3 seconds after system start booting. When
it hapen I can't see what is up, because shift+pageup doesn't work.
So, AFAIK the only way to catch that oops is serial console?

Regards,
Michal Piotrowski

  parent reply	other threads:[~2005-09-12  9:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-12  6:21 Fw: [OOPS] 2.6.13-mm2 scsi, sata, ich5 Andrew Morton
     [not found] ` <6bffcb0e05091202296a07f1ad@mail.gmail.com>
2005-09-12  9:38   ` Michal Piotrowski [this message]
2005-09-12  9:40   ` Andrew Morton

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=6bffcb0e05091202382d2493c@mail.gmail.com \
    --to=michal.k.k.piotrowski@gmail.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox