Accessing hardware

I am trying to access the input stream coming from a
video card and either save it as a file or place it in
an array. I am not sure if I need a pointer to the
device (if I do I dont know where to find it) or if I
need to write a driver (again not sure how to do
this).What you're trying to do is not an easy task.
Maybe you should try one of these products
http://www.jungo.com/windriver.html
http://www.computer-solutions.co.uk/chipdev/windriver.htm
Also, do a google serch on "frame grabbers" to see of the shelf products doing what you need.
Hope that helps

Similar Messages

For Experts: Why does LabView cause System reboot while accessing hardware with driver?

Hello NI Developers!
I use LabView 7.1 under Windows XP
I have a programm console application which accesses through Jungo Windriver PCI-E board.
This program works fine - and performs DMA data transfer between PC and Board's memory.
In order to implement this console application work together with LabView I did following:
1) Added this function inside the source:
_declspec(dllexport) void LVMainFunction(uInt32 *IntValue);
_declspec(dllexport) void LVMainFunction(uInt32 *IntValue)
    AllocConsole();                   //Open new console window
   SetConsoleTitle(L"Debug Window"); //Set a title for console window
    freopen("CONOUT$","a+",stdout); //redirec standard output stream to current window so
                                    // so we are able to see "printf" outputs
   freopen("CONIN$","a+",stdin);    //redirec standard input stream to current window so
                                    // so we are able pass inputs from keyboard
   main();                          //Call applications main function which does all the work
2) Compiled this new source as DLL library
3) Call LVMainFunction(...) function from LabView using Call Library Node
In the result: Executing VI - opens new console window, shows debug outputs and receives keyboard inputs.
It works fine till the last function, which perform DMA data transfer - and reboots PC.
1) Why does this happen?
2) I understand that opening console from Call Library Node, attaches together this console window and running VI. So If I close one of them - both windows closes.
   So does LabView have somekind of restrictions of accessing Hardware's functions?
I can read Board's resource information and view size of memory on board, interrupt functions and other information about device, but when I try to reach
DMA my system reboots. And I understand that this should be some kind of LabView problem, cause I tried different implementations, even without use of
console window - and the result is the same.
3) Should I split the program in to two separate processes and perform data exchange using Sockets or Pipes techology?
Thank you in advance!
ACiDUser
Message Edited by ACiDuser on 11-13-2008 09:37 AM

Hello!
At LAST!!!
I solved this problem!
From the beginning I was following National Instruments manual on how to build DLL with external IDE:
http://zone.ni.com/reference/en-XX/help/371361A-01/lvhowto/building_library_project/
Set the Struct member alignment control to 1 Byte.
Now this option caused my PC to reboot!
So could someone explain why this happened? and If it is a bad tip, so it's better to remove from manual. Then other people will not have such problems as I did
- wasting 2 monthes of time determining the problem.
I changed it to Set the Struct member alignment control to DEFAULT.
and now everything works fine.
Regards
Message Edited by ACiDuser on 11-13-2008 11:14 AM

Imac mid 2011 os10.7.5 can't access hardware test. could months ago, now no.

using alt+D can get (wifi only) connection to page with world map in circle, below "connecting internet recovery" and statement the "this may take a while".
Gives no option for ethernet , showing only wifi accounts even when wifi is turned off on compu.
After waiting quite a while an exclamation point covers circle with world and below says: apple.com/support -2002d - going there find nothing applicable to case.
I was able to access with no problem several times up til last couple of months. Can any one please advise how to access hardware test?????
Many thanks.
Carmenoax

using alt+D can get (wifi only) connection to page with world map in circle, below "connecting internet recovery" and statement the "this may take a while".
Gives no option for ethernet , showing only wifi accounts even when wifi is turned off on compu.
After waiting quite a while an exclamation point covers circle with world and below says: apple.com/support -2002d - going there find nothing applicable to case.
I was able to access with no problem several times up til last couple of months. Can any one please advise how to access hardware test?????
Many thanks.
Carmenoax

How to access hardware?

Hi there,
Could someone please tell me if it is possible to access hardware ports with java (i.e. like inport() and outport() in c)?
Is there any separate API available? (-> NOT the COMM API!!!)
If not, do i have to use JNI?
Concluding, is there any commercial library that allows you to do this in java?
Thanks in advance,
John

Hi again!
I choosed to go on and use the JNI ability of java.
I downloaded Borland c++ 5.5.1 which is a free 32-bit command line compiler for c++. I tried the "hello world" example in the JNI tutorial page and it worked great. However, when i tried to compile some code that contained the functions 'inportb' and 'outportb' (i.e. which is the reason of why i am using JNI) it tells me that these are undefined even if i imported the correct header files!
After some search i find out that borland removed these functions for security reasons with windows! (WHAT!?)
To conclude, my question is:
Does anyone know any free c++ compiler that is able to generate .dll files and also supports the functions 'inportb' and 'outportb'
Thanks a million times!
John

Java Program accessing hardware driver

I am planning to develope a project with a USB smart card reader. The USB smart card reader is for some form of authenication purpose of the card holder to verify that the authenticated user is using the program. The application will be a web based program in which a java applet (or java application) will be developed for the web page to access the local USB smart card reader. Can Java Applet has some form of ability to access the hardware, either by accessing the smart card API or it can directly access the USB port to read/write information directly to the smart card reader, provided that the USB reader can provide the low-level communication protocol.

You will have to sign your applet
And you might also need native libraries to access
the card readerThanks for your prompt help.
Because I am quite new to Java, I might ask some naive question.
When you "sign" the applet, which I believe it will be done in the browser setting to trust the applet, this will loosen the security concern of the applet, right?
The native libraries should then be in the form of a DLL in windows environment which the Java applet can call, right? And could you provide some sample code that how a DLL function call can be integrated into Jave.
Thanks again for your help.

Accessing hardware board with two VIs simultaneously

Hello,
I have a NI BNC-2090 board that I use to interface with a multimeter (which I get my data from) and an ion gauge (which needs to have its filament current regulated and held constant). I have a VI which I've written that performs both the data acquisition and current regulation, but it can only do one of these tasks at a time, which is undesirable because the filament current drifts when the data is being gathered.
In order to prevent the filament current from drifting, I want to create two standalone programs that I can run in parallel, so that the filament current can be regulated continuously and so that data can be acquired on demand. I've attached two programs which I've made to do this.
Each of the attached programs does its job very well. The problem I have arises when I try to run them both simultaneously. The error I get is Error -50103, which tells me the specified resource (my board, if I understand this correctly) is reserved.
I tried to be a little more explicit in my task creation and I also tried defining global virtual channels in MAX to no avail.
Any help would be greatly appreciated.
Regards,
Ali
Solved!
Go to Solution.
Attachments:
Standalone DAQ.vi ‏40 KB
Standalone PID Feedback.vi ‏51 KB

Ali H. wrote:
Brian,
Having all my reads in one task and all my writes in another makes sense, especially after I learned that the board has only one A/D converter.
What I'm struggling with now is how to restructure my set up. Is there a way to share tasks between VIs and keep the VIs distinct like I want so that I can run them individually or together as I need? Or will that requirement force me to incorporate the VIs I posted as subVIs of another VI which passes the same read and write tasks to both subVIs? (If this is unclear, see attached png; the case structures are so I can choose which subVIs run and the while loop is there so I can turn them on and off).
Thanks.
Yes, By adding in a Special type of Action Engine I've dubbed a "Resource Module" as a hardware access layer for yor task. Since the Module is not re-enterant any vi can call the Resource Module without fear of causing DAQmx errors but, the second caller will wait for the first call to finish. Here is an example notice that it keeps the resorurce discriptor (in this case a DAQmx Digital Out Task) on a Shift register to avoid the need for the caller to know what is going on with the resource (saves wires too).
Jeff
Attachments:
Attenuator.vi ‏30 KB

Hi friendz..plz hlp me to access hardware details

..any way to retrieve hardware details using java..java methods or java classes supporting tis..i want build an application for a network admin..to get all the hardware details of a system such as hardisk capacity ..free space ..memmory etc..plz help me..

Hi,
Check out the following Eg: to handle exceptions of FM in Reports,
CALL FUNCTION 'Z_CALL_TRANS' STARTING NEW TASK 'test'
        EXPORTING
          tcode          = 'SESS'
        EXCEPTIONS
          invalid_tcode = 1
          not_authorised = 2
          OTHERS         = 3.
      IF sy-subrc = 1.
        MESSAGE 'Invalid T-code' TYPE 'E'.
      ELSEIF sy-subrc = 2.
        MESSAGE 'Not Authorised to use this Transaction' TYPE 'E'.
      ENDIF.
