just to be sure?
Now, in case Mike (or anyone with the same problem) confirms, what
can we do to have it fixed? Thank you.
BR,
--
José Pérez Arauzo
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-curren
ce 16.0 on pci0
usbus0: waiting for BIOS to give up control
xhci0: 32 byte context size.
usbus0 on xhci0
xhci0@pci0:0:16:0: class=0x0c0330 card=0x080d1025 chip=0x78141022
rev=0x01 hdr=0x00
vendor = 'Advanced Micro Devices [AMD]'
class = serial bus
su
Hi Garrett,
On Tue, 30 Sep 2014 09:57:19 -0700, Garrett Cooper wrote
> > On Sep 30, 2014, at 7:44, "Mike." wrote:
> >
> > On 9/29/2014 at 11:04 PM José Pérez Arauzo wrote:
> >
> > |This encoded message has been converted to an attachment.
> > |
&
and might be it'AHCI actually.
Warner Losh (the maintainer) sent at least 3 messages about this, he's
very cooperative I think.
I'll try the no-SMP thing now just to see how it works.
BR,
--
José Pérez Arauzo
___
freebsd-current@free
Hi Mike,
On Mon, 29 Sep 2014 16:03:44 -0400, Mike. wrote
[...]
> So that should put a time bracket on the issue, roughly the first
> half of 2014.
can you boot 271146? Just buildkernel and installkernel. Thank you.
BR,
--
José Pérez
. It might not apply to the specific case where
device probe does not complete, but I'll give it a try. Give me a
day or two.
Thank you!
BR,
--
José Pérez Arauzo
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listi
Hi Benjamin,
On Sun, 28 Sep 2014 15:54:36 -0400 (EDT), Benjamin Kaduk wrote
> On Sun, 28 Sep 2014, José Pérez Arauzo wrote:
>
> > Hello,
> > I am trying to track down a (deadlock?) issue in CURRENT via DDB. The
kernel does
> > not complete hw probes on my Acer V5.
> &g
Hi Garrett,
On Sun, 28 Sep 2014 13:38:24 -0700, Garrett Cooper wrote
> On Sep 28, 2014, at 0:34, José Pérez Arauzo wrote:
>
> > Hello,
> > I am trying to track down a (deadlock?) issue in CURRENT via DDB. The
kernel does
> > not complete hw probes on my Acer V5.
> >
ror 5, Retry was blocked
> ada0 at ata0 bus 0 scbus0 target 0 lun 0
> ada0: ATA-6 device
> ada0: Serial Number MPC412Y4G6J1AE
> ada0: 100.000MB/s transfers (UDMA5, PIO 8192bytes)
> ada0: 76319MB (156301488 512 byte sectors: 16H 63S/T 16383C)
> ada0: Previously was known as ad0
> cd0 at ata1 bus 0 scbus1 target
ave a USB to serial showing up as
/dev/cuaU0, do I need to grab another one and a nullmodem cable or there are
better
alternatives? Thank you.
BR,
--
José Pérez Arauzo
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/lis
at 9:12 AM, Adrian Chadd wrote:
>
> > Hi!
> >
> > 271146 was Warner's AHCI probe/attach changes. Maybe he'll have some ideas.
> > :)
> >
> > Warner?
> >
> >
> > -a
> >
> >
> > On 25 September 2014 08
On Thu, 25 Sep 2014 09:26:56 -0700, David Wolfskill wrote
> On Thu, Sep 25, 2014 at 05:48:13PM +0200, José Pérez Arauzo wrote:
> > Hi,
> > on my Acer Aspire V5, AHCI does not complete device_attach after 271145.
> >
> > Am I the only one experiencing this? Can
Hi,
on my Acer Aspire V5, AHCI does not complete device_attach after 271145.
Am I the only one experiencing this? Can I help fixing it? Thank you.
BR,
--
José Pérez Arauzo
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman
13 matches
Mail list logo
