I had like 40 reboots the two days I had mine. Have sent it for service for surley it must be hardware errors bacuse not even Nokia could release a phone that full of bugs
29-10-2011 10:55 - edited 29-10-2011 10:58
One reboot a day isn't a good enough reason to give my beauty out of my hands - it's just annoying. I want fully stable and reliable phone. Besides, shop is out of stock and I'm not interested in getting my money back. Now I tailed all syslog messages into MyDocs and I'm waiting for reboot to come. I'm curious what is the reason of this. I remember n900 situation time ago so I wonder how it's related.
@MattiasA: Next update of n9 has 3k+ fixes so I belive it has many software/driver issues.
PS: LOL even this forum has bugs, I had to post reply again "An Unexpected Error has occurred. Sorry, your request failed. A notification has been sent to the development team for investigation. Exception ID: 59F266E0 Please click the Back button on your browser. Return to my original page"
01-11-2011 16:55 - edited 01-11-2011 17:21
I'm not the only one with this problem ( http://talk.maemo.org/showthread.php?t=79576). Back in the day (n900 -> https://bugs.maemo.org/show_bug.cgi?id=6334 ) we had few helpful people from nokia to help resolve similar issue.
But what can we do now? I'm not sure if I want to wait for next sofware update. That pesky watchdog kicking reboot for no reason is getting on my nerves. I can't event see dmesg because nokia decided to 'protect' system from user...
First 3 reboots made my n9 completely dead with 'Clear Black Screen Of Death [tm]'. I had to flash my n9 to recover from this state. I don't think many users have enough knowledge for this.
ah, just saw somewhere (I guess someone with n950) about dmesg and I didn't even check...ah, my bad.
Anyway, to get xterm you don't have to enable devel mode, few apps from ovi pulls xterm as dependency (nano,irssi,etc..)
If you find anything usefull about it, don't hestitate to share. Thanks.
As for me I think my n9 counts every reboot because I get no more no less 3 reboots a day, kinda odd.
I've had an n9 64gb for all of a day and have experienced about 15 spontaneous reboots in that time for a wide range of tasks like app launching, view switching, list scrolling etc.
Love the hardware, love the software potential but the list of people filling up other forums with the same complaint makes me worry that this is not something that can be fixed solely through an update.
03-11-2011 1:31 - edited 03-11-2011 1:34
I'm doing more digging..
Unlike Maemo 5, Harmattan is quite neatly tied down.. Lots of really useful stuff to do debugging is prohibited.. Darn it..
However,what I've found so far:
[ 4195.550537] HW Recovery dump generated at 1320282493052795
[ 4195.552551] Dumping 2 render state buffers
[ 4198.260192] SGX Hardware Recovery triggered (from SGXOSTimer)
[ 4198.260284] PID = 2400, process name = grob
[ 4198.260284] EVENT_STATUS = 0x20000000
[ 4198.260284] EVENT_STATUS2 = 0x00000008
[ 4198.260284] BIF_CTRL = 0x00000000
[ 4198.260314] BIF_INT_STAT = 0x00004004
[ 4198.260314] BIF_MEM_REQ_STAT = 0x00000000
[ 4198.260314] BIF_FAULT = 0x00B44000
[ 4198.260314] CLKGATECTL = 0x00222220
[ 4198.260314] Last SGX microkernel status code: 0xad000038
each of the app crashes I've come across (crashes, not reboots) seems to be accompanied with somethign like this
This is a kernel error log, it is caused by, what seems to be, the graphics system.
Like Maemo, the N9 uses Xorg as the graphics software. This software talks to a graphics driver in the kernel that talks to the "graphics card" Problem with buggy hardware or buggy drivers (Especially graphics drivers) is that they ruin things for everyone!
Now, the question is, why are so many phones apparently unaffected? this can be very very slight manufacturing differences in the hardware.. It might be some tiny part of the CPU takes slightly longer to do something, or it might be slightly quicker and the driver assumes that all the hardware is identicle..
Now, it could be that this flaw can be worked around in software, Xorg or Kernel driver and it will increase the stability for everyone.. This would be good, but it means waiting for PR1.1 (assuming they've already got a fix planned)
The problem, however, could actually be faulty hardware.. like a failure in the graphics system memory that causes the gpu to behave unexpectidy, in a way the OS/kernel does not anticipate and cannot correct.. This would be defective hardware..
Problem is, there seem to be too many users with flawed devices.. So, Fingers crossed it'll be something that can be addresses in the driver.. More digging to do, I'm trying to find out what actually happens when an app dies.. Its proving to be slightly harder than anticipated..
The log reports that "grob" failed.. I believe grob is the web browser
The development tool sets that you can install from Settings -> Security -> Development mode are pretty awesome! Its really nice having some space and tools to poke around!
Is it just (some of) the N9 64mb version that is affected by this problems, i havn't seen anyone write that they have a 16mb version with (these) issues? If so, is there any other diffrerences between they versions aside from the memorychip?
I had a Swedish Black 64 GB and not an Austrian and had the exact same problem - random reboots all the time and had to reflash within our hour after I got it. But it didnt help, just kept on crashing and rebooting. Now I am waiting for getting my money back, this pos phone was for sure my last Nokia. Nokia once made great phones, N95, E71 and E90 and N8 but now they are dead. Really enjoyed the N9 the hours I used it but fed up with Nokia that they can release a device working this badly - it aint even beta quality on the software