rtnet-users Mailing List for RTnet - Real-Time Networking for Linux (Page 6)
Brought to you by:
bet-frogger,
kiszka
Menu
▾
▴
rtnet-users — support, discussion, and announcement list
You can subscribe to this list here.
| 2003 |
Jan
(31) |
Feb
(54) |
Mar
(37) |
Apr
(25) |
May
(77) |
Jun
(56) |
Jul
(38) |
Aug
(21) |
Sep
(49) |
Oct
(22) |
Nov
(45) |
Dec
(42) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2004 |
Jan
(46) |
Feb
(56) |
Mar
(70) |
Apr
(22) |
May
(36) |
Jun
(33) |
Jul
(23) |
Aug
(22) |
Sep
(20) |
Oct
(85) |
Nov
(40) |
Dec
(23) |
| 2005 |
Jan
(17) |
Feb
(13) |
Mar
(17) |
Apr
(23) |
May
(72) |
Jun
(56) |
Jul
(41) |
Aug
(17) |
Sep
(29) |
Oct
(19) |
Nov
(62) |
Dec
(44) |
| 2006 |
Jan
(33) |
Feb
(9) |
Mar
(131) |
Apr
(32) |
May
(39) |
Jun
(26) |
Jul
(45) |
Aug
(124) |
Sep
(57) |
Oct
(80) |
Nov
(69) |
Dec
(26) |
| 2007 |
Jan
(50) |
Feb
(39) |
Mar
(53) |
Apr
(23) |
May
(148) |
Jun
(59) |
Jul
(71) |
Aug
(91) |
Sep
(99) |
Oct
(63) |
Nov
(113) |
Dec
(27) |
| 2008 |
Jan
(9) |
Feb
(12) |
Mar
(38) |
Apr
(65) |
May
(65) |
Jun
(16) |
Jul
(8) |
Aug
(55) |
Sep
(15) |
Oct
(29) |
Nov
(28) |
Dec
(7) |
| 2009 |
Jan
(6) |
Feb
(6) |
Mar
(6) |
Apr
(10) |
May
(4) |
Jun
(7) |
Jul
(28) |
Aug
(4) |
Sep
(17) |
Oct
(16) |
Nov
(18) |
Dec
(30) |
| 2010 |
Jan
(6) |
Feb
(15) |
Mar
(46) |
Apr
(48) |
May
(63) |
Jun
(13) |
Jul
(40) |
Aug
(11) |
Sep
(28) |
Oct
(35) |
Nov
(5) |
Dec
(8) |
| 2011 |
Jan
(14) |
Feb
(17) |
Mar
(15) |
Apr
(9) |
May
(2) |
Jun
|
Jul
(10) |
Aug
(6) |
Sep
(13) |
Oct
(2) |
Nov
(9) |
Dec
(1) |
| 2012 |
Jan
(19) |
Feb
(13) |
Mar
(1) |
Apr
|
May
(14) |
Jun
(21) |
Jul
(13) |
Aug
(3) |
Sep
(8) |
Oct
(28) |
Nov
|
Dec
(6) |
| 2013 |
Jan
(3) |
Feb
|
Mar
(8) |
Apr
|
May
(18) |
Jun
(16) |
Jul
|
Aug
(12) |
Sep
(5) |
Oct
(14) |
Nov
(9) |
Dec
(8) |
| 2014 |
Jan
(5) |
Feb
(4) |
Mar
(3) |
Apr
(3) |
May
(13) |
Jun
(6) |
Jul
(2) |
Aug
|
Sep
(2) |
Oct
(2) |
Nov
(8) |
Dec
(8) |
| 2015 |
Jan
(22) |
Feb
|
Mar
(1) |
Apr
(3) |
May
(4) |
Jun
(3) |
Jul
(1) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2018 |
Jan
|
Feb
|
Mar
|
Apr
(2) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(1) |
Dec
|
| 2019 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(2) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2023 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(1) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: sam s. <sa...@em...> - 2013-10-02 16:59:24
|
I am getting this exact error (RTnet 0.9.13) http://www.mail-archive.com/rtn...@li.../msg03371.html This is what I did. lspci -nnk gets me 03:00.2 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 0a) Subsystem: ASUSTeK Computer Inc. Device [1043:1457] Kernel modules: r8169 Next sudo echo "10ec 8168" > /sys/bus/pci/drivers/rt_r8169/new_id and get in dmesg [ 951.112877] rt_r8169: region #1 not an MMIO resource, aborting Is there any work around? My google foo is failing me. sam |
|
From: Ilesh P. <pat...@gm...> - 2013-09-25 08:40:09
|
---------- Forwarded message ---------- From: Ilesh Patel <pat...@gm...> Date: Sat, Sep 14, 2013 at 1:53 PM Subject: RTnet on FPGA To: rtn...@li... Hello, We have implement a FPGA board with Microblaze Processors core support. Which having 1G Ethernet IP core support also. We have port Xenomai as real time OS on our board and RTnet for real time Ethernet support. I want to know for communication with PC and FPGA board through Ethernet there is a driver required or not ? If driver is required then, I have to implement new driver for our board or we can use driver which is available in RTnet source directory ? Can you suggest any driver which I can use directly ? Thanks & Regards, Ilesh Patel. |
|
From: Ilesh P. <pat...@gm...> - 2013-09-16 12:02:35
|
Hello, We have implement a FPGA board with Microblaze Processors core support. Which having 1G Ethernet IP core support also. We have port Xenomai as real time OS on our board and RTnet for real time Ethernet support. I want to know for communication with PC and FPGA board through Ethernet there is a driver required or not ? If driver is required then, I have to implement new driver for our board or we can use driver which is available in RTnet source directory ? Can you suggest any driver which I can use directly ? Thanks & Regards, Ilesh Patel. |
|
From: Jan K. <jan...@we...> - 2013-09-14 08:56:53
|
On 2013-09-09 14:37, Johan Cockx wrote: > Hello, > > Are there any PCI-express network cards that are supported by rtnet 0.9.12? > I need to install two additional network cards in a computer with only one > PCI slot free, preferably without changing the software. Alternatively, > can anyone point me to a dual PCI network card supported by rtnet 0.9.12? e1000e-driven adapters, e.g., are PCIe-based. Jan |
|
From: Hidde V. (E2M) <hve...@e2...> - 2013-09-11 10:26:10
|
Hello, In my last mail I had three issues: 1. A driver could not allocate an interrupt. 2. My particular realtek device was not supported. 3. I am unable to connect to a realtime application from a non-realtime application locally. I resolved the first issue by enabling shared interrupts in the Xenomai kernel options. To get the realtek device working I ported a recent Linux driver to RTNet. It works for my particular device and should also work for other currently unsupported network cards. However, I can give no guarantees. The driver is attached and can be used as a drop-in replacement for the current driver. I am still not sure how to solve the last issue. The suggestion to use the rtmac driver does not seem to work. Kind regards, Hidde Verstoep E2M Technologies B.V. On Thu, Aug 8, 2013 at 12:06 PM, Hidde Verstoep (E2M) < hve...@e2...> wrote: > Hello, > > I installed RTNet with Xenomai on two machines. Both machines have three > network cards, of which I need only two to work with RTNet. I have some > issues with these machines and I also have another RTNet question. > > PC1: > Intel Corporation 82574L Gigabit Network Connection [8086:10d3] > Intel Corporation 82572EI Gigabit Ethernet Controller (Copper) [8086:107d] > Intel Corporation 82574L Gigabit Network Connection [8086:10d3] > > All cards work in Linux without RTNet. I can succesfully open and use > rteth0 and rteth1 using the rt_e1000e driver. Can not open rteth2, it fails > with "rt_e1000e: Unable to allocate interrupt, Error: -16" in > "PC1-dmesg.log". The 82574L cards seem to share an interrupt. Since I only > need two network cards, this issue is not really important to me. But I > thought it would be good to report it anyway. > > PC2: > Intel Corporation 82541PI Gigabit Ethernet Controller [8086:107c] > Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet > controller [10ec:8168] > Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet > controller [10ec:8168] > > All cards work in Linux without RTNet. I can succesfully open and use > rteth0 using the rt_e1000 driver. Can not open the other two cards with the > rt_r8169 driver. Simply adding these devices to the pci device id table of > the driver is not enough. The error that occurs in this case can be found > in "PC2-dmesg.log". I think it is related to > http://sourceforge.net/mailarchive/message.php?msg_id=30580637 . Is there > any more information available since then? > > I am using a non-realtime application to control a realtime application > via the network. It is useful to be able to run both applications locally. > Is it possible to make a connection from the non-realtime application (via > the Linux network stack) to the realtime application (via the RTNet network > stack)? If so, how? > > Thanks in advance, > > Hidde Verstoep > E2M Technologies B.V. > |
|
From: Johan C. <joh...@si...> - 2013-09-09 13:08:56
|
Hello, Are there any PCI-express network cards that are supported by rtnet 0.9.12? I need to install two additional network cards in a computer with only one PCI slot free, preferably without changing the software. Alternatively, can anyone point me to a dual PCI network card supported by rtnet 0.9.12? Thanks, Johan --- Johan Cockx - Sikando bvba - +32 499 20 54 40 - http://www.sikando.com |
|
From: Sebastian H. <seb...@gm...> - 2013-08-27 11:06:23
|
Thanks for your reply! I repeated a few of the steps of the setup. I recompiled RTAI and RTnet. I also deleted the udev rules. But unfortunately i can't say for sure what caused the problem. |
|
From: Jan K. <jan...@si...> - 2013-08-27 10:27:24
|
On 2013-08-27 12:22, Jan Kiszka wrote: > On 2013-08-27 12:20, Sebastian Hölzer wrote: >> Hi, >> >> i got my setup running still using RTAI. I can use rtping and run the rtai >> example. What was the trick? >> >> However after starting the rtnet script the rt_e1000e driver says >> "rt_e1000e: Reset adapter" several times. >> >> After a few resets the communication is established. >> Do you have any idea why this is happening? You could compare these resets with those triggered by the Linux driver during startup. I don't know by heart how often this triggers, but I know that the startup phase takes a while here as well. >> >> Another thing i noticed is that the ping time varies within the range of >> cycle time up to two times the cycle time. >> Is this the normal behavier? Yes. Just think about the asynchronous timing, when the external event arrives and when it can be delivered over the cyclic channel. >> > > Please send via the mailing list. Oops, now I added the CC already. Jan -- Siemens AG, Corporate Technology, CT RTC ITP SES-DE Corporate Competence Center Embedded Linux |
|
From: Jan K. <jan...@si...> - 2013-08-27 10:22:27
|
On 2013-08-27 12:20, Sebastian Hölzer wrote: > Hi, > > i got my setup running still using RTAI. I can use rtping and run the rtai > example. > > However after starting the rtnet script the rt_e1000e driver says > "rt_e1000e: Reset adapter" several times. > > After a few resets the communication is established. > Do you have any idea why this is happening? > > Another thing i noticed is that the ping time varies within the range of > cycle time up to two times the cycle time. > Is this the normal behavier? > Please send via the mailing list. Thanks, Jan -- Siemens AG, Corporate Technology, CT RTC ITP SES-DE Corporate Competence Center Embedded Linux |
|
From: Frederik B. <fre...@tr...> - 2013-08-08 14:58:20
|
I think you need the rtmac driver on which you can put an udp or tcp module. Look at http://www.rts.uni-hannover.de/rtnet/lxr/source/Documentation/README.rtmac Frederik On 8 August 2013 12:06, Hidde Verstoep (E2M) <hve...@e2...>wrote: > Hello, > > I installed RTNet with Xenomai on two machines. Both machines have three > network cards, of which I need only two to work with RTNet. I have some > issues with these machines and I also have another RTNet question. > > PC1: > Intel Corporation 82574L Gigabit Network Connection [8086:10d3] > Intel Corporation 82572EI Gigabit Ethernet Controller (Copper) [8086:107d] > Intel Corporation 82574L Gigabit Network Connection [8086:10d3] > > All cards work in Linux without RTNet. I can succesfully open and use > rteth0 and rteth1 using the rt_e1000e driver. Can not open rteth2, it fails > with "rt_e1000e: Unable to allocate interrupt, Error: -16" in > "PC1-dmesg.log". The 82574L cards seem to share an interrupt. Since I only > need two network cards, this issue is not really important to me. But I > thought it would be good to report it anyway. > > PC2: > Intel Corporation 82541PI Gigabit Ethernet Controller [8086:107c] > Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet > controller [10ec:8168] > Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet > controller [10ec:8168] > > All cards work in Linux without RTNet. I can succesfully open and use > rteth0 using the rt_e1000 driver. Can not open the other two cards with the > rt_r8169 driver. Simply adding these devices to the pci device id table of > the driver is not enough. The error that occurs in this case can be found > in "PC2-dmesg.log". I think it is related to > http://sourceforge.net/mailarchive/message.php?msg_id=30580637 . Is there > any more information available since then? > > I am using a non-realtime application to control a realtime application > via the network. It is useful to be able to run both applications locally. > Is it possible to make a connection from the non-realtime application (via > the Linux network stack) to the realtime application (via the RTNet network > stack)? If so, how? > > Thanks in advance, > > Hidde Verstoep > E2M Technologies B.V. > > > ------------------------------------------------------------------------------ > Get 100% visibility into Java/.NET code with AppDynamics Lite! > It's a free troubleshooting tool designed for production. > Get down to code-level detail for bottlenecks, with <2% overhead. > Download for free and get started troubleshooting in minutes. > http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk > _______________________________________________ > RTnet-users mailing list > RTn...@li... > https://lists.sourceforge.net/lists/listinfo/rtnet-users > > |
|
From: Sebastian H. <seb...@gm...> - 2013-08-06 07:32:31
|
> 1. The rt_e1000e lacks some magic required to fully support your
> specific NIC (you could provide lspci -vv -s 07:00.0 to cross-check
> with what I have around)
>
That's what lspci -w -s 07:00.0 returns. IRQ 28 is not listed as a
Real-time IRQ used by RTAI.
Could this be the problem?
07:00.0 Ethernet controller: Intel Corporation 82574L Gigabit Network
Connection
Subsystem: Intel Corporation Device 0000
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR+ FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort-
<MAbort- >SERR- <PERR- INTx-
Latency: 0, Cache Line Size: 64 bytes
Interrupt: pin A routed to IRQ 28
Region 0: Memory at febe0000 (32-bit, non-prefetchable) [size=128K]
Region 2: I/O ports at ec00 [size=32]
Region 3: Memory at febdc000 (32-bit, non-prefetchable) [size=16K]
Capabilities: [c8] Power Management version 2
Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA
PME(D0+,D1-,D2-,D3hot+,D3cold+)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=1 PME-
Capabilities: [d0] MSI: Enable+ Count=1/1 Maskable- 64bit+
Address: 00000000fee0f00c Data: 41c9
Capabilities: [e0] Express (v1) Endpoint, MSI 00
DevCap: MaxPayload 256 bytes, PhantFunc 0, Latency L0s <512ns,
L1 <64us
ExtTag- AttnBtn- AttnInd- PwrInd- RBE+ FLReset-
DevCtl: Report errors: Correctable+ Non-Fatal+ Fatal+
Unsupported+
RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop+
MaxPayload 128 bytes, MaxReadReq 512 bytes
DevSta: CorrErr+ UncorrErr- FatalErr- UnsuppReq+ AuxPwr+
TransPend-
LnkCap: Port #0, Speed 2.5GT/s, Width x1, ASPM L0s L1, Latency
L0 <128ns, L1 <64us
ClockPM- Surprise- LLActRep- BwNot-
LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- Retrain- CommClk+
ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
LnkSta: Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk+
DLActive- BWMgmt- ABWMgmt-
Capabilities: [a0] MSI-X: Enable- Count=1 Masked-
Vector table: BAR=3 offset=00000000
PBA: BAR=3 offset=00002000
Capabilities: [100 v1] Advanced Error Reporting
UESta: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF-
MalfTLP- ECRC- UnsupReq- ACSViol-
UEMsk: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF-
MalfTLP- ECRC- UnsupReq- ACSViol-
UESvrt: DLP+ SDES- TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt- RxOF+
MalfTLP+ ECRC- UnsupReq- ACSViol-
CESta: RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+
CEMsk: RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+
AERCap: First Error Pointer: 00, GenCap- CGenEn- ChkCap- ChkEn-
Capabilities: [140 v1] Device Serial Number 00-d0-c9-ff-ff-e1-66-b7
Kernel driver in use: rt_e1000e
>
> 2. Something is broken in RTAI or that old RTAI/I-pipe patch that
> prevents those IRQs from being enabled or delivered. I'm only
> testing on 3.x kernels with Xenomai, so I can't help with that
> particular setup.
>
>
I will try to use a new Kernel with Xenomai if i can't get RTNet working on
the 2.6.32.11 Kernel.
Is there a certain setup you would recommend?
|
|
From: Jan K. <jan...@si...> - 2013-08-05 16:44:33
|
On 2013-08-05 16:40, Sebastian Hölzer wrote:
> I tried to force legacy interrupts but i still have the same exact problem.
>
> As for the RTAI reports, Realtime IRQs are listed .
> Correct me if i'm wrong but i think the attached dmesg output tells me
> that IRQ #18 is used for the network interface card.
> Is there more that i can do to narrow down the problem?
>
> ** Real-time IRQs used by RTAI:
>
> #18 at f8a5268f
> #1291 at f8806c74
> #1292 at f880671b
>
Yeah, hat likely means at least IRQ 18 for the first NIC was registered.
No idea why they do not make, though.
There are basically two potential reasons for the issue:
1. The rt_e1000e lacks some magic required to fully support your
specific NIC (you could provide lspci -vv -s 07:00.0 to cross-check
with what I have around)
2. Something is broken in RTAI or that old RTAI/I-pipe patch that
prevents those IRQs from being enabled or delivered. I'm only
testing on 3.x kernels with Xenomai, so I can't help with that
particular setup.
Jan
--
Siemens AG, Corporate Technology, CT RTC ITP SES-DE
Corporate Competence Center Embedded Linux
|
|
From: Sebastian H. <seb...@gm...> - 2013-08-05 14:40:13
|
I tried to force legacy interrupts but i still have the same exact problem.
As for the RTAI reports, Realtime IRQs are listed .
Correct me if i'm wrong but i think the attached dmesg output tells me that
IRQ #18 is used for the network interface card.
Is there more that i can do to narrow down the problem?
** Real-time IRQs used by RTAI:
#18 at f8a5268f
#1291 at f8806c74
#1292 at f880671b
[ 0.000000] Initializing cgroup subsys cpuset
[ 0.000000] Linux version 2.6.32.11 (root@debian) (gcc version 4.4.5
(Debian 4.4.5-8) ) #1 SMP Thu Jul 4 09:58:19 CDT 2013
[ 0.000000] KERNEL supported cpus:
[ 0.000000] Intel GenuineIntel
[ 0.000000] AMD AuthenticAMD
[ 0.000000] NSC Geode by NSC
[ 0.000000] Cyrix CyrixInstead
[ 0.000000] Centaur CentaurHauls
[ 0.000000] Transmeta GenuineTMx86
[ 0.000000] Transmeta TransmetaCPU
[ 0.000000] UMC UMC UMC UMC
[ 0.000000] BIOS-provided physical RAM map:
[ 0.000000] BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
[ 0.000000] BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)
[ 0.000000] BIOS-e820: 00000000000e0000 - 0000000000100000 (reserved)
[ 0.000000] BIOS-e820: 0000000000100000 - 000000007f6a0000 (usable)
[ 0.000000] BIOS-e820: 000000007f6a0000 - 000000007f6ae000 (ACPI data)
[ 0.000000] BIOS-e820: 000000007f6ae000 - 000000007f6e0000 (ACPI NVS)
[ 0.000000] BIOS-e820: 000000007f6e0000 - 0000000080000000 (reserved)
[ 0.000000] BIOS-e820: 00000000fee00000 - 00000000fee01000 (reserved)
[ 0.000000] BIOS-e820: 00000000ffb00000 - 0000000100000000 (reserved)
[ 0.000000] DMI present.
[ 0.000000] AMI BIOS detected: BIOS may corrupt low RAM, working around
it.
[ 0.000000] e820 update range: 0000000000000000 - 0000000000010000
(usable) ==> (reserved)
[ 0.000000] last_pfn = 0x7f6a0 max_arch_pfn = 0x100000
[ 0.000000] MTRR default type: uncachable
[ 0.000000] MTRR fixed ranges enabled:
[ 0.000000] 00000-9FFFF write-back
[ 0.000000] A0000-BFFFF uncachable
[ 0.000000] C0000-CFFFF write-protect
[ 0.000000] D0000-DFFFF uncachable
[ 0.000000] E0000-EFFFF write-through
[ 0.000000] F0000-FFFFF write-protect
[ 0.000000] MTRR variable ranges enabled:
[ 0.000000] 0 base 000000000 mask F80000000 write-back
[ 0.000000] 1 base 07F700000 mask FFFF00000 uncachable
[ 0.000000] 2 base 07F800000 mask FFF800000 uncachable
[ 0.000000] 3 disabled
[ 0.000000] 4 disabled
[ 0.000000] 5 disabled
[ 0.000000] 6 disabled
[ 0.000000] 7 disabled
[ 0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new
0x7010600070106
[ 0.000000] initial memory mapped : 0 - 01800000
[ 0.000000] init_memory_mapping: 0000000000000000-00000000373fe000
[ 0.000000] 0000000000 - 0000400000 page 4k
[ 0.000000] 0000400000 - 0037000000 page 2M
[ 0.000000] 0037000000 - 00373fe000 page 4k
[ 0.000000] kernel direct mapping tables up to 373fe000 @ 10000-16000
[ 0.000000] RAMDISK: 37730000 - 37feff2c
[ 0.000000] Allocated new RAMDISK: 00100000 - 009bff2c
[ 0.000000] Move RAMDISK from 0000000037730000 - 0000000037feff2b to
00100000 - 009bff2b
[ 0.000000] ACPI: RSDP 000f9dc0 00024 (v02 ACPIAM)
[ 0.000000] ACPI: XSDT 7f6a0100 00054 (v01 072611 XSDT1025 20110726 MSFT
00000097)
[ 0.000000] ACPI: FACP 7f6a0290 000F4 (v04 072611 FACP1025 20110726 MSFT
00000097)
[ 0.000000] ACPI: DSDT 7f6a0440 05E58 (v02 763Dx 763Dx02Q 00000001 INTL
20051117)
[ 0.000000] ACPI: FACS 7f6ae000 00040
[ 0.000000] ACPI: APIC 7f6a0390 0006C (v02 072611 APIC1025 20110726 MSFT
00000097)
[ 0.000000] ACPI: MCFG 7f6a0400 0003C (v01 072611 OEMMCFG 20110726 MSFT
00000097)
[ 0.000000] ACPI: OEMB 7f6ae040 00072 (v01 072611 OEMB1025 20110726 MSFT
00000097)
[ 0.000000] ACPI: GSCI 7f6ae0c0 02024 (v01 072611 GMCHSCI 20110726 MSFT
00000097)
[ 0.000000] ACPI: SSDT 7f6b0720 004F0 (v01 PmRef CpuPm 00003000 INTL
20051117)
[ 0.000000] ACPI: Local APIC address 0xfee00000
[ 0.000000] 1154MB HIGHMEM available.
[ 0.000000] 883MB LOWMEM available.
[ 0.000000] mapped low ram: 0 - 373fe000
[ 0.000000] low ram: 0 - 373fe000
[ 0.000000] node 0 low ram: 00000000 - 373fe000
[ 0.000000] node 0 bootmap 00012000 - 00018e80
[ 0.000000] (9 early reservations) ==> bootmem [0000000000 - 00373fe000]
[ 0.000000] #0 [0000000000 - 0000001000] BIOS data page ==>
[0000000000 - 0000001000]
[ 0.000000] #1 [0000001000 - 0000002000] EX TRAMPOLINE ==>
[0000001000 - 0000002000]
[ 0.000000] #2 [0000006000 - 0000007000] TRAMPOLINE ==>
[0000006000 - 0000007000]
[ 0.000000] #3 [0001000000 - 00014dd2d4] TEXT DATA BSS ==>
[0001000000 - 00014dd2d4]
[ 0.000000] #4 [000009fc00 - 0000100000] BIOS reserved ==>
[000009fc00 - 0000100000]
[ 0.000000] #5 [00014de000 - 00014e41bf] BRK ==>
[00014de000 - 00014e41bf]
[ 0.000000] #6 [0000010000 - 0000012000] PGTABLE ==>
[0000010000 - 0000012000]
[ 0.000000] #7 [0000100000 - 00009bff2c] NEW RAMDISK ==>
[0000100000 - 00009bff2c]
[ 0.000000] #8 [0000012000 - 0000019000] BOOTMAP ==>
[0000012000 - 0000019000]
[ 0.000000] found SMP MP-table at [c00ff780] ff780
[ 0.000000] Zone PFN ranges:
[ 0.000000] DMA 0x00000010 -> 0x00001000
[ 0.000000] Normal 0x00001000 -> 0x000373fe
[ 0.000000] HighMem 0x000373fe -> 0x0007f6a0
[ 0.000000] Movable zone start PFN for each node
[ 0.000000] early_node_map[2] active PFN ranges
[ 0.000000] 0: 0x00000010 -> 0x0000009f
[ 0.000000] 0: 0x00000100 -> 0x0007f6a0
[ 0.000000] On node 0 totalpages: 521775
[ 0.000000] free_area_init_node: node 0, pgdat c139f780, node_mem_map
c14e6200
[ 0.000000] DMA zone: 32 pages used for memmap
[ 0.000000] DMA zone: 0 pages reserved
[ 0.000000] DMA zone: 3951 pages, LIFO batch:0
[ 0.000000] Normal zone: 1736 pages used for memmap
[ 0.000000] Normal zone: 220470 pages, LIFO batch:31
[ 0.000000] HighMem zone: 2310 pages used for memmap
[ 0.000000] HighMem zone: 293276 pages, LIFO batch:31
[ 0.000000] Using APIC driver default
[ 0.000000] ACPI: PM-Timer IO Port: 0x808
[ 0.000000] ACPI: Local APIC address 0xfee00000
[ 0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x01] enabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x04] lapic_id[0x03] enabled)
[ 0.000000] ACPI: IOAPIC (id[0x04] address[0xfec00000] gsi_base[0])
[ 0.000000] IOAPIC[0]: apic_id 4, version 32, address 0xfec00000, GSI
0-23
[ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
[ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
[ 0.000000] ACPI: IRQ0 used by override.
[ 0.000000] ACPI: IRQ2 used by override.
[ 0.000000] ACPI: IRQ9 used by override.
[ 0.000000] Using ACPI (MADT) for SMP configuration information
[ 0.000000] SMP: Allowing 4 CPUs, 0 hotplug CPUs
[ 0.000000] nr_irqs_gsi: 24
[ 0.000000] PM: Registered nosave memory: 000000000009f000 -
00000000000a0000
[ 0.000000] PM: Registered nosave memory: 00000000000a0000 -
00000000000e0000
[ 0.000000] PM: Registered nosave memory: 00000000000e0000 -
0000000000100000
[ 0.000000] Allocating PCI resources starting at 80000000 (gap:
80000000:7ee00000)
[ 0.000000] NR_CPUS:32 nr_cpumask_bits:32 nr_cpu_ids:4 nr_node_ids:1
[ 0.000000] PERCPU: Embedded 19 pages/cpu @c2800000 s55992 r0 d21832
u1048576
[ 0.000000] pcpu-alloc: s55992 r0 d21832 u1048576 alloc=1*4194304
[ 0.000000] pcpu-alloc: [0] 0 1 2 3
[ 0.000000] Built 1 zonelists in Zone order, mobility grouping on.
Total pages: 517697
[ 0.000000] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-2.6.32.11
root=UUID=84c9ed4f-85f0-4143-bbfc-245fbb2f4949 ro quiet pcie_aspm=off
[ 0.000000] PCIe ASPM is disabled
[ 0.000000] PID hash table entries: 4096 (order: 2, 16384 bytes)
[ 0.000000] Dentry cache hash table entries: 131072 (order: 7, 524288
bytes)
[ 0.000000] Inode-cache hash table entries: 65536 (order: 6, 262144
bytes)
[ 0.000000] Enabling fast FPU save and restore... done.
[ 0.000000] Enabling unmasked SIMD FPU exception support... done.
[ 0.000000] Initializing CPU#0
[ 0.000000] Initializing HighMem for node 0 (000373fe:0007f6a0)
[ 0.000000] Memory: 2054588k/2087552k available (2468k kernel code,
31460k reserved, 1280k data, 364k init, 1182344k highmem)
[ 0.000000] virtual kernel memory layout:
[ 0.000000] fixmap : 0xffd57000 - 0xfffff000 (2720 kB)
[ 0.000000] pkmap : 0xff400000 - 0xff800000 (4096 kB)
[ 0.000000] vmalloc : 0xf7bfe000 - 0xff3fe000 ( 120 MB)
[ 0.000000] lowmem : 0xc0000000 - 0xf73fe000 ( 883 MB)
[ 0.000000] .init : 0xc13aa000 - 0xc1405000 ( 364 kB)
[ 0.000000] .data : 0xc1269126 - 0xc13a9240 (1280 kB)
[ 0.000000] .text : 0xc1000000 - 0xc1269126 (2468 kB)
[ 0.000000] Checking if this processor honours the WP bit even in
supervisor mode...Ok.
[ 0.000000] SLUB: Genslabs=13, HWalign=64, Order=0-3, MinObjects=0,
CPUs=4, Nodes=1
[ 0.000000] Hierarchical RCU implementation.
[ 0.000000] NR_IRQS:1280
[ 0.000000] Extended CMOS year: 2000
[ 0.000000] I-pipe 2.6-03: pipeline enabled.
[ 0.000000] Console: colour dummy device 80x25
[ 0.000000] console [tty0] enabled
[ 0.000000] Fast TSC calibration using PIT
[ 0.000000] Detected 1662.263 MHz processor.
[ 0.004008] Calibrating delay loop (skipped), value calculated using
timer frequency.. 3324.52 BogoMIPS (lpj=6649052)
[ 0.004049] Security Framework initialized
[ 0.004057] SELinux: Disabled at boot.
[ 0.004071] Mount-cache hash table entries: 512
[ 0.004277] Initializing cgroup subsys ns
[ 0.004285] Initializing cgroup subsys cpuacct
[ 0.004294] Initializing cgroup subsys devices
[ 0.004299] Initializing cgroup subsys freezer
[ 0.004304] Initializing cgroup subsys net_cls
[ 0.004334] CPU: L1 I cache: 32K, L1 D cache: 24K
[ 0.004340] CPU: L2 cache: 512K
[ 0.004345] CPU: Physical Processor ID: 0
[ 0.004349] CPU: Processor Core ID: 0
[ 0.004355] mce: CPU supports 5 MCE banks
[ 0.004369] CPU0: Thermal monitoring enabled (TM1)
[ 0.004383] Performance Events: Atom events, Intel PMU driver.
[ 0.004395] ... version: 3
[ 0.004399] ... bit width: 40
[ 0.004403] ... generic registers: 2
[ 0.004408] ... value mask: 000000ffffffffff
[ 0.004412] ... max period: 000000007fffffff
[ 0.004417] ... fixed-purpose events: 3
[ 0.004421] ... event mask: 0000000700000003
[ 0.004430] Checking 'hlt' instruction... OK.
[ 0.020385] ACPI: Core revision 20090903
[ 0.036091] Enabling APIC mode: Flat. Using 1 I/O APICs
[ 0.036480] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
[ 0.040001] ..MP-BIOS bug: 8254 timer not connected to IO-APIC
[ 0.040001] ...trying to set up timer (IRQ0) through the 8259A ...
[ 0.040001] ..... (found apic 0 pin 2) ...
[ 0.080812] ....... works.
[ 0.080817] CPU0: Intel(R) Atom(TM) CPU D510 @ 1.66GHz stepping 0a
[ 0.084001] APIC calibration not consistent with PM-Timer: 120ms instead
of 100ms
[ 0.084001] APIC delta adjusted to PM-Timer: 1039061 (1246950)
[ 0.084001] Booting processor 1 APIC 0x2 ip 0x6000
[ 0.008000] Initializing CPU#1
[ 0.008000] CPU: L1 I cache: 32K, L1 D cache: 24K
[ 0.008000] CPU: L2 cache: 512K
[ 0.008000] CPU: Physical Processor ID: 0
[ 0.008000] CPU: Processor Core ID: 1
[ 0.008000] CPU1: Thermal monitoring enabled (TM1)
[ 0.168049] CPU1: Intel(R) Atom(TM) CPU D510 @ 1.66GHz stepping 0a
[ 0.168067] checking TSC synchronization [CPU#0 -> CPU#1]: passed.
[ 0.172203] Booting processor 2 APIC 0x1 ip 0x6000
[ 0.008000] Initializing CPU#2
[ 0.008000] CPU: L1 I cache: 32K, L1 D cache: 24K
[ 0.008000] CPU: L2 cache: 512K
[ 0.008000] CPU: Physical Processor ID: 0
[ 0.008000] CPU: Processor Core ID: 0
[ 0.008000] CPU2: Thermal monitoring enabled (TM1)
[ 0.260085] CPU2: Intel(R) Atom(TM) CPU D510 @ 1.66GHz stepping 0a
[ 0.260111] checking TSC synchronization [CPU#0 -> CPU#2]: passed.
[ 0.264227] Booting processor 3 APIC 0x3 ip 0x6000
[ 0.008000] Initializing CPU#3
[ 0.008000] CPU: L1 I cache: 32K, L1 D cache: 24K
[ 0.008000] CPU: L2 cache: 512K
[ 0.008000] CPU: Physical Processor ID: 0
[ 0.008000] CPU: Processor Core ID: 1
[ 0.008000] CPU3: Thermal monitoring enabled (TM1)
[ 0.352105] CPU3: Intel(R) Atom(TM) CPU D510 @ 1.66GHz stepping 0a
[ 0.352128] checking TSC synchronization [CPU#0 -> CPU#3]: passed.
[ 0.356062] Brought up 4 CPUs
[ 0.356068] Total of 4 processors activated (13286.34 BogoMIPS).
[ 0.356946] CPU0 attaching sched-domain:
[ 0.356955] domain 0: span 0,2 level SIBLING
[ 0.356961] groups: 0 (cpu_power = 589) 2 (cpu_power = 589)
[ 0.356975] domain 1: span 0,2 level MC
[ 0.356981] groups: 0,2 (cpu_power = 1178)
[ 0.356991] domain 2: span 0-3 level CPU
[ 0.356997] groups: 0,2 (cpu_power = 1178) 1,3 (cpu_power = 1178)
[ 0.357013] CPU1 attaching sched-domain:
[ 0.357018] domain 0: span 1,3 level SIBLING
[ 0.357024] groups: 1 (cpu_power = 589) 3 (cpu_power = 589)
[ 0.357037] domain 1: span 1,3 level MC
[ 0.357042] groups: 1,3 (cpu_power = 1178)
[ 0.357052] domain 2: span 0-3 level CPU
[ 0.357058] groups: 1,3 (cpu_power = 1178) 0,2 (cpu_power = 1178)
[ 0.357072] CPU2 attaching sched-domain:
[ 0.357077] domain 0: span 0,2 level SIBLING
[ 0.357083] groups: 2 (cpu_power = 589) 0 (cpu_power = 589)
[ 0.357096] domain 1: span 0,2 level MC
[ 0.357101] groups: 0,2 (cpu_power = 1178)
[ 0.357111] domain 2: span 0-3 level CPU
[ 0.357116] groups: 0,2 (cpu_power = 1178) 1,3 (cpu_power = 1178)
[ 0.357130] CPU3 attaching sched-domain:
[ 0.357135] domain 0: span 1,3 level SIBLING
[ 0.357141] groups: 3 (cpu_power = 589) 1 (cpu_power = 589)
[ 0.357154] domain 1: span 1,3 level MC
[ 0.357159] groups: 1,3 (cpu_power = 1178)
[ 0.357169] domain 2: span 0-3 level CPU
[ 0.357174] groups: 1,3 (cpu_power = 1178) 0,2 (cpu_power = 1178)
[ 0.357561] devtmpfs: initialized
[ 0.357561] regulator: core version 0.5
[ 0.357561] NET: Registered protocol family 16
[ 0.357561] ACPI: bus type pci registered
[ 0.357561] PCI: MCFG configuration 0: base e0000000 segment 0 buses 0 -
255
[ 0.357561] PCI: Not using MMCONFIG.
[ 0.357561] PCI: PCI BIOS revision 3.00 entry at 0xf0031, last bus=7
[ 0.357561] PCI: Using configuration type 1 for base access
[ 0.360138] bio: create slab <bio-0> at 0
[ 0.361458] ACPI: EC: Look up EC in DSDT
[ 0.367704] ACPI: Executed 1 blocks of module-level executable AML code
[ 0.379200] ACPI: Interpreter enabled
[ 0.379216] ACPI: (supports S0 S1 S3 S4 S5)
[ 0.379273] ACPI: Using IOAPIC for interrupt routing
[ 0.379369] PCI: MCFG configuration 0: base e0000000 segment 0 buses 0 -
255
[ 0.387125] PCI: MCFG area at e0000000 reserved in ACPI motherboard
resources
[ 0.387132] PCI: Using MMCONFIG for extended config space
[ 0.403376] ACPI: EC: GPE = 0x16, I/O: command/status = 0x66, data = 0x62
[ 0.404551] ACPI: No dock devices found.
[ 0.405264] ACPI: PCI Root Bridge [PCI0] (0000:00)
[ 0.405394] pci 0000:00:02.0: reg 10 32bit mmio: [0xfe500000-0xfe57ffff]
[ 0.405404] pci 0000:00:02.0: reg 14 io port: [0x8400-0x8407]
[ 0.405413] pci 0000:00:02.0: reg 18 32bit mmio pref:
[0xd0000000-0xdfffffff]
[ 0.405422] pci 0000:00:02.0: reg 1c 32bit mmio: [0xfe400000-0xfe4fffff]
[ 0.405472] pci 0000:00:02.1: reg 10 32bit mmio: [0xfe380000-0xfe3fffff]
[ 0.405570] pci 0000:00:1b.0: reg 10 64bit mmio: [0xfe5f8000-0xfe5fbfff]
[ 0.405620] pci 0000:00:1b.0: PME# supported from D0 D3hot D3cold
[ 0.405628] pci 0000:00:1b.0: PME# disabled
[ 0.405702] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
[ 0.405709] pci 0000:00:1c.0: PME# disabled
[ 0.405784] pci 0000:00:1c.1: PME# supported from D0 D3hot D3cold
[ 0.405792] pci 0000:00:1c.1: PME# disabled
[ 0.405867] pci 0000:00:1c.2: PME# supported from D0 D3hot D3cold
[ 0.405874] pci 0000:00:1c.2: PME# disabled
[ 0.405949] pci 0000:00:1c.3: PME# supported from D0 D3hot D3cold
[ 0.405956] pci 0000:00:1c.3: PME# disabled
[ 0.406013] pci 0000:00:1d.0: reg 20 io port: [0x8c00-0x8c1f]
[ 0.406073] pci 0000:00:1d.1: reg 20 io port: [0x8880-0x889f]
[ 0.406132] pci 0000:00:1d.2: reg 20 io port: [0x8800-0x881f]
[ 0.406190] pci 0000:00:1d.3: reg 20 io port: [0x8480-0x849f]
[ 0.406254] pci 0000:00:1d.7: reg 10 32bit mmio: [0xfe5ff800-0xfe5ffbff]
[ 0.406311] pci 0000:00:1d.7: PME# supported from D0 D3hot D3cold
[ 0.406319] pci 0000:00:1d.7: PME# disabled
[ 0.406468] pci 0000:00:1f.0: Force enabled HPET at 0xfed00000
[ 0.406479] pci 0000:00:1f.0: quirk: region 0800-087f claimed by ICH6
ACPI/GPIO/TCO
[ 0.406487] pci 0000:00:1f.0: quirk: region 0500-053f claimed by ICH6
GPIO
[ 0.406495] pci 0000:00:1f.0: ICH7 LPC Generic IO decode 1 PIO at 0280
(mask 007f)
[ 0.406548] pci 0000:00:1f.1: reg 10 io port: [0x00-0x07]
[ 0.406559] pci 0000:00:1f.1: reg 14 io port: [0x00-0x03]
[ 0.406569] pci 0000:00:1f.1: reg 18 io port: [0x8f0-0x8f7]
[ 0.406580] pci 0000:00:1f.1: reg 1c io port: [0x8f8-0x8fb]
[ 0.406591] pci 0000:00:1f.1: reg 20 io port: [0xffa0-0xffaf]
[ 0.406641] pci 0000:00:1f.2: reg 10 io port: [0x9c00-0x9c07]
[ 0.406652] pci 0000:00:1f.2: reg 14 io port: [0x9880-0x9883]
[ 0.406662] pci 0000:00:1f.2: reg 18 io port: [0x9800-0x9807]
[ 0.406672] pci 0000:00:1f.2: reg 1c io port: [0x9480-0x9483]
[ 0.406682] pci 0000:00:1f.2: reg 20 io port: [0x9400-0x940f]
[ 0.406692] pci 0000:00:1f.2: reg 24 io port: [0x9080-0x908f]
[ 0.406718] pci 0000:00:1f.2: PME# supported from D3hot
[ 0.406725] pci 0000:00:1f.2: PME# disabled
[ 0.406752] pci 0000:00:1f.3: reg 10 32bit mmio: [0xfe5ffc00-0xfe5ffcff]
[ 0.406774] pci 0000:00:1f.3: reg 20 io port: [0x400-0x41f]
[ 0.406872] pci 0000:02:00.0: reg 10 64bit mmio pref:
[0xfdff0000-0xfdffffff]
[ 0.406971] pci 0000:02:00.0: disabling ASPM on pre-1.1 PCIe device.
You can enable it with 'pcie_aspm=force'
[ 0.407011] pci 0000:00:1c.0: bridge io port: [0xc000-0xcfff]
[ 0.407019] pci 0000:00:1c.0: bridge 32bit mmio: [0xfe700000-0xfe7fffff]
[ 0.407029] pci 0000:00:1c.0: bridge 64bit mmio pref:
[0xfdf00000-0xfdffffff]
[ 0.407087] pci 0000:03:00.0: reg 14 io port: [0xcc00-0xcc7f]
[ 0.407103] pci 0000:03:00.0: reg 18 io port: [0xc800-0xc8ff]
[ 0.407148] pci 0000:03:00.0: reg 30 32bit mmio pref:
[0xfe7f0000-0xfe7f07ff]
[ 0.407250] pci 0000:02:00.0: bridge io port: [0xc000-0xcfff]
[ 0.407260] pci 0000:02:00.0: bridge 32bit mmio: [0xfe700000-0xfe7fffff]
[ 0.407353] pci 0000:04:00.0: reg 14 32bit mmio: [0xfe8ff000-0xfe8fffff]
[ 0.407425] pci 0000:04:00.0: supports D1 D2
[ 0.407504] pci 0000:00:1c.1: bridge 32bit mmio: [0xfe800000-0xfe9fffff]
[ 0.407576] pci 0000:05:00.0: reg 10 32bit mmio: [0xfe9ff800-0xfe9fffff]
[ 0.407590] pci 0000:05:00.0: reg 14 32bit mmio: [0xfe9f8000-0xfe9fbfff]
[ 0.407664] pci 0000:05:00.0: supports D1 D2
[ 0.407669] pci 0000:05:00.0: PME# supported from D0 D1 D2 D3hot
[ 0.407678] pci 0000:05:00.0: PME# disabled
[ 0.407770] pci 0000:04:00.0: bridge 32bit mmio: [0xfe900000-0xfe9fffff]
[ 0.407864] pci 0000:06:00.0: reg 10 32bit mmio: [0xfeae0000-0xfeafffff]
[ 0.407889] pci 0000:06:00.0: reg 18 io port: [0xdc00-0xdc1f]
[ 0.407905] pci 0000:06:00.0: reg 1c 32bit mmio: [0xfeadc000-0xfeadffff]
[ 0.407994] pci 0000:06:00.0: PME# supported from D0 D3hot D3cold
[ 0.408014] pci 0000:06:00.0: PME# disabled
[ 0.408103] pci 0000:00:1c.2: bridge io port: [0xd000-0xdfff]
[ 0.408111] pci 0000:00:1c.2: bridge 32bit mmio: [0xfea00000-0xfeafffff]
[ 0.408195] pci 0000:07:00.0: reg 10 32bit mmio: [0xfebe0000-0xfebfffff]
[ 0.408221] pci 0000:07:00.0: reg 18 io port: [0xec00-0xec1f]
[ 0.408236] pci 0000:07:00.0: reg 1c 32bit mmio: [0xfebdc000-0xfebdffff]
[ 0.408325] pci 0000:07:00.0: PME# supported from D0 D3hot D3cold
[ 0.408335] pci 0000:07:00.0: PME# disabled
[ 0.408423] pci 0000:00:1c.3: bridge io port: [0xe000-0xefff]
[ 0.408431] pci 0000:00:1c.3: bridge 32bit mmio: [0xfeb00000-0xfebfffff]
[ 0.408498] pci 0000:01:0e.0: reg 10 io port: [0xbc00-0xbc07]
[ 0.408509] pci 0000:01:0e.0: reg 14 io port: [0xb880-0xb887]
[ 0.408520] pci 0000:01:0e.0: reg 18 io port: [0xb800-0xb807]
[ 0.408531] pci 0000:01:0e.0: reg 1c io port: [0xb480-0xb487]
[ 0.408542] pci 0000:01:0e.0: reg 20 io port: [0xb400-0xb41f]
[ 0.408553] pci 0000:01:0e.0: reg 24 32bit mmio: [0xfe6ff000-0xfe6fffff]
[ 0.408582] pci 0000:01:0e.0: supports D2
[ 0.408587] pci 0000:01:0e.0: PME# supported from D0 D2 D3hot
[ 0.408594] pci 0000:01:0e.0: PME# disabled
[ 0.408634] pci 0000:01:0e.1: reg 10 io port: [0xb000-0xb0ff]
[ 0.408646] pci 0000:01:0e.1: reg 14 32bit mmio: [0xfe6fe000-0xfe6fefff]
[ 0.408657] pci 0000:01:0e.1: reg 18 io port: [0xac00-0xac1f]
[ 0.408668] pci 0000:01:0e.1: reg 1c 32bit mmio: [0xfe6fd000-0xfe6fdfff]
[ 0.408706] pci 0000:01:0e.1: supports D2
[ 0.408711] pci 0000:01:0e.1: PME# supported from D0 D2 D3hot
[ 0.408718] pci 0000:01:0e.1: PME# disabled
[ 0.408763] pci 0000:00:1e.0: transparent bridge
[ 0.408771] pci 0000:00:1e.0: bridge io port: [0xa000-0xbfff]
[ 0.408778] pci 0000:00:1e.0: bridge 32bit mmio: [0xfe600000-0xfe6fffff]
[ 0.408810] pci_bus 0000:00: on NUMA node 0
[ 0.408820] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
[ 0.409098] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.P0P1._PRT]
[ 0.409587] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.P0P4._PRT]
[ 0.409709] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.P0P5._PRT]
[ 0.409882] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.P0P6._PRT]
[ 0.410003] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.P0P7._PRT]
[ 0.442472] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 10 *11 12 14
15)
[ 0.442697] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 *6 7 10 11 12 14
15)
[ 0.444234] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 *4 5 6 7 10 11 12 14
15)
[ 0.444455] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 7 *10 11 12 14
15)
[ 0.444676] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 11 12 14
*15)
[ 0.444897] ACPI: PCI Interrupt Link [LNKF] (IRQs *3 4 5 6 7 10 11 12 14
15)
[ 0.445118] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 *10 11 12 14
15)
[ 0.445339] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 *5 6 7 10 11 12 14
15)
[ 0.445549] vgaarb: device added:
PCI:0000:00:02.0,decodes=io+mem,owns=io+mem,locks=none
[ 0.445576] vgaarb: loaded
[ 0.445653] PCI: Using ACPI for IRQ routing
[ 0.445653] hpet clockevent registered
[ 0.445653] HPET: 3 timers in total, 0 timers will be used for per-cpu
timer
[ 0.445653] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0
[ 0.445653] hpet0: 3 comparators, 64-bit 14.318180 MHz counter
[ 0.456013] Switching to clocksource tsc
[ 0.458361] pnp: PnP ACPI init
[ 0.458400] ACPI: bus type pnp registered
[ 0.465015] pnp: PnP ACPI: found 13 devices
[ 0.465022] ACPI: ACPI bus type pnp unregistered
[ 0.465030] PnPBIOS: Disabled by ACPI PNP
[ 0.465056] system 00:01: iomem range 0xfed14000-0xfed19fff has been
reserved
[ 0.465063] system 00:01: iomem range 0xfed90000-0xfed93fff has been
reserved
[ 0.465080] system 00:07: iomem range 0xffc00000-0xffefffff has been
reserved
[ 0.465093] system 00:08: iomem range 0xfec00000-0xfec00fff could not be
reserved
[ 0.465101] system 00:08: iomem range 0xfee00000-0xfee00fff has been
reserved
[ 0.465115] system 00:09: ioport range 0x900-0x90f has been reserved
[ 0.465129] system 00:0a: ioport range 0x4d0-0x4d1 has been reserved
[ 0.465136] system 00:0a: ioport range 0x800-0x87f has been reserved
[ 0.465144] system 00:0a: ioport range 0x500-0x53f has been reserved
[ 0.465152] system 00:0a: iomem range 0xfed1c000-0xfed1ffff has been
reserved
[ 0.465159] system 00:0a: iomem range 0xfed20000-0xfed3ffff has been
reserved
[ 0.465167] system 00:0a: iomem range 0xfed40000-0xfed8ffff has been
reserved
[ 0.465180] system 00:0b: iomem range 0xe0000000-0xefffffff has been
reserved
[ 0.465193] system 00:0c: iomem range 0x0-0x9ffff could not be reserved
[ 0.465201] system 00:0c: iomem range 0xc0000-0xcffff could not be
reserved
[ 0.465208] system 00:0c: iomem range 0xe0000-0xfffff could not be
reserved
[ 0.465216] system 00:0c: iomem range 0x100000-0x7f6fffff could not be
reserved
[ 0.465224] system 00:0c: iomem range 0xfed90000-0xffffffff could not be
reserved
[ 0.500176] pci 0000:02:00.0: PCI bridge, secondary bus 0000:03
[ 0.500186] pci 0000:02:00.0: IO window: 0xc000-0xcfff
[ 0.500199] pci 0000:02:00.0: MEM window: 0xfe700000-0xfe7fffff
[ 0.500208] pci 0000:02:00.0: PREFETCH window: disabled
[ 0.500223] pci 0000:00:1c.0: PCI bridge, secondary bus 0000:02
[ 0.500230] pci 0000:00:1c.0: IO window: 0xc000-0xcfff
[ 0.500238] pci 0000:00:1c.0: MEM window: 0xfe700000-0xfe7fffff
[ 0.500247] pci 0000:00:1c.0: PREFETCH window:
0x000000fdf00000-0x000000fdffffff
[ 0.500258] pci 0000:04:00.0: PCI bridge, secondary bus 0000:05
[ 0.500262] pci 0000:04:00.0: IO window: disabled
[ 0.500273] pci 0000:04:00.0: MEM window: 0xfe900000-0xfe9fffff
[ 0.500282] pci 0000:04:00.0: PREFETCH window: disabled
[ 0.500294] pci 0000:00:1c.1: PCI bridge, secondary bus 0000:04
[ 0.500301] pci 0000:00:1c.1: IO window: 0x1000-0x1fff
[ 0.500309] pci 0000:00:1c.1: MEM window: 0xfe800000-0xfe9fffff
[ 0.500317] pci 0000:00:1c.1: PREFETCH window:
0x00000080000000-0x000000801fffff
[ 0.500328] pci 0000:00:1c.2: PCI bridge, secondary bus 0000:06
[ 0.500334] pci 0000:00:1c.2: IO window: 0xd000-0xdfff
[ 0.500343] pci 0000:00:1c.2: MEM window: 0xfea00000-0xfeafffff
[ 0.500351] pci 0000:00:1c.2: PREFETCH window:
0x00000080200000-0x000000803fffff
[ 0.500361] pci 0000:00:1c.3: PCI bridge, secondary bus 0000:07
[ 0.500368] pci 0000:00:1c.3: IO window: 0xe000-0xefff
[ 0.500376] pci 0000:00:1c.3: MEM window: 0xfeb00000-0xfebfffff
[ 0.500384] pci 0000:00:1c.3: PREFETCH window:
0x00000080400000-0x000000805fffff
[ 0.500395] pci 0000:00:1e.0: PCI bridge, secondary bus 0000:01
[ 0.500401] pci 0000:00:1e.0: IO window: 0xa000-0xbfff
[ 0.500410] pci 0000:00:1e.0: MEM window: 0xfe600000-0xfe6fffff
[ 0.500417] pci 0000:00:1e.0: PREFETCH window: disabled
[ 0.500446] pci 0000:00:1c.0: PCI INT A -> GSI 22 (level, low) -> IRQ 22
[ 0.500454] pci 0000:00:1c.0: setting latency timer to 64
[ 0.500471] pci 0000:02:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
[ 0.500482] pci 0000:02:00.0: setting latency timer to 64
[ 0.500496] pci 0000:00:1c.1: enabling device (0106 -> 0107)
[ 0.500506] pci 0000:00:1c.1: PCI INT B -> GSI 23 (level, low) -> IRQ 23
[ 0.500514] pci 0000:00:1c.1: setting latency timer to 64
[ 0.500532] pci 0000:04:00.0: setting latency timer to 64
[ 0.500548] pci 0000:00:1c.2: PCI INT C -> GSI 20 (level, low) -> IRQ 20
[ 0.500556] pci 0000:00:1c.2: setting latency timer to 64
[ 0.500572] pci 0000:00:1c.3: PCI INT D -> GSI 21 (level, low) -> IRQ 21
[ 0.500579] pci 0000:00:1c.3: setting latency timer to 64
[ 0.500590] pci 0000:00:1e.0: setting latency timer to 64
[ 0.500599] pci_bus 0000:00: resource 0 io: [0x00-0xffff]
[ 0.500605] pci_bus 0000:00: resource 1 mem: [0x000000-0xffffffff]
[ 0.500612] pci_bus 0000:02: resource 0 io: [0xc000-0xcfff]
[ 0.500619] pci_bus 0000:02: resource 1 mem: [0xfe700000-0xfe7fffff]
[ 0.500625] pci_bus 0000:02: resource 2 pref mem [0xfdf00000-0xfdffffff]
[ 0.500632] pci_bus 0000:03: resource 0 io: [0xc000-0xcfff]
[ 0.500638] pci_bus 0000:03: resource 1 mem: [0xfe700000-0xfe7fffff]
[ 0.500645] pci_bus 0000:04: resource 0 io: [0x1000-0x1fff]
[ 0.500651] pci_bus 0000:04: resource 1 mem: [0xfe800000-0xfe9fffff]
[ 0.500658] pci_bus 0000:04: resource 2 pref mem [0x80000000-0x801fffff]
[ 0.500664] pci_bus 0000:05: resource 1 mem: [0xfe900000-0xfe9fffff]
[ 0.500671] pci_bus 0000:06: resource 0 io: [0xd000-0xdfff]
[ 0.500677] pci_bus 0000:06: resource 1 mem: [0xfea00000-0xfeafffff]
[ 0.500684] pci_bus 0000:06: resource 2 pref mem [0x80200000-0x803fffff]
[ 0.500690] pci_bus 0000:07: resource 0 io: [0xe000-0xefff]
[ 0.500696] pci_bus 0000:07: resource 1 mem: [0xfeb00000-0xfebfffff]
[ 0.500703] pci_bus 0000:07: resource 2 pref mem [0x80400000-0x805fffff]
[ 0.500710] pci_bus 0000:01: resource 0 io: [0xa000-0xbfff]
[ 0.500716] pci_bus 0000:01: resource 1 mem: [0xfe600000-0xfe6fffff]
[ 0.500722] pci_bus 0000:01: resource 3 io: [0x00-0xffff]
[ 0.500728] pci_bus 0000:01: resource 4 mem: [0x000000-0xffffffff]
[ 0.500798] NET: Registered protocol family 2
[ 0.500986] IP route cache hash table entries: 32768 (order: 5, 131072
bytes)
[ 0.501609] TCP established hash table entries: 131072 (order: 8,
1048576 bytes)
[ 0.502532] TCP bind hash table entries: 65536 (order: 7, 524288 bytes)
[ 0.502959] TCP: Hash tables configured (established 131072 bind 65536)
[ 0.502965] TCP reno registered
[ 0.503154] NET: Registered protocol family 1
[ 0.503194] pci 0000:00:02.0: Boot video device
[ 0.503426] Unpacking initramfs...
[ 0.923912] Freeing initrd memory: 8959k freed
[ 0.931357] audit: initializing netlink socket (disabled)
[ 0.931380] type=2000 audit(1375707646.927:1): initialized
[ 0.937200] highmem bounce pool size: 64 pages
[ 0.937211] HugeTLB registered 4 MB page size, pre-allocated 0 pages
[ 0.940188] VFS: Disk quotas dquot_6.5.2
[ 0.940308] Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[ 0.940465] msgmni has been set to 1723
[ 0.940984] alg: No test for stdrng (krng)
[ 0.941012] io scheduler noop registered
[ 0.941018] io scheduler anticipatory registered
[ 0.941023] io scheduler deadline registered
[ 0.941110] io scheduler cfq registered (default)
[ 0.941348] pcieport 0000:00:1c.0: irq 24 for MSI/MSI-X
[ 0.941361] pcieport 0000:00:1c.0: setting latency timer to 64
[ 0.941543] pcieport 0000:00:1c.1: irq 25 for MSI/MSI-X
[ 0.941555] pcieport 0000:00:1c.1: setting latency timer to 64
[ 0.941726] pcieport 0000:00:1c.2: irq 26 for MSI/MSI-X
[ 0.941738] pcieport 0000:00:1c.2: setting latency timer to 64
[ 0.941914] pcieport 0000:00:1c.3: irq 27 for MSI/MSI-X
[ 0.941926] pcieport 0000:00:1c.3: setting latency timer to 64
[ 0.942276] efifb: probing for efifb
[ 0.942421] efifb: framebuffer at 0xd0000000, mapped to 0xf7c80000,
using 3072k, total 3072k
[ 0.942428] efifb: mode is 1024x768x32, linelength=4096, pages=1
[ 0.942432] efifb: scrolling: redraw
[ 0.942439] efifb: Truecolor: size=8:8:8:8, shift=24:16:8:0
[ 0.981733] Console: switching to colour frame buffer device 128x48
[ 1.020692] fb0: EFI VGA frame buffer device
[ 1.020801] isapnp: Scanning for PnP cards...
[ 1.375082] isapnp: No Plug & Play device found
[ 1.378010] Linux agpgart interface v0.103
[ 1.378171] agpgart-intel 0000:00:00.0: Intel IGD Chipset
[ 1.378420] agpgart-intel 0000:00:00.0: detected 8188K stolen memory
[ 1.391369] agpgart-intel 0000:00:00.0: AGP aperture is 256M @ 0xd0000000
[ 1.391522] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
[ 1.392144] serial 0000:01:0e.0: PCI INT A -> GSI 18 (level, low) -> IRQ
18
[ 1.392154] serial 0000:01:0e.0: PCI INT A disabled
[ 1.392185] serial 0000:01:0e.1: PCI INT A -> GSI 18 (level, low) -> IRQ
18
[ 1.392193] serial 0000:01:0e.1: PCI INT A disabled
[ 1.392385] PNP: No PS/2 controller found. Probing ports directly.
[ 1.394719] serio: i8042 KBD port at 0x60,0x64 irq 1
[ 1.394734] serio: i8042 AUX port at 0x60,0x64 irq 12
[ 1.394884] mice: PS/2 mouse device common for all mice
[ 1.394967] rtc_cmos 00:03: RTC can wake from S4
[ 1.395045] rtc_cmos 00:03: rtc core: registered rtc_cmos as rtc0
[ 1.395080] rtc0: alarms up to one month, y3k, 114 bytes nvram, hpet irqs
[ 1.395106] cpuidle: using governor ladder
[ 1.395111] cpuidle: using governor menu
[ 1.395121] No iBFT detected.
[ 1.395906] TCP cubic registered
[ 1.396221] NET: Registered protocol family 10
[ 1.397213] lo: Disabled Privacy Extensions
[ 1.397908] Mobile IPv6
[ 1.397915] NET: Registered protocol family 17
[ 1.397946] Using IPI No-Shortcut mode
[ 1.398111] PM: Resume from disk failed.
[ 1.398133] registered taskstats version 1
[ 1.398868] rtc_cmos 00:03: setting system clock to 2013-08-05 13:00:47
UTC (1375707647)
[ 1.398947] Initalizing network drop monitor service
[ 1.399000] Freeing unused kernel memory: 364k freed
[ 1.399253] Write protecting the kernel text: 2472k
[ 1.399287] Write protecting the kernel read-only data: 876k
[ 1.521316] udev[71]: starting version 164
[ 1.676309] usbcore: registered new interface driver usbfs
[ 1.676370] usbcore: registered new interface driver hub
[ 1.676466] usbcore: registered new device driver usb
[ 1.688072] e1000e: Intel(R) PRO/1000 Network Driver - 1.0.2-k2
[ 1.688081] e1000e: Copyright (c) 1999-2008 Intel Corporation.
[ 1.688189] e1000e 0000:06:00.0: PCI INT A -> GSI 18 (level, low) -> IRQ
18
[ 1.688238] e1000e 0000:06:00.0: setting latency timer to 64
[ 1.688439] 0000:06:00.0: 0000:06:00.0: Failed to initialize MSI-X
interrupts. Falling back to MSI interrupts.
[ 1.689295] e1000e 0000:06:00.0: irq 28 for MSI/MSI-X
[ 1.696057] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[ 1.696123] ehci_hcd 0000:00:1d.7: PCI INT A -> GSI 23 (level, low) ->
IRQ 23
[ 1.696172] ehci_hcd 0000:00:1d.7: setting latency timer to 64
[ 1.696182] ehci_hcd 0000:00:1d.7: EHCI Host Controller
[ 1.696239] ehci_hcd 0000:00:1d.7: new USB bus registered, assigned bus
number 1
[ 1.696292] ehci_hcd 0000:00:1d.7: debug port 1
[ 1.700194] ehci_hcd 0000:00:1d.7: cache line size of 32 is not supported
[ 1.700286] ehci_hcd 0000:00:1d.7: irq 23, io mem 0xfe5ff800
[ 1.716033] ehci_hcd 0000:00:1d.7: USB 2.0 started, EHCI 1.00
[ 1.716098] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[ 1.716108] usb usb1: New USB device strings: Mfr=3, Product=2,
SerialNumber=1
[ 1.716116] usb usb1: Product: EHCI Host Controller
[ 1.716124] usb usb1: Manufacturer: Linux 2.6.32.11 ehci_hcd
[ 1.716131] usb usb1: SerialNumber: 0000:00:1d.7
[ 1.716361] usb usb1: configuration #1 chosen from 1 choice
[ 1.716460] hub 1-0:1.0: USB hub found
[ 1.716483] hub 1-0:1.0: 8 ports detected
[ 1.721368] Uniform Multi-Platform E-IDE driver
[ 1.724225] piix 0000:00:1f.1: IDE controller (0x8086:0x2850 rev 0x04)
[ 1.724258] PIIX_IDE 0000:00:1f.1: PCI INT A -> GSI 19 (level, low) ->
IRQ 19
[ 1.724279] piix 0000:00:1f.1: IDE port disabled
[ 1.724298] piix 0000:00:1f.1: not 100% native mode: will probe irqs
later
[ 1.724310] ide0: BM-DMA at 0xffa0-0xffa7
[ 1.724323] Probing IDE interface ide0...
[ 1.728430] uhci_hcd: USB Universal Host Controller Interface driver
[ 1.770278] SCSI subsystem initialized
[ 1.780693] firewire_ohci 0000:05:00.0: PCI INT A -> GSI 17 (level, low)
-> IRQ 17
[ 1.810935] 0000:06:00.0: eth0: (PCI Express:2.5GB/s:Width x1)
00:d0:c9:e1:66:b6
[ 1.810946] 0000:06:00.0: eth0: Intel(R) PRO/1000 Network Connection
[ 1.811040] 0000:06:00.0: eth0: MAC: 3, PHY: 8, PBA No: ffffff-0ff
[ 1.811134] e1000e 0000:07:00.0: PCI INT A -> GSI 19 (level, low) -> IRQ
19
[ 1.811183] e1000e 0000:07:00.0: setting latency timer to 64
[ 1.811394] 0000:07:00.0: 0000:07:00.0: Failed to initialize MSI-X
interrupts. Falling back to MSI interrupts.
[ 1.812239] e1000e 0000:07:00.0: irq 29 for MSI/MSI-X
[ 1.827331] libata version 3.00 loaded.
[ 1.856021] firewire_ohci: Added fw-ohci device 0000:05:00.0, OHCI
version 1.10
[ 1.938914] 0000:07:00.0: eth1: (PCI Express:2.5GB/s:Width x1)
00:d0:c9:e1:66:b7
[ 1.938922] 0000:07:00.0: eth1: Intel(R) PRO/1000 Network Connection
[ 1.939011] 0000:07:00.0: eth1: MAC: 3, PHY: 8, PBA No: ffffff-0ff
[ 2.084030] usb 1-3: new high speed USB device using ehci_hcd and
address 3
[ 2.223812] usb 1-3: New USB device found, idVendor=058f, idProduct=6387
[ 2.223820] usb 1-3: New USB device strings: Mfr=1, Product=2,
SerialNumber=3
[ 2.223827] usb 1-3: Product: Mass Storage
[ 2.223832] usb 1-3: Manufacturer: Generic
[ 2.223836] usb 1-3: SerialNumber: 792C94C8
[ 2.224008] usb 1-3: configuration #1 chosen from 1 choice
[ 2.241645] Initializing USB Mass Storage driver...
[ 2.241882] scsi0 : SCSI emulation for USB Mass Storage devices
[ 2.242158] usbcore: registered new interface driver usb-storage
[ 2.242166] USB Mass Storage support registered.
[ 2.242309] usb-storage: device found at 3
[ 2.242315] usb-storage: waiting for device to settle before scanning
[ 2.292029] hdb: TS16GCF133, CFA DISK drive
[ 2.292116] hdb: host max PIO4 wanted PIO255(auto-tune) selected PIO4
[ 2.292266] hdb: UDMA/66 mode selected
[ 2.292434] ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
[ 2.292610] uhci_hcd 0000:00:1d.0: PCI INT A -> GSI 23 (level, low) ->
IRQ 23
[ 2.292634] uhci_hcd 0000:00:1d.0: setting latency timer to 64
[ 2.292644] uhci_hcd 0000:00:1d.0: UHCI Host Controller
[ 2.292682] uhci_hcd 0000:00:1d.0: new USB bus registered, assigned bus
number 2
[ 2.292732] uhci_hcd 0000:00:1d.0: irq 23, io base 0x00008c00
[ 2.292845] usb usb2: New USB device found, idVendor=1d6b, idProduct=0001
[ 2.292855] usb usb2: New USB device strings: Mfr=3, Product=2,
SerialNumber=1
[ 2.292864] usb usb2: Product: UHCI Host Controller
[ 2.292871] usb usb2: Manufacturer: Linux 2.6.32.11 uhci_hcd
[ 2.292878] usb usb2: SerialNumber: 0000:00:1d.0
[ 2.293093] usb usb2: configuration #1 chosen from 1 choice
[ 2.293171] hub 2-0:1.0: USB hub found
[ 2.293189] hub 2-0:1.0: 2 ports detected
[ 2.293344] uhci_hcd 0000:00:1d.1: PCI INT B -> GSI 19 (level, low) ->
IRQ 19
[ 2.293362] uhci_hcd 0000:00:1d.1: setting latency timer to 64
[ 2.293371] uhci_hcd 0000:00:1d.1: UHCI Host Controller
[ 2.293399] uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus
number 3
[ 2.293464] uhci_hcd 0000:00:1d.1: irq 19, io base 0x00008880
[ 2.293575] usb usb3: New USB device found, idVendor=1d6b, idProduct=0001
[ 2.293582] usb usb3: New USB device strings: Mfr=3, Product=2,
SerialNumber=1
[ 2.293587] usb usb3: Product: UHCI Host Controller
[ 2.293593] usb usb3: Manufacturer: Linux 2.6.32.11 uhci_hcd
[ 2.293598] usb usb3: SerialNumber: 0000:00:1d.1
[ 2.293758] usb usb3: configuration #1 chosen from 1 choice
[ 2.293825] hub 3-0:1.0: USB hub found
[ 2.293841] hub 3-0:1.0: 2 ports detected
[ 2.293938] ata_piix 0000:00:1f.2: version 2.13
[ 2.293961] ata_piix 0000:00:1f.2: PCI INT B -> GSI 18 (level, low) ->
IRQ 18
[ 2.293970] ata_piix 0000:00:1f.2: MAP [ P0 P2 P1 P3 ]
[ 2.352167] firewire_core: created device fw0: GUID 00d0c901a0000d70,
S800
[ 2.449550] ata_piix 0000:00:1f.2: setting latency timer to 64
[ 2.449675] scsi1 : ata_piix
[ 2.449842] scsi2 : ata_piix
[ 2.452780] ata1: SATA max UDMA/133 cmd 0x9c00 ctl 0x9880 bmdma 0x9400
irq 18
[ 2.452791] ata2: SATA max UDMA/133 cmd 0x9800 ctl 0x9480 bmdma 0x9408
irq 18
[ 2.452896] uhci_hcd 0000:00:1d.2: PCI INT C -> GSI 18 (level, low) ->
IRQ 18
[ 2.452912] uhci_hcd 0000:00:1d.2: setting latency timer to 64
[ 2.452922] uhci_hcd 0000:00:1d.2: UHCI Host Controller
[ 2.452963] uhci_hcd 0000:00:1d.2: new USB bus registered, assigned bus
number 4
[ 2.453011] uhci_hcd 0000:00:1d.2: irq 18, io base 0x00008800
[ 2.453106] usb usb4: New USB device found, idVendor=1d6b, idProduct=0001
[ 2.453113] usb usb4: New USB device strings: Mfr=3, Product=2,
SerialNumber=1
[ 2.453119] usb usb4: Product: UHCI Host Controller
[ 2.453124] usb usb4: Manufacturer: Linux 2.6.32.11 uhci_hcd
[ 2.453129] usb usb4: SerialNumber: 0000:00:1d.2
[ 2.453310] usb usb4: configuration #1 chosen from 1 choice
[ 2.453402] hub 4-0:1.0: USB hub found
[ 2.453426] hub 4-0:1.0: 2 ports detected
[ 2.453602] uhci_hcd 0000:00:1d.3: PCI INT D -> GSI 16 (level, low) ->
IRQ 16
[ 2.453617] uhci_hcd 0000:00:1d.3: setting latency timer to 64
[ 2.453624] uhci_hcd 0000:00:1d.3: UHCI Host Controller
[ 2.453646] uhci_hcd 0000:00:1d.3: new USB bus registered, assigned bus
number 5
[ 2.453697] uhci_hcd 0000:00:1d.3: irq 16, io base 0x00008480
[ 2.453780] usb usb5: New USB device found, idVendor=1d6b, idProduct=0001
[ 2.453787] usb usb5: New USB device strings: Mfr=3, Product=2,
SerialNumber=1
[ 2.453793] usb usb5: Product: UHCI Host Controller
[ 2.453798] usb usb5: Manufacturer: Linux 2.6.32.11 uhci_hcd
[ 2.453806] usb usb5: SerialNumber: 0000:00:1d.3
[ 2.454012] usb usb5: configuration #1 chosen from 1 choice
[ 2.454084] hub 5-0:1.0: USB hub found
[ 2.454101] hub 5-0:1.0: 2 ports detected
[ 2.604028] usb 2-2: new low speed USB device using uhci_hcd and address
2
[ 2.781895] usb 2-2: New USB device found, idVendor=046d, idProduct=c31c
[ 2.781904] usb 2-2: New USB device strings: Mfr=1, Product=2,
SerialNumber=0
[ 2.781910] usb 2-2: Product: USB Keyboard
[ 2.781915] usb 2-2: Manufacturer: Logitech
[ 2.782093] usb 2-2: configuration #1 chosen from 1 choice
[ 2.832254] usbcore: registered new interface driver hiddev
[ 2.847449] input: Logitech USB Keyboard as
/devices/pci0000:00/0000:00:1d.0/usb2/2-2/2-2:1.0/input/input0
[ 2.847565] generic-usb 0003:046D:C31C.0001: input,hidraw0: USB HID
v1.10 Keyboard [Logitech USB Keyboard] on usb-0000:00:1d.0-2/input0
[ 2.888137] input: Logitech USB Keyboard as
/devices/pci0000:00/0000:00:1d.0/usb2/2-2/2-2:1.1/input/input1
[ 2.888228] generic-usb 0003:046D:C31C.0002: input,hidraw1: USB HID
v1.10 Device [Logitech USB Keyboard] on usb-0000:00:1d.0-2/input1
[ 2.888280] usbcore: registered new interface driver usbhid
[ 2.888287] usbhid: v2.6:USB HID core driver
[ 3.102672] ata1.00: SATA link down (SStatus 0 SControl 310)
[ 3.102690] ata1.01: SATA link down (SStatus 0 SControl 310)
[ 3.800026] ata2.01: failed to resume link (SControl 0)
[ 3.811050] ata2.00: SATA link down (SStatus 0 SControl 310)
[ 3.811067] ata2.01: SATA link down (SStatus 0 SControl 0)
[ 3.826581] ide-gd driver 1.18
[ 3.826658] hdb: max request size: 128KiB
[ 3.826667] hdb: 31293360 sectors (16022 MB) w/1KiB Cache,
CHS=31045/16/63
[ 3.826791] hdb: hdb1 hdb2 < hdb5 >
[ 3.949285] PM: Starting manual resume from disk
[ 3.949293] PM: Resume from partition 3:69
[ 3.949298] PM: Checking hibernation image.
[ 3.949712] PM: Error -22 checking image file
[ 3.949718] PM: Resume from disk failed.
[ 3.986226] kjournald starting. Commit interval 5 seconds
[ 3.986253] EXT3-fs: mounted filesystem with ordered data mode.
[ 4.332700] udev[367]: starting version 164
[ 4.501793] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
[ 4.549620] input: Power Button as
/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input2
[ 4.549640] ACPI: Power Button [PWRB]
[ 4.549923] input: Power Button as
/devices/LNXSYSTM:00/LNXPWRBN:00/input/input3
[ 4.549938] ACPI: Power Button [PWRF]
[ 4.553475] input: PC Speaker as /devices/platform/pcspkr/input/input4
[ 4.591321] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
[ 4.624790] i801_smbus 0000:00:1f.3: PCI INT C -> GSI 17 (level, low) ->
IRQ 17
[ 4.635974] Error: Driver 'pcspkr' is already registered, aborting...
[ 4.674615] HDA Intel 0000:00:1b.0: PCI INT A -> GSI 21 (level, low) ->
IRQ 21
[ 4.674698] HDA Intel 0000:00:1b.0: setting latency timer to 64
[ 7.240236] usb-storage: device scan complete
[ 7.242071] scsi 0:0:0:0: Direct-Access Generic Flash Disk
8.07 PQ: 0 ANSI: 2
[ 7.259428] sd 0:0:0:0: [sda] 15974400 512-byte logical blocks: (8.17
GB/7.61 GiB)
[ 7.259917] sd 0:0:0:0: [sda] Write Protect is off
[ 7.259926] sd 0:0:0:0: [sda] Mode Sense: 03 00 00 00
[ 7.259931] sd 0:0:0:0: [sda] Assuming drive cache: write through
[ 7.262543] sd 0:0:0:0: [sda] Assuming drive cache: write through
[ 7.263003] sda: sda1
[ 7.266547] sd 0:0:0:0: [sda] Assuming drive cache: write through
[ 7.267013] sd 0:0:0:0: [sda] Attached SCSI removable disk
[ 7.913252] Adding 686072k swap on /dev/hdb5. Priority:-1 extents:1
across:686072k
[ 7.993381] EXT3 FS on hdb1, internal journal
[ 8.039005] device-mapper: uevent: version 1.0.3
[ 8.039217] device-mapper: ioctl: 4.15.0-ioctl (2009-04-01) initialised:
dm-...@re...
[ 8.119948] loop: module loaded
[ 8.810040] e1000e 0000:06:00.0: irq 28 for MSI/MSI-X
[ 8.868144] e1000e 0000:06:00.0: irq 28 for MSI/MSI-X
[ 8.868903] ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 10.444957] e1000e: eth0 NIC Link is Up 100 Mbps Half Duplex, Flow
Control: None
[ 10.445026] 0000:06:00.0: eth0: 10/100 speed: disabling TSO
[ 10.445408] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ 20.944017] eth0: no IPv6 routers present
[ 434.015318] I-pipe: Domain RTAI registered.
[ 434.015335] RTAI[hal]: <3.9.1> mounted over IPIPE-NOTHREADS 2.6-03.
[ 434.015342] RTAI[hal]: compiled with gcc version 4.4.5 (Debian 4.4.5-8) .
[ 434.015461] RTAI[hal]: mounted (IPIPE-NOTHREADS, IMMEDIATE (INTERNAL
IRQs VECTORED), ISOL_CPUS_MASK: 0).
[ 434.015468] PIPELINE layers:
[ 434.015475] f87eaa60 9ac15d93 RTAI 2147483647
[ 434.015482] c14983a0 0 Linux 100
[ 434.055625] RTAI[malloc]: global heap size = 2097152 bytes, <BSD>.
[ 434.056113] RTAI[sched]: IMMEDIATE, MP, USER/KERNEL SPACE: <without RTAI
OWN KTASKs>, <uses LINUX SYSCALLs>, kstacks pool size = 524288 bytes.
[ 434.056132] RTAI[sched]: hard timer type/freq = APIC/10389960(Hz);
default timing: periodic; linear timed lists.
[ 434.056143] RTAI[sched]: Linux timer freq = 250 (Hz), TimeBase freq =
1662263000 hz.
[ 434.056150] RTAI[sched]: timer setup = 999 ns, resched latency = 2943 ns.
[ 434.094643] RTDM started.
[ 434.139313] e1000e 0000:07:00.0: PCI INT A disabled
[ 434.526271] e1000e 0000:06:00.0: PCI INT A disabled
[ 473.259754]
[ 473.259758] *** RTnet 0.9.13 - built on Jul 22 2013 10:07:31 ***
[ 473.259762]
[ 473.259768] RTnet: initialising real-time networking
[ 473.285472] rt_e1000e: Intel(R) PRO/1000 Network Driver - 1.5.1-k-rt
[ 473.285480] rt_e1000e: Copyright(c) 1999 - 2011 Intel Corporation.
[ 473.285546] rt_e1000e 0000:06:00.0: Disabling ASPM L0s
[ 473.285614] rt_e1000e 0000:06:00.0: PCI INT A -> GSI 18 (level, low) ->
IRQ 18
[ 473.285671] rt_e1000e 0000:06:00.0: setting latency timer to 64
[ 473.285846] Interrupt Mode set to 0
[ 473.399038] RTnet: registered rteth0
[ 473.399045] rt_e1000e: (PCI Express:2.5GT/s:Width x1) 00:d0:c9:e1:66:b6
[ 473.399050] rt_e1000e: Intel(R) PRO/1000 Network Connection
[ 473.399138] rt_e1000e: MAC: 3, PHY: 8, PBA No: FFFFFF-0FF
[ 473.399167] rt_e1000e 0000:07:00.0: Disabling ASPM L0s
[ 473.399223] rt_e1000e 0000:07:00.0: PCI INT A -> GSI 19 (level, low) ->
IRQ 19
[ 473.399265] rt_e1000e 0000:07:00.0: setting latency timer to 64
[ 473.399472] rt_e1000e: Failed to initialize MSI-X interrupts. Falling
back to MSI interrupts.
[ 473.416071] rt_e1000e 0000:07:00.0: irq 28 for MSI/MSI-X
[ 473.536774] RTnet: registered rteth1
[ 473.536781] rt_e1000e: (PCI Express:2.5GT/s:Width x1) 00:d0:c9:e1:66:b7
[ 473.536786] rt_e1000e: Intel(R) PRO/1000 Network Connection
[ 473.536873] rt_e1000e: MAC: 3, PHY: 8, PBA No: FFFFFF-0FF
[ 473.553070] initializing loopback...
[ 473.553105] RTnet: registered rtlo
[ 473.565835] RTcfg: init real-time configuration distribution protocol
[ 473.577958] RTmac: init realtime media access control
[ 473.587442] RTmac/TDMA: init time division multiple access control
mechanism
[ 475.281051] e1000e: rteth0 NIC Link is Up 100 Mbps Half Duplex, Flow
Control: None
[ 475.281117] rt_e1000e: 10/100 speed: disabling TSO
On Mon, Aug 5, 2013 at 12:46 PM, Jan Kiszka <jan...@si...> wrote:
> On 2013-08-05 12:36, Sebastian Hölzer wrote:
> > On Mon, Aug 5, 2013 at 10:27 AM, Jan Kiszka <jan...@si...>
> wrote:
> >
> >> On 2013-08-05 10:08, Sebastian Hölzer wrote:
> >>> Hi
> >>>
> >>> I'm trying to configure a Realtime Master-Slave Network.
> >>> I am using linux 2.6.32.11, rtai 3.9.1, rtnet 0.9.13 on two similar
> >>> machines.
> >>>
> >>> If I type in "rtnet start" i get the following output
> >>> "rt_e1000e: Failed to initialize MSI-X interrupts. Falling back to MSI
> >>> interrupts."
> >>> on both the Master and the Slave.
> >>>
> >>> If i try to Ping the Slave i get the folling output
> >>> "ioctl: No route to host"
> >>> I can however ping the localhost without a problem.
> >>>
> >>> If i try to ping the master or the localhost from the slave the machine
> >>> prints
> >>> "ioctl: No buffer space available"
> >>>
> >>> If i type dmesg on the master it says
> >>> "TDMA: Failed to transmit sync frame!" multiple times while the output
> on
> >>> the slave seems to be ok.
> >>>
> >>> Please provide suggestions on how i can further narrow down the
> Problem.
> >>
> >> You are likely facing interrupt problems. The NIC is not getting any IRQ
> >> through, thus will quickly run out of TX buffers.
> >>
> >> Does the e1000e driver of Linux fall back to MSI as well? What does RTAI
> >> report about registered RT IRQs, is the NIC listed? You may try to force
> >> the NIC to use legacy INTx (module parameter IntMode=0), but that may
> >> also create IRQ conflicts with Linux devices.
> >>
> >> Jan
> >>
> >
> > Thanks for your help!
> > Yes the e1000e driver also falls back to MSI and the NIC is listed.
> > I'm not sure what RTAI reports about registered RT IRQs.
> > Can you give me a hint on how to find out about the registered RT IRQs?
> > Is there a command to list all registered RT IRQs? or is this also listed
> > in dmesg?
>
> IIRC (used RTAI for the last time some 8 years ago), there were some
> entries in /proc/rtai.
>
> >
> > How do I try to force the NIC to use legacy Interrupts?
> > I guess i have to load the driver modules like this. modprobe rt_e1000e
> > IntMode=0
> > Is this right?
>
> Yes.
>
> >
> > Is this the right way to configure rtnet.conf if want to use the RTnet
> > script?
> > # RT-NIC driver
> > RT_DRIVER="rt_e1000e"
> > RT_DRIVER_OPTIONS="IntMode=0"
>
> This should work as well.
>
> Jan
>
> --
> Siemens AG, Corporate Technology, CT RTC ITP SES-DE
> Corporate Competence Center Embedded Linux
>
|
|
From: Jan K. <jan...@si...> - 2013-08-05 10:46:44
|
On 2013-08-05 12:36, Sebastian Hölzer wrote: > On Mon, Aug 5, 2013 at 10:27 AM, Jan Kiszka <jan...@si...> wrote: > >> On 2013-08-05 10:08, Sebastian Hölzer wrote: >>> Hi >>> >>> I'm trying to configure a Realtime Master-Slave Network. >>> I am using linux 2.6.32.11, rtai 3.9.1, rtnet 0.9.13 on two similar >>> machines. >>> >>> If I type in "rtnet start" i get the following output >>> "rt_e1000e: Failed to initialize MSI-X interrupts. Falling back to MSI >>> interrupts." >>> on both the Master and the Slave. >>> >>> If i try to Ping the Slave i get the folling output >>> "ioctl: No route to host" >>> I can however ping the localhost without a problem. >>> >>> If i try to ping the master or the localhost from the slave the machine >>> prints >>> "ioctl: No buffer space available" >>> >>> If i type dmesg on the master it says >>> "TDMA: Failed to transmit sync frame!" multiple times while the output on >>> the slave seems to be ok. >>> >>> Please provide suggestions on how i can further narrow down the Problem. >> >> You are likely facing interrupt problems. The NIC is not getting any IRQ >> through, thus will quickly run out of TX buffers. >> >> Does the e1000e driver of Linux fall back to MSI as well? What does RTAI >> report about registered RT IRQs, is the NIC listed? You may try to force >> the NIC to use legacy INTx (module parameter IntMode=0), but that may >> also create IRQ conflicts with Linux devices. >> >> Jan >> > > Thanks for your help! > Yes the e1000e driver also falls back to MSI and the NIC is listed. > I'm not sure what RTAI reports about registered RT IRQs. > Can you give me a hint on how to find out about the registered RT IRQs? > Is there a command to list all registered RT IRQs? or is this also listed > in dmesg? IIRC (used RTAI for the last time some 8 years ago), there were some entries in /proc/rtai. > > How do I try to force the NIC to use legacy Interrupts? > I guess i have to load the driver modules like this. modprobe rt_e1000e > IntMode=0 > Is this right? Yes. > > Is this the right way to configure rtnet.conf if want to use the RTnet > script? > # RT-NIC driver > RT_DRIVER="rt_e1000e" > RT_DRIVER_OPTIONS="IntMode=0" This should work as well. Jan -- Siemens AG, Corporate Technology, CT RTC ITP SES-DE Corporate Competence Center Embedded Linux |
|
From: Sebastian H. <seb...@gm...> - 2013-08-05 10:37:04
|
On Mon, Aug 5, 2013 at 10:27 AM, Jan Kiszka <jan...@si...> wrote: > On 2013-08-05 10:08, Sebastian Hölzer wrote: > > Hi > > > > I'm trying to configure a Realtime Master-Slave Network. > > I am using linux 2.6.32.11, rtai 3.9.1, rtnet 0.9.13 on two similar > > machines. > > > > If I type in "rtnet start" i get the following output > > "rt_e1000e: Failed to initialize MSI-X interrupts. Falling back to MSI > > interrupts." > > on both the Master and the Slave. > > > > If i try to Ping the Slave i get the folling output > > "ioctl: No route to host" > > I can however ping the localhost without a problem. > > > > If i try to ping the master or the localhost from the slave the machine > > prints > > "ioctl: No buffer space available" > > > > If i type dmesg on the master it says > > "TDMA: Failed to transmit sync frame!" multiple times while the output on > > the slave seems to be ok. > > > > Please provide suggestions on how i can further narrow down the Problem. > > You are likely facing interrupt problems. The NIC is not getting any IRQ > through, thus will quickly run out of TX buffers. > > Does the e1000e driver of Linux fall back to MSI as well? What does RTAI > report about registered RT IRQs, is the NIC listed? You may try to force > the NIC to use legacy INTx (module parameter IntMode=0), but that may > also create IRQ conflicts with Linux devices. > > Jan > Thanks for your help! Yes the e1000e driver also falls back to MSI and the NIC is listed. I'm not sure what RTAI reports about registered RT IRQs. Can you give me a hint on how to find out about the registered RT IRQs? Is there a command to list all registered RT IRQs? or is this also listed in dmesg? How do I try to force the NIC to use legacy Interrupts? I guess i have to load the driver modules like this. modprobe rt_e1000e IntMode=0 Is this right? Is this the right way to configure rtnet.conf if want to use the RTnet script? # RT-NIC driver RT_DRIVER="rt_e1000e" RT_DRIVER_OPTIONS="IntMode=0" |
|
From: Jan K. <jan...@si...> - 2013-08-05 08:28:08
|
On 2013-08-05 10:08, Sebastian Hölzer wrote: > Hi > > I'm trying to configure a Realtime Master-Slave Network. > I am using linux 2.6.32.11, rtai 3.9.1, rtnet 0.9.13 on two similar > machines. > > If I type in "rtnet start" i get the following output > "rt_e1000e: Failed to initialize MSI-X interrupts. Falling back to MSI > interrupts." > on both the Master and the Slave. > > If i try to Ping the Slave i get the folling output > "ioctl: No route to host" > I can however ping the localhost without a problem. > > If i try to ping the master or the localhost from the slave the machine > prints > "ioctl: No buffer space available" > > If i type dmesg on the master it says > "TDMA: Failed to transmit sync frame!" multiple times while the output on > the slave seems to be ok. > > Please provide suggestions on how i can further narrow down the Problem. You are likely facing interrupt problems. The NIC is not getting any IRQ through, thus will quickly run out of TX buffers. Does the e1000e driver of Linux fall back to MSI as well? What does RTAI report about registered RT IRQs, is the NIC listed? You may try to force the NIC to use legacy INTx (module parameter IntMode=0), but that may also create IRQ conflicts with Linux devices. Jan -- Siemens AG, Corporate Technology, CT RTC ITP SES-DE Corporate Competence Center Embedded Linux |
|
From: Sebastian H. <seb...@gm...> - 2013-08-05 08:08:21
|
Hi I'm trying to configure a Realtime Master-Slave Network. I am using linux 2.6.32.11, rtai 3.9.1, rtnet 0.9.13 on two similar machines. If I type in "rtnet start" i get the following output "rt_e1000e: Failed to initialize MSI-X interrupts. Falling back to MSI interrupts." on both the Master and the Slave. If i try to Ping the Slave i get the folling output "ioctl: No route to host" I can however ping the localhost without a problem. If i try to ping the master or the localhost from the slave the machine prints "ioctl: No buffer space available" If i type dmesg on the master it says "TDMA: Failed to transmit sync frame!" multiple times while the output on the slave seems to be ok. Please provide suggestions on how i can further narrow down the Problem. Thanks in advance! Sebastian Hölzer |
|
From: Vasudev K. <kam...@gm...> - 2013-06-27 10:48:45
|
Hello folks, We were using rtnet driver rt_8139too for communication and we recently observed following message in the dmesg log [1484843.526318] rteth0: Abnormal interrupt, status 00000002. [1484845.840420] rteth0: Transmit error, Tx status 4030403c. What is the meaning of these messages? Is this some thing serious or can be safely ignored? The version of rtnet which is used is 0.9.11 and below is the version string for rt_8139too [ 31.254442] rt_8139too Fast Ethernet driver 0.9.24-rt0.7 [ 31.254563] rt_8139too: pci dev 0000:06:07.0 (id 10ec:8139 rev 20) is an enhanced 8139C+ chip [ 31.254646] rt_8139too: Use the "8139cp" driver for improved performance and stability. Thank you in advance. Warm Regards -- Vasudev Kamath http://copyninja.info copyninja@{frndk.de|vasudev.homelinux.net} |
|
From: Leopold Palomo-A. <le...@al...> - 2013-06-19 12:43:49
|
A Dimecres, 19 de juny de 2013, Gilles Chanteperdrix va escriure: > > Leopold Palomo Avellaneda wrote: > > My problem is that neither of the three options fits my needs and to make > > a > > combination of two of them puts repeated options in the compiler. For > > example > > rtdm+native: > > > > -lnative -L/usr/lib -lxenomai -lpthread -lrt -lrtdm -L/usr/lib -lxenomai > > -lpthread -lrt > > So, what is the problem with this? Do you get a compiler warning? A > compilation error? well, obviously it's not a big problem, neither a problem. It's just that an option for rtnet will help a beginner user and don't waste time trying to understand why it doesn't link. And to have a long long lines with options to the linker could produce that you don't see some errors in some option because the overinformation. Leo -- -- Linux User 152692 Catalonia |
|
From: Gilles C. <gil...@xe...> - 2013-06-19 11:45:25
|
Leopold Palomo Avellaneda wrote:
> My problem is that neither of the three options fits my needs and to make
> a
> combination of two of them puts repeated options in the compiler. For
> example
> rtdm+native:
>
> -lnative -L/usr/lib -lxenomai -lpthread -lrt -lrtdm -L/usr/lib -lxenomai
> -lpthread -lrt
So, what is the problem with this? Do you get a compiler warning? A
compilation error?
--
Gilles.
|
|
From: Leopold P. A. <le...@al...> - 2013-06-18 21:33:32
|
A Dimarts, 18 de juny de 2013, Gilles Chanteperdrix va escriure: > Leopold Palomo Avellaneda wrote: > > Hi, > > > > first of all sorry for the cross-posting but I think that there's > > something > > wrong in the xeno-config options in both projects. If I run: > > > > $ xeno-config --skin=native --ldflags > > -lnative -L/usr/lib -lxenomai -lpthread -lrt > > > > $ xeno-config --skin=posix --ldflags > > -Wl,@/usr/lib/posix.wrappers -L/usr/lib -lpthread_rt -lxenomai -lpthread > > -lrt > > > > $ xeno-config --skin=rtdm --ldflags > > -lrtdm -L/usr/lib -lxenomai -lpthread -lrt > > > > > > So, in my application, that I _only_ use rtnet calls and also, the > > pthread calls (pthread_*, rt_* calls) > > > > none of the options described fits my needs. Or rtdm skin adds the native > > lib, > > or we create another --ldflags with rtdm, native. > > > > What do you think? > > Hi, > > I am not sure I understand your question. > > If you want to use the RTDM skin only, then use the flags given by > xeno-config --skin=rtdm > > If you want to use the RTDM skin with the native skin, then use the flags > given by both xeno-config --skin=rtdm and xeno-config --skin=native > > If you want to use the RTDM skin through the posix skin, then only use the > flags given by xeno-config --skin=posix > > If you want to use the 3 skins (RTDM, native, posix), then use the flags > given by all three calls to xeno-config. > My problem is that neither of the three options fits my needs and to make a combination of two of them puts repeated options in the compiler. For example rtdm+native: -lnative -L/usr/lib -lxenomai -lpthread -lrt -lrtdm -L/usr/lib -lxenomai -lpthread -lrt I miss a "skin" rtnet, because IMHO the common use of rtnet using that calls cannot be set by none of the options of xeno-config, and you need a combination of both (rtdm+native). I hope have been more clear now. Regards, Leo -- -- Linux User 152692 PGP: 0xF944807E Catalonia ------------------------------------- A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail? |
|
From: Gilles C. <gil...@xe...> - 2013-06-18 16:09:17
|
Leopold Palomo Avellaneda wrote:
> Hi,
>
> first of all sorry for the cross-posting but I think that there's
> something
> wrong in the xeno-config options in both projects. If I run:
>
> $ xeno-config --skin=native --ldflags
> -lnative -L/usr/lib -lxenomai -lpthread -lrt
>
> $ xeno-config --skin=posix --ldflags
> -Wl,@/usr/lib/posix.wrappers -L/usr/lib -lpthread_rt -lxenomai -lpthread
> -lrt
>
> $ xeno-config --skin=rtdm --ldflags
> -lrtdm -L/usr/lib -lxenomai -lpthread -lrt
>
>
> So, in my application, that I _only_ use rtnet calls and also, the pthread
> calls (pthread_*, rt_* calls)
>
> none of the options described fits my needs. Or rtdm skin adds the native
> lib,
> or we create another --ldflags with rtdm, native.
>
> What do you think?
Hi,
I am not sure I understand your question.
If you want to use the RTDM skin only, then use the flags given by
xeno-config --skin=rtdm
If you want to use the RTDM skin with the native skin, then use the flags
given by both xeno-config --skin=rtdm and xeno-config --skin=native
If you want to use the RTDM skin through the posix skin, then only use the
flags given by xeno-config --skin=posix
If you want to use the 3 skins (RTDM, native, posix), then use the flags
given by all three calls to xeno-config.
Regards.
--
Gilles.
|
|
From: Leopold P. A. <le...@al...> - 2013-06-15 15:40:41
|
Hi, first of all sorry for the cross-posting but I think that there's something wrong in the xeno-config options in both projects. If I run: $ xeno-config --skin=native --ldflags -lnative -L/usr/lib -lxenomai -lpthread -lrt $ xeno-config --skin=posix --ldflags -Wl,@/usr/lib/posix.wrappers -L/usr/lib -lpthread_rt -lxenomai -lpthread -lrt $ xeno-config --skin=rtdm --ldflags -lrtdm -L/usr/lib -lxenomai -lpthread -lrt So, in my application, that I _only_ use rtnet calls and also, the pthread calls (pthread_*, rt_* calls) none of the options described fits my needs. Or rtdm skin adds the native lib, or we create another --ldflags with rtdm, native. What do you think? Best regards, Leopold --------------------------- /usr/bin/gcc -fPIC -Wl,--no-undefined -lrt -lrtdm -L/usr/lib -lxenomai - lpthread -lrt -Wl,--no-undefined -lrt -shared -Wl,-soname,libsoemrt.so.1.3.0 -o libsoemrt.so.1.3.0 CMakeFiles/soem_dynamic_rt.dir/soem/ethercatbase.c.o CMakeFiles/soem_dynamic_rt.dir/soem/ethercatcoe.c.o CMakeFiles/soem_dynamic_rt.dir/soem/ethercatconfig.c.o CMakeFiles/soem_dynamic_rt.dir/soem/ethercatdc.c.o CMakeFiles/soem_dynamic_rt.dir/soem/ethercatfoe.c.o CMakeFiles/soem_dynamic_rt.dir/soem/ethercatmain.c.o CMakeFiles/soem_dynamic_rt.dir/soem/ethercatprint.c.o CMakeFiles/soem_dynamic_rt.dir/soem/ethercatsoe.c.o CMakeFiles/soem_dynamic_rt.dir/oshw/linux/nicdrv.c.o CMakeFiles/soem_dynamic_rt.dir/oshw/linux/oshw.c.o CMakeFiles/soem_dynamic_rt.dir/osal/linux/osal.c.o ..... CMakeFiles/soem_dynamic_rt.dir/oshw/linux/nicdrv.c.o: In function `ecx_setupnic': nicdrv.c:(.text+0x309): undefined reference to `rt_mutex_create' nicdrv.c:(.text+0x325): undefined reference to `rt_mutex_create' nicdrv.c:(.text+0x341): undefined reference to `rt_mutex_create' CMakeFiles/soem_dynamic_rt.dir/oshw/linux/nicdrv.c.o: In function `ecx_getindex': nicdrv.c:(.text+0x761): undefined reference to `rt_mutex_acquire' nicdrv.c:(.text+0x821): undefined reference to `rt_mutex_release' CMakeFiles/soem_dynamic_rt.dir/oshw/linux/nicdrv.c.o: In function `ecx_outframe_red': nicdrv.c:(.text+0x99c): undefined reference to `rt_mutex_acquire' nicdrv.c:(.text+0xa25): undefined reference to `rt_mutex_release' CMakeFiles/soem_dynamic_rt.dir/oshw/linux/nicdrv.c.o: In function `ecx_inframe': nicdrv.c:(.text+0xbad): undefined reference to `rt_mutex_acquire' nicdrv.c:(.text+0xd83): undefined reference to `rt_mutex_release' collect2: error: ld returned 1 exit status -- -- Linux User 152692 PGP: 0xF944807E Catalonia ------------------------------------- A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail? |
|
From: Mariusz J. <mar...@wp...> - 2013-06-14 08:01:04
|
Hi, > >>>>> > >>>>> 2. If some station stop responding (stop sending a heartbeats), is there a way to inform a application that some station is down? Or that the station is up? > >>>> > >>>> The information is exported via /proc on both client and server. Unless > >>>> I forget something, there is no event signaling mechanism to wait on > >>>> such an error via the rtcfg tool, e.g. But that would be implementable > >>>> if required. > >>> > >>> Do you have something special in mind. This information is present in the system, the only problem is to export it to application. If you don't mind I could try to take care of it, with a little help from your side. > >> > >> Well, there could be something like "rtcfg <dev> monitor > >> [event,event,...]" with one event being "node-failure". Then you will > >> need to define and implement a corresponding RTcfg-config IOCTL that > >> implements the actual blocking of the caller and its wakeup on the > >> specified events in the kernel. The return code of the IOCTL or some > >> additional data structure could provide information about the event that > >> caused a wakeup. Well, that's a first, rough description if such an > >> interface. What would be important is to match it against an actual use > >> case, i.e. some script or application that will actually call "rtcfg > >> monitor". Otherwise, we risk designing something that no one would use > >> in the end. What do you have in mind here? > > > > I though rather about application api (xenomai native, posix). So, in the first step, I should implement ioctl blocking service and something like event-info structure. Then I prepare example containing relevant use case. The "rtcfg <dev> monito [event,event,...]" is last on my TODO list. What do you think about it? > > Keep in mind that the whole RTcfg implementation in RTnet is > conceptually non-RT. Thus, providing interfaces to real-time skins that > differ from those IOCTLs that also the command line tool uses makes > little sense. > In this case, I agree that it does not make sense to implement a RT API. So I will follow a concept of the RTcfg implementation, and implement a event IOCTLs in accordance with other such system calls. Now, I am thinking about example, I see to options: - one rt app that create a two rt thread which one of them is blocked on non-rt IOCTL system call, - two application: a rt app doing something, a non-rt app monitoring events (sending info to a rt app through a pipe). What do you think? I assume, that rt applications are a control related applications that handle also communication issues. In this case we have to deliver a station down/up information to them somehow. Mariusz |
|
From: Jan K. <jan...@we...> - 2013-06-14 05:51:38
|
On 2013-06-13 23:08, Mariusz Janiak wrote: >>>>> >>>>> 2. If some station stop responding (stop sending a heartbeats), is there a way to inform a application that some station is down? Or that the station is up? >>>> >>>> The information is exported via /proc on both client and server. Unless >>>> I forget something, there is no event signaling mechanism to wait on >>>> such an error via the rtcfg tool, e.g. But that would be implementable >>>> if required. >>> >>> Do you have something special in mind. This information is present in the system, the only problem is to export it to application. If you don't mind I could try to take care of it, with a little help from your side. >> >> Well, there could be something like "rtcfg <dev> monitor >> [event,event,...]" with one event being "node-failure". Then you will >> need to define and implement a corresponding RTcfg-config IOCTL that >> implements the actual blocking of the caller and its wakeup on the >> specified events in the kernel. The return code of the IOCTL or some >> additional data structure could provide information about the event that >> caused a wakeup. Well, that's a first, rough description if such an >> interface. What would be important is to match it against an actual use >> case, i.e. some script or application that will actually call "rtcfg >> monitor". Otherwise, we risk designing something that no one would use >> in the end. What do you have in mind here? > > I though rather about application api (xenomai native, posix). So, in the first step, I should implement ioctl blocking service and something like event-info structure. Then I prepare example containing relevant use case. The "rtcfg <dev> monito [event,event,...]" is last on my TODO list. What do you think about it? Keep in mind that the whole RTcfg implementation in RTnet is conceptually non-RT. Thus, providing interfaces to real-time skins that differ from those IOCTLs that also the command line tool uses makes little sense. Jan |
37 messages has been excluded from this view by a project administrator.
