LinuxQuestions.org
Visit the LQ Articles and Editorials section
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Hardware > Linux - Embedded & Single-board computer
User Name
Password
Linux - Embedded & Single-board computer This forum is for the discussion of Linux on both embedded devices and single-board computers (such as the Raspberry Pi, BeagleBoard and PandaBoard). Discussions involving Arduino, plug computers and other micro-controller like devices are also welcome.

Notices

Reply
 
LinkBack Search this Thread
Old 12-05-2007, 08:54 AM   #1
vipulp
LQ Newbie
 
Registered: Jan 2007
Posts: 1

Rep: Reputation: 0
Getting Spurious error on Linux 2.6.20


Hi All,

I am developing the back up and restore utility for the linux kernel version 2.6.20. For this i am intercepting the block write request performed by submit_bio() function present in linux/block/ll_rw_blk.c file. This function calls generic_make_request(). I intercept this function call and replace my own make request at its place and perform back up, later on once back up is over i replaces the original function back.
My problem is while calling submit_bio() function some how i get the following error message.

atkbd.c: Spurious Ack on isa 0060/serio0, some program might be trying to access hardware directly.

With this i have following problems:

->This error has very random behavior, sometimes it appears sometimes it doesn't.

->This error is a scrolling error and i am not able to see previous printk messages for debugging.

->I am not getting the fact that this error comes for the key board
interrupt routine, which doesn't come anywhere in the picture of my utility.

Can you please throw some light on it.
Let me know in case of any further query.
Thank you very much.
 
Old 12-07-2007, 03:19 AM   #2
t0bias
Member
 
Registered: Aug 2005
Distribution: Fedora 13, RHEL 5.3, Ubuntu 10.04, Debian Lenny
Posts: 128

Rep: Reputation: 16
Hi,

you said

Quote:
->This error is a scrolling error and i am not able to see previous printk messages for debugging.
actually, i think this information might be useful. how are you connected to your embedded
device? if via a "classical" com-port, try using minicom and activate the protocolling-function
using the shell parameter (i don't actually remember what the parameter was called like,
but --help will show it). that helped me last time i came across a similar problem.

greetz,

toby
 
Old 12-07-2007, 03:20 AM   #3
t0bias
Member
 
Registered: Aug 2005
Distribution: Fedora 13, RHEL 5.3, Ubuntu 10.04, Debian Lenny
Posts: 128

Rep: Reputation: 16
the minicom-parameter is
Code:
minicom -C [FILENAME]
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Trackbacks are Off
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Spurious Interrupt eglow Linux - Software 8 07-19-2006 08:04 PM
Spurious interrupt Dasc Linux - Hardware 2 07-26-2004 09:57 AM
spurious 8529A interupt 7??????????? d4harvey Red Hat 3 03-24-2004 07:28 PM
spurious interrupt IRQ15 Mathews Linux - Newbie 0 08-29-2003 10:03 PM


All times are GMT -5. The time now is 02:08 PM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration