Ticket #2012 (new defect)

Opened 10 years ago

Last modified 9 months ago

2008 updated and FDOM failure to register to vodafone Australia

Reported by: billk Owned by: zecke
Priority: normal Milestone:
Component: Qtopia Version: GTA02v5
Severity: major Keywords: GSM Register
Cc: Blocked By:
Blocking: Estimated Completion (week):
HasPatchForReview: PatchReviewResult:
Reproducible: always

Description

Raised new bug as this doesnt quite fit the profile of existing bugs
Affects at least two users in Australia on vodafone GSM

The phone fails to register and doesnt retry if qtopia isnt ready. Works fine on 2007.2, fails on ASU/2008.8 updated/FDOM

editing /etc/init.d/Xsession.d/89qtopia to swap the last lines and add a sleep:
_
# Now start Qtopia
/usr/bin/app-restarter "$QTOPIA_MESSAGE" qpe 2>&1 | logger &
sleep 30
echo 1 > /sys/devices/platform/neo1973-pm-gsm.0/power_on

This has proven reliable. I set a PIN during testing, so I have not tested it in pin-less mode which is where I started. It would be better if the phone would try and reregister after an initial failure - but it doesnt seem to.

BillK

Attachments

a (63.2 KB) - added by BillK 10 years ago.
logread A
b (63.3 KB) - added by BillK 10 years ago.
logread B
c (56.1 KB) - added by BillK 10 years ago.
Logread c
list_installed (42.4 KB) - added by BillK 10 years ago.

Change History

comment:1 Changed 10 years ago by zecke

  • Milestone Om2008.8 deleted

I don't understand. Could you provide the output of logread as http://wiki.openmoko.org/wiki/Bug_Filing_Policy to understand what "does not register" actually means?

Do you propose to start Qtopia first and then turn the modem on? I'm a bit confused.

comment:2 Changed 10 years ago by BillK

Yes.
First, Ive just replaced the circa 1999 Vodafone SIM with a new 128K and its vastly improved - enough for me to say its mostly a SIM problem

Yes, it seems to be a timing issue because if I power the GSM, then wait 30 seconds before stating qpe it has a greater success rate (not perfect!)

The new SIM improves it with the standard startup, but sometimes takes a few reboots until the sim dialog pops up.

With no sim PIN set, it has never connected.

Next rebbot that fails I'll geberate a logread.

BillK

comment:3 Changed 10 years ago by zecke

Please read http://wiki.openmoko.org/wiki/Bug_Filing_Policy. You still miss the output of logread and I'm not willing to do handwaving. Please read the http://wiki.openmoko.org/wiki/Bug_Filing_Policy and attach the output of logread once for a successfull and once for a non-successful start.

Changed 10 years ago by BillK

  • Attachment a added

logread A

Changed 10 years ago by BillK

  • Attachment b added

logread B

Changed 10 years ago by BillK

  • Attachment c added

Logread c

comment:4 follow-up: ↓ 6 Changed 10 years ago by BillK

ok, the above logreads (as the previous statement said, I need a failure before its worth generating a logread):

  1. covers a time period when the phone was suspended and an SMS (I sent from another phone) arrived. It woke up with the display not correctly written - no sms. Opening the messages app showed no new messages
  1. covers two more messages that never arrived - probably blocked at vodafone as no indication they arrived
  1. is after a reboot and refusal to register. I didnt wait too long as it never gets out of "user.notice root: AtChat? : F : "AT-Command Interpreter ready"" repetitions.

I restarted X and it brought up the pin dialog (tested, rxed an sms ok)

Note that a kernel error occurs just before most (all?) of the problem spots - "user.err kernel: [ 67.570000] BUG: sleeping function called from invalid context at kernel/mutex.c:207"

comment:5 Changed 10 years ago by zecke

Okay please read http://wiki.openmoko.org/wiki/Bug_Filing_Policy and attach the output of opkg list_installed and we can actually look at the content of this issue.

comment:6 in reply to: ↑ 4 Changed 10 years ago by zecke

Replying to BillK:

ok, the above logreads (as the previous statement said, I need a failure before its worth generating a logread):

Sorry, what does SMS have to do with this bug?

Changed 10 years ago by BillK

comment:7 Changed 10 years ago by BillK

list_installed attached.

The failure to register and SMS failure seem related. After fighting this registration thing since I first got the FR, with only 2007.2 being in any way acceptable (Ive tried ASU/2008.8/2008.9/FDOM/FSO) - it seems that there are timing issues involved (perhaps SIM/GSM provider triggered) that are manifesting themselves in number of ways.

  1. Failure to register - always happens if the kernel error is in the log
  2. SMS seems to be problematic and often (not always) problems co-incide with the same error

It *could* be two separate issues, or part of the same one so its better to have all the information in ways the FR is misbehaving.

Oddly, actual calls seem ok.

BillK

comment:8 Changed 9 months ago by Larcadist

Precio Cialis Farmacia Espana http://cialtobuy.com - cialis buy online Buy Z Pak Online
Cialis Pas De Generique Keflex Pediatric Dosing
Brand Cialis And Levitra <a href=http://cialtobuy.com >cialis</a> Find Cheapeast Isotretinoin

Note: See TracTickets for help on using tickets.