[prev in list] [next in list] [prev in thread] [next in thread] 

List:       haiku-bugs
Subject:    [haiku-bugs] Re: [Haiku] #16794: XHCI: Divide error exception in SubmitNormalRequest
From:       "Haiku" <trac () haiku-os ! org>
Date:       2021-04-19 5:54:08
Message-ID: 059.89c0f342f51fadbf22fa8494bdeb600a () haiku-os ! org
[Download RAW message or body]

--===============6290391261400503975==
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable

#16794: XHCI: Divide error exception in SubmitNormalRequest
-------------------------------+----------------------------
  Reporter:  LSS37040          |      Owner:  waddlesplash
      Type:  bug               |     Status:  new
  Priority:  normal            |  Milestone:  Unscheduled
 Component:  Drivers/USB/XHCI  |    Version:  R1/Development
Resolution:                    |   Keywords:
Blocked By:                    |   Blocking:  16878
  Platform:  x86-64            |
-------------------------------+----------------------------
Comment (by LSS37040):

 Replying to [comment:5 waddlesplash]:
 > I wonder if the problem here is that the xhci_endpoint is actually not
 initialized. Adding checks for that may solve this. However I am not sure
 how we can wind up in a state where the endpoint is not initialized but a
 Pipe exists...

 I'm not an expert, but I do recall seeing some BIOSes/bootloaders don't
 play well with empty card readers before (that I either need to insert a
 card in it, or hide the reader somehow).

 I think the BIOS could interpret empty card readers in all kinds of ways,
 and in some cases would cause certain BIOS/system calls to return invalid
 values which make the caller freaks out.
-- =

Ticket URL: <https://dev.haiku-os.org/ticket/16794#comment:7>
Haiku <https://dev.haiku-os.org>
The Haiku operating system.
--===============6290391261400503975==--

[prev in list] [next in list] [prev in thread] [next in thread]