Sy-subrc is equal to the order of the exceptions declared in that function module.

How to access performance counter directly?

What I am going to do is programming with hardware performace counters of UltraSPARC T2+ processors in Solaris 10. I programmed a loadable syscall to invoke the hv_niagara_getperf or ultra_getpic, trying to get the counters' data. But there just comes a panic, unresponsive without any text notice, and then reset. I don't know what's the real causes because I am not very familiar with SUN servers.
I did some experiments both in primary domain and logical domain. In primary domain, both hv_niagara_getperf and ultra_getpic lead to panic, and in logical domain, hv_niagara_getperf return the ENOACCESS status and ultra_getpic lead to panic.
My question are:
1, If there is some initialization works or privilege settings to do to prevent panic?
2, If Logical Domain can be set privileges to access hardware performace counters? (I read the Hypervisor api manuals and it says only one domain can access performance counters. But vcpus is divided and allocated to different domains, every vcpu has its performace counters, how can I do to access their own performace counters in different domains?)
3, I know there are methods such as libcpc, cpc module, and pcbe module for users or develpers to get performace data. What I am working at is to make some threads performance tuning on UltraSPARC T2+, Is the overhead acceptable to use these library or modules supported by the OS architecture.
Please help me, indicate my fault and give me some advice or instruction. Thank you very much.

What I am going to do is programming with hardware performace counters of UltraSPARC T2+ processors in Solaris 10. I programmed a loadable syscall to invoke the hv_niagara_getperf or ultra_getpic, trying to get the counters' data. But there just comes a panic, unresponsive without any text notice, and then reset. I don't know what's the real causes because I am not very familiar with SUN servers.
I did some experiments both in primary domain and logical domain. In primary domain, both hv_niagara_getperf and ultra_getpic lead to panic, and in logical domain, hv_niagara_getperf return the ENOACCESS status and ultra_getpic lead to panic.
My question are:
1, If there is some initialization works or privilege settings to do to prevent panic?
2, If Logical Domain can be set privileges to access hardware performace counters? (I read the Hypervisor api manuals and it says only one domain can access performance counters. But vcpus is divided and allocated to different domains, every vcpu has its performace counters, how can I do to access their own performace counters in different domains?)
3, I know there are methods such as libcpc, cpc module, and pcbe module for users or develpers to get performace data. What I am working at is to make some threads performance tuning on UltraSPARC T2+, Is the overhead acceptable to use these library or modules supported by the OS architecture.
Please help me, indicate my fault and give me some advice or instruction. Thank you very much.

Information about hardware development links

Hello everyone,
Sorry to ask this in this forum but I know no other compatible forum. My question is: how to develop a script or program that accesses hardware ports directly. Is it possible via SQL? Maybe via C++ or much more difficult if not impossible via Java? Thanks for any information.
Sincerely,
André Luiz

Did you try googling for this?
http://www.google.com/search?hl=en&lr=&q=java+to+access+hardware+ports&btnG=Search

Hardware SSL Accelerator + JSSE

Hi all,
How can I use hardware SSL/TLS accelerator with java platform. The server part of application needs hardware SSL/TLS acceleration. I was looking for information how "access" hardware accelerator from java application. The result was that I need custom JCE Provider which can work with this piece of hardware. Ok this point is clear. So I start looking for hardware accelarators which provide JCE Provider. But I failed. The questions are:
Did I understand correctly the mechanizm how use such piece of hardware?
Which hardware SSL accelerators provide JCE Provider?
Is somewhere universal JCE Provider which uses "external" SSL implementation e.g. OpenSSL (I was thinking about "bridge" between my application and hardware accelerator using external implementation)?
Every advice welcome. thank you and have a nice day.

Look into the mozilla.org's package jss. It is a C API
with java
interconnects (JNI) which will allow you to interface
with hardware
accelerators using PKCS#11...
You will need to have a compiler!ok .. it looks good. but how exactly it works? How I exactly redirect SSL request from CPU to hardware SSL accelerator.
I rather want to use standard JSSE from Java2 platform.
thanks for advice.

Hardware information thru Java prog

Can anybody provide me the information about how in Java one can retreive information regarding Hard disk serial number, free space, total space of hard disk etc through Java programming. It is possible in Visual Basic and I am sure there must be some method to get this info in Java.
I would also like to know various other utilities/methods thru which one can communicate with system hardware

To access hardware you must to use native methods ie your java application must to invoke some native library (DLL's in Windows) because this issue is OS dependent. There is an Java API specially dealing with this topic: JNI (Java Native Interface).

Window doesn't close wheh Call Library Function Node set to Run in Any Thread

This is a problem regarding Call Library Function Nodes running in the UI thread or any thread.
I have a camera which has its own API supplied as a dll. I have created a set of VI wrappers which each call a function in the dll through a Call Library Function Node.
Initially each CLFN was set to 'Run in the UI thread' (the default).
To start the camera streaming images I call (through a CLFN)
ICubeSDK_Start(int CamIndex, Hwnd, ImgHandle, bool Preview, bool callback);
If Preview = True then the image is displayed in a preview window.
If ImgHandle = NULL a default preview window
is used.
In the CLFN definition I define:
ImgHandle as a U32
Preview as a I32
To stop the camera streaming images I call
ICubeSDK_Stop(int CamIndex)
In the actual implementation I set ImgHandle = 0 (NULL) and Preview = 1 (true).
This all works fine, and a preview window is opened and images displayed. When I call ICubeSDK_Stop the preview window is closed.
However, I would prefer to set the CLFN to 'Run in any thread' because
a) when run in the UI thread the preview window randomly gets sent to the back when I switch focus between open VI windows (presumably because it is in the same thread as the VIs)
b) I don't want to put unnecessary stuff in the UI thread
c) my (naive?) understanding is that it is safer to run in any thread
So I have set all CLFNs to 'Run in any thread'
When I do this the preview window opens OK, and behaves like any other non LabVIEW controlled window in terms of focus. But when I call ICubeSDK_Stop() the preview window does not get closed properly, it just shows a blank image. I can't close it manually, there is no X in the corner and no option to close it from the taskbar. To get rid of it I have to close the LabVIEW project it is spawned from, which often results in a crash. It does appear as a separate item in task manager but if I 'end process' it, LabVIEW closes (and often crashes) as well.
If I change only the CLFNs that call the Start and Stop functions back to 'Run in the UI thread' then it all works fine again, except that the preview window gets sent to the back randomly as before.
So, what do I have to do to get the preview window to close properly if I set the CLFN to 'Run in any thread'.
Alternatively, is there a way to close the window programmatically (ie force it to close) after I have called ICube_Stop.
Thanks
DAve

Hi Dave,
The "Run In UI Thread" switches from the thread the VIs currently executing in to the user interface thread. If you select "Run in Any Thread", the Call Library Function Node continues in the currently executing thread. By default, all Call Library Function Nodes run in the User Interface thread.
Before you configure the Call Library Function Node to run in any thread, you have to make sure that the code is thread safe. Code is thread safe when it does not store any global data (e.g. global variables, files on disks, etc.), does not access any hardware, does not make calls to any functions, libraries or drivers that are not thread safe.
Unfortunately, since you said that your DLL accesses hardware, it is not recommended to use "Run in Any Thread." This is probably why you are seeing the crash.
If your preview window gets sent to the back you can programmatically bring it forward. Here is an example of how this can be done: http://decibel.ni.com/content/docs/DOC-4551
If you want to completely close the window down you can do so as described in this link: http://digital.ni.com/public.nsf/allkb/81E9C1441900FFCE8625748F0055DBB0?OpenDocument
I also thought you might find this useful: http://zone.ni.com/devzone/cda/tut/p/id/3009
I hope this helps.
Regards,
Mahdieh G
Applications Engineer
National Instruments UK&Ireland

A Quality Assurance Engineer's perspective on Neo2 PS/2 Port Problems.

