Network interface problem

Network interface problem

[Tvrtko A. Uršulin]

More problems:

My server has onboard tg3, and additional 3c905 network card. While booting 
xen outputs: 

3c59x: Donald Becker and others. www.scyld.com/network/vortex.html
00:06.0: 3Com PCI 3c905C Tornado at 0xd400. Vers LK1.1.16
tg3.c:v2.3 (November 5, 2003)
tg3: Could not obtain valid ethernet address, aborting.

And 3c905 becomes eth0 while tg3 is unavailable. What am I doing wrong?


-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn

Re: Network interface problem

[Rolf Neugebauer]

At the moment you can only have one active ethernet card.

you can selected the card you'd like xen to use with:
ifname=eth*
in the kernel command line under grub

For example I use a 3c905 for grub netbooting and then a tg3 for Xen.
works fine.

Rolf

On Wed, 2004-02-11 at 10:05, Tvrtko A. Uršulin wrote:
> More problems:
> 
> My server has onboard tg3, and additional 3c905 network card. While booting 
> xen outputs: 
> 
> 3c59x: Donald Becker and others. www.scyld.com/network/vortex.html
> 00:06.0: 3Com PCI 3c905C Tornado at 0xd400. Vers LK1.1.16
> tg3.c:v2.3 (November 5, 2003)
> tg3: Could not obtain valid ethernet address, aborting.
> 
> And 3c905 becomes eth0 while tg3 is unavailable. What am I doing wrong?
> 
> 
> -------------------------------------------------------
> The SF.Net email is sponsored by EclipseCon 2004
> Premiere Conference on Open Tools Development and Integration
> See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
> http://www.eclipsecon.org/osdn
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/xen-devel



-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn

Re: Network interface problem

[Keir Fraser]

> 
> More problems:
> 
> My server has onboard tg3, and additional 3c905 network card. While booting 
> xen outputs: 
> 
> 3c59x: Donald Becker and others. www.scyld.com/network/vortex.html
> 00:06.0: 3Com PCI 3c905C Tornado at 0xd400. Vers LK1.1.16
> tg3.c:v2.3 (November 5, 2003)
> tg3: Could not obtain valid ethernet address, aborting.
> 
> And 3c905 becomes eth0 while tg3 is unavailable. What am I doing wrong?

Does normal Linux 2.4.24 boot okay?

If not, it's a driver problem.

If it does, please send us the boot output from Xen and from normal
Linux 2.4.24.

 -- Keir


-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn

Re: Network interface problem

[Tvrtko A. Uršulin]

On Wednesday 11 February 2004 11:15, Keir Fraser wrote:
> > More problems:
> >
> > My server has onboard tg3, and additional 3c905 network card. While
> > booting xen outputs:
> >
> > 3c59x: Donald Becker and others. www.scyld.com/network/vortex.html
> > 00:06.0: 3Com PCI 3c905C Tornado at 0xd400. Vers LK1.1.16
> > tg3.c:v2.3 (November 5, 2003)
> > tg3: Could not obtain valid ethernet address, aborting.
> >
> > And 3c905 becomes eth0 while tg3 is unavailable. What am I doing wrong?
>
> Does normal Linux 2.4.24 boot okay?

Yes, both cards working just fine.

> If not, it's a driver problem.

What about that 'only one active ethernet card' Rolf Neugebauer said?

> If it does, please send us the boot output from Xen and from normal
> Linux 2.4.24.

This is from normal linux:

Feb 10 16:08:47 xen kernel: Broadcom Gigabit Ethernet Driver bcm5700 with 
Broadcom NIC Extension (NI
CE) ver. 6.2.17 (07/14/03)
Feb 10 16:08:47 xen kernel: eth0: HP NC7760 Gigabit Server Adapter found at 
mem fe000000, IRQ 12, no
de addr 000802f7c1fa
Feb 10 16:08:47 xen kernel: eth0: Broadcom BCM5703 Integrated Copper 
transceiver found
Feb 10 16:08:47 xen kernel: eth0: Scatter-gather ON, 64-bit DMA ON, Tx 
Checksum ON, Rx Checksum ON,
802.1Q VLAN ON, NAPI ON

And this is Xen:

 __  __            _   ____
 \ \/ /___ _ __   / | |___ \
  \  // _ \ '_ \  | |   __) |
  /  \  __/ | | | | |_ / __/
 /_/\_\___|_| |_| |_(_)_____|

 http://www.cl.cam.ac.uk/netos/xen
 University of Cambridge Computer Laboratory

 Xen version 1.2 (root@local) (gcc version 3.3.1 (SuSE Linux)) Tue Feb 10 
15:544

Initialised all memory on a 1023MB machine
Reading BIOS drive-info tables at 0xfef6f and 0xfef6f
CPU0: Before vendor init, caps: bfebfbff 00000000 00000000, vendor = 0
CPU caps: afebfbff 00000000 00000000 00000000
found SMP MP-table at 000f07b0
Memory Reservation 0xf07b0, 4096 bytes
Memory Reservation 0xf03a0, 4096 bytes
Intel MultiProcessor Specification v1.4
    Virtual Wire compatibility mode.
OEM ID: ASUS     Product ID: PROD00000000 APIC at: 0xFEE00000
Processor #0 Pentium 4(tm) XEON(tm) APIC version 20
I/O APIC #4 Version 17 at 0xFEC00000.
I/O APIC #5 Version 17 at 0xFEC01000.
I/O APIC #6 Version 17 at 0xFEC02000.
Enabling APIC mode: Flat.Using 3 I/O APICs
Processors: 1
Initialising domains
Initialising schedulers
Initializing CPU#0
Detected 2665.961 MHz processor.
CPU0: Before vendor init, caps: bfebfbff 00000000 00000000, vendor = 0
CPU caps: afebfbff 00000000 00000000 00000000
CPU0 booted
enabled ExtINT on CPU#0
ESR value before enabling vector: 00000000
ESR value after enabling vector: 00000000
Error: only one processor found.
ENABLING IO-APIC IRQs
Setting 4 in the phys_id_present_map
...changing IO-APIC physical APIC ID to 4 ... ok.
Setting 5 in the phys_id_present_map
...changing IO-APIC physical APIC ID to 5 ... ok.
Setting 6 in the phys_id_present_map
...changing IO-APIC physical APIC ID to 6 ... ok.
init IO_APIC IRQs
 IO-APIC (apicid-pin) 4-0, 4-3, 4-5, 4-10, 4-12, 5-0, 5-4, 5-6, 5-7, 5-8, 
