On Fri, Aug 5, 2016 at 11:15 AM, Daniel Drake wrote:
> Hi Alexander,
>
> Reviving an old topic here...
>
> We are seeing this "problem" on an increasing number of units from the
> vendor, and searching around it can also be seen on Dell and HP
> products. Always with the same
On Fri, Aug 5, 2016 at 11:15 AM, Daniel Drake wrote:
> Hi Alexander,
>
> Reviving an old topic here...
>
> We are seeing this "problem" on an increasing number of units from the
> vendor, and searching around it can also be seen on Dell and HP
> products. Always with the same Realtek b723 wifi
On Fri, Aug 05, 2016 at 12:15:53PM -0600, Daniel Drake wrote:
> Hi Alexander,
>
> Reviving an old topic here...
>
> We are seeing this "problem" on an increasing number of units from the
> vendor, and searching around it can also be seen on Dell and HP
> products. Always with the same Realtek
On Fri, Aug 05, 2016 at 12:15:53PM -0600, Daniel Drake wrote:
> Hi Alexander,
>
> Reviving an old topic here...
>
> We are seeing this "problem" on an increasing number of units from the
> vendor, and searching around it can also be seen on Dell and HP
> products. Always with the same Realtek
Hi Alexander,
Reviving an old topic here...
We are seeing this "problem" on an increasing number of units from the
vendor, and searching around it can also be seen on Dell and HP
products. Always with the same Realtek b723 wifi device. e.g.
Hi Alexander,
Reviving an old topic here...
We are seeing this "problem" on an increasing number of units from the
vendor, and searching around it can also be seen on Dell and HP
products. Always with the same Realtek b723 wifi device. e.g.
On 09/03/2015 06:32 AM, Daniel Drake wrote:
On Wed, Sep 2, 2015 at 7:57 PM, Alexander Duyck
wrote:
Since it is correctable errors it is likely some sort of signalling issue.
Could we get the output of something like an lspci -vt? Then you would be
able to tell what the device is on the other
On Wed, Sep 2, 2015 at 7:57 PM, Alexander Duyck
wrote:
> Since it is correctable errors it is likely some sort of signalling issue.
> Could we get the output of something like an lspci -vt? Then you would be
> able to tell what the device is on the other side of the link from 00:1c.5
> and then
On 09/03/2015 06:32 AM, Daniel Drake wrote:
On Wed, Sep 2, 2015 at 7:57 PM, Alexander Duyck
wrote:
Since it is correctable errors it is likely some sort of signalling issue.
Could we get the output of something like an lspci -vt? Then you would be
able to tell what
On Wed, Sep 2, 2015 at 7:57 PM, Alexander Duyck
wrote:
> Since it is correctable errors it is likely some sort of signalling issue.
> Could we get the output of something like an lspci -vt? Then you would be
> able to tell what the device is on the other side of the
On 09/02/2015 03:53 PM, Bjorn Helgaas wrote:
On Wed, Sep 2, 2015 at 5:01 PM, Daniel Drake wrote:
Hi,
Working with a sample for a new laptop based on Intel Skylake, the
kernel logs are full of these messages:
pcieport :00:1c.5: AER: Corrected error received: id=00e5
pcieport
On Wed, Sep 2, 2015 at 5:01 PM, Daniel Drake wrote:
> Hi,
>
> Working with a sample for a new laptop based on Intel Skylake, the
> kernel logs are full of these messages:
>
> pcieport :00:1c.5: AER: Corrected error received: id=00e5
> pcieport :00:1c.5: PCIe Bus Error:
Hi,
Working with a sample for a new laptop based on Intel Skylake, the
kernel logs are full of these messages:
pcieport :00:1c.5: AER: Corrected error received: id=00e5
pcieport :00:1c.5: PCIe Bus Error: severity=Corrected,
type=Physical Layer, id=00e5(Receiver ID)
pcieport
On 09/02/2015 03:53 PM, Bjorn Helgaas wrote:
On Wed, Sep 2, 2015 at 5:01 PM, Daniel Drake wrote:
Hi,
Working with a sample for a new laptop based on Intel Skylake, the
kernel logs are full of these messages:
pcieport :00:1c.5: AER: Corrected error received: id=00e5
Hi,
Working with a sample for a new laptop based on Intel Skylake, the
kernel logs are full of these messages:
pcieport :00:1c.5: AER: Corrected error received: id=00e5
pcieport :00:1c.5: PCIe Bus Error: severity=Corrected,
type=Physical Layer, id=00e5(Receiver ID)
pcieport
On Wed, Sep 2, 2015 at 5:01 PM, Daniel Drake wrote:
> Hi,
>
> Working with a sample for a new laptop based on Intel Skylake, the
> kernel logs are full of these messages:
>
> pcieport :00:1c.5: AER: Corrected error received: id=00e5
> pcieport :00:1c.5: PCIe Bus
16 matches
Mail list logo