I came here looking for some insight . . . . and while i got some confirmation that it's a common problem, I think some things need to be cleared up.
There's a mistake being made that disconnects cause and effect by lumping together effects that aren't necessarily from the same cause. Don't feel bad, everybody does it, I've just been trained to be critical about it.
I think there is more than one issue. Here's why.
1: I think the chipset or BIOS is cooking the ps/2 mouse data stream (and maybe USB HID data streams as well) when the "BIOS Support for USB Mouse" option is turned on. By this i mean that it's presenting the operating system with a virtual mouse device and working some behind-the-scenes magic on the data between computer and mouse.
My evidence:
With that option turned on, Linux kernel 2.6.12.2 (vanilla kernel.org sources) says this:
Jul 10 19:38:00 type kernel: input: PS/2 Generic Mouse on isa0060/serio1
Jul 10 19:38:00 type kernel: psmouse.c: Failed to enable mouse on isa0060/serio1
Jul 10 19:38:01 type kernel: psmouse.c: Mouse at isa0060/serio1/input0 lost synchronization, throwing 1 bytes away.
And with that option turned off, the kernel says this:
Jul 11 21:58:48 type kernel: input: ImExPS/2 Generic Explorer Mouse on isa0060/serio1
I think this bios option prevents the linux kernel serio driver from allowing the psmouse driver to perform two-way communication with the mouse in the standard way.
Disabling this bios option also makes all my PS/2 mice and trackballs work on bootup, where all of them needed to be re-plugged or have the kvm switch to another port and back before they would work previously.
I think many people are having some of their problems purely because of this bios option.
I think this is very bad, and that the developers responsible for this bios feature should be subjected to a public flogging and sent to a reeducation camp where they might learn to respect the law that the quality of a piece of software is inversely proportional to the amount of magic performed within it.
I can't even think of what the advantage of a virtual PS/2 mouse would be. You want to run DOS with mouse.com driving your usb mouse or something? We're supporting Win95 OSR1 users? I guess it might make Partition Magic boot floppies a tiny bit easier to manage, but sheesh. The damage far outweighs the benefit.
Even when it works, it will only work for fairly plain mice that don't need special protocols to work.
I don't think MSI did this, I think the bios vendor did it, and MSI doesn't realize what's going on.
Yes, I know the Explorer is a USB mouse on a PS/2 adapter, but i started down this road because my Logitech trackball - which uses the MouseManPlus protocol - and it still didn't work right when i replaced the mouse. I have a PS/2 based KVM that I'd like to keep using. The KVM has been out of the loop for these diagnostics.
2: While i admit that it could very well be a PS/2 port power issue, I think it has nothing at all to do with system power supply problems, least of all the 12V rail.
Why? Why on earth would my 5V keyboard and mouse care what's happening on the 12V rail, what's why.
Furthermore, the same KB and mouse mostly kinda/sorta work on a USB to PS2 adapter cable, which is on the exact same 5V rail as the keyboard and mouse ports, and if anything should draw MORE power.
They are however probably on separate fuses.
If it's a power problem, I'm leaning toward it being a slow-blowing fuse on the PS/2 ports that is being pushed near it's limits and is thus rippling. This is conjecture, and only MSI's rework guys or someone with a lot of diagnostic gear can tell you for sure.
3: Having fixed the mouse initialization and synchronization problems, I still have a problem.
I replaced my Lexmark (IBM) PS/2 keyboard with a KeyTronic PS/2 keyboard, replaced my Logitech Trackman Marble FX with a Microsoft Trackball Explorer, and sometimes, I still get an input lockup.
The mouse will just stop tracking in mid-sweep and the keyboard will stop keying.
And then the kernel says this:
Jul 11 23:37:49 type kernel: atkbd.c: Keyboard on isa0060/serio0 reports too many keys pressed.
Jul 11 23:37:50 type last message repeated 54 times
Jul 11 23:37:50 type kernel: atkbd.c: Spurious ACK on isa0060/serio0. Some program, like XFree86, might be trying access hardware directly
Jul 11 23:37:50 type kernel: input: AT Translated Set 2 keyboard on isa0060/serio0
Jul 11 23:37:50 type kernel: atkbd.c: Keyboard on isa0060/serio0 reports too many keys pressed.
Jul 11 23:38:18 type last message repeated 623 times
Jul 11 23:38:18 type kernel: atkbd.c: Unknown key released (translated set 2, code 0x7c on isa0060/serio0).
Jul 11 23:38:18 type kernel: atkbd.c: Use 'setkeycodes 7c <keycode>' to make it known.
Jul 11 23:38:18 type kernel: atkbd.c: Spurious ACK on isa0060/serio0. Some program, like XFree86, might be trying access hardware directly
Jul 11 23:38:19 type kernel: atkbd.c: Keyboard on isa0060/serio0 reports too many keys pressed.
Jul 11 23:38:19 type last message repeated 10 times
Jul 11 23:38:19 type kernel: atkbd.c: Unknown key released (translated set 2, code 0x68 on isa0060/serio0).
Jul 11 23:38:19 type kernel: atkbd.c: Use 'setkeycodes 68 <keycode>' to make it known.
Jul 11 23:38:19 type kernel: atkbd.c: Spurious ACK on isa0060/serio0. Some program, like XFree86, might be trying access hardware directly
Jul 11 23:38:21 type kernel: atkbd.c: Keyboard on isa0060/serio0 reports too many keys pressed.
Jul 11 23:38:21 type last message repeated 4 times
Jul 11 23:38:21 type kernel: atkbd.c: Spurious ACK on isa0060/serio0. Some program, like XFree86, might be trying access hardware directly
Jul 11 23:38:46 type kernel: atkbd.c: Keyboard on isa0060/serio0 reports too many keys pressed.
Jul 11 23:39:16 type last message repeated 2439 times
Jul 11 23:40:16 type last message repeated 4986 times
Jul 11 23:41:16 type last message repeated 4988 times
Jul 11 23:42:16 type last message repeated 4987 times
Jul 11 23:43:16 type last message repeated 4987 times
Jul 11 23:44:16 type last message repeated 4987 times
Jul 11 23:45:16 type last message repeated 4986 times
Jul 11 23:46:16 type last message repeated 4944 times
Jul 11 23:46:24 type last message repeated 688 times
I wonder if the "AT Translated" designation that the atkbd driver gives the keyboard may indicate that the PS/2 keyboard is having it's data stream cooked as well?
Edit: (for geeks) - It turns out that bios can set up your keyboard as either "raw" or "translated". It's possible to switch a keyboard back into "raw" mode, but most operating systems don't do this because it can cause problems on laptops and other computers that don't have their keyboard on a normal ps/2 port.
I don't mind having a keyboard on a usb converter, but the usb converter translates the ps/2 mouse signals too poorly. My Trackman FX has no buttons on the usb converter, and the Explorer is missing two buttons on the usb converter.
4: I don't have the 'reboot' problem, but maybe that only happens in windows.
What i see sometimes is the above, and sometimes the keyboard starts responding slowly - like it takes 30 seconds per keypress. And sometimes by re-plugging the connectors i can get it to come back.
I'm CERTAIN that some of these problems - at least one of them - can be fixed in bios. If only by defaulting the mouse bios support to off. This won't keep you from being able to navigate in bios or use your USB mouse in any OS since Win95 OSR2.1.
For at least the mouse problems, it appears that many of the problems people have reported can be resolved merely by disabling "BIOS Support for USB Mouse".

Quote from: d2thez on 13-July-05, 10:00:03
Ok, I am lost to be honest, but I just need to know if this applies to me. Please help!
I have a K8N Neo Platinum for the socket 754, not a Neo2. I use a USB mouse and a PS/2 keyboard. I have both "USB keyboard/storage support" and "USB mouse support" enabled in my bios.
You have me scared from reading your post that having them enabled will short out my PS/2 or USB. Will this happen? And should I have these options enabled or not?
And finally, if I do disable them, do I lose and functionality?? Please help me out here!
Relax. You're not going to short out anything or lose any functionality.
The first one - USB Keyboard/Storage Support - this makes it possible for you to boot off of USB drives (like the flash drives) and makes USB keyboards work in DOS. It may be required to make USB keyboards work in bios setup, but i haven't tested that.
If you have a PS/2 keyboard and you don't intend to boot off of a USB drive, you can safely disable that option with no loss in functionality of any kind.
The second one - USB Mouse Support - This is a bit of software in BIOS that takes control of USB mice and makes them appear like PS/2 mice in order to provide easy mouse support for operating systmems that don't understand USB.
Specifically, DOS and Windows versions prior to Win95 OSR2.1.
Since Win95 probably won't boot at all on an Athlon64 - and in any case won't have the drivers you need for nearly anything - the only possible scenario where you might need this feature is if you were booting some old versions of Partition Magic or Norton Ghost or other utility floppy that runs on DOS, supports mouse navigation, and is old enough that it doesn't have a DOS USB mouse driver. Newer versions of pqmagic and ghost probably have usb mouse support on their boot floppies.
You can stop reading now if you just wanted to be reassured.
The reason it causes a problem is because mice are far more complex than keyboards. For some reason, even if you don't have a USB mouse installed, the signals from your PS/2 mouse are run through software in BIOS to make the signals from your mouse look like the signals from a generic PS/2 mouse - instead of a mouse that speaks the MouseMan protocol or the Intelimouse protocol or the Explorer protocol (or three or four other protocols).
This sounds like a strange way to do it, but it's actually easier in software to treat all inputs to the same logic and translate them to a virtual device than it is to detect whether translation is needed and then only translate the signals that need it.
This interferes with the mouse drivers. It also makes it impossible for some mice to 'wake up' properly when the computer is turned on.
It also doesn't work very well because it doesn't install all the myriad mouse protocols out there. KVM manufacturers have the same problem. If they fix the Intelimouse protocol they frequently break the MouseMan protocol.
If your mouse has only two or three buttons and no scroll wheel (which counts as two or three buttons), and your mouse was not made by Microsoft or Logitech, chances are your mouse only speaks the plain PS/2 Mouse protocol and you won't have problems with translation, but you might have some other symptoms. It appears that the BIOS may actually understand the Intelimouse protocol, so Microsoft mice may work anyway.

