6710 Navigator random lockups during navigation

While extensively using the GPS functionality of my new 6710 for the first time this week, I've come across a problem of random lockups during navigation.
There seems to be no obvious pattern to the phenomenon, sometimes it occurs just a few seconds after the route has been calculated and navigation has startet, at other times it occurs after already having navigated a large part of the route.
My subjective impression is, lockups are more likely to occur whenever the device tries to calculate an alternate route (when the user instructed it to do so by selecting the respective option) due to traffic information it received.
After a lockup, the navigation program cannot be closed the usual way (by selecting 'Exit'), but only by pressing the red 'hang up' key; and even then, it stays in memory (it's still in the 'open programs' list). Sometimes, the phone altogether is locked up, only way to "re-animate" it then is to switch it off and on again.
Anyone experienced a similar issue, and/or has an idea what might be the problem here, and how to solve it?

Hello,
When i asked nokia about this problem their reply was: "we don't offer support for third party apps, try using ovi". It didn't matter for them that a NAVIGATOR phone does not support a navigation software, considering that Ovi Maps does not know the street i'm living on, neither 90% of my country.So i can't use Ovi, because it will not take me anywhere.
It is a surprise for me that they even want money for Ovi considering the above.
F'more i tried the new Garmin software version (5.00.60) , but i obtained the same result, even though hanging lessens a little bit.
I even had Garmin on my E50, E51 and N73 but did not had this problem.
I think a new firmware will fix this issue.
Regards,
Cristi.

Similar Messages

Nokia 6710 navigator

This is driving me mad!!!!!!!!!!!!!!!!!! How do you delete the map history on the Nokia 6710 navigator. I have played around with the phone putting in all different locations to try it out, but now want to get rid of all the saved locations. Have even restored factory settings, but when go to maps all the old locations are still there. You cannot highlight and delete them with the 'c' (cancel key) either!!
Advice please???

Have even restored factory settings, but when go to maps all the old locations are still there.
That would be as you have not deleted anything from the maps .
Previous posts that may help .
Favorites can be deleted on maps.ovi.com on your PC. If you are synced, the your favorites would appear there. Once you delete them there and sync again, the favorites on your phone would be deleted as well.
Go to Menu>Apps>Location>Landmarks. Delete them from there.
That fails contact the maps team at Nokia .
jje

6710 navigator daily event setup

Hello, I have a 6710 Navigator. How can I setup a daily event so that the phone reminds me about that on a specific time daily ?
Thanks in advance !

You can set the events in the Calendar..
Refer Pg. 10 of..
http://nds1.nokia.com/phones/files/guides/Nokia_6710_Navigator_UG_en.pdf
--------------------------------------------------------------------------------------------------------------------------------------------------------------If you find this helpful, pl. hit the White Star in Green Box...

6710 Navigator

Hi all.
Its probably been asked but can anyone tell me when the 6710 navigator is due to arrive in the UK
Thanks
Solved!
Go to Solution.

No official date has been announced for this model yet other than "Q3" which is July to September.
Some sites have said late July/Early August.
Online retailers are most likely to get it first so keep your eye on those.

Nokia 6710 navigator podłoczenie do drukarki hp de...

zapora ogniowa Mozé mi ktos powiedzieć JAK nokie 6710 navigator podłoczyć do Drukarki HP DeskJet F500 prosze podpwiedz

jak podłoczyć nokie navigator 6710 do drukarki hp deskjt f500 muj imel [email protected] prosze o pomodz

Nokia 6710 Navigator keypad problems

Hi, I have a relatively new 6710 Navigator but the keypad is starting to do strange things. Occassionaly it wont recognise that I have pressed a button despite having pressed it several times and now it starts another function when I press a different button. E.g Maps startup when I press call cancel button. are there any reset functions/instructions to reset phone?

Here I was thinking I was the only one having these problems.
My phone is being replaced for the 4th time. I have rung Nokia helpline (waste of time) now waiting on head office to return my call about a refund. I've had it for 6 months and it only works the day I get it and slowly deteriorates from there on until I've had enough again!
The zooming, the messaging, maps starting up, keyboard freezing and the loud speaker... loud is not the word I'd use. I can barely hear it and have resorted to holding the device while driving which I'm against.
Has anyone had their phone replaced with a different model by Nokia? They customer centre told me they don't do it,,,, ever!

AVOID the Nokia 6710 Navigator.

ALL my problems began on wed, the 6710 arrived, put in my sim card all was well, then it goes down hill all the way down
into a deep ditch then into lots of poo.
After several hours of use, say 3 the zoom bar was making it zoom in and out on webpages and nokia maps, no option to turn off the zoom bar so i ring up my service provider and tell them they tell me to take it to the 3 shop and show them the fault ok no problem...
I get into the shop and show them the fault...
Zooms in and out.
Now it's triggering the centre button for the menu too, so now it selects things you don't even select, how nice.
30 minutes later I have a swapped phone, while in the shop i put the sim card in and I run Nokia Maps 3.0 the screen
loads up and all of a sudden i hear a loud static type white noise coming from it next thing i know the phone switches
off, ok possibly a bad bug (no GPS reception to get a lock it just got confused), wifi everything else looked ok.
still, best run the GPS app to find your location, again it crashes it restarts on it's own.
Anyway I used the other features seemed ok no crashing so i left the shop, I get back home 20 minute drive, I open up the GPS locator app again, surprise surprise it crashes yet again
So I tried it once more, what else i have i got to lose, next thing i know the PHONE REPEATEDLY started switching itself off and then on, i would see the nokia logo intro screen start up, then it would die and turn off, I sat and watched it switch itself on and off like this for about 2 minutes ok let's pull the battery out and wait a few minutes I put the battery back in and went to switch it on.
???? switch on.... pressing the power button, not switching on, this has died, completely and utterly died (yes phone charger is plugged in battery half power before it died)
ok fine... I head back to the nokia store.
Look see, this is even worse it's now dead, ok...
THIRD phone taken out of yet a new box (i'm on my THIRD 6710 in only 48 hours) PLEASE let this work, ok zoom bar works, gps works, no crashes ok good fine THANK YOU!!!!
oh um, hmmm I run nokia Maps i try to get it to navigate, oh Nokia has a lifetime licence or 2 years at least for the nokia 6710, but mine is telling me i have to pay for a perscription um ok what?....
fast forward 3 hours of talking to Nokia, my service provider, tech support, you name it, i spoke to them, EVENTUALLYafter no less than 4 phone calls to the nokia centre first time they put me on hold, second time they said they would call me back (still waiting for that phone call) I tried once again but i got no answer..
Finally a 4th (nice woman) i explained the problem and explained that this is the 3rd phone, but all the licences have already expired this is not what i bought... ok to try and help I recalled some info which i read months ago about nokia taking sim info and matching it against the IMEI
after 1 1/2 hours on the phone she tells me i'm in 'luck' she then had to track down someone with level 3 nokia privlidge or something like that as she did not have the clearence to do this job, so 30 minutes later she tracks down someone in the know and in clearance to do this 5 minute job...
Finally after 2 hours I managed to supply her with enough info to pass on to change my licence info to match the 3rd phone...
Yay
3 phones, $20+ of calls
3 hours of talking
No licence
over 4 hours of "resetting, trying. deleting, installing"
Vast amounts of time and effort wasted trying to get the 6710 Navigator working.
Something which should have taken only an hour turned into an absolute nightmare.
So if the first 2 were faulty, this would indicate that ON AVERAGE only 1 in every 3
nokia 6710's actually WORK, and there's no evidence to suggest that even this 3rd
one will be working in 6 months time either due to the zoom bar's really bad design
or design flaw.
So is it a nice phone?.... yes it's feature rich and very powerful providing it works.
1/10 for build quality, stay away from it, I now have to live with it and hope nothing goes wrong.

I was just thinking, if it is a cable that comes lose which connects the slider bar and that's the root issue because it's poorly connected to begin with....How many people when calibrating the compass (like i did to begin with) would overly shake the phone, up down, around, side back to front.... each time it's not going to help a poorly connected cable..
I guess the answer to stop this slider/scroll bar issue is a simple one, don't shake it, don't move it, just leave it on the table at home ) )

