|
Klaus Pantleon(deleted)
|
Fsys.umass in .boot not working
|
|
Klaus Pantleon(deleted)
02/16/2016 4:52 AM
post115742
|
Fsys.umass in .boot not working
Hello QNX4 supporters,
I have here a railmounted PC working under QNX4 but still one problem.
The io-usb and Fsys.umass are working properly when I start them after the boot process.
Starte after boot process the Fsys.umass offers /dev/hd1 and I can mount and access the storage.
But when I start the io-usb and Fsys.umass inside .boot the hd will not be recognized.
The .boot itself is OK and is working when I use it on another PC to boot from USB.
What can I test furthermore?
|
|
|
|
|
|
Klaus Pantleon(deleted)
|
Re: Fsys.umass in .boot not working
|
|
Klaus Pantleon(deleted)
02/17/2016 2:17 AM
post115754
|
Re: Fsys.umass in .boot not working
I got further Information:
The Problem is not tight to the Bootimage but whether the tasks "io-usb" and "usb" are started remotely using "on -f" or
not.
If I use the "usb -v" locally I get sometimes following output:
#####
(root)//268/root>//138/bin/usb -v
USB 0 (EHCI) v1.10, v1.01 DDK, v1.01 HCD
Control, Interrupt, Bulk, Isoch, High speed
device 1 - descriptors - Input/output error
device 2 - descriptors - Input/output error
device 3 - descriptors - Input/output error
Device Address : 4
Upstream Host Controller : 0
Upstream Device Address : 1
Upstream Port : 4
Upstream Port Speed : Low
Vendor : 0x04f2
Product : 0x1113
Device Release : r0.01
Class : 0x00 (Independant per interface)
Max PacketSize0 : 8
Configurations : 1
Configuration : 1
Attributes : 0xa0 (Bus-powered, Remote-wakeup)
Max Power : 100 mA
(root)//268/root>
########
If I telnet into another machine (138) and start there the "usb -v" remotely I get following:
########
(root)//138/root>on -f 268 //138/bin/usb -v
USB 0 (EHCI) v1.10, v1.01 DDK, v1.01 HCD
Control, Interrupt, Bulk, Isoch, High speed
Device Address : 1
Upstream Host Controller : 0
Upstream Device Address : 0
Upstream Port : 0
Upstream Port Speed : High
Vendor : 0x8087
Product : 0x07e6
Device Release : r0.14
Class : 0x09 (Hub)
Subclass : 0x00
Protocol : 0x01
Max PacketSize0 : 64
Hub Number Ports : 4
Hub Characteristics : 0x0009 (Individual power, Individual over-current)
Hub Power On->Good : 0 ms
Hub Power Requirements : 0 mA
Configurations : 1
Configuration : 1
Attributes : 0xe0 (Self-powered, Remote-wakeup)
Max Power : 0 mA
device 2 - descriptors - Input/output error
device 3 - descriptors - Input/output error
device 4 - descriptors - Input/output error
(root)//138/root>
######
If I start the "io-usb" inside a pterm on another machine (138) the return of the comand is OK an I see all USB devices
listed in the output.
By the way. This is my first PC where the Net.e1000 is running on same IRQ like the USB.
BR, Klaus
|
|
|
|
|
|
Oleg Bolshakov
|
Re: Fsys.umass in .boot not working
|
|
Oleg Bolshakov
02/17/2016 9:50 AM
post115761
|
Re: Fsys.umass in .boot not working
Hi Klaus,
Can you post here your build file for USB boot image?
Respectfully,
Oleg
17 февр. 2016 г., в 10:17:32, Klaus Pantleon <community-noreply@qnx.com> написал:
> I got further Information:
> The Problem is not tight to the Bootimage but whether the tasks "io-usb" and "usb" are started remotely using "on -f"
or not.
> If I use the "usb -v" locally I get sometimes following output:
>
> #####
> (root)//268/root>//138/bin/usb -v
> USB 0 (EHCI) v1.10, v1.01 DDK, v1.01 HCD
> Control, Interrupt, Bulk, Isoch, High speed
>
> device 1 - descriptors - Input/output error
>
> device 2 - descriptors - Input/output error
>
> device 3 - descriptors - Input/output error
>
> Device Address : 4
> Upstream Host Controller : 0
> Upstream Device Address : 1
> Upstream Port : 4
> Upstream Port Speed : Low
> Vendor : 0x04f2
> Product : 0x1113
> Device Release : r0.01
> Class : 0x00 (Independant per interface)
> Max PacketSize0 : 8
> Configurations : 1
> Configuration : 1
> Attributes : 0xa0 (Bus-powered, Remote-wakeup)
> Max Power : 100 mA
>
> (root)//268/root>
> ########
>
> If I telnet into another machine (138) and start there the "usb -v" remotely I get following:
>
> ########
> (root)//138/root>on -f 268 //138/bin/usb -v
> USB 0 (EHCI) v1.10, v1.01 DDK, v1.01 HCD
> Control, Interrupt, Bulk, Isoch, High speed
>
> Device Address : 1
> Upstream Host Controller : 0
> Upstream Device Address : 0
> Upstream Port : 0
> Upstream Port Speed : High
> Vendor : 0x8087
> Product : 0x07e6
> Device Release : r0.14
> Class : 0x09 (Hub)
> Subclass : 0x00
> Protocol : 0x01
> Max PacketSize0 : 64
> Hub Number Ports : 4
> Hub Characteristics : 0x0009 (Individual power, Individual over-current)
> Hub Power On->Good : 0 ms
> Hub Power Requirements : 0 mA
> Configurations : 1
> Configuration : 1
> Attributes : 0xe0 (Self-powered, Remote-wakeup)
> Max Power : 0 mA
>
> device 2 - descriptors - Input/output error
>
> device 3 - descriptors - Input/output error
>
> device 4 - descriptors - Input/output error
>
> (root)//138/root>
> ######
>
> If I start the "io-usb" inside a pterm on another machine (138) the return of the comand is OK an I see all USB
devices listed in the output.
>
> By the way. This is my first PC where the Net.e1000 is running on same IRQ like the USB.
>
> BR, Klaus
>
>
>
>
>
>
>
>
>
>
>
> _______________________________________________
>
> General
> http://community.qnx.com/sf/go/post115754
> To cancel your subscription to this discussion, please e-mail general-qnx4-unsubscribe@community.qnx.com
|
|
|
|
|
|
Klaus Pantleon(deleted)
|
Re: Fsys.umass in .boot not working
|
|
Klaus Pantleon(deleted)
02/17/2016 9:57 AM
post115764
|
Re: Fsys.umass in .boot not working
Hi Oleg,
during my Research I found that the cause is not based in the .boot.
When I start Net.e1000 with nettrap it uses INT7.
When I start io-usb it uses also INT7.
When I enter "usb -v" without network traffic I get not the USB device list.
The Output will Show something of the previous post but not the correct listing-
When I enter "usb -v" and generate network traffic to the node in Background I get the USB device list.
Even the Fsys.umass recognizes the memory stick and I can access the filesystem of the stick.
Is it possible that the Interrupt handling in io-usb is confused?
|
|
|
|
|
|
Oleg Bolshakov
|
Re: Fsys.umass in .boot not working
|
|
Oleg Bolshakov
02/17/2016 10:34 AM
post115767
|
Re: Fsys.umass in .boot not working
Please post here sin ver output and build file.
Отправлено с моего смартфона BlackBerry 10.
Исходное сообщение
От: Klaus Pantleon
Отправлено: среда, 17 февраля 2016 г., 17:57
Кому: general-qnx4
Ответить: general-qnx4@community.qnx.com
Тема: Re: Fsys.umass in .boot not working
Hi Oleg,
during my Research I found that the cause is not based in the .boot.
When I start Net.e1000 with nettrap it uses INT7.
When I start io-usb it uses also INT7.
When I enter "usb -v" without network traffic I get not the USB device list.
The Output will Show something of the previous post but not the correct listing-
When I enter "usb -v" and generate network traffic to the node in Background I get the USB device list.
Even the Fsys.umass recognizes the memory stick and I can access the filesystem of the stick.
Is it possible that the Interrupt handling in io-usb is confused?
_______________________________________________
General
http://community.qnx.com/sf/go/post115764
To cancel your subscription to this discussion, please e-mail general-qnx4-unsubscribe@community.qnx.com
|
|
|
|
|
|
Klaus Pantleon(deleted)
|
Re: Fsys.umass in .boot not working
|
|
Klaus Pantleon(deleted)
02/17/2016 10:39 AM
post115768
|
Re: Fsys.umass in .boot not working
Hi Oleg,
the Problem is not in .build.
It`s in usage of USB on INT7 and not Interrupt will be generated from the USB stick
(root)//268/root>sin ver
PROGRAM NAME VERSION DATE
sys/Proc32 Proc 4.25R Feb 15 2012
sys/Proc32 Slib16 4.23G Oct 04 1996
sys/Slib32 Slib32 4.24B Aug 12 1997
/bin/Fsys Fsys32 4.24Z Jul 06 2009
/bin/Fsys.atapi atapi 4.25G Jul 06 2009
//268/hd0t77/bin/Pipe Pipe 4.23A Feb 26 1996
//268/hd0t77/bin/Dev32 Dev32 4.23G Oct 04 1996
//268/*/bin/Dev32.ansi Dev32.ansi 4.23H Nov 21 1996
//268/*/bin/Dev32.ser Dev.ser 4.25A Feb 14 2003
//268/*/bin/io-usb USB 2.00L Mar 01 2013
//268/hd0t77/bin/Net Net 4.25G Jul 06 2009
//268/*/bin/Net.e1000 Net.e1000 4.25D Dec 19 2013
(root)//268/root>sin irq
IRQ PID PROGRAM CS:IP DS
-1 20 //268/hd0t77/bin/Dev32 0005:005760 000D
-1 23 //268/*/bin/Dev32.ansi 0005:005DC0 000D
-1 25 //268/*/bin/Dev32.ser 0005:001450 000D
-1 57 //268/hd0t77/bin/Net 0015:0267B1 001D
0 1 sys/Proc32 00F0:004D83 00F8
0 57 //268/hd0t77/bin/Net 0015:02685E 001D
1 23 //268/*/bin/Dev32.ansi 0005:00690C 000D
3 25 //268/*/bin/Dev32.ser 0005:00162D 000D
4 25 //268/*/bin/Dev32.ser 0005:001634 000D
7 45 //268/*/bin/io-usb 0005:006DF5 000D
7 57 //268/hd0t77/bin/Net 0015:02659C 001D
13 1 sys/Proc32 00F0:004D47 00F8
15 5 /bin/Fsys.atapi 0005:00AEFD 000D
|
|
|
|
|
|
Oleg Bolshakov
|
Re: Fsys.umass in .boot not working
|
|
Oleg Bolshakov
02/18/2016 4:16 AM
post115786
|
Re: Fsys.umass in .boot not working
Hi Klaus,
It seems like BIOS sets incorrect IRQ number for USB controller. In that case io-usb can’t get interrupt. With working
Net.e1000 on the same IRQ io-usb gets interrupts from network controller.
Can you post here sin ar and show_pci -vvv outputs? Can you launch another OS in non-APIC mode? What IRQ is used for USB
? Does USB work?
Respectfully,
Oleg
17 февр. 2016 г., в 18:39:45, Klaus Pantleon <community-noreply@qnx.com> написал:
> Hi Oleg,
> the Problem is not in .build.
> It`s in usage of USB on INT7 and not Interrupt will be generated from the USB stick
>
>
> (root)//268/root>sin ver
> PROGRAM NAME VERSION DATE
> sys/Proc32 Proc 4.25R Feb 15 2012
> sys/Proc32 Slib16 4.23G Oct 04 1996
> sys/Slib32 Slib32 4.24B Aug 12 1997
> /bin/Fsys Fsys32 4.24Z Jul 06 2009
> /bin/Fsys.atapi atapi 4.25G Jul 06 2009
> //268/hd0t77/bin/Pipe Pipe 4.23A Feb 26 1996
> //268/hd0t77/bin/Dev32 Dev32 4.23G Oct 04 1996
> //268/*/bin/Dev32.ansi Dev32.ansi 4.23H Nov 21 1996
> //268/*/bin/Dev32.ser Dev.ser 4.25A Feb 14 2003
> //268/*/bin/io-usb USB 2.00L Mar 01 2013
> //268/hd0t77/bin/Net Net 4.25G Jul 06 2009
> //268/*/bin/Net.e1000 Net.e1000 4.25D Dec 19 2013
>
> (root)//268/root>sin irq
> IRQ PID PROGRAM CS:IP DS
> -1 20 //268/hd0t77/bin/Dev32 0005:005760 000D
> -1 23 //268/*/bin/Dev32.ansi 0005:005DC0 000D
> -1 25 //268/*/bin/Dev32.ser 0005:001450 000D
> -1 57 //268/hd0t77/bin/Net 0015:0267B1 001D
> 0 1 sys/Proc32 00F0:004D83 00F8
> 0 57 //268/hd0t77/bin/Net 0015:02685E 001D
> 1 23 //268/*/bin/Dev32.ansi 0005:00690C 000D
> 3 25 //268/*/bin/Dev32.ser 0005:00162D 000D
> 4 25 //268/*/bin/Dev32.ser 0005:001634 000D
> 7 45 //268/*/bin/io-usb 0005:006DF5 000D
> 7 57 //268/hd0t77/bin/Net 0015:02659C 001D
> 13 1 sys/Proc32 00F0:004D47 00F8
> 15 5 /bin/Fsys.atapi 0005:00AEFD 000D
>
>
>
>
>
> _______________________________________________
>
> General
> http://community.qnx.com/sf/go/post115768
> To cancel your subscription to this discussion, please e-mail general-qnx4-unsubscribe@community.qnx.com
|
|
|
|
|
|
Klaus Pantleon(deleted)
|
Re: Fsys.umass in .boot not working
|
|
Klaus Pantleon(deleted)
02/18/2016 8:15 AM
post115788
|
Re: Fsys.umass in .boot not working
Hi Oleg,
the non APIC OS test will take s while to prepare. But in the following you see the 'sin ar' and 'show_pci -vvv':
(root)//268/root>sin ar
PID USER NAME ARGUMENTS
1 System Proc32 -l 268 -p2000 -P26 -n320 -r8000
2 System Slib32
4 System Fsys -A
5 System Fsys.atapi
9 System Not available.
19 System Pipe
20 System Dev -n 100
23 System Dev.ansi -Q -n 4
25 System Dev.ser -b38400 -t14
32 System tinit -t /dev/ser1
33 System /bin/nameloc
34 System /bin/nameloc
36 root -sh
45 root io-usb
57 root Net -d4
308 root Net.e1000 -I0 -l1
28201 root sin ar
(root)//268/root>show_pci -vvv
PCI version = 3.00
Vendor ID = 8086h, INTEL CORPORATION
Device ID = f00h,
PCI index = 0h
Class Code = 060000h Bridge (Host/PCI) ProgIF=0
Revision ID = eh
Bus number = 0
Device number = 0
Function num = 0
Status Reg = 0h
Command Reg = 7h
Header type = 0h Single-function
BIST = 0h Build-in-self-test not supported
Latency Timer = 0h
Cache Line Size= 0h
Subsystem Vendor ID = 8086h
Subsystem ID = 7270h
Max Lat = 0ns
Min Gnt = 0ns
PCI Int Pin = 0, NC
Interrupt line = 0
Device Dependent Registers:
0x40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xA0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xB0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xC0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xD0: 00 00 00 00 01 00 00 00 00 00 00 00 00 00 00 00
0xE0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xF0: 66 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Vendor ID = 8086h, INTEL CORPORATION
Device ID = f31h,
PCI index = 0h
Class Code = 030000h Display (VGA) ProgIF=0
Revision ID = eh
Bus number = 0
Device number = 2
Function num = 0
Status Reg = 10h
Command Reg = 7h
Header type = 0h Single-function
BIST = 0h Build-in-self-test not supported
Latency Timer = 0h
Cache Line Size= 0h
Base Address = MEM@d0000000h,32bit length 4194304 MEM@c0000000h,Prefetchable,32bit length 268435456 IO@7050h length 8
bytes
Subsystem Vendor ID = 8086h
Subsystem ID = 7270h
Max Lat = 0ns
Min Gnt = 0ns
PCI Int Pin = 1, INT A
Interrupt line = 7
Capabilities Pointer = d0h
Capability ID = 1h
Capabilities = 22h - 0h
Capability ID = 5h
Capabilities = 0h - 0h
Capability ID = 9h
Capabilities = 107h - 0h
Device Dependent Registers:
0x40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x50: 11 02 00 00 00 00 00 00 00 00 00 00 01 00 00 bb
0x60: 00 00 02 00 00 00 00 00 00 00 00 00 00 00 00 00
0x70: 01 00 e0 ba 00 00 00 00 00 00 00 00 00 00 00 00
0x80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x90: 05 b0 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xA0: 00 00 00 00 13 00 06 03 00 00 00 00 00 00 00 00
0xB0: 09 00 07 01 00 00 00 00 00 00 00 00 00 00 00 00
0xC0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xD0: 01 90 22 00 00 00 00 00 00 00 00 00 00 00 00 00
0xE0: 00 80 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xF0: 00 00 00 00 00 00 00 00 d1 0f 01 00 18 00 80 b8
Vendor ID = 8086h, INTEL CORPORATION
Device ID = f21h,
PCI index = 0h
Class Code = 01018ah Mass Storage (IDE) ProgIF=138
Revision ID = eh
Bus number = 0
Device number = 19
Function num = 0
Status Reg = 2b0h
Command Reg = 7h
Header type = 0h Single-function
BIST = 0h Build-in-self-test not supported
Latency Timer...
View Full Message
|
|
|
|
|
|
Klaus Pantleon(deleted)
|
Re: Fsys.umass in .boot not working
|
|
Klaus Pantleon(deleted)
02/19/2016 2:04 AM
post115797
|
Re: Fsys.umass in .boot not working
Hi Oleg,
when I use Debian 8.3 and set apic=off the USB ports are still usable at running Linux.
The USB and the Network Drivers are using the same IRQ7 and I can use the USB keyboard/mouse whether there is a cable
conencted to the network port or not.
Therefore I assume that the IRQ Routing on the PC is OK.
The PCI listing is attached:
root@nano:~# lspci -v
00:00.0 Host bridge: Intel Corporation Atom Processor Z36xxx/Z37xxx Series SoC Transaction Register (rev 0e)
Subsystem: Intel Corporation Device 7270
Flags: bus master, fast devsel, latency 0
Kernel driver in use: iosf_mbi_pci
00:02.0 VGA compatible controller: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display (rev 0e) (prog-if 00 [VGA controller])
Subsystem: Intel Corporation Device 7270
Flags: bus master, fast devsel, latency 0, IRQ 7
Memory at d0000000 (32-bit, non-prefetchable) [size=4M]
Memory at c0000000 (32-bit, prefetchable) [size=256M]
I/O ports at 7050 [size=8]
Expansion ROM at <unassigned>
[disabled]
Capabilities: [d0] Power Management version 2
Capabilities: [90] MSI: Enable- Count=1/1 Maskable- 64bit-
Capabilities: [b0] Vendor Specific Information: Len=07 <?>
00:13.0 IDE interface: Intel Corporation Device 0f21 (rev 0e) (prog-if 8a [Master SecP PriP])
Subsystem: Intel Corporation Device 7270
Flags: bus master, 66MHz, medium devsel, latency 0, IRQ 10
I/O ports at 01f0 [size=8]
I/O ports at 03f4
I/O ports at 0170 [size=8]
I/O ports at 0374
I/O ports at 7030 [size=16]
I/O ports at 7020 [size=16]
Capabilities: [70] Power Management version 3
Kernel driver in use: ata_piix
00:1a.0 Encryption controller: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Trusted Execution Engine (rev 0e)
Subsystem: Intel Corporation Device 7270
Flags: bus master, fast devsel, latency 0, IRQ 11
Memory at d0800000 (32-bit, non-prefetchable) [size=1M]
Memory at d0700000 (32-bit, non-prefetchable) [size=1M]
Capabilities: [80] Power Management version 3
Capabilities: [a0] MSI: Enable- Count=1/1 Maskable- 64bit-
00:1b.0 Audio device: Intel Corporation Atom Processor Z36xxx/Z37xxx Series High Definition Audio Controller (rev 0e)
Subsystem: Intel Corporation Device 7270
Flags: bus master, fast devsel, latency 0, IRQ 26
Memory at d0900000 (64-bit, non-prefetchable) [size=16K]
Capabilities: [50] Power Management version 2
Capabilities: [60] MSI: Enable+ Count=1/1 Maskable- 64bit+
Kernel driver in use: snd_hda_intel
00:1c.0 PCI bridge: Intel Corporation Device 0f48 (rev 0e) (prog-if 00 [Normal decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
I/O behind bridge: 00001000-00001fff
Memory behind bridge: d0600000-d06fffff
Prefetchable memory behind bridge: 0000000140000000-00000001401fffff
Capabilities: [40] Express Root Port (Slot+), MSI 00
Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit-
Capabilities: [90] Subsystem: Intel Corporation Device 7270
Capabilities: [a0] Power Management version 3
Kernel driver in use: pcieport
00:1c.1 PCI bridge: Intel Corporation Device 0f4a (rev 0e) (prog-if 00 [Normal decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=02, subordinate=02, sec-latency=0
I/O behind bridge: 00006000-00006fff
Memory behind bridge: d0500000-d05fffff
Prefetchable memory behind bridge: 0000000140200000-00000001403fffff
Capabilities: [40] Express Root Port (Slot+), MSI 00
Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit-
Capabilities: [90] Subsystem: Intel...
View Full Message
|
|
|
|
|
|
Klaus Pantleon(deleted)
|
Re: Fsys.umass in .boot not working
|
|
Klaus Pantleon(deleted)
02/19/2016 2:39 AM
post115798
|
Re: Fsys.umass in .boot not working
Hi Oleg,
sorry for the misleading Information but I'm confused about the Interrupt Routing on the new device.
If I set "acpi=off noapic" as boot parameter in linux I get with "lspci -v" the info that network and USB is using IRQ7.
But when I wacht the intrrupts using 'watch -n "cat /proc/Interrupts" ' I see that the Interrupts of the Network traffic
are on 21 and 22.
How I can force the disabling of APIC other then "acpi=off noapic".
BR, Klaus
root@nano:~# cat /proc/interrupts
CPU0
0: 8 XT-PIC-XT-PIC timer
1: 2 XT-PIC-XT-PIC i8042
2: 0 XT-PIC-XT-PIC cascade
7: 231 XT-PIC-XT-PIC ehci_hcd:usb1, i801_smbus
8: 0 XT-PIC-XT-PIC rtc0
12: 4 XT-PIC-XT-PIC i8042
14: 5249 XT-PIC-XT-PIC ata_piix
15: 0 XT-PIC-XT-PIC ata_piix
16: 0 PCI-MSI-edge PCIe PME, pciehp
17: 0 PCI-MSI-edge PCIe PME, pciehp
18: 0 PCI-MSI-edge PCIe PME, pciehp
19: 0 PCI-MSI-edge PCIe PME, pciehp
20: 1 PCI-MSI-edge eth0
21: 1138 PCI-MSI-edge eth0-rx-0
22: 1132 PCI-MSI-edge eth0-tx-0
23: 0 PCI-MSI-edge eth1
24: 234 PCI-MSI-edge eth1-rx-0
25: 234 PCI-MSI-edge eth1-tx-0
26: 621 PCI-MSI-edge snd_hda_intel
NMI: 2 Non-maskable interrupts
LOC: 121832 Local timer interrupts
SPU: 0 Spurious interrupts
PMI: 2 Performance monitoring interrupts
IWI: 0 IRQ work interrupts
RTR: 0 APIC ICR read retries
RES: 0 Rescheduling interrupts
CAL: 0 Function call interrupts
TLB: 0 TLB shootdowns
TRM: 0 Thermal event interrupts
THR: 0 Threshold APIC interrupts
MCE: 0 Machine check exceptions
MCP: 2 Machine check polls
HYP: 0 Hypervisor callback interrupts
ERR: 0
MIS: 0
|
|
|
|
|
|
Oleg Bolshakov
|
Re: Fsys.umass in .boot not working
|
|
Oleg Bolshakov
02/19/2016 7:54 AM
post115801
|
Re: Fsys.umass in .boot not working
Hi Klaus,
You can use "acpi=off noapic pci=nomsi" to disable APIC and MSI. Please post here output of cat /proc/interrupts .
Respectfully,
Oleg
19 февр. 2016 г., в 10:39:02, Klaus Pantleon <community-noreply@qnx.com> написал:
> Hi Oleg,
> sorry for the misleading Information but I'm confused about the Interrupt Routing on the new device.
> If I set "acpi=off noapic" as boot parameter in linux I get with "lspci -v" the info that network and USB is using
IRQ7.
> But when I wacht the intrrupts using 'watch -n "cat /proc/Interrupts" ' I see that the Interrupts of the Network
traffic are on 21 and 22.
> How I can force the disabling of APIC other then "acpi=off noapic".
>
> BR, Klaus
>
> root@nano:~# cat /proc/interrupts
> CPU0
> 0: 8 XT-PIC-XT-PIC timer
> 1: 2 XT-PIC-XT-PIC i8042
> 2: 0 XT-PIC-XT-PIC cascade
> 7: 231 XT-PIC-XT-PIC ehci_hcd:usb1, i801_smbus
> 8: 0 XT-PIC-XT-PIC rtc0
> 12: 4 XT-PIC-XT-PIC i8042
> 14: 5249 XT-PIC-XT-PIC ata_piix
> 15: 0 XT-PIC-XT-PIC ata_piix
> 16: 0 PCI-MSI-edge PCIe PME, pciehp
> 17: 0 PCI-MSI-edge PCIe PME, pciehp
> 18: 0 PCI-MSI-edge PCIe PME, pciehp
> 19: 0 PCI-MSI-edge PCIe PME, pciehp
> 20: 1 PCI-MSI-edge eth0
> 21: 1138 PCI-MSI-edge eth0-rx-0
> 22: 1132 PCI-MSI-edge eth0-tx-0
> 23: 0 PCI-MSI-edge eth1
> 24: 234 PCI-MSI-edge eth1-rx-0
> 25: 234 PCI-MSI-edge eth1-tx-0
> 26: 621 PCI-MSI-edge snd_hda_intel
> NMI: 2 Non-maskable interrupts
> LOC: 121832 Local timer interrupts
> SPU: 0 Spurious interrupts
> PMI: 2 Performance monitoring interrupts
> IWI: 0 IRQ work interrupts
> RTR: 0 APIC ICR read retries
> RES: 0 Rescheduling interrupts
> CAL: 0 Function call interrupts
> TLB: 0 TLB shootdowns
> TRM: 0 Thermal event interrupts
> THR: 0 Threshold APIC interrupts
> MCE: 0 Machine check exceptions
> MCP: 2 Machine check polls
> HYP: 0 Hypervisor callback interrupts
> ERR: 0
> MIS: 0
>
>
>
>
> _______________________________________________
>
> General
> http://community.qnx.com/sf/go/post115798
> To cancel your subscription to this discussion, please e-mail general-qnx4-unsubscribe@community.qnx.com
|
|
|
|
|
|
Klaus Pantleon(deleted)
|
Re: Fsys.umass in .boot not working
|
|
Klaus Pantleon(deleted)
02/19/2016 8:53 AM
post115804
|
Re: Fsys.umass in .boot not working
Hi Oleg,
thanks for the boot parameter ! I ws searching for them but had no success. the "pci=nomsi" was new for me.
root@nano:~# cat /proc/interrupts
CPU0
0: 8 XT-PIC-XT-PIC timer
1: 2 XT-PIC-XT-PIC i8042
2: 0 XT-PIC-XT-PIC cascade
7: 2050 XT-PIC-XT-PIC PCIe PME, PCIe PME, PCIe PME, PCIe PME, pciehp, pciehp, pciehp, pciehp, ehci_hcd:
usb1, i801_smbus, eth0, eth1
8: 0 XT-PIC-XT-PIC rtc0
11: 621 XT-PIC-XT-PIC snd_hda_intel
12: 4 XT-PIC-XT-PIC i8042
14: 5588 XT-PIC-XT-PIC ata_piix
15: 0 XT-PIC-XT-PIC ata_piix
NMI: 2 Non-maskable interrupts
LOC: 190123 Local timer interrupts
SPU: 0 Spurious interrupts
PMI: 2 Performance monitoring interrupts
IWI: 0 IRQ work interrupts
RTR: 0 APIC ICR read retries
RES: 0 Rescheduling interrupts
CAL: 0 Function call interrupts
TLB: 0 TLB shootdowns
TRM: 0 Thermal event interrupts
THR: 0 Threshold APIC interrupts
MCE: 0 Machine check exceptions
MCP: 3 Machine check polls
HYP: 0 Hypervisor callback interrupts
ERR: 0
MIS: 0
|
|
|
|
|
|
Oleg Bolshakov
|
Re: Fsys.umass in .boot not working
|
|
Oleg Bolshakov
02/22/2016 1:25 PM
post115836
|
Re: Fsys.umass in .boot not working
Hi Klaus,
Does USB controller work fine using this configuration?
Respectfully,
Oleg
19 февр. 2016 г., в 16:53, Klaus Pantleon <community-noreply@qnx.com> написал:
> Hi Oleg,
> thanks for the boot parameter ! I ws searching for them but had no success. the "pci=nomsi" was new for me.
>
>
> root@nano:~# cat /proc/interrupts
> CPU0
> 0: 8 XT-PIC-XT-PIC timer
> 1: 2 XT-PIC-XT-PIC i8042
> 2: 0 XT-PIC-XT-PIC cascade
> 7: 2050 XT-PIC-XT-PIC PCIe PME, PCIe PME, PCIe PME, PCIe PME, pciehp, pciehp, pciehp, pciehp, ehci_hcd:
usb1, i801_smbus, eth0, eth1
> 8: 0 XT-PIC-XT-PIC rtc0
> 11: 621 XT-PIC-XT-PIC snd_hda_intel
> 12: 4 XT-PIC-XT-PIC i8042
> 14: 5588 XT-PIC-XT-PIC ata_piix
> 15: 0 XT-PIC-XT-PIC ata_piix
> NMI: 2 Non-maskable interrupts
> LOC: 190123 Local timer interrupts
> SPU: 0 Spurious interrupts
> PMI: 2 Performance monitoring interrupts
> IWI: 0 IRQ work interrupts
> RTR: 0 APIC ICR read retries
> RES: 0 Rescheduling interrupts
> CAL: 0 Function call interrupts
> TLB: 0 TLB shootdowns
> TRM: 0 Thermal event interrupts
> THR: 0 Threshold APIC interrupts
> MCE: 0 Machine check exceptions
> MCP: 3 Machine check polls
> HYP: 0 Hypervisor callback interrupts
> ERR: 0
> MIS: 0
>
>
>
>
>
>
> _______________________________________________
>
> General
> http://community.qnx.com/sf/go/post115804
> To cancel your subscription to this discussion, please e-mail general-qnx4-unsubscribe@community.qnx.com
|
|
|
|
|
|
Klaus Pantleon(deleted)
|
Re: Fsys.umass in .boot not working
|
|
Klaus Pantleon(deleted)
02/23/2016 1:48 AM
post115843
|
Re: Fsys.umass in .boot not working
Hello Oleg,
using your proposed boot parameters I get the above /proc/Interrupts and the usb mouse/keyboard is working whether or
not there is the Network cable connected. the Network and the USB is working without any remarkable problem. The device
gets an IP address using dhcp and I can use the mouse/Keyboard in gdm even when I disconnect the Network cable.
BR, Klaus
|
|
|
|
|
|
Klaus Pantleon(deleted)
|
Re: Fsys.umass in .boot not working
|
|
Klaus Pantleon(deleted)
04/06/2016 4:46 AM
post116055
|
Re: Fsys.umass in .boot not working
Hello Oleg,
is there a possibility to change the USB stack in that way, that it can use USB-Kbd/Mouse/Storage in that way that same
Interrupt of USB port and internal devices laike Network Card is possible?
BR, Klaus
|
|
|
|
|
|
Oleg Bolshakov
|
Re: Fsys.umass in .boot not working
|
|
Oleg Bolshakov
04/07/2016 7:15 AM
post116066
|
Re: Fsys.umass in .boot not working
Hi Klaus,
We aren’t sure where is a problem. To determine it we should test your hardware. The problem may be in BIOS. USB stack
reads interrupt number from PCI configuration. Can you tune PCI or IRQ in BIOS settings?
Respectfully,
Oleg
6 апр. 2016 г., в 11:46:19, Klaus Pantleon <community-noreply@qnx.com> написал:
> Hello Oleg,
>
> is there a possibility to change the USB stack in that way, that it can use USB-Kbd/Mouse/Storage in that way that
same Interrupt of USB port and internal devices laike Network Card is possible?
>
> BR, Klaus
>
>
>
> _______________________________________________
>
> General
> http://community.qnx.com/sf/go/post116055
> To cancel your subscription to this discussion, please e-mail general-qnx4-unsubscribe@community.qnx.com
|
|
|
|
|
|
