Frequency Division on 6602

CVI - I am using one of the counter outputs at 2000hZ as the source of another counter and wish to divide by some number. There are some examples but not for TIO. I have tried the FSK application but it always seems to divide by 5, I have also tried to setup the output with the divide by number but that does not seem to work as well. Any suggestions?
Attachments:
tmr_question.c ‏4 KB

Hello;
There aren't examples showing how to do that for TIO boards, however, you can use one of the examples for STC, and replace the function calls that are not supported by TIO devices by the ones that are supported.
You can find a list of all functions that are supported by each device in the NI-DAQ on line help. To find that list, open the NI-DAQ on line help,maximize the option "NI-DAQ functions" on the left hand side, and choose the link "Listed by Hardware Product".
Hope this helps.
Filipe A.
Applications Engineer
National Instruments

Similar Messages

  • Any ideas on how to use a 6602 to do frequency division?

    Uisng traditional DAQ.
    The 6602 user manual says it can do frequency division but I can not find an shipping example for this operation.
    In the end I want to be able to use the 6602 to handle the interface to a quadrature encoder.
    I want the 6602 to generate a sample pulse I can use for other DAQ work.
    I would like to get one pulse for both transitions of both the A and B signals, or otherwise stated;
    A pulse when
    A goes high
    B goes high
    A goes low
    B goes low
    I was thinking if I could configure a counter (or group) to operate as a frequency divider and use each of the encoders as a clock signal AND just do a divide by "1" I would have what I was after.
    Big Picture (incase it makes a difference)
    A quadrature encoder is coupled to a resolver I am testing. I need to corelate the angular displacement with the measurement from the resolver. While the shaft of the encoder and resolver are spinning, I want the encoder to clock the analog input samples.
    Thank you for reading,
    Ben
    Ben Rayner
    I am currently active on.. MainStream Preppers
    Rayner's Ridge is under construction

    Ben,
    First the executive summary: Sorry, No Can Do.
    You won't be able to generate a sampling clock pulse on the transition to each of the 4 quadrature states.   Here's a thread I was involved in where a similar question was asked.   If you need to correlate in exactly that manner, you may want to pick up a quadrature decoder chip such as the 7084.  It'll generate a "pulse" whose width is controlled by selection of an RC time constant during circuit build.  I put "pulse" in quotes because it isn't truly a TTL signal due to the long transition time.  I would recommend that you plan on adding a Schmitt trigger to square it up, perhaps another to re-invert it back to original polarity.
    However, all that being said, you may be better off using an internal sampling clock to drive analog and encoder position acquisition anyway.  On many encoders I've used, the transitions are NOT perfect 1/4 divisions of the cycle.  You can sometimes see this on the spec sheets where the A to B relative phase is given as, say, 90 +/- 15 degrees.  There will also be a tolerance on the phasing of A's rising and falling edges, maybe 180 +/- 10 degrees (it's often a little tighter than the A to B phasing).
    In practice, I've typically found that these deviations tend to be systematic rather than random.  Of the company's 1000 similar encoders, the phase stays within the range 90 +/- 15.  With my 1 instance, the phase may be 84 +/-3 around a full rev of the encoder.  The point is that if you generate pulses with the quadrature transitions, the samples still won't *really* be equally-spaced in position.  They'll just think they are.
    I'd suggest at least considering high-speed sampling with an internal clock that's shared by both tasks.  Then do a little bit of curve-fitting / interpolation to the data when you need to derive more precision.
    Re: frequency division.  You have to select a specific edge (either rising-only or falling-only) as the active edge.   Your counter will then ignore the other type of edge.  Also, you'll need to specify the # of edges each for the idle and pulse states.  These must each be >= 2.  So you can't divide by 1 - the best* you can do is to divide by 4.  (*Technically, you could sort-of divide by 2 if you configure the counter to pulse rather than toggle its output.  However you can't control the pulse width, and as I recall it's fixed at 50 nanoseconds.)  Write back if you'd like to see an example.
    -Kevin P.

  • How to do frequency division to a external signal use the api with vc

    i use the api and vc do frequency division.
    and i choose the function DAQmxCreateCOPulseChanTicks
    the problem is the parameter of sourceTermianl in DAQmxCreateCOPulseChanTicks
    i just do not how to use it, please help me ,thanks

        I can`t see your VI cause i've a lower version. I hope this VI to do what you want. 
    But now i have one question: Somebody knows why i get this message when i enable the disable diagram of the this vi? The message is attached, version is 8.0, winxp.
    Paul
    Mechatronic engineer
    Lima-Perú
    Attachments:
    FOURIER_TIME_SCALING.vi ‏25 KB
    msg.JPG ‏31 KB

  • Quadrature encoder frequency division dotNet Net VB C#

    Hello,
    following a long search on this forum, I have decided to start this thread for dotNet developper.
    I have a PCI-6602 with a quadrature encoder (A,B,Z). The pulse frequency is average (10kHz).
    I am only using A and B channels.
    The function I have to implement is to generate an output every N pulses in the forward direction. N being an integer and ranging from 1 to let say 100.
    I have no constraint on the output. I am it can be a bit toggling or a pulse generation.
    What functions shall I call in MeasurementStudio.Net to implement this ?
    How many counters should I use ?
    On the register basis, my guess is that I have to pre-load a value in the register.
    Then when downcounting the counter reaches 0 this in turn does 2 things:
    reloads the counter to its preset value
    triggers the output generation (TerminalCount)
    Thanks for any help you may bring 
    NOTEs FOR NI guys:
    By the way, in the NI samples, quadrature doesn't work all the way.  I nthe sample  "CountDigEvents" with CountDirection set to "Externally controlled",  backward motion is never displayed. This is because the counter is read as a UInt32.
    Solved!
    Go to Solution.

    Hi,
    Your first ideas are pretty good, it should be a good way to implement a solution for your problematic.
    I am not used to work with MeasurementStudio, but this is few links which you could use or which could help you with theoretical points:
    http://zone.ni.com/devzone/cda/tut/p/id/3167
    <link no longer exists>
    http://zone.ni.com/devzone/cda/epd/p/id/2999#0requirements
    Hope it could help
    Mathieu B
    National Instruments France
    #adMrkt{text-align: center;font-size:11px; font-weight: bold;} #adMrkt a {text-decoration: none;} #adMrkt a:hover{font-size: 9px;} #adMrkt a span{display: none;} #adMrkt a:hover span{display: block;}
    Forum Aéronautique, Spatial et Défense. Avec la participation exceptionnelle de Bernard DUPRIEU, Res...

  • Measuring frequency using a 6602 device

    Hello,
    How can we measure the frequency of a signal using a 6602 device? How many counters are needed for this purpose?
    We intend to use our own device driver, hence detailed instructions will be much appreciated.
    Thank you,
    Itai

    The origin of the time stamp depends on the type of network module you are using. The following discussion covers how time stamps are generated with the FP-1600 and FP-1000:
    http://exchange.ni.com/servlet/ProcessRequest?RHIVEID=101&RNAME=ViewQuestion&HOID=50650000000800000020230000&ECategory=Distributed+I%2FO.FieldPoint
    My best recommendation is to purchase another CTR module. Using software timing will usually give you erratic results. That being said, make sure to use the "tick count (ms)" function if you must use software timing. That is the most accurate method for software timing. Also, you should set the counters to reset on read as recommended in Method 2 of this KnowledgeBase:
    http://ae.natinst.com/operations/ae/public.nsf/fca7838c4500dc108
    62567a100753500/d8db42f9fdc3607e862568640047f144?OpenDocument
    Regards,
    Michael Shasteen
    Applications Engineering
    National Instruments
    www.ni.com/ask
    1-866-ASK-MY-NI

  • Frequency multiplication on 6602

    I am doing frequency multiplication with NI 6602 counter (see attached picture LV 2011 snippet):
    Ctr0 is triggered by external clock with measured period (say 50 ms, 20 Hz). Ctr0 task is retriggerable, so it is running continuously.
    Ctr3 task is retriggerable finite generation - to multiply frequency 100 times (to 2 kHz, 500 us) I generate 100 pulses, high time+low time slightly below 500 us. So all 100 pulses end just before the next ctr 0 trigger. Phase between this task and input triggers is controlled by changing low time of ctr0 task during runtime. 
    My problem is that when I change delay, ctr3 task can skip one trigger period (50ms). It happens when I reduce the delay and ctr0 pulse is generated before previous ctr 3 finite generation finishes, so ctr3 waits for the next pulse. But they should be running continuously, allowed pause in generating pulses is 5 ms maximum. 
    One solution is to use a different counter to generate 500 us pulses, and connect it while main tasks are switching. I will have wrong phase for a while, but pause in generating will be smaller.
    But I am running out of counters, also disconnecting main task and connecting different task will take time. And I do not like this solution. Any advice?
    I can not generate 99 pulses, switch phase, then switch back to 100 pulses, number of samples can not be changed at run-time.
    Attachments:
    6602 frequency multiplier with phase control.png ‏47 KB

    Shane,
    The goal is to continuously produce phase shifted signal with multiplied frequency (see picture). And change delay without disturbing this signal significantly
    Input triggers run continuously, all tasks are retriggerable, so they run continuously too.
    See the picture with N = 4 and delay change problem.
    Attachments:
    frequency multiplied signals.png ‏13 KB

  • Frequency divide by N doesn't work on Counter-Ti​mer PCI-6602

    Hello everybody,
    I tried to do something basic ( ?) with this Counter-Timer 6602 Board, and it doesn’t work.
    So I hope some people with more experience than me could understand what happens here.
    1) What I need:
    I need to generate 4 synchonised clocks, whose periods will be multiple of 1 ms.
    2) What I have:
    LabVIEW 7.0 and a PCI-6602 Counter-Timer Board in a DELL PC running under XP pro.
    The PCI-6602 Counter-Timer Board has 8 counter timers named CTR 0, CTR 1, ... CTR7.
    3) What I have already done, and that worked:
    - Generate a 1 kHz “Master Clock” signal from CTR 4, configured by “Continuous Pulse Generator Config.vi” (found in “Data Acquisition, Counters...).
    - configure CTR 0 and CTR 1 to work as frequency dividers, by use of “Down Counter or Divider Config.vi”.
    - Apply the output signal of CTR 4 (OUT ) to the SOURCE inputs of CTR 0 and CTR 1 by means of physical wiring in the SCB-68 connection box.
    When I do this, I get two nice secondary clock signals on my oscilloscope screen, ( with periods = 3 ms, or 5 ms or whatever multiples of 1 ms I choose) from CTR 0 and CTR 1 outputs , very clean and perfectly in phase with the 1 kHz Master Clock.
    So far, so good...
    But I still need 2 more secondary clocks...
    One would say: “No problem, do the same trick with two other counters...” Well, not so simple, it seems...
    4) What I tried to do, and that didn’t work:
    When I try to do the same frequency division with any of the remaining counters, (CTR2 to CTR7), the program stops and I get an error “ –10020 : Time base not valid “.
    I can’t figure out what happens here: I thought any counter could be configured to work as a frequency divider, but it seems not to be so, and I am stuck here.
    Has anyone an idea about how to fix this type of problem?
    Attached file: hor_div02New.vi
    Attachments:
    hor_div02New.vi ‏123 KB

    karolik,
    I'm just adding a followup in English. As Marc L. mentioned, the particular vi named "Down Counter or Divider Config" isn't compatible with the 6602. While the 6602 does have the ability to generate 4 synchronized clocks, a different syntax is needed. Here's how I'd do it:
    Traditional NI-DAQ
    1. Configure a continuous pulsetrain on CTR 4. Route its output to, say, RTSI 4. Don't start it yet.
    2. Configure CTR 0,1,2,3 for continuous pulsetrains using RTSI 4 as their "timebase source." Start them.
    3. Start the CTR 4 pulsetrain.
    4. Now CTR's 0-3 should generate separate clocks with synchronized phasing.
    DAQmx
    1. Configure a continuous pulsetrain on CTR 4. Don't start it yet.
    2. Configure CTR 0,1,2,3 for continuous pulsetrains using "Ticks" for units. Use a DAQmx property node (probably Channel property node, but am not 100% sure and don't have a LV PC handy to check) to specify that the "ctr4 internal output" should be used as the timebase. Start them.
    3. Start the CTR 4 pulsetrain.
    4. Now CTR's 0-3 should generate separate clocks with synchronized phasing.
    -Kevin P.

  • 6602 Frequency measuremen​t on all channels

    Hi,
    I want to measure the frequency with a 6602 Board on more than 3 channels (max. 8 channels): It is possible with 3 channels but not with more. Does anyone have a .vi example how do do it?
    Thank you
    Patrick

    My additional questions for the example with 8 counters: http://zone.ni.com/devzone/cda/epd/p/id/4836.
    There are three inputs:
    The source input: SCR0...SCR8, the count terminal and the external timing source.
    I don`t know exactly the functions of the last two: I think the count terminal ist the signal for reading out the whole buffer and the timing source is for saving the SCR Datas directly into the single buffer (this signal is needed for a single edge counter, too).
    To measure a signal of 400 Hz on SCR0 (PFI 39) I take for the timing source a Signal with 100Hz to port PFI 38. To clear the buffer I take a Signal of10 Hz at PFI 37.
    But it do not work: It shows me counts at all the timers and without the 400 Hz  Signal on SCR0.
    I hope someone can show me the error.
    Thank you
    Patrick

  • Frequency divider/ pulse generation from 1 to n

    Hi,
    I have a sample pulse which in some cases needs to be divided. I tried to use the pulse train generation function, which works fine (giving me a pulse every n sample pulses), but only starting at 2 input pulses. I need to be able to use this function from a division of 1 and up.
    Put in another way, can a counter be configured in such a way that it outputs a pulse every rising edge of the source signal?
    I'm using a PXI 6602 counter card and am programming it through calls to NIDAQ32.DLL under Labview 7.

    Hi Walter,
    In short, no. You can't output a pulse on every input pulse. You can however configure the degree of division. Here are the rules for division:
    When set to pulse train generation, you will have a register for the low value of the pulse train and a register for the high value. What happens in typical pulse generation is that these registers are loaded with count values such as 2 and 2 for each register respectively. In default operation, the first register will count 2 pulses on the source and then toggle the output. The second register will then count to pulses and toggle the output again. The operation then cycles back to the first register. This toggling effectively creates a pulse train that is divided by 4 and a duty cycle of 50%.
    You can however change the output mode to pulse instead of toggling upon completion of counting on a register. In the above example, you would count 2 source edges and then pulse for the first register and the count 2 more edges and pulse again for the second register. You will of course repeat this in pulse train generation mode. This mode allows you to obtain greater resolution since you are now dividing by 2 but your duty cycle will be different. Each pulsed output will be equivalent in size to the source pulse width.
    Finally, the two registers can be populated with integer values of 2 or greater. Therefore, the smallest frequency division is 2.
    You will have to work with these three elements to obtain the pulse train of your desired frequency. Hope that helps. Have a good day.
    Ron
    Applications Engineering
    National Instruments

  • How can I generate synchroniz​ed pulse trains with 6602?

    Hi,
    I would like to generate multiple pulse trains with different frequencies with the 6602 TIO card. Currently I am able to generate pulse trains with different frequencies. But is there any way to synchronize all the pulse trains? For example, I'd like to have all pulse trains with their first low-to-high at the same moment.
    Thanks!
    Dan

    Dan,
    Absolutely, the NI-TIO chip on the PCI-6602 supports a start trigger. If you configure all of the counters that are generating a pulse train to use this start trigger, they will be synchronized. The example Generate Pulse Train - Start Trig (NI-TIO).vi demonstrates this process for one counter. In LabVIEW 7, this example can be found in the following location:
    Examples >> Hardware Input and Output >> Traditional DAQ >> Counters >> NI-TIO
    You will need to add code for the other counters, but this example should give you the general idea. Furthermore, this example demonstrates how you can use one of the digital lines to generate the start trigger.
    Good luck with your application.
    Spencer S.

  • How can I get a list of BSSIDs without using netsh?

    I'm looking for an object that would have contents similar to the output of
    netsh wlan show networks mode=bssid
    I don't want to use unreliable parsing of text output, so using netsh is out.  The WMI interface that worked in windows xp doesn't work now.  There's an API, but there is no NET interface so it's pretty difficult to work with in powershell. 
    I know of a couple of adapters, but I'd like to keep this contained in one script.  I don't think I could find or write a type for the API that I could invoke in powershell.
    Is there anything else I'm missing?

    Oh, sorry, you have said that you don't want to use netsh.
    I will involve someone familiar with this to further look at this issue. Hope there is a way for you to use without the usage of netsh.
    There might be some time delay. Appreciate your patience.
    Thank you for your understanding and support.
    Regards,
    Yan Li
    Cataleya Li
    TechNet Community Support
    Thanks, but I think I got it all figured out.  I used the C# code from the managed wifi api project (http://managedwifi.codeplex.com/) though it needed a little tweaking - had to get everything in one
    namespace so powershell could easily consume it without external files.  Had to do a little manual type conversion with the output because yay unmanaged and untyped API output.  This still needs some tweaking to present it better, but this will do
    the basics.
    Note that this is two parts.  String all the code from this post and the next into one ps1.
    $NativeWifiCode = @'
    using System;
    using System.Collections.Generic;
    using System.ComponentModel;
    using System.Runtime.InteropServices;
    using System.Net.NetworkInformation;
    using System.Threading;
    using System.Text;
    using System.Diagnostics;
    namespace NativeWifi
    /// <summary>
    /// Represents a client to the Zeroconf (Native Wifi) service.
    /// </summary>
    /// <remarks>
    /// This class is the entrypoint to Native Wifi management. To manage WiFi settings, create an instance
    /// of this class.
    /// </remarks>
    public static class Wlan
    #region P/Invoke API
    /// <summary>
    /// Defines various opcodes used to set and query parameters for an interface.
    /// </summary>
    /// <remarks>
    /// Corresponds to the native <c>WLAN_INTF_OPCODE</c> type.
    /// </remarks>
    public enum WlanIntfOpcode
    /// <summary>
    /// Opcode used to set or query whether auto config is enabled.
    /// </summary>
    AutoconfEnabled = 1,
    /// <summary>
    /// Opcode used to set or query whether background scan is enabled.
    /// </summary>
    BackgroundScanEnabled,
    /// <summary>
    /// Opcode used to set or query the media streaming mode of the driver.
    /// </summary>
    MediaStreamingMode,
    /// <summary>
    /// Opcode used to set or query the radio state.
    /// </summary>
    RadioState,
    /// <summary>
    /// Opcode used to set or query the BSS type of the interface.
    /// </summary>
    BssType,
    /// <summary>
    /// Opcode used to query the state of the interface.
    /// </summary>
    InterfaceState,
    /// <summary>
    /// Opcode used to query information about the current connection of the interface.
    /// </summary>
    CurrentConnection,
    /// <summary>
    /// Opcose used to query the current channel on which the wireless interface is operating.
    /// </summary>
    ChannelNumber,
    /// <summary>
    /// Opcode used to query the supported auth/cipher pairs for infrastructure mode.
    /// </summary>
    SupportedInfrastructureAuthCipherPairs,
    /// <summary>
    /// Opcode used to query the supported auth/cipher pairs for ad hoc mode.
    /// </summary>
    SupportedAdhocAuthCipherPairs,
    /// <summary>
    /// Opcode used to query the list of supported country or region strings.
    /// </summary>
    SupportedCountryOrRegionStringList,
    /// <summary>
    /// Opcode used to set or query the current operation mode of the wireless interface.
    /// </summary>
    CurrentOperationMode,
    /// <summary>
    /// Opcode used to query driver statistics.
    /// </summary>
    Statistics = 0x10000101,
    /// <summary>
    /// Opcode used to query the received signal strength.
    /// </summary>
    RSSI,
    SecurityStart = 0x20010000,
    SecurityEnd = 0x2fffffff,
    IhvStart = 0x30000000,
    IhvEnd = 0x3fffffff
    /// <summary>
    /// Specifies the origin of automatic configuration (auto config) settings.
    /// </summary>
    /// <remarks>
    /// Corresponds to the native <c>WLAN_OPCODE_VALUE_TYPE</c> type.
    /// </remarks>
    public enum WlanOpcodeValueType
    /// <summary>
    /// The auto config settings were queried, but the origin of the settings was not determined.
    /// </summary>
    QueryOnly = 0,
    /// <summary>
    /// The auto config settings were set by group policy.
    /// </summary>
    SetByGroupPolicy = 1,
    /// <summary>
    /// The auto config settings were set by the user.
    /// </summary>
    SetByUser = 2,
    /// <summary>
    /// The auto config settings are invalid.
    /// </summary>
    Invalid = 3
    public const uint WLAN_CLIENT_VERSION_XP_SP2 = 1;
    public const uint WLAN_CLIENT_VERSION_LONGHORN = 2;
    [DllImport("wlanapi.dll")]
    public static extern int WlanOpenHandle(
    [In] UInt32 clientVersion,
    [In, Out] IntPtr pReserved,
    [Out] out UInt32 negotiatedVersion,
    [Out] out IntPtr clientHandle);
    [DllImport("wlanapi.dll")]
    public static extern int WlanCloseHandle(
    [In] IntPtr clientHandle,
    [In, Out] IntPtr pReserved);
    [DllImport("wlanapi.dll")]
    public static extern int WlanEnumInterfaces(
    [In] IntPtr clientHandle,
    [In, Out] IntPtr pReserved,
    [Out] out IntPtr ppInterfaceList);
    [DllImport("wlanapi.dll")]
    public static extern int WlanQueryInterface(
    [In] IntPtr clientHandle,
    [In, MarshalAs(UnmanagedType.LPStruct)] Guid interfaceGuid,
    [In] WlanIntfOpcode opCode,
    [In, Out] IntPtr pReserved,
    [Out] out int dataSize,
    [Out] out IntPtr ppData,
    [Out] out WlanOpcodeValueType wlanOpcodeValueType);
    [DllImport("wlanapi.dll")]
    public static extern int WlanSetInterface(
    [In] IntPtr clientHandle,
    [In, MarshalAs(UnmanagedType.LPStruct)] Guid interfaceGuid,
    [In] WlanIntfOpcode opCode,
    [In] uint dataSize,
    [In] IntPtr pData,
    [In, Out] IntPtr pReserved);
    /// <param name="pDot11Ssid">Not supported on Windows XP SP2: must be a <c>null</c> reference.</param>
    /// <param name="pIeData">Not supported on Windows XP SP2: must be a <c>null</c> reference.</param>
    [DllImport("wlanapi.dll")]
    public static extern int WlanScan(
    [In] IntPtr clientHandle,
    [In, MarshalAs(UnmanagedType.LPStruct)] Guid interfaceGuid,
    [In] IntPtr pDot11Ssid,
    [In] IntPtr pIeData,
    [In, Out] IntPtr pReserved);
    /// <summary>
    /// Defines flags passed to <see cref="WlanGetAvailableNetworkList"/>.
    /// </summary>
    [Flags]
    public enum WlanGetAvailableNetworkFlags
    /// <summary>
    /// Include all ad-hoc network profiles in the available network list, including profiles that are not visible.
    /// </summary>
    IncludeAllAdhocProfiles = 0x00000001,
    /// <summary>
    /// Include all hidden network profiles in the available network list, including profiles that are not visible.
    /// </summary>
    IncludeAllManualHiddenProfiles = 0x00000002
    /// <summary>
    /// The header of an array of information about available networks.
    /// </summary>
    [StructLayout(LayoutKind.Sequential)]
    internal struct WlanAvailableNetworkListHeader
    /// <summary>
    /// Contains the number of <see cref="WlanAvailableNetwork"/> items following the header.
    /// </summary>
    public uint numberOfItems;
    /// <summary>
    /// The index of the current item. The index of the first item is 0.
    /// </summary>
    public uint index;
    /// <summary>
    /// Defines the flags which specify characteristics of an available network.
    /// </summary>
    [Flags]
    public enum WlanAvailableNetworkFlags
    /// <summary>
    /// This network is currently connected.
    /// </summary>
    Connected = 0x00000001,
    /// <summary>
    /// There is a profile for this network.
    /// </summary>
    HasProfile = 0x00000002
    /// <summary>
    /// Contains information about an available wireless network.
    /// </summary>
    [StructLayout(LayoutKind.Sequential, CharSet=CharSet.Unicode)]
    public struct WlanAvailableNetwork
    /// <summary>
    /// Contains the profile name associated with the network.
    /// If the network doesn't have a profile, this member will be empty.
    /// If multiple profiles are associated with the network, there will be multiple entries with the same SSID in the visible network list. Profile names are case-sensitive.
    /// </summary>
    [MarshalAs(UnmanagedType.ByValTStr, SizeConst = 256)]
    public string profileName;
    /// <summary>
    /// Contains the SSID of the visible wireless network.
    /// </summary>
    public Dot11Ssid dot11Ssid;
    /// <summary>
    /// Specifies whether the network is an infrastructure or an ad-hoc one.
    /// </summary>
    public Dot11BssType dot11BssType;
    /// <summary>
    /// Indicates the number of BSSIDs in the network.
    /// </summary>
    public uint numberOfBssids;
    /// <summary>
    /// Indicates whether the network is connectable.
    /// </summary>
    public bool networkConnectable;
    /// <summary>
    /// Indicates why a network cannot be connected to. This member is only valid when <see cref="networkConnectable"/> is <c>false</c>.
    /// </summary>
    public WlanReasonCode wlanNotConnectableReason;
    /// <summary>
    /// The number of PHY types supported on available networks.
    /// The maximum value of this field is 8. If more than 8 PHY types are supported, <see cref="morePhyTypes"/> must be set to <c>true</c>.
    /// </summary>
    private uint numberOfPhyTypes;
    /// <summary>
    /// Contains an array of <see cref="Dot11PhyType"/> values that represent the PHY types supported by the available networks.
    /// When <see cref="numberOfPhyTypes"/> is greater than 8, this array contains only the first 8 PHY types.
    /// </summary>
    [MarshalAs(UnmanagedType.ByValArray, SizeConst = 8)]
    private Dot11PhyType[] dot11PhyTypes;
    /// <summary>
    /// Gets the <see cref="Dot11PhyType"/> values that represent the PHY types supported by the available networks.
    /// </summary>
    public Dot11PhyType[] Dot11PhyTypes
    get
    Dot11PhyType[] ret = new Dot11PhyType[numberOfPhyTypes];
    Array.Copy(dot11PhyTypes, ret, numberOfPhyTypes);
    return ret;
    /// <summary>
    /// Specifies if there are more than 8 PHY types supported.
    /// When this member is set to <c>true</c>, an application must call <see cref="WlanClient.WlanInterface.GetNetworkBssList"/> to get the complete list of PHY types.
    /// <see cref="WlanBssEntry.phyId"/> contains the PHY type for an entry.
    /// </summary>
    public bool morePhyTypes;
    /// <summary>
    /// A percentage value that represents the signal quality of the network.
    /// This field contains a value between 0 and 100.
    /// A value of 0 implies an actual RSSI signal strength of -100 dbm.
    /// A value of 100 implies an actual RSSI signal strength of -50 dbm.
    /// You can calculate the RSSI signal strength value for values between 1 and 99 using linear interpolation.
    /// </summary>
    public uint wlanSignalQuality;
    /// <summary>
    /// Indicates whether security is enabled on the network.
    /// </summary>
    public bool securityEnabled;
    /// <summary>
    /// Indicates the default authentication algorithm used to join this network for the first time.
    /// </summary>
    public Dot11AuthAlgorithm dot11DefaultAuthAlgorithm;
    /// <summary>
    /// Indicates the default cipher algorithm to be used when joining this network.
    /// </summary>
    public Dot11CipherAlgorithm dot11DefaultCipherAlgorithm;
    /// <summary>
    /// Contains various flags specifying characteristics of the available network.
    /// </summary>
    public WlanAvailableNetworkFlags flags;
    /// <summary>
    /// Reserved for future use. Must be set to NULL.
    /// </summary>
    uint reserved;
    [DllImport("wlanapi.dll")]
    public static extern int WlanGetAvailableNetworkList(
    [In] IntPtr clientHandle,
    [In, MarshalAs(UnmanagedType.LPStruct)] Guid interfaceGuid,
    [In] WlanGetAvailableNetworkFlags flags,
    [In, Out] IntPtr reservedPtr,
    [Out] out IntPtr availableNetworkListPtr);
    [Flags]
    public enum WlanProfileFlags
    /// <remarks>
    /// The only option available on Windows XP SP2.
    /// </remarks>
    AllUser = 0,
    GroupPolicy = 1,
    User = 2
    [DllImport("wlanapi.dll")]
    public static extern int WlanSetProfile(
    [In] IntPtr clientHandle,
    [In, MarshalAs(UnmanagedType.LPStruct)] Guid interfaceGuid,
    [In] WlanProfileFlags flags,
    [In, MarshalAs(UnmanagedType.LPWStr)] string profileXml,
    [In, Optional, MarshalAs(UnmanagedType.LPWStr)] string allUserProfileSecurity,
    [In] bool overwrite,
    [In] IntPtr pReserved,
    [Out] out WlanReasonCode reasonCode);
    /// <summary>
    /// Defines the access mask of an all-user profile.
    /// </summary>
    [Flags]
    public enum WlanAccess
    /// <summary>
    /// The user can view profile permissions.
    /// </summary>
    ReadAccess = 0x00020000 | 0x0001,
    /// <summary>
    /// The user has read access, and the user can also connect to and disconnect from a network using the profile.
    /// </summary>
    ExecuteAccess = ReadAccess | 0x0020,
    /// <summary>
    /// The user has execute access and the user can also modify and delete permissions associated with a profile.
    /// </summary>
    WriteAccess = ReadAccess | ExecuteAccess | 0x0002 | 0x00010000 | 0x00040000
    /// <param name="flags">Not supported on Windows XP SP2: must be a <c>null</c> reference.</param>
    [DllImport("wlanapi.dll")]
    public static extern int WlanGetProfile(
    [In] IntPtr clientHandle,
    [In, MarshalAs(UnmanagedType.LPStruct)] Guid interfaceGuid,
    [In, MarshalAs(UnmanagedType.LPWStr)] string profileName,
    [In] IntPtr pReserved,
    [Out] out IntPtr profileXml,
    [Out, Optional] out WlanProfileFlags flags,
    [Out, Optional] out WlanAccess grantedAccess);
    [DllImport("wlanapi.dll")]
    public static extern int WlanGetProfileList(
    [In] IntPtr clientHandle,
    [In, MarshalAs(UnmanagedType.LPStruct)] Guid interfaceGuid,
    [In] IntPtr pReserved,
    [Out] out IntPtr profileList
    [DllImport("wlanapi.dll")]
    public static extern void WlanFreeMemory(IntPtr pMemory);
    [DllImport("wlanapi.dll")]
    public static extern int WlanReasonCodeToString(
    [In] WlanReasonCode reasonCode,
    [In] int bufferSize,
    [In, Out] StringBuilder stringBuffer,
    IntPtr pReserved
    /// <summary>
    /// Defines the mask which specifies where a notification comes from.
    /// </summary>
    [Flags]
    public enum WlanNotificationSource
    None = 0,
    /// <summary>
    /// All notifications, including those generated by the 802.1X module.
    /// </summary>
    All = 0X0000FFFF,
    /// <summary>
    /// Notifications generated by the auto configuration module.
    /// </summary>
    ACM = 0X00000008,
    /// <summary>
    /// Notifications generated by MSM.
    /// </summary>
    MSM = 0X00000010,
    /// <summary>
    /// Notifications generated by the security module.
    /// </summary>
    Security = 0X00000020,
    /// <summary>
    /// Notifications generated by independent hardware vendors (IHV).
    /// </summary>
    IHV = 0X00000040
    /// <summary>
    /// Defines the types of ACM (<see cref="WlanNotificationSource.ACM"/>) notifications.
    /// </summary>
    /// <remarks>
    /// The enumeration identifiers correspond to the native <c>wlan_notification_acm_</c> identifiers.
    /// On Windows XP SP2, only the <c>ConnectionComplete</c> and <c>Disconnected</c> notifications are available.
    /// </remarks>
    public enum WlanNotificationCodeAcm
    AutoconfEnabled = 1,
    AutoconfDisabled,
    BackgroundScanEnabled,
    BackgroundScanDisabled,
    BssTypeChange,
    PowerSettingChange,
    ScanComplete,
    ScanFail,
    ConnectionStart,
    ConnectionComplete,
    ConnectionAttemptFail,
    FilterListChange,
    InterfaceArrival,
    InterfaceRemoval,
    ProfileChange,
    ProfileNameChange,
    ProfilesExhausted,
    NetworkNotAvailable,
    NetworkAvailable,
    Disconnecting,
    Disconnected,
    AdhocNetworkStateChange
    /// <summary>
    /// Defines the types of an MSM (<see cref="WlanNotificationSource.MSM"/>) notifications.
    /// </summary>
    /// <remarks>
    /// The enumeration identifiers correspond to the native <c>wlan_notification_msm_</c> identifiers.
    /// </remarks>
    public enum WlanNotificationCodeMsm
    Associating = 1,
    Associated,
    Authenticating,
    Connected,
    RoamingStart,
    RoamingEnd,
    RadioStateChange,
    SignalQualityChange,
    Disassociating,
    Disconnected,
    PeerJoin,
    PeerLeave,
    AdapterRemoval,
    AdapterOperationModeChange
    /// <summary>
    /// Contains information provided when registering for WLAN notifications.
    /// </summary>
    /// <remarks>
    /// Corresponds to the native <c>WLAN_NOTIFICATION_DATA</c> type.
    /// </remarks>
    [StructLayout(LayoutKind.Sequential)]
    public struct WlanNotificationData
    /// <summary>
    /// Specifies where the notification comes from.
    /// </summary>
    /// <remarks>
    /// On Windows XP SP2, this field must be set to <see cref="WlanNotificationSource.None"/>, <see cref="WlanNotificationSource.All"/> or <see cref="WlanNotificationSource.ACM"/>.
    /// </remarks>
    public WlanNotificationSource notificationSource;
    /// <summary>
    /// Indicates the type of notification. The value of this field indicates what type of associated data will be present in <see cref="dataPtr"/>.
    /// </summary>
    public int notificationCode;
    /// <summary>
    /// Indicates which interface the notification is for.
    /// </summary>
    public Guid interfaceGuid;
    /// <summary>
    /// Specifies the size of <see cref="dataPtr"/>, in bytes.
    /// </summary>
    public int dataSize;
    /// <summary>
    /// Pointer to additional data needed for the notification, as indicated by <see cref="notificationCode"/>.
    /// </summary>
    public IntPtr dataPtr;
    /// <summary>
    /// Gets the notification code (in the correct enumeration type) according to the notification source.
    /// </summary>
    public object NotificationCode
    get
    switch (notificationSource)
    case WlanNotificationSource.MSM:
    return (WlanNotificationCodeMsm)notificationCode;
    case WlanNotificationSource.ACM:
    return (WlanNotificationCodeAcm)notificationCode;
    default:
    return notificationCode;
    /// <summary>
    /// Defines the callback function which accepts WLAN notifications.
    /// </summary>
    public delegate void WlanNotificationCallbackDelegate(ref WlanNotificationData notificationData, IntPtr context);
    [DllImport("wlanapi.dll")]
    public static extern int WlanRegisterNotification(
    [In] IntPtr clientHandle,
    [In] WlanNotificationSource notifSource,
    [In] bool ignoreDuplicate,
    [In] WlanNotificationCallbackDelegate funcCallback,
    [In] IntPtr callbackContext,
    [In] IntPtr reserved,
    [Out] out WlanNotificationSource prevNotifSource);
    /// <summary>
    /// Defines flags which affect connecting to a WLAN network.
    /// </summary>
    [Flags]
    public enum WlanConnectionFlags
    /// <summary>
    /// Connect to the destination network even if the destination is a hidden network. A hidden network does not broadcast its SSID. Do not use this flag if the destination network is an ad-hoc network.
    /// <para>If the profile specified by <see cref="WlanConnectionParameters.profile"/> is not <c>null</c>, then this flag is ignored and the nonBroadcast profile element determines whether to connect to a hidden network.</para>
    /// </summary>
    HiddenNetwork = 0x00000001,
    /// <summary>
    /// Do not form an ad-hoc network. Only join an ad-hoc network if the network already exists. Do not use this flag if the destination network is an infrastructure network.
    /// </summary>
    AdhocJoinOnly = 0x00000002,
    /// <summary>
    /// Ignore the privacy bit when connecting to the network. Ignoring the privacy bit has the effect of ignoring whether packets are encryption and ignoring the method of encryption used. Only use this flag when connecting to an infrastructure network using a temporary profile.
    /// </summary>
    IgnorePrivacyBit = 0x00000004,
    /// <summary>
    /// Exempt EAPOL traffic from encryption and decryption. This flag is used when an application must send EAPOL traffic over an infrastructure network that uses Open authentication and WEP encryption. This flag must not be used to connect to networks that require 802.1X authentication. This flag is only valid when <see cref="WlanConnectionParameters.wlanConnectionMode"/> is set to <see cref="WlanConnectionMode.TemporaryProfile"/>. Avoid using this flag whenever possible.
    /// </summary>
    EapolPassthrough = 0x00000008
    /// <summary>
    /// Specifies the parameters used when using the <see cref="WlanConnect"/> function.
    /// </summary>
    /// <remarks>
    /// Corresponds to the native <c>WLAN_CONNECTION_PARAMETERS</c> type.
    /// </remarks>
    [StructLayout(LayoutKind.Sequential)]
    public struct WlanConnectionParameters
    /// <summary>
    /// Specifies the mode of connection.
    /// </summary>
    public WlanConnectionMode wlanConnectionMode;
    /// <summary>
    /// Specifies the profile being used for the connection.
    /// The contents of the field depend on the <see cref="wlanConnectionMode"/>:
    /// <list type="table">
    /// <listheader>
    /// <term>Value of <see cref="wlanConnectionMode"/></term>
    /// <description>Contents of the profile string</description>
    /// </listheader>
    /// <item>
    /// <term><see cref="WlanConnectionMode.Profile"/></term>
    /// <description>The name of the profile used for the connection.</description>
    /// </item>
    /// <item>
    /// <term><see cref="WlanConnectionMode.TemporaryProfile"/></term>
    /// <description>The XML representation of the profile used for the connection.</description>
    /// </item>
    /// <item>
    /// <term><see cref="WlanConnectionMode.DiscoverySecure"/>, <see cref="WlanConnectionMode.DiscoveryUnsecure"/> or <see cref="WlanConnectionMode.Auto"/></term>
    /// <description><c>null</c></description>
    /// </item>
    /// </list>
    /// </summary>
    [MarshalAs(UnmanagedType.LPWStr)]
    public string profile;
    /// <summary>
    /// Pointer to a <see cref="Dot11Ssid"/> structure that specifies the SSID of the network to connect to.
    /// This field is optional. When set to <c>null</c>, all SSIDs in the profile will be tried.
    /// This field must not be <c>null</c> if <see cref="wlanConnectionMode"/> is set to <see cref="WlanConnectionMode.DiscoverySecure"/> or <see cref="WlanConnectionMode.DiscoveryUnsecure"/>.
    /// </summary>
    public IntPtr dot11SsidPtr;
    /// <summary>
    /// Pointer to a <c>Dot11BssidList</c> structure that contains the list of basic service set (BSS) identifiers desired for the connection.
    /// </summary>
    /// <remarks>
    /// On Windows XP SP2, must be set to <c>null</c>.
    /// </remarks>
    public IntPtr desiredBssidListPtr;
    /// <summary>
    /// A <see cref="Dot11BssType"/> value that indicates the BSS type of the network. If a profile is provided, this BSS type must be the same as the one in the profile.
    /// </summary>
    public Dot11BssType dot11BssType;
    /// <summary>
    /// Specifies ocnnection parameters.
    /// </summary>
    /// <remarks>
    /// On Windows XP SP2, must be set to 0.
    /// </remarks>
    public WlanConnectionFlags flags;
    /// <summary>
    /// The connection state of an ad hoc network.
    /// </summary>
    public enum WlanAdhocNetworkState
    /// <summary>
    /// The ad hoc network has been formed, but no client or host is connected to the network.
    /// </summary>
    Formed = 0,
    /// <summary>
    /// A client or host is connected to the ad hoc network.
    /// </summary>
    Connected = 1
    [DllImport("wlanapi.dll")]
    public static extern int WlanConnect(
    [In] IntPtr clientHandle,
    [In, MarshalAs(UnmanagedType.LPStruct)] Guid interfaceGuid,
    [In] ref WlanConnectionParameters connectionParameters,
    IntPtr pReserved);
    [DllImport("wlanapi.dll")]
    public static extern int WlanDeleteProfile(
    [In] IntPtr clientHandle,
    [In, MarshalAs(UnmanagedType.LPStruct)] Guid interfaceGuid,
    [In, MarshalAs(UnmanagedType.LPWStr)] string profileName,
    IntPtr reservedPtr
    [DllImport("wlanapi.dll")]
    public static extern int WlanGetNetworkBssList(
    [In] IntPtr clientHandle,
    [In, MarshalAs(UnmanagedType.LPStruct)] Guid interfaceGuid,
    [In] IntPtr dot11SsidInt,
    [In] Dot11BssType dot11BssType,
    [In] bool securityEnabled,
    IntPtr reservedPtr,
    [Out] out IntPtr wlanBssList
    [StructLayout(LayoutKind.Sequential)]
    internal struct WlanBssListHeader
    internal uint totalSize;
    internal uint numberOfItems;
    /// <summary>
    /// Contains information about a basic service set (BSS).
    /// </summary>
    [StructLayout(LayoutKind.Sequential)]
    public struct WlanBssEntry
    /// <summary>
    /// Contains the SSID of the access point (AP) associated with the BSS.
    /// </summary>
    public Dot11Ssid dot11Ssid;
    /// <summary>
    /// The identifier of the PHY on which the AP is operating.
    /// </summary>
    public uint phyId;
    /// <summary>
    /// Contains the BSS identifier.
    /// </summary>
    [MarshalAs(UnmanagedType.ByValArray, SizeConst = 6)]
    public byte[] dot11Bssid;
    /// <summary>
    /// Specifies whether the network is infrastructure or ad hoc.
    /// </summary>
    public Dot11BssType dot11BssType;
    public Dot11PhyType dot11BssPhyType;
    /// <summary>
    /// The received signal strength in dBm.
    /// </summary>
    public int rssi;
    /// <summary>
    /// The link quality reported by the driver. Ranges from 0-100.
    /// </summary>
    public uint linkQuality;
    /// <summary>
    /// If 802.11d is not implemented, the network interface card (NIC) must set this field to TRUE. If 802.11d is implemented (but not necessarily enabled), the NIC must set this field to TRUE if the BSS operation complies with the configured regulatory domain.
    /// </summary>
    public bool inRegDomain;
    /// <summary>
    /// Contains the beacon interval value from the beacon packet or probe response.
    /// </summary>
    public ushort beaconPeriod;
    /// <summary>
    /// The timestamp from the beacon packet or probe response.
    /// </summary>
    public ulong timestamp;
    /// <summary>
    /// The host timestamp value when the beacon or probe response is received.
    /// </summary>
    public ulong hostTimestamp;
    /// <summary>
    /// The capability value from the beacon packet or probe response.
    /// </summary>
    public ushort capabilityInformation;
    /// <summary>
    /// The frequency of the center channel, in kHz.
    /// </summary>
    public uint chCenterFrequency;
    /// <summary>
    /// Contains the set of data transfer rates supported by the BSS.
    /// </summary>
    public WlanRateSet wlanRateSet;
    /// <summary>
    /// The offset of the information element (IE) data blob.
    /// </summary>
    public uint ieOffset;
    /// <summary>
    /// The size of the IE data blob, in bytes.
    /// </summary>
    public uint ieSize;
    /// <summary>
    /// Contains the set of supported data rates.
    /// </summary>
    [StructLayout(LayoutKind.Sequential)]
    public struct WlanRateSet
    /// <summary>
    /// The length, in bytes, of <see cref="rateSet"/>.
    /// </summary>
    private uint rateSetLength;
    /// <summary>
    /// An array of supported data transfer rates.
    /// </summary>
    [MarshalAs(UnmanagedType.ByValArray, SizeConst = 126)]
    private ushort[] rateSet;
    /// <summary>
    /// Gets an array of supported data transfer rates.
    /// If the rate is a basic rate, the first bit of the rate value is set to 1.
    /// A basic rate is the data transfer rate that all stations in a basic service set (BSS) can use to receive frames from the wireless medium.
    /// </summary>
    public ushort[] Rates
    get
    ushort[] rates = new ushort[rateSetLength / sizeof(ushort)];
    Array.Copy(rateSet, rates, rates.Length);
    return rates;
    /// <summary>
    /// Calculates the data transfer rate in mbit/s for a supported rate.
    /// </summary>
    /// <param name="rateIndex">The WLAN rate index (0-based).</param>
    /// <returns>The data transfer rate in mbit/s.</returns>
    /// <exception cref="ArgumentOutOfRangeException">Thrown if <param name="rateIndex"/> does not specify an existing rate.</exception>
    public double GetRateInMbps(int rateIndex)
    if ((rateIndex < 0) || (rateIndex > rateSet.Length))
    throw new ArgumentOutOfRangeException("rateIndex");
    return (rateSet[rateIndex] & 0x7FFF) * 0.5;
    /// <summary>
    /// Represents an error occuring during WLAN operations which indicate their failure via a <see cref="WlanReasonCode"/>.
    /// </summary>
    public class WlanException : Exception
    private readonly WlanReasonCode reasonCode;
    public WlanException(WlanReasonCode reasonCode)
    this.reasonCode = reasonCode;
    /// <summary>
    /// Gets the WLAN reason code.
    /// </summary>
    /// <value>The WLAN reason code.</value>
    public WlanReasonCode ReasonCode
    get { return reasonCode; }
    /// <summary>
    /// Gets a message that describes the reason code.
    /// </summary>
    /// <value></value>
    /// <returns>The error message that explains the reason for the exception, or an empty string("").</returns>
    public override string Message
    get
    StringBuilder sb = new StringBuilder(1024);
    return
    WlanReasonCodeToString(reasonCode, sb.Capacity, sb, IntPtr.Zero) == 0 ?
    sb.ToString() :
    string.Empty;
    // TODO: .NET-ify the WlanReasonCode enum (naming convention + docs).
    /// <summary>
    /// Defines reasons for a failure of a WLAN operation.
    /// </summary>
    /// <remarks>
    /// Corresponds to the native reason code identifiers (<c>WLAN_REASON_CODE_xxx</c> identifiers).
    /// </remarks>
    public enum WlanReasonCode
    Success = 0,
    // general codes
    UNKNOWN = 0x10000 + 1,
    RANGE_SIZE = 0x10000,
    BASE = 0x10000 + RANGE_SIZE,
    // range for Auto Config
    AC_BASE = 0x10000 + RANGE_SIZE,
    AC_CONNECT_BASE = (AC_BASE + RANGE_SIZE / 2),
    AC_END = (AC_BASE + RANGE_SIZE - 1),
    // range for profile manager
    // it has profile adding failure reason codes, but may not have
    // connection reason codes
    PROFILE_BASE = 0x10000 + (7 * RANGE_SIZE),
    PROFILE_CONNECT_BASE = (PROFILE_BASE + RANGE_SIZE / 2),
    PROFILE_END = (PROFILE_BASE + RANGE_SIZE - 1),
    // range for MSM
    MSM_BASE = 0x10000 + (2 * RANGE_SIZE),
    MSM_CONNECT_BASE = (MSM_BASE + RANGE_SIZE / 2),
    MSM_END = (MSM_BASE + RANGE_SIZE - 1),
    // range for MSMSEC
    MSMSEC_BASE = 0x10000 + (3 * RANGE_SIZE),
    MSMSEC_CONNECT_BASE = (MSMSEC_BASE + RANGE_SIZE / 2),
    MSMSEC_END = (MSMSEC_BASE + RANGE_SIZE - 1),
    // AC network incompatible reason codes
    NETWORK_NOT_COMPATIBLE = (AC_BASE + 1),
    PROFILE_NOT_COMPATIBLE = (AC_BASE + 2),
    // AC connect reason code
    NO_AUTO_CONNECTION = (AC_CONNECT_BASE + 1),
    NOT_VISIBLE = (AC_CONNECT_BASE + 2),
    GP_DENIED = (AC_CONNECT_BASE + 3),
    USER_DENIED = (AC_CONNECT_BASE + 4),
    BSS_TYPE_NOT_ALLOWED = (AC_CONNECT_BASE + 5),
    IN_FAILED_LIST = (AC_CONNECT_BASE + 6),
    IN_BLOCKED_LIST = (AC_CONNECT_BASE + 7),
    SSID_LIST_TOO_LONG = (AC_CONNECT_BASE + 8),
    CONNECT_CALL_FAIL = (AC_CONNECT_BASE + 9),
    SCAN_CALL_FAIL = (AC_CONNECT_BASE + 10),
    NETWORK_NOT_AVAILABLE = (AC_CONNECT_BASE + 11),
    PROFILE_CHANGED_OR_DELETED = (AC_CONNECT_BASE + 12),
    KEY_MISMATCH = (AC_CONNECT_BASE + 13),
    USER_NOT_RESPOND = (AC_CONNECT_BASE + 14),
    // Profile validation errors
    INVALID_PROFILE_SCHEMA = (PROFILE_BASE + 1),
    PROFILE_MISSING = (PROFILE_BASE + 2),
    INVALID_PROFILE_NAME = (PROFILE_BASE + 3),
    INVALID_PROFILE_TYPE = (PROFILE_BASE + 4),
    INVALID_PHY_TYPE = (PROFILE_BASE + 5),
    MSM_SECURITY_MISSING = (PROFILE_BASE + 6),
    IHV_SECURITY_NOT_SUPPORTED = (PROFILE_BASE + 7),
    IHV_OUI_MISMATCH = (PROFILE_BASE + 8),
    // IHV OUI not present but there is IHV settings in profile
    IHV_OUI_MISSING = (PROFILE_BASE + 9),
    // IHV OUI is present but there is no IHV settings in profile
    IHV_SETTINGS_MISSING = (PROFILE_BASE + 10),
    // both/conflict MSMSec and IHV security settings exist in profile
    CONFLICT_SECURITY = (PROFILE_BASE + 11),
    // no IHV or MSMSec security settings in profile
    SECURITY_MISSING = (PROFILE_BASE + 12),
    INVALID_BSS_TYPE = (PROFILE_BASE + 13),
    INVALID_ADHOC_CONNECTION_MODE = (PROFILE_BASE + 14),
    NON_BROADCAST_SET_FOR_ADHOC = (PROFILE_BASE + 15),
    AUTO_SWITCH_SET_FOR_ADHOC = (PROFILE_BASE + 16),
    AUTO_SWITCH_SET_FOR_MANUAL_CONNECTION = (PROFILE_BASE + 17),
    IHV_SECURITY_ONEX_MISSING = (PROFILE_BASE + 18),
    PROFILE_SSID_INVALID = (PROFILE_BASE + 19),
    TOO_MANY_SSID = (PROFILE_BASE + 20),
    // MSM network incompatible reasons
    UNSUPPORTED_SECURITY_SET_BY_OS = (MSM_BASE + 1),
    UNSUPPORTED_SECURITY_SET = (MSM_BASE + 2),
    BSS_TYPE_UNMATCH = (MSM_BASE + 3),
    PHY_TYPE_UNMATCH = (MSM_BASE + 4),
    DATARATE_UNMATCH = (MSM_BASE + 5),
    // MSM connection failure reasons, to be defined
    // failure reason codes
    // user called to disconnect
    USER_CANCELLED = (MSM_CONNECT_BASE + 1),
    // got disconnect while associating
    ASSOCIATION_FAILURE = (MSM_CONNECT_BASE + 2),
    // timeout for association
    ASSOCIATION_TIMEOUT = (MSM_CONNECT_BASE + 3),
    // pre-association security completed with failure
    PRE_SECURITY_FAILURE = (MSM_CONNECT_BASE + 4),
    // fail to start post-association security
    START_SECURITY_FAILURE = (MSM_CONNECT_BASE + 5),
    // post-association security completed with failure
    SECURITY_FAILURE = (MSM_CONNECT_BASE + 6),
    // security watchdog timeout
    SECURITY_TIMEOUT = (MSM_CONNECT_BASE + 7),
    // got disconnect from driver when roaming
    ROAMING_FAILURE = (MSM_CONNECT_BASE + 8),
    // failed to start security for roaming
    ROAMING_SECURITY_FAILURE = (MSM_CONNECT_BASE + 9),
    // failed to start security for adhoc-join
    ADHOC_SECURITY_FAILURE = (MSM_CONNECT_BASE + 10),
    // got disconnection from driver
    DRIVER_DISCONNECTED = (MSM_CONNECT_BASE + 11),
    // driver operation failed
    DRIVER_OPERATION_FAILURE = (MSM_CONNECT_BASE + 12),
    // Ihv service is not available
    IHV_NOT_AVAILABLE = (MSM_CONNECT_BASE + 13),
    // Response from ihv timed out
    IHV_NOT_RESPONDING = (MSM_CONNECT_BASE + 14),
    // Timed out waiting for driver to disconnect
    DISCONNECT_TIMEOUT = (MSM_CONNECT_BASE + 15),
    // An internal error prevented the operation from being completed.
    INTERNAL_FAILURE = (MSM_CONNECT_BASE + 16),
    // UI Request timed out.
    UI_REQUEST_TIMEOUT = (MSM_CONNECT_BASE + 17),
    // Roaming too often, post security is not completed after 5 times.
    TOO_MANY_SECURITY_ATTEMPTS = (MSM_CONNECT_BASE + 18),
    // MSMSEC reason codes
    MSMSEC_MIN = MSMSEC_BASE,
    // Key index specified is not valid
    MSMSEC_PROFILE_INVALID_KEY_INDEX = (MSMSEC_BASE + 1),
    // Key required, PSK present
    MSMSEC_PROFILE_PSK_PRESENT = (MSMSEC_BASE + 2),
    // Invalid key length
    MSMSEC_PROFILE_KEY_LENGTH = (MSMSEC_BASE + 3),
    // Invalid PSK length
    MSMSEC_PROFILE_PSK_LENGTH = (MSMSEC_BASE + 4),
    // No auth/cipher specified
    MSMSEC_PROFILE_NO_AUTH_CIPHER_SPECIFIED = (MSMSEC_BASE + 5),
    // Too many auth/cipher specified
    MSMSEC_PROFILE_TOO_MANY_AUTH_CIPHER_SPECIFIED = (MSMSEC_BASE + 6),
    // Profile contains duplicate auth/cipher
    MSMSEC_PROFILE_DUPLICATE_AUTH_CIPHER = (MSMSEC_BASE + 7),
    // Profile raw data is invalid (1x or key data)
    MSMSEC_PROFILE_RAWDATA_INVALID = (MSMSEC_BASE + 8),
    // Invalid auth/cipher combination
    MSMSEC_PROFILE_INVALID_AUTH_CIPHER = (MSMSEC_BASE + 9),
    // 802.1x disabled when it's required to be enabled
    MSMSEC_PROFILE_ONEX_DISABLED = (MSMSEC_BASE + 10),
    // 802.1x enabled when it's required to be disabled
    MSMSEC_PROFILE_ONEX_ENABLED = (MSMSEC_BASE + 11),
    MSMSEC_PROFILE_INVALID_PMKCACHE_MODE = (MSMSEC_BASE + 12),
    MSMSEC_PROFILE_INVALID_PMKCACHE_SIZE = (MSMSEC_BASE + 13),
    MSMSEC_PROFILE_INVALID_PMKCACHE_TTL = (MSMSEC_BASE + 14),
    MSMSEC_PROFILE_INVALID_PREAUTH_MODE = (MSMSEC_BASE + 15),
    MSMSEC_PROFILE_INVALID_PREAUTH_THROTTLE = (MSMSEC_BASE + 16),
    // PreAuth enabled when PMK cache is disabled
    MSMSEC_PROFILE_PREAUTH_ONLY_ENABLED = (MSMSEC_BASE + 17),
    // Capability matching failed at network
    MSMSEC_CAPABILITY_NETWORK = (MSMSEC_BASE + 18),
    // Capability matching failed at NIC
    MSMSEC_CAPABILITY_NIC = (MSMSEC_BASE + 19),
    // Capability matching failed at profile
    MSMSEC_CAPABILITY_PROFILE = (MSMSEC_BASE + 20),
    // Network does not support specified discovery type
    MSMSEC_CAPABILITY_DISCOVERY = (MSMSEC_BASE + 21),
    // Passphrase contains invalid character
    MSMSEC_PROFILE_PASSPHRASE_CHAR = (MSMSEC_BASE + 22),
    // Key material contains invalid character
    MSMSEC_PROFILE_KEYMATERIAL_CHAR = (MSMSEC_BASE + 23),
    // Wrong key type specified for the auth/cipher pair
    MSMSEC_PROFILE_WRONG_KEYTYPE = (MSMSEC_BASE + 24),
    // "Mixed cell" suspected (AP not beaconing privacy, we have privacy enabled profile)
    MSMSEC_MIXED_CELL = (MSMSEC_BASE + 25),
    // Auth timers or number of timeouts in profile is incorrect
    MSMSEC_PROFILE_AUTH_TIMERS_INVALID = (MSMSEC_BASE + 26),
    // Group key update interval in profile is incorrect
    MSMSEC_PROFILE_INVALID_GKEY_INTV = (MSMSEC_BASE + 27),
    // "Transition network" suspected, trying legacy 802.11 security
    MSMSEC_TRANSITION_NETWORK = (MSMSEC_BASE + 28),
    // Key contains characters which do not map to ASCII
    MSMSEC_PROFILE_KEY_UNMAPPED_CHAR = (MSMSEC_BASE + 29),
    // Capability matching failed at profile (auth not found)
    MSMSEC_CAPABILITY_PROFILE_AUTH = (MSMSEC_BASE + 30),
    // Capability matching failed at profile (cipher not found)
    MSMSEC_CAPABILITY_PROFILE_CIPHER = (MSMSEC_BASE + 31),
    // Failed to queue UI request
    MSMSEC_UI_REQUEST_FAILURE = (MSMSEC_CONNECT_BASE + 1),
    // 802.1x authentication did not start within configured time
    MSMSEC_AUTH_START_TIMEOUT = (MSMSEC_CONNECT_BASE + 2),
    // 802.1x authentication did not complete within configured time
    MSMSEC_AUTH_SUCCESS_TIMEOUT = (MSMSEC_CONNECT_BASE + 3),
    // Dynamic key exchange did not start within configured time
    MSMSEC_KEY_START_TIMEOUT = (MSMSEC_CONNECT_BASE + 4),
    // Dynamic key exchange did not succeed within configured time
    MSMSEC_KEY_SUCCESS_TIMEOUT = (MSMSEC_CONNECT_BASE + 5),
    // Message 3 of 4 way handshake has no key data (RSN/WPA)
    MSMSEC_M3_MISSING_KEY_DATA = (MSMSEC_CONNECT_BASE + 6),
    // Message 3 of 4 way handshake has no IE (RSN/WPA)
    MSMSEC_M3_MISSING_IE = (MSMSEC_CONNECT_BASE + 7),
    // Message 3 of 4 way handshake has no Group Key (RSN)
    MSMSEC_M3_MISSING_GRP_KEY = (MSMSEC_CONNECT_BASE + 8),
    // Matching security capabilities of IE in M3 failed (RSN/WPA)
    MSMSEC_PR_IE_MATCHING = (MSMSEC_CONNECT_BASE + 9),
    // Matching security capabilities of Secondary IE in M3 failed (RSN)
    MSMSEC_SEC_IE_MATCHING = (MSMSEC_CONNECT_BASE + 10),
    // Required a pairwise key but AP configured only group keys
    MSMSEC_NO_PAIRWISE_KEY = (MSMSEC_CONNECT_BASE + 11),
    // Message 1 of group key handshake has no key data (RSN/WPA)
    MSMSEC_G1_MISSING_KEY_DATA = (MSMSEC_CONNECT_BASE + 12),
    // Message 1 of group key handshake has no group key
    MSMSEC_G1_MISSING_GRP_KEY = (MSMSEC_CONNECT_BASE + 13),
    // AP reset secure bit after connection was secured
    MSMSEC_PEER_INDICATED_INSECURE = (MSMSEC_CONNECT_BASE + 14),
    // 802.1x indicated there is no authenticator but profile requires 802.1x
    MSMSEC_NO_AUTHENTICATOR = (MSMSEC_CONNECT_BASE + 15),
    // Plumbing settings to NIC failed
    MSMSEC_NIC_FAILURE = (MSMSEC_CONNECT_BASE + 16),
    // Operation was cancelled by caller
    MSMSEC_CANCELLED = (MSMSEC_CONNECT_BASE + 17),
    // Key was in incorrect format
    MSMSEC_KEY_FORMAT = (MSMSEC_CONNECT_BASE + 18),
    // Security downgrade detected
    MSMSEC_DOWNGRADE_DETECTED = (MSMSEC_CONNECT_BASE + 19),
    // PSK mismatch suspected
    MSMSEC_PSK_MISMATCH_SUSPECTED = (MSMSEC_CONNECT_BASE + 20),
    // Forced failure because connection method was not secure
    MSMSEC_FORCED_FAILURE = (MSMSEC_CONNECT_BASE + 21),
    // ui request couldn't be queued or user pressed cancel
    MSMSEC_SECURITY_UI_FAILURE = (MSMSEC_CONNECT_BASE + 22),
    MSMSEC_MAX = MSMSEC_END
    /// <summary>
    /// Contains information about connection related notifications.
    /// </summary>
    /// <remarks>
    /// Corresponds to the native <c>WLAN_CONNECTION_NOTIFICATION_DATA</c> type.
    /// </remarks>
    [StructLayout(LayoutKind.Sequential, CharSet = CharSet.Unicode)]
    public struct WlanConnectionNotificationData
    /// <remarks>
    /// On Windows XP SP 2, only <see cref="WlanConnectionMode.Profile"/> is supported.
    /// </remarks>
    public WlanConnectionMode wlanConnectionMode;
    /// <summary>
    /// The name of the profile used for the connection. Profile names are case-sensitive.
    /// </summary>
    [MarshalAs(UnmanagedType.ByValTStr, SizeConst = 32)]
    public string profileName;
    /// <summary>
    /// The SSID of the association.
    /// </summary>
    public Dot11Ssid dot11Ssid;
    /// <summary>
    /// The BSS network type.
    /// </summary>
    public Dot11BssType dot11BssType;
    /// <summary>
    /// Indicates whether security is enabled for this connection.
    /// </summary>
    public bool securityEnabled;
    /// <summary>
    /// Indicates the reason for an operation failure.
    /// This field has a value of <see cref="WlanReasonCode.Success"/> for all connection-related notifications except <see cref="WlanNotificationCodeAcm.ConnectionComplete"/>.
    /// If the connection fails, this field indicates the reason for the failure.
    /// </summary>
    public WlanReasonCode wlanReasonCode;
    /// <summary>
    /// This field contains the XML presentation of the profile used for discovery, if the connection succeeds.
    /// </summary>
    [MarshalAs(UnmanagedType.ByValTStr, SizeConst = 1)]
    public string profileXml;
    /// <summary>
    /// Indicates the state of an interface.
    /// </summary>
    /// <remarks>
    /// Corresponds to the native <c>WLAN_INTERFACE_STATE</c> type.
    /// </remarks>
    public enum WlanInterfaceState
    /// <summary>
    /// The interface is not ready to operate.
    /// </summary>
    NotReady = 0,
    /// <summary>
    /// The interface is connected to a network.
    /// </summary>
    Connected = 1,
    /// <summary>
    /// The interface is the first node in an ad hoc network. No peer has connected.
    /// </summary>
    AdHocNetworkFormed = 2,
    /// <summary>
    /// The interface is disconnecting from the current network.
    /// </summary>
    Disconnecting = 3,
    /// <summary>
    /// The interface is not connected to any network.
    /// </summary>
    Disconnected = 4,
    /// <summary>
    /// The interface is attempting to associate with a network.
    /// </summary>
    Associating = 5,
    /// <summary>
    /// Auto configuration is discovering the settings for the network.
    /// </summary>
    Discovering = 6,
    /// <summary>
    /// The interface is in the process of authenticating.
    /// </summary>
    Authenticating = 7
    /// <summary>
    /// Contains the SSID of an interface.
    /// </summary>
    public struct Dot11Ssid
    /// <summary>
    /// The length, in bytes, of the <see cref="SSID"/> array.
    /// </summary>
    public uint SSIDLength;
    /// <summary>
    /// The SSID.
    /// </summary>
    [MarshalAs(UnmanagedType.ByValArray, SizeConst = 32)]
    public byte[] SSID;
    /// <summary>
    /// Defines an 802.11 PHY and media type.
    /// </summary>
    /// <remarks>
    /// Corresponds to the native <c>DOT11_PHY_TYPE</c> type.
    /// </remarks>
    public enum Dot11PhyType : uint
    /// <summary>
    /// Specifies an unknown or uninitialized PHY type.
    /// </summary>
    Unknown = 0,
    /// <summary>
    /// Specifies any PHY type.
    /// </summary>
    Any = Unknown,
    /// <summary>
    /// Specifies a frequency-hopping spread-spectrum (FHSS) PHY. Bluetooth devices can use FHSS or an adaptation of FHSS.
    /// </summary>
    FHSS = 1,
    /// <summary>
    /// Specifies a direct sequence spread spectrum (DSSS) PHY.
    /// </summary>
    DSSS = 2,
    /// <summary>
    /// Specifies an infrared (IR) baseband PHY.
    /// </summary>
    IrBaseband = 3,
    /// <summary>
    /// Specifies an orthogonal frequency division multiplexing (OFDM) PHY. 802.11a devices can use OFDM.
    /// </summary>
    OFDM = 4,
    /// <summary>
    /// Specifies a high-rate DSSS (HRDSSS) PHY.
    /// </summary>
    HRDSSS = 5,
    /// <summary>
    /// Specifies an extended rate PHY (ERP). 802.11g devices can use ERP.
    /// </summary>
    ERP = 6,
    /// <summary>
    /// Specifies the start of the range that is used to define PHY types that are developed by an independent hardware vendor (IHV).
    /// </summary>
    IHV_Start = 0x80000000,
    /// <summary>
    /// Specifies the end of the range that is used to define PHY types that are developed by an independent hardware vendor (IHV).
    /// </summary>
    IHV_End = 0xffffffff

  • Systemd-logind occasionally fails to start

    Hi,
    I am running Arch with Cinnamon started by mdm-display-manager. I had this running for quite some time without an issue.
    Recently an issue popped out - OCCASIONALLY systemd-logind fails to start and I get stuck on boot screen. This happens maybe once in 5-10 boots. I have to do hard reset afterwards. CTL+ALT+DEL won't work, I can not switch to other console and I have no network to SSH to that machine.
    Other than that, system starts just fine.
    I am not sure, how to debug this further and would appreciate advice.
    # journalctl --since=today --unit=systemd-logind
    May 26 09:42:34 phenom systemd[1]: Starting Login Service...
    May 26 09:42:59 phenom systemd[1]: systemd-logind.service: main process exited, code=exited, status=1/FAILURE
    May 26 09:42:59 phenom systemd[1]: Failed to start Login Service.
    May 26 09:42:59 phenom systemd[1]: Unit systemd-logind.service entered failed state.
    May 26 09:42:59 phenom systemd[1]: systemd-logind.service failed.
    May 26 09:42:59 phenom systemd[1]: systemd-logind.service has no holdoff time, scheduling restart.
    # journalctl --since=today
    May 26 09:42:34 phenom systemd-journal[198]: Runtime journal is using 8.0M (max allowed 802.5M, trying to leave 1.1G free of 7.7G available → current limit 802.5M).
    May 26 09:42:34 phenom systemd-journal[198]: Permanent journal is using 2.0G (max allowed 4.0G, trying to leave 4.0G free of 36.6G available → current limit 4.0G).
    May 26 09:42:34 phenom systemd-journal[198]: Time spent on flushing to /var is 11.024ms for 2 entries.
    May 26 09:42:34 phenom kernel: Initializing cgroup subsys cpuset
    May 26 09:42:34 phenom kernel: Initializing cgroup subsys cpu
    May 26 09:42:34 phenom kernel: Initializing cgroup subsys cpuacct
    May 26 09:42:34 phenom kernel: Linux version 4.0.4-2-ARCH (builduser@foutrelis) (gcc version 5.1.0 (GCC) ) #1 SMP PREEMPT Fri May 22 03:05:23 UTC 2015
    May 26 09:42:34 phenom kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-linux root=UUID=d36ad497-1614-4cc5-8cc9-da2d5e5a417c rw
    May 26 09:42:34 phenom kernel: tseg: 00cff00000
    May 26 09:42:34 phenom kernel: e820: BIOS-provided physical RAM map:
    May 26 09:42:34 phenom kernel: BIOS-e820: [mem 0x0000000000000000-0x0000000000099fff] usable
    May 26 09:42:34 phenom kernel: BIOS-e820: [mem 0x000000000009f800-0x000000000009ffff] reserved
    May 26 09:42:34 phenom kernel: BIOS-e820: [mem 0x00000000000f0000-0x00000000000fffff] reserved
    May 26 09:42:34 phenom kernel: BIOS-e820: [mem 0x0000000000100000-0x00000000cfd9ffff] usable
    May 26 09:42:34 phenom kernel: BIOS-e820: [mem 0x00000000cfda0000-0x00000000cfdd0fff] ACPI NVS
    May 26 09:42:34 phenom kernel: BIOS-e820: [mem 0x00000000cfdd1000-0x00000000cfdfffff] ACPI data
    May 26 09:42:34 phenom kernel: BIOS-e820: [mem 0x00000000cfe00000-0x00000000cfefffff] reserved
    May 26 09:42:34 phenom kernel: BIOS-e820: [mem 0x00000000e0000000-0x00000000efffffff] reserved
    May 26 09:42:34 phenom kernel: BIOS-e820: [mem 0x00000000fec00000-0x00000000ffffffff] reserved
    May 26 09:42:34 phenom kernel: BIOS-e820: [mem 0x0000000100000000-0x000000042fffffff] usable
    May 26 09:42:34 phenom kernel: NX (Execute Disable) protection: active
    May 26 09:42:34 phenom kernel: SMBIOS 2.4 present.
    May 26 09:42:34 phenom kernel: DMI: Gigabyte Technology Co., Ltd. GA-990XA-UD3/GA-990XA-UD3, BIOS F9 10/13/2011
    May 26 09:42:34 phenom kernel: e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
    May 26 09:42:34 phenom kernel: e820: remove [mem 0x000a0000-0x000fffff] usable
    May 26 09:42:34 phenom kernel: AGP: No AGP bridge found
    May 26 09:42:34 phenom kernel: e820: last_pfn = 0x430000 max_arch_pfn = 0x400000000
    May 26 09:42:34 phenom kernel: MTRR default type: uncachable
    May 26 09:42:34 phenom kernel: MTRR fixed ranges enabled:
    May 26 09:42:34 phenom kernel: 00000-9FFFF write-back
    May 26 09:42:34 phenom kernel: A0000-BFFFF uncachable
    May 26 09:42:34 phenom kernel: C0000-C7FFF write-protect
    May 26 09:42:34 phenom kernel: C8000-FFFFF uncachable
    May 26 09:42:34 phenom kernel: MTRR variable ranges enabled:
    May 26 09:42:34 phenom kernel: 0 base 000000000000 mask FFFF80000000 write-back
    May 26 09:42:34 phenom kernel: 1 base 000080000000 mask FFFFC0000000 write-back
    May 26 09:42:34 phenom kernel: 2 base 0000C0000000 mask FFFFF0000000 write-back
    May 26 09:42:34 phenom kernel: 3 base 0000CFE00000 mask FFFFFFE00000 uncachable
    May 26 09:42:34 phenom kernel: 4 disabled
    May 26 09:42:34 phenom kernel: 5 disabled
    May 26 09:42:34 phenom kernel: 6 disabled
    May 26 09:42:34 phenom kernel: 7 disabled
    May 26 09:42:34 phenom kernel: TOM2: 0000000430000000 aka 17152M
    May 26 09:42:34 phenom kernel: PAT configuration [0-7]: WB WC UC- UC WB WC UC- UC
    May 26 09:42:34 phenom kernel: e820: update [mem 0xcfe00000-0xffffffff] usable ==> reserved
    May 26 09:42:34 phenom kernel: e820: last_pfn = 0xcfda0 max_arch_pfn = 0x400000000
    May 26 09:42:34 phenom kernel: found SMP MP-table at [mem 0x000f4b30-0x000f4b3f] mapped at [ffff8800000f4b30]
    May 26 09:42:34 phenom kernel: Scanning 1 areas for low memory corruption
    May 26 09:42:34 phenom kernel: Base memory trampoline at [ffff880000094000] 94000 size 24576
    May 26 09:42:34 phenom kernel: Using GB pages for direct mapping
    May 26 09:42:34 phenom kernel: init_memory_mapping: [mem 0x00000000-0x000fffff]
    May 26 09:42:34 phenom kernel: [mem 0x00000000-0x000fffff] page 4k
    May 26 09:42:34 phenom kernel: BRK [0x01b1d000, 0x01b1dfff] PGTABLE
    May 26 09:42:34 phenom kernel: BRK [0x01b1e000, 0x01b1efff] PGTABLE
    May 26 09:42:34 phenom kernel: BRK [0x01b1f000, 0x01b1ffff] PGTABLE
    May 26 09:42:34 phenom kernel: init_memory_mapping: [mem 0x42fe00000-0x42fffffff]
    May 26 09:42:34 phenom kernel: [mem 0x42fe00000-0x42fffffff] page 2M
    May 26 09:42:34 phenom kernel: BRK [0x01b20000, 0x01b20fff] PGTABLE
    May 26 09:42:34 phenom kernel: init_memory_mapping: [mem 0x420000000-0x42fdfffff]
    May 26 09:42:34 phenom kernel: [mem 0x420000000-0x42fdfffff] page 2M
    May 26 09:42:34 phenom kernel: init_memory_mapping: [mem 0x400000000-0x41fffffff]
    May 26 09:42:34 phenom kernel: [mem 0x400000000-0x41fffffff] page 2M
    May 26 09:42:34 phenom kernel: init_memory_mapping: [mem 0x00100000-0xcfd9ffff]
    May 26 09:42:34 phenom kernel: [mem 0x00100000-0x001fffff] page 4k
    May 26 09:42:34 phenom kernel: [mem 0x00200000-0x3fffffff] page 2M
    May 26 09:42:34 phenom kernel: [mem 0x40000000-0xbfffffff] page 1G
    May 26 09:42:34 phenom kernel: [mem 0xc0000000-0xcfbfffff] page 2M
    May 26 09:42:34 phenom kernel: [mem 0xcfc00000-0xcfd9ffff] page 4k
    May 26 09:42:34 phenom kernel: init_memory_mapping: [mem 0x100000000-0x3ffffffff]
    May 26 09:42:34 phenom kernel: [mem 0x100000000-0x3ffffffff] page 1G
    May 26 09:42:34 phenom kernel: RAMDISK: [mem 0x362ae000-0x3714efff]
    May 26 09:42:34 phenom kernel: ACPI: Early table checksum verification disabled
    May 26 09:42:34 phenom kernel: ACPI: RSDP 0x00000000000F6A50 000014 (v00 GBT )
    May 26 09:42:34 phenom kernel: ACPI: RSDT 0x00000000CFDD1000 000048 (v01 GBT GBTUACPI 42302E31 GBTU 01010101)
    May 26 09:42:34 phenom kernel: ACPI: FACP 0x00000000CFDD1080 000074 (v01 GBT GBTUACPI 42302E31 GBTU 01010101)
    May 26 09:42:34 phenom kernel: ACPI: DSDT 0x00000000CFDD1100 007A4B (v01 GBT GBTUACPI 00001000 MSFT 03000000)
    May 26 09:42:34 phenom kernel: ACPI: FACS 0x00000000CFDA0000 000040
    May 26 09:42:34 phenom kernel: ACPI: SSDT 0x00000000CFDD8C40 000EDC (v01 PTLTD POWERNOW 00000001 LTP 00000001)
    May 26 09:42:34 phenom kernel: ACPI: MSDM 0x00000000CFDD9B40 000055 (v03 GBT GBTUACPI 42302E31 GBTU 01010101)
    May 26 09:42:34 phenom kernel: ACPI: HPET 0x00000000CFDD9BC0 000038 (v01 GBT GBTUACPI 42302E31 GBTU 00000098)
    May 26 09:42:34 phenom kernel: ACPI: MCFG 0x00000000CFDD9C00 00003C (v01 GBT GBTUACPI 42302E31 GBTU 01010101)
    May 26 09:42:34 phenom kernel: ACPI: MATS 0x00000000CFDD9C80 000034 (v01 GBT 00000000 00000000)
    May 26 09:42:34 phenom kernel: ACPI: TAMG 0x00000000CFDD9CF0 000202 (v01 GBT GBT B0 5455312E BG?? 53450101)
    May 26 09:42:34 phenom kernel: ACPI: APIC 0x00000000CFDD8B80 0000BC (v01 GBT GBTUACPI 42302E31 GBTU 01010101)
    May 26 09:42:34 phenom kernel: ACPI: MATS 0x00000000CFDD9F00 006207 (v01 MATS RCM 80000001 INTL 20061109)
    May 26 09:42:34 phenom kernel: ACPI: Local APIC address 0xfee00000
    May 26 09:42:34 phenom kernel: Scanning NUMA topology in Northbridge 24
    May 26 09:42:34 phenom kernel: No NUMA configuration found
    May 26 09:42:34 phenom kernel: Faking a node at [mem 0x0000000000000000-0x000000042fffffff]
    May 26 09:42:34 phenom kernel: NODE_DATA(0) allocated [mem 0x42fffa000-0x42fffdfff]
    May 26 09:42:34 phenom kernel: [ffffea0000000000-ffffea0010bfffff] PMD -> [ffff88041f600000-ffff88042f5fffff] on node 0
    May 26 09:42:34 phenom kernel: Zone ranges:
    May 26 09:42:34 phenom kernel: DMA [mem 0x0000000000001000-0x0000000000ffffff]
    May 26 09:42:34 phenom kernel: DMA32 [mem 0x0000000001000000-0x00000000ffffffff]
    May 26 09:42:34 phenom kernel: Normal [mem 0x0000000100000000-0x000000042fffffff]
    May 26 09:42:34 phenom kernel: Movable zone start for each node
    May 26 09:42:34 phenom kernel: Early memory node ranges
    May 26 09:42:34 phenom kernel: node 0: [mem 0x0000000000001000-0x0000000000099fff]
    May 26 09:42:34 phenom kernel: node 0: [mem 0x0000000000100000-0x00000000cfd9ffff]
    May 26 09:42:34 phenom kernel: node 0: [mem 0x0000000100000000-0x000000042fffffff]
    May 26 09:42:34 phenom kernel: Initmem setup node 0 [mem 0x0000000000001000-0x000000042fffffff]
    May 26 09:42:34 phenom kernel: On node 0 totalpages: 4193593
    May 26 09:42:34 phenom kernel: DMA zone: 64 pages used for memmap
    May 26 09:42:34 phenom kernel: DMA zone: 21 pages reserved
    May 26 09:42:34 phenom kernel: DMA zone: 3993 pages, LIFO batch:0
    May 26 09:42:34 phenom kernel: DMA32 zone: 13239 pages used for memmap
    May 26 09:42:34 phenom kernel: DMA32 zone: 847264 pages, LIFO batch:31
    May 26 09:42:34 phenom kernel: Normal zone: 52224 pages used for memmap
    May 26 09:42:34 phenom kernel: Normal zone: 3342336 pages, LIFO batch:31
    May 26 09:42:34 phenom kernel: ACPI: PM-Timer IO Port: 0x808
    May 26 09:42:34 phenom kernel: ACPI: Local APIC address 0xfee00000
    May 26 09:42:34 phenom kernel: ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
    May 26 09:42:34 phenom kernel: ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
    May 26 09:42:34 phenom kernel: ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled)
    May 26 09:42:34 phenom kernel: ACPI: LAPIC (acpi_id[0x03] lapic_id[0x03] enabled)
    May 26 09:42:34 phenom kernel: ACPI: LAPIC (acpi_id[0x04] lapic_id[0x04] enabled)
    May 26 09:42:34 phenom kernel: ACPI: LAPIC (acpi_id[0x05] lapic_id[0x05] enabled)
    May 26 09:42:34 phenom kernel: ACPI: LAPIC (acpi_id[0x06] lapic_id[0x06] disabled)
    May 26 09:42:34 phenom kernel: ACPI: LAPIC (acpi_id[0x07] lapic_id[0x07] disabled)
    May 26 09:42:34 phenom kernel: ACPI: LAPIC_NMI (acpi_id[0x00] dfl dfl lint[0x1])
    May 26 09:42:34 phenom kernel: ACPI: LAPIC_NMI (acpi_id[0x01] dfl dfl lint[0x1])
    May 26 09:42:34 phenom kernel: ACPI: LAPIC_NMI (acpi_id[0x02] dfl dfl lint[0x1])
    May 26 09:42:34 phenom kernel: ACPI: LAPIC_NMI (acpi_id[0x03] dfl dfl lint[0x1])
    May 26 09:42:34 phenom kernel: ACPI: LAPIC_NMI (acpi_id[0x04] dfl dfl lint[0x1])
    May 26 09:42:34 phenom kernel: ACPI: LAPIC_NMI (acpi_id[0x05] dfl dfl lint[0x1])
    May 26 09:42:34 phenom kernel: ACPI: LAPIC_NMI (acpi_id[0x06] dfl dfl lint[0x1])
    May 26 09:42:34 phenom kernel: ACPI: LAPIC_NMI (acpi_id[0x07] dfl dfl lint[0x1])
    May 26 09:42:34 phenom kernel: ACPI: IOAPIC (id[0x08] address[0xfec00000] gsi_base[0])
    May 26 09:42:34 phenom kernel: IOAPIC[0]: apic_id 8, version 33, address 0xfec00000, GSI 0-23
    May 26 09:42:34 phenom kernel: ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
    May 26 09:42:34 phenom kernel: ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 low level)
    May 26 09:42:34 phenom kernel: ACPI: IRQ0 used by override.
    May 26 09:42:34 phenom kernel: ACPI: IRQ9 used by override.
    May 26 09:42:34 phenom kernel: Using ACPI (MADT) for SMP configuration information
    May 26 09:42:34 phenom kernel: ACPI: HPET id: 0x10b9a201 base: 0xfed00000
    May 26 09:42:34 phenom kernel: smpboot: Allowing 8 CPUs, 2 hotplug CPUs
    May 26 09:42:34 phenom kernel: PM: Registered nosave memory: [mem 0x00000000-0x00000fff]
    May 26 09:42:34 phenom kernel: PM: Registered nosave memory: [mem 0x0009a000-0x0009ffff]
    May 26 09:42:34 phenom kernel: PM: Registered nosave memory: [mem 0x000a0000-0x000effff]
    May 26 09:42:34 phenom kernel: PM: Registered nosave memory: [mem 0x000f0000-0x000fffff]
    May 26 09:42:34 phenom kernel: PM: Registered nosave memory: [mem 0xcfda0000-0xcfdd0fff]
    May 26 09:42:34 phenom kernel: PM: Registered nosave memory: [mem 0xcfdd1000-0xcfdfffff]
    May 26 09:42:34 phenom kernel: PM: Registered nosave memory: [mem 0xcfe00000-0xcfefffff]
    May 26 09:42:34 phenom kernel: PM: Registered nosave memory: [mem 0xcff00000-0xdfffffff]
    May 26 09:42:34 phenom kernel: PM: Registered nosave memory: [mem 0xe0000000-0xefffffff]
    May 26 09:42:34 phenom kernel: PM: Registered nosave memory: [mem 0xf0000000-0xfebfffff]
    May 26 09:42:34 phenom kernel: PM: Registered nosave memory: [mem 0xfec00000-0xffffffff]
    May 26 09:42:34 phenom kernel: e820: [mem 0xcff00000-0xdfffffff] available for PCI devices
    May 26 09:42:34 phenom kernel: Booting paravirtualized kernel on bare hardware
    May 26 09:42:34 phenom kernel: setup_percpu: NR_CPUS:128 nr_cpumask_bits:128 nr_cpu_ids:8 nr_node_ids:1
    May 26 09:42:34 phenom kernel: PERCPU: Embedded 31 pages/cpu @ffff88042fc00000 s86232 r8192 d32552 u262144
    May 26 09:42:34 phenom kernel: pcpu-alloc: s86232 r8192 d32552 u262144 alloc=1*2097152
    May 26 09:42:34 phenom kernel: pcpu-alloc: [0] 0 1 2 3 4 5 6 7
    May 26 09:42:34 phenom kernel: Built 1 zonelists in Node order, mobility grouping on. Total pages: 4128045
    May 26 09:42:34 phenom kernel: Policy zone: Normal
    May 26 09:42:34 phenom kernel: Kernel command line: BOOT_IMAGE=/boot/vmlinuz-linux root=UUID=d36ad497-1614-4cc5-8cc9-da2d5e5a417c rw
    May 26 09:42:34 phenom kernel: PID hash table entries: 4096 (order: 3, 32768 bytes)
    May 26 09:42:34 phenom kernel: AGP: Checking aperture...
    May 26 09:42:34 phenom kernel: AGP: No AGP bridge found
    May 26 09:42:34 phenom kernel: AGP: Node 0: aperture [bus addr 0xc4000000-0xc5ffffff] (32MB)
    May 26 09:42:34 phenom kernel: Aperture pointing to e820 RAM. Ignoring.
    May 26 09:42:34 phenom kernel: AGP: Your BIOS doesn't leave a aperture memory hole
    May 26 09:42:34 phenom kernel: AGP: Please enable the IOMMU option in the BIOS setup
    May 26 09:42:34 phenom kernel: AGP: This costs you 64MB of RAM
    May 26 09:42:34 phenom kernel: AGP: Mapping aperture over RAM [mem 0xc4000000-0xc7ffffff] (65536KB)
    May 26 09:42:34 phenom kernel: PM: Registered nosave memory: [mem 0xc4000000-0xc7ffffff]
    May 26 09:42:34 phenom kernel: Memory: 16352908K/16774372K available (5628K kernel code, 840K rwdata, 1784K rodata, 1160K init, 1152K bss, 421464K reserved, 0K cma-reserved)
    May 26 09:42:34 phenom kernel: SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=8, Nodes=1
    May 26 09:42:34 phenom kernel: Preemptible hierarchical RCU implementation.
    May 26 09:42:34 phenom kernel: RCU dyntick-idle grace-period acceleration is enabled.
    May 26 09:42:34 phenom kernel: RCU restricting CPUs from NR_CPUS=128 to nr_cpu_ids=8.
    May 26 09:42:34 phenom kernel: RCU: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=8
    May 26 09:42:34 phenom kernel: NR_IRQS:8448 nr_irqs:488 16
    May 26 09:42:34 phenom kernel: spurious 8259A interrupt: IRQ7.
    May 26 09:42:34 phenom kernel: Console: colour dummy device 80x25
    May 26 09:42:34 phenom kernel: console [tty0] enabled
    May 26 09:42:34 phenom kernel: hpet clockevent registered
    May 26 09:42:34 phenom kernel: tsc: Fast TSC calibration using PIT
    May 26 09:42:34 phenom kernel: tsc: Detected 3300.124 MHz processor
    May 26 09:42:34 phenom kernel: Calibrating delay loop (skipped), value calculated using timer frequency.. 6602.25 BogoMIPS (lpj=11000413)
    May 26 09:42:34 phenom kernel: pid_max: default: 32768 minimum: 301
    May 26 09:42:34 phenom kernel: ACPI: Core revision 20150204
    May 26 09:42:34 phenom kernel: ACPI: All ACPI Tables successfully acquired
    May 26 09:42:34 phenom kernel: Security Framework initialized
    May 26 09:42:34 phenom kernel: Yama: becoming mindful.
    May 26 09:42:34 phenom kernel: Dentry cache hash table entries: 2097152 (order: 12, 16777216 bytes)
    May 26 09:42:34 phenom kernel: Inode-cache hash table entries: 1048576 (order: 11, 8388608 bytes)
    May 26 09:42:34 phenom kernel: Mount-cache hash table entries: 32768 (order: 6, 262144 bytes)
    May 26 09:42:34 phenom kernel: Mountpoint-cache hash table entries: 32768 (order: 6, 262144 bytes)
    May 26 09:42:34 phenom kernel: Initializing cgroup subsys blkio
    May 26 09:42:34 phenom kernel: Initializing cgroup subsys memory
    May 26 09:42:34 phenom kernel: Initializing cgroup subsys devices
    May 26 09:42:34 phenom kernel: Initializing cgroup subsys freezer
    May 26 09:42:34 phenom kernel: Initializing cgroup subsys net_cls
    May 26 09:42:34 phenom kernel: CPU: Physical Processor ID: 0
    May 26 09:42:34 phenom kernel: CPU: Processor Core ID: 0
    May 26 09:42:34 phenom kernel: mce: CPU supports 6 MCE banks
    May 26 09:42:34 phenom kernel: LVT offset 0 assigned for vector 0xf9
    May 26 09:42:34 phenom kernel: process: using AMD E400 aware idle routine
    May 26 09:42:34 phenom kernel: Last level iTLB entries: 4KB 512, 2MB 16, 4MB 8
    May 26 09:42:34 phenom kernel: Last level dTLB entries: 4KB 512, 2MB 128, 4MB 64, 1GB 0
    May 26 09:42:34 phenom kernel: Freeing SMP alternatives memory: 20K (ffffffff819f6000 - ffffffff819fb000)
    May 26 09:42:34 phenom kernel: ftrace: allocating 21316 entries in 84 pages
    May 26 09:42:34 phenom kernel: ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
    May 26 09:42:34 phenom kernel: smpboot: CPU0: AMD Phenom(tm) II X6 1100T Processor (fam: 10, model: 0a, stepping: 00)
    May 26 09:42:34 phenom kernel: Performance Events: AMD PMU driver.
    May 26 09:42:34 phenom kernel: ... version: 0
    May 26 09:42:34 phenom kernel: ... bit width: 48
    May 26 09:42:34 phenom kernel: ... generic registers: 4
    May 26 09:42:34 phenom kernel: ... value mask: 0000ffffffffffff
    May 26 09:42:34 phenom kernel: ... max period: 00007fffffffffff
    May 26 09:42:34 phenom kernel: ... fixed-purpose events: 0
    May 26 09:42:34 phenom kernel: ... event mask: 000000000000000f
    May 26 09:42:34 phenom kernel: process: System has AMD C1E enabled
    May 26 09:42:34 phenom kernel: process: Switch to broadcast mode on CPU0
    May 26 09:42:34 phenom kernel: NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
    May 26 09:42:34 phenom kernel: x86: Booting SMP configuration:
    May 26 09:42:34 phenom kernel: .... node #0, CPUs: #1
    May 26 09:42:34 phenom kernel: process: Switch to broadcast mode on CPU1
    May 26 09:42:34 phenom kernel: #2
    May 26 09:42:34 phenom kernel: process: Switch to broadcast mode on CPU2
    May 26 09:42:34 phenom kernel: #3
    May 26 09:42:34 phenom kernel: process: Switch to broadcast mode on CPU3
    May 26 09:42:34 phenom kernel: #4
    May 26 09:42:34 phenom kernel: process: Switch to broadcast mode on CPU4
    May 26 09:42:34 phenom kernel: #5
    May 26 09:42:34 phenom kernel: x86: Booted up 1 node, 6 CPUs
    May 26 09:42:34 phenom kernel: smpboot: Total of 6 processors activated (39617.54 BogoMIPS)
    May 26 09:42:34 phenom kernel: process: Switch to broadcast mode on CPU5
    May 26 09:42:34 phenom kernel: devtmpfs: initialized
    May 26 09:42:34 phenom kernel: PM: Registering ACPI NVS region [mem 0xcfda0000-0xcfdd0fff] (200704 bytes)
    May 26 09:42:34 phenom kernel: pinctrl core: initialized pinctrl subsystem
    May 26 09:42:34 phenom kernel: RTC time: 7:42:28, date: 05/26/15
    May 26 09:42:34 phenom kernel: NET: Registered protocol family 16
    May 26 09:42:34 phenom kernel: cpuidle: using governor ladder
    May 26 09:42:34 phenom kernel: cpuidle: using governor menu
    May 26 09:42:34 phenom kernel: node 0 link 0: io port [9000, ffff]
    May 26 09:42:34 phenom kernel: TOM: 00000000d0000000 aka 3328M
    May 26 09:42:34 phenom kernel: Fam 10h mmconf [mem 0xe0000000-0xe00fffff]
    May 26 09:42:34 phenom kernel: node 0 link 0: mmio [a0000, bffff]
    May 26 09:42:34 phenom kernel: node 0 link 0: mmio [d0000000, dfffffff]
    May 26 09:42:34 phenom kernel: node 0 link 0: mmio [f0000000, ffffffff]
    May 26 09:42:34 phenom kernel: node 0 link 0: mmio [e0000000, e06fffff] ==> [e0100000, e06fffff]
    May 26 09:42:34 phenom kernel: TOM2: 0000000430000000 aka 17152M
    May 26 09:42:34 phenom kernel: bus: [bus 00-06] on node 0 link 0
    May 26 09:42:34 phenom kernel: bus: 00 [io 0x0000-0xffff]
    May 26 09:42:34 phenom kernel: bus: 00 [mem 0x000a0000-0x000bffff]
    May 26 09:42:34 phenom kernel: bus: 00 [mem 0xd0000000-0xdfffffff]
    May 26 09:42:34 phenom kernel: bus: 00 [mem 0xe0700000-0xffffffff]
    May 26 09:42:34 phenom kernel: bus: 00 [mem 0xe0100000-0xe06fffff]
    May 26 09:42:34 phenom kernel: bus: 00 [mem 0x430000000-0xfcffffffff]
    May 26 09:42:34 phenom kernel: ACPI: bus type PCI registered
    May 26 09:42:34 phenom kernel: acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
    May 26 09:42:34 phenom kernel: PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0xe0000000-0xefffffff] (base 0xe0000000)
    May 26 09:42:34 phenom kernel: PCI: MMCONFIG at [mem 0xe0000000-0xefffffff] reserved in E820
    May 26 09:42:34 phenom kernel: PCI: Using configuration type 1 for base access
    May 26 09:42:34 phenom kernel: mtrr: your CPUs had inconsistent variable MTRR settings
    May 26 09:42:34 phenom kernel: mtrr: probably your BIOS does not setup all CPUs.
    May 26 09:42:34 phenom kernel: mtrr: corrected configuration.
    May 26 09:42:34 phenom kernel: ACPI: Added _OSI(Module Device)
    May 26 09:42:34 phenom kernel: ACPI: Added _OSI(Processor Device)
    May 26 09:42:34 phenom kernel: ACPI: Added _OSI(3.0 _SCP Extensions)
    May 26 09:42:34 phenom kernel: ACPI: Added _OSI(Processor Aggregator Device)
    May 26 09:42:34 phenom kernel: ACPI: Actual Package length (1) is larger than NumElements field (0), truncated
    May 26 09:42:34 phenom kernel: ACPI: Actual Package length (1) is larger than NumElements field (0), truncated
    May 26 09:42:34 phenom kernel: ACPI: Actual Package length (1) is larger than NumElements field (0), truncated
    May 26 09:42:34 phenom kernel: ACPI: Actual Package length (1) is larger than NumElements field (0), truncated
    May 26 09:42:34 phenom kernel: ACPI: Interpreter enabled
    May 26 09:42:34 phenom kernel: ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S1_] (20150204/hwxface-580)
    May 26 09:42:34 phenom kernel: ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20150204/hwxface-580)
    May 26 09:42:34 phenom kernel: ACPI: (supports S0 S3 S4 S5)
    May 26 09:42:34 phenom kernel: ACPI: Using IOAPIC for interrupt routing
    May 26 09:42:34 phenom kernel: PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
    May 26 09:42:34 phenom kernel: ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-ff])
    May 26 09:42:34 phenom kernel: acpi PNP0A03:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
    May 26 09:42:34 phenom kernel: acpi PNP0A03:00: _OSC failed (AE_NOT_FOUND); disabling ASPM
    May 26 09:42:34 phenom kernel: PCI host bridge to bus 0000:00
    May 26 09:42:34 phenom kernel: pci_bus 0000:00: root bus resource [bus 00-ff]
    May 26 09:42:34 phenom kernel: pci_bus 0000:00: root bus resource [io 0x0000-0x0cf7 window]
    May 26 09:42:34 phenom kernel: pci_bus 0000:00: root bus resource [io 0x0d00-0xffff window]
    May 26 09:42:34 phenom kernel: pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff window]
    May 26 09:42:34 phenom kernel: pci_bus 0000:00: root bus resource [mem 0x000c0000-0x000dffff window]
    May 26 09:42:34 phenom kernel: pci_bus 0000:00: root bus resource [mem 0xfed40000-0xfed44fff window]
    May 26 09:42:34 phenom kernel: pci_bus 0000:00: root bus resource [mem 0xd0000000-0xfebfffff window]
    May 26 09:42:34 phenom kernel: pci 0000:00:00.0: [1002:5a14] type 00 class 0x060000
    May 26 09:42:34 phenom kernel: pci 0000:00:00.0: [Firmware Bug]: reg 0x1c: invalid BAR (can't size)
    May 26 09:42:34 phenom kernel: pci 0000:00:02.0: [1002:5a16] type 01 class 0x060400
    May 26 09:42:34 phenom kernel: pci 0000:00:02.0: PME# supported from D0 D3hot D3cold
    May 26 09:42:34 phenom kernel: pci 0000:00:02.0: System wakeup disabled by ACPI
    May 26 09:42:34 phenom kernel: pci 0000:00:04.0: [1002:5a18] type 01 class 0x060400
    May 26 09:42:34 phenom kernel: pci 0000:00:04.0: PME# supported from D0 D3hot D3cold
    May 26 09:42:34 phenom kernel: pci 0000:00:04.0: System wakeup disabled by ACPI
    May 26 09:42:34 phenom kernel: pci 0000:00:09.0: [1002:5a1c] type 01 class 0x060400
    May 26 09:42:34 phenom kernel: pci 0000:00:09.0: PME# supported from D0 D3hot D3cold
    May 26 09:42:34 phenom kernel: pci 0000:00:09.0: System wakeup disabled by ACPI
    May 26 09:42:34 phenom kernel: pci 0000:00:0a.0: [1002:5a1d] type 01 class 0x060400
    May 26 09:42:34 phenom kernel: pci 0000:00:0a.0: PME# supported from D0 D3hot D3cold
    May 26 09:42:34 phenom kernel: pci 0000:00:0a.0: System wakeup disabled by ACPI
    May 26 09:42:34 phenom kernel: pci 0000:00:11.0: [1002:4391] type 00 class 0x010601
    May 26 09:42:34 phenom kernel: pci 0000:00:11.0: reg 0x10: [io 0xff00-0xff07]
    May 26 09:42:34 phenom kernel: pci 0000:00:11.0: reg 0x14: [io 0xfe00-0xfe03]
    May 26 09:42:34 phenom kernel: pci 0000:00:11.0: reg 0x18: [io 0xfd00-0xfd07]
    May 26 09:42:34 phenom kernel: pci 0000:00:11.0: reg 0x1c: [io 0xfc00-0xfc03]
    May 26 09:42:34 phenom kernel: pci 0000:00:11.0: reg 0x20: [io 0xfb00-0xfb0f]
    May 26 09:42:34 phenom kernel: pci 0000:00:11.0: reg 0x24: [mem 0xfdfff000-0xfdfff3ff]
    May 26 09:42:34 phenom kernel: pci 0000:00:12.0: [1002:4397] type 00 class 0x0c0310
    May 26 09:42:34 phenom kernel: pci 0000:00:12.0: reg 0x10: [mem 0xfdffe000-0xfdffefff]
    May 26 09:42:34 phenom kernel: pci 0000:00:12.0: System wakeup disabled by ACPI
    May 26 09:42:34 phenom kernel: pci 0000:00:12.2: [1002:4396] type 00 class 0x0c0320
    May 26 09:42:34 phenom kernel: pci 0000:00:12.2: reg 0x10: [mem 0xfdffd000-0xfdffd0ff]
    May 26 09:42:34 phenom kernel: pci 0000:00:12.2: supports D1 D2
    May 26 09:42:34 phenom kernel: pci 0000:00:12.2: PME# supported from D0 D1 D2 D3hot
    May 26 09:42:34 phenom kernel: pci 0000:00:12.2: System wakeup disabled by ACPI
    May 26 09:42:34 phenom kernel: pci 0000:00:13.0: [1002:4397] type 00 class 0x0c0310
    May 26 09:42:34 phenom kernel: pci 0000:00:13.0: reg 0x10: [mem 0xfdffc000-0xfdffcfff]
    May 26 09:42:34 phenom kernel: pci 0000:00:13.0: System wakeup disabled by ACPI
    May 26 09:42:34 phenom kernel: pci 0000:00:13.2: [1002:4396] type 00 class 0x0c0320
    May 26 09:42:34 phenom kernel: pci 0000:00:13.2: reg 0x10: [mem 0xfdffb000-0xfdffb0ff]
    May 26 09:42:34 phenom kernel: pci 0000:00:13.2: supports D1 D2
    May 26 09:42:34 phenom kernel: pci 0000:00:13.2: PME# supported from D0 D1 D2 D3hot
    May 26 09:42:34 phenom kernel: pci 0000:00:13.2: System wakeup disabled by ACPI
    May 26 09:42:34 phenom kernel: pci 0000:00:14.0: [1002:4385] type 00 class 0x0c0500
    May 26 09:42:34 phenom kernel: pci 0000:00:14.1: [1002:439c] type 00 class 0x01018a
    May 26 09:42:34 phenom kernel: pci 0000:00:14.1: reg 0x10: [io 0x0000-0x0007]
    May 26 09:42:34 phenom kernel: pci 0000:00:14.1: reg 0x14: [io 0x0000-0x0003]
    May 26 09:42:34 phenom kernel: pci 0000:00:14.1: reg 0x18: [io 0x0000-0x0007]
    May 26 09:42:34 phenom kernel: pci 0000:00:14.1: reg 0x1c: [io 0x0000-0x0003]
    May 26 09:42:34 phenom kernel: pci 0000:00:14.1: reg 0x20: [io 0xfa00-0xfa0f]
    May 26 09:42:34 phenom kernel: pci 0000:00:14.1: legacy IDE quirk: reg 0x10: [io 0x01f0-0x01f7]
    May 26 09:42:34 phenom kernel: pci 0000:00:14.1: legacy IDE quirk: reg 0x14: [io 0x03f6]
    May 26 09:42:34 phenom kernel: pci 0000:00:14.1: legacy IDE quirk: reg 0x18: [io 0x0170-0x0177]
    May 26 09:42:34 phenom kernel: pci 0000:00:14.1: legacy IDE quirk: reg 0x1c: [io 0x0376]
    May 26 09:42:34 phenom kernel: pci 0000:00:14.2: [1002:4383] type 00 class 0x040300
    May 26 09:42:34 phenom kernel: pci 0000:00:14.2: reg 0x10: [mem 0xfdff4000-0xfdff7fff 64bit]
    May 26 09:42:34 phenom kernel: pci 0000:00:14.2: PME# supported from D0 D3hot D3cold
    May 26 09:42:34 phenom kernel: pci 0000:00:14.2: System wakeup disabled by ACPI
    May 26 09:42:34 phenom kernel: pci 0000:00:14.3: [1002:439d] type 00 class 0x060100
    May 26 09:42:34 phenom kernel: pci 0000:00:14.4: [1002:4384] type 01 class 0x060401
    May 26 09:42:34 phenom kernel: pci 0000:00:14.4: System wakeup disabled by ACPI
    May 26 09:42:34 phenom kernel: pci 0000:00:14.5: [1002:4399] type 00 class 0x0c0310
    May 26 09:42:34 phenom kernel: pci 0000:00:14.5: reg 0x10: [mem 0xfdffa000-0xfdffafff]
    May 26 09:42:34 phenom kernel: pci 0000:00:14.5: System wakeup disabled by ACPI
    May 26 09:42:34 phenom kernel: pci 0000:00:15.0: [1002:43a0] type 01 class 0x060400
    May 26 09:42:34 phenom kernel: pci 0000:00:15.0: supports D1 D2
    May 26 09:42:34 phenom kernel: pci 0000:00:15.0: System wakeup disabled by ACPI
    May 26 09:42:34 phenom kernel: pci 0000:00:16.0: [1002:4397] type 00 class 0x0c0310
    May 26 09:42:34 phenom kernel: pci 0000:00:16.0: reg 0x10: [mem 0xfdff9000-0xfdff9fff]
    May 26 09:42:34 phenom kernel: pci 0000:00:16.0: System wakeup disabled by ACPI
    May 26 09:42:34 phenom kernel: pci 0000:00:16.2: [1002:4396] type 00 class 0x0c0320
    May 26 09:42:34 phenom kernel: pci 0000:00:16.2: reg 0x10: [mem 0xfdff8000-0xfdff80ff]
    May 26 09:42:34 phenom kernel: pci 0000:00:16.2: supports D1 D2
    May 26 09:42:34 phenom kernel: pci 0000:00:16.2: PME# supported from D0 D1 D2 D3hot
    May 26 09:42:34 phenom kernel: pci 0000:00:16.2: System wakeup disabled by ACPI
    May 26 09:42:34 phenom kernel: pci 0000:00:18.0: [1022:1200] type 00 class 0x060000
    May 26 09:42:34 phenom kernel: pci 0000:00:18.1: [1022:1201] type 00 class 0x060000
    May 26 09:42:34 phenom kernel: pci 0000:00:18.2: [1022:1202] type 00 class 0x060000
    May 26 09:42:34 phenom kernel: pci 0000:00:18.3: [1022:1203] type 00 class 0x060000
    May 26 09:42:34 phenom kernel: pci 0000:00:18.4: [1022:1204] type 00 class 0x060000
    May 26 09:42:34 phenom kernel: pci 0000:01:00.0: [1002:6779] type 00 class 0x030000
    May 26 09:42:34 phenom kernel: pci 0000:01:00.0: reg 0x10: [mem 0xd0000000-0xdfffffff 64bit pref]
    May 26 09:42:34 phenom kernel: pci 0000:01:00.0: reg 0x18: [mem 0xfd5c0000-0xfd5dffff 64bit]
    May 26 09:42:34 phenom kernel: pci 0000:01:00.0: reg 0x20: [io 0xce00-0xceff]
    May 26 09:42:34 phenom kernel: pci 0000:01:00.0: reg 0x30: [mem 0x00000000-0x0001ffff pref]
    May 26 09:42:34 phenom kernel: pci 0000:01:00.0: supports D1 D2
    May 26 09:42:34 phenom kernel: pci 0000:01:00.1: [1002:aa98] type 00 class 0x040300
    May 26 09:42:34 phenom kernel: pci 0000:01:00.1: reg 0x10: [mem 0xfd5fc000-0xfd5fffff 64bit]
    May 26 09:42:34 phenom kernel: pci 0000:01:00.1: supports D1 D2
    May 26 09:42:34 phenom kernel: pci 0000:00:02.0: PCI bridge to [bus 01]
    May 26 09:42:34 phenom kernel: pci 0000:00:02.0: bridge window [io 0xc000-0xcfff]
    May 26 09:42:34 phenom kernel: pci 0000:00:02.0: bridge window [mem 0xfd500000-0xfd5fffff]
    May 26 09:42:34 phenom kernel: pci 0000:00:02.0: bridge window [mem 0xd0000000-0xdfffffff 64bit pref]
    May 26 09:42:34 phenom kernel: pci 0000:02:00.0: [1b6f:7023] type 00 class 0x0c0330
    May 26 09:42:34 phenom kernel: pci 0000:02:00.0: reg 0x10: [mem 0xfd4f8000-0xfd4fffff 64bit]
    May 26 09:42:34 phenom kernel: pci 0000:02:00.0: supports D1 D2
    May 26 09:42:34 phenom kernel: pci 0000:02:00.0: PME# supported from D0 D1 D2 D3hot D3cold
    May 26 09:42:34 phenom kernel: pci 0000:00:04.0: PCI bridge to [bus 02]
    May 26 09:42:34 phenom kernel: pci 0000:00:04.0: bridge window [io 0xb000-0xbfff]
    May 26 09:42:34 phenom kernel: pci 0000:00:04.0: bridge window [mem 0xfd400000-0xfd4fffff]
    May 26 09:42:34 phenom kernel: pci 0000:00:04.0: bridge window [mem 0xfde00000-0xfdefffff 64bit pref]
    May 26 09:42:34 phenom kernel: pci 0000:03:00.0: [10ec:8168] type 00 class 0x020000
    May 26 09:42:34 phenom kernel: pci 0000:03:00.0: reg 0x10: [io 0xee00-0xeeff]
    May 26 09:42:34 phenom kernel: pci 0000:03:00.0: reg 0x18: [mem 0xfdcff000-0xfdcfffff 64bit pref]
    May 26 09:42:34 phenom kernel: pci 0000:03:00.0: reg 0x20: [mem 0xfdcf8000-0xfdcfbfff 64bit pref]
    May 26 09:42:34 phenom kernel: pci 0000:03:00.0: supports D1 D2
    May 26 09:42:34 phenom kernel: pci 0000:03:00.0: PME# supported from D0 D1 D2 D3hot D3cold
    May 26 09:42:34 phenom kernel: pci 0000:00:09.0: PCI bridge to [bus 03]
    May 26 09:42:34 phenom kernel: pci 0000:00:09.0: bridge window [io 0xe000-0xefff]
    May 26 09:42:34 phenom kernel: pci 0000:00:09.0: bridge window [mem 0xfdd00000-0xfddfffff]
    May 26 09:42:34 phenom kernel: pci 0000:00:09.0: bridge window [mem 0xfdc00000-0xfdcfffff 64bit pref]
    May 26 09:42:34 phenom kernel: pci 0000:04:00.0: [1b6f:7023] type 00 class 0x0c0330
    May 26 09:42:34 phenom kernel: pci 0000:04:00.0: reg 0x10: [mem 0xfdbf8000-0xfdbfffff 64bit]
    May 26 09:42:34 phenom kernel: pci 0000:04:00.0: supports D1 D2
    May 26 09:42:34 phenom kernel: pci 0000:04:00.0: PME# supported from D0 D1 D2 D3hot D3cold
    May 26 09:42:34 phenom kernel: pci 0000:00:0a.0: PCI bridge to [bus 04]
    May 26 09:42:34 phenom kernel: pci 0000:00:0a.0: bridge window [io 0xd000-0xdfff]
    May 26 09:42:34 phenom kernel: pci 0000:00:0a.0: bridge window [mem 0xfdb00000-0xfdbfffff]
    May 26 09:42:34 phenom kernel: pci 0000:00:0a.0: bridge window [mem 0xfd800000-0xfd8fffff 64bit pref]
    May 26 09:42:34 phenom kernel: pci 0000:05:0e.0: [1106:3044] type 00 class 0x0c0010
    May 26 09:42:34 phenom kernel: pci 0000:05:0e.0: reg 0x10: [mem 0xfdaff000-0xfdaff7ff]
    May 26 09:42:34 phenom kernel: pci 0000:05:0e.0: reg 0x14: [io 0xaf00-0xaf7f]
    May 26 09:42:34 phenom kernel: pci 0000:05:0e.0: supports D2
    May 26 09:42:34 phenom kernel: pci 0000:05:0e.0: PME# supported from D2 D3hot D3cold
    May 26 09:42:34 phenom kernel: pci 0000:00:14.4: PCI bridge to [bus 05] (subtractive decode)
    May 26 09:42:34 phenom kernel: pci 0000:00:14.4: bridge window [io 0xa000-0xafff]
    May 26 09:42:34 phenom kernel: pci 0000:00:14.4: bridge window [mem 0xfda00000-0xfdafffff]
    May 26 09:42:34 phenom kernel: pci 0000:00:14.4: bridge window [mem 0xfd900000-0xfd9fffff pref]
    May 26 09:42:34 phenom kernel: pci 0000:00:14.4: bridge window [io 0x0000-0x0cf7 window] (subtractive decode)
    May 26 09:42:34 phenom kernel: pci 0000:00:14.4: bridge window [io 0x0d00-0xffff window] (subtractive decode)
    May 26 09:42:34 phenom kernel: pci 0000:00:14.4: bridge window [mem 0x000a0000-0x000bffff window] (subtractive decode)
    May 26 09:42:34 phenom kernel: pci 0000:00:14.4: bridge window [mem 0x000c0000-0x000dffff window] (subtractive decode)
    May 26 09:42:34 phenom kernel: pci 0000:00:14.4: bridge window [mem 0xfed40000-0xfed44fff window] (subtractive decode)
    May 26 09:42:34 phenom kernel: pci 0000:00:14.4: bridge window [mem 0xd0000000-0xfebfffff window] (subtractive decode)
    May 26 09:42:34 phenom kernel: pci 0000:00:15.0: PCI bridge to [bus 06]
    May 26 09:42:34 phenom kernel: pci 0000:00:15.0: bridge window [io 0x9000-0x9fff]
    May 26 09:42:34 phenom kernel: pci 0000:00:15.0: bridge window [mem 0xfd700000-0xfd7fffff]
    May 26 09:42:34 phenom kernel: pci 0000:00:15.0: bridge window [mem 0xfd600000-0xfd6fffff 64bit pref]
    May 26 09:42:34 phenom kernel: pci_bus 0000:00: on NUMA node 0
    May 26 09:42:34 phenom kernel: ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 10 11) *0
    May 26 09:42:34 phenom kernel: ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 10 11) *0
    May 26 09:42:34 phenom kernel: ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 6 7 10 11) *0
    May 26 09:42:34 phenom kernel: ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 7 10 11) *0
    May 26 09:42:34 phenom kernel: ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 11) *0
    May 26 09:42:34 phenom kernel: ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 10 11) *0
    May 26 09:42:34 phenom kernel: ACPI: PCI Interrupt Link [LNK0] (IRQs 3 4 5 6 7 10 11) *0
    May 26 09:42:34 phenom kernel: ACPI: PCI Interrupt Link [LNK1] (IRQs 3 4 5 6 7 10 11) *0
    May 26 09:42:34 phenom kernel: vgaarb: setting as boot device: PCI:0000:01:00.0
    May 26 09:42:34 phenom kernel: vgaarb: device added: PCI:0000:01:00.0,decodes=io+mem,owns=io+mem,locks=none
    May 26 09:42:34 phenom kernel: vgaarb: loaded
    May 26 09:42:34 phenom kernel: vgaarb: bridge control possible 0000:01:00.0
    May 26 09:42:34 phenom kernel: PCI: Using ACPI for IRQ routing
    May 26 09:42:34 phenom kernel: PCI: pci_cache_line_size set to 64 bytes
    May 26 09:42:34 phenom kernel: e820: reserve RAM buffer [mem 0x0009a000-0x0009ffff]
    May 26 09:42:34 phenom kernel: e820: reserve RAM buffer [mem 0xcfda0000-0xcfffffff]
    May 26 09:42:34 phenom kernel: NetLabel: Initializing
    May 26 09:42:34 phenom kernel: NetLabel: domain hash size = 128
    May 26 09:42:34 phenom kernel: NetLabel: protocols = UNLABELED CIPSOv4
    May 26 09:42:34 phenom kernel: NetLabel: unlabeled traffic allowed by default
    May 26 09:42:34 phenom kernel: hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0
    May 26 09:42:34 phenom kernel: hpet0: 3 comparators, 32-bit 14.318180 MHz counter
    May 26 09:42:34 phenom kernel: Switched to clocksource hpet
    May 26 09:42:34 phenom kernel: pnp: PnP ACPI init
    May 26 09:42:34 phenom kernel: system 00:00: [io 0x04d0-0x04d1] has been reserved
    May 26 09:42:34 phenom kernel: system 00:00: [io 0x0220-0x0225] has been reserved
    May 26 09:42:34 phenom kernel: system 00:00: [io 0x0290-0x0294] has been reserved
    May 26 09:42:34 phenom kernel: system 00:00: Plug and Play ACPI device, IDs PNP0c02 (active)
    May 26 09:42:34 phenom kernel: pnp 00:01: disabling [mem 0x00000000-0x00000fff window] because it overlaps 0000:01:00.0 BAR 6 [mem 0x00000000-0x0001ffff pref]
    May 26 09:42:34 phenom kernel: system 00:01: [io 0x0900-0x091f] has been reserved
    May 26 09:42:34 phenom kernel: system 00:01: [io 0x0228-0x022f] has been reserved
    May 26 09:42:34 phenom kernel: system 00:01: [io 0x040b] has been reserved
    May 26 09:42:34 phenom kernel: system 00:01: [io 0x04d6] has been reserved
    May 26 09:42:34 phenom kernel: system 00:01: [io 0x0c00-0x0c01] has been reserved
    May 26 09:42:34 phenom kernel: system 00:01: [io 0x0c14] has been reserved
    May 26 09:42:34 phenom kernel: system 00:01: [io 0x0c50-0x0c52] has been reserved
    May 26 09:42:34 phenom kernel: system 00:01: [io 0x0c6c-0x0c6d] has been reserved
    May 26 09:42:34 phenom kernel: system 00:01: [io 0x0c6f] has been reserved
    May 26 09:42:34 phenom kernel: system 00:01: [io 0x0cd0-0x0cd1] has been reserved
    May 26 09:42:34 phenom kernel: system 00:01: [io 0x0cd2-0x0cd3] has been reserved
    May 26 09:42:34 phenom kernel: system 00:01: [io 0x0cd4-0x0cdf] has been reserved
    May 26 09:42:34 phenom kernel: system 00:01: [io 0x0800-0x08fe] could not be reserved
    May 26 09:42:34 phenom kernel: system 00:01: [io 0x0a10-0x0a17] has been reserved
    May 26 09:42:34 phenom kernel: system 00:01: [io 0x0b00-0x0b0f] has been reserved
    May 26 09:42:34 phenom kernel: system 00:01: [io 0x0b10-0x0b1f] has been reserved
    May 26 09:42:34 phenom kernel: system 00:01: [io 0x0b20-0x0b3f] has been reserved
    May 26 09:42:34 phenom kernel: system 00:01: [mem 0xfee00400-0xfee00fff window] has been reserved
    May 26 09:42:34 phenom kernel: system 00:01: Plug and Play ACPI device, IDs PNP0c02 (active)
    May 26 09:42:34 phenom kernel: pnp 00:02: Plug and Play ACPI device, IDs PNP0b00 (active)
    May 26 09:42:34 phenom kernel: pnp 00:03: Plug and Play ACPI device, IDs PNP0501 (active)
    May 26 09:42:34 phenom kernel: system 00:04: [mem 0xe0000000-0xefffffff] has been reserved
    May 26 09:42:34 phenom kernel: system 00:04: Plug and Play ACPI device, IDs PNP0c02 (active)
    May 26 09:42:34 phenom kernel: system 00:05: [mem 0x000d4200-0x000d7fff] has been reserved
    May 26 09:42:34 phenom kernel: system 00:05: [mem 0x000f0000-0x000f7fff] could not be reserved
    May 26 09:42:34 phenom kernel: system 00:05: [mem 0x000f8000-0x000fbfff] could not be reserved
    May 26 09:42:34 phenom kernel: system 00:05: [mem 0x000fc000-0x000fffff] could not be reserved
    May 26 09:42:34 phenom kernel: system 00:05: [mem 0xcfda0000-0xcfdfffff] could not be reserved
    May 26 09:42:34 phenom kernel: system 00:05: [mem 0xffff0000-0xffffffff] has been reserved
    May 26 09:42:34 phenom kernel: system 00:05: [mem 0x00000000-0x0009ffff] could not be reserved
    May 26 09:42:34 phenom kernel: system 00:05: [mem 0x00100000-0xcfd9ffff] could not be reserved
    May 26 09:42:34 phenom kernel: system 00:05: [mem 0xcfe00000-0xcfefffff] has been reserved
    May 26 09:42:34 phenom kernel: system 00:05: [mem 0xcff00000-0xcfffffff] could not be reserved
    May 26 09:42:34 phenom kernel: system 00:05: [mem 0xfec00000-0xfec00fff] could not be reserved
    May 26 09:42:34 phenom kernel: system 00:05: [mem 0xfee00000-0xfee00fff] could not be reserved
    May 26 09:42:34 phenom kernel: system 00:05: [mem 0xfff80000-0xfffeffff] has been reserved
    May 26 09:42:34 phenom kernel: system 00:05: Plug and Play ACPI device, IDs PNP0c01 (active)
    May 26 09:42:34 phenom kernel: pnp: PnP ACPI: found 6 devices
    May 26 09:42:34 phenom kernel: pci 0000:01:00.0: BAR 6: assigned [mem 0xfd500000-0xfd51ffff pref]
    May 26 09:42:34 phenom kernel: pci 0000:00:02.0: PCI bridge to [bus 01]
    May 26 09:42:34 phenom kernel: pci 0000:00:02.0: bridge window [io 0xc000-0xcfff]
    May 26 09:42:34 phenom kernel: pci 0000:00:02.0: bridge window [mem 0xfd500000-0xfd5fffff]
    May 26 09:42:34 phenom kernel: pci 0000:00:02.0: bridge window [mem 0xd0000000-0xdfffffff 64bit pref]
    May 26 09:42:34 phenom kernel: pci 0000:00:04.0: PCI bridge to [bus 02]
    May 26 09:42:34 phenom kernel: pci 0000:00:04.0: bridge window [io 0xb000-0xbfff]
    May 26 09:42:34 phenom kernel: pci 0000:00:04.0: bridge window [mem 0xfd400000-0xfd4fffff]
    May 26 09:42:34 phenom kernel: pci 0000:00:04.0: bridge window [mem 0xfde00000-0xfdefffff 64bit pref]
    May 26 09:42:34 phenom kernel: pci 0000:00:09.0: PCI bridge to [bus 03]
    May 26 09:42:34 phenom kernel: pci 0000:00:09.0: bridge window [io 0xe000-0xefff]
    May 26 09:42:34 phenom kernel: pci 0000:00:09.0: bridge window [mem 0xfdd00000-0xfddfffff]
    May 26 09:42:34 phenom kernel: pci 0000:00:09.0: bridge window [mem 0xfdc00000-0xfdcfffff 64bit pref]
    May 26 09:42:34 phenom kernel: pci 0000:00:0a.0: PCI bridge to [bus 04]
    May 26 09:42:34 phenom kernel: pci 0000:00:0a.0: bridge window [io 0xd000-0xdfff]
    May 26 09:42:34 phenom kernel: pci 0000:00:0a.0: bridge window [mem 0xfdb00000-0xfdbfffff]
    May 26 09:42:34 phenom kernel: pci 0000:00:0a.0: bridge window [mem 0xfd800000-0xfd8fffff 64bit pref]
    May 26 09:42:34 phenom kernel: pci 0000:00:14.4: PCI bridge to [bus 05]
    May 26 09:42:34 phenom kernel: pci 0000:00:14.4: bridge window [io 0xa000-0xafff]
    May 26 09:42:34 phenom kernel: pci 0000:00:14.4: bridge window [mem 0xfda00000-0xfdafffff]
    May 26 09:42:34 phenom kernel: pci 0000:00:14.4: bridge window [mem 0xfd900000-0xfd9fffff pref]
    May 26 09:42:34 phenom kernel: pci 0000:00:15.0: PCI bridge to [bus 06]
    May 26 09:42:34 phenom kernel: pci 0000:00:15.0: bridge window [io 0x9000-0x9fff]
    May 26 09:42:34 phenom kernel: pci 0000:00:15.0: bridge window [mem 0xfd700000-0xfd7fffff]
    May 26 09:42:34 phenom kernel: pci 0000:00:15.0: bridge window [mem 0xfd600000-0xfd6fffff 64bit pref]
    May 26 09:42:34 phenom kernel: pci_bus 0000:00: resource 4 [io 0x0000-0x0cf7 window]
    May 26 09:42:34 phenom kernel: pci_bus 0000:00: resource 5 [io 0x0d00-0xffff window]
    May 26 09:42:34 phenom kernel: pci_bus 0000:00: resource 6 [mem 0x000a0000-0x000bffff window]
    May 26 09:42:34 phenom kernel: pci_bus 0000:00: resource 7 [mem 0x000c0000-0x000dffff window]
    May 26 09:42:34 phenom kernel: pci_bus 0000:00: resource 8 [mem 0xfed40000-0xfed44fff window]
    May 26 09:42:34 phenom kernel: pci_bus 0000:00: resource 9 [mem 0xd0000000-0xfebfffff window]
    May 26 09:42:34 phenom kernel: pci_bus 0000:01: resource 0 [io 0xc000-0xcfff]
    May 26 09:42:34 phenom kernel: pci_bus 0000:01: resource 1 [mem 0xfd500000-0xfd5fffff]
    May 26 09:42:34 phenom kernel: pci_bus 0000:01: resource 2 [mem 0xd0000000-0xdfffffff 64bit pref]
    May 26 09:42:34 phenom kernel: pci_bus 0000:02: resource 0 [io 0xb000-0xbfff]
    May 26 09:42:34 phenom kernel: pci_bus 0000:02: resource 1 [mem 0xfd400000-0xfd4fffff]
    May 26 09:42:34 phenom kernel: pci_bus 0000:02: resource 2 [mem 0xfde00000-0xfdefffff 64bit pref]
    May 26 09:42:34 phenom kernel: pci_bus 0000:03: resource 0 [io 0xe000-0xefff]
    May 26 09:42:34 phenom kernel: pci_bus 0000:03: resource 1 [mem 0xfdd00000-0xfddfffff]
    May 26 09:42:34 phenom kernel: pci_bus 0000:03: resource 2 [mem 0xfdc00000-0xfdcfffff 64bit pref]
    May 26 09:42:34 phenom kernel: pci_bus 0000:04: resource 0 [io 0xd000-0xdfff]
    May 26 09:42:34 phenom kernel: pci_bus 0000:04: resource 1 [mem 0xfdb00000-0xfdbfffff]
    May 26 09:42:34 phenom kernel: pci_bus 0000:04: resource 2 [mem 0xfd800000-0xfd8fffff 64bit pref]
    May 26 09:42:34 phenom kernel: pci_bus 0000:05: resource 0 [io 0xa000-0xafff]
    May 26 09:42:34 phenom kernel: pci_bus 0000:05: resource 1 [mem 0xfda00000-0xfdafffff]
    May 26 09:42:34 phenom kernel: pci_bus 0000:05: resource 2 [mem 0xfd900000-0xfd9fffff pref]
    May 26 09:42:34 phenom kernel: pci_bus 0000:05: resource 4 [io 0x0000-0x0cf7 window]
    May 26 09:42:34 phenom kernel: pci_bus 0000:05: resource 5 [io 0x0d00-0xffff window]
    May 26 09:42:34 phenom kernel: pci_bus 0000:05: resource 6 [mem 0x000a0000-0x000bffff window]
    May 26 09:42:34 phenom kernel: pci_bus 0000:05: resource 7 [mem 0x000c0000-0x000dffff window]
    May 26 09:42:34 phenom kernel: pci_bus 0000:05: resource 8 [mem 0xfed40000-0xfed44fff window]
    May 26 09:42:34 phenom kernel: pci_bus 0000:05: resource 9 [mem 0xd0000000-0xfebfffff window]
    May 26 09:42:34 phenom kernel: pci_bus 0000:06: resource 0 [io 0x9000-0x9fff]
    May 26 09:42:34 phenom kernel: pci_bus 0000:06: resource 1 [mem 0xfd700000-0xfd7fffff]
    May 26 09:42:34 phenom kernel: pci_bus 0000:06: resource 2 [mem 0xfd600000-0xfd6fffff 64bit pref]
    May 26 09:42:34 phenom kernel: NET: Registered protocol family 2
    May 26 09:42:34 phenom kernel: TCP established hash table entries: 131072 (order: 8, 1048576 bytes)
    May 26 09:42:34 phenom kernel: TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
    May 26 09:42:34 phenom kernel: TCP: Hash tables configured (established 131072 bind 65536)
    May 26 09:42:34 phenom kernel: TCP: reno registered
    May 26 09:42:34 phenom kernel: UDP hash table entries: 8192 (order: 6, 262144 bytes)
    May 26 09:42:34 phenom kernel: UDP-Lite hash table entries: 8192 (order: 6, 262144 bytes)
    May 26 09:42:34 phenom kernel: NET: Registered protocol family 1
    May 26 09:42:34 phenom kernel: pci 0000:01:00.0: Video device with shadowed ROM
    May 26 09:42:34 phenom kernel: PCI: CLS 64 bytes, default 64
    May 26 09:42:34 phenom kernel: Unpacking initramfs...
    May 26 09:42:34 phenom kernel: Freeing initrd memory: 14980K (ffff8800362ae000 - ffff88003714f000)
    May 26 09:42:34 phenom kernel: PCI-DMA: Disabling AGP.
    May 26 09:42:34 phenom kernel: PCI-DMA: aperture base @ c4000000 size 65536 KB
    May 26 09:42:34 phenom kernel: PCI-DMA: using GART IOMMU.
    May 26 09:42:34 phenom kernel: PCI-DMA: Reserving 64MB of IOMMU area in the AGP aperture
    May 26 09:42:34 phenom kernel: microcode: CPU0: patch_level=0x010000bf
    May 26 09:42:34 phenom kernel: microcode: CPU1: patch_level=0x010000bf
    May 26 09:42:34 phenom kernel: microcode: CPU2: patch_level=0x010000bf
    May 26 09:42:34 phenom kernel: microcode: CPU3: patch_level=0x010000bf
    May 26 09:42:34 phenom kernel: microcode: CPU4: patch_level=0x010000bf
    May 26 09:42:34 phenom kernel: microcode: CPU5: patch_level=0x010000bf
    May 26 09:42:34 phenom kernel: microcode: Microcode Update Driver: v2.00 <[email protected]>, Peter Oruba
    May 26 09:42:34 phenom kernel: LVT offset 1 assigned for vector 0x400
    May 26 09:42:34 phenom kernel: IBS: LVT offset 1 assigned
    May 26 09:42:34 phenom kernel: perf: AMD IBS detected (0x0000001f)
    May 26 09:42:34 phenom kernel: Scanning for low memory corruption every 60 seconds
    May 26 09:42:34 phenom kernel: futex hash table entries: 2048 (order: 5, 131072 bytes)
    May 26 09:42:34 phenom kernel: Initialise system trusted keyring
    May 26 09:42:34 phenom kernel: HugeTLB registered 2 MB page size, pre-allocated 0 pages
    May 26 09:42:34 phenom kernel: zpool: loaded
    May 26 09:42:34 phenom kernel: zbud: loaded
    May 26 09:42:34 phenom kernel: VFS: Disk quotas dquot_6.5.2
    May 26 09:42:34 phenom kernel: VFS: Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
    May 26 09:42:34 phenom kernel: Key type big_key registered
    May 26 09:42:34 phenom kernel: Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
    May 26 09:42:34 phenom kernel: io scheduler noop registered
    May 26 09:42:34 phenom kernel: io scheduler deadline registered
    May 26 09:42:34 phenom kernel: io scheduler cfq registered (default)
    May 26 09:42:34 phenom kernel: pci_hotplug: PCI Hot Plug PCI Core version: 0.5
    May 26 09:42:34 phenom kernel: pciehp: PCI Express Hot Plug Controller Driver version: 0.4
    May 26 09:42:34 phenom kernel: vesafb: mode is 1600x1200x32, linelength=6400, pages=0
    May 26 09:42:34 phenom kernel: vesafb: scrolling: redraw
    May 26 09:42:34 phenom kernel: vesafb: Truecolor: size=0:8:8:8, shift=0:16:8:0
    May 26 09:42:34 phenom kernel: vesafb: framebuffer at 0xd0000000, mapped to 0xffffc90011c00000, using 7552k, total 7552k
    May 26 09:42:34 phenom kernel: Console: switching to colour frame buffer device 200x75
    May 26 09:42:34 phenom kernel: fb0: VESA VGA frame buffer device
    May 26 09:42:34 phenom kernel: GHES: HEST is not enabled!
    May 26 09:42:34 phenom kernel: Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
    May 26 09:42:34 phenom kernel: 00:03: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A
    May 26 09:42:34 phenom kernel: Linux agpgart interface v0.103
    May 26 09:42:34 phenom kernel: rtc_cmos 00:02: RTC can wake from S4
    May 26 09:42:34 phenom kernel: rtc_cmos 00:02: rtc core: registered rtc_cmos as rtc0
    May 26 09:42:34 phenom kernel: rtc_cmos 00:02: alarms up to one month, 242 bytes nvram, hpet irqs
    May 26 09:42:34 phenom kernel: rtc-cmos: BIOS has alarm-disable quirk.
    May 26 09:42:34 phenom kernel: RTC alarms disabled
    May 26 09:42:34 phenom kernel: ledtrig-cpu: registered to indicate activity on CPUs
    May 26 09:42:34 phenom kernel: TCP: cubic registered
    May 26 09:42:34 phenom kernel: NET: Registered protocol family 10
    May 26 09:42:34 phenom kernel: NET: Registered protocol family 17
    May 26 09:42:34 phenom kernel: Loading compiled-in X.509 certificates
    May 26 09:42:34 phenom kernel: registered taskstats version 1
    May 26 09:42:34 phenom kernel: Magic number: 15:372:724
    May 26 09:42:34 phenom kernel: rtc_cmos 00:02: setting system clock to 2015-05-26 07:42:29 UTC (1432626149)
    May 26 09:42:34 phenom kernel: PM: Hibernation image not present or could not be loaded.
    May 26 09:42:34 phenom kernel: Freeing unused kernel memory: 1160K (ffffffff818d4000 - ffffffff819f6000)
    May 26 09:42:34 phenom kernel: Write protecting the kernel read-only data: 8192k
    May 26 09:42:34 phenom kernel: Freeing unused kernel memory: 504K (ffff880001582000 - ffff880001600000)
    May 26 09:42:34 phenom kernel: Freeing unused kernel memory: 264K (ffff8800017be000 - ffff880001800000)
    May 26 09:42:34 phenom kernel: random: systemd-tmpfile urandom read with 3 bits of entropy available
    May 26 09:42:34 phenom kernel: [drm] Initialized drm 1.1.0 20060810
    May 26 09:42:34 phenom kernel: [drm] radeon kernel modesetting enabled.
    May 26 09:42:34 phenom kernel: checking generic (d0000000 760000) vs hw (d0000000 10000000)
    May 26 09:42:34 phenom kernel: fb: switching to radeondrmfb from VESA VGA
    May 26 09:42:34 phenom kernel: Console: switching to colour dummy device 80x25
    May 26 09:42:34 phenom kernel: [drm] initializing kernel modesetting (CAICOS 0x1002:0x6779 0x1043:0x0483).
    May 26 09:42:34 phenom kernel: [drm] register mmio base: 0xFD5C0000
    May 26 09:42:34 phenom kernel: [drm] register mmio size: 131072
    May 26 09:42:34 phenom kernel: ATOM BIOS: 6779.13.12.0.45.AS01
    May 26 09:42:34 phenom kernel: radeon 0000:01:00.0: VRAM: 1024M 0x0000000000000000 - 0x000000003FFFFFFF (1024M used)
    May 26 09:42:34 phenom kernel: radeon 0000:01:00.0: GTT: 1024M 0x0000000040000000 - 0x000000007FFFFFFF
    May 26 09:42:34 phenom kernel: [drm] Detected VRAM RAM=1024M, BAR=256M
    May 26 09:42:34 phenom kernel: [drm] RAM width 64bits DDR
    May 26 09:42:34 phenom kernel: [TTM] Zone kernel: Available graphics memory: 8217894 kiB
    May 26 09:42:34 phenom kernel: [TTM] Zone dma32: Available graphics memory: 2097152 kiB
    May 26 09:42:34 phenom kernel: [TTM] Initializing pool allocator
    May 26 09:42:34 phenom kernel: [TTM] Initializing DMA pool allocator
    May 26 09:42:34 phenom kernel: [drm] radeon: 1024M of VRAM memory ready
    May 26 09:42:34 phenom kernel: [drm] radeon: 1024M of GTT memory ready.
    May 26 09:42:34 phenom kernel: [drm] Loading CAICOS Microcode
    May 26 09:42:34 phenom kernel: [drm] Internal thermal controller without fan control
    May 26 09:42:34 phenom kernel: [drm] radeon: dpm initialized
    May 26 09:42:34 phenom kernel: [drm] GART: num cpu pages 262144, num gpu pages 262144
    May 26 09:42:34 phenom kernel: [drm] enabling PCIE gen 2 link speeds, disable with radeon.pcie_gen2=0
    May 26 09:42:34 phenom kernel: [drm] PCIE GART of 1024M enabled (table at 0x0000000000274000).
    May 26 09:42:34 phenom kernel: radeon 0000:01:00.0: WB enabled
    May 26 09:42:34 phenom kernel: radeon 0000:01:00.0: fence driver on ring 0 use gpu addr 0x0000000040000c00 and cpu addr 0xffff88041a0cdc00
    May 26 09:42:34 phenom kernel: radeon 0000:01:00.0: fence driver on ring 3 use gpu addr 0x0000000040000c0c and cpu addr 0xffff88041a0cdc0c
    May 26 09:42:34 phenom kernel: radeon 0000:01:00.0: fence driver on ring 5 use gpu addr 0x0000000000072118 and cpu addr 0xffffc900126b2118
    May 26 09:42:34 phenom kernel: [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
    May 26 09:42:34 phenom kernel: [drm] Driver supports precise vblank timestamp query.
    May 26 09:42:34 phenom kernel: radeon 0000:01:00.0: radeon: MSI limited to 32-bit
    May 26 09:42:34 phenom kernel: radeon 0000:01:00.0: radeon: using MSI.
    May 26 09:42:34 phenom kernel: [drm] radeon: irq initialized.
    May 26 09:42:34 phenom kernel: [drm] ring test on 0 succeeded in 2 usecs
    May 26 09:42:34 phenom kernel: [drm] ring test on 3 succeeded in 7 usecs
    May 26 09:42:34 phenom kernel: [drm] ring test on 5 succeeded in 2 usecs
    May 26 09:42:34 phenom kernel: [drm] UVD initialized successfully.
    May 26 09:42:34 phenom kernel: [drm] ib test on ring 0 succeeded in 0 usecs
    May 26 09:42:34 phenom kernel: [drm] ib test on ring 3 succeeded in 0 usecs
    May 26 09:42:34 phenom kernel: [drm] ib test on ring 5 succeeded
    May 26 09:42:34 phenom kernel: [drm] Radeon Display Connectors
    May 26 09:42:34 phenom kernel: [drm] Connector 0:
    May 26 09:42:34 phenom kernel: [drm] HDMI-A-1
    May 26 09:42:34 phenom kernel: [drm] HPD1
    May 26 09:42:34 phenom kernel: [drm] DDC: 0x6460 0x6460 0x6464 0x6464 0x6468 0x6468 0x646c 0x646c
    May 26 09:42:34 phenom kernel: [drm] Encoders:
    May 26 09:42:34 phenom kernel: [drm] DFP1: INTERNAL_UNIPHY1
    May 26 09:42:34 phenom kernel: [drm] Connector 1:
    May 26 09:42:34 phenom kernel: [drm] DVI-D-1
    May 26 09:42:34 phenom kernel: [drm] HPD4
    May 26 09:42:34 phenom kernel: [drm] DDC: 0x6450 0x6450 0x6454 0x6454 0x6458 0x6458 0x645c 0x645c
    May 26 09:42:34 phenom kernel: [drm] Encoders:
    May 26 09:42:34 phenom kernel: [drm] DFP2: INTERNAL_UNIPHY
    May 26 09:42:34 phenom kernel: [drm] Connector 2:
    May 26 09:42:34 phenom kernel: [drm] VGA-1
    May 26 09:42:34 phenom kernel: [drm] DDC: 0x6430 0x6430 0x6434 0x6434 0x6438 0x6438 0x643c 0x643c
    May 26 09:42:34 phenom kernel: [drm] Encoders:
    May 26 09:42:34 phenom kernel: [drm] CRT1: INTERNAL_KLDSCP_DAC1
    May 26 09:42:34 phenom kernel: tsc: Refined TSC clocksource calibration: 3300.098 MHz
    May 26 09:42:34 phenom kernel: [drm] fb mappable at 0xD0475000
    May 26 09:42:34 phenom kernel: [drm] vram apper at 0xD0000000
    May 26 09:42:34 phenom kernel: [drm] size 9216000
    May 26 09:42:34 phenom kernel: [drm] fb depth is 24
    May 26 09:42:34 phenom kernel: [drm] pitch is 7680
    May 26 09:42:34 phenom kernel: fbcon: radeondrmfb (fb0) is primary device
    May 26 09:42:34 phenom kernel: Console: switching to colour frame buffer device 240x75
    May 26 09:42:34 phenom kernel: radeon 0000:01:00.0: fb0: radeondrmfb frame buffer device
    May 26 09:42:34 phenom kernel: radeon 0000:01:00.0: registered panic notifier
    May 26 09:42:34 phenom kernel: [drm] Initialized radeon 2.41.0 20080528 for 0000:01:00.0 on minor 0
    May 26 09:42:34 phenom kernel: wmi: Mapper loaded
    May 26 09:42:34 phenom kernel: input: Power Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input0
    May 26 09:42:34 phenom kernel: ACPI: Power Button [PWRB]
    May 26 09:42:34 phenom kernel: input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input1
    May 26 09:42:34 phenom kernel: ACPI: Power Button [PWRF]
    May 26 09:42:34 phenom kernel: MXM: GUID detected in BIOS
    May 26 09:42:34 phenom kernel: i8042: PNP: No PS/2 controller found. Probing ports directly.
    May 26 09:42:34 phenom kernel: i8042: Failed to disable AUX port, but continuing anyway... Is this a SiS?
    May 26 09:42:34 phenom kernel: i8042: If AUX port is really absent please use the 'i8042.noaux' option
    May 26 09:42:34 phenom kernel: serio: i8042 KBD port at 0x60,0x64 irq 1
    May 26 09:42:34 phenom kernel: ACPI: bus type USB registered
    May 26 09:42:34 phenom kernel: usbcore: registered new interface driver usbfs
    May 26 09:42:34 phenom kernel: SCSI subsystem initialized
    May 26 09:42:34 phenom kernel: usbcore: registered new interface driver hub
    May 26 09:42:34 phenom kernel: usbcore: registered new device driver usb
    May 26 09:42:34 phenom kernel: ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
    May 26 09:42:34 phenom kernel: ehci-pci: EHCI PCI platform driver
    May 26 09:42:34 phenom kernel: QUIRK: Enable AMD PLL fix
    May 26 09:42:34 phenom kernel: ehci-pci 0000:00:12.2: EHCI Host Controller
    May 26 09:42:34 phenom kernel: ehci-pci 0000:00:12.2: new USB bus registered, assigned bus number 1
    May 26 09:42:34 phenom kernel: ehci-pci 0000:00:12.2: applying AMD SB700/SB800/Hudson-2/3 EHCI dummy qh workaround
    May 26 09:42:34 phenom kernel: ehci-pci 0000:00:12.2: debug port 1
    May 26 09:42:34 phenom kernel: ehci-pci 0000:00:12.2: irq 17, io mem 0xfdffd000
    May 26 09:42:34 phenom kernel: ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
    May 26 09:42:34 phenom kernel: ohci-pci: OHCI PCI platform driver
    May 26 09:42:34 phenom kernel: libata version 3.00 loaded.
    May 26 09:42:34 phenom kernel: ehci-pci 0000:00:12.2: USB 2.0 started, EHCI 1.00
    May 26 09:42:34 phenom kernel: hub 1-0:1.0: USB hub found
    May 26 09:42:34 phenom kernel: hub 1-0:1.0: 5 ports detected
    May 26 09:42:34 phenom kernel: xhci_hcd 0000:02:00.0: xHCI Host Controller
    May 26 09:42:34 phenom kernel: xhci_hcd 0000:02:00.0: new USB bus registered, assigned bus number 2
    May 26 09:42:34 phenom kernel: xhci_hcd 0000:02:00.0: hcc params 0x040050af hci version 0x100 quirks 0x00080490
    May 26 09:42:34 phenom kernel: hub 2-0:1.0: USB hub found
    May 26 09:42:34 phenom kernel: hub 2-0:1.0: 2 ports detected
    May 26 09:42:34 phenom kernel: xhci_hcd 0000:02:00.0: xHCI Host Controller
    May 26 09:42:34 phenom kernel: xhci_hcd 0000:02:00.0: new USB bus registered, assigned bus number 3
    May 26 09:42:34 phenom kernel: ehci-pci 0000:00:13.2: EHCI Host Controller
    May 26 09:42:34 phenom kernel: hub 3-0:1.0: USB hub found
    May 26 09:42:34 phenom kernel: hub 3-0:1.0: 2 ports detected
    May 26 09:42:34 phenom kernel: ehci-pci 0000:00:13.2: new USB bus registered, assigned bus number 4
    May 26 09:42:34 phenom kernel: ehci-pci 0000:00:13.2: applying AMD SB700/SB800/Hudson-2/3 EHCI dummy qh workaround
    May 26 09:42:34 phenom kernel: ehci-pci 0000:00:13.2: debug port 1
    May 26 09:42:34 phenom kernel: ehci-pci 0000:00:13.2: irq 17, io mem 0xfdffb000
    May 26 09:42:34 phenom kernel: ehci-pci 0000:00:13.2: USB 2.0 started, EHCI 1.00
    May 26 09:42:34 phenom kernel: hub 4-0:1.0: USB hub found
    May 26 09:42:34 phenom kernel: hub 4-0:1.0: 5 ports detected
    May 26 09:42:34 phenom kernel: xhci_hcd 0000:04:00.0: xHCI Host Controller
    May 26 09:42:34 phenom kernel: xhci_hcd 0000:04:00.0: new USB bus registered, assigned bus number 5
    May 26 09:42:34 phenom kernel: xhci_hcd 0000:04:00.0: hcc params 0x040050af hci version 0x100 quirks 0x00080490
    May 26 09:42:34 phenom kernel: hub 5-0:1.0: USB hub found
    May 26 09:42:34 phenom kernel: hub 5-0:1.0: 2 ports detected
    May 26 09:42:34 phenom kernel: xhci_hcd 0000:04:00.0: xHCI Host Controller
    May 26 09:42:34 phenom kernel: xhci_hcd 0000:04:00.0: new USB bus registered, assigned bus number 6
    May 26 09:42:34 phenom kernel: ehci-pci 0000:00:16.2: EHCI Host Controller
    May 26 09:42:34 phenom kernel: hub 6-0:1.0: USB hub found
    May 26 09:42:34 phenom kernel: hub 6-0:1.0: 2 ports detected
    May 26 09:42:34 phenom kernel: ehci-pci 0000:00:16.2: new USB bus registered, assigned bus number 7
    May 26 09:42:34 phenom kernel: ehci-pci 0000:00:16.2: applying AMD SB700/SB800/Hudson-2/3 EHCI dummy qh workaround
    May 26 09:42:34 phenom kernel: ehci-pci 0000:00:16.2: debug port 1
    May 26 09:42:34 phenom kernel: ehci-pci 0000:00:16.2: irq 17, io mem 0xfdff8000
    May 26 09:42:34 phenom kernel: ehci-pci 0000:00:16.2: USB 2.0 started, EHCI 1.00
    May 26 09:42:34 phenom kernel: hub 7-0:1.0: USB hub found
    May 26 09:42:34 phenom kernel: hub 7-0:1.0: 4 ports detected
    May 26 09:42:34 phenom kernel: ohci-pci 0000:00:12.0: OHCI PCI host controller
    May 26 09:42:34 phenom kernel: ohci-pci 0000:00:12.0: new USB bus registered, assigned bus number 8
    May 26 09:42:34 phenom kernel: ohci-pci 0000:00:12.0: irq 18, io mem 0xfdffe000
    May 26 09:42:34 phenom kernel: firewire_ohci 0000:05:0e.0: added OHCI v1.10 device as card 0, 4 IR + 8 IT contexts, quirks 0x11
    May 26 09:42:34 phenom kernel: hub 8-0:1.0: USB hub found
    May 26 09:42:34 phenom kernel: hub 8-0:1.0: 5 ports detected
    May 26 09:42:34 phenom kernel: ohci-pci 0000:00:13.0: OHCI PCI host controller
    May 26 09:42:34 phenom kernel: ohci-pci 0000:00:13.0: new USB bus registered, assigned bus number 9
    May 26 09:42:34 phenom kernel: ohci-pci 0000:00:13.0: irq 18, io mem 0xfdffc000
    May 26 09:42:34 phenom kernel: hub 9-0:1.0: USB hub found
    May 26 09:42:34 phenom kernel: hub 9-0:1.0: 5 ports detected
    May 26 09:42:34 phenom kernel: ohci-pci 0000:00:14.5: OHCI PCI host controller
    May 26 09:42:34 phenom kernel: ohci-pci 0000:00:14.5: new USB bus registered, assigned bus number 10
    May 26 09:42:34 phenom kernel: ohci-pci 0000:00:14.5: irq 18, io mem 0xfdffa000
    May 26 09:42:34 phenom kernel: hub 10-0:1.0: USB hub found
    May 26 09:42:34 phenom kernel: hub 10-0:1.0: 2 ports detected
    May 26 09:42:34 phenom kernel: ohci-pci 0000:00:16.0: OHCI PCI host controller
    May 26 09:42:34 phenom kernel: ohci-pci 0000:00:16.0: new USB bus registered, assigned bus number 11
    May 26 09:42:34 phenom kernel: ohci-pci 0000:00:16.0: irq 18, io mem 0xfdff9000
    May 26 09:42:34 phenom kernel: hub 11-0:1.0: USB hub found
    May 26 09:42:34 phenom kernel: hub 11-0:1.0: 4 ports detected
    May 26 09:42:34 phenom kernel: scsi host0: pata_atiixp
    May 26 09:42:34 phenom kernel: scsi host1: pata_atiixp
    May 26 09:42:34 phenom kernel: ata1: PATA max UDMA/100 cmd 0x1f0 ctl 0x3f6 bmdma 0xfa00 irq 14
    May 26 09:42:34 phenom kernel: ata2: PATA max UDMA/100 cmd 0x170 ctl 0x376 bmdma 0xfa08 irq 15
    May 26 09:42:34 phenom kernel: ahci 0000:00:11.0: version 3.0
    May 26 09:42:34 phenom kernel: ahci 0000:00:11.0: AHCI 0001.0200 32 slots 4 ports 6 Gbps 0xf impl SATA mode
    May 26 09:42:34 phenom kernel: ahci 0000:00:11.0: flags: 64bit ncq sntf ilck pm led clo pmp pio slum part
    May 26 09:42:34 phenom kernel: scsi host2: ahci
    May 26 09:42:34 phenom kernel: scsi host3: ahci
    May 26 09:42:34 phenom kernel: scsi host4: ahci
    May 26 09:42:34 phenom kernel: scsi host5: ahci
    May 26 09:42:34 phenom kernel: ata3: SATA max UDMA/133 abar m1024@0xfdfff000 port 0xfdfff100 irq 19
    May 26 09:42:34 phenom kernel: ata4: SATA max UDMA/133 abar m1024@0xfdfff000 port 0xfdfff180 irq 19
    May 26 09:42:34 phenom kernel: ata5: SATA max UDMA/133 abar m1024@0xfdfff000 port 0xfdfff200 irq 19
    May 26 09:42:34 phenom kernel: ata6: SATA max UDMA/133 abar m1024@0xfdfff000 port 0xfdfff280 irq 19
    May 26 09:42:34 phenom kernel: usb 1-1: new high-speed USB device number 2 using ehci-pci
    May 26 09:42:34 phenom kernel: usb 2-2: new high-speed USB device number 2 using xhci_hcd
    May 26 09:42:34 phenom kernel: usb 7-4: new high-speed USB device number 2 using ehci-pci
    May 26 09:42:34 phenom kernel: ata1.01: ATAPI: PLEXTOR DVDR PX-820A, 1.00, max UDMA/66
    May 26 09:42:34 phenom kernel: ata1.01: limited to UDMA/33 due to 40-wire cable
    May 26 09:42:34 phenom kernel: hub 1-1:1.0: USB hub found
    May 26 09:42:34 phenom kernel: hub 1-1:1.0: 4 ports detected
    May 26 09:42:34 phenom kernel: ata1.01: configured for UDMA/33
    May 26 09:42:34 phenom kernel: scsi 0:0:1:0: CD-ROM PLEXTOR DVDR PX-820A 1.00 PQ: 0 ANSI: 5
    May 26 09:42:34 phenom kernel: firewire_core 0000:05:0e.0: created device fw0: GUID 0049e55059f30500, S400
    May 26 09:42:34 phenom kernel: ata3: SATA link down (SStatus 0 SControl 300)
    May 26 09:42:34 phenom kernel: ata4: SATA link down (SStatus 0 SControl 300)
    May 26 09:42:34 phenom kernel: Switched to clocksource tsc
    May 26 09:42:34 phenom kernel: usb 1-1.1: new low-speed USB device number 3 using ehci-pci
    May 26 09:42:34 phenom kernel: ata6: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
    May 26 09:42:34 phe

    Hi,
    I have exactly the same problem. systemd-logind sporadically fails to start, therefore preventing the login prompt to appear. Resetting the machine is the only solution in that case. Most of the time, the system start works without problems though. Here are a few relevant lines from my logs:
    # journalctl --unit=systemd-logind | grep -C50 'Connection timed out'
    -- Reboot --
    Apr 22 10:16:36 deltaflyer systemd[1]: Starting Login Service...
    Apr 22 10:17:01 deltaflyer systemd-logind[377]: Failed to enable subscription: Connection timed out
    Apr 22 10:17:01 deltaflyer systemd-logind[377]: Failed to fully start up daemon: Connection timed out
    Apr 22 10:17:01 deltaflyer systemd[1]: systemd-logind.service: main process exited, code=exited, status=1/FAILURE
    Apr 22 10:17:01 deltaflyer systemd[1]: Failed to start Login Service.
    Apr 22 10:17:01 deltaflyer systemd[1]: Unit systemd-logind.service entered failed state.
    Apr 22 10:17:01 deltaflyer systemd[1]: systemd-logind.service failed.
    Apr 22 10:17:01 deltaflyer systemd[1]: systemd-logind.service has no holdoff time, scheduling restart.
    -- Reboot --
    Here is relevant output from the complete log (not only systemd-logind):
    # journalctl | grep -C10 'Connection timed out'
    Apr 22 10:17:01 deltaflyer dbus[389]: [system] Successfully activated service 'org.freedesktop.systemd1'
    Apr 22 10:17:01 deltaflyer NetworkManager[387]: <info> NetworkManager (version 1.0.0) is starting...
    Apr 22 10:17:01 deltaflyer acpid[386]: starting up with netlink and the input layer
    Apr 22 10:17:01 deltaflyer smartd[381]: Unable to monitor any SMART enabled devices. Try debug (-d) option. Exiting...
    Apr 22 10:17:01 deltaflyer /usr/bin/gpm[390]: imps2: Auto-detected intellimouse PS/2
    Apr 22 10:17:01 deltaflyer dbus[389]: [system] Activating via systemd: service name='org.freedesktop.ColorManager' unit='colord.service'
    Apr 22 10:17:01 deltaflyer NetworkManager[387]: <info> Read config: /etc/NetworkManager/NetworkManager.conf
    Apr 22 10:17:01 deltaflyer NetworkManager[387]: <info> WEXT support is enabled
    Apr 22 10:16:36 deltaflyer systemd[1]: Starting Virtual console mouse server...
    Apr 22 10:16:36 deltaflyer systemd[1]: Started D-Bus System Message Bus.
    Apr 22 10:17:01 deltaflyer systemd-logind[377]: Failed to enable subscription: Connection timed out
    Apr 22 10:17:01 deltaflyer systemd-logind[377]: Failed to fully start up daemon: Connection timed out
    Apr 22 10:17:01 deltaflyer systemd[1]: Failed to register name: Connection timed out
    Apr 22 10:17:01 deltaflyer systemd[1]: Failed to set up API bus: Connection timed out
    Apr 22 10:17:01 deltaflyer systemd[1]: Starting D-Bus System Message Bus...
    Apr 22 10:17:01 deltaflyer systemd[1]: Started LVM2 PV scan on device 254:0.
    Apr 22 10:17:01 deltaflyer lvm[320]: 7 logical volume(s) in volume group "deltaflyer" now active
    Apr 22 10:17:01 deltaflyer dbus[389]: [system] Activating via systemd: service name='org.freedesktop.login1' unit='dbus-org.freedesktop.login1.service'
    Apr 22 10:17:01 deltaflyer acpid[386]: 1 rule loaded
    Apr 22 10:17:01 deltaflyer acpid[386]: waiting for events: event logging is off
    Apr 22 10:17:01 deltaflyer NetworkManager[387]: <info> VPN: loaded org.freedesktop.NetworkManager.openvpn
    Apr 22 10:17:01 deltaflyer NetworkManager[387]: <info> Loaded plugin keyfile: (c) 2007 - 2013 Red Hat, Inc. To report bugs please use the NetworkManager mailing list.
    Apr 22 10:17:01 deltaflyer systemd[1]: Started Restore Sound Card State.
    Mai 11 11:20:56 deltaflyer acpid[638]: starting up with netlink and the input layer
    Mai 11 11:20:56 deltaflyer smartd[640]: Monitoring 1 ATA and 0 SCSI devices
    Mai 11 11:20:56 deltaflyer /usr/bin/gpm[637]: imps2: Auto-detected intellimouse PS/2
    Mai 11 11:20:56 deltaflyer dbus[642]: [system] Activating via systemd: service name='org.freedesktop.ColorManager' unit='colord.service'
    Mai 11 11:20:56 deltaflyer NetworkManager[633]: <info> Read config: /etc/NetworkManager/NetworkManager.conf
    Mai 11 11:20:56 deltaflyer NetworkManager[633]: <info> WEXT support is enabled
    Mai 11 11:20:56 deltaflyer dbus[642]: [system] Activating via systemd: service name='org.freedesktop.login1' unit='dbus-org.freedesktop.login1.service'
    Mai 11 11:20:56 deltaflyer acpid[638]: 1 rule loaded
    Mai 11 11:20:56 deltaflyer acpid[638]: waiting for events: event logging is off
    Mai 11 11:20:31 deltaflyer systemd[1]: Started D-Bus System Message Bus.
    Mai 11 11:20:56 deltaflyer systemd-logind[634]: Failed to enable subscription: Connection timed out
    Mai 11 11:20:56 deltaflyer systemd-logind[634]: Failed to fully start up daemon: Connection timed out
    Mai 11 11:20:56 deltaflyer systemd[1]: Failed to register name: Connection timed out
    Mai 11 11:20:56 deltaflyer systemd[1]: Failed to set up API bus: Connection timed out
    Mai 11 11:20:56 deltaflyer systemd[1]: Starting D-Bus System Message Bus...
    Mai 11 11:20:56 deltaflyer systemd[1]: Started Manage Sound Card State (restore and store).
    Mai 11 11:20:56 deltaflyer systemd[1]: Starting Restore Sound Card State...
    Mai 11 11:20:56 deltaflyer systemd[1]: Started Daily man-db cache update.
    Mai 11 11:20:56 deltaflyer systemd[1]: Starting Daily man-db cache update.
    Mai 11 11:20:56 deltaflyer systemd[1]: Started Daily verification of password and group files.
    Mai 11 11:20:56 deltaflyer systemd[1]: systemd-logind.service: main process exited, code=exited, status=1/FAILURE
    Mai 11 11:20:56 deltaflyer systemd[1]: Failed to start Login Service.
    Mai 11 11:20:56 deltaflyer systemd[1]: Unit systemd-logind.service entered failed state.
    Mai 11 11:20:56 deltaflyer systemd[1]: systemd-logind.service failed.
    Mai 27 16:47:34 deltaflyer smartd[399]: Device: /dev/sda [SAT], VBOX HARDDISK, S/N:VB9c7c4cff-f1cdf11a, FW:1.0, 500 GB
    Mai 27 16:47:34 deltaflyer smartd[399]: Device: /dev/sda [SAT], not found in smartd database.
    Mai 27 16:47:34 deltaflyer smartd[399]: Device: /dev/sda [SAT], lacks SMART capability
    Mai 27 16:47:34 deltaflyer smartd[399]: Device: /dev/sda [SAT], to proceed anyway, use '-T permissive' Directive.
    Mai 27 16:47:34 deltaflyer smartd[399]: Unable to monitor any SMART enabled devices. Try debug (-d) option. Exiting...
    Mai 27 16:47:59 deltaflyer /usr/bin/gpm[400]: *** info [mice.c(1990)]:
    Mai 27 16:47:59 deltaflyer dbus[402]: [system] Successfully activated service 'org.freedesktop.systemd1'
    Mai 27 16:47:59 deltaflyer nm-dispatcher[395]: Could not get the system bus (Timeout was reached). Make sure the message bus daemon is running!
    Mai 27 16:47:59 deltaflyer acpid[391]: starting up with netlink and the input layer
    Mai 27 16:47:34 deltaflyer systemd[1]: Started D-Bus System Message Bus.
    Mai 27 16:47:59 deltaflyer systemd-logind[392]: Failed to enable subscription: Connection timed out
    Mai 27 16:47:59 deltaflyer systemd-logind[392]: Failed to fully start up daemon: Connection timed out
    Mai 27 16:47:59 deltaflyer systemd[1]: Failed to register name: Connection timed out
    Mai 27 16:47:59 deltaflyer systemd[1]: Failed to set up API bus: Connection timed out
    Mai 27 16:47:59 deltaflyer systemd[1]: Starting D-Bus System Message Bus...
    Mai 27 16:47:59 deltaflyer systemd[1]: Starting Preprocess NFS configuration...
    Mai 27 16:47:59 deltaflyer systemd[1]: Starting Network Manager...
    Mai 27 16:47:59 deltaflyer systemd[1]: Starting VirtualBox Guest Service...
    Mai 27 16:47:59 deltaflyer systemd[1]: Started LVM2 PV scan on device 254:0.
    Mai 27 16:47:59 deltaflyer /usr/bin/gpm[400]: imps2: Auto-detected intellimouse PS/2
    Mai 27 16:47:59 deltaflyer dbus[402]: [system] Activating via systemd: service name='org.freedesktop.ColorManager' unit='colord.service'
    Mai 27 16:47:59 deltaflyer upowerd[393]: (upowerd:393): UPower-WARNING **: Failed to acquire org.freedesktop.UPower: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
    Mai 27 16:47:59 deltaflyer upowerd[393]: (upowerd:393): UPower-WARNING **: Could not acquire name; bailing out
    Mai 27 16:47:59 deltaflyer systemd[1]: Started Restore Sound Card State.
    It almost seems to be a problem with a dbus and/or NetworkManager race condition.

  • How to prevent B radio clients from connecting

    How can I enforce only G & A radio clients from being able to connect to my 1131AG Access Points?
    I know that when a B client connects it automatically brings all the G clients down to B due to the fact that G is backward compatible but does not operate at 54 mbps with a mix of B clients.

    Hi Sparky,
    Here is one method;
    To set the 2.4-GHz, 802.11g radio to serve only 802.11g client devices, set any Orthogonal Frequency Division Multiplexing (OFDM) data rate (6, 9, 12, 18, 24, 36, 48, 54) to Basic.
    Note: The client must support the basic rate that you select or it cannot associate to the wireless device. If you select 12 Mbps or higher for the basic data rate on the 802.11g radio, 802.11b client devices cannot associate to the wireless device's 802.11g radio.
    From this good doc;
    http://www.cisco.com/en/US/docs/wireless/access_point/12.3_2_JA/configuration/guide/s32rf.html#wp1083005
    Hope this helps!
    Rob

  • RCA vs. S-video

    Being that the new displays only work with the new generation MBP's (I think, right?) I found a great compromise.
    I'm now looking for a great t.v. that will serve two purposes. Being my television and main display for the MBP. I just need to know who wins the battle? RCA or S-video.
    I'm almost positive I'm not the only one who isn't curious about this, so why not post some recommendations on displays? inches and price aren't a big concern. Though I am not Job's himself.

    RCA refers to the shape of the plug. There are two common video formats that use RCA: composite and component.
    Composite is an analog signal that combines luminance, hue, and saturation on a single cable using a technique called frequency-division multiplexing. The mixing of the signals introduces some distortion and noise which leads to lower picture quality. A modern HDTV will convert the signal to 480i resolution. The aspect ratio of the picture is not transmitted, but it's basically standard 4:3 TV.
    S-Video is similar to composite, but uses a 4-pin DIN connector that separates the luminance from the chrominance (hue and saturation) into two different signals. The result is that the signal is clearer and there's more definition. A modern HDTV will convert the signal to 480i resolution. The aspect ratio of the picture is not transmitted, but it's basically standard 4:3 TV.
    Component video uses RCA-style connectors like composite video does, but it uses a separate connector for each portion of the signal (again, luminance, hue, and saturation). The result is the highest possible definition for an analog signal, provided the source. It comes in two flavors, but only one is used in modern TVs: YPbPr. This gives the highest definition of any of the analog video formats and the best color reproduction, though perhaps not as true as RGB composite video (what's used in VGA computer monitors). It's standard-definition 480i like the other 2 above.
    If you are going to buy a digital TV, however, you probably want to use a digital input. This has the advantage that you can use the native resolution of your digital TV set, have a perfectly sharp picture, and have the maximum range of colors available. There are two common standards found on HDTV sets: DVI and HDMI. HDMI is the most common. DVI is the native standard for Macs prior to the new display-port MacBook Pros. Adapters to go from your Mac to DVI or HDMI are available. The digital standards provide the best possible picture, but at the cost that the cables need to be <15' in length (less than 10' is best).
    One thing to note: the resolution and color range of an HDTV is generally much less than that of an LCD monitor, and they typically cost much more (they incorporate tuners and other controls). The highest resolution of an HDTV is going to be 1920x1080@60Hz.

  • Freezing Freeview TV on Qosimos in the UK

    Hi All,
    I have read all the threads on the problem of freezing Freeview digital TV .
    This is a very serious issue here in the UK.
    It happens on all Qosimo's with the Hybrid DVB-T Tuner. How can it be a Transmitter problem, when other computers [Media Centre] with DVB-T cards work fine?
    This needs to be sorted out and I hope Toshiba don't let us down !
    Nearly all main UK Digital Transmitters are on Horizontal Polarisation and will remain so after 2012 with the relay transmitters mainly on vertical polarisation.
    I am not convinced it has anything do with polarisation how come other cards and pcs work fine!
    OTHERWISE THE QOSIMO'S MACHINES ARE GREAT .
    So lets hit this one on the head !
    cheers
    Blackbob
    [Edited by: admin]

    Hello guys
    I understood that you are a little bit disappointed about this but to find a universal solution is not so easy like you think. I have phoned with one Toshiba guy and he explained me the whole situation on this way:
    The TV tuners in Qosmio units are much complex as TV tuners in TV boxes that are designed for digital signal only. Qosmio TV tuner is designed for analog and digital signal receiving and must be also arrange to work with Toshiba designed Qosmioplayer. DVB technology is pretty new and many users don't know exactly how it work and that there are many, but really many, factors that can be responsible for different kind of problems. The fact is that Qosmios sold in whole Europe have the same TV tuner but those claims comes just from UK. Obviously is there some specific problem.
    DVB-T technology is used very successfully in Nordic countries but till now Toshiba didn't get any claims from there. On this forum you can also find just some users from UK.
    The very interesting thing is that DVB-T transmitters using for their transmission the COFDM modulation (Coded Orthogonal Frequency Division Multiplex). These transmitters are using either 2K or the 8K transmission mode.
    ? 2K mode:2048 possible carrier, effective 1704 used
    ? 8K mode: 8192 possible carrier, effective 6817 used
    The 2K mode has not a strong depth of coverage (e.g. 17 km from the transmitter, by using 8K mode 67-34 km). The 2K mode is more suitable for mobile reception (support receiving signal up to 300km/h), in comparison the 8K mode support receiving a signal approximately by tempo of 92-112km/h). This is possibly not so much important for you but it is just for info.
    Interesting is that 2K mode is used in UK but not in many other countries. The hardware designers work on this to find a universal solution and I believe that it is not easy to design TV tuner for UK only. With every new technology there are problems that must be corrected and it is really not unusual that it can take a longer period of time.
    Sorry if you are not satisfied with my posting but at the moment there is not much to do.
    Good luck!

Maybe you are looking for

  • Error PRKR-1007  while creating a database

    Hi We have an oracle RAC with a 10.2.0.4 database over linux. Few days ago we drop a database with the dbca assistant. Now we need to create one with the same name with dbca, but it shows that the db_name already exist. Trying to delete again the SIG

  • Recover app no longer in iTunes store

    Hi folks, I have an app that I bought fair and square from the iTunes store shortly after getting my first gen iPad in August 2010. This iPad is synced to my Apple ID on a PC laptop. Since this was set up I have moved to a Macbook and bought a second

  • Remove scroll bar from html snippet?

    Hello there, I have a little html sniipet on the fron page of my website which includes text from a small Goole sites page. The page it references has some google related text at the bottom ad is thus higher than the size of the snippet 'box'. O my i

  • PDF picture frames?

    I downloaded this free benefit that is supposed to allow me to put frames around my pictures. To use it, the website says "Please click the button below and select "save" when prompted to download the files to your computer.* To add your photos, simp

  • HP ePrintcenter - cannot sign in

    I can't sign in to eprint, why?  it stills writes to me "server error". please help me.