Skip to content

[bluetooth][PTS] Getting Connection failed to be established ocasionally #10146

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
MariuszSkamra opened this issue Sep 21, 2018 · 6 comments
Closed
Assignees
Labels
area: Bluetooth bug The issue is a bug, or the PR is fixing a bug priority: medium Medium impact/importance bug

Comments

@MariuszSkamra
Copy link
Collaborator

MariuszSkamra commented Sep 21, 2018

Trying to connect to PTS, Im getting connection failed to be established occasionally.

Reproducible 2/10
TestCase: GATT/CL/GAD/BV-03-C
IUT: Zephyr, nRF52840PDK

Reproduce with bt shell:

connect 00:1b:dc:08:e6:83 (public)
gatt-discover-include
disconnect

Procedure repeats few times

@MariuszSkamra
Copy link
Collaborator Author

@MaureenHelm MaureenHelm added bug The issue is a bug, or the PR is fixing a bug priority: medium Medium impact/importance bug area: Bluetooth labels Sep 25, 2018
@joerchan
Copy link
Collaborator

joerchan commented Oct 3, 2018

The sniffer trace that has been uploaded does not show a connection that disconnected with that error code, but there is a hole in the sniffer trace , so it might be that the sniffer missed it. Can we get a new sniffer trace?

Also could you provide some more information to help me reproduce the issue?

  • Which device is central.
  • which device is peripheral.
  • a specific commit
  • Any special configuration

So far I haven't been able to reproduce the frequency of connection failed that you describe. But in a noisy environment this behaviour is expected. A CRC error on the connect request could be the cause.

@galak
Copy link
Collaborator

galak commented Dec 13, 2018

@MariuszSkamra Are you still seeing this with recent runs of PTS?

@nashif
Copy link
Member

nashif commented Jan 31, 2019

@cvinayak what is the status of this issue?

@cvinayak
Copy link
Collaborator

we should close this, as there has been no follow up on reproducing it since Sept 21 and I have run conformance tests as part of v1.14.0-rc1 testing that passes all conformance tests.

@carlescufi
Copy link
Member

Closing as non-applicable anymore.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: Bluetooth bug The issue is a bug, or the PR is fixing a bug priority: medium Medium impact/importance bug
Projects
None yet
Development

No branches or pull requests

7 participants