Random kernel lockups during boot

I'm not sure since when exactly but my computer has had lockups during bootup
before kernel passes control to init. I think with 2.6.30 the problem was so
bad that the computer did not boot at all with having acpi enabled.
Now I can boot computer with ACPI, but I get random lockups at the same places
where I got the lockups with earlier kernels. This is annoying as I can't trust
the computer to bootup without me being next to it, and I think it has other
consequences as well (http://bugzilla.kernel.org/show_bug.cgi?id=15210).
But as the errors do not exhibit themselves all the time, I'm having trouble
debugging it. I enabled kernel commandline 'debug' and am now waiting to see
the problem reappear so that maybe I can get more information. Are there some
more arguments that would make the debugging easier, and maybe sending
bugreport to http://bugzilla.kernel.org worthwile.
Edit: The last visible lines are a few "Found enabled HT MSI Mapping"
Last edited by Masse (2010-02-05 07:06:19)

I've temporarily fixed the problem by doing the following:
removed cryptsetup (1.3.1-2)
removed lvm2 (2.02.88-1)
removed mdadm (3.2.2-4)
removed linux (3.0.6-2)
upgraded mkinitcpio-busybox (1.18.5-1 -> 1.18.2-1)
installed gen-init-cpio (2.6.36-1)
upgraded udev (173-3 -> 167-2)
upgraded mkinitcpio (0.7.3-1 -> 0.6.11-1)
installed kernel26 (2.6.38.5-1)
upgraded nvidia-173xx-utils (173.14.31-1 -> 173.14.30-1)
upgraded nvidia-173xx (173.14.31-2 -> 173.14.30-1)
upgraded initscripts (2011.07.3-1 -> 2011.04.1-2)
upgraded net-tools (1.60.20110819cvs-1 -> 1.60-18)
I also restored my old /etc/mkinitcpio.conf, /etc/inittab and /etc/rc.conf.
I'm still interested in a solution to the original problem. Is it a problem with my configuration, the new kernel, the udev version or something else?
The difference in inittab is just a -s option and the mkinitcpio.conf files are the same except for some comments. rc.conf has the biggest changes and is now (removed comments):
LOCALE="en_US.UTF-8"
DAEMON_LOCALE="no"
HARDWARECLOCK="UTC"
TIMEZONE="Europe/Stockholm"
KEYMAP="se-lat6"
CONSOLEFONT=
CONSOLEMAP=
USECOLOR="yes"
VERBOSE="3"
MOD_AUTOLOAD="yes"
MODULES=(!usblp !pcspkr)
UDEV_TIMEOUT=30
USEDMRAID="no"
USEBTRFS="no"
USELVM="no"
HOSTNAME="archon"
eth0="dhcp"
INTERFACES=(eth0)
ROUTES=(!gateway)
NETWORK_PERSIST="no"
DAEMONS=(syslog-ng @network dbus preload !netfs !wicd @crond @cups @sshd @startntpd)
Last edited by Mogger (2011-10-11 14:04:20)

Random pauses during songs.

I've had my nano since november 2005, about a month ago while I was listening to it my ipod suddenly paused for no reason(I dont recall jerking on the headphone wire or jack at all).
Ever since then the ipod keeps randomly pausing during songs, the odd thing is it doesn't only do it when I wiggle the headphone jack, it does it sometimes even when its sitting flat on my sofa without anything at all touching it and alot of slack in the headphone wire. Also the ipod does it even when the hold button is on as well so it isnt the play/pause button.
I tried sending it to apple but under the reasons for replacing the nano there was no option for damaged headphone jacks so I chose "damaged dock port" since it is very close to the headphone jack, and I also wrote in the description that the headphone jack is broken. Apple sent back the same nano saying they couldn't find any problem with it so I'm out of ideas.
Oh and yes I've tried resetting it and everything.

hmm another question, when i try to open another service request to send my ipod in again, it says it cant because my ipod already has a service request open, even though ive already gotten my ipod back since last week when i sent it in...any idea how long it will take till i can send it in again?

HT4993 iPhone makes random Keytone during call ~ Please help

I thought it was just my phone, but I decided to look up this random keytone during phone calls on the internet and found this is a common problem with iPhones. I have a iPhone 5s and this has been happening since I purchased it in Nov 13.
I cannot believe there is not a fix for this very annoying problem.
Please let me know if there is a solution I just have not come across yet.
Thank you.

The keytone noise is random during phone calls. My cell carrier is Sprint and my internet provider is AT&T. However, after reading about 100 post today on differt blogs it does not seem to be an issue with a carrier or a internet provider.
What I have been reading is that it happen after doing updates on the iPhones. Mine happen to start as soon as I opened and used my new iPhone 5s. It is so annoying and I have read enough about the issue today to know that there are 100s out there if not 1000s with the same issue. Different carriers, different internet providers, but all the same type of phones iPhones 4s and 5s after doing updates.
Since it is a known problem I was hoping someone at Apple would be able to tell me if it can't be fixed that at least they are working on a fix.

My MacBook Pro randomly froze during a sync to my iPhone and started making a scratching noise by the power button. I shut it off then turned it back on and it won't take me to the desk tops it will just flash a folder with a question mark in it. What do

My MacBook Pro randomly froze during a sync to my iPhone and started making a scratching noise by the power button. I shut it off then turned it back on and it won't take me to the desk tops it will just flash a folder with a question mark in it. What do I do?

You have a HDD problem (hopefully you have a backup). Start with the information on this support article:
https://support.apple.com/kb/TS1440
Ciao.

Bad keyboard causing random lockups and not allowing booting up?

Will a bad keyboard, or keyboard port, make a computer lockup and keep it from rebooting?
I have a slimline s3200n that has been having random lockups. When I try to reboot it, it gets stuck at the startup screen (the one where you get the F9, F10, etc options). I can hit F9 for hours and the computer does nothing. I have to do another hard shutdown and if I wait for a little bit the computer will start back up again. Will work fine, then randomly lockup and go through the cycle again.
I tried to run the Hardware diagnostic utility but it gave me an error, didnt write down the exact error, but it was a timeout error while gathering hardware information.
I am using the keyboard that came with the computer and I do not have another keyboard to use for a test.

I have this exact same issue, and am wondering what to do. I have a 2.2 GHz Intel Core 2 Duo and am using 10.4.11 as software. I have a Dell monitor. Anyone have any thoughts?

865P NEO random lockups.

Hi Folks,
It's been two days now that I have tried every possible system component stress test, voltage and configuration adjustment and even clean Windows 98SE installation tests in order to eliminate or at least locate the cause of random lockups sometimes in games, sometimes even just at system idle.
My system configuration is:
Enermax 300 Watts PSU
865P NEO (not NEO 2) Bios v1.1
Pentium 2.4B 533Mhz bus (no overclocking done)
ThermalTake Spark 7 Cooler
Two Kingston DDR 333Mhz sticks in Dual Channel mode
ATI Radeon 9700 Pro
Seagate Barracuda 40Gb
Sound Blaster Audigy sound card
Liteon 48x24x48 CDRW
I know these kind of problems are the most difficult to detect, so any idea at this moment is very welcome. All I can say is that all these components were tested also on an ASUS P4S800 without any single issue, what leads me to think of a possible falty motherboard.
Thanks in advance for sharing you experiences.
Gig

Hi NovJoe,
Thanks for you kind response. I discarded in the first place the PSU, as I mention in my message, due to the fact that the same components worked using the same PSU on an ASUS P4S800 flawleslly. Besides, if you calculate the total power consumption of the components I have, taking in account that in some stress tests like (3DMark) not all are involved, I think you'll agree that the PSU it's not an issue.
As a matter a fact, yesterday i finally managed to eradicate those mind buggling random lockups selecting the Performance Mode in the BIOS and setting the CPU voltage to 1.575. As opposite of the Fail Safe Mode, the other one brought much more stability to the system, but watching closely the voltages, I have note an incredible CPU voltage drop to almost 1.44V. I know, you'll say: "I told was the PSU", but I did the same test with the ASUS motheboard and the CPU voltage was steady as a rock. So, I said to myself: "We'll let's pump it up a bit to prevent that low voltage drops. Voila, now the variations go between 1.52 and 1.57. Reslult: NO more lockups.
The only thing that remains unanswered to me is if all 865P NEO have that CPU voltage drop issue. So, I kindly invite anyone who is willing to and have a couple of minutes to take peek into the System Health option in the BIOS and post the CPU minimum and maximum voltage ranges.
Thanks once again for your postings.
Gig

[A64] RS480 random lockups, hard crashes, rebooting, freezing

Now that I've got your attention, specs:
AMD A64 3200+ rev. e (Venice)
MSI RS480, bios ver. 3.4
2x512 Corsair Value Select Dual Channel kit PC3200 CAS2.5
Leadtek PX6600GT Extreme (550/1100 stock)
SB Live! Value
WD 80GB 7200rpm 8mb cache IDE ATA100
Seasonic SS-380 (25a on 12v rails, 380w total)
Pioneer DVR-109
Inwin S500T mATX case
Nexus 92mm CPU fan on Thermalright XP-90 heatsink
I've been experiencing random lockups and restarts in 3d apps & games (Battlefield 2, Warcraft 3, Warhammer 40k: Dawn of War, GTA:SA) since I built this system back in May. I'm so sick of this computer right now that I could happily take a sledge to it and reduce it to rubble.
Symptoms:
1) Random reboots and lockups, *not* due to heat. Heat prior to lockups using Speedfan has the CPU consistently around 50 C and the video card consistently at 40-45 C. Needless to say, these are very cool temps, but an extra case fan was added to make sure that air flow in case was good.
2) Motherboard RMA'd after purchase - simply refused to post.
3) RAM RMA'd after about a month after several dozen memtest86 errors found. New RAM has been tested - each stick individually & together - and no errors after testing each configuration for 12 hours.
4) Video card RMA'd after massive heat spikes (upwards 120 C) detected. New video card arrived yesterday & have had one lockup since, which wasn't unusual with old setup. Problem still remains.
5) Sound card was removed for testing when lockup in #4 above occurred, which leads me to believe that my POS SB Live isn't the problem. Too bad, as it would have been a terrific excuse to upgrade to an Audigy 2 ZS.
6) When video card was removed, system was rock solid, not a single crash. With video card in, crashed all the time prior to RMA, and once in two days after new one received. While the old video card certainly appeared to have problems, I'm hesitant at this point to put all my problems on the video card. Is this an erroneous assumption?
7) At least eight or nine different Forceware versions were used for testing; different driver versions did not prevent crashes.
Now, it hasn't crashed again (which means nothing; it's been a couple of hours) since disabling SATA in bios and downloading & installing AMD driver for processor. Will be moving RAM from slots 1 & 2 to 3 & 4 shortly. Before my sanity is finally and truly lost, is there anything else that anybody can think of to stop these hard locks? I'm off to move the RAM around and do some further testing, but any advice whatsoever would be absolutely terrific. Thanks!
(topic title changed. apparently some people thought I was kidding.)

