Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
Help debug dmesg
View unanswered posts
View posts from last 24 hours

 
Reply to topic    Gentoo Forums Forum Index Gentoo on PPC
View previous topic :: View next topic  
Author Message
feliperal
Apprentice
Apprentice


Joined: 09 Mar 2003
Posts: 168

PostPosted: Sun Jan 18, 2004 2:39 am    Post subject: Help debug dmesg Reply with quote

I am trying to resolve why am I getting this ouput overflowing my dmesg and logs:
Code:

IN from bad port 64 at c0240d20
IN from bad port 64 at c0240d20
IN from bad port 64 at c0240d20
IN from bad port 64 at c0240d20
IN from bad port 64 at c0240d20
IN from bad port 64 at c0240d20
IN from bad port 64 at c0240d20
IN from bad port 64 at c0240d20
IN from bad port 64 at c0240d20
IN from bad port 64 at c0240d20
IN from bad port 64 at c0240d20
IN from bad port 64 at c0240d20
IN from bad port 64 at c0240d20
IN from bad port 64 at c0240d20
IN from bad port 64 at c0240d20
IN from bad port 64 at c0240d20
IN from bad port 64 at c0240d20
IN from bad port 64 at c0240d20
IN from bad port 64 at c0240d20
IN from bad port 64 at c0240d20
IN from bad port 64 at c0240d20
IN from bad port 64 at c0240d20
IN from bad port 64 at c0240d20
IN from bad port 64 at c0240d20
IN from bad port 64 at c0240d20
IN from bad port 64 at c0240d20
IN from bad port 64 at c0240d20
IN from bad port 64 at c0240d20
IN from bad port 64 at c0240d20
IN from bad port 64 at c0240d20
IN from bad port 64 at c0240d20
IN from bad port 64 at c0240d20
IN from bad port 64 at c0240d20
IN from bad port 64 at c0240d20
IN from bad port 64 at c0240d20
IN from bad port 64 at c0240d20
IN from bad port 64 at c0240d20
IN from bad port 64 at c0240d20
IN from bad port 64 at c0240d20
IN from bad port 64 at c0240d20
IN from bad port 64 at c0240d20
IN from bad port 64 at c0240d20
IN from bad port 64 at c0240d20
IN from bad port 64 at c0240d20
IN from bad port 64 at c0240d20
IN from bad port 64 at c0240d20
IN from bad port 64 at c0240d20
IN from bad port 64 at c0240d20
IN from bad port 64 at c0240d20
IN from bad port 64 at c0240d20
IN from bad port 64 at c0240d20
IN from bad port 64 at c0240d20
IN from bad port 64 at c0240d20
IN from bad port 64 at c0240d20
IN from bad port 64 at c0240d20
IN from bad port 64 at c0240d20
IN from bad port 64 at c0240d20
IN from bad port 64 at c0240d20
IN from bad port 64 at c0240d20
IN from bad port 64 at c0240d20
IN from bad port 64 at c0240d20
IN from bad port 64 at c0240d20
IN from bad port 64 at c0240d20
IN from bad port 64 at c0240d20
IN from bad port 64 at c0240d20
IN from bad port 64 at c0240d20
IN from bad port 64 at c0240d20
IN from bad port 64 at c0240d20
IN from bad port 64 at c0240d20
IN from bad port 64 at c0240d20
IN from bad port 64 at c0240d20
IN from bad port 64 at c0240d20
IN from bad port 64 at c0240d20
IN from bad port 64 at c0240d20
IN from bad port 64 at c0240d20
IN from bad port 64 at c0240d20
IN from bad port 64 at c0240d20
IN from bad port 64 at c0240d20
IN from bad port 64 at c0240d20
IN from bad port 64 at c0240d20
IN from bad port 64 at c0240d20
IN from bad port 64 at c0240d20
IN from bad port 64 at c0240d20
IN from bad port 64 at c0240d20
IN from bad port 64 at c0240d20
IN from bad port 64 at c0240d20
IN from bad port 64 at c0240d20
IN from bad port 64 at c0240d20
IN from bad port 64 at c0240d20
IN from bad port 64 at c0240d20
IN from bad port 64 at c0240d20
IN from bad port 64 at c0240d20
IN from bad port 64 at c0240d20
IN from bad port 64 at c0240d20
IN from bad port 64 at c0240d20
IN from bad port 64 at c0240d20
IN from bad port 64 at c0240d20
IN from bad port 64 at c0240d20
IN from bad port 64 at c0240d20
IN from bad port 64 at c0240d20
IN from bad port 64 at c0240d20
IN from bad port 64 at c0240d20
IN from bad port 64 at c0240d20
IN from bad port 64 at c0240d20
IN from bad port 64 at c0240d20
IN from bad port 64 at c0240d20
IN from bad port 64 at c0240d20
IN from bad port 64 at c0240d20
IN from bad port 64 at c0240d20
IN from bad port 64 at c0240d20
IN from bad port 64 at c0240d20
IN from bad port 64 at c0240d20
IN from bad port 64 at c0240d20
IN from bad port 64 at c0240d20
IN from bad port 64 at c0240d20
IN from bad port 64 at c0240d20
IN from bad port 64 at c0240d20
IN from bad port 64 at c0240d20
IN from bad port 64 at c0240d20
IN from bad port 64 at c0240d20
IN from bad port 64 at c0240d20
IN from bad port 64 at c0240d20
IN from bad port 64 at c0240d20
IN from bad port 64 at c0240d20
IN from bad port 64 at c0240d20
IN from bad port 64 at c0240d20
IN from bad port 64 at c0240d20
IN from bad port 64 at c0240d20
IN from bad port 64 at c0240d20
IN from bad port 64 at c0240d20
IN from bad port 64 at c0240d20
IN from bad port 64 at c0240d20
IN from bad port 64 at c0240d20
IN from bad port 64 at c0240d20
IN from bad port 64 at c0240d20
IN from bad port 64 at c0240d20
IN from bad port 64 at c0240d20
IN from bad port 64 at c0240d20
IN from bad port 64 at c0240d20
IN from bad port 64 at c0240d20
IN from bad port 64 at c0240d20
IN from bad port 64 at c0240d20
IN from bad port 64 at c0240d20
IN from bad port 64 at c0240d20
IN from bad port 64 at c0240d20
IN from bad port 64 at c0240d20
IN from bad port 64 at c0240d20
IN from bad port 64 at c0240d20
IN from bad port 64 at c0240d20
IN from bad port 64 at c0240d20
IN from bad port 64 at c0240d20
IN from bad port 64 at c0240d20
IN from bad port 64 at c0240d20
IN from bad port 64 at c0240d20
IN from bad port 64 at c0240d20
IN from bad port 64 at c0240d20
IN from bad port 64 at c0240d20
IN from bad port 64 at c0240d20
IN from bad port 64 at c0240d20
IN from bad port 64 at c0240d20
IN from bad port 64 at c0240d20
IN from bad port 64 at c0240d20
IN from bad port 64 at c0240d20
IN from bad port 64 at c0240d20
IN from bad port 64 at c0240d20
IN from bad port 64 at c0240d20
IN from bad port 64 at c0240d20
IN from bad port 64 at c0240d20
IN from bad port 64 at c0240d20
IN from bad port 64 at c0240d20
IN from bad port 64 at c0240d20
IN from bad port 64 at c0240d20
IN from bad port 64 at c0240d20
IN from bad port 64 at c0240d20
IN from bad port 64 at c0240d20



Back to top
View user's profile Send private message
mikulus
Tux's lil' helper
Tux's lil' helper


Joined: 03 Jun 2002
Posts: 77

PostPosted: Mon Jan 19, 2004 6:05 am    Post subject: Reply with quote

The message
Code:
IN from bad port 64 at c0240d20


comes from linux/arch/ppc/kernel/traps.c. Basiclly, the location at 0x64 cannot be read. Try upgrading to later PPC kernel or fixing your hw/kernel parameters.
_________________
"Two things are infinite - the universe and human stupidity. And I am not sure about the universe."
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Gentoo on PPC All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum