All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-scsi@vger.kernel.org
Subject: [Bug 207855] arcconf host reset causes kernel panic -> driver crash?
Date: Sat, 06 Jun 2020 09:01:52 +0000	[thread overview]
Message-ID: <bug-207855-11613-65jbrZzXKy@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-207855-11613@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=207855

Janpieter Sollie (janpieter.sollie@edpnet.be) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |OBSOLETE

--- Comment #7 from Janpieter Sollie (janpieter.sollie@edpnet.be) ---
I figured out it was due to an insufficient +5V line which made devices
function the wrong way,I added some extra +5V juice and it worked without any
problem.
Neverthless, is it an option to "isolate" the storage driver somewhat so the
other PCI devices are kept up-and-running?
There are still some points of investigation:
-If it's PCI related, why does the dedicated VGA + onboard USB still work?
-If it's storage subsystem related, why does network IO fail?
-If it's driver related, why is AHCI going down as well?
I guess this is not supposed to happen, so I'll see whether I can make it crash
again, and eventually try to reset the whole PCI bus (and see whether that
would help)

-- 
You are receiving this mail because:
You are the assignee for the bug.

  parent reply	other threads:[~2020-06-06  9:01 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-22  8:49 [Bug 207855] New: arcconf host reset causes kernel panic -> driver crash? bugzilla-daemon
2020-05-22  9:19 ` [Bug 207855] " bugzilla-daemon
2020-05-22  9:40 ` bugzilla-daemon
2020-05-23 16:29 ` bugzilla-daemon
2020-05-23 17:53 ` bugzilla-daemon
2020-05-23 18:38 ` bugzilla-daemon
2020-05-23 19:09 ` bugzilla-daemon
2020-06-06  9:01 ` bugzilla-daemon [this message]
2020-07-13 11:46 ` bugzilla-daemon
2020-07-13 11:47 ` bugzilla-daemon
2020-07-13 19:10 ` bugzilla-daemon
2020-07-15  8:45 ` bugzilla-daemon
2020-07-15  8:50 ` bugzilla-daemon
2020-07-19  6:36 ` bugzilla-daemon
2020-11-07 17:11 ` bugzilla-daemon

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=bug-207855-11613-65jbrZzXKy@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.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.