|
Joe Krachey
10/25/2011 11:10 AM
post89586
|
We have a MPC7448 card with an Intel 82546 network controller. When we attempt to connect to a BCM5396 Ethernet switch,
the system hangs ( no more serial data anyways). This is how we bring the interface up:
io-net -d mv64360 memrange=0xf1000000,deviceindex=0,verbose=4 -d mv64360
memrange=0xf1000000,deviceindex=1,verbose=4 -d i82544
duplex=1,speed=1000 -ptcpip
We are using Neutrino 6.3.2 along with Service Pack 3 Network Drivers Patch (Patch ID 685). Are there any newer updates
to devn-i82544.so for 6.3.x?
Our Neutrino port was working correctly until our chassis vendor updated the network switch.
We have confirmed that the hardware is functional with our linux port for this card.
Thanks
Joe Krachey
|
|
|
|
|
|
Hugh Brown
10/25/2011 11:19 AM
post89589
|
Please try the attached driver. The new driver is called devn-e1000.so.
--
Hugh Brown
QNX Software Systems Limited
175 Terence Matthews Crescent,
Ottawa. ON. K2M 1W8.
Telephone: 613-591-0931
On 11-10-25 11:11 AM, "Joe Krachey" <community-noreply@qnx.com> wrote:
>We have a MPC7448 card with an Intel 82546 network controller. When we
>attempt to connect to a BCM5396 Ethernet switch, the system hangs ( no
>more serial data anyways). This is how we bring the interface up:
>
>io-net -d mv64360 memrange=0xf1000000,deviceindex=0,verbose=4 -d mv64360
> memrange=0xf1000000,deviceindex=1,verbose=4 -d i82544
> duplex=1,speed=1000 -ptcpip
>
>
>
>We are using Neutrino 6.3.2 along with Service Pack 3 Network Drivers
>Patch (Patch ID 685). Are there any newer updates to devn-i82544.so for
>6.3.x?
>
>Our Neutrino port was working correctly until our chassis vendor updated
>the network switch.
>We have confirmed that the hardware is functional with our linux port for
>this card.
>
>Thanks
>Joe Krachey
>
>
>
>_______________________________________________
>
>Networking Drivers
>http://community.qnx.com/sf/go/post89586
>
|
|
|
|
|
|
Joe Krachey
10/25/2011 12:37 PM
post89593
|
It still hangs in the same manner using the e1000.so driver.
|
|
|
|
|
|
Hugh Brown
10/25/2011 12:38 PM
post89595
|
If you only run the e1000 driver, does it still hang? Maybe it is getting
the incorrect interrupt.
--
Hugh Brown
QNX Software Systems Limited
175 Terence Matthews Crescent,
Ottawa. ON. K2M 1W8.
Telephone: 613-591-0931
On 11-10-25 12:37 PM, "Joe Krachey" <community-noreply@qnx.com> wrote:
>It still hangs in the same manner using the e1000.so driver.
>
>
>
>_______________________________________________
>
>Networking Drivers
>http://community.qnx.com/sf/go/post89593
>
|
|
|
|
|
|
Joe Krachey
10/25/2011 12:45 PM
post89596
|
When I only load the e1000 driver, it gives a kernel panic.
# io-net -d e1000 duplex=1,speed=1000 -ptcpip
#
Shutdown[0,0] S/C/F=5/2/6 C/D=00207970/0026277c state(4bfc)= now lock exit specret 12
QNX Version 6.3.2 Release 2006/03/16-14:18:26EST
[0]PID-TID=1-1? P/T FL=00019001/08000000 "proc/boot/procnto-600"
[0]ASPACE PID=45063 PF=00401010 ""
ppcbe context[0f382b00]:
0000: 40000000 0f382bb0 00267658 40000010 00000002 31000024 00000000 00000000
0020: 00000002 00000004 00000000 00000006 05ac9440 00269610 00000062 00000000
0040: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00262778
0060: 00008000 00000001 002621f8 00000000 0000f000 00004bfb 0f382bc0 0f7f56f0
0080: 002444c4 0f7e9040 00021032 0f7e90dc 44000000 20000000 00000000 00000000
00a0: 00000000
instruction[0f7e90dc]:
0f 7f 56 f0 00 24 44 c4 0f 7e 98 bc 00 20 90 32 00 23 e7 b8 44 00 00 00 20 00
stack[0f382bb0]:
0000: 00000000 00000000 00000000 00000000 00009032 0f382c70 00267658 0f7eb650
0020: 00000000 0000000f 00000000 311003c0 00000002 00000004 00000000 00000006
0040: 05ac9440 00269610 00000062 0f7eb650 00000000 00000000 00000000 00000000
0060: 00000000 00000000 00000000 00262778 00008000 00000001 002621f8 00000000
|
|
|
|
|
|
Hugh Brown
10/25/2011 12:50 PM
post89598
|
If you use the timer interrupt with the e1000 driver, does it still panic?
io-net -de1000 irq=...
I think that the timer irq on PPC is normally something like 0x80000000.
--
Hugh Brown
QNX Software Systems Limited
175 Terence Matthews Crescent,
Ottawa. ON. K2M 1W8.
Telephone: 613-591-0931
On 11-10-25 12:45 PM, "Joe Krachey" <community-noreply@qnx.com> wrote:
>When I only load the e1000 driver, it gives a kernel panic.
>
># io-net -d e1000 duplex=1,speed=1000 -ptcpip
>#
>Shutdown[0,0] S/C/F=5/2/6 C/D=00207970/0026277c state(4bfc)= now lock
>exit specret 12
>QNX Version 6.3.2 Release 2006/03/16-14:18:26EST
>[0]PID-TID=1-1? P/T FL=00019001/08000000 "proc/boot/procnto-600"
>[0]ASPACE PID=45063 PF=00401010 ""
>ppcbe context[0f382b00]:
>0000: 40000000 0f382bb0 00267658 40000010 00000002 31000024 00000000
>00000000
>0020: 00000002 00000004 00000000 00000006 05ac9440 00269610 00000062
>00000000
>0040: 00000000 00000000 00000000 00000000 00000000 00000000 00000000
>00262778
>0060: 00008000 00000001 002621f8 00000000 0000f000 00004bfb 0f382bc0
>0f7f56f0
>0080: 002444c4 0f7e9040 00021032 0f7e90dc 44000000 20000000 00000000
>00000000
>00a0: 00000000
>instruction[0f7e90dc]:
>0f 7f 56 f0 00 24 44 c4 0f 7e 98 bc 00 20 90 32 00 23 e7 b8 44 00 00 00
>20 00
>stack[0f382bb0]:
>0000: 00000000 00000000 00000000 00000000 00009032 0f382c70 00267658
>0f7eb650
>0020: 00000000 0000000f 00000000 311003c0 00000002 00000004 00000000
>00000006
>0040: 05ac9440 00269610 00000062 0f7eb650 00000000 00000000 00000000
>00000000
>0060: 00000000 00000000 00000000 00262778 00008000 00000001 002621f8
>00000000
>
>
>
>_______________________________________________
>
>Networking Drivers
>http://community.qnx.com/sf/go/post89596
>
|
|
|
|
|
|
Joe Krachey
10/27/2011 9:36 AM
post89675
|
I added the -irq=0x80000000 to the e1000 driver and it would still hang.
I tried this with the 82544 driver and was able to successfully load that driver when adding the -irq=0x80000000.
|
|
|
|
|
|
Joe Krachey
10/27/2011 9:43 AM
post89676
|
Is the e1000 6.3.2 driver compatible with 6.3.0? We are running with 6.3.0.
|
|
|
|
|
|
Hugh Brown
10/27/2011 10:08 AM
post89678
|
Yes, it should be compatible.
You will have to start the driver with "verbose=4" on the command line to
see where the driver is hanging. Look at the sloginfo output.
--
Hugh Brown
QNX Software Systems Limited
175 Terence Matthews Crescent,
Ottawa. ON. K2M 1W8.
Telephone: 613-591-0931
On 11-10-27 9:43 AM, "Joe Krachey" <community-noreply@qnx.com> wrote:
>Is the e1000 6.3.2 driver compatible with 6.3.0? We are running with
>6.3.0.
>
>
>
>
>
>_______________________________________________
>
>Networking Drivers
>http://community.qnx.com/sf/go/post89676
>
|
|
|
|
|
|
Joe Krachey
10/27/2011 10:44 AM
post89682
|
When I add the -verbose=4, when using the e1000 driver, I get the following output:
# io-net -d mv64360 memrange=0xf1000000,deviceindex=0,verbose=4 -d mv64360 memrange=0xf1000000,deviceindex=1,verbose=4 -
d e1000 -verbose=4 -irq=0x80000000 duplex=1,speed=1000 -ptcpip
# io-net: illegal option -- e
io-net: illegal option -- r
io-net: illegal option -- b
io-net: illegal option -- o
io-net: illegal option -- e
io-net: illegal option -- =
io-net: illegal option -- 4
The prompt does not come back to run sloginfo.
When I add the same -verbose to the 82544 driver, it does not hang but I get the same error messages.
# io-net -d mv64360 memrange=0xf1000000,deviceindex=0,verbose=4 -d mv64360 memrange=0xf1000000,deviceindex=1,verbose=4 -
d i82544 -verbose=4 duplex=1,speed=1000 -ptcpip
# io-net: illegal option -- e
io-net: illegal option -- r
io-net: illegal option -- b
io-net: illegal option -- o
io-net: illegal option -- e
io-net: illegal option -- =
io-net: illegal option -- 4
Jan 01 00:00:19 5 10 0 MAC 1: shutdown1
Jan 01 00:00:19 5 10 0 MAC 1: shutdown2
Jan 01 00:00:19 5 10 0 MAC 0: shutdown1
Jan 01 00:00:19 5 10 0 MAC 0: shutdown2
Jan 01 00:00:22 5 10 0 MAC 0 : SDRAM bank/size/CS 0/0x20000000/0xe enumerated
Jan 01 00:00:22 5 10 0 devn-mv64360: MII transceiver found at address 4.
Jan 01 00:00:22 5 10 0 MAC 1 : SDRAM bank/size/CS 0/0x20000000/0xe enumerated
Jan 01 00:00:22 5 10 0 devn-mv64360: MII transceiver found at address 8.
Jan 01 00:00:22 5 17 0 io_open for id = 3
Jan 01 00:00:22 5 17 0 Alloc IRQ 97 - Flags c01
Jan 01 00:00:22 5 17 0 Alloc IRQ 98 - Flags c01
Jan 01 00:00:22 5 14 0 tcpip starting
Jan 01 00:00:22 3 14 0 Using pseudo random generator. See "random" option
The board does not hang, but the interfaces do not work.
-Joe
----- Original Message -----
From: "Hugh Brown" <community-noreply@qnx.com>
To: "drivers-networking" <post89678@community.qnx.com>
Sent: Thursday, October 27, 2011 9:08:25 AM
Subject: Re: devn-i82544 hang
Yes, it should be compatible.
You will have to start the driver with "verbose=4" on the command line to
see where the driver is hanging. Look at the sloginfo output.
--
Hugh Brown
QNX Software Systems Limited
175 Terence Matthews Crescent,
Ottawa. ON. K2M 1W8.
Telephone: 613-591-0931
On 11-10-27 9:43 AM, "Joe Krachey" <community-noreply@qnx.com> wrote:
>Is the e1000 6.3.2 driver compatible with 6.3.0? We are running with
>6.3.0.
>
>
>
>
>
>_______________________________________________
>
>Networking Drivers
>http://community.qnx.com/sf/go/post89676
>
_______________________________________________
Networking Drivers
http://community.qnx.com/sf/go/post89678
|
|
|
|
|
|
Hugh Brown
10/27/2011 10:57 AM
post89684
|
Sorry it is "-vvvv" under io-net.
--
Hugh Brown
QNX Software Systems Limited
175 Terence Matthews Crescent,
Ottawa. ON. K2M 1W8.
Telephone: 613-591-0931
On 11-10-27 10:44 AM, "Joe Krachey" <community-noreply@qnx.com> wrote:
>When I add the -verbose=4, when using the e1000 driver, I get the
>following output:
>
>
># io-net -d mv64360 memrange=0xf1000000,deviceindex=0,verbose=4 -d
>mv64360 memrange=0xf1000000,deviceindex=1,verbose=4 -d e1000 -verbose=4
>-irq=0x80000000 duplex=1,speed=1000 -ptcpip
>
># io-net: illegal option -- e
>io-net: illegal option -- r
>io-net: illegal option -- b
>io-net: illegal option -- o
>io-net: illegal option -- e
>io-net: illegal option -- =
>io-net: illegal option -- 4
>
>The prompt does not come back to run sloginfo.
>
>When I add the same -verbose to the 82544 driver, it does not hang but I
>get the same error messages.
>
># io-net -d mv64360 memrange=0xf1000000,deviceindex=0,verbose=4 -d
>mv64360 memrange=0xf1000000,deviceindex=1,verbose=4 -d i82544 -verbose=4
>duplex=1,speed=1000 -ptcpip
># io-net: illegal option -- e
>io-net: illegal option -- r
>io-net: illegal option -- b
>io-net: illegal option -- o
>io-net: illegal option -- e
>io-net: illegal option -- =
>io-net: illegal option -- 4
>
>Jan 01 00:00:19 5 10 0 MAC 1: shutdown1
>Jan 01 00:00:19 5 10 0 MAC 1: shutdown2
>Jan 01 00:00:19 5 10 0 MAC 0: shutdown1
>Jan 01 00:00:19 5 10 0 MAC 0: shutdown2
>Jan 01 00:00:22 5 10 0 MAC 0 : SDRAM bank/size/CS 0/0x20000000/0xe
>enumerated
>Jan 01 00:00:22 5 10 0 devn-mv64360: MII transceiver found at address 4.
>Jan 01 00:00:22 5 10 0 MAC 1 : SDRAM bank/size/CS 0/0x20000000/0xe
>enumerated
>Jan 01 00:00:22 5 10 0 devn-mv64360: MII transceiver found at address 8.
>Jan 01 00:00:22 5 17 0 io_open for id = 3
>Jan 01 00:00:22 5 17 0 Alloc IRQ 97 - Flags c01
>Jan 01 00:00:22 5 17 0 Alloc IRQ 98 - Flags c01
>Jan 01 00:00:22 5 14 0 tcpip starting
>Jan 01 00:00:22 3 14 0 Using pseudo random generator. See "random" option
>
>The board does not hang, but the interfaces do not work.
>
>-Joe
>
>
>----- Original Message -----
>
>From: "Hugh Brown" <community-noreply@qnx.com>
>To: "drivers-networking" <post89678@community.qnx.com>
>Sent: Thursday, October 27, 2011 9:08:25 AM
>Subject: Re: devn-i82544 hang
>
>Yes, it should be compatible.
>You will have to start the driver with "verbose=4" on the command line to
>see where the driver is hanging. Look at the sloginfo output.
>
>--
>Hugh Brown
>QNX Software Systems Limited
>175 Terence Matthews Crescent,
>Ottawa. ON. K2M 1W8.
>Telephone: 613-591-0931
>
>
>
>
>
>
>
>On 11-10-27 9:43 AM, "Joe Krachey" <community-noreply@qnx.com> wrote:
>
>>Is the e1000 6.3.2 driver compatible with 6.3.0? We are running with
>>6.3.0.
>>
>>
>>
>>
>>
>>_______________________________________________
>>
>>Networking Drivers
>>http://community.qnx.com/sf/go/post89676
>>
>
>
>
>
>_______________________________________________
>
>Networking Drivers
>http://community.qnx.com/sf/go/post89678
>
>
>
>
>
>
>_______________________________________________
>
>Networking Drivers
>http://community.qnx.com/sf/go/post89682
>
|
|
|
|
|
|
Joe Krachey
10/27/2011 11:13 AM
post89686
|
It actually reports the same behavior without the error messages. ( I should have caught the error messages were the
rest of 'verbose').
Hang
io-net -vvvv -d mv64360 memrange=0xf1000000,deviceindex=0,verbose=4 -d mv64360 memrange=0xf1000000,deviceindex=1,verbose
=4 -d i82544 duplex=1,speed=1000 -ptcpip
No Hang
io-net -d mv64360 memrange=0xf1000000,deviceindex=0,verbose=4 -d mv64360 memrange=0xf1000000,deviceindex=1,verbose=4 -d
i82544 -vvvv duplex=1,speed=1000 -ptcpip
Jan 01 00:00:13 5 10 0 MAC 1: shutdown1
Jan 01 00:00:13 5 10 0 MAC 1: shutdown2
Jan 01 00:00:13 5 10 0 MAC 0: shutdown1
Jan 01 00:00:13 5 10 0 MAC 0: shutdown2
Jan 01 00:00:18 5 10 0 MAC 0 : SDRAM bank/size/CS 0/0x20000000/0xe enumerated
Jan 01 00:00:18 5 10 0 devn-mv64360: MII transceiver found at address 4.
Jan 01 00:00:18 5 10 0 MAC 1 : SDRAM bank/size/CS 0/0x20000000/0xe enumerated
Jan 01 00:00:18 5 10 0 devn-mv64360: MII transceiver found at address 8.
Jan 01 00:00:18 5 17 0 io_open for id = 3
Jan 01 00:00:18 5 17 0 Alloc IRQ 97 - Flags c01
Jan 01 00:00:18 5 17 0 Alloc IRQ 98 - Flags c01
Jan 01 00:00:18 5 14 0 tcpip starting
Hang
io-net -d mv64360 memrange=0xf1000000,deviceindex=0,verbose=4 -d mv64360 memrange=0xf1000000,deviceindex=1,verbose=4 -d
e1000 -vvvv duplex=1,speed=1000 -ptcpip
The fact that the 82544 driver will hang or not hang based on the verbose flag seems like a timing issue.
-Joe
----- Original Message -----
From: "Hugh Brown" <community-noreply@qnx.com>
To: "drivers-networking" <post89684@community.qnx.com>
Sent: Thursday, October 27, 2011 9:57:38 AM
Subject: Re: devn-i82544 hang
Sorry it is "-vvvv" under io-net.
--
Hugh Brown
QNX Software Systems Limited
175 Terence Matthews Crescent,
Ottawa. ON. K2M 1W8.
Telephone: 613-591-0931
On 11-10-27 10:44 AM, "Joe Krachey" <community-noreply@qnx.com> wrote:
>When I add the -verbose=4, when using the e1000 driver, I get the
>following output:
>
>
># io-net -d mv64360 memrange=0xf1000000,deviceindex=0,verbose=4 -d
>mv64360 memrange=0xf1000000,deviceindex=1,verbose=4 -d e1000 -verbose=4
>-irq=0x80000000 duplex=1,speed=1000 -ptcpip
>
># io-net: illegal option -- e
>io-net: illegal option -- r
>io-net: illegal option -- b
>io-net: illegal option -- o
>io-net: illegal option -- e
>io-net: illegal option -- =
>io-net: illegal option -- 4
>
>The prompt does not come back to run sloginfo.
>
>When I add the same -verbose to the 82544 driver, it does not hang but I
>get the same error messages.
>
># io-net -d mv64360 memrange=0xf1000000,deviceindex=0,verbose=4 -d
>mv64360 memrange=0xf1000000,deviceindex=1,verbose=4 -d i82544 -verbose=4
>duplex=1,speed=1000 -ptcpip
># io-net: illegal option -- e
>io-net: illegal option -- r
>io-net: illegal option -- b
>io-net: illegal option -- o
>io-net: illegal option -- e
>io-net: illegal option -- =
>io-net: illegal option -- 4
>
>Jan 01 00:00:19 5 10 0 MAC 1: shutdown1
>Jan 01 00:00:19 5 10 0 MAC 1: shutdown2
>Jan 01 00:00:19 5 10 0 MAC 0: shutdown1
>Jan 01 00:00:19 5 10 0 MAC 0: shutdown2
>Jan 01 00:00:22 5 10 0 MAC 0 : SDRAM bank/size/CS 0/0x20000000/0xe
>enumerated
>Jan 01 00:00:22 5 10 0 devn-mv64360: MII transceiver found at address 4.
>Jan 01 00:00:22 5 10 0 MAC 1 : SDRAM bank/size/CS 0/0x20000000/0xe
>enumerated
>Jan 01 00:00:22 5 10 0 devn-mv64360: MII transceiver found at address 8.
>Jan 01 00:00:22 5 17 0 io_open for id = 3
>Jan 01 00:00:22 5 17 0 Alloc IRQ 97 - Flags c01
>Jan 01 00:00:22 5 17 0 Alloc IRQ 98 - Flags c01
>Jan 01 00:00:22 5 14 0 tcpip starting
>Jan 01 00:00:22 3 14 0 Using pseudo random generator. See "random" option
>
>The board does not hang, but the interfaces do not work.
>...
View Full Message
|
|
|
|
|
|
Hugh Brown
10/27/2011 11:26 AM
post89687
|
Don't start io-net with '-vvvv', start the e1000 driver with '-vvvv'.
Please don't start any other drivers! Just run "io-net -de1000 -vvvv" and
see what is in sloginfo.
--
Hugh Brown
QNX Software Systems Limited
175 Terence Matthews Crescent,
Ottawa. ON. K2M 1W8.
Telephone: 613-591-0931
On 11-10-27 11:13 AM, "Joe Krachey" <community-noreply@qnx.com> wrote:
>It actually reports the same behavior without the error messages. ( I
>should have caught the error messages were the rest of 'verbose').
>
>Hang
>
>io-net -vvvv -d mv64360 memrange=0xf1000000,deviceindex=0,verbose=4 -d
>mv64360 memrange=0xf1000000,deviceindex=1,verbose=4 -d i82544
>duplex=1,speed=1000 -ptcpip
>
>No Hang
>
>io-net -d mv64360 memrange=0xf1000000,deviceindex=0,verbose=4 -d mv64360
>memrange=0xf1000000,deviceindex=1,verbose=4 -d i82544 -vvvv
>duplex=1,speed=1000 -ptcpip
>
>Jan 01 00:00:13 5 10 0 MAC 1: shutdown1
>Jan 01 00:00:13 5 10 0 MAC 1: shutdown2
>Jan 01 00:00:13 5 10 0 MAC 0: shutdown1
>Jan 01 00:00:13 5 10 0 MAC 0: shutdown2
>Jan 01 00:00:18 5 10 0 MAC 0 : SDRAM bank/size/CS 0/0x20000000/0xe
>enumerated
>Jan 01 00:00:18 5 10 0 devn-mv64360: MII transceiver found at address 4.
>Jan 01 00:00:18 5 10 0 MAC 1 : SDRAM bank/size/CS 0/0x20000000/0xe
>enumerated
>Jan 01 00:00:18 5 10 0 devn-mv64360: MII transceiver found at address 8.
>Jan 01 00:00:18 5 17 0 io_open for id = 3
>Jan 01 00:00:18 5 17 0 Alloc IRQ 97 - Flags c01
>Jan 01 00:00:18 5 17 0 Alloc IRQ 98 - Flags c01
>Jan 01 00:00:18 5 14 0 tcpip starting
>
>Hang
>
>io-net -d mv64360 memrange=0xf1000000,deviceindex=0,verbose=4 -d mv64360
>memrange=0xf1000000,deviceindex=1,verbose=4 -d e1000 -vvvv
>duplex=1,speed=1000 -ptcpip
>
>The fact that the 82544 driver will hang or not hang based on the verbose
>flag seems like a timing issue.
>
>-Joe
>----- Original Message -----
>
>From: "Hugh Brown" <community-noreply@qnx.com>
>To: "drivers-networking" <post89684@community.qnx.com>
>Sent: Thursday, October 27, 2011 9:57:38 AM
>Subject: Re: devn-i82544 hang
>
>Sorry it is "-vvvv" under io-net.
>
>--
>Hugh Brown
>QNX Software Systems Limited
>175 Terence Matthews Crescent,
>Ottawa. ON. K2M 1W8.
>Telephone: 613-591-0931
>
>
>
>
>
>
>
>On 11-10-27 10:44 AM, "Joe Krachey" <community-noreply@qnx.com> wrote:
>
>>When I add the -verbose=4, when using the e1000 driver, I get the
>>following output:
>>
>>
>># io-net -d mv64360 memrange=0xf1000000,deviceindex=0,verbose=4 -d
>>mv64360 memrange=0xf1000000,deviceindex=1,verbose=4 -d e1000 -verbose=4
>>-irq=0x80000000 duplex=1,speed=1000 -ptcpip
>>
>># io-net: illegal option -- e
>>io-net: illegal option -- r
>>io-net: illegal option -- b
>>io-net: illegal option -- o
>>io-net: illegal option -- e
>>io-net: illegal option -- =
>>io-net: illegal option -- 4
>>
>>The prompt does not come back to run sloginfo.
>>
>>When I add the same -verbose to the 82544 driver, it does not hang but I
>>get the same error messages.
>>
>># io-net -d mv64360 memrange=0xf1000000,deviceindex=0,verbose=4 -d
>>mv64360 memrange=0xf1000000,deviceindex=1,verbose=4 -d i82544 -verbose=4
>>duplex=1,speed=1000 -ptcpip
>># io-net: illegal option -- e
>>io-net: illegal option -- r
>>io-net: illegal option -- b
>>io-net: illegal option -- o
>>io-net: illegal option -- e
>>io-net: illegal option -- =
>>io-net: illegal option -- 4
>>
>>Jan 01 00:00:19 5 10 0 MAC 1: shutdown1
>>Jan 01 00:00:19 5 10 0 MAC 1: shutdown2
>>Jan 01 00:00:19 5 10 0 MAC 0:...
View Full Message
|
|
|
|
|
|
Joe Krachey
10/27/2011 11:42 AM
post89690
|
Is there a way to direct output from sloginfo to the console? This system runs out of RAM, so the contents of sloginfo
get cleared after the card reboots.
# io-net -de1000 -vvvv
#
#
Shutdown[0,0] S/C/F=5/2/6 C/D=00207970/0026277c state(18693)= now exit 3
QNX Version 6.3.2 Release 2006/03/16-14:18:26EST
[0]PID-TID=1-1? P/T FL=00019001/08000000 "proc/boot/procnto-600"
[0]ASPACE PID=40967 PF=00401010 "proc/boov`-net"
ppcbe context[0e113d70]:
0000: 40000000 0e113e20 00267658 40000010 00000002 31000024 00000000 00000000
0020: 00000002 00000004 00000000 00000005 983d7140 00269610 00000062 00000000
0040: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00262778
0060: 00008000 00000001 002621f8 00000000 0000f000 00018692 0e113e30 0f7f56f0
0080: 002444c4 0f7e9040 00021032 0f7e90dc 44000000 20000000 00000000 00000000
00a0: 00000000
instruction[0f7e90dc]:
0f 7f 56 f0 00 24 44 c4 0f 7e 98 bc 00 20 90 32 00 23 e7 b8 44 00 00 00 20 00
stack[0e113e20]:
0000: 00000000 00000000 00000000 00000000 00009032 0e113ee0 00267658 0f7eb650
0020: 00000000 0000000f 00000000 311003c0 00000002 00000004 00000000 00000005
0040: 983d7140 00269610 00000062 0f7eb650 00000000 00000000 00000000 00000000
0060: 00000000 00000000 00000000 00262778 00008000 00000001 002621f8 00000000
----- Original Message -----
|
|
|
|
|
|
Hugh Brown
10/27/2011 11:44 AM
post89691
|
sloginfo -w &
io-net -de1000 -vvvv
--
Hugh Brown
QNX Software Systems Limited
175 Terence Matthews Crescent,
Ottawa. ON. K2M 1W8.
Telephone: 613-591-0931
On 11-10-27 11:42 AM, "Joe Krachey" <community-noreply@qnx.com> wrote:
>Is there a way to direct output from sloginfo to the console? This system
>runs out of RAM, so the contents of sloginfo get cleared after the card
>reboots.
>
># io-net -de1000 -vvvv
>#
>#
>Shutdown[0,0] S/C/F=5/2/6 C/D=00207970/0026277c state(18693)= now exit 3
>QNX Version 6.3.2 Release 2006/03/16-14:18:26EST
>[0]PID-TID=1-1? P/T FL=00019001/08000000 "proc/boot/procnto-600"
>[0]ASPACE PID=40967 PF=00401010 "proc/boov`-net"
>ppcbe context[0e113d70]:
>0000: 40000000 0e113e20 00267658 40000010 00000002 31000024 00000000
>00000000
>0020: 00000002 00000004 00000000 00000005 983d7140 00269610 00000062
>00000000
>0040: 00000000 00000000 00000000 00000000 00000000 00000000 00000000
>00262778
>0060: 00008000 00000001 002621f8 00000000 0000f000 00018692 0e113e30
>0f7f56f0
>0080: 002444c4 0f7e9040 00021032 0f7e90dc 44000000 20000000 00000000
>00000000
>00a0: 00000000
>instruction[0f7e90dc]:
>0f 7f 56 f0 00 24 44 c4 0f 7e 98 bc 00 20 90 32 00 23 e7 b8 44 00 00 00
>20 00
>stack[0e113e20]:
>0000: 00000000 00000000 00000000 00000000 00009032 0e113ee0 00267658
>0f7eb650
>0020: 00000000 0000000f 00000000 311003c0 00000002 00000004 00000000
>00000005
>0040: 983d7140 00269610 00000062 0f7eb650 00000000 00000000 00000000
>00000000
>0060: 00000000 00000000 00000000 00262778 00008000 00000001 002621f8
>00000000
>----- Original Message -----
>
>
>
>
>
>
>
>
>_______________________________________________
>
>Networking Drivers
>http://community.qnx.com/sf/go/post89690
>
|
|
|
|
|
|
Joe Krachey
10/27/2011 11:55 AM
post89692
|
# sloginfo -w & io-net -de1000 -vvvv
[2] 20492
Time Sev Major Minor Args
Jan 01 00:00:00 5 17 0 pci_server: Oct 25 2011 09:28:32
Jan 01 00:00:00 5 17 0 Low memory CPU a0000000 - PCI a0000000
# Jan 01 00:00:00 5 17 0 High memory CPU bfffffff - PCI c0000000
Jan 01 00:00:00 5 17 0 Low port CPU f0000000 - PCI f0000000
Jan 01 00:00:00 5 17 0 High port CPU f07fffff - PCI f0800000
Jan 01 00:00:00 5 17 0 Found host bridge 0 f8
Jan 01 00:00:00 5 17 0 Configure bridge - bus 0 - devfunc f8
Jan 01 00:00:00 5 17 0 cb Bus 0 - Devfn f8 - dword ff0000
Jan 01 00:00:00 5 17 0 find_bus 0
Jan 01 00:00:00 5 17 0 alloc_bus 0 0
Jan 01 00:00:00 5 17 0 Bus 0 - Device 31 - Function 0
Jan 01 00:00:00 5 17 0 Vendor 11ab Device 6485 Index 0 ClassCode 60000
Jan 01 00:00:00 5 17 0 find_bus 0
Jan 01 00:00:00 5 17 0 Setup bridge 0 - Lastbus = 0
Jan 01 00:00:00 5 17 0 Configure bridge - bus 0 - devfunc f9
Jan 01 00:00:00 5 17 0 cb Bus 0 - Devfn f9 - dword 1ff0000
Jan 01 00:00:00 5 17 0 find_bus 0
Jan 01 00:00:00 5 17 0 Bus 0 - Device 31
<hangs here>
|
|
|
|
|
|
Hugh Brown
10/27/2011 11:59 AM
post89693
|
That is still PCI server output. Are you starting this manually or in the
boot script? If in the boot script, allow some time for sloginfo to output
its data before starting io-net.
--
Hugh Brown
QNX Software Systems Limited
175 Terence Matthews Crescent,
Ottawa. ON. K2M 1W8.
Telephone: 613-591-0931
On 11-10-27 11:55 AM, "Joe Krachey" <community-noreply@qnx.com> wrote:
># sloginfo -w & io-net -de1000 -vvvv
>[2] 20492
>Time Sev Major Minor Args
>Jan 01 00:00:00 5 17 0 pci_server: Oct 25 2011 09:28:32
>Jan 01 00:00:00 5 17 0 Low memory CPU a0000000 - PCI a0000000
># Jan 01 00:00:00 5 17 0 High memory CPU bfffffff - PCI c0000000
>Jan 01 00:00:00 5 17 0 Low port CPU f0000000 - PCI f0000000
>Jan 01 00:00:00 5 17 0 High port CPU f07fffff - PCI f0800000
>Jan 01 00:00:00 5 17 0 Found host bridge 0 f8
>Jan 01 00:00:00 5 17 0 Configure bridge - bus 0 - devfunc f8
>Jan 01 00:00:00 5 17 0 cb Bus 0 - Devfn f8 - dword ff0000
>Jan 01 00:00:00 5 17 0 find_bus 0
>Jan 01 00:00:00 5 17 0 alloc_bus 0 0
>Jan 01 00:00:00 5 17 0 Bus 0 - Device 31 - Function 0
>Jan 01 00:00:00 5 17 0 Vendor 11ab Device 6485 Index 0 ClassCode 60000
>Jan 01 00:00:00 5 17 0 find_bus 0
>Jan 01 00:00:00 5 17 0 Setup bridge 0 - Lastbus = 0
>Jan 01 00:00:00 5 17 0 Configure bridge - bus 0 - devfunc f9
>Jan 01 00:00:00 5 17 0 cb Bus 0 - Devfn f9 - dword 1ff0000
>Jan 01 00:00:00 5 17 0 find_bus 0
>Jan 01 00:00:00 5 17 0 Bus 0 - Device 31
><hangs here>
>
>
>
>
>_______________________________________________
>
>Networking Drivers
>http://community.qnx.com/sf/go/post89692
>
|
|
|
|
|
|
Joe Krachey
10/27/2011 12:04 PM
post89696
|
Manually.
# io-net -de1000 -vvvv
# Jan 01 00:01:14 5 17 0 io_open for id = 3
Jan 01 00:01:14 5 17 0 in temp fix, i= 4, device_enabled = 0, show_pci = 0, next_attach = 0, Bus=0x0 Devfunc=0x40
Jan 01 00:01:14 5 17 0 find_bus 0
Jan 01 00:01:14 5 17 0 Port Request Start f0000000 - End f0800000 - Size = 256
Jan 01 00:01:14 5 17 0 Address = f07fff00 - End f07fffff
Jan 01 00:01:14 5 17 0 Alloc IRQ 97 - Flags c01
Jan 01 00:01:14 6 10 0 i82544_create_instance
Jan 01 00:01:14 6 10 0 i82544_create_instance1
Jan 01 00:01:14 5 17 0 in temp fix, i= 4, device_enabled = 0, show_pci = 0, next_attach = 0, Bus=0x0 Devfunc=0x41
Jan 01 00:01:14 5 17 0 find_bus 0
Jan 01 00:01:14 5 17 0 Port Request Start f0000000 - End f0800000 - Size = 256
Jan 01 00:01:14 5 17 0 Address = f07ffe00 - End f07ffeff
Jan 01 00:01:14 5 17 0 Alloc IRQ 98 - Flags c01
Jan 01 00:01:14 6 10 0 i82544_create_instance
Jan 01 00:01:14 6 10 0 i82544_create_instance1
----- Original Message -----
From: "Hugh Brown" <community-noreply@qnx.com>
To: "drivers-networking" <post89693@community.qnx.com>
Sent: Thursday, October 27, 2011 10:59:30 AM
Subject: Re: devn-i82544 hang
That is still PCI server output. Are you starting this manually or in the
boot script? If in the boot script, allow some time for sloginfo to output
its data before starting io-net.
--
Hugh Brown
QNX Software Systems Limited
175 Terence Matthews Crescent,
Ottawa. ON. K2M 1W8.
Telephone: 613-591-0931
On 11-10-27 11:55 AM, "Joe Krachey" <community-noreply@qnx.com> wrote:
># sloginfo -w & io-net -de1000 -vvvv
>[2] 20492
>Time Sev Major Minor Args
>Jan 01 00:00:00 5 17 0 pci_server: Oct 25 2011 09:28:32
>Jan 01 00:00:00 5 17 0 Low memory CPU a0000000 - PCI a0000000
># Jan 01 00:00:00 5 17 0 High memory CPU bfffffff - PCI c0000000
>Jan 01 00:00:00 5 17 0 Low port CPU f0000000 - PCI f0000000
>Jan 01 00:00:00 5 17 0 High port CPU f07fffff - PCI f0800000
>Jan 01 00:00:00 5 17 0 Found host bridge 0 f8
>Jan 01 00:00:00 5 17 0 Configure bridge - bus 0 - devfunc f8
>Jan 01 00:00:00 5 17 0 cb Bus 0 - Devfn f8 - dword ff0000
>Jan 01 00:00:00 5 17 0 find_bus 0
>Jan 01 00:00:00 5 17 0 alloc_bus 0 0
>Jan 01 00:00:00 5 17 0 Bus 0 - Device 31 - Function 0
>Jan 01 00:00:00 5 17 0 Vendor 11ab Device 6485 Index 0 ClassCode 60000
>Jan 01 00:00:00 5 17 0 find_bus 0
>Jan 01 00:00:00 5 17 0 Setup bridge 0 - Lastbus = 0
>Jan 01 00:00:00 5 17 0 Configure bridge - bus 0 - devfunc f9
>Jan 01 00:00:00 5 17 0 cb Bus 0 - Devfn f9 - dword 1ff0000
>Jan 01 00:00:00 5 17 0 find_bus 0
>Jan 01 00:00:00 5 17 0 Bus 0 - Device 31
><hangs here>
>
>
>
>
>_______________________________________________
>
>Networking Drivers
>http://community.qnx.com/sf/go/post89692
>
_______________________________________________
Networking Drivers
http://community.qnx.com/sf/go/post89693
|
|
|
|
|
|
Hugh Brown
10/27/2011 12:30 PM
post89698
|
It appears that there is something wrong on the PCI bus, as the driver is
trying to start 2 instances of itself on the same device. I think that the
command line option is '-i0' to only start the first instance of the
driver.
--
Hugh Brown
QNX Software Systems Limited
175 Terence Matthews Crescent,
Ottawa. ON. K2M 1W8.
Telephone: 613-591-0931
On 11-10-27 12:04 PM, "Joe Krachey" <community-noreply@qnx.com> wrote:
>Manually.
>
># io-net -de1000 -vvvv
># Jan 01 00:01:14 5 17 0 io_open for id = 3
>Jan 01 00:01:14 5 17 0 in temp fix, i= 4, device_enabled = 0, show_pci =
>0, next_attach = 0, Bus=0x0 Devfunc=0x40
>
>Jan 01 00:01:14 5 17 0 find_bus 0
>Jan 01 00:01:14 5 17 0 Port Request Start f0000000 - End f0800000 - Size
>= 256
>Jan 01 00:01:14 5 17 0 Address = f07fff00 - End f07fffff
>Jan 01 00:01:14 5 17 0 Alloc IRQ 97 - Flags c01
>Jan 01 00:01:14 6 10 0 i82544_create_instance
>Jan 01 00:01:14 6 10 0 i82544_create_instance1
>Jan 01 00:01:14 5 17 0 in temp fix, i= 4, device_enabled = 0, show_pci =
>0, next_attach = 0, Bus=0x0 Devfunc=0x41
>
>Jan 01 00:01:14 5 17 0 find_bus 0
>Jan 01 00:01:14 5 17 0 Port Request Start f0000000 - End f0800000 - Size
>= 256
>Jan 01 00:01:14 5 17 0 Address = f07ffe00 - End f07ffeff
>Jan 01 00:01:14 5 17 0 Alloc IRQ 98 - Flags c01
>Jan 01 00:01:14 6 10 0 i82544_create_instance
>Jan 01 00:01:14 6 10 0 i82544_create_instance1
>
>
>----- Original Message -----
>
>From: "Hugh Brown" <community-noreply@qnx.com>
>To: "drivers-networking" <post89693@community.qnx.com>
>Sent: Thursday, October 27, 2011 10:59:30 AM
>Subject: Re: devn-i82544 hang
>
>That is still PCI server output. Are you starting this manually or in the
>boot script? If in the boot script, allow some time for sloginfo to
>output
>its data before starting io-net.
>
>--
>Hugh Brown
>QNX Software Systems Limited
>175 Terence Matthews Crescent,
>Ottawa. ON. K2M 1W8.
>Telephone: 613-591-0931
>
>
>
>
>
>
>
>On 11-10-27 11:55 AM, "Joe Krachey" <community-noreply@qnx.com> wrote:
>
>># sloginfo -w & io-net -de1000 -vvvv
>>[2] 20492
>>Time Sev Major Minor Args
>>Jan 01 00:00:00 5 17 0 pci_server: Oct 25 2011 09:28:32
>>Jan 01 00:00:00 5 17 0 Low memory CPU a0000000 - PCI a0000000
>># Jan 01 00:00:00 5 17 0 High memory CPU bfffffff - PCI c0000000
>>Jan 01 00:00:00 5 17 0 Low port CPU f0000000 - PCI f0000000
>>Jan 01 00:00:00 5 17 0 High port CPU f07fffff - PCI f0800000
>>Jan 01 00:00:00 5 17 0 Found host bridge 0 f8
>>Jan 01 00:00:00 5 17 0 Configure bridge - bus 0 - devfunc f8
>>Jan 01 00:00:00 5 17 0 cb Bus 0 - Devfn f8 - dword ff0000
>>Jan 01 00:00:00 5 17 0 find_bus 0
>>Jan 01 00:00:00 5 17 0 alloc_bus 0 0
>>Jan 01 00:00:00 5 17 0 Bus 0 - Device 31 - Function 0
>>Jan 01 00:00:00 5 17 0 Vendor 11ab Device 6485 Index 0 ClassCode 60000
>>Jan 01 00:00:00 5 17 0 find_bus 0
>>Jan 01 00:00:00 5 17 0 Setup bridge 0 - Lastbus = 0
>>Jan 01 00:00:00 5 17 0 Configure bridge - bus 0 - devfunc f9
>>Jan 01 00:00:00 5 17 0 cb Bus 0 - Devfn f9 - dword 1ff0000
>>Jan 01 00:00:00 5 17 0 find_bus 0
>>Jan 01 00:00:00 5 17 0 Bus 0 - Device 31
>><hangs here>
>>
>>
>>
>>
>>_______________________________________________
>>
>>Networking Drivers
>>http://community.qnx.com/sf/go/post89692
>>
>
>
>
>
>_______________________________________________
>
>Networking Drivers
>http://community.qnx.com/sf/go/post89693
>
>
>
>
>
>
>_______________________________________________
>
>Networking...
|
|
|
|
|
|
Joe Krachey
10/27/2011 1:09 PM
post89700
|
The -i0 did not work. I think it tries to create two instances of the
driver because the 82546 is a dual port GBE controller.
I'm able to successfully load the e1000 driver if I un-plug the ethernet
cable from the RJ45 Jack. As soon as I plug the ethernet cable in, the
board hangs. The same thing happens with thh i82544 driver. The other
thing to note is that we are using the fiber interfaces on the 82456.
FYI... I'm only in the office on Tuesday/Thursday mornings, so I won't
be able to run any additional tests until next week.
-Joe
On Thursday, October 27, 2011 11:30:24 AM, Hugh Brown wrote:
>
> It appears that there is something wrong on the PCI bus, as the driver is
> trying to start 2 instances of itself on the same device. I think that the
> command line option is '-i0' to only start the first instance of the
> driver.
>
|
|
|
|
|
|
Joe Krachey
11/01/2011 11:13 AM
post89805
|
I confirmed that our card functions correctly using both the e1000 and
i82544 drivers in a different chassis that contains a different network
switch. (Kontron uTCA Chassis)
I've also confirmed that the Linux is able to correctly use the network
interface on the Performance Technologies uTCA Chassis (AMP5070 - the
chassis where QNX hangs). Our card used to function properly until the
network card in the AMP5070 was changed to the broadcom 5396 in the
latest version of this chassis. Since our QNX port does not hang until
I plug the ethernet cable in, I would guess the hang occurs when trying
trying to parse the data packets being received from the ethernet
switch. My guess is that the Broadcom switch is sending data in a
format that the e1000 andn i82544 drivers are not expecting.
Do you have any recommendations for printing out the data packets as
they are received to determine where the driver is dying?
-Joe
On Thursday, October 27, 2011 12:08:35 PM, Joe Krachey wrote:
>
> The -i0 did not work. I think it tries to create two instances of the
> driver because the 82546 is a dual port GBE controller.
>
> I'm able to successfully load the e1000 driver if I un-plug the
> ethernet cable from the RJ45 Jack. As soon as I plug the ethernet
> cable in, the board hangs. The same thing happens with thh i82544
> driver. The other thing to note is that we are using the fiber
> interfaces on the 82456.
>
> FYI... I'm only in the office on Tuesday/Thursday mornings, so I won't
> be able to run any additional tests until next week.
>
> -Joe
>
> On Thursday, October 27, 2011 11:30:24 AM, Hugh Brown wrote:
>>
>>
>> It appears that there is something wrong on the PCI bus, as the
>> driver is
>> trying to start 2 instances of itself on the same device. I think
>> that the
>> command line option is '-i0' to only start the first instance of the
>> driver.
>>
>
>
>
|
|
|
|
|
|
Hugh Brown
11/01/2011 11:24 AM
post89806
|
Are you able to configure the Broadcom switch? It might be that the switch
is sending vlan packets or jumbo frames to the driver.
--
Hugh Brown
QNX Software Systems Limited
175 Terence Matthews Crescent,
Ottawa. ON. K2M 1W8.
Telephone: 613-591-0931
On 11-11-01 11:13 AM, "Joe Krachey" <community-noreply@qnx.com> wrote:
>I confirmed that our card functions correctly using both the e1000 and
>i82544 drivers in a different chassis that contains a different network
>switch. (Kontron uTCA Chassis)
>
>I've also confirmed that the Linux is able to correctly use the network
>interface on the Performance Technologies uTCA Chassis (AMP5070 - the
>chassis where QNX hangs). Our card used to function properly until the
>network card in the AMP5070 was changed to the broadcom 5396 in the
>latest version of this chassis. Since our QNX port does not hang until
>I plug the ethernet cable in, I would guess the hang occurs when trying
>trying to parse the data packets being received from the ethernet
>switch. My guess is that the Broadcom switch is sending data in a
>format that the e1000 andn i82544 drivers are not expecting.
>
>Do you have any recommendations for printing out the data packets as
>they are received to determine where the driver is dying?
>
>-Joe
>
>
>On Thursday, October 27, 2011 12:08:35 PM, Joe Krachey wrote:
>>
>> The -i0 did not work. I think it tries to create two instances of the
>> driver because the 82546 is a dual port GBE controller.
>>
>> I'm able to successfully load the e1000 driver if I un-plug the
>> ethernet cable from the RJ45 Jack. As soon as I plug the ethernet
>> cable in, the board hangs. The same thing happens with thh i82544
>> driver. The other thing to note is that we are using the fiber
>> interfaces on the 82456.
>>
>> FYI... I'm only in the office on Tuesday/Thursday mornings, so I won't
>> be able to run any additional tests until next week.
>>
>> -Joe
>>
>> On Thursday, October 27, 2011 11:30:24 AM, Hugh Brown wrote:
>>>
>>>
>>> It appears that there is something wrong on the PCI bus, as the
>>> driver is
>>> trying to start 2 instances of itself on the same device. I think
>>> that the
>>> command line option is '-i0' to only start the first instance of the
>>> driver.
>>>
>>
>>
>>
>
>
>
>
>
>_______________________________________________
>
>Networking Drivers
>http://community.qnx.com/sf/go/post89805
>
|
|
|
|
|
|
Joe Krachey
11/03/2011 10:23 AM
post89858
|
There are some configuration settings we can change to configure the
switch. we are checking with our customer if they have any
requirements to use VLANs or jumbo frames...
On Tuesday, November 01, 2011 10:24:47 AM, Hugh Brown wrote:
> Are you able to configure the Broadcom switch? It might be that the switch
> is sending vlan packets or jumbo frames to the driver.
>
|
|
|
|
|
|
Joe Krachey
11/11/2011 6:34 PM
post90058
|
Hugh,
We finally were able to get the proper cabling allowing us to configure
the the switch. Jumbo Frames were disabled by default. This made no
difference, the card still hung. The switch is configured so that all
ports are on a single VLAN. How would this make a difference to the
e1000 driver?
Is there a way to provide any extra debugging information for you to
take a look at? We are also open to allowing remote access to the
system if that would help.
-Joe
On 11/1/2011 10:24 AM, Hugh Brown wrote:
> Are you able to configure the Broadcom switch? It might be that the switch
> is sending vlan packets or jumbo frames to the driver.
>
|
|
|
|
|
|
Hugh Brown
11/14/2011 7:49 AM
post90074
|
You said in a previous post that the driver works in a different chassis,
so that is where I would start looking. What are the differences between
the 2 chassis? I am still convinced that this is an interrupt problem.
It isn't much use giving me remote access if the machine hangs when the
driver is started. The fact that the machine doesn't hang when the cable
is removed is because the driver isn't receiving any interrupts. As soon
as you plug the cable in, the driver receives a link interrupt, so that is
why I am saying the the problem is most probably that the driver is
getting an incorrect interrupt assigned to it.
--
Hugh Brown
QNX Software Systems Limited
175 Terence Matthews Crescent,
Ottawa. ON. K2M 1W8.
Telephone: 613-591-0931
On 11-11-11 6:34 PM, "Joe Krachey" <community-noreply@qnx.com> wrote:
>Hugh,
>
>We finally were able to get the proper cabling allowing us to configure
>the the switch. Jumbo Frames were disabled by default. This made no
>difference, the card still hung. The switch is configured so that all
>ports are on a single VLAN. How would this make a difference to the
>e1000 driver?
>
>Is there a way to provide any extra debugging information for you to
>take a look at? We are also open to allowing remote access to the
>system if that would help.
>
>-Joe
>
>On 11/1/2011 10:24 AM, Hugh Brown wrote:
>> Are you able to configure the Broadcom switch? It might be that the
>>switch
>> is sending vlan packets or jumbo frames to the driver.
>>
>
>
>
>
>_______________________________________________
>
>Networking Drivers
>http://community.qnx.com/sf/go/post90058
>
|
|
|
|
|
|
