5142 rexplore
Hello
I want to acquire real data only using 5142 I have mention the path through which options I want to acquire the real data (attachment) include Real acq, real_frequency translation. What should be the options I have to set for this. The vi’s I attached here are
For real acquisition. But If u look at these they don’t set the acquisition type to real. Only complex data is acquired either I set it to complex or real.the Vi in which (Complex_bydefult) I do not set the data processing Mode or DDC option but it acquires same complex data as I acquired using (Real_Socalled). This means that either I set the data processing mode to real or not it(Real _Socalled) is acquiring complex data. Am I not setting the options correctly what I am missing. How do I set this complex interleaving or it is active by default when I acquire complex data only.
Someone respond to my 5142 channel queries about two channel acq saying
Technically you can do downconversion from ch 0 and ch 1 at the same time. However, you will only get real data (and not complex data) for each channel (I is ch 0 and Q is channel 1). Also, both channels will have to frequency translate from the same IF/center frequency. If you want to do this, then start from the baseband example and enable frequency translation (and set the center frequency). You will probably want to set the I and Q phase appropriately. 2 channel real I have attached will work how if channel 0, channel1 are acquiring both complex data also. I think if this is the case then there is something wrong……what will de the data flow in this case. active channelQ 1
Regards
Madd
Attachments:
5142_questions.zip 270 KB
Hi Madd,
The 5142 is capable of being used as a regular digitizer to acquire real data. You can also use the OSP in the following 4 ways:
Send one IF signal to CH 0 and perform quadrature downconversion on the signal (complex data is returned).
Send I and Q baseband signals to CH 0 and CH 1 and perform alias-protected decimation (complex data is returned).
Send a signal to CH 0 and perform alias-protected decimation (real data is returned)
Send a signal to CH 0 and perform real downconversion on the signal (real data is returned)
Which
of the above do you wish to implement? It is not completely clear to
me from your post, but if you want to do real downconversion (#4), then
you should start with the niScope EX OSP Downconversion.vi
example found in example finder under Hardware Input and Output
>> Modular Instruments >> NI-SCOPE >> Features.
-John
John Passiak
Similar Messages
-
How to know the capacity of Onboard memory of 5142 digitizer or any other digitizer
We have purchased couple of digitizers and AWGs for a particular project for our customer, my customer is asking us to show the onboard memory capacity. How can i show to them the capacity of the onboard memory of those card? We have purchased (5142,5622,5451,5442)
Hi Tejeswar,
I think you already figured this out, but just incase not, you could see the on board memory details in the hardware documentation(Start >> All Programs >> National Instruments >>NI-SCOPE>>Documentation>>Specification). -
KB2878635 / EventID 5142, 5120
Hi there,
We are running a 4 node Windows 2012 Core Hyper-V Cluster with CSVs (free online available w2k12 core) . Since wie tried to backup the VMs at Cluster level using the built-in Windows Backup we are facing the the EventIDs 5142 & 5120 causing downtimes
of several VMs due to temporary loss of connectivity to the CSVs.
KB2878635 describes the issue and Powershell (get-hotfix) tells that the hotfix has not been installed yet. Once we try to install it, the Setup Routine tells us that the hotfix is not applicable to the Computer. We checked the file Versions on the System
compared to the Versions mentioned in the KB - the KB contains newer Versions...
Any suggestions?
Cheerio
HolgerHi Holger,
" Most patches will be deployed in a .MSU format. To apply these under native Hyper-V/Server Core, run the following at a command-prompt: “WUSA patchname.MSU /QUIET”.
For details please refer to following link:
http://support.microsoft.com/kb/934307/en
Best Regards
Elton Ji
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place. -
Continuous, gap-free acquisition and processing with PCI-5142 and Labview
I am trying to continuously acquire data from a PCI-5142 in Labview 7.0. I have NI-SCOPE software installed, and right now, the best I can do is to acquire the data in chunks and then stitch the chunks together. However, this results in a short (approx. 10ms) amount of data loss between chunks. Since I am trying to do a cross-correlation of a function with my data, across chunks, I need the chunks to be contiguous. Additionally, I need to do this processing in real time so I cannot just stream to disk. What are my options?
Be sure that you are not stopping and re-starting the acquisition in between reads. Also, be sure you are not reading from a new record each time. There will be some time between separate acquisitions or separate records.
The best way to acquire continuously is to configure a single record, set the Reference Trigger to Software, and never send a Software Trigger. Set the Fetch Relative To attibute to Read Position. That way, every time you read data, it will start at the first unread data point. So you shouldn't see any gaps in the data (the chunks will be contiguous).
Please refer to two examples included in the NI-Scope driver:
- niScope EX Fetch Forever
- niScope EX Fetch In Chunks -
Trigger IF-RIO 5641R and Digitizer 5142
Hi,
I'm trying to generate a trigger from the FPGA of my IF-RIO to start the acquisition on a digitizer 5142. I want to do this with the PXI line, but I don't have the same line in the FPGA I/O (PXIe_Trig0...PXIe_Trig6) and in the Scope driver (RTSI0..RTSI6, PFI0..PFI2).
So is it possible to do this? If yes which line I have to use?
Thank you
Cordialement,
Simon D.
CLA | Certified LabVIEW Architect
CTA | Certified TestStand Architect
Solved!
Go to Solution.Thank you!
So if it's the same line, i think i have an other problem because it's not working
I tried this:
And for the FPGA side, I simulate my trigger:
I always have a timeout.
Maybe I forgot something?
Cordialement,
Simon D.
CLA | Certified LabVIEW Architect
CTA | Certified TestStand Architect -
Pxi 5142 triggered status attribute?
I have a PXI 5142, I am providing an input signal to one of the channels. This seems really simple and I can't seem to figure it out.
I am using labwindows. I want to just see if the digitizer was triggered. so I set up the system where the input should occur, initialize a session with digitizer with triggering etc, wait for some amount of time the triggering event should occur in, check to see if the triggered condition occured, true or false.
This is breaking my brain. i feel like this should be really easy, but I am struggling... any guidance would be appreciated.was able to get the desired effect by clearing out waveforms before check, setting up desired trigger settings, reading NISCOPE_ATTR_RECORDS_DONE attribute and make sure its 0, then start acquisition and allow time for system response that should trigger capture, then poll NISCOPE_ATTR_RECORDS_DONE again to see that a waveform was captured. if desired trigger event did not occur, NISCOPE_ATTR_RECORDS_DONE will return 0, otherwise it should have captured a waveform due to trigger
thanks. -
How to build FM radio receiver on PXI 5600 and PXI 5142 with help of labview
How to build FM radio receiver on PXI 5600 and PXI 5142 with help of labview?
PLZ TELL ME!
Solved!
Go to Solution.Dude,
Your way of asking questions sucks!
- Do not use such fonts!
- Try to find things out yourself first (apparently GovBob was able to find info, so could you)
- Have you asked GovBob if he likes it that you mail him for more questions?
You ask for a complete solution on a project YOU have to do. (you dont learn of it if you dont try it yourself first)
Hopefully you will ask questions in a less DEMANDING way next time.
Good luck with your project -
Changing the sampling rate of the Digitizer 5142
Dears,
Can i change the sampling rate of the digitizer 5142 ( for the 100MS/s can i change it to be smaller), can i change it at the spectrum mode and the IQ mode?Thank you for posting on the NI Discussion Forums. Since this question is related to your other forum post, let’s move the discussion over there to answer this question.
Chris_G
Sr Test Engineer
Medtronic, Inc. -
What is the start frequency for the digitizer 5142
Dears,
what is the start and stop frequency of the digitizer 5142 which is 100MS/s?Hello Ahmed.Abdulbaky,
When you say “start” and “stop” frequencies, I assume that you are inquiring about the maximum and minimum sampling rates of the 5142 digitizer. Is this correct? If so, then take a look at page 13 of the NI PXI/PCI-5142 Specifications, and you will see under Real-Time Sampling that the minimum and maximum sampling rates are 1.526 kS/s and 100 MS/s, respectively.
To answer your question from your other post, yes, you can change the sampling rate of the digitizer through the NI-SCOPE API. If you are using LabVIEW with the device, there is a VI called “niScope Configure Horizontal Timing.vi” that you can use to set the sampling rate, by wiring the desired sampling rate to the min sample rate input. This VI can be found in the functions palette under Measurement I/O » NI-SCOPE » niScope Sonfigure Horizontal Timing.vi.
Chris_G
Sr Test Engineer
Medtronic, Inc. -
Accurate frequency measurement using PXI 5142 Digitizer
I am Using PXI 5142 Digitizer to read the frequency of a 10 MHz atomic clock up to 8 decimal places. I am using single tone measurement block. But I can't get that accurate fix on the frequency because of the jitter.
Can someone help.
Thanks in Advance.Thanks For your reply; The device is connected to the digitizer through BNC connector.
Digitzer Scope Settings:
Samples/seconds --> 2G S/s
Record Length --> 800
Aqiusition mode ---> N Samples
Best Regards,
Helal
Attachments:
Block Diagram.JPG 117 KB
Front Panel.JPG 91 KB -
Hello
Greatefull for ur relpies NI. I have new question. what if i want to acquire a signal greater than 50Mhz using 5142. lets say i want to acquire a 70Mhz signal. Alisaing will be the result and my signals aliased componet will now lie at 30Mhz within the nyquist spectrum.And now i can fileter this signbal out using band pass filter and store it to my disk . Am i write ?. Also with the bandwidth of 40Mhz it will lie from 10Mhz to 50Mhz Yes or No?
Regards
MaddHello Madd,
This will depend on what you set your maximum frequency to. If you set the max frequency to -1 via the Config Chan Characteristics VI you will use the full 100 MS/s and the anti-aliasing filter will be disabled. In this instance you will see both the 70 MHz tone and the aliased 30 MHz tone +- your bandwidth in each case. If you enable the anti-aliasing filter via the same VI mentioned, 35 MHz for instance, you will not be able to take advantage of this phenomena without the effects of attenuation.
I did a quick experiment to illustrate this. I generated two tones, one 68 MHz tone at -5 dBm and one 72 MHz tone at 0 dBm and acquired at an NCO frequency of both 70 MHz and 30 MHz. My IQ rate was 40 MS/s.
Full BW
Left @ 30 MHz, Right @ 70 MHz
Anti-Alias Filter
Left @ 30 MHz, Right @ 70 MHz
Notice the >60 dB attenuation in the second case - this correlates to the frequency response of the anti-alias filter documented in the 5142 section of the NI Digitizers Help file.
Regards,
Message Edited by Speedy Badger on 03-11-2009 11:10 AM
Message Edited by Speedy Badger on 03-11-2009 11:12 AM
Chris Behnke
Sr. RF Engineer
High Frequency Measurements
Attachments:
[email protected] 13 KB
[email protected] 12 KB -
Hi,
I have 5661 (RF downconverter 5600 and digitizer 5142). I want to acquire the 15MHz IF signal of the downconverter through digitizer with DDC diabled(I don't want the IQ data centered around 0. I want to acquire the real 15MHz signal). For that i'll have to use the downconverter and digitizer seperately and have to configure 5600 in its downconverter only mode using niRFSA and 5142 using ni-scope. Is it possible to do that ? How can I pass the session handle from RFSA to ni-scope ?
thanxHi Sandee,
The IF output of the PXI-5600 is always 20 MHz wide. Normally, this gets filtered down to the requested Span in the NI-RFSA settings by the OSP on the PXI-5142. The 5142 digitizes the full 20 MHz IF and then digitally downconverts, filters, and decimates (to the requested IQ Rate) the signal.
In your case, the OSP is disabled, so you will need to do any filtering of the IF signal yourself in software.
The Span setting used in this example, which sets an NI-RFSA span while the NI-RFSA driver is operating the PXI-5600 in downconverter-only mode, is a little confusing in this case.The Span setting in this case is only used to set the tuning increment of the PXI-5600. The PXI-5600 tunes in either 1 MHz or 5 MHz steps, depending on the Span setting.
If the span is < 10 MHz, the PXI-5600 will tune in 5 MHz steps and have a narrower loop bandwidth, which slightly improves phase noise performance. This is the default setting of the attached example.
If the span is > 10 MHz, the PXI-5600 will tune in 1 MHz steps and
have a wider loop bandwidth, which slightly degrades phase noise
performance.
Regards,
Andy Hinde
RF Systems Engineer
National Instruments
Message Edited by Andy Hinde on 06-08-2010 09:07 AM -
Hi,
i have problem to start infinite acq in pxi5142 board
1) card is set to complex acq
2) ddc is enabled
3) ddc freq translation is enabled
4) I am trying to set cont. acq with this function
niScope_ConfigureTriggerSoftware (vi, 0.0, 0.0);
5) but during niScope_InitiateAcquisition I am getting
error that software trigger is not available... only: none, immediate, edge
6) what i need is to start infinite, continous acq,
niScope_SetAttributeViInt32(m_hVi, VI_NULL, NISCOPE_ATTR_FETCH_RELATIVE_TO, NISCOPE_VAL_READ_POINTER)
and fetch the data with
niScope_FetchComplex
What I can do ?
/rb
Solved!
Go to Solution.Are you setting the NISCOPE_ATTR_REF_TRIGGER_DETECTOR_LOCATION attribute to NISCOPE_VAL_DDC_OUTPUT?
Either set it to NISCOPE_VAL_ANALOG_DETECTION_CIRCUIT or leave it unset. -
Choosing a PXIe controller for streaming 200 MBps
Warning: This is a long post with several questions. My appologies in advance.
I am a physics professor at a small liberal-arts college, and will be replacing a very old multi-channel analyzer for doing basic gamma-ray spectroscopy. I would like to get a complete PXI system for maximum flexability. Hopefully this configuration could be used for a lot of other experiments such as pulsed NMR. But the most demanding role of the equipment would be gamma-ray spectroscopy, so I'll focus on that.
For this, I will need to be measuring either the maximum height of an electrical pulse, or (more often) the integrated voltage of the pulse. Pulses are typically 500 ns wide (at half maximum), and between roughly 2-200 mV without a preamp and up to 10V after the preamp. With the PXI-5122 I don't think I'll need a preamp (better timing information and simpler pedagogy). A 100 MHz sampling rate would give me at least 50 samples over the main portion of the peak, and about 300 samples over the entire range of integration. This should be plenty if not a bit of overkill.
My main questions are related to finding a long-term solution, and keeping up with the high data rate. I'm mostly convinced that I want the NI PXIe-5122 digitizer board, and the cheapest (8-slot) PXIe chassis. But I don't know what controller to use, or software environment (LabView / LabWindows / homebrew C++). This system will likely run about $15,000, which is more than my department's yearly budget. I have special funds to accomplish this now, but I want to minimize any future expenses in maintenance and updates.
The pulses to be measured arrive at random intervals, so performance will be best when I can still measure the heights or areas of pulses arriving in short succession. Obviously if two pulses overlap, I have to get clever and probably ignore them both. But I want to minimize dead time - the time after one pulse arrives that I become receptive to the next one. Dead times of less than 2 or 3 microseconds would be nice.
I can imagine two general approaches. One is to trigger on a pulse and have about a 3 us (or longer) readout window. There could be a little bit of pileup inspection to tell if I happen to be seeing the beginning of a second pulse after the one responsible for the trigger. Then I probably have to wait for some kind of re-arming time of the digitizer before it's ready to trigger on another pulse. Hopefully this time is short, 1 or 2 us. Is it? I don't see this in the spec sheet unless it's equivalent to minimum holdoff (2 us). For experiments with low rates of pulses, this seems like the easiest approach.
The other possibility is to stream data to the host computer, and somehow process the data as it rolls in. For high rate experiments, this would be a better mode of operation if the computer can keep up. For several minutes of continuous data collection, I cannot rely on buffering the entire sample in memory. I could stream to a RAID, but it's too expensive and I want to get feedback in real time as pulses are collected.
With this in mind, what would you recommend for a controller? The three choices that seem most reasonable to me are getting an embedded controller running Windows (or Linux?), an embedded controller running Labview real-time OS, or a fast interface card like the PCIe8371 and a powerful desktop PC. If all options are workable, which one would give me the lowest cost of upgrades over the next decade or so? I like the idea of a real-time embedded controller because I believe any run-of-the-mill desktop PC (whatever IT gives us) could connect and run the user interface including data display and higher-level analysis. Is that correct? But I am unsure of the life-span of an embedded controller, and am a little wary of the increased cost and need for periodic updates. How are real-time OS upgrades handled? Are they necessary? Real-time sounds nice and all that, but in reality I do not need to process the data stream in a real-time environment. It's just the computer and the digitizer board (not a control system), and both should buffer data very nicely. Is there a raw performance difference between the two OSes available for embedded controllers?
As for live processing of the streaming data, is this even possible? I'm not thinking very precisely about this (would really have to just try and find out), but it seems like it could possibly work on a a 2 GHz dual-core system. It would have to handle 200 MBps, but the data processing is extremely simple. For example one thread could mark the beginnings and ends of pulses, and do simple pile-up inspection. Another thread could integrate the pulses (no curve fitting or interpolation necessary, just simple addition) and store results in a table or list. Naievely, I'd have not quite 20 clock cycles per sample. It would be tight. Maybe just getting the data into the CPU cache is prohibitively slow. I'm not really even knowledgeable enough to make a reasonable guess. If it were possible, I would imagine that I would need to code it in LabWindows CVI and not LabView. That's not a big problem, but does anyone else have a good read on this? I have experience with C/C++, and some with LabView, but not LabWindows (yet).
What are my options if this system doesn't work out? The return policy is somewhat unfriendly, as 30 days may pass quickly as I struggle with the system while teaching full time. I'll have some student help and eventually a few long days over the summer. An alternative system could be built around XIA's Pixie-4 digitizer, which should mostly just work out of the box. I prefer somewhat the NI PXI-5122 solution because it's cheaper, better performance, has much more flexability, and suffers less from vendor lock-in. XIA's software is proprietary and very costly. If support ends or XIA gets bought out, I could be left with yet another legacy system. Bad.
The Pixie-4 does the peak detection and integration in hardware (FPGAs I think) so computing requirements are minimal. But again I prefer the flexibility of the NI digitizers. I would, however, be very interested if data from something as fast as the 5122 could be streamed into an FPGA-based DSP module. I haven't been able to find such a module yet. Any suggestions?
Otherwise, am I on the right track in general on this kind of system, or badly mistaken about some issue? Just want some reassurance before taking the plunge.drnikitin,
The reason you did not find the spec for the rearm time for
the 5133 is because the USB-5133 is not capable of multi-record acquisition. The rearm time is a spec for the reference
trigger, and that trigger is used when fetching the next record. So every time you want to do another fetch
you will have to stop and restart your task.
To grab a lot of data increase your minimum record size. Keep in mind that you have 4MB of on board
memory per channel.
Since you will only be able to fetch 1 record at a time,
there really isn’t a way to use streaming.
When you call fetch, it will transfer the amount of data you specify to
PC memory through the USB port (up to 12 MB/s for USB 2.0 – Idealy).
Topher C,
We do have a Digitizer that has onboard signal processing
(OSP), which would be quicker than performing post processing. It is
the NI 5142
and can perform the following signal
processing functions. It is
essentially a 5122 but with built in OSP.
It may be a little out of your price range, but it may be worth a
look.
For more
information on streaming take a look at these two links (if you havn’t
already).
High-Speed
Data Streaming: Programming and Benchmarks
Streaming Options for PXI
Express
When dealing with different LabVIEW versions
it is important to note that previous versions will be compatible with new
versions; such as going from 8.0 to 8.5.
Keep in mind that if you go too far back then LabVIEW may complain, but
you still may be able to run your VI. If
you have a newer version going to an older version then we do have options in
LabVIEW to save your VI for older versions.
It’s usually just 1 version back, but in LabVIEW 8.5 you can save for
LabVIEW 8.2 and 8.0.
ESD,
Here is the link
I was referring to earlier about DMA transfers. DMA is actually done every time you call a
fetch or read function in LabVIEW or CVI (through NI-SCOPE).
Topher C and ESD,
LabVIEW is a combination of a compiled
language and an interpreted language.
Whenever you make a change to the block diagram LabVIEW compiles
itself. This way when you hit run, it is
ready to execute. During execution LabVIEW
uses the run-time engine to reference shared libraries (such as dll’s). Take a look at this DevZone article about
how LabVIEW compiles it’s block diagram (user code).
I hope all of this information helps!
Ryan N
National Instruments
Application Engineer
ni.com/support -
[SOLVED] system very slow after upgrade
I did today pacman -Syu after some time. I have Dell D630 laptop, Core 2 Duo 2x1.8GHz, 2GB RAM, VGA: Intel X3100. Now the whole system is really slow. I mean REALLY slow. Even opening terminal (urxvt) takes time. Browsing is slow. Mplayer can not handle 720p .mkv playback enymore. cpufreq-info shows both cores uses max. 1.8 GHz frequency under load. I tried top/htop/atop/iotop/powertop but found no suspicious process eating resources. Messages from error.log:
Mar 29 23:16:05 tortuga kernel: ata4.01: failed to resume link (SControl 0)
Mar 29 23:16:05 tortuga kernel: vboxdrv: Warning: 2.6.31+ kernel detected. Most likely the hardware performance
Mar 29 23:16:05 tortuga kernel: vboxdrv: counter framework which can generate NMIs is active. You have to prevent
Mar 29 23:16:05 tortuga kernel: vboxdrv: the usage of hardware performance counters by
Mar 29 23:16:05 tortuga kernel: vboxdrv: echo 2 > /proc/sys/kernel/perf_counter_paranoid
I googled botth messages and as far as I can understand they are not source/symptom of my slowness.
If anybody have hint where to search, any advice will be really helpfull, because I am truly lost...
dmesg
# dmesg
Linux version 2.6.32-ARCH (thomas@evey) (gcc version 4.4.3 (GCC) ) #1 SMP PREEMPT Mon Mar 15 20:08:25 UTC 2010
KERNEL supported cpus:
Intel GenuineIntel
AMD AuthenticAMD
NSC Geode by NSC
Cyrix CyrixInstead
Centaur CentaurHauls
Transmeta GenuineTMx86
Transmeta TransmetaCPU
UMC UMC UMC UMC
BIOS-provided physical RAM map:
BIOS-e820: 0000000000000000 - 000000000009f000 (usable)
BIOS-e820: 000000000009f000 - 00000000000a0000 (reserved)
BIOS-e820: 0000000000100000 - 000000007f680400 (usable)
BIOS-e820: 000000007f680400 - 0000000080000000 (reserved)
BIOS-e820: 00000000f8000000 - 00000000fc000000 (reserved)
BIOS-e820: 00000000fec00000 - 00000000fec10000 (reserved)
BIOS-e820: 00000000fed18000 - 00000000fed1c000 (reserved)
BIOS-e820: 00000000fed20000 - 00000000fed90000 (reserved)
BIOS-e820: 00000000feda0000 - 00000000feda6000 (reserved)
BIOS-e820: 00000000fee00000 - 00000000fee10000 (reserved)
BIOS-e820: 00000000ffe00000 - 0000000100000000 (reserved)
DMI 2.4 present.
last_pfn = 0x7f680 max_arch_pfn = 0x100000
MTRR default type: uncachable
MTRR fixed ranges enabled:
00000-9FFFF write-back
A0000-BFFFF uncachable
C0000-CFFFF write-protect
D0000-EFFFF uncachable
F0000-FFFFF write-protect
MTRR variable ranges enabled:
0 base 000000000 mask F80000000 write-back
1 base 07F800000 mask FFF800000 uncachable
2 base 07F700000 mask FFFF00000 uncachable
3 disabled
4 disabled
5 disabled
6 disabled
7 disabled
x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
e820 update range: 0000000000002000 - 0000000000006000 (usable) ==> (reserved)
Scanning 1 areas for low memory corruption
modified physical RAM map:
modified: 0000000000000000 - 0000000000002000 (usable)
modified: 0000000000002000 - 0000000000006000 (reserved)
modified: 0000000000006000 - 000000000009f000 (usable)
modified: 000000000009f000 - 00000000000a0000 (reserved)
modified: 0000000000100000 - 000000007f680400 (usable)
modified: 000000007f680400 - 0000000080000000 (reserved)
modified: 00000000f8000000 - 00000000fc000000 (reserved)
modified: 00000000fec00000 - 00000000fec10000 (reserved)
modified: 00000000fed18000 - 00000000fed1c000 (reserved)
modified: 00000000fed20000 - 00000000fed90000 (reserved)
modified: 00000000feda0000 - 00000000feda6000 (reserved)
modified: 00000000fee00000 - 00000000fee10000 (reserved)
modified: 00000000ffe00000 - 0000000100000000 (reserved)
initial memory mapped : 0 - 01800000
init_memory_mapping: 0000000000000000-00000000377fe000
0000000000 - 0000400000 page 4k
0000400000 - 0037400000 page 2M
0037400000 - 00377fe000 page 4k
kernel direct mapping tables up to 377fe000 @ 7000-c000
RAMDISK: 7f363000 - 7f66fa7a
Allocated new RAMDISK: 00100000 - 0040ca7a
Move RAMDISK from 000000007f363000 - 000000007f66fa79 to 00100000 - 0040ca79
ACPI: RSDP 000fbb00 00024 (v02 DELL )
ACPI: XSDT 7f681e00 00064 (v01 DELL M08 27D70717 ASL 00000061)
ACPI: FACP 7f681c9c 000F4 (v04 DELL M08 27D70717 ASL 00000061)
ACPI: DSDT 7f682400 0613B (v02 INT430 SYSFexxx 00001001 INTL 20050624)
ACPI: FACS 7f690c00 00040
ACPI: HPET 7f681f00 00038 (v01 DELL M08 00000001 ASL 00000061)
ACPI: APIC 7f682000 00068 (v01 DELL M08 27D70717 ASL 00000047)
ACPI: ASF! 7f681c00 0007E (v32 DELL M08 27D70717 ASL 00000061)
ACPI: MCFG 7f681fc0 0003E (v16 DELL M08 27D70717 ASL 00000061)
ACPI: SLIC 7f68209c 00024 (v01 DELL M08 27D70717 ASL 00000061)
ACPI: TCPA 7f682300 00032 (v01 00000000 ASL 00000000)
ACPI: SSDT 7f680731 004CC (v01 PmRef CpuPm 00003000 INTL 20050624)
ACPI: Local APIC address 0xfee00000
1150MB HIGHMEM available.
887MB LOWMEM available.
mapped low ram: 0 - 377fe000
low ram: 0 - 377fe000
node 0 low ram: 00000000 - 377fe000
node 0 bootmap 00008000 - 0000ef00
(9 early reservations) ==> bootmem [0000000000 - 00377fe000]
#0 [0000000000 - 0000001000] BIOS data page ==> [0000000000 - 0000001000]
#1 [0000001000 - 0000002000] EX TRAMPOLINE ==> [0000001000 - 0000002000]
#2 [0000006000 - 0000007000] TRAMPOLINE ==> [0000006000 - 0000007000]
#3 [0001000000 - 000152f024] TEXT DATA BSS ==> [0001000000 - 000152f024]
#4 [000009f000 - 0000100000] BIOS reserved ==> [000009f000 - 0000100000]
#5 [0001530000 - 0001536188] BRK ==> [0001530000 - 0001536188]
#6 [0000007000 - 0000008000] PGTABLE ==> [0000007000 - 0000008000]
#7 [0000100000 - 000040ca7a] NEW RAMDISK ==> [0000100000 - 000040ca7a]
#8 [0000008000 - 000000f000] BOOTMAP ==> [0000008000 - 000000f000]
Zone PFN ranges:
DMA 0x00000000 -> 0x00001000
Normal 0x00001000 -> 0x000377fe
HighMem 0x000377fe -> 0x0007f680
Movable zone start PFN for each node
early_node_map[3] active PFN ranges
0: 0x00000000 -> 0x00000002
0: 0x00000006 -> 0x0000009f
0: 0x00000100 -> 0x0007f680
On node 0 totalpages: 521755
free_area_init_node: node 0, pgdat c13dbe60, node_mem_map c1538000
DMA zone: 32 pages used for memmap
DMA zone: 0 pages reserved
DMA zone: 3963 pages, LIFO batch:0
Normal zone: 1744 pages used for memmap
Normal zone: 221486 pages, LIFO batch:31
HighMem zone: 2302 pages used for memmap
HighMem zone: 292228 pages, LIFO batch:31
Using APIC driver default
ACPI: PM-Timer IO Port: 0x1008
ACPI: Local APIC address 0xfee00000
ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0])
IOAPIC[0]: apic_id 2, version 32, address 0xfec00000, GSI 0-23
ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
ACPI: IRQ0 used by override.
ACPI: IRQ2 used by override.
ACPI: IRQ9 used by override.
Enabling APIC mode: Flat. Using 1 I/O APICs
Using ACPI (MADT) for SMP configuration information
ACPI: HPET id: 0x8086a201 base: 0xfed00000
SMP: Allowing 2 CPUs, 0 hotplug CPUs
nr_irqs_gsi: 24
PM: Registered nosave memory: 0000000000002000 - 0000000000006000
PM: Registered nosave memory: 000000000009f000 - 00000000000a0000
PM: Registered nosave memory: 00000000000a0000 - 0000000000100000
Allocating PCI resources starting at 80000000 (gap: 80000000:78000000)
Booting paravirtualized kernel on bare hardware
NR_CPUS:8 nr_cpumask_bits:8 nr_cpu_ids:2 nr_node_ids:1
PERCPU: Embedded 14 pages/cpu @c2800000 s34680 r0 d22664 u2097152
pcpu-alloc: s34680 r0 d22664 u2097152 alloc=1*4194304
pcpu-alloc: [0] 0 1
Built 1 zonelists in Zone order, mobility grouping on. Total pages: 517677
Kernel command line: root=/dev/group1/arch ro
PID hash table entries: 4096 (order: 2, 16384 bytes)
Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Initializing CPU#0
Initializing HighMem for node 0 (000377fe:0007f680)
Memory: 2060220k/2087424k available (2797k kernel code, 25764k reserved, 1185k data, 412k init, 1178120k highmem)
virtual kernel memory layout:
fixmap : 0xfff1e000 - 0xfffff000 ( 900 kB)
pkmap : 0xff800000 - 0xffc00000 (4096 kB)
vmalloc : 0xf7ffe000 - 0xff7fe000 ( 120 MB)
lowmem : 0xc0000000 - 0xf77fe000 ( 887 MB)
.init : 0xc13e4000 - 0xc144b000 ( 412 kB)
.data : 0xc12bb55a - 0xc13e3a08 (1185 kB)
.text : 0xc1000000 - 0xc12bb55a (2797 kB)
Checking if this processor honours the WP bit even in supervisor mode...Ok.
SLUB: Genslabs=13, HWalign=64, Order=0-3, MinObjects=0, CPUs=2, Nodes=1
Hierarchical RCU implementation.
NR_IRQS:512
Extended CMOS year: 2000
Console: colour VGA+ 80x25
console [tty0] enabled
hpet clockevent registered
HPET: 3 timers in total, 0 timers will be used for per-cpu timer
Fast TSC calibration using PIT
Detected 1795.296 MHz processor.
Calibrating delay loop (skipped), value calculated using timer frequency.. 3592.20 BogoMIPS (lpj=5984320)
Security Framework initialized
Mount-cache hash table entries: 512
CPU: L1 I cache: 32K, L1 D cache: 32K
CPU: L2 cache: 2048K
CPU: Physical Processor ID: 0
CPU: Processor Core ID: 0
mce: CPU supports 6 MCE banks
CPU0: Thermal monitoring enabled (TM2)
using mwait in idle threads.
Performance Events: Core2 events, Intel PMU driver.
... version: 2
... bit width: 40
... generic registers: 2
... value mask: 000000ffffffffff
... max period: 000000007fffffff
... fixed-purpose events: 3
... event mask: 0000000700000003
Checking 'hlt' instruction... OK.
ACPI: Core revision 20090903
..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
CPU0: Intel(R) Core(TM)2 Duo CPU T7100 @ 1.80GHz stepping 0d
Booting processor 1 APIC 0x1 ip 0x6000
Initializing CPU#1
CPU: L1 I cache: 32K, L1 D cache: 32K
CPU: L2 cache: 2048K
CPU: Physical Processor ID: 0
CPU: Processor Core ID: 1
CPU1: Thermal monitoring enabled (TM2)
CPU1: Intel(R) Core(TM)2 Duo CPU T7100 @ 1.80GHz stepping 0d
checking TSC synchronization [CPU#0 -> CPU#1]: passed.
Brought up 2 CPUs
Total of 2 processors activated (7184.82 BogoMIPS).
CPU0 attaching sched-domain:
domain 0: span 0-1 level MC
groups: 0 1
CPU1 attaching sched-domain:
domain 0: span 0-1 level MC
groups: 1 0
NET: Registered protocol family 16
ACPI: bus type pci registered
PCI: MCFG configuration 0: base f8000000 segment 0 buses 0 - 63
PCI: MCFG area at f8000000 reserved in E820
PCI: Using MMCONFIG for extended config space
PCI: Using configuration type 1 for base access
bio: create slab <bio-0> at 0
ACPI: EC: Look up EC in DSDT
ACPI: SSDT 7f690c80 00043 (v01 LMPWR DELLLOM 00001001 INTL 20050624)
ACPI: Interpreter enabled
ACPI: (supports S0 S3 S4 S5)
ACPI: Using IOAPIC for interrupt routing
ACPI: ACPI Dock Station Driver: 3 docks/bays found
ACPI: PCI Root Bridge [PCI0] (0000:00)
pci 0000:00:02.0: reg 10 64bit mmio: [0xfea00000-0xfeafffff]
pci 0000:00:02.0: reg 18 64bit mmio pref: [0xe0000000-0xefffffff]
pci 0000:00:02.0: reg 20 io port: [0xefe8-0xefef]
pci 0000:00:02.1: reg 10 64bit mmio: [0xfeb00000-0xfebfffff]
pci 0000:00:1a.0: reg 20 io port: [0x6f20-0x6f3f]
pci 0000:00:1a.1: reg 20 io port: [0x6f00-0x6f1f]
pci 0000:00:1a.7: reg 10 32bit mmio: [0xfed1c400-0xfed1c7ff]
pci 0000:00:1a.7: PME# supported from D0 D3hot D3cold
pci 0000:00:1a.7: PME# disabled
pci 0000:00:1b.0: reg 10 64bit mmio: [0xfe9fc000-0xfe9fffff]
pci 0000:00:1b.0: PME# supported from D0 D3hot D3cold
pci 0000:00:1b.0: PME# disabled
pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
pci 0000:00:1c.0: PME# disabled
pci 0000:00:1c.1: PME# supported from D0 D3hot D3cold
pci 0000:00:1c.1: PME# disabled
pci 0000:00:1c.5: PME# supported from D0 D3hot D3cold
pci 0000:00:1c.5: PME# disabled
pci 0000:00:1d.0: reg 20 io port: [0x6f80-0x6f9f]
pci 0000:00:1d.1: reg 20 io port: [0x6f60-0x6f7f]
pci 0000:00:1d.2: reg 20 io port: [0x6f40-0x6f5f]
pci 0000:00:1d.7: reg 10 32bit mmio: [0xfed1c000-0xfed1c3ff]
pci 0000:00:1d.7: PME# supported from D0 D3hot D3cold
pci 0000:00:1d.7: PME# disabled
pci 0000:00:1f.0: quirk: region 1000-107f claimed by ICH6 ACPI/GPIO/TCO
pci 0000:00:1f.0: quirk: region 1080-10bf claimed by ICH6 GPIO
pci 0000:00:1f.0: ICH7 LPC Generic IO decode 1 PIO at 0900 (mask 007f)
pci 0000:00:1f.0: ICH7 LPC Generic IO decode 3 PIO at 0c80 (mask 003f)
pci 0000:00:1f.1: reg 10 io port: [0x1f0-0x1f7]
pci 0000:00:1f.1: reg 14 io port: [0x3f4-0x3f7]
pci 0000:00:1f.1: reg 18 io port: [0x170-0x177]
pci 0000:00:1f.1: reg 1c io port: [0x374-0x377]
pci 0000:00:1f.1: reg 20 io port: [0x6fa0-0x6faf]
pci 0000:00:1f.2: reg 10 io port: [0x6eb0-0x6eb7]
pci 0000:00:1f.2: reg 14 io port: [0x6eb8-0x6ebb]
pci 0000:00:1f.2: reg 18 io port: [0x6ec0-0x6ec7]
pci 0000:00:1f.2: reg 1c io port: [0x6ec8-0x6ecb]
pci 0000:00:1f.2: reg 20 io port: [0x6ee0-0x6eef]
pci 0000:00:1f.2: reg 24 io port: [0xeff0-0xefff]
pci 0000:00:1f.2: PME# supported from D3hot
pci 0000:00:1f.2: PME# disabled
pci 0000:00:1f.3: reg 10 32bit mmio: [0xfe9fbf00-0xfe9fbfff]
pci 0000:00:1f.3: reg 20 io port: [0x10c0-0x10df]
pci 0000:0c:00.0: reg 10 32bit mmio: [0xfe8ff000-0xfe8fffff]
pci 0000:0c:00.0: PME# supported from D0 D3hot D3cold
pci 0000:0c:00.0: PME# disabled
pci 0000:00:1c.1: bridge 32bit mmio: [0xfe800000-0xfe8fffff]
pci 0000:09:00.0: reg 10 64bit mmio: [0xfe7f0000-0xfe7fffff]
pci 0000:09:00.0: PME# supported from D3hot D3cold
pci 0000:09:00.0: PME# disabled
pci 0000:00:1c.5: bridge 32bit mmio: [0xfe700000-0xfe7fffff]
pci 0000:03:01.0: reg 10 32bit mmio: [0x000000-0x000fff]
pci 0000:03:01.0: supports D1 D2
pci 0000:03:01.0: PME# supported from D0 D1 D2 D3hot D3cold
pci 0000:03:01.0: PME# disabled
pci 0000:03:01.4: reg 10 32bit mmio: [0xfe6ff000-0xfe6fffff]
pci 0000:03:01.4: reg 14 32bit mmio: [0xfe6fe800-0xfe6fefff]
pci 0000:03:01.4: supports D1 D2
pci 0000:03:01.4: PME# supported from D0 D1 D2 D3hot D3cold
pci 0000:03:01.4: PME# disabled
pci 0000:00:1e.0: transparent bridge
pci 0000:00:1e.0: bridge 32bit mmio: [0xfe600000-0xfe6fffff]
pci_bus 0000:00: on NUMA node 0
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PCIE._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.RP01._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.RP02._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.RP06._PRT]
ACPI: PCI Interrupt Link [LNKA] (IRQs 9 10 *11)
ACPI: PCI Interrupt Link [LNKB] (IRQs 5 7) *10
ACPI: PCI Interrupt Link [LNKC] (IRQs 9 10 11) *0, disabled.
ACPI: PCI Interrupt Link [LNKD] (IRQs 5 7 9 10 11) *3
ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 9 *10 11 12 14 15)
ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 *9 10 11 12 14 15)
ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 *5 6 7 9 10 11 12 14 15)
ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 9 10 11 12 14 15) *0, disabled.
vgaarb: device added: PCI:0000:00:02.0,decodes=io+mem,owns=io+mem,locks=none
vgaarb: loaded
PCI: Using ACPI for IRQ routing
NetLabel: Initializing
NetLabel: domain hash size = 128
NetLabel: protocols = UNLABELED CIPSOv4
NetLabel: unlabeled traffic allowed by default
Switching to clocksource tsc
pnp: PnP ACPI init
ACPI: bus type pnp registered
pnp 00:0b: io resource (0x1000-0x1005) overlaps 0000:00:1f.0 BAR 13 (0x1000-0x107f), disabling
pnp 00:0b: io resource (0x1008-0x100f) overlaps 0000:00:1f.0 BAR 13 (0x1000-0x107f), disabling
pnp 00:0c: io resource (0x1006-0x1007) overlaps 0000:00:1f.0 BAR 13 (0x1000-0x107f), disabling
pnp 00:0c: io resource (0x100a-0x1059) overlaps 0000:00:1f.0 BAR 13 (0x1000-0x107f), disabling
pnp 00:0c: io resource (0x1060-0x107f) overlaps 0000:00:1f.0 BAR 13 (0x1000-0x107f), disabling
pnp 00:0c: io resource (0x1010-0x102f) overlaps 0000:00:1f.0 BAR 13 (0x1000-0x107f), disabling
pnp: PnP ACPI: found 14 devices
ACPI: ACPI bus type pnp unregistered
system 00:05: ioport range 0xc80-0xcaf has been reserved
system 00:05: ioport range 0xcc0-0xcff could not be reserved
system 00:08: iomem range 0xfed00000-0xfed003ff has been reserved
system 00:0a: ioport range 0xcb0-0xcbb has been reserved
system 00:0a: iomem range 0xfed40000-0xfed44fff has been reserved
system 00:0b: ioport range 0x900-0x97f has been reserved
system 00:0b: ioport range 0x4d0-0x4d1 has been reserved
system 00:0c: ioport range 0xf400-0xf4fe has been reserved
system 00:0c: ioport range 0x1080-0x10bf has been reserved
system 00:0c: ioport range 0x10c0-0x10df has been reserved
system 00:0c: ioport range 0x809-0x809 has been reserved
system 00:0d: iomem range 0x0-0x9efff could not be reserved
system 00:0d: iomem range 0x9f000-0x9ffff could not be reserved
system 00:0d: iomem range 0xc0000-0xcffff could not be reserved
system 00:0d: iomem range 0xe0000-0xfffff could not be reserved
system 00:0d: iomem range 0x100000-0x7f6803ff could not be reserved
system 00:0d: iomem range 0x7f680400-0x7f6fffff has been reserved
system 00:0d: iomem range 0x7f700000-0x7f7fffff has been reserved
system 00:0d: iomem range 0x7f700000-0x7fefffff could not be reserved
system 00:0d: iomem range 0xffe00000-0xffffffff has been reserved
system 00:0d: iomem range 0xffa00000-0xffbfffff has been reserved
system 00:0d: iomem range 0xfec00000-0xfec0ffff could not be reserved
system 00:0d: iomem range 0xfee00000-0xfee0ffff has been reserved
system 00:0d: iomem range 0xfed20000-0xfed3ffff has been reserved
system 00:0d: iomem range 0xfed45000-0xfed8ffff has been reserved
system 00:0d: iomem range 0xfeda0000-0xfeda3fff has been reserved
system 00:0d: iomem range 0xfeda4000-0xfeda4fff has been reserved
system 00:0d: iomem range 0xfeda5000-0xfeda5fff has been reserved
system 00:0d: iomem range 0xfeda6000-0xfeda6fff has been reserved
system 00:0d: iomem range 0xfed18000-0xfed1bfff has been reserved
system 00:0d: iomem range 0xf8000000-0xfbffffff has been reserved
pci 0000:00:1c.0: PCI bridge, secondary bus 0000:0b
pci 0000:00:1c.0: IO window: 0x2000-0x2fff
pci 0000:00:1c.0: MEM window: 0x84000000-0x841fffff
pci 0000:00:1c.0: PREFETCH window: 0x00000084200000-0x000000843fffff
pci 0000:00:1c.1: PCI bridge, secondary bus 0000:0c
pci 0000:00:1c.1: IO window: 0x3000-0x3fff
pci 0000:00:1c.1: MEM window: 0xfe800000-0xfe8fffff
pci 0000:00:1c.1: PREFETCH window: 0x00000084400000-0x000000845fffff
pci 0000:00:1c.5: PCI bridge, secondary bus 0000:09
pci 0000:00:1c.5: IO window: 0x4000-0x4fff
pci 0000:00:1c.5: MEM window: 0xfe700000-0xfe7fffff
pci 0000:00:1c.5: PREFETCH window: 0x00000084600000-0x000000847fffff
pci 0000:03:01.0: CardBus bridge, secondary bus 0000:04
pci 0000:03:01.0: IO window: 0x005000-0x0050ff
pci 0000:03:01.0: IO window: 0x005400-0x0054ff
pci 0000:03:01.0: PREFETCH window: 0x80000000-0x83ffffff
pci 0000:03:01.0: MEM window: 0x88000000-0x8bffffff
pci 0000:00:1e.0: PCI bridge, secondary bus 0000:03
pci 0000:00:1e.0: IO window: 0x5000-0x5fff
pci 0000:00:1e.0: MEM window: 0xfe600000-0xfe6fffff
pci 0000:00:1e.0: PREFETCH window: 0x80000000-0x83ffffff
pci 0000:00:1c.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
pci 0000:00:1c.0: setting latency timer to 64
pci 0000:00:1c.1: PCI INT B -> GSI 17 (level, low) -> IRQ 17
pci 0000:00:1c.1: setting latency timer to 64
pci 0000:00:1c.5: PCI INT B -> GSI 17 (level, low) -> IRQ 17
pci 0000:00:1c.5: setting latency timer to 64
pci 0000:00:1e.0: setting latency timer to 64
pci 0000:03:01.0: enabling device (0000 -> 0003)
pci 0000:03:01.0: PCI INT A -> GSI 19 (level, low) -> IRQ 19
pci_bus 0000:00: resource 0 io: [0x00-0xffff]
pci_bus 0000:00: resource 1 mem: [0x000000-0xffffffff]
pci_bus 0000:0b: resource 0 io: [0x2000-0x2fff]
pci_bus 0000:0b: resource 1 mem: [0x84000000-0x841fffff]
pci_bus 0000:0b: resource 2 pref mem [0x84200000-0x843fffff]
pci_bus 0000:0c: resource 0 io: [0x3000-0x3fff]
pci_bus 0000:0c: resource 1 mem: [0xfe800000-0xfe8fffff]
pci_bus 0000:0c: resource 2 pref mem [0x84400000-0x845fffff]
pci_bus 0000:09: resource 0 io: [0x4000-0x4fff]
pci_bus 0000:09: resource 1 mem: [0xfe700000-0xfe7fffff]
pci_bus 0000:09: resource 2 pref mem [0x84600000-0x847fffff]
pci_bus 0000:03: resource 0 io: [0x5000-0x5fff]
pci_bus 0000:03: resource 1 mem: [0xfe600000-0xfe6fffff]
pci_bus 0000:03: resource 2 pref mem [0x80000000-0x83ffffff]
pci_bus 0000:03: resource 3 io: [0x00-0xffff]
pci_bus 0000:03: resource 4 mem: [0x000000-0xffffffff]
pci_bus 0000:04: resource 0 io: [0x5000-0x50ff]
pci_bus 0000:04: resource 1 io: [0x5400-0x54ff]
pci_bus 0000:04: resource 2 pref mem [0x80000000-0x83ffffff]
pci_bus 0000:04: resource 3 mem: [0x88000000-0x8bffffff]
NET: Registered protocol family 2
IP route cache hash table entries: 32768 (order: 5, 131072 bytes)
TCP established hash table entries: 131072 (order: 8, 1048576 bytes)
TCP bind hash table entries: 65536 (order: 7, 524288 bytes)
TCP: Hash tables configured (established 131072 bind 65536)
TCP reno registered
NET: Registered protocol family 1
pci 0000:00:02.0: Boot video device
Unpacking initramfs...
Freeing initrd memory: 3122k freed
apm: BIOS not found.
Scanning for low memory corruption every 60 seconds
audit: initializing netlink socket (disabled)
type=2000 audit(1269905228.550:1): initialized
highmem bounce pool size: 64 pages
VFS: Disk quotas dquot_6.5.2
Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
msgmni has been set to 1730
alg: No test for stdrng (krng)
Block layer SCSI generic (bsg) driver version 0.4 loaded (major 254)
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered (default)
pcieport 0000:00:1c.0: irq 24 for MSI/MSI-X
pcieport 0000:00:1c.0: setting latency timer to 64
pcieport 0000:00:1c.1: irq 25 for MSI/MSI-X
pcieport 0000:00:1c.1: setting latency timer to 64
pcieport 0000:00:1c.5: irq 26 for MSI/MSI-X
pcieport 0000:00:1c.5: setting latency timer to 64
isapnp: Scanning for PnP cards...
isapnp: No Plug & Play device found
Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
00:09: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
input: Macintosh mouse button emulation as /devices/virtual/input/input0
PNP: PS/2 Controller [PNP0303:KBC,PNP0f13:PS2M] at 0x60,0x64 irq 1,12
serio: i8042 KBD port at 0x60,0x64 irq 1
serio: i8042 AUX port at 0x60,0x64 irq 12
mice: PS/2 mouse device common for all mice
cpuidle: using governor ladder
cpuidle: using governor menu
TCP cubic registered
NET: Registered protocol family 17
Using IPI No-Shortcut mode
PM: Resume from disk failed.
registered taskstats version 1
Initalizing network drop monitor service
Freeing unused kernel memory: 412k freed
input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input1
SCSI subsystem initialized
libata version 3.00 loaded.
ata_piix 0000:00:1f.1: version 2.13
ata_piix 0000:00:1f.1: PCI INT A -> GSI 16 (level, low) -> IRQ 16
ata_piix 0000:00:1f.1: setting latency timer to 64
scsi0 : ata_piix
scsi1 : ata_piix
ata1: PATA max UDMA/100 cmd 0x1f0 ctl 0x3f6 bmdma 0x6fa0 irq 14
ata2: PATA max UDMA/100 cmd 0x170 ctl 0x376 bmdma 0x6fa8 irq 15
ata_piix 0000:00:1f.2: PCI INT B -> GSI 17 (level, low) -> IRQ 17
ata_piix 0000:00:1f.2: MAP [ P0 P2 P1 P3 ]
ata2: port disabled. ignoring.
ata_piix 0000:00:1f.2: setting latency timer to 64
scsi2 : ata_piix
scsi3 : ata_piix
ata3: SATA max UDMA/133 cmd 0x6eb0 ctl 0x6eb8 bmdma 0x6ee0 irq 17
ata4: SATA max UDMA/133 cmd 0x6ec0 ctl 0x6ec8 bmdma 0x6ee8 irq 17
ata1.00: ATAPI: PBDS DVD+/-RW DS-8W1P, BD1B, max UDMA/33
ata1.00: configured for UDMA/33
scsi 0:0:0:0: CD-ROM PBDS DVD+-RW DS-8W1P BD1B PQ: 0 ANSI: 5
ata3.00: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata3.01: SATA link down (SStatus 0 SControl 300)
ata3.00: ATA-7: ST9160823AS, 3.ADC, max UDMA/133
ata3.00: 312581808 sectors, multi 8: LBA48 NCQ (depth 0/32)
ata3.00: configured for UDMA/133
scsi 2:0:0:0: Direct-Access ATA ST9160823AS 3.AD PQ: 0 ANSI: 5
ata4.01: failed to resume link (SControl 0)
ata4.00: SATA link down (SStatus 0 SControl 300)
ata4.01: SATA link down (SStatus 0 SControl 0)
sd 2:0:0:0: [sda] 312581808 512-byte logical blocks: (160 GB/149 GiB)
sd 2:0:0:0: [sda] Write Protect is off
sd 2:0:0:0: [sda] Mode Sense: 00 3a 00 00
sd 2:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sda: sda1 sda2 sda3
sd 2:0:0:0: [sda] Attached SCSI disk
sr0: scsi3-mmc drive: 24x/24x writer cd/rw xa/form2 cdda tray
Uniform CD-ROM driver Revision: 3.20
sr 0:0:0:0: Attached scsi CD-ROM sr0
device-mapper: uevent: version 1.0.3
device-mapper: ioctl: 4.15.0-ioctl (2009-04-01) initialised: [email protected]
padlock: VIA PadLock not detected.
EXT4-fs (dm-4): INFO: recovery required on readonly filesystem
EXT4-fs (dm-4): write access will be enabled during recovery
EXT4-fs (dm-4): orphan cleanup on readonly fs
EXT4-fs (dm-4): ext4_orphan_cleanup: deleting unreferenced inode 79470
EXT4-fs (dm-4): ext4_orphan_cleanup: deleting unreferenced inode 79469
EXT4-fs (dm-4): ext4_orphan_cleanup: deleting unreferenced inode 79468
EXT4-fs (dm-4): ext4_orphan_cleanup: deleting unreferenced inode 79467
EXT4-fs (dm-4): ext4_orphan_cleanup: deleting unreferenced inode 79466
EXT4-fs (dm-4): ext4_orphan_cleanup: deleting unreferenced inode 48873
EXT4-fs (dm-4): ext4_orphan_cleanup: deleting unreferenced inode 14902
EXT4-fs (dm-4): ext4_orphan_cleanup: deleting unreferenced inode 115506
EXT4-fs (dm-4): ext4_orphan_cleanup: deleting unreferenced inode 2598
EXT4-fs (dm-4): 9 orphan inodes deleted
EXT4-fs (dm-4): recovery complete
EXT4-fs (dm-4): mounted filesystem with ordered data mode
rtc_cmos 00:03: RTC can wake from S4
rtc_cmos 00:03: rtc core: registered rtc_cmos as rtc0
rtc0: alarms up to one month, y3k, 114 bytes nvram, hpet irqs
udev: starting version 151
fuse init (API version 7.13)
ACPI: SSDT 7f681138 00244 (v01 PmRef Cpu0Ist 00003000 INTL 20050624)
ACPI: SSDT 7f680bfd 004B6 (v01 PmRef Cpu0Cst 00003001 INTL 20050624)
Monitor-Mwait will be used to enter C-1 state
Monitor-Mwait will be used to enter C-2 state
Monitor-Mwait will be used to enter C-3 state
Marking TSC unstable due to TSC halts in idle
processor LNXCPU:00: registered as cooling_device0
ACPI: SSDT 7f68137c 000C4 (v01 PmRef Cpu1Ist 00003000 INTL 20050624)
ACPI: SSDT 7f6810b3 00085 (v01 PmRef Cpu1Cst 00003000 INTL 20050624)
Switching to clocksource hpet
processor LNXCPU:01: registered as cooling_device1
dcdbas dcdbas: Dell Systems Management Base Driver (version 5.6.0-3.2)
thermal LNXTHERM:01: registered as thermal_zone0
ACPI: Thermal Zone [THM] (95 C)
sr 0:0:0:0: Attached scsi generic sg0 type 5
sd 2:0:0:0: Attached scsi generic sg1 type 0
ACPI: AC Adapter [AC] (on-line)
input: Lid Switch as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input2
ACPI: Lid Switch [LID]
input: Power Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input3
ACPI: Power Button [PBTN]
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
ehci_hcd 0000:00:1a.7: PCI INT C -> GSI 22 (level, low) -> IRQ 22
ehci_hcd 0000:00:1a.7: setting latency timer to 64
ehci_hcd 0000:00:1a.7: EHCI Host Controller
ehci_hcd 0000:00:1a.7: new USB bus registered, assigned bus number 1
ehci_hcd 0000:00:1a.7: debug port 1
iTCO_vendor_support: vendor-support=0
ehci_hcd 0000:00:1a.7: cache line size of 32 is not supported
ehci_hcd 0000:00:1a.7: irq 22, io mem 0xfed1c400
Linux agpgart interface v0.103
ehci_hcd 0000:00:1a.7: USB 2.0 started, EHCI 1.00
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 4 ports detected
ehci_hcd 0000:00:1d.7: PCI INT A -> GSI 20 (level, low) -> IRQ 20
ehci_hcd 0000:00:1d.7: setting latency timer to 64
ehci_hcd 0000:00:1d.7: EHCI Host Controller
ehci_hcd 0000:00:1d.7: new USB bus registered, assigned bus number 2
ehci_hcd 0000:00:1d.7: debug port 1
ehci_hcd 0000:00:1d.7: cache line size of 32 is not supported
ehci_hcd 0000:00:1d.7: irq 20, io mem 0xfed1c000
ehci_hcd 0000:00:1d.7: USB 2.0 started, EHCI 1.00
usb usb2: configuration #1 chosen from 1 choice
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 6 ports detected
ACPI: Battery Slot [BAT0] (battery present)
input: Sleep Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input4
ACPI: Sleep Button [SBTN]
ACPI: WMI: Mapper loaded
ACPI: Battery Slot [BAT1] (battery absent)
tg3.c:v3.102 (September 1, 2009)
tg3 0000:09:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
tg3 0000:09:00.0: setting latency timer to 64
i801_smbus 0000:00:1f.3: PCI INT B -> GSI 17 (level, low) -> IRQ 17
iTCO_wdt: Intel TCO WatchDog Timer Driver v1.05
agpgart-intel 0000:00:00.0: Intel 965GM Chipset
agpgart-intel 0000:00:00.0: detected 7676K stolen memory
iTCO_wdt: Found a ICH8M TCO device (Version=2, TCOBASE=0x1060)
iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0)
agpgart-intel 0000:00:00.0: AGP aperture is 256M @ 0xe0000000
eth0: Tigon3 [partno(BCM95755m) rev a002] (PCI Express) MAC address 00:1c:23:1c:0d:5b
eth0: attached PHY is 5755 (10/100/1000Base-T Ethernet) (WireSpeed[1])
eth0: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[0] TSOcap[1]
eth0: dma_rwctrl[76180000] dma_mask[64-bit]
uhci_hcd: USB Universal Host Controller Interface driver
uhci_hcd 0000:00:1a.0: PCI INT A -> GSI 20 (level, low) -> IRQ 20
uhci_hcd 0000:00:1a.0: setting latency timer to 64
uhci_hcd 0000:00:1a.0: UHCI Host Controller
uhci_hcd 0000:00:1a.0: new USB bus registered, assigned bus number 3
uhci_hcd 0000:00:1a.0: irq 20, io base 0x00006f20
usb usb3: configuration #1 chosen from 1 choice
hub 3-0:1.0: USB hub found
hub 3-0:1.0: 2 ports detected
uhci_hcd 0000:00:1a.1: PCI INT B -> GSI 21 (level, low) -> IRQ 21
uhci_hcd 0000:00:1a.1: setting latency timer to 64
uhci_hcd 0000:00:1a.1: UHCI Host Controller
uhci_hcd 0000:00:1a.1: new USB bus registered, assigned bus number 4
uhci_hcd 0000:00:1a.1: irq 21, io base 0x00006f00
usb usb4: configuration #1 chosen from 1 choice
hub 4-0:1.0: USB hub found
hub 4-0:1.0: 2 ports detected
uhci_hcd 0000:00:1d.0: PCI INT A -> GSI 20 (level, low) -> IRQ 20
uhci_hcd 0000:00:1d.0: setting latency timer to 64
uhci_hcd 0000:00:1d.0: UHCI Host Controller
uhci_hcd 0000:00:1d.0: new USB bus registered, assigned bus number 5
uhci_hcd 0000:00:1d.0: irq 20, io base 0x00006f80
usb usb5: configuration #1 chosen from 1 choice
hub 5-0:1.0: USB hub found
hub 5-0:1.0: 2 ports detected
uhci_hcd 0000:00:1d.1: PCI INT B -> GSI 21 (level, low) -> IRQ 21
uhci_hcd 0000:00:1d.1: setting latency timer to 64
uhci_hcd 0000:00:1d.1: UHCI Host Controller
uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus number 6
uhci_hcd 0000:00:1d.1: irq 21, io base 0x00006f60
usb usb6: configuration #1 chosen from 1 choice
hub 6-0:1.0: USB hub found
hub 6-0:1.0: 2 ports detected
uhci_hcd 0000:00:1d.2: PCI INT C -> GSI 22 (level, low) -> IRQ 22
uhci_hcd 0000:00:1d.2: setting latency timer to 64
uhci_hcd 0000:00:1d.2: UHCI Host Controller
uhci_hcd 0000:00:1d.2: new USB bus registered, assigned bus number 7
uhci_hcd 0000:00:1d.2: irq 22, io base 0x00006f40
usb usb7: configuration #1 chosen from 1 choice
hub 7-0:1.0: USB hub found
hub 7-0:1.0: 2 ports detected
[drm] Initialized drm 1.1.0 20060810
cfg80211: Calling CRDA to update world regulatory domain
input: DualPoint Stick as /devices/platform/i8042/serio1/input/input5
input: AlpsPS/2 ALPS DualPoint TouchPad as /devices/platform/i8042/serio1/input/input6
yenta_cardbus 0000:03:01.0: CardBus bridge found [1028:01f9]
yenta_cardbus 0000:03:01.0: O2: res at 0x94/0xD4: 00/ea
yenta_cardbus 0000:03:01.0: O2: enabling read prefetch/write burst
i915 0000:00:02.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
i915 0000:00:02.0: setting latency timer to 64
i915 0000:00:02.0: irq 27 for MSI/MSI-X
[drm] set up 7M of stolen space
iwl3945: Intel(R) PRO/Wireless 3945ABG/BG Network Connection driver for Linux, 1.2.26ks
iwl3945: Copyright(c) 2003-2009 Intel Corporation
iwl3945 0000:0c:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
iwl3945 0000:0c:00.0: setting latency timer to 64
yenta_cardbus 0000:03:01.0: ISA IRQ mask 0x0cb8, PCI irq 19
yenta_cardbus 0000:03:01.0: Socket status: 30000006
pci_bus 0000:03: Raising subordinate bus# of parent bus (#03) from #04 to #07
yenta_cardbus 0000:03:01.0: pcmcia: parent PCI bridge I/O window: 0x5000 - 0x5fff
pcmcia_socket pcmcia_socket0: cs: IO port probe 0x5000-0x5fff: clean.
yenta_cardbus 0000:03:01.0: pcmcia: parent PCI bridge Memory window: 0xfe600000 - 0xfe6fffff
yenta_cardbus 0000:03:01.0: pcmcia: parent PCI bridge Memory window: 0x80000000 - 0x83ffffff
firewire_ohci 0000:03:01.4: PCI INT A -> GSI 19 (level, low) -> IRQ 19
iwl3945 0000:0c:00.0: Tunable channels: 13 802.11bg, 23 802.11a channels
iwl3945 0000:0c:00.0: Detected Intel Wireless WiFi Link 3945ABG
iwl3945 0000:0c:00.0: irq 28 for MSI/MSI-X
usb 5-1: new low speed USB device using uhci_hcd and address 2
firewire_ohci: Added fw-ohci device 0000:03:01.4, OHCI version 1.10
phy0: Selected rate control algorithm 'iwl-3945-rs'
usb 5-1: configuration #1 chosen from 1 choice
vboxdrv: Trying to deactivate the NMI watchdog permanently...
vboxdrv: Successfully done.
vboxdrv: Found 2 processor cores.
vboxdrv: fAsync=0 offMin=0x19e offMax=0x5df
vboxdrv: TSC mode is 'synchronous', kernel timer mode is 'normal'.
vboxdrv: Successfully loaded version 3.1.4_OSE (interface 0x00100001).
usb 7-1: new full speed USB device using uhci_hcd and address 2
usbcore: registered new interface driver hiddev
input: B16_b_02 USB-PS/2 Optical Mouse as /devices/pci0000:00/0000:00:1d.0/usb5/5-1/5-1:1.0/input/input7
generic-usb 0003:046D:C025.0001: input,hidraw0: USB HID v1.10 Mouse [B16_b_02 USB-PS/2 Optical Mouse] on usb-0000:00:1d.0-1/input0
usbcore: registered new interface driver usbhid
usbhid: v2.6:USB HID core driver
firewire_core: created device fw0: GUID 384fc00038f52070, S400
pcmcia_socket pcmcia_socket0: cs: IO port probe 0x100-0x3af: clean.
pcmcia_socket pcmcia_socket0: cs: IO port probe 0x3e0-0x4ff: clean.
pcmcia_socket pcmcia_socket0: cs: IO port probe 0x820-0x8ff: clean.
pcmcia_socket pcmcia_socket0: cs: IO port probe 0xc00-0xcf7: clean.
pcmcia_socket pcmcia_socket0: cs: IO port probe 0xa00-0xaff:
usb 7-1: configuration #1 chosen from 1 choice
clean.
hub 7-1:1.0: USB hub found
hub 7-1:1.0: 4 ports detected
usb 7-1.2: new full speed USB device using uhci_hcd and address 3
[drm] TV-16: set mode NTSC 480i 0
usb 7-1.2: configuration #1 chosen from 1 choice
[drm] LVDS-8: set mode 1280x800 1f
CPU0: Temperature above threshold, cpu clock throttled (total events = 1)
Disabling lock debugging due to kernel taint
CPU0: Temperature/speed normal
Console: switching to colour frame buffer device 160x50
fb0: inteldrmfb frame buffer device
registered panic notifier
input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/LNXVIDEO:01/input/input8
ACPI: Video Device [VID1] (multi-head: yes rom: no post: no)
ACPI Warning for \_SB_.PCI0.VID2._DOD: Return Package has no elements (empty) (20090903/nspredef-433)
input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/LNXVIDEO:02/input/input9
ACPI: Video Device [VID2] (multi-head: yes rom: no post: no)
[drm] Initialized i915 1.6.0 20080730 for 0000:00:02.0 on minor 0
HDA Intel 0000:00:1b.0: PCI INT A -> GSI 21 (level, low) -> IRQ 21
HDA Intel 0000:00:1b.0: setting latency timer to 64
input: HDA Digital PCBeep as /devices/pci0000:00/0000:00:1b.0/input/input10
input: HDA Intel Mic at Ext Left Jack as /devices/pci0000:00/0000:00:1b.0/sound/card0/input11
input: HDA Intel HP Out at Ext Left Jack as /devices/pci0000:00/0000:00:1b.0/sound/card0/input12
loop: module loaded
EXT4-fs (dm-2): mounted filesystem with ordered data mode
EXT4-fs (dm-3): mounted filesystem with ordered data mode
iwl3945 0000:0c:00.0: firmware: requesting iwlwifi-3945-2.ucode
iwl3945 0000:0c:00.0: loaded firmware version 15.32.2.9
Registered led device: iwl-phy0::radio
Registered led device: iwl-phy0::assoc
Registered led device: iwl-phy0::RX
Registered led device: iwl-phy0::TX
NET: Registered protocol family 10
lo: Disabled Privacy Extensions
ADDRCONF(NETDEV_UP): wlan0: link is not ready
tg3 0000:09:00.0: irq 29 for MSI/MSI-X
ADDRCONF(NETDEV_UP): eth0: link is not ready
tg3: eth0: Link is up at 100 Mbps, full duplex.
tg3: eth0: Flow control is on for TX and on for RX.
ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[drm] TV-16: set mode NTSC 480i 0
[drm] TV-16: set mode NTSC 480i 0
[drm] TV-16: set mode NTSC 480i 0
[drm] TV-16: set mode NTSC 480i 0
CE: hpet increasing min_delta_ns to 15000 nsec
eth0: no IPv6 routers present
CE: hpet increasing min_delta_ns to 22500 nsec
Registered led device: iwl-phy0::radio
Registered led device: iwl-phy0::assoc
Registered led device: iwl-phy0::RX
Registered led device: iwl-phy0::TX
ADDRCONF(NETDEV_UP): wlan0: link is not ready
tg3 0000:09:00.0: PME# enabled
tg3 0000:09:00.0: PME# disabled
tg3 0000:09:00.0: irq 29 for MSI/MSI-X
ADDRCONF(NETDEV_UP): eth0: link is not ready
tg3 0000:09:00.0: PME# enabled
tg3 0000:09:00.0: PME# disabled
tg3 0000:09:00.0: irq 29 for MSI/MSI-X
ADDRCONF(NETDEV_UP): eth0: link is not ready
tg3: eth0: Link is up at 100 Mbps, full duplex.
tg3: eth0: Flow control is on for TX and on for RX.
ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
eth0: no IPv6 routers present
usb 5-1: USB disconnect, address 2
usb 5-1: new low speed USB device using uhci_hcd and address 3
usb 5-1: configuration #1 chosen from 1 choice
input: B16_b_02 USB-PS/2 Optical Mouse as /devices/pci0000:00/0000:00:1d.0/usb5/5-1/5-1:1.0/input/input13
generic-usb 0003:046D:C025.0002: input,hidraw0: USB HID v1.10 Mouse [B16_b_02 USB-PS/2 Optical Mouse] on usb-0000:00:1d.0-1/input0
usb 5-1: USB disconnect, address 3
usb 5-1: new low speed USB device using uhci_hcd and address 4
usb 5-1: configuration #1 chosen from 1 choice
input: B16_b_02 USB-PS/2 Optical Mouse as /devices/pci0000:00/0000:00:1d.0/usb5/5-1/5-1:1.0/input/input14
generic-usb 0003:046D:C025.0003: input,hidraw0: USB HID v1.10 Mouse [B16_b_02 USB-PS/2 Optical Mouse] on usb-0000:00:1d.0-1/input0
Machine check events logged
CE: hpet increasing min_delta_ns to 33750 nsec
input input14: event field not found
input input14: event field not found
usb 5-1: USB disconnect, address 4
usb 5-1: new low speed USB device using uhci_hcd and address 5
usb 5-1: configuration #1 chosen from 1 choice
input: B16_b_02 USB-PS/2 Optical Mouse as /devices/pci0000:00/0000:00:1d.0/usb5/5-1/5-1:1.0/input/input15
generic-usb 0003:046D:C025.0004: input,hidraw0: USB HID v1.10 Mouse [B16_b_02 USB-PS/2 Optical Mouse] on usb-0000:00:1d.0-1/input0
ps -Af
# ps -Af
UID PID PPID C STIME TTY TIME CMD
root 1 0 0 Mar29 ? 00:00:00 init [5]
root 2 0 0 Mar29 ? 00:00:00 [kthreadd]
root 3 2 0 Mar29 ? 00:00:00 [migration/0]
root 4 2 0 Mar29 ? 00:00:00 [ksoftirqd/0]
root 5 2 0 Mar29 ? 00:00:00 [watchdog/0]
root 6 2 0 Mar29 ? 00:00:00 [migration/1]
root 7 2 0 Mar29 ? 00:00:00 [ksoftirqd/1]
root 8 2 0 Mar29 ? 00:00:00 [watchdog/1]
root 9 2 0 Mar29 ? 00:00:00 [events/0]
root 10 2 0 Mar29 ? 00:00:00 [events/1]
root 11 2 0 Mar29 ? 00:00:00 [khelper]
root 12 2 0 Mar29 ? 00:00:00 [async/mgr]
root 13 2 0 Mar29 ? 00:00:00 [pm]
root 14 2 0 Mar29 ? 00:00:00 [sync_supers]
root 15 2 0 Mar29 ? 00:00:00 [bdi-default]
root 16 2 0 Mar29 ? 00:00:00 [kblockd/0]
root 17 2 0 Mar29 ? 00:00:00 [kblockd/1]
root 18 2 0 Mar29 ? 00:00:00 [kacpid]
root 19 2 0 Mar29 ? 00:00:00 [kacpi_notify]
root 20 2 0 Mar29 ? 00:00:00 [kacpi_hotplug]
root 21 2 0 Mar29 ? 00:00:00 [kseriod]
root 24 2 0 Mar29 ? 00:00:00 [khungtaskd]
root 25 2 0 Mar29 ? 00:00:00 [kswapd0]
root 26 2 0 Mar29 ? 00:00:00 [ksmd]
root 27 2 0 Mar29 ? 00:00:00 [aio/0]
root 28 2 0 Mar29 ? 00:00:00 [aio/1]
root 29 2 0 Mar29 ? 00:00:00 [crypto/0]
root 30 2 0 Mar29 ? 00:00:00 [crypto/1]
root 732 2 0 Mar29 ? 00:00:01 [ata/0]
root 771 2 0 Mar29 ? 00:00:00 [ata/1]
root 800 2 0 Mar29 ? 00:00:00 [ata_aux]
root 836 2 0 Mar29 ? 00:00:02 [scsi_eh_0]
root 884 2 0 Mar29 ? 00:00:00 [scsi_eh_1]
root 930 2 0 Mar29 ? 00:00:00 [scsi_eh_2]
root 931 2 0 Mar29 ? 00:00:00 [scsi_eh_3]
root 968 2 0 Mar29 ? 00:00:00 [kstriped]
root 971 2 0 Mar29 ? 00:00:00 [kdmflush]
root 974 2 0 Mar29 ? 00:00:00 [kdmflush]
root 977 2 0 Mar29 ? 00:00:00 [kdmflush]
root 980 2 0 Mar29 ? 00:00:00 [kdmflush]
root 1014 2 0 Mar29 ? 00:00:00 [kdmflush]
root 1015 2 0 Mar29 ? 00:00:01 [kcryptd_io]
root 1016 2 2 Mar29 ? 00:01:10 [kcryptd]
root 1025 2 0 Mar29 ? 00:00:00 [jbd2/dm-4-8]
root 1026 2 0 Mar29 ? 00:00:00 [ext4-dio-unwrit]
root 1027 2 0 Mar29 ? 00:00:00 [ext4-dio-unwrit]
root 1060 1 0 Mar29 ? 00:00:00 /sbin/udevd --daemon
root 1591 2 0 Mar29 ? 00:00:01 [flush-254:4]
root 1747 2 0 Mar29 ? 00:00:00 [kondemand/0]
root 1795 2 0 Mar29 ? 00:00:00 [kondemand/1]
root 1920 2 0 Mar29 ? 00:00:00 [kconservative/0]
root 1961 2 0 Mar29 ? 00:00:00 [kconservative/1]
root 2168 2 0 Mar29 ? 00:00:00 [kpsmoused]
root 2563 2 0 Mar29 ? 00:00:00 [ksuspend_usbd]
root 2591 2 0 Mar29 ? 00:00:00 [khubd]
root 2961 2 0 Mar29 ? 00:00:00 [i915/0]
root 2962 2 0 Mar29 ? 00:00:00 [i915/1]
root 2974 2 0 Mar29 ? 00:00:00 [pccardd]
root 2996 2 0 Mar29 ? 00:00:00 [iwl3945]
root 3004 2 0 Mar29 ? 00:00:01 [phy0]
root 3073 2 0 Mar29 ? 00:00:00 [usbhid_resumer]
root 3336 2 0 Mar29 ? 00:00:00 [hd-audio0]
root 4143 2 0 Mar29 ? 00:00:00 [kdmflush]
root 4144 2 0 Mar29 ? 00:00:00 [kcryptd_io]
root 4145 2 0 Mar29 ? 00:00:00 [kcryptd]
root 4170 2 0 Mar29 ? 00:00:00 [jbd2/dm-2-8]
root 4171 2 0 Mar29 ? 00:00:00 [ext4-dio-unwrit]
root 4172 2 0 Mar29 ? 00:00:00 [ext4-dio-unwrit]
root 4173 2 0 Mar29 ? 00:00:00 [jbd2/dm-3-8]
root 4174 2 0 Mar29 ? 00:00:00 [ext4-dio-unwrit]
root 4175 2 0 Mar29 ? 00:00:00 [ext4-dio-unwrit]
root 4180 1 0 Mar29 ? 00:00:00 /sbin/mount.ntfs-3g /dev/sda1 /mnt/win -o rw,noexec,nosuid,nodev,users,uid=1001,gid=100,fmask=0113,dmask=000
root 4448 1 0 Mar29 ? 00:00:00 supervising syslog-ng
root 4449 4448 0 Mar29 ? 00:00:00 /usr/sbin/syslog-ng
root 4458 1 0 Mar29 ? 00:00:00 /usr/sbin/acpid
dbus 4472 1 1 Mar29 ? 00:00:27 /usr/bin/dbus-daemon --system
hal 4475 1 0 Mar29 ? 00:00:04 /usr/sbin/hald
root 4476 4475 0 Mar29 ? 00:00:00 hald-runner
root 4504 4476 0 Mar29 ? 00:00:00 hald-addon-input: Listening on /dev/input/event4 /dev/input/event3 /dev/input/event9 /dev/input/event8 /dev/
root 4508 4476 0 Mar29 ? 00:00:00 /usr/lib/hal/hald-addon-rfkill-killswitch
root 4520 4476 0 Mar29 ? 00:00:03 hald-addon-storage: polling /dev/sr0 (every 2 sec)
root 4521 4476 0 Mar29 ? 00:00:00 /usr/lib/hal/hald-addon-cpufreq
hal 4522 4476 0 Mar29 ? 00:00:00 hald-addon-acpi: listening on acpid socket /var/run/acpid.socket
root 4851 1 0 Mar29 ? 00:00:00 /usr/sbin/crond -S -l info
root 4863 1 1 Mar29 ? 00:00:37 /usr/bin/python -O /usr/share/wicd/daemon/wicd-daemon.py
ntp 4877 1 0 Mar29 ? 00:00:00 /usr/sbin/ntpd -s
root 4894 4863 0 Mar29 ? 00:00:25 /usr/bin/python -O /usr/share/wicd/daemon/monitor.py
mpd 4908 1 0 Mar29 ? 00:00:00 /usr/bin/mpd /etc/mpd.conf
root 4916 1 0 Mar29 ? 00:00:00 truecrypt -t -k /etc/dropboxkey --protect-hidden=no --password= --fs-options=umask=0002,uid=dropbox,gid=drop
root 4918 1 0 Mar29 ? 00:00:00 truecrypt -t -k /etc/dropboxkey --protect-hidden=no --password= --fs-options=umask=0002,uid=dropbox,gid=drop
root 4925 2 0 Mar29 ? 00:00:00 [loop0]
root 4928 2 0 Mar29 ? 00:00:00 [kdmflush]
root 4929 2 0 Mar29 ? 00:00:00 [kcryptd_io]
root 4930 2 0 Mar29 ? 00:00:00 [kcryptd]
root 4947 1 0 Mar29 tty1 00:00:00 /sbin/agetty 38400 tty1 linux
root 4948 1 0 Mar29 tty2 00:00:00 /sbin/agetty 38400 tty2 linux
root 4949 1 0 Mar29 tty3 00:00:00 /sbin/agetty 38400 tty3 linux
root 4950 1 0 Mar29 tty6 00:00:00 /bin/login -f
zed 4951 4950 0 Mar29 tty6 00:00:00 -bash
zed 4993 4951 0 Mar29 tty6 00:00:00 /bin/sh /usr/bin/startx
zed 5010 4993 0 Mar29 tty6 00:00:00 xinit /home/zed/.xinitrc -- /etc/X11/xinit/xserverrc :0 -auth /tmp/serverauth.LXTS3D7lp0
root 5011 5010 10 Mar29 tty4 00:04:27 /usr/bin/X -nolisten tcp
zed 5020 5010 0 Mar29 tty6 00:00:00 ck-launch-session openbox-session
root 5022 1 0 Mar29 ? 00:00:00 /usr/sbin/console-kit-daemon --no-daemon
zed 5095 5020 0 Mar29 tty6 00:00:03 /usr/bin/openbox
zed 5099 5095 0 Mar29 tty6 00:00:00 gnome-session
root 5106 1 0 Mar29 ? 00:00:00 /usr/sbin/ntpd -s
zed 5109 1 0 Mar29 ? 00:00:00 /usr/bin/ssh-agent
zed 5113 1 0 Mar29 tty6 00:00:00 dbus-launch --exit-with-session gnome-session
zed 5114 1 0 Mar29 ? 00:00:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session
root 5118 1 0 Mar29 ? 00:00:00 /usr/lib/DeviceKit/devkit-power-daemon
zed 5122 1 0 Mar29 ? 00:00:00 /usr/lib/GConf/gconfd-2
zed 5140 1 0 Mar29 tty6 00:00:00 gnome-keyring-daemon --start
zed 5142 5099 0 Mar29 tty6 00:00:06 gnome-panel
zed 5152 1 0 Mar29 ? 00:00:00 /usr/lib/gvfs/gvfsd
zed 5157 1 0 Mar29 ? 00:00:00 /usr/lib/gvfs//gvfs-fuse-daemon /home/zed/.gvfs
zed 5161 5099 0 Mar29 tty6 00:00:00 /usr/lib/gnome-disk-utility/gdu-notification-daemon
zed 5162 5099 0 Mar29 tty6 00:00:08 /usr/bin/python -O /usr/share/wicd/gtk/wicd-client.py
zed 5163 5099 0 Mar29 tty6 00:00:00 /usr/lib/polkit-gnome/polkit-gnome-authentication-agent-1
zed 5165 1 0 Mar29 ? 00:00:00 /usr/lib/bonobo/bonobo-activation-server --ac-activate --ior-output-fd=18
root 5167 1 0 Mar29 ? 00:00:00 /usr/lib/polkit-1/polkitd
root 5170 1 0 Mar29 ? 00:00:00 /usr/lib/DeviceKit/devkit-disks-daemon
root 5171 5170 0 Mar29 ? 00:00:02 devkit-disks-daemon: polling /dev/sr0
zed 5188 1 0 Mar29 ? 00:00:01 /usr/lib/gnome-applets/mixer_applet2 --oaf-activate-iid=OAFIID:GNOME_MixerApplet_Factory --oaf-ior-fd=18
zed 5190 1 0 Mar29 ? 00:00:00 /usr/lib/gnome-panel/notification-area-applet --oaf-activate-iid=OAFIID:GNOME_NotificationAreaApplet_Factory
zed 5192 1 0 Mar29 ? 00:00:00 /usr/lib/gnome-applets/battstat-applet-2 --oaf-activate-iid=OAFIID:GNOME_BattstatApplet_Factory --oaf-ior-fd
zed 5200 1 0 Mar29 ? 00:00:18 /usr/lib/gnome-panel/wnck-applet --oaf-activate-iid=OAFIID:GNOME_Wncklet_Factory --oaf-ior-fd=19
zed 5202 1 0 Mar29 ? 00:00:00 /usr/lib/gvfs/gvfs-gdu-volume-monitor
zed 5208 1 0 Mar29 ? 00:00:00 /usr/lib/gvfs/gvfs-gphoto2-volume-monitor
zed 5215 1 0 Mar29 ? 00:00:03 python /usr/lib/hamster-applet/hamster-applet --oaf-activate-iid=OAFIID:Hamster_Applet_Factory --oaf-ior-fd=
zed 5218 1 0 Mar29 ? 00:00:01 /usr/lib/gnome-panel/clock-applet --oaf-activate-iid=OAFIID:GNOME_ClockApplet_Factory --oaf-ior-fd=32
zed 5236 1 0 Mar29 ? 00:00:00 /usr/lib/evolution-data-server-1.2/evolution-data-server-2.28 --oaf-activate-iid=OAFIID:GNOME_Evolution_Data
root 5257 4476 0 Mar29 ? 00:00:00 /usr/lib/hal/hald-addon-leds
root 5270 4863 0 Mar29 ? 00:00:00 [dhcpcd] <defunct>
root 5291 1 0 Mar29 ? 00:00:00 /sbin/dhcpcd eth0 -h tortuga
zed 5295 5095 0 Mar29 tty6 00:00:02 urxvt -fn -*-terminus-medium-*-*-*-16-*-*-*-*-*-iso8859-2 -e sudo su -
root 5297 5295 0 Mar29 pts/0 00:00:00 su -
root 5299 5297 0 Mar29 pts/0 00:00:06 -bash
zed 5364 5095 16 Mar29 tty6 00:07:00 /usr/lib/chromium/chromium
zed 5365 5364 0 Mar29 tty6 00:00:18 /usr/lib/chromium/chromium
zed 5366 5364 0 Mar29 tty6 00:00:00 /usr/lib/chromium/chromium --type=zygote
zed 5390 5366 0 Mar29 tty6 00:00:03 /usr/lib/chromium/chromium --type=extension --lang=en-US --force-fieldtest=DnsImpact/_default_enabled_prefet
zed 5395 5366 0 Mar29 tty6 00:00:04 /usr/lib/chromium/chromium --type=extension --lang=en-US --force-fieldtest=DnsImpact/_default_enabled_prefet
zed 5406 5366 0 Mar29 tty6 00:00:06 /usr/lib/chromium/chromium --type=extension --lang=en-US --force-fieldtest=DnsImpact/_default_enabled_prefet
zed 5411 5366 0 Mar29 tty6 00:00:04 /usr/lib/chromium/chromium --type=extension --lang=en-US --force-fieldtest=DnsImpact/_default_enabled_prefet
zed 5479 5366 7 Mar29 tty6 00:03:10 /usr/lib/chromium/chromium --type=renderer --lang=en-US --force-fieldtest=CacheSize/CacheSizeGroup_3/DnsImpa
dropbox 5492 1 0 Mar29 ? 00:00:10 /home/dropbox/.dropbox-dist/dropbox
zed 5543 1 0 Mar29 ? 00:00:00 kdeinit4: kdeinit4 Running...
zed 5545 5543 0 Mar29 ? 00:00:00 kdeinit4: klauncher [kdeinit] --fd=8
zed 5548 1 0 Mar29 ? 00:00:02 kdeinit4: kded4 [kdeinit]
zed 5562 5543 0 Mar29 ? 00:00:00 kdeinit4: kio_file [kdeinit] file local:/tmp
zed 5567 1 0 Mar29 ? 00:00:01 /usr/bin/knotify4
root 5572 1060 0 Mar29 ? 00:00:00 /sbin/udevd --daemon
zed 5717 1 0 Mar29 ? 00:00:00 /usr/lib/gamin/gam_server
zed 6126 5366 2 Mar29 tty6 00:00:28 /usr/lib/chromium/chromium --type=extension --lang=en-US --force-fieldtest=CacheSize/CacheSizeGroup_3/DnsImp
root 6459 1 0 Mar29 ? 00:00:00 /usr/lib/sa/sadc -F -L -S DISK 600 6 -
root 6518 1060 0 00:01 ? 00:00:00 /sbin/udevd --daemon
root 6804 2 0 00:10 ? 00:00:00 [flush-254:6]
root 6807 5299 0 00:10 pts/0 00:00:00 ps -Af
Edit: typo
Edit2: I found the source of slowness - removing vboxdrv module restores system performance. How to get VirtualBox working I will try to solve somewhere else.
Last edited by stabele (2010-03-30 20:40:52)sand_man wrote:X is running at 25% cpu on average
Your's and mine problems are probably not connected, I had low CPU utilization from all sources (including X), but system was dead slow anyway.
Maybe you are looking for
-
Screen Blanks (ACPI) on VivoBook after upgrade
When I boot normally, I get to select my GRUB option, type my password for my encrypted partition, and then then screen goes blank and stays blank. I have found that if I plug in a VGA cable the monitor will show a prompt to login, and I can start X
-
Macbook display shows black and white lines when fullscreen
If i leave my Macbook on for a while without shutting down and then I view a photo or movie (in player or safari) fullscreen the screen shows just black and white lines. Sort of like bad tv reception. It has happened a few times and a reboot has fixe
-
Hierarchy node variable - successor node data not displayed
Hello, I have a query with a hierarchy in the rows section. This hierarchy is restricted by a hierarchy node variable with the following settings: variable type hierarchy node; customer exit; single value; mandatory; not ready for input; cannot b
-
Mavericks upgrade - lost draft emails
I've just upgraded to Mavericks and found that almost all the emails in my draft folder have disappeared. Some of them where very important so I'm hoping someone can advise if there is a way to get them back? Any help much appreciated! Emma
-
Process order - material component deleted
Hi, I would like to know where can I check if a material component has been deleted in a created process order. Would there be any history for this?