Quote from: Tiresmoke on 28-July-05, 02:39:59
Well yes it could be the RAM. For what it is worth everyone I have seen with Kingmax RAM seems to be happy and so far as I know it works with all the cores. It is also not very expensive stuff. Hope that helps.
Kingmax, eh? I'll see if I can find any (I'm in Canada). Do you know how good their customer service is?
I think that before I try to pick up some new ram I'll send Corsair an email; according to their site, the VS is supposed to be compatible with the RS480, which is one of the reasons I bought it. Who knows; maybe they'll upgrade the RAM that I've got for cheap. But thanks for the advice!
Quote from: dannol48
FYI...you're not the first to report problems trying an nVidia gForce video card on this motherboard (ATI surroundview enabled Xpress 200 chipset).
If you didn't notice, the Compatibility Report posted for the board ONLY has ATI Radeon cards.
Bloody hell! Why didn't I check that? Well, I gotta think about this some more. Good grief. Thanks for bringing this to my attention!

[SOLVED] Random lockups 3.10.10-1 kernel 64bit

I have for a while random lockups on my system. The whole system halts all i can do is hardreset the system. No keyboard respons at all.
This is Journalctl -r output just before i reset the system. There are over 1000 lines of "kernel: mei_me 0000:00:16.0: reset: wrong host start response"
-- Reboot --
sep 10 12:39:52 asusarch systemd[1]: Started Trigger Flushing of Journal to Persistent Storage.
sep 10 12:39:52 asusarch systemd[1]: systemd-journald.service: main process exited, code=exited, status=1/FAILURE
sep 10 12:39:52 asusarch systemd-journal[1858]: Journal started
sep 10 12:39:52 asusarch systemd-journal[1858]: Allowing system journal files to grow to 8.0M.
sep 10 12:39:52 asusarch systemd[1]: Started Trigger Flushing of Journal to Persistent Storage.
sep 10 12:39:52 asusarch systemd[1]: systemd-journald.service: main process exited, code=exited, status=1/FAILURE
sep 10 12:39:52 asusarch systemd-journal[1854]: Journal started
sep 10 12:39:52 asusarch systemd-journal[1854]: Allowing system journal files to grow to 8.0M.
sep 10 12:39:52 asusarch systemd[1]: Started Trigger Flushing of Journal to Persistent Storage.
sep 10 12:39:52 asusarch systemd[1]: systemd-journald.service: main process exited, code=exited, status=1/FAILURE
sep 10 12:39:52 asusarch systemd-journal[1850]: Journal started
sep 10 12:39:52 asusarch systemd-journal[1850]: Allowing system journal files to grow to 8.0M.
sep 10 12:39:52 asusarch systemd[1]: Started Trigger Flushing of Journal to Persistent Storage.
sep 10 12:39:52 asusarch systemd[1]: systemd-journald.service: main process exited, code=killed, status=10/USR1
sep 10 12:39:52 asusarch systemd[1]: systemd-journald.service: main process exited, code=exited, status=1/FAILURE
sep 10 12:39:52 asusarch systemd-journal[1847]: Journal started
sep 10 12:39:52 asusarch systemd-journal[1847]: Allowing system journal files to grow to 8.0M.
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: reset: wrong host start response
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: unexpected reset: dev_state = RESETTING
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: reset: unexpected enumeration response hbm.
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: unexpected reset: dev_state = RESETTING
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: reset: wrong host start response
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: unexpected reset: dev_state = RESETTING
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: reset: unexpected enumeration response hbm.
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: unexpected reset: dev_state = RESETTING
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: reset: wrong host start response
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: unexpected reset: dev_state = RESETTING
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: reset: unexpected enumeration response hbm.
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: unexpected reset: dev_state = RESETTING
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: reset: wrong host start response
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: unexpected reset: dev_state = RESETTING
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: reset: unexpected enumeration response hbm.
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: unexpected reset: dev_state = RESETTING
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: reset: wrong host start response
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: unexpected reset: dev_state = RESETTING
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: reset: unexpected enumeration response hbm.
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: unexpected reset: dev_state = RESETTING
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: reset: wrong host start response
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: unexpected reset: dev_state = RESETTING
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: reset: unexpected enumeration response hbm.
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: unexpected reset: dev_state = RESETTING
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: reset: wrong host start response
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: unexpected reset: dev_state = RESETTING
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: reset: unexpected enumeration response hbm.
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: unexpected reset: dev_state = RESETTING
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: reset: wrong host start response
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: unexpected reset: dev_state = RESETTING
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: reset: unexpected enumeration response hbm.
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: unexpected reset: dev_state = RESETTING
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: reset: wrong host start response
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: unexpected reset: dev_state = RESETTING
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: reset: unexpected enumeration response hbm.
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: unexpected reset: dev_state = RESETTING
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: reset: wrong host start response
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: unexpected reset: dev_state = RESETTING
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: reset: unexpected enumeration response hbm.
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: unexpected reset: dev_state = RESETTING
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: reset: wrong host start response
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: unexpected reset: dev_state = RESETTING
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: reset: unexpected enumeration response hbm.
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: unexpected reset: dev_state = RESETTING
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: reset: wrong host start response
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: unexpected reset: dev_state = RESETTING
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: reset: unexpected enumeration response hbm.
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: unexpected reset: dev_state = RESETTING
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: reset: wrong host start response
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: unexpected reset: dev_state = RESETTING
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: reset: unexpected enumeration response hbm.
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: unexpected reset: dev_state = RESETTING
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: reset: wrong host start response
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: unexpected reset: dev_state = RESETTING
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: reset: unexpected enumeration response hbm.
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: unexpected reset: dev_state = RESETTING
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: reset: wrong host start response
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: unexpected reset: dev_state = RESETTING
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: reset: unexpected enumeration response hbm.
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: unexpected reset: dev_state = RESETTING
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: reset: wrong host start response
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: unexpected reset: dev_state = RESETTING
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: reset: unexpected enumeration response hbm.
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: unexpected reset: dev_state = RESETTING
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: reset: wrong host start response
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: unexpected reset: dev_state = RESETTING
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: reset: unexpected enumeration response hbm.
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: unexpected reset: dev_state = RESETTING
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: reset: wrong host start response
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: unexpected reset: dev_state = RESETTING
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: reset: unexpected enumeration response hbm.
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: unexpected reset: dev_state = RESETTING
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: reset: wrong host start response
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: unexpected reset: dev_state = RESETTING
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: reset: unexpected enumeration response hbm.
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: unexpected reset: dev_state = RESETTING
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: reset: wrong host start response
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: unexpected reset: dev_state = RESETTING
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: reset: unexpected enumeration response hbm.
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: unexpected reset: dev_state = RESETTING
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: reset: wrong host start response
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: unexpected reset: dev_state = RESETTING
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: reset: unexpected enumeration response hbm.
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: unexpected reset: dev_state = RESETTING
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: reset: wrong host start response
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: unexpected reset: dev_state = RESETTING
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: reset: unexpected enumeration response hbm.
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: unexpected reset: dev_state = RESETTING
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: reset: wrong host start response
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: unexpected reset: dev_state = RESETTING
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: reset: unexpected enumeration response hbm.
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: unexpected reset: dev_state = RESETTING
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: reset: wrong host start response
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: unexpected reset: dev_state = RESETTING
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: reset: unexpected enumeration response hbm.
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: unexpected reset: dev_state = RESETTING
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: reset: wrong host start response
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: unexpected reset: dev_state = RESETTING
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: reset: unexpected enumeration response hbm.
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: unexpected reset: dev_state = RESETTING
Anyone that has an idea what i can do to track down the problem.
Last edited by cecar (2013-09-11 09:22:11)

Blacklist/unload the mei_me module. This may have negative consequences on suspending (though I have noticed no difference on my Core2Duo machine).
When you system locks up, does it really lock up? That is, can you try enabling the Magic SysRq key and then try to use that the next time this happens? I suspect that your userspace might have frozen, but the kernel should still be alive and functioning (otherwise you would typically end up with a kernel panic).
In any case, I don't think that the mei_me thing would cause a total lockup of your machine. Besides the journal being spammed like crazy with those messages, I didn't notice any difference in the functionality of the machine.
Edit: I think that in cases such as this, the simplest thing you can do is change kernels and see if the problem persists. As it is, you have provided no real indication that the issue is even related to the kernel upgrade/version. So downgrade just the kernel and see if the problem persists (or install the [testing] kernel).
Last edited by WonderWoofy (2013-09-10 17:40:13)

6710 Navigator random lockups during navigation

Similar Messages

Maybe you are looking for