5-9, .
..TIMER: vector=0x41 pin1=2 pin2=0
..MP-BIOS bug: 8254 timer not connected to IO-APIC
...trying to set up timer (IRQ0) through the 8259A ...
..... (found pin 0) ...works.
number of MP IRQ sources: 16.
number of IO-APIC #4 registers: 16.
number of IO-APIC #5 registers: 16.
number of IO-APIC #6 registers: 16.
testing the IO APIC.......................

IO APIC #4......
.... register #00: 04000000
.......    : physical APIC id: 04
.... register #01: 000F0011
.......     : max redirection entries: 000F
.......     : PRQ implemented: 0
.......     : IO APIC version: 0011
.... register #02: 04000000
.......     : arbitration: 04
.... IRQ redirection table:
 NR Log Phy Mask Trig IRR Pol Stat Dest Deli Vect:
 00 001 01  0    0    0   0   0    1    1    41
 01 0FF 0F  0    0    0   0   0    1    1    49
 02 001 01  1    0    0   0   0    0    0    00
 03 000 00  1    0    0   0   0    0    0    00
 04 0FF 0F  0    0    0   0   0    1    1    51
 05 000 00  1    0    0   0   0    0    0    00
 06 0FF 0F  0    0    0   0   0    1    1    59
 07 0FF 0F  0    0    0   0   0    1    1    61
 08 0FF 0F  0    0    0   0   0    1    1    69
 09 0FF 0F  0    0    0   0   0    1    1    71
 0a 000 00  1    0    0   0   0    0    0    00
 0b 0FF 0F  1    1    0   1   0    1    1    79
 0c 000 00  1    0    0   0   0    0    0    00
 0d 0FF 0F  0    0    0   0   0    1    1    81
 0e 0FF 0F  0    0    0   0   0    1    1    89
 0f 0FF 0F  0    0    0   0   0    1    1    91

IO APIC #5......
.... register #00: 05000000
.......    : physical APIC id: 05
.... register #01: 000F0011
.......     : max redirection entries: 000F
.......     : PRQ implemented: 0
.......     : IO APIC version: 0011
.... register #02: 05000000
.......     : arbitration: 05
.... IRQ redirection table:
 NR Log Phy Mask Trig IRR Pol Stat Dest Deli Vect:
 00 000 00  1    0    0   0   0    0    0    00
 01 0FF 0F  1    1    0   1   0    1    1    99
 02 0FF 0F  1    1    0   1   0    1    1    A1
 03 0FF 0F  1    1    0   1   0    1    1    A9
 04 000 00  1    0    0   0   0    0    0    00
 05 0FF 0F  1    1    0   1   0    1    1    B1
 06 000 00  1    0    0   0   0    0    0    00
 07 000 00  1    0    0   0   0    0    0    00
 08 000 00  1    0    0   0   0    0    0    00
 09 000 00  1    0    0   0   0    0    0    00
 0a 000 00  1    0    0   0   0    0    0    00
 0b 000 00  1    0    0   0   0    0    0    00
 0c 000 00  1    0    0   0   0    0    0    00
 0d 000 00  1    0    0   0   0    0    0    00
 0e 000 00  1    0    0   0   0    0    0    00
 0f 000 00  1    0    0   0   0    0    0    00

IO APIC #6......
.... register #00: 06000000
.......    : physical APIC id: 06
.... register #01: 000F0011
.......     : max redirection entries: 000F
.......     : PRQ implemented: 0
.......     : IO APIC version: 0011
.... register #02: 06000000
.......     : arbitration: 06
.... IRQ redirection table:
 NR Log Phy Mask Trig IRR Pol Stat Dest Deli Vect:
 00 000 00  1    0    0   0   0    0    0    00
 01 000 00  1    0    0   0   0    0    0    00
 02 000 00  1    0    0   0   0    0    0    00
 03 000 00  1    0    0   0   0    0    0    00
 04 000 00  1    0    0   0   0    0    0    00
 05 000 00  1    0    0   0   0    0    0    00
 06 000 00  1    0    0   0   0    0    0    00
 07 000 00  1    0    0   0   0    0    0    00
 08 000 00  1    0    0   0   0    0    0    00
 09 000 00  1    0    0   0   0    0    0    00
 0a 000 00  1    0    0   0   0    0    0    00
 0b 000 00  1    0    0   0   0    0    0    00
 0c 000 00  1    0    0   0   0    0    0    00
 0d 000 00  1    0    0   0   0    0    0    00
 0e 000 00  1    0    0   0   0    0    0    00
 0f 000 00  1    0    0   0   0    0    0    00
IRQ to pin mappings:
IRQ0 -> 0:0
IRQ1 -> 0:1
IRQ4 -> 0:4
IRQ6 -> 0:6
IRQ7 -> 0:7
IRQ8 -> 0:8
IRQ9 -> 0:9
IRQ11 -> 0:11
IRQ13 -> 0:13
IRQ14 -> 0:14
IRQ15 -> 0:15
IRQ17 -> 1:1
IRQ18 -> 1:2
IRQ19 -> 1:3
IRQ21 -> 1:5
.................................... done.
Using local APIC timer interrupts.
Calibrating APIC timer for CPU0...
..... CPU speed is 2666.1900 MHz.
..... Bus speed is 133.3093 MHz.
..... bus_scale = 0x00008883
ACT: Initialising Accurate timers
Time init:
.... System Time: 12098457ns
.... cpu_freq:    00000000:9EE75970
.... scale:       00000001:8019FD56
.... Wall Clock:  1076493384s 0us
Start schedulers
PCI: PCI BIOS revision 2.10 entry at 0xf17b0, last bus=0
PCI: Using configuration type 1
PCI: Probing PCI hardware
PCI: Ignoring BAR0-3 of IDE controller 00:0f.1
PCI: Using IRQ router ServerWorks [1166/0203] at 00:0f.0
PCI->APIC IRQ transform: (B0,I3,P0) -> 18
PCI->APIC IRQ transform: (B0,I4,P0) -> 19
PCI->APIC IRQ transform: (B0,I6,P0) -> 21
PCI->APIC IRQ transform: (B0,I9,P0) -> 17
PCI->APIC IRQ transform: (B0,I15,P0) -> 11
Intel(R) PRO/1000 Network Driver - version 5.2.16
Copyright (c) 1999-2003 Intel Corporation.
3c59x: Donald Becker and others. www.scyld.com/network/vortex.html
00:06.0: 3Com PCI 3c905C Tornado at 0xd400. Vers LK1.1.16
tg3.c:v2.3 (November 5, 2003)
tg3: Could not obtain valid ethernet address, aborting.
Uniform Multi-Platform E-IDE driver Revision: 6.31
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
PCI_IDE: unknown IDE controller on PCI bus 00 device 79, VID=1166, DID=0213
PCI_IDE: chipset revision 160
PCI_IDE: not 100% native mode: will probe irqs later
    ide0: BM-DMA at 0xa400-0xa407, BIOS settings: hda:pio, hdb:pio
    ide1: BM-DMA at 0xa408-0xa40f, BIOS settings: hdc:DMA, hdd:pio