Need help: Unable to handle kernel paging request at virtual address; javac

Hi
we're working with apache tomcat under linux mandrake 10. (x86)
when our webapp get recompiled the server stop responding
(web server, telnet, etc... are down, but the server is pingable)
after a hard reboot , we get this message in var/log/messages :
Unable to handle kernel paging request at virtual address 02000064
kernel: printing eip:
kernel: c018e379
kernel: *pde = 00000000
kernel: Oops: 0000 [#1]
kernel: CPU: 1
kernel: EIP: 0060:[proc_pid_stat+137/928] Not tainted VLI
kernel: EIP: 0060:[<c018e379>] Not tainted VLI
kernel: EFLAGS: 00010286
kernel: EIP is at proc_pid_stat+0x89/0x3a0
kernel: eax: 00000000 ebx: 02000000 ecx: d85ac000 edx: 92960700
kernel: esi: d11ea6f0 edi: ded440a0 ebp: cf0ddf44 esp: cf0ddee4
kernel: ds: 007b es: 007b ss: 0068
kernel: Process javac (pid: 2415, threadinfo=cf0dc000 task=d11ea6f0)
kernel: Stack: c0143d5a c1259e78 00000000 c1259e78 c0343980 0000015b 00000000 cf0ddf40
attached ther is kernel messages, pci , dmesg.
Thanks
Massimo TRENTO
Apache Tomcat/4.1.30
j2sdk1.4.2_01
kernel 2.6.3-7mdksmp #1 SMP
--- DMESG ---
00100000 - 000000001f6f0000 (usable)
BIOS-e820: 000000001f6f0000 - 000000001f6fb000 (ACPI data)
BIOS-e820: 000000001f6fb000 - 000000001f700000 (ACPI NVS)
BIOS-e820: 000000001f700000 - 000000001f780000 (usable)
BIOS-e820: 000000001f780000 - 0000000020000000 (reserved)
BIOS-e820: 00000000fec00000 - 00000000fed00400 (reserved)
BIOS-e820: 00000000fee00000 - 00000000fef00000 (reserved)
BIOS-e820: 00000000ffb80000 - 00000000ffc00000 (reserved)
BIOS-e820: 00000000fff00000 - 0000000100000000 (reserved)
503MB LOWMEM available.
found SMP MP-table at 000f7920
hm, page 000f7000 reserved twice.
hm, page 000f8000 reserved twice.
hm, page 0009f000 reserved twice.
hm, page 000a0000 reserved twice.
On node 0 totalpages: 128896
DMA zone: 4096 pages, LIFO batch:1
Normal zone: 124800 pages, LIFO batch:16
HighMem zone: 0 pages, LIFO batch:1
DMI present.
ACPI: RSDP (v000 PTLTD ) @ 0x000f7980
ACPI: RSDT (v001 PTLTD RSDT 0x00050000 LTP 0x00000000) @ 0x1f6f74ed
ACPI: FADT (v001 FSC D156x 0x00050000 0x000f4240) @ 0x1f6f751d
ACPI: MADT (v001 FSC APIC 0x00050000 CSF 0x00000000) @ 0x1f6faf76
ACPI: BOOT (v001 PTLTD $SBFTBL$ 0x00050000 LTP 0x00000001) @ 0x1f6fafd8
ACPI: DSDT (v001 FSC D156x 0x00050000 MSFT 0x0100000e) @ 0x00000000
ACPI: PM-Timer IO Port: 0xf008
ACPI: Local APIC address 0xfee00000
ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
Processor #0 15:2 APIC version 20
ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
Processor #1 15:2 APIC version 20
ACPI: LAPIC_NMI (acpi_id[0xff] high edge lint[0x1])
Using ACPI for processor (LAPIC) configuration information
Intel MultiProcessor Specification v1.1
Virtual Wire compatibility mode.
OEM ID: Product ID: APIC at: 0xFEE00000
I/O APIC #2 Version 32 at 0xFEC00000.
Enabling APIC mode: Flat. Using 1 I/O APICs
Processors: 2
Built 1 zonelists
Kernel command line: auto BOOT_IMAGE=linux-nonfb ro root=301 noapic devfs=mount acpi=ht resume=/dev/hda5
Initializing CPU#0
PID hash table entries: 2048 (order 11: 16384 bytes)
Detected 2793.223 MHz processor.
Using pmtmr for high-res timesource
Console: colour VGA+ 80x25
Memory: 504916k/515584k available (1920k kernel code, 9820k reserved, 892k data, 288k init, 0k highmem)
Checking if this processor honours the WP bit even in supervisor mode... Ok.
Calibrating delay loop... 5537.79 BogoMIPS
Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
Mount-cache hash table entries: 512 (order: 0, 4096 bytes)
checking if image is initramfs...it isn't (no cpio magic); looks like an initrd
Freeing initrd memory: 225k freed
CPU: After generic identify, caps: bfebfbff 00000000 00000000 00000000
CPU: After vendor identify, caps: bfebfbff 00000000 00000000 00000000
CPU: Trace cache: 12K uops, L1 D cache: 8K
CPU: L2 cache: 512K
CPU: Physical Processor ID: 0
CPU: After all inits, caps: bfebfbff 00000000 00000000 00000080
Intel machine check architecture supported.
Intel machine check reporting enabled on CPU#0.
CPU#0: Intel P4/Xeon Extended MCE MSRs (12) available
CPU#0: Thermal monitoring enabled
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Checking 'hlt' instruction... OK.
POSIX conformance testing by UNIFIX
CPU0: Intel(R) Pentium(R) 4 CPU 2.80GHz stepping 09
per-CPU timeslice cutoff: 1462.56 usecs.
task migration cache decay timeout: 2 msecs.
enabled ExtINT on CPU#0
ESR value before enabling vector: 00000000
ESR value after enabling vector: 00000000
Booting processor 1/1 eip 3000
Initializing CPU#1
masked ExtINT on CPU#1
ESR value before enabling vector: 00000000
ESR value after enabling vector: 00000000
Calibrating delay loop... 5570.56 BogoMIPS
CPU: After generic identify, caps: bfebfbff 00000000 00000000 00000000
CPU: After vendor identify, caps: bfebfbff 00000000 00000000 00000000
CPU: Trace cache: 12K uops, L1 D cache: 8K
CPU: L2 cache: 512K
CPU: Physical Processor ID: 0
CPU: After all inits, caps: bfebfbff 00000000 00000000 00000080
Intel machine check architecture supported.
Intel machine check reporting enabled on CPU#1.
CPU#1: Intel P4/Xeon Extended MCE MSRs (12) available
CPU#1: Thermal monitoring enabled
CPU1: Intel(R) Pentium(R) 4 CPU 2.80GHz stepping 09
Total of 2 processors activated (11108.35 BogoMIPS).
cpu_sibling_map[0] = 1
cpu_sibling_map[1] = 0
Using local APIC timer interrupts.
calibrating APIC timer ...
..... CPU clock speed is 2792.0645 MHz.
..... host bus clock speed is 199.0474 MHz.
checking TSC synchronization across 2 CPUs: passed.
Starting migration thread for cpu 0
Starting migration thread for cpu 1
Brought up 1 CPUs
NET: Registered protocol family 16
EISA bus registered
PCI: PCI BIOS revision 2.10 entry at 0xfd8cb, last bus=3
PCI: Using configuration type 1
mtrr: v2.0 (20020519)
ACPI: Subsystem revision 20040211
ACPI: Interpreter disabled.
Linux Plug and Play Support v0.97 (c) Adam Belay
PnPBIOS: Disabled
PCI: Probing PCI hardware
PCI: Probing PCI hardware (bus 00)
PCI: Ignoring BAR0-3 of IDE controller 0000:00:1f.1
Transparent bridge - 0000:00:1e.0
PCI: Discovered primary peer bus 01 [IRQ]
PCI: Using IRQ router PIIX/ICH [8086/24d0] at 0000:00:1f.0
PCI: IRQ 0 for device 0000:00:1f.1 doesn't match PIRQ mask - try pci=usepirqmask
PCI: Found IRQ 10 for device 0000:00:1f.1
PCI: Sharing IRQ 10 with 0000:00:1d.2
PCI: Sharing IRQ 10 with 0000:00:1f.2
PCI: Sharing IRQ 10 with 0000:02:01.0
SBF: Simple Boot Flag extension found and enabled.
SBF: Setting boot flags 0x1
apm: BIOS version 1.2 Flags 0x03 (Driver version 1.16ac)
apm: disabled - APM is not SMP safe.
Starting balanced_irq
ikconfig 0.7 with /proc/config*
VFS: Disk quotas dquot_6.5.1
devfs: 2004-01-31 Richard Gooch ([email protected])
devfs: boot_options: 0x1
Initializing Cryptographic API
isapnp: Scanning for PnP cards...
isapnp: No Plug & Play device found
pty: 1024 Unix98 ptys configured
Serial: 8250/16550 driver $Revision: 1.90 $ 8 ports, IRQ sharing enabled
ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
RAMDISK driver initialized: 16 RAM disks of 32000K size 1024 blocksize
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
ICH5: IDE controller at PCI slot 0000:00:1f.1
PCI: Found IRQ 10 for device 0000:00:1f.1
PCI: Sharing IRQ 10 with 0000:00:1d.2
PCI: Sharing IRQ 10 with 0000:00:1f.2
PCI: Sharing IRQ 10 with 0000:02:01.0
ICH5: chipset revision 2
ICH5: not 100% native mode: will probe irqs later
ide0: BM-DMA at 0x3000-0x3007, BIOS settings: hda:DMA, hdb:pio
ide1: BM-DMA at 0x3008-0x300f, BIOS settings: hdc:DMA, hdd:pio
hda: WDC WD800LB-07DNA2, ATA DISK drive
Using anticipatory io scheduler
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
hdc: LITE-ON COMBO LTC-48161H, ATAPI CD/DVD-ROM drive
ide1 at 0x170-0x177,0x376 on irq 15
ICH5-SATA: IDE controller at PCI slot 0000:00:1f.2
PCI: Found IRQ 10 for device 0000:00:1f.2
PCI: Sharing IRQ 10 with 0000:00:1d.2
PCI: Sharing IRQ 10 with 0000:00:1f.1
PCI: Sharing IRQ 10 with 0000:02:01.0
ICH5-SATA: chipset revision 2
ICH5-SATA: 100% native mode on irq 10
ide2: BM-DMA at 0x3010-0x3017, BIOS settings: hde:pio, hdf:pio
ide3: BM-DMA at 0x3018-0x301f, BIOS settings: hdg:pio, hdh:pio
hda: max request size: 1024KiB
hda: 156301488 sectors (80026 MB) w/2048KiB Cache, CHS=16383/255/63, UDMA(100)
/dev/ide/host0/bus0/target0/lun0: p1 p2 < p5 p6 >
mice: PS/2 mouse device common for all mice
serio: i8042 AUX port at 0x60,0x64 irq 12
input: ImPS/2 Generic Wheel Mouse on isa0060/serio1
serio: i8042 KBD port at 0x60,0x64 irq 1
input: AT Translated Set 2 keyboard on isa0060/serio0
md: md driver 0.90.0 MAX_MD_DEVS=256, MD_SB_DISKS=27
EISA: Probing bus 0 at eisa0
NET: Registered protocol family 2
IP: routing cache hash table of 4096 buckets, 32Kbytes
TCP: Hash tables configured (established 32768 bind 32768)
NET: Registered protocol family 1
BIOS EDD facility v0.13 2004-Mar-09, 1 devices found
Please report your BIOS at http://linux.dell.com/edd/results.html
PM: Reading pmdisk image.
PM: Resume from disk failed.
md: Autodetecting RAID arrays.
md: autorun ...
md: ... autorun DONE.
RAMDISK: Compressed image found at block 0
VFS: Mounted root (ext2 filesystem).
Mounted devfs on /dev
SCSI subsystem initialized
libata version 1.00 loaded.
EXT3-fs: INFO: recovery required on readonly filesystem.
EXT3-fs: write access will be enabled during recovery.
kjournald starting. Commit interval 5 seconds
EXT3-fs: hda1: orphan cleanup on readonly fs
ext3_orphan_cleanup: deleting unreferenced inode 1038473
ext3_orphan_cleanup: deleting unreferenced inode 1038472
ext3_orphan_cleanup: deleting unreferenced inode 1038471
ext3_orphan_cleanup: deleting unreferenced inode 1038470
ext3_orphan_cleanup: deleting unreferenced inode 1038469
ext3_orphan_cleanup: deleting unreferenced inode 1038467
ext3_orphan_cleanup: deleting unreferenced inode 1038466
ext3_orphan_cleanup: deleting unreferenced inode 1038464
ext3_orphan_cleanup: deleting unreferenced inode 1038463
ext3_orphan_cleanup: deleting unreferenced inode 1038462
ext3_orphan_cleanup: deleting unreferenced inode 1038461
ext3_orphan_cleanup: deleting unreferenced inode 1038460
ext3_orphan_cleanup: deleting unreferenced inode 1038459
ext3_orphan_cleanup: deleting unreferenced inode 1038458
ext3_orphan_cleanup: deleting unreferenced inode 1038457
ext3_orphan_cleanup: deleting unreferenced inode 1038456
ext3_orphan_cleanup: deleting unreferenced inode 1038455
ext3_orphan_cleanup: deleting unreferenced inode 1038454
ext3_orphan_cleanup: deleting unreferenced inode 973782
EXT3-fs: hda1: 19 orphan inodes deleted
EXT3-fs: recovery complete.
EXT3-fs: mounted filesystem with ordered data mode.
Mounted devfs on /dev
Freeing unused kernel memory: 288k freed
Real Time Clock Driver v1.12
drivers/usb/core/usb.c: registered new driver usbfs
drivers/usb/core/usb.c: registered new driver hub
drivers/usb/host/uhci-hcd.c: USB Universal Host Controller Interface driver v2.1
PCI: Found IRQ 9 for device 0000:00:1d.0
PCI: Sharing IRQ 9 with 0000:00:02.0
PCI: Sharing IRQ 9 with 0000:00:1d.3
uhci_hcd 0000:00:1d.0: UHCI Host Controller
PCI: Setting latency timer of device 0000:00:1d.0 to 64
uhci_hcd 0000:00:1d.0: irq 9, io base 00001400
uhci_hcd 0000:00:1d.0: new USB bus registered, assigned bus number 1
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 2 ports detected
PCI: Found IRQ 11 for device 0000:00:1d.1
uhci_hcd 0000:00:1d.1: UHCI Host Controller
PCI: Setting latency timer of device 0000:00:1d.1 to 64
uhci_hcd 0000:00:1d.1: irq 11, io base 00001800
uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus number 2
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 2 ports detected
PCI: Found IRQ 10 for device 0000:00:1d.2
PCI: Sharing IRQ 10 with 0000:00:1f.1
PCI: Sharing IRQ 10 with 0000:00:1f.2
PCI: Sharing IRQ 10 with 0000:02:01.0
uhci_hcd 0000:00:1d.2: UHCI Host Controller
PCI: Setting latency timer of device 0000:00:1d.2 to 64
uhci_hcd 0000:00:1d.2: irq 10, io base 00001c00
uhci_hcd 0000:00:1d.2: new USB bus registered, assigned bus number 3
hub 3-0:1.0: USB hub found
hub 3-0:1.0: 2 ports detected
PCI: Found IRQ 9 for device 0000:00:1d.3
PCI: Sharing IRQ 9 with 0000:00:02.0
PCI: Sharing IRQ 9 with 0000:00:1d.0
uhci_hcd 0000:00:1d.3: UHCI Host Controller
PCI: Setting latency timer of device 0000:00:1d.3 to 64
uhci_hcd 0000:00:1d.3: irq 9, io base 00002000
uhci_hcd 0000:00:1d.3: new USB bus registered, assigned bus number 4
hub 4-0:1.0: USB hub found
hub 4-0:1.0: 2 ports detected
PCI: Found IRQ 9 for device 0000:00:1d.7
ehci_hcd 0000:00:1d.7: EHCI Host Controller
PCI: Setting latency timer of device 0000:00:1d.7 to 64
ehci_hcd 0000:00:1d.7: irq 9, pci mem e0004000
ehci_hcd 0000:00:1d.7: new USB bus registered, assigned bus number 5
PCI: cache line size of 128 is not supported by device 0000:00:1d.7
ehci_hcd 0000:00:1d.7: USB 2.0 enabled, EHCI 1.00, driver 2003-Dec-29
hub 5-0:1.0: USB hub found
hub 5-0:1.0: 8 ports detected
EXT3 FS on hda1, internal journal
Adding 522072k swap on /dev/hda5. Priority:-1 extents:1
Linux agpgart interface v0.100 (c) Dave Jones
agpgart: Detected an Intel 865 Chipset.
agpgart: Maximum main memory to use for agp memory: 431M
agpgart: Detected 8060K stolen memory.
agpgart: AGP aperture is 128M @ 0xf0000000
Supermount version 2.0.4 for kernel 2.6
kjournald starting. Commit interval 5 seconds
EXT3 FS on hda6, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
Intel(R) PRO/1000 Network Driver - version 5.2.30.1-k2
Copyright (c) 1999-2004 Intel Corporation.
PCI: Found IRQ 10 for device 0000:02:01.0
PCI: Sharing IRQ 10 with 0000:00:1d.2
PCI: Sharing IRQ 10 with 0000:00:1f.1
PCI: Sharing IRQ 10 with 0000:00:1f.2
PCI: Setting latency timer of device 0000:02:01.0 to 64
eth0: Intel(R) PRO/1000 Network Connection
inserting floppy driver for 2.6.3-7mdksmp
Floppy drive(s): fd0 is 1.44M
FDC 0 is a post-1991 82077
hdc: ATAPI 48X DVD-ROM CD-R/RW CD-MRW drive, 2048kB Cache, UDMA(33)
Uniform CD-ROM driver Revision: 3.20
ide-floppy driver 0.99.newide
drivers/usb/core/usb.c: registered new driver hiddev
drivers/usb/core/usb.c: registered new driver hid
drivers/usb/input/hid-core.c: v2.0:USB HID core driver
NET: Registered protocol family 17
e1000: eth0 NIC Link is Up 100 Mbps Half Duplex
PCI: Found IRQ 5 for device 0000:00:1f.5
PCI: Sharing IRQ 5 with 0000:00:1f.3
PCI: Setting latency timer of device 0000:00:1f.5 to 64
intel8x0_measure_ac97_clock: measured 49851 usecs
intel8x0: clocking to 48000
NET: Registered protocol family 10
Disabled Privacy Extensions on device c037da00(lo)
IPv6 over IPv4 tunneling driver
Installing knfsd (copyright (C) 1996 [email protected]).
atkbd.c: Unknown key released (translated set 2, code 0x7a on isa0060/serio0).
atkbd.c: This is an XFree86 bug. It shouldn't access hardware directly.
atkbd.c: Unknown key released (translated set 2, code 0x7a on isa0060/serio0).
atkbd.c: This is an XFree86 bug. It shouldn't access hardware directly.
eth0: no IPv6 routers present
Neighbour table overflow.
Neighbour table overflow.
Neighbour table overflow.
Neighbour table overflow.
Neighbour table overflow.
Neighbour table overflow.
Neighbour table overflow.
Neighbour table overflow.
Neighbour table overflow.
Neighbour table overflow.
printk: 24045 messages suppressed.
Neighbour table overflow.
printk: 24276 messages suppressed.
Neighbour table overflow.
printk: 16555 messages suppressed.
Neighbour table overflow.
Neighbour table overflow.
Neighbour table overflow.
Neighbour table overflow.
Neighbour table overflow.
Neighbour table overflow.
Neighbour table overflow.
Neighbour table overflow.
Neighbour table overflow.
Neighbour table overflow.
printk: 24221 messages suppressed.
Neighbour table overflow.
printk: 24272 messages suppressed.
Neighbour table overflow.
printk: 15931 messages suppressed.
Neighbour table overflow.
Neighbour table overflow.
Neighbour table overflow.
Neighbour table overflow.
Neighbour table overflow.
Neighbour table overflow.
Neighbour table overflow.
Neighbour table overflow.
Neighbour table overflow.
Neighbour table overflow.
printk: 24289 messages suppressed.
Neighbour table overflow.
printk: 21235 messages suppressed.
Neighbour table overflow.
---- LSPCI ---
00:00.0 Host bridge: Intel Corp. 82865G/PE/P Processor to I/O Controller (rev 02)
00:02.0 VGA compatible controller: Intel Corp. 82865G Integrated Graphics Device (rev 02)
00:03.0 PCI bridge: Intel Corp. 82865G/PE/P Processor to PCI to CSA Bridge (rev 02)
00:1d.0 USB Controller: Intel Corp. 82801EB USB (rev 02)
00:1d.1 USB Controller: Intel Corp. 82801EB USB (rev 02)
00:1d.2 USB Controller: Intel Corp. 82801EB USB (rev 02)
00:1d.3 USB Controller: Intel Corp. 82801EB USB (rev 02)
00:1d.7 USB Controller: Intel Corp. 82801EB USB2 (rev 02)
00:1e.0 PCI bridge: Intel Corp. 82801BA/CA/DB/EB PCI Bridge (rev c2)
00:1f.0 ISA bridge: Intel Corp. 82801EB LPC Interface Controller (rev 02)
00:1f.1 IDE interface: Intel Corp. 82801EB Ultra ATA Storage Controller (rev 02)
00:1f.2 IDE interface: Intel Corp. 82801EB Ultra ATA Storage Controller (rev 02)
00:1f.3 SMBus: Intel Corp. 82801EB SMBus Controller (rev 02)
00:1f.5 Multimedia audio controller: Intel Corp. 82801EB AC'97 Audio Controller (rev 02)
02:01.0 Ethernet controller: Intel Corp.: Unknown device 1019
-- LSMOD --
Module Size Used by
nfsd 175840 8
exportfs 7552 1 nfsd
md5 4864 1
ipv6 251392 29
snd-seq-oss 33568 0
snd-seq-midi-event 8704 1 snd-seq-oss
snd-seq 55696 4 snd-seq-oss,snd-seq-midi-event
snd-pcm-oss 53316 0
snd-mixer-oss 19008 1 snd-pcm-oss
snd-intel8x0 34440 0
snd-ac97-codec 59588 1 snd-intel8x0
snd-pcm 97440 2 snd-pcm-oss,snd-intel8x0
snd-timer 26660 2 snd-seq,snd-pcm
gameport 5664 1 snd-intel8x0
snd-page-alloc 12996 2 snd-intel8x0,snd-pcm
snd-mpu401-uart 8320 1 snd-intel8x0
snd-rawmidi 25248 1 snd-mpu401-uart
snd-seq-device 9032 3 snd-seq-oss,snd-seq,snd-rawmidi
snd 55492 12 snd-seq-oss,snd-seq-midi-event,snd-seq,snd-pcm-oss,snd-mixer-oss,snd-intel8x0,snd-ac97-codec,snd-pcm,snd-timer,snd-mpu401-uart,snd-rawmidi,snd-seq-device
soundcore 10560 1 snd
af_packet 22632 0
hid 55360 0
raw 8640 1
ide-floppy 19776 0
ide-tape 36752 0
ide-cd 41764 0
cdrom 38272 1 ide-cd
floppy 61620 0
e1000 83460 0
supermount 39856 1
intel-agp 18364 1
agpgart 32460 2 intel-agp
ehci-hcd 25572 0
uhci-hcd 31856 0
usbcore 103228 5 hid,ehci-hcd,uhci-hcd
rtc 13640 0
ext3 114216 2
jbd 61976 1 ext3
sd_mod 17696 0
ata_piix 8836 0
libata 40256 1 ata_piix,[permanent]
scsi_mod 117104 2 sd_mod,libata
----- /var/log/kernel/warnings -------
Oct 5 10:16:47 nsilaslin02 kernel: printing eip:
Oct 5 10:16:47 nsilaslin02 kernel: c018e379
Oct 5 10:16:47 nsilaslin02 kernel: Oops: 0000 [#1]
Oct 5 10:16:47 nsilaslin02 kernel: CPU: 1
Oct 5 10:16:47 nsilaslin02 kernel: EIP: 0060:[proc_pid_stat+137/928] Not tainted VLI
Oct 5 10:16:47 nsilaslin02 kernel: EIP: 0060:[<c018e379>] Not tainted VLI
Oct 5 10:16:47 nsilaslin02 kernel: EFLAGS: 00010286
Oct 5 10:16:47 nsilaslin02 kernel: EIP is at proc_pid_stat+0x89/0x3a0
Oct 5 10:16:47 nsilaslin02 kernel: eax: 00000000 ebx: 02000000 ecx: d85ac000 edx: 92960700
Oct 5 10:16:47 nsilaslin02 kernel: esi: d11ea6f0 edi: ded440a0 ebp: cf0ddf44 esp: cf0ddee4
Oct 5 10:16:47 nsilaslin02 kernel: ds: 007b es: 007b ss: 0068
Oct 5 10:16:47 nsilaslin02 kernel: Process javac (pid: 2415, threadinfo=cf0dc000 task=d11ea6f0)
Oct 5 10:16:47 nsilaslin02 kernel: Stack: c0143d5a c1259e78 00000000 c1259e78 c0343980 0000015b 00000000 cf0ddf40
Oct 5 10:16:47 nsilaslin02 kernel: 52143e93 00000000 00000000 00000000 00000000 00000000 00000000 00000000
Oct 5 10:16:47 nsilaslin02 kernel: 00000000 00000000 000000d0 00001000 000000d0 d11ea6f0 00000400 de64f060
Oct 5 10:16:47 nsilaslin02 kernel: Call Trace:
Oct 5 10:16:47 nsilaslin02 kernel: [buffered_rmqueue+234/400] buffered_rmqueue+0xea/0x190
Oct 5 10:16:47 nsilaslin02 kernel: [<c0143d5a>] buffered_rmqueue+0xea/0x190
Oct 5 10:16:47 nsilaslin02 kernel: [proc_info_read+75/320] proc_info_read+0x4b/0x140
Oct 5 10:16:47 nsilaslin02 kernel: [<c018b60b>] proc_info_read+0x4b/0x140
Oct 5 10:16:47 nsilaslin02 kernel: [vfs_read+142/224] vfs_read+0x8e/0xe0
Oct 5 10:16:47 nsilaslin02 kernel: [<c015bf2e>] vfs_read+0x8e/0xe0
Oct 5 10:16:47 nsilaslin02 kernel: [sys_read+46/80] sys_read+0x2e/0x50
Oct 5 10:16:47 nsilaslin02 kernel: [<c015c14e>] sys_read+0x2e/0x50
Oct 5 10:16:47 nsilaslin02 kernel: [sysenter_past_esp+82/121] sysenter_past_esp+0x52/0x79
Oct 5 10:16:47 nsilaslin02 kernel: [<c010b1b9>] sysenter_past_esp+0x52/0x79
Oct 5 10:16:47 nsilaslin02 kernel:
Oct 5 10:16:47 nsilaslin02 kernel: Code: 00 00 8b 7e 68 85 ff 74 09 57 e8 b3 5f f9 ff 59 89 c7 8b 8e 24 03 00 00 85 c9 74 38 8b 81 98 00 00 00 89 45 c8 8b 59 04 8b 51 08 <0f> bf 43 64 0f bf 5b 66 c1 e0 14 09 d8 01 d0 89 c1 c1 e9 14 0f
Oct 5 10:30:32 nsilaslin02 kernel: Linux version 2.6.3-7mdksmp ([email protected]) (gcc version 3.3.2 (Mandrake Linux 10.0 3.3.2-6mdk)) #1 SMP Wed Mar 17 14:24:28 CET 2004
Oct 5 10:30:32 nsilaslin02 kernel: BIOS-e820: 0000000000000000 - 000000000009f800 (usable)
Oct 5 10:30:32 nsilaslin02 kernel: BIOS-e820: 000000000009f800 - 00000000000a0000 (reserved)
Oct 5 10:30:32 nsilaslin02 kernel: BIOS-e820: 00000000000e0000 - 0000000000100000 (reserved)
Oct 5 10:30:32 nsilaslin02 kernel: BIOS-e820: 0000000000100000 - 000000001f6f0000 (usable)
Oct 5 10:30:32 nsilaslin02 kernel: BIOS-e820: 000000001f6f0000 - 000000001f6fb000 (ACPI data)
Oct 5 10:30:32 nsilaslin02 kernel: BIOS-e820: 000000001f6fb000 - 000000001f700000 (ACPI NVS)
Oct 5 10:30:32 nsilaslin02 kernel: BIOS-e820: 000000001f700000 - 000000001f780000 (usable)
Oct 5 10:30:32 nsilaslin02 kernel: BIOS-e820: 000000001f780000 - 0000000020000000 (reserved)
Oct 5 10:30:32 nsilaslin02 kernel: BIOS-e820: 00000000fec00000 - 00000000fed00400 (reserved)
Oct 5 10:30:32 nsilaslin02 kernel: BIOS-e820: 00000000fee00000 - 00000000fef00000 (reserved)
Oct 5 10:30:32 nsilaslin02 kernel: BIOS-e820: 00000000ffb80000 - 00000000ffc00000 (reserved)
Oct 5 10:30:32 nsilaslin02 kernel: BIOS-e820: 00000000fff00000 - 0000000100000000 (reserved)
Oct 5 10:30:32 nsilaslin02 kernel: hm, page 000f7000 reserved twice.
Oct 5 10:30:32 nsilaslin02 kernel: hm, page 000f8000 reserved twice.
Oct 5 10:30:32 nsilaslin02 kernel: hm, page 0009f000 reserved twice.
Oct 5 10:30:32 nsilaslin02 kernel: hm, page 000a0000 reserved twice.
Oct 5 10:30:32 nsilaslin02 kernel: On node 0 totalpages: 128896
Oct 5 10:30:32 nsilaslin02 kernel: DMA zone: 4096 pages, LIFO batch:1
Oct 5 10:30:32 nsilaslin02 kernel: Normal zone: 124800 pages, LIFO batch:16
Oct 5 10:30:32 nsilaslin02 kernel: HighMem zone: 0 pages, LIFO batch:1
Oct 5 10:30:33 nsilaslin02 kernel: Processor #0 15:2 APIC version 20
Oct 5 10:30:33 nsilaslin02 kernel: Processor #1 15:2 APIC version 20
Oct 5 10:30:33 nsilaslin02 kernel: Enabling APIC mode: Flat. Using 1 I/O APICs
Oct 5 10:30:33 nsilaslin02 kernel: Built 1 zonelists
Oct 5 10:30:33 nsilaslin02 kernel: Kernel command line: auto BOOT_IMAGE=linux-nonfb ro root=301 noapic devfs=mount acpi=ht resume=/dev/hda5
Oct 5 10:30:33 nsilaslin02 kernel: PID hash table entries: 2048 (order 11: 16384 bytes)
Oct 5 10:30:33 nsilaslin02 kernel: Detected 2793.223 MHz processor.
Oct 5 10:30:33 nsilaslin02 kernel: Console: colour VGA+ 80x25
Oct 5 10:30:33 nsilaslin02 kernel: Checking if this processor honours the WP bit even in supervisor mode... Ok.
Oct 5 10:30:33 nsilaslin02 kernel: Calibrating delay loop... 5537.79 BogoMIPS
Oct 5 10:30:33 nsilaslin02 kernel: Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
Oct 5 10:30:33 nsilaslin02 kernel: Mount-cache hash table entries: 512 (order: 0, 4096 bytes)
Oct 5 10:30:33 nsilaslin02 kernel: POSIX conformance testing by UNIFIX
Oct 5 10:30:33 nsilaslin02 kernel: CPU0: Intel(R) Pentium(R) 4 CPU 2.80GHz stepping 09
Oct 5 10:30:33 nsilaslin02 kernel: per-CPU timeslice cutoff: 1462.56 usecs.
Oct 5 10:30:33 nsilaslin02 kernel: task migration cache decay timeout: 2 msecs.
Oct 5 10:30:33 nsilaslin02 kernel: enabled ExtINT on CPU#0
Oct 5 10:30:33 nsilaslin02 kernel: ESR value before enabling vector: 00000000
Oct 5 10:30:33 nsilaslin02 kernel: ESR value after enabling vector: 00000000
Oct 5 10:30:33 nsilaslin02 kernel: Booting processor 1/1 eip 3000
Oct 5 10:30:33 nsilaslin02 kernel: masked ExtINT on CPU#1
Oct 5 10:30:33 nsilaslin02 kernel: ESR value before enabling vector: 00000000
Oct 5 10:30:33 nsilaslin02 kernel: ESR value after enabling vector: 00000000
Oct 5 10:30:33 nsilaslin02 kernel: Calibrating delay loop... 5570.56 BogoMIPS
Oct 5 10:30:33 nsilaslin02 kernel: CPU1: Intel(R) Pentium(R) 4 CPU 2.80GHz stepping 09
Oct 5 10:30:33 nsilaslin02 kernel: cpu_sibling_map[0] = 1
Oct 5 10:30:33 nsilaslin02 kernel: cpu_sibling_map[1] = 0
Oct 5 10:30:33 nsilaslin02 kernel: Using local APIC timer interrupts.
Oct 5 10:30:33 nsilaslin02 kernel: calibrating APIC timer ...
Oct 5 10:30:33 nsilaslin02 kernel: ..... CPU clock speed is 2792.0645 MHz.
Oct 5 10:30:33 nsilaslin02 kernel: ..... host bus clock speed is 199.0474 MHz.
Oct 5 10:30:33 nsilaslin02 kernel: checking TSC synchronization across 2 CPUs: passed.
Oct 5 10:30:33 nsilaslin02 kernel: Starting migration thread for cpu 0
Oct 5 10:30:33 nsilaslin02 kernel: Starting migration thread for cpu 1
Oct 5 10:30:33 nsilaslin02 kernel: Brought up 1 CPUs
Oct 5 10:30:33 nsilaslin02 kernel: PCI: Probing PCI hardware
Oct 5 10:30:33 nsilaslin02 kernel: PCI: Probing PCI hardware (bus 00)
Oct 5 10:30:33 nsilaslin02 kernel: Transparent bridge - 0000:00:1e.0
Oct 5 10:30:33 nsilaslin02 kernel: PCI: IRQ 0 for device 0000:00:1f.1 doesn't match PIRQ mask - try pci=usepirqmask
Oct 5 10:30:33 nsilaslin02 kernel: pty: 1024 Unix98 ptys configured
Oct 5 10:30:33 nsilaslin02 kernel: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
Oct 5 10:30:33 nsilaslin02 kernel: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
Oct 5 10:30:33 nsilaslin02 kernel: RAMDISK driver initialized: 16 RAM disks of 32000K size 1024 blocksize
Oct 5 10:30:33 nsilaslin02 kernel: hda: WDC WD800LB-07DNA2, ATA DISK drive
Oct 5 10:30:33 nsilaslin02 kernel: Using anticipatory io scheduler
Oct 5 10:30:33 nsilaslin02 kernel: ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
Oct 5 10:30:33 nsilaslin02 kernel: hdc: LITE-ON COMBO LTC-48161H, ATAPI CD/DVD-ROM drive
Oct 5 10:30:33 nsilaslin02 kernel: ide1 at 0x170-0x177,0x376 on irq 15
Oct 5 10:30:33 nsilaslin02 kernel: hda: max request size: 1024KiB
Oct 5 10:30:33 nsilaslin02 kernel: VFS: Mounted root (ext2 filesystem).
Oct 5 10:30:33 nsilaslin02 kernel: PCI: cache line size of 128 is not supported by device 0000:00:1d.7
Oct 5 10:30:33 nsilaslin02 kernel: hdc: ATAPI 48X DVD-ROM CD-R/RW CD-MRW drive, 2048kB Cache, UDMA(33)
Oct 5 10:30:33 nsilaslin02 kernel: ide-floppy driver 0.99.newide
Oct 5 10:30:39 nsilaslin02 kernel: atkbd.c: Unknown key released (translated set 2, code 0x7a on isa0060/serio0).
Oct 5 10:30:39 nsilaslin02 kernel: atkbd.c: This is an XFree86 bug. It shouldn't access hardware directly.
Oct 5 10:30:39 nsilaslin02 kernel: atkbd.c: Unknown key released (translated set 2, code 0x7a on isa0060/serio0).
Oct 5 10:30:39 nsilaslin02 kernel: atkbd.c: This is an XFree86 bug. It shouldn't access hardware directly.
Oct 5 10:30:50 nsilaslin02 kernel: Neighbour table overflow.
Oct 5 10:30:50 nsilaslin02 last message repeated 9 times
Oct 5 10:30:55 nsilaslin02 kernel: printk: 24045 messages suppressed.
Oct 5 10:30:55 nsilaslin02 kernel: Neighbour table overflow.
Oct 5 10:31:00 nsilaslin02 kernel: printk: 24276 messages suppressed.
Oct 5 10:31:00 nsilaslin02 kernel: Neighbour table overflow.
Oct 5 10:36:06 nsilaslin02 kernel: printk: 16555 messages suppressed.
Oct 5 10:36:06 nsilaslin02 kernel: Neighbour table overflow.
Oct 5 10:36:06 nsilaslin02 last message repeated 9 times
Oct 5 10:36:11 nsilaslin02 kernel: printk: 24221 messages suppressed.
Oct 5 10:36:11 nsilaslin02 kernel: Neighbour table overflow.
Oct 5 10:36:16 nsilaslin02 kernel: printk: 24272 messages suppressed.
Oct 5 10:36:16 nsilaslin02 kernel: Neighbour table overflow.
Oct 5 10:46:22 nsilaslin02 kernel: printk: 15931 messages suppressed.
Oct 5 10:46:22 nsilaslin02 kernel: Neighbour table overflow.
Oct 5 10:46:22 nsilaslin02 last message repeated 9 times
Oct 5 10:46:27 nsilaslin02 kernel: printk: 24289 messages suppressed.
Oct 5 10:46:27 nsilaslin02 kernel: Neighbour table overflow.
Oct 5 10:46:32 nsilaslin02 kernel: printk: 21235 messages suppressed.
Oct 5 10:46:32 nsilaslin02 kernel: Neighbour table overflow.

Java programs are run by a virtual machine which is running in userland. They don't "mess" with the kernel.
OTOH, each userland program interacts with the kernel through system calls, signals, pageing activity, ...
My guess is that it's either broken hardware, or a fault in the linux kernel.
Is the crash reproducible? Does ist always crash with the same error message, at the same "eip" location?
If the crashes are sporadic and non deterministic, with different error messages each time, then I'd say it's
a hardware problem. Otherwise, it could be a linux kernel software problem.

Ni-DAQ single-point analog sample latency.

I am maybe in my own little world here in wanting to do software-triggered analog sampling and wanting to do it fast. Having bought a PCI-6014 which is capable of 4 microsecond analog sampling I found a simple AI_Read took 95usec. I was somewhat disappointed. Much reading of FAQs and other's postings here didn't help. I posted my own question and got little help.
Well, having spent days working out such problems as how to access hardware under windows I would just like to throw this to the NI world:
Digital in/out: was 6 usec. now 0.9usec.
Analog in: was 95usec. Now 19 if a channel/gain change is required. 6 usec if not.
To the hardware developers - lets have a cheer. The register-level programming is a bit con
voluted, but that comes with the territory when the triggering, etc, is so flexible.
To the software developers - boo, hiss. Wake up, get your act together. So far as programming the card is concerned I did exactly as described in the "E-Series register-level programming manual". The no-change-to-gain-channel case just does the last, trigger step.
Now, imagine what I could charge if I could make the latest nVidia or ATI video card go 10x faster. I suspect those guys know how to write drivers though.

Hi Michael,
There's no question that efficiencies can be exploited once we start using RLP. Configuring the hardware is definitely quicker using this approach. However, programming specific applications using RLP begins to be a headache once you leave the realm of the simple application.
Using the NI-DAQ driver on the other hand gives me a consistent, intuitive interface over almost all of their hardware products. I am also able to pick up LabVIEW, look at some example code and have an application up and running in less than a couple hours without ever programming data acquisition before. NI-DAQ also has an abstraction layer which offers programming benefits but will invariably add some delay to function calls.
It is also important to note that acquisition times are not lost because of the latency of the configuration calls. You will be able to acquire triggered and continuous data at hardware rates!! The only benefit that is lacking is if you want to start a software call to the card in 6us. But this seems to be a mute point since your software timing is OS dependent anyway. Why push a software call to be 6us when your are not sure when the OS will process your application's code.
The only time having a quick configuration would be a benefit is if you are constantly reconfiguring in a software loop. But then your are still restrained by OS timing so you will never have true deterministic results unless you go to an RT system.
The developers of the NI-DAQ driver have had to make many trade-offs when developing such a comprehensive and flexible driver and accommodating every scenario with every user is an impossibility. This particular instance happens to be one of them.
I would like it to be known though that I have been successful, with the NI-DAQ 7.0 driver, at acquiring continuous pattern input with the PCI-6534 card at 50ns resolutions (20MHz). Obviously, the driver has its benefits!!
Anyway, I appreciate the chance to discuss this type of situation.
Ron
Applications Engineer
National Instruments

Accessing hardware

Similar Messages

Maybe you are looking for