From: Jeffrin Thalakkottoor <jeffrin@rajagiritech.edu.in>
To: ruscur@russell.cc, sbobroff@linux.ibm.com, oohall@gmail.com,
Bjorn Helgaas <bhelgaas@google.com>
Cc: linuxppc-dev@lists.ozlabs.org, linux-pci@vger.kernel.org,
lkml <linux-kernel@vger.kernel.org>,
stable@vger.kernel.org
Subject: Re: PROBLEM: PCIe Bus Error atleast
Date: Sat, 2 Nov 2019 00:34:01 +0530 [thread overview]
Message-ID: <CAG=yYwmYCLOktQxhsyjarybbR+aF2Z3RuXVj4hfE5wD_6nJjNA@mail.gmail.com> (raw)
In-Reply-To: <CAG=yYwmQHyp62qKDoiM091iXKs5iP8rNBLs9kc7Wi_PDCgMrbw@mail.gmail.com>
On Sat, Nov 2, 2019 at 12:15 AM Jeffrin Thalakkottoor
<jeffrin@rajagiritech.edu.in> wrote:
> But i think when i tried again today i could not reprodu....
i do not know why, but now iam able to reproduce the error
more details follows
---------------------x------x------------------------------------------
GNU Make 4.2.1
Binutils 2.33.1
Util-linux 2.33.1
Mount 2.33.1
Linux C Library 2.29
Dynamic linker (ldd) 2.29
Procps 3.3.15
Kbd 2.0.4
Console-tools 2.0.4
Sh-utils 8.30
Udev 241
------------------------x-----------------x---------------------------
$gcc --version
gcc (Debian 9.2.1-14) 9.2.1 20191025
Copyright (C) 2019 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
---------------------x----------x----------------------------------
--
software engineer
rajagiri school of engineering and technology
next prev parent reply other threads:[~2019-11-01 19:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-01 18:45 PROBLEM: PCIe Bus Error atleast Jeffrin Thalakkottoor
2019-11-01 19:04 ` Jeffrin Thalakkottoor [this message]
2019-11-03 23:38 ` Oliver O'Halloran
[not found] ` <CAG=yYw=RjFg4NnR2jxkPujg5M2W01CP92bJZU77OZjaqH2vnOg@mail.gmail.com>
2019-11-04 19:34 ` Jeffrin Thalakkottoor
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='CAG=yYwmYCLOktQxhsyjarybbR+aF2Z3RuXVj4hfE5wD_6nJjNA@mail.gmail.com' \
--to=jeffrin@rajagiritech.edu.in \
--cc=bhelgaas@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=oohall@gmail.com \
--cc=ruscur@russell.cc \
--cc=sbobroff@linux.ibm.com \
--cc=stable@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;
as well as URLs for NNTP newsgroup(s).