hdc: HL-DT-ST CD-ROM GCR-8482B, ATAPI CD/DVD-ROM drive
ide1 at 0x170-0x177,0x376 on irq 15
hdc: ATAPI 48X CD-ROM drive, 128kB Cache
Uniform CD-ROM driver Revision: 3.12
SCSI subsystem driver Revision: 1.00
Red Hat/Adaptec aacraid driver (1.1.2 Feb 10 2004 15:54:21)
scsi0 : Adaptec AIC7XXX EISA/VLB/PCI SCSI HBA DRIVER, Rev 6.2.8
        <Adaptec (Compaq OEM) 29160 Ultra160 SCSI adapter>
      Vendor: COMPAQ    Model: BD03695CC8        Rev: HPB6
  Type:   Direct-Access                      ANSI SCSI revision: 03
(scsi0:A:0): 160.000MB/s transfers (80.000MHz DT, offset 127, 16bit)
  Vendor: MAXTOR    Model: ATLAS10K4_36WLS   Rev: DFV0
  Type:   Direct-Access                      ANSI SCSI revision: 03
(scsi0:A:1): 160.000MB/s transfers (80.000MHz DT, offset 127, 16bit)
  Vendor: MAXTOR    Model: ATLAS10K4_36WLS   Rev: DFV0
  Type:   Direct-Access                      ANSI SCSI revision: 03
(scsi0:A:2): 160.000MB/s transfers (80.000MHz DT, offset 127, 16bit)
scsi0:A:0:0: Tagged Queuing enabled.  Depth 253
scsi0:A:1:0: Tagged Queuing enabled.  Depth 253
scsi0:A:2:0: Tagged Queuing enabled.  Depth 253
Attached scsi disk sda at scsi0, channel 0, id 0, lun 0
Attached scsi disk sdb at scsi0, channel 0, id 1, lun 0
Attached scsi disk sdc at scsi0, channel 0, id 2, lun 0
SCSI device sda: 71132000 512-byte hdwr sectors (36420 MB)
SCSI device sdb: 71833096 512-byte hdwr sectors (36779 MB)
SCSI device sdc: 71833096 512-byte hdwr sectors (36779 MB)
Device eth0 opened and ready for use.
DOM0: Guest OS virtual load address is c0000000
DOM0: xen_console_init
DOM0: Linux version 2.4.24 (root@xen) (gcc version 3.3.1 (SuSE Linux)) #5 Wed 
F4
DOM0: On node 0 totalpages: 32768
DOM0: zone(0): 4096 pages.
DOM0: zone(1): 28672 pages.
DOM0: zone(2): 0 pages.
DOM0: Kernel command line: (hd0,0)/xenolinux.gz root=/dev/sda3 console=tty0 
con0
DOM0: Initializing CPU#0
DOM0: Xen reported: 2665.961 MHz processor.
DOM0: Console: colour VGA+ 80x25
DOM0: Linux version 2.4.24 (root@xen) (gcc version 3.3.1 (SuSE Linux)) #5 Wed 
F4
DOM0: On node 0 totalpages: 32768
DOM0: zone(0): 4096 pages.
DOM0: zone(1): 28672 pages.
DOM0: zone(2): 0 pages.
DOM0: Kernel command line: (hd0,0)/xenolinux.gz root=/dev/sda3 console=tty0 
con0
DOM0: Initializing CPU#0
DOM0: Xen reported: 2665.961 MHz processor.
DOM0: Console: colour VGA+ 80x25
DOM0: Calibrating delay loop... 30198.98 BogoMIPS
DOM0: Memory: 127860k/131072k available (1098k kernel code, 3212k reserved, 
184)
DOM0: Dentry cache hash table entries: 16384 (order: 5, 131072 bytes)
DOM0: Inode cache hash table entries: 8192 (order: 4, 65536 bytes)
DOM0: Mount cache hash table entries: 512 (order: 0, 4096 bytes)
DOM0: Buffer cache hash table entries: 8192 (order: 3, 32768 bytes)
DOM0: Page-cache hash table entries: 32768 (order: 5, 131072 bytes)
DOM0: CPU: L1 I cache: 12K, L1 D cache: 8K
DOM0: CPU: L2 cache: 512K
DOM0: CPU: Intel(R) Pentium(R) 4 CPU 2.66GHz stepping 09
DOM0: POSIX conformance testing by UNIFIX
DOM0: Linux NET4.0 for Linux 2.4
DOM0: Based upon Swansea University Computer Society NET3.039
DOM0: Initializing RT netlink socket
DOM0: Starting kswapd
DOM0: Journalled Block Device driver loaded
DOM0: Xeno console successfully installed
DOM0: Successfully installed virtual firewall/router interface
DOM0: Starting Xeno Balloon driver
DOM0: pty: 256 Unix98 ptys configured
DOM0: Partition check:
DOM0:  sda: sda1 sda2 sda3 sda4
DOM0:  sdb: unknown partition table
DOM0:  sdc: unknown partition table
DOM0: Skipping partition check on cdrom /dev/hdc
DOM0: NET4: Linux TCP/IP 1.0 for NET4.0
DOM0: IP Protocols: ICMP, UDP, TCP
DOM0: IP: routing cache hash table of 1024 buckets, 8Kbytes
DOM0: TCP: Hash tables configured (established 8192 bind 16384)
DOM0: NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
DOM0: root_device_name = sda3
DOM0: kjournald starting.  Commit interval 5 seconds
DOM0: EXT3 FS 2.4-0.9.19, 19 August 2002 on sd(8,3), internal journal
DOM0: EXT3-fs: mounted filesystem with ordered data mode.
DOM0: VFS: Mounted root (ext3 filesystem).
DOM0: Freeing unused kernel memory: 36k freed
DOM0: INIT: version 2.82 booting
DOM0: System Boot Control: Running /etc/init.d/boot
DOM0: Mounting /proc filesystem7[?25l[80C[10D[1;32mdone[m8[?25h
DOM0: Mounting /dev/pts7[?25l[80C[10D[1;32mdone[m8[?25h
DOM0: [m[?25hmodprobe: modprobe: Can't open dependencies 
file /lib/modules/2.4.)
DOM0: [m[?25hshowconsole: Warning: the ioctl TIOCGDEV is not known by the 
kernel
DOM0: /etc/init.d/boot.d/S04boot.lvm: line 28: [: =: unary operator expected
DOM0: [m[?25hActivating swap-devices in /etc/fstab...
DOM0: Adding Swap: 530136k swap-space (priority 42)
DOM0: 7[?25l[1A[80C[10D[1;32mdone[m8[?25hshowconsole: Warning: the ioctl 
TIOCGDl
DOM0: /etc/init.d/boot.d/S05boot.localfs: line 58: [: =: unary operator 
expected
DOM0: Checking file systems...
DOM0: fsck 1.34 (25-Jul-2003)
DOM0: /dev/sda3: clean, 57725/788704 files, 218574/1574370 blocks
DOM0: /dev/sda1: clean, 40/10040 files, 11124/40128 blocks
DOM0: 7[?25l[1A[80C[10D[1;32mdone[m8[?25hEXT3 FS 2.4-0.9.19, 19 August 2002 on 
l
DOM0: Setting up /lib/modules/2.4.247[?25l[80C[10D[1;32mdone[m8[?25h
DOM0: Mounting local file systems...
DOM0: proc on /proc type proc (rw)
DOM0: devpts on /dev/pts type devpts (rw,mode=0620,gid=5)



-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn

Re: Network interface problem

[Keir Fraser]

> This is from normal linux:
> 
> Feb 10 16:08:47 xen kernel: Broadcom Gigabit Ethernet Driver bcm5700 with 
> Broadcom NIC Extension (NI
> CE) ver. 6.2.17 (07/14/03)
> Feb 10 16:08:47 xen kernel: eth0: HP NC7760 Gigabit Server Adapter found at 
> mem fe000000, IRQ 12, no
> de addr 000802f7c1fa
> Feb 10 16:08:47 xen kernel: eth0: Broadcom BCM5703 Integrated Copper 
> transceiver found
> Feb 10 16:08:47 xen kernel: eth0: Scatter-gather ON, 64-bit DMA ON, Tx 
> Checksum ON, Rx Checksum ON,
> 802.1Q VLAN ON, NAPI ON

This isn't output from the standard Linux tg3 driver, which is what
Xen uses. In fact, I don't think this driver is included in Linux
2.4.24. Are you runnign a different Linux version, or did you install
this driver from another source?

 -- Keir


-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn

Re: Network interface problem

[Rolf Neugebauer]

On Wed, 2004-02-11 at 10:34, Tvrtko A. Uršulin wrote:
> On Wednesday 11 February 2004 11:15, Keir Fraser wrote:
> > > More problems:
> > >
> > > My server has onboard tg3, and additional 3c905 network card. While
> > > booting xen outputs:
> > >
> > > 3c59x: Donald Becker and others. www.scyld.com/network/vortex.html
> > > 00:06.0: 3Com PCI 3c905C Tornado at 0xd400. Vers LK1.1.16
> > > tg3.c:v2.3 (November 5, 2003)
> > > tg3: Could not obtain valid ethernet address, aborting.
> > >
> > > And 3c905 becomes eth0 while tg3 is unavailable. What am I doing wrong?
> >
> > Does normal Linux 2.4.24 boot okay?
> 
> Yes, both cards working just fine.
> 
> > If not, it's a driver problem.
> 
> What about that 'only one active ethernet card' Rolf Neugebauer said?

I don't think this is a problem. As keir pointed out there appears to be
a driver problem. 

My comment was related to selecting which of the _detected_ ethernet
interface xen should use. Xen seem to have a problem with detecting your
tg3 card properly.

Rolf
[this time sending from an email address which is actually subscribed to
the mailing list...]



-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn

Re: Network interface problem

[Tvrtko A. Uršulin]

On Wednesday 11 February 2004 11:43, Keir Fraser wrote:
> > This is from normal linux:
> >
> > Feb 10 16:08:47 xen kernel: Broadcom Gigabit Ethernet Driver bcm5700 with
> > Broadcom NIC Extension (NI
> > CE) ver. 6.2.17 (07/14/03)
> > Feb 10 16:08:47 xen kernel: eth0: HP NC7760 Gigabit Server Adapter found
> > at mem fe000000, IRQ 12, no
> > de addr 000802f7c1fa
> > Feb 10 16:08:47 xen kernel: eth0: Broadcom BCM5703 Integrated Copper
> > transceiver found
> > Feb 10 16:08:47 xen kernel: eth0: Scatter-gather ON, 64-bit DMA ON, Tx
> > Checksum ON, Rx Checksum ON,
> > 802.1Q VLAN ON, NAPI ON
>
> This isn't output from the standard Linux tg3 driver, which is what
> Xen uses. In fact, I don't think this driver is included in Linux
> 2.4.24. Are you runnign a different Linux version, or did you install
> this driver from another source?

Yes, you are right. :) This is the output for 2.4.21-SuSE kernel. But 
previously, on the same server I was running vanilla 2.4.24 (+ grsec) and I 
am 100% sure both cards were operational because they were heavily used. 
Because I made a clean install for the purpose of trying Xen, I have never 
bothered to compile own kernel because it is not needed. 

If you need the actual output I can compile the kernel and provide it. But if 
you only need the proof that both cards are working can you trust my word for 
it?


-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn

Re: Network interface problem

[Keir Fraser]

> Yes, you are right. :) This is the output for 2.4.21-SuSE kernel. But 
> previously, on the same server I was running vanilla 2.4.24 (+ grsec) and I 
> am 100% sure both cards were operational because they were heavily used. 
> Because I made a clean install for the purpose of trying Xen, I have never 
> bothered to compile own kernel because it is not needed. 
> 
> If you need the actual output I can compile the kernel and provide it. But if 
> you only need the proof that both cards are working can you trust my word for 
> it?

In fact I will need the _full_ boot-time output both from Xen and from
normal vanilla Linux 2.4.24 (not a vendor kernel!). 

Even if this weren't the case, I've quickly learned never to trust a
bug report until I've personally eyeballed it. ;-)

 -- Keir


-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn

Re: Network interface problem

[Tvrtko A. Uršulin]

On Wednesday 11 February 2004 12:01, Keir Fraser wrote:

> In fact I will need the _full_ boot-time output both from Xen and from
> normal vanilla Linux 2.4.24 (not a vendor kernel!).
>
> Even if this weren't the case, I've quickly learned never to trust a
> bug report until I've personally eyeballed it. ;-)

That is a smart policy. I am sorry I tried to convince you to trust me. :) It 
seems that tg3 issue really isn't related to Xen. It really doesn't work 
under vanilla 2.4.24 with:

tg3.c:v2.3 (November 5, 2003)
tg3: Could not obtain valid ethernet address, aborting.

While under 2.4.24-grsec it does:

tg3.c:v2.3 (November 5, 2003)
eth0: Tigon3 [partno(BCM95702A20) rev 1002 PHY(5703)] (PCI:33MHz:32-bit) 
10/100/1000BaseT Ethernet 00:08:02:f7:c1:fa
tg3: eth0: Link is up at 100 Mbps, full duplex.
tg3: eth0: Flow control is off for TX and off for RX.

That is really strange and I will post it to LKML and grsec MLs. Complete 
kernel logs differ only in kernel memory usage and cpu speed calculation.

So it seems that I have never tried 2.4.24 vanilla before, only thought that I 
did. :)


-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn

Re: Network interface problem

[Keir Fraser]

> That is a smart policy. I am sorry I tried to convince you to trust me. :) It 
> seems that tg3 issue really isn't related to Xen. It really doesn't work 
> under vanilla 2.4.24 with:
> 
> tg3.c:v2.3 (November 5, 2003)
> tg3: Could not obtain valid ethernet address, aborting.
> 
> While under 2.4.24-grsec it does:
> 
> tg3.c:v2.3 (November 5, 2003)
> eth0: Tigon3 [partno(BCM95702A20) rev 1002 PHY(5703)] (PCI:33MHz:32-bit) 
> 10/100/1000BaseT Ethernet 00:08:02:f7:c1:fa
> tg3: eth0: Link is up at 100 Mbps, full duplex.
> tg3: eth0: Flow control is off for TX and off for RX.
> 
> That is really strange and I will post it to LKML and grsec MLs. Complete 
> kernel logs differ only in kernel memory usage and cpu speed calculation.
> 
> So it seems that I have never tried 2.4.24 vanilla before, only thought that I 
> did. :)

It may be that their kernel has a more up-to-date tg3 driver (i.e.,
newer than version v2.3 committed on Nov 5, 2003).

 -- Keir


-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn

Re: Network interface problem

[Tvrtko A. Uršulin]

On Wednesday 11 February 2004 12:57, Keir Fraser wrote:

> It may be that their kernel has a more up-to-date tg3 driver (i.e.,
> newer than version v2.3 committed on Nov 5, 2003).

Nope, they do not touch that part of kernel, and besides, the log says it is 
the same version.

However, while trying to catch that mmu failure from previous email I booted 
to Xen compiled without -DNDEBUG. 

tg3 now works!?!? Log follows...

[root@homer root]# cat minicom.cap
 __  __            _   ____
 \ \/ /___ _ __   / | |___ \
  \  // _ \ '_ \  | |   __) |
  /  \  __/ | | | | |_ / __/
 /_/\_\___|_| |_| |_(_)_____|

 http://www.cl.cam.ac.uk/netos/xen
 University of Cambridge Computer Laboratory

 Xen version 1.2 (root@local) (gcc version 3.3.1 (SuSE Linux)) Wed Feb 11 
13:01:55 CET 2004

Initialised all memory on a 1023MB machine
Reading BIOS drive-info tables at 0xfef6f and 0xfef6f
CPU0: Before vendor init, caps: bfebfbff 00000000 00000000, vendor = 0
CPU caps: afebfbff 00000000 00000000 00000000
found SMP MP-table at 000f07b0
Memory Reservation 0xf07b0, 4096 bytes
Memory Reservation 0xf03a0, 4096 bytes
Intel MultiProcessor Specification v1.4
    Virtual Wire compatibility mode.
OEM ID: ASUS     Product ID: PROD00000000 APIC at: 0xFEE00000
Processor #0 Pentium 4(tm) XEON(tm) APIC version 20
I/O APIC #4 Version 17 at 0xFEC00000.
I/O APIC #5 Version 17 at 0xFEC01000.
I/O APIC #6 Version 17 at 0xFEC02000.
Enabling APIC mode: Flat.Using 3 I/O APICs
Processors: 1
Initialising domains
Initialising schedulers
Initializing CPU#0
Detected 2666.051 MHz processor.
CPU0: Before vendor init, caps: bfebfbff 00000000 00000000, vendor = 0
CPU caps: afebfbff 00000000 00000000 00000000
CPU0 booted
enabled ExtINT on CPU#0
ESR value before enabling vector: 00000000
ESR value after enabling vector: 00000000
Error: only one processor found.
ENABLING IO-APIC IRQs
Setting 4 in the phys_id_present_map
...changing IO-APIC physical APIC ID to 4 ... ok.
Setting 5 in the phys_id_present_map
...changing IO-APIC physical APIC ID to 5 ... ok.
Setting 6 in the phys_id_present_map
...changing IO-APIC physical APIC ID to 6 ... ok.
init IO_APIC IRQs
 IO-APIC (apicid-pin) 4-0, 4-3, 4-5, 4-10, 4-12, 5-0, 5-4, 5-6, 5-7, 5-8, 5-9, 
5-10, 5-11, 5-12, 5-13, 5-14, 5-15, 6-0, 6-1, 6-2, 6-3, 6-4, 6-5, 6-6, 6-7, 
6-8, 6-9, 6-10, 6-11, 6-12, 6-13, 6-14, 6-15 not connected.
..TIMER: vector=0x41 pin1=2 pin2=0
..MP-BIOS bug: 8254 timer not connected to IO-APIC
...trying to set up timer (IRQ0) through the 8259A ...
..... (found pin 0) ...works.
number of MP IRQ sources: 16.
number of IO-APIC #4 registers: 16.
number of IO-APIC #5 registers: 16.
number of IO-APIC #6 registers: 16.
testing the IO APIC.......................

IO APIC #4......
.... register #00: 04000000
.......    : physical APIC id: 04
.... register #01: 000F0011
.......     : max redirection entries: 000F
.......     : PRQ implemented: 0
.......     : IO APIC version: 0011
.... register #02: 04000000
.......     : arbitration: 04
.... IRQ redirection table:
 NR Log Phy Mask Trig IRR Pol Stat Dest Deli Vect:
 00 001 01  0    0    0   0   0    1    1    41
 01 0FF 0F  0    0    0   0   0    1    1    49
 02 001 01  1    0    0   0   0    0    0    00
 03 000 00  1    0    0   0   0    0    0    00
 04 0FF 0F  0    0    0   0   0    1    1    51
 05 000 00  1    0    0   0   0    0    0    00
 06 0FF 0F  0    0    0   0   0    1    1    59
 07 0FF 0F  0    0    0   0   0    1    1    61
 08 0FF 0F  0    0    0   0   0    1    1    69
 09 0FF 0F  0    0    0   0   0    1    1    71
 0a 000 00  1    0    0   0   0    0    0    00
 0b 0FF 0F  1    1    0   1   0    1    1    79
 0c 000 00  1    0    0   0   0    0    0    00
 0d 0FF 0F  0    0    0   0   0    1    1    81
 0e 0FF 0F  0    0    0   0   0    1    1    89
 0f 0FF 0F  0    0    0   0   0    1    1    91

IO APIC #5......
.... register #00: 05000000
.......    : physical APIC id: 05
.... register #01: 000F0011
.......     : max redirection entries: 000F
.......     : PRQ implemented: 0
.......     : IO APIC version: 0011
.... register #02: 05000000
.......     : arbitration: 05
.... IRQ redirection table:
 NR Log Phy Mask Trig IRR Pol Stat Dest Deli Vect:
 00 000 00  1    0    0   0   0    0    0    00
 01 0FF 0F  1    1    0   1   0    1    1    99
 02 0FF 0F  1    1    0   1   0    1    1    A1
 03 0FF 0F  1    1    0   1   0    1    1    A9
 04 000 00  1    0    0   0   0    0    0    00
 05 0FF 0F  1    1    0   1   0    1    1    B1
 06 000 00  1    0    0   0   0    0    0    00
 07 000 00  1    0    0   0   0    0    0    00
 08 000 00  1    0    0   0   0    0    0    00
 09 000 00  1    0    0   0   0    0    0    00
 0a 000 00  1    0    0   0   0    0    0    00
 0b 000 00  1    0    0   0   0    0    0    00
 0c 000 00  1    0    0   0   0    0    0    00
 0d 000 00  1    0    0   0   0    0    0    00
 0e 000 00  1    0    0   0   0    0    0    00
 0f 000 00  1    0    0   0   0    0    0    00

IO APIC #6......
.... register #00: 06000000
.......    : physical APIC id: 06
.... register #01: 000F0011
.......     : max redirection entries: 000F
.......     : PRQ implemented: 0
.......     : IO APIC version: 0011
.... register #02: 06000000
.......     : arbitration: 06
.... IRQ redirection table:
 NR Log Phy Mask Trig IRR Pol Stat Dest Deli Vect:
 00 000 00  1    0    0   0   0    0    0    00
 01 000 00  1    0    0   0   0    0    0    00
 02 000 00  1    0    0   0   0    0    0    00
 03 000 00  1    0    0   0   0    0    0    00
 04 000 00  1    0    0   0   0    0    0    00
 05 000 00  1    0    0   0   0    0    0    00
 06 000 00  1    0    0   0   0    0    0    00
 07 000 00  1    0    0   0   0    0    0    00
 08 000 00  1    0    0   0   0    0    0    00
 09 000 00  1    0    0   0   0    0    0    00
 0a 000 00  1    0    0   0   0    0    0    00
 0b 000 00  1    0    0   0   0    0    0    00
 0c 000 00  1    0    0   0   0    0    0    00
 0d 000 00  1    0    0   0   0    0    0    00
 0e 000 00  1    0    0   0   0    0    0    00
 0f 000 00  1    0    0   0   0    0    0    00
IRQ to pin mappings:
IRQ0 -> 0:0
IRQ1 -> 0:1
IRQ4 -> 0:4
IRQ6 -> 0:6
IRQ7 -> 0:7
IRQ8 -> 0:8
IRQ9 -> 0:9
IRQ11 -> 0:11
IRQ13 -> 0:13
IRQ14 -> 0:14
IRQ15 -> 0:15
IRQ17 -> 1:1
IRQ18 -> 1:2
IRQ19 -> 1:3
IRQ21 -> 1:5
.................................... done.
Using local APIC timer interrupts.
Calibrating APIC timer for CPU0...
..... CPU speed is 2666.1899 MHz.
..... Bus speed is 133.3094 MHz.
..... bus_scale = 0x00008883
ACT: Initialising Accurate timers
Time init:
.... System Time: 12095965ns
.... cpu_freq:    00000000:9EE8B810
.... scale:       00000001:8016ADD6
.... Wall Clock:  1076501066s 0us
Start schedulers
PCI: PCI BIOS revision 2.10 entry at 0xf17b0, last bus=0
PCI: Using configuration type 1
PCI: Probing PCI hardware
PCI: Ignoring BAR0-3 of IDE controller 00:0f.1
PCI: Using IRQ router ServerWorks [1166/0203] at 00:0f.0
PCI->APIC IRQ transform: (B0,I3,P0) -> 18
PCI->APIC IRQ transform: (B0,I4,P0) -> 19
PCI->APIC IRQ transform: (B0,I6,P0) -> 21
PCI->APIC IRQ transform: (B0,I9,P0) -> 17
PCI->APIC IRQ transform: (B0,I15,P0) -> 11
Intel(R) PRO/1000 Network Driver - version 5.2.16
Copyright (c) 1999-2003 Intel Corporation.
3c59x: Donald Becker and others. www.scyld.com/network/vortex.html
00:06.0: 3Com PCI 3c905C Tornado at 0xd400. Vers LK1.1.16
tg3.c:v2.3 (November 5, 2003)
eth1: Tigon3 [partno(BCM95702A20) rev 1002 PHY(5703)] (PCI:33MHz:32-bit) 
10/100/1000BaseT Ethernet 00:08:02:f7:c1:fa
Uniform Multi-Platform E-IDE driver Revision: 6.31
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
PCI_IDE: unknown IDE controller on PCI bus 00 device 79, VID=1166, DID=0213
PCI_IDE: chipset revision 160
PCI_IDE: not 100% native mode: will probe irqs later
    ide0: BM-DMA at 0xa400-0xa407, BIOS settings: hda:pio, hdb:pio
    ide1: BM-DMA at 0xa408-0xa40f, BIOS settings: hdc:DMA, hdd:pio
hdc: HL-DT-ST CD-ROM GCR-8482B, ATAPI CD/DVD-ROM drive
ide1 at 0x170-0x177,0x376 on irq 15
hdc: ATAPI 48X CD-ROM drive, 128kB Cache
Uniform CD-ROM driver Revision: 3.12
SCSI subsystem driver Revision: 1.00
Red Hat/Adaptec aacraid driver (1.1.2 Feb 11 2004 13:01:19)
scsi0 : Adaptec AIC7XXX EISA/VLB/PCI SCSI HBA DRIVER, Rev 6.2.8
        <Adaptec (Compaq OEM) 29160 Ultra160 SCSI adapter>
      Vendor: COMPAQ    Model: BD03695CC8        Rev: HPB6
  Type:   Direct-Access                      ANSI SCSI revision: 03
(scsi0:A:0): 160.000MB/s transfers (80.000MHz DT, offset 127, 16bit)
  Vendor: MAXTOR    Model: ATLAS10K4_36WLS   Rev: DFV0
  Type:   Direct-Access                      ANSI SCSI revision: 03
(scsi0:A:1): 160.000MB/s transfers (80.000MHz DT, offset 127, 16bit)
  Vendor: MAXTOR    Model: ATLAS10K4_36WLS   Rev: DFV0
  Type:   Direct-Access                      ANSI SCSI revision: 03
(scsi0:A:2): 160.000MB/s transfers (80.000MHz DT, offset 127, 16bit)
scsi0:A:0:0: Tagged Queuing enabled.  Depth 253
scsi0:A:1:0: Tagged Queuing enabled.  Depth 253
scsi0:A:2:0: Tagged Queuing enabled.  Depth 253
Attached scsi disk sda at scsi0, channel 0, id 0, lun 0
Attached scsi disk sdb at scsi0, channel 0, id 1, lun 0
Attached scsi disk sdc at scsi0, channel 0, id 2, lun 0
SCSI device sda: 71132000 512-byte hdwr sectors (36420 MB)
SCSI device sdb: 71833096 512-byte hdwr sectors (36779 MB)
SCSI device sdc: 71833096 512-byte hdwr sectors (36779 MB)
Device eth0 opened and ready for use.
DOM0: Guest OS virtual load address is c0000000
DOM0: xen_console_init
DOM0: Linux version 2.4.24-xeno (root@xen) (gcc version 3.3.1 (SuSE Linux)) #6 
Wed Feb 11 12:51:35 CET 2004
DOM0: On node 0 totalpages: 32768
DOM0: zone(0): 4096 pages.
DOM0: zone(1): 28672 pages.
DOM0: zone(2): 0 pages.
DOM0: Kernel command line: (hd0,0)/xenolinux.gz root=/dev/sda3 console=tty0 
console=xencons0
DOM0: Initializing CPU#0
DOM0: Xen reported: 2666.051 MHz processor.
DOM0: Console: colour VGA+ 80x25
DOM0: Linux version 2.4.24-xeno (root@xen) (gcc version 3.3.1 (SuSE Linux)) #6 
Wed Feb 11 12:51:35 CET 2004
DOM0: On node 0 totalpages: 32768
DOM0: zone(0): 4096 pages.
DOM0: zone(1): 28672 pages.
DOM0: zone(2): 0 pages.
DOM0: Kernel command line: (hd0,0)/xenolinux.gz root=/dev/sda3 console=tty0 
console=xencons0
DOM0: Initializing CPU#0
DOM0: Xen reported: 2666.051 MHz processor.
DOM0: Console: colour VGA+ 80x25
DOM0: Calibrating delay loop... 23540.53 BogoMIPS
DOM0: Memory: 127860k/131072k available (1098k kernel code, 3212k reserved, 
184k data, 36k init, 0k highmem)
DOM0: Dentry cache hash table entries: 16384 (order: 5, 131072 bytes)
DOM0: Inode cache hash table entries: 8192 (order: 4, 65536 bytes)
DOM0: Mount cache hash table entries: 512 (order: 0, 4096 bytes)
DOM0: Buffer cache hash table entries: 8192 (order: 3, 32768 bytes)
DOM0: Page-cache hash table entries: 32768 (order: 5, 131072 bytes)
DOM0: CPU: L1 I cache: 12K, L1 D cache: 8K
DOM0: CPU: L2 cache: 512K
DOM0: CPU: Intel(R) Pentium(R) 4 CPU 2.66GHz stepping 09
DOM0: POSIX conformance testing by UNIFIX
DOM0: Linux NET4.0 for Linux 2.4
DOM0: Based upon Swansea University Computer Society NET3.039
DOM0: Initializing RT netlink socket
DOM0: Starting kswapd
DOM0: Journalled Block Device driver loaded
DOM0: Xeno console successfully installed
DOM0: Successfully installed virtual firewall/router interface
DOM0: Starting Xeno Balloon driver
DOM0: pty: 256 Unix98 ptys configured
DOM0: Partition check:
DOM0:  sda: sda1 sda2 sda3 sda4
DOM0:  sdb: sdb1
DOM0:  sdc: unknown partition table
DOM0: Skipping partition check on cdrom /dev/hdc
DOM0: NET4: Linux TCP/IP 1.0 for NET4.0
DOM0: IP Protocols: ICMP, UDP, TCP
DOM0: IP: routing cache hash table of 1024 buckets, 8Kbytes
DOM0: TCP: Hash tables configured (established 8192 bind 16384)
DOM0: NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
DOM0: root_device_name = sda3
DOM0: kjournald starting.  Commit interval 5 seconds
DOM0: EXT3 FS 2.4-0.9.19, 19 August 2002 on sd(8,3), internal journal
DOM0: EXT3-fs: recovery complete.
DOM0: EXT3-fs: mounted filesystem with ordered data mode.
DOM0: VFS: Mounted root (ext3 filesystem).
DOM0: Freeing unused kernel memory: 36k freed
DOM0: INIT: version 2.82 booting
DOM0: System Boot Control: Running /etc/init.d/boot
DOM0: Mounting /proc filesystem7[?25l[80C[10D[1;32mdone[m8[?25h
DOM0: Mounting /dev/pts7[?25l[80C[10D[1;32mdone[m8[?25h
DOM0: [m[?25hmodprobe: modprobe: Can't locate module block-major-9
DOM0: [m[?25hshowconsole: Warning: the ioctl TIOCGDEV is not known by the 
kernel
DOM0: /etc/init.d/boot.d/S04boot.lvm: line 28: [: =: unary operator expected
DOM0: [m[?25hActivating swap-devices in /etc/fstab...
DOM0: Adding Swap: 530136k swap-space (priority 42)



-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn

Re: Network interface problem

[Ian Pratt]

> It may be that their kernel has a more up-to-date tg3 driver (i.e.,
> newer than version v2.3 committed on Nov 5, 2003).

Indeed.  The stock Linux 2.4.24 driver does not support the
BCM95702.

I expect that it'll get updated in due course, in which case we
can forward port the change to Xen.

There's no sign of it in 2.4.25-rc1

http://linux.bkbits.net:8080/linux-2.4/hist/drivers/net/tg3.c?nav=index.html|src/.|src/drivers|src/drivers/net

I'm loathe to start pulling drivers in from sources other than
the mainline Linux tree as we'll start getting confused about
lineage, which will make future updates harder.

Of course, don't let that stop you ;-)

Best,
Ian


-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn

Re: Network interface problem

[Ian Pratt]

> 
> > It may be that their kernel has a more up-to-date tg3 driver (i.e.,
> > newer than version v2.3 committed on Nov 5, 2003).
> 
> Indeed.  The stock Linux 2.4.24 driver does not support the
> BCM95702.

Please ignore my entire previous email -- I was looking in the list
of PHY pcids not the MAC ones. The BCM95702 is supported in stock
2.4.24 Linux and should work.

The fact that you're having trouble getting it to work with stock
Linux is quite mysterious. 

There doesn't appear to be anything in the changelog to suggest
there's a fix in 2.4.25-rc1 but it might be worth trying.

I'd certainly get it working under Linux before attempting to get
it working under Xen.

Ian
 
> I expect that it'll get updated in due course, in which case we
> can forward port the change to Xen.
> 
> There's no sign of it in 2.4.25-rc1
> 
> http://linux.bkbits.net:8080/linux-2.4/hist/drivers/net/tg3.c?nav=index.html|src/.|src/drivers|src/drivers/net
> 
> I'm loathe to start pulling drivers in from sources other than
> the mainline Linux tree as we'll start getting confused about
> lineage, which will make future updates harder.
> 
> Of course, don't let that stop you ;-)
> 
> Best,
> Ian



-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn

Re: Network interface problem

[Tvrtko A. Uršulin]

On Wednesday 11 February 2004 13:40, Ian Pratt wrote:

> Please ignore my entire previous email -- I was looking in the list
> of PHY pcids not the MAC ones. The BCM95702 is supported in stock
> 2.4.24 Linux and should work.

No problem. :)

> The fact that you're having trouble getting it to work with stock
> Linux is quite mysterious.

More mysterious when you consider that it works with grsecurity patch which 
doesn't touch drivers/net/anything, and even more when you read my post in 
which I wrote that it works under Xen compiled without -DNDEBUG.

I have already informed LKML, GRSEc and LND ML's onm the situation and will 
report here on any conclusions.


-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn

Re: Network interface problem

[Keir Fraser]

> > Please ignore my entire previous email -- I was looking in the list
> > of PHY pcids not the MAC ones. The BCM95702 is supported in stock
> > 2.4.24 Linux and should work.
> 
> No problem. :)
> 
> > The fact that you're having trouble getting it to work with stock
> > Linux is quite mysterious.
> 
> More mysterious when you consider that it works with grsecurity patch which 
> doesn't touch drivers/net/anything, and even more when you read my post in 
> which I wrote that it works under Xen compiled without -DNDEBUG.
> 
> I have already informed LKML, GRSEc and LND ML's onm the situation and will 
> report here on any conclusions.

Use a different GCC -- I think it's a very possible culprit here.

We mostly use GCC 3.2.2 here (since it's what comes with Redhat
9). However GCC 3.3.3 should also work.

 -- Keir


-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn

Re: Network interface problem

[Keir Fraser]

> > > Please ignore my entire previous email -- I was looking in the list
> > > of PHY pcids not the MAC ones. The BCM95702 is supported in stock
> > > 2.4.24 Linux and should work.
> > 
> > No problem. :)
> > 
> > > The fact that you're having trouble getting it to work with stock
> > > Linux is quite mysterious.
> > 
> > More mysterious when you consider that it works with grsecurity patch which 
> > doesn't touch drivers/net/anything, and even more when you read my post in 
> > which I wrote that it works under Xen compiled without -DNDEBUG.
> > 
> > I have already informed LKML, GRSEc and LND ML's onm the situation and will 
> > report here on any conclusions.
> 
> Use a different GCC -- I think it's a very possible culprit here.
> 
> We mostly use GCC 3.2.2 here (since it's what comes with Redhat
> 9). However GCC 3.3.3 should also work.

Another thing to try is downloading our latest build of Xen 1.2 from
the project download page: 
 http://www.cl.cam.ac.uk/Research/SRG/netos/xen/downloads.html

Also, the Linux developers recommend using GCC 2.95.3 for maximum
stability. This is therefore probably a good choice for Xen as well,
although all our testing uses 3.3.2 as shipped with Redhat 9.

 -- Keir


-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn

Re: Network interface problem

[Tvrtko A. Uršulin]

On Wednesday 11 February 2004 14:40, Keir Fraser wrote:

> Use a different GCC -- I think it's a very possible culprit here.
>
> We mostly use GCC 3.2.2 here (since it's what comes with Redhat
> 9). However GCC 3.3.3 should also work.

3.3.1 here. Known problems?


-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn

Re: Network interface problem

[Keir Fraser]

> On Wednesday 11 February 2004 14:40, Keir Fraser wrote:
> 
> > Use a different GCC -- I think it's a very possible culprit here.
> >
> > We mostly use GCC 3.2.2 here (since it's what comes with Redhat
> > 9). However GCC 3.3.3 should also work.
> 
> 3.3.1 here. Known problems?

The only GCC version that many Linux developers will aceept bug
reports from is 2.95.3. Building Linxu with many of the GCC 3.x
compilers is an unknown --- often it works, sometimes it
doesn't. Often this is a lurking kernel bug, but not always.

 -- Keir


-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn

Re: Network interface problem

[stevegt]

On Wed, Feb 11, 2004 at 01:54:56PM +0000, Keir Fraser wrote:
> Also, the Linux developers recommend using GCC 2.95.3 for maximum
> stability. This is therefore probably a good choice for Xen as well,
> although all our testing uses 3.3.2 as shipped with Redhat 9.

I had to stop using 2.95.4 for Xen a few weeks ago, and 3.0.4 last week.
In both cases, they built fine but had runtime errors ranging from
incomplete boot to intermittent instability.

I'm using 3.3.2 on Debian testing (sarge) right now and it seems to work
well -- several guests running on a few hosts since the middle of last
week, some in production.

I'm not sure any gcc < 3.2 is safe for Xen right now.

Steve
-- 
Stephen G. Traugott  (KG6HDQ)
UNIX/Linux Infrastructure Architect, TerraLuna LLC
stevegt@TerraLuna.Org 
http://www.stevegt.com -- http://Infrastructures.Org 


-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click

Re: Network interface problem

[Keir Fraser]

> On Wed, Feb 11, 2004 at 01:54:56PM +0000, Keir Fraser wrote:
> > Also, the Linux developers recommend using GCC 2.95.3 for maximum
> > stability. This is therefore probably a good choice for Xen as well,
> > although all our testing uses 3.3.2 as shipped with Redhat 9.
> 
> I had to stop using 2.95.4 for Xen a few weeks ago, and 3.0.4 last week.
> In both cases, they built fine but had runtime errors ranging from
> incomplete boot to intermittent instability.
> 
> I'm using 3.3.2 on Debian testing (sarge) right now and it seems to work
> well -- several guests running on a few hosts since the middle of last
> week, some in production.
> 
> I'm not sure any gcc < 3.2 is safe for Xen right now.

I made the assembly stubs, that Xenolinux uses to call Xen, more
conservative yesterday (allow GCC fewer optimisations). I'd be
interested to know whether you can still easily trigger crashes by
using one of the 'bad' compilers.

 -- Keir


-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click