[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#369298: Etch upgrade breaks smc-ultra driver on 2.6.15 kernel



Package: linux-image-2.6.15-1-686
Version: 2.6.15-8

	This report is for Etch as of 5/28/2006.
	Etch was installed on 4/15/2006.  It was upgraded around 5/24/2006,
and that appears to have broken the smc-ultra driver.  A number of utilities
and libraries were automatically upgraded at that time.
	This is not the same bug I reported in #362056.  In this new case an
IRQ is available for the ISA-PNP Ethernet board, but the interface fails to
come up for some different reason.

---------------------------------------------------------------------------

	The hardware platform is a triple-homed router/firewall/server,
consisting of:

H-P Vectra VL, Pentium Pro with 128 MB RAM and 80 GB EIDE disk, IDE CD-ROM,
and floppy disk

Two 3C905B PCI UTP Ethernet boards
One SMC-Ultra ISA-PNP Combo AUI/10Base2/UTP board

	One of the 3C905B boards was used to install Debian Etch, and in the
process it was configured as eth0 with DHCP.  Following installation, the
Ethernet boards were configured as follows:


# /etc/modules: kernel modules to load at boot time.
#
# Edited by J. A. Carroll for ulysses.local
# 
# 2006/3/20  Added smc-ultra and 3c509, with a line to force
#            3c59x to load first so that it will always be eth0
# 
# This file should contain the names of kernel modules that are
# to be loaded at boot time, one per line.  Comments begin with
# a "#", and everything on the line after them are ignored.

ide-cd
ide-disk
ide-generic
psmouse

# Local additions for ulysses
3c59x
smc-ultra


	(isapnp doesn't load the smc-ultra driver, so /etc/modules must be
edited to make it load at boot time.  But /etc/modules is read before the
PCI bus is scanned, which would cause the SMC board to become eth0; that
would complicate shorewall configuration and make the SMC unavailable for
the coax subnets.  So 3c59x must be placed before smc-ultra in the file.)


# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).
#
# Edited by J. A. Carroll for ulysses.local
# 2006/3/20  Added eth1 and eth2 stanzas

# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
# Connects to the cable modem or outer firewall
auto eth0
iface eth0 inet dhcp
	hwaddress ether 00:05:02:8E:4F:3A  

# The inner LAN for the upstairs Macintoshes
# DHCP server provided in this interface
auto eth1
iface eth1 inet static
	address 192.168.71.
	netmask 255.255.255.0

# The DMZ or inner LAN for the downstairs hosts
auto eth2
iface eth2 inet static
	address 192.168.136.55
	netmask 255.255.255.0


	(The hwaddress statement is required to spoof the MAC address of a
defunct Macintosh.  All attempts to get the ISP to provision any other MAC
address have proved fruitless.  For this reason, it's not practical to use
factory MAC addresses to force specific eth? names to be assigned to
specific 3C905B boards.)


	These configuration files worked as expected.  The first 3C905B came
up at boot and obtained a DHCP lease, the second came up with static address
192.168.71.1, and the SMC-Ultra came up as 192.168.136.55.  Pings and
everything else worked properly.  Various other services and hacks were
tested, but I didn't get as far as configuring a firewall.

---------------------------------------------------------------------------


	About 5/24/2006 I brought the system up to date with
		aptitude update
		aptitude upgrade

	Following that, the SMC-Ultra board wouldn't come up any more.
Investigation showed that the module didn't load correctly and get assigned
to the interface name eth2.  The error messages:

Script started on Sun 28 May 2006 04:13:55 PM EDT
ulysses:/data/root/scratch# modprobe smc-ultra
ulysses:/data/root/scratch# ifup -a
ifup: interface lo already configured
ifup: interface eth0 already configured
ifup: interface eth1 already configured
SIOCSIFADDR: No such device
eth2: ERROR while getting interface flags: No such device
SIOCSIFNETMASK: No such device
eth2: ERROR while getting interface flags: No such device
Failed to bring up eth2.
ulysses:/data/root/scratch# cat /proc/interrupts
           CPU0       
  0:    9925975          XT-PIC  timer
  1:       3379          XT-PIC  i8042
  2:          0          XT-PIC  cascade
  7:          1          XT-PIC  parport0
  8:          4          XT-PIC  rtc
  9:          0          XT-PIC  acpi
 10:          0          XT-PIC  cs46xx, eth1
 11:      11459          XT-PIC  uhci_hcd:usb1, eth0
 12:      36814          XT-PIC  i8042
 14:      13224          XT-PIC  ide0
 15:         63          XT-PIC  ide1
NMI:          0 
LOC:          0 
ERR:          0
MIS:          0
ulysses:/data/root/scratch# 
ulysses:/data/root/scratch# cat /proc/ioports
0000-001f : dma1
0020-0021 : pic1
0040-0043 : timer0
0050-0053 : timer1
0060-006f : keyboard
0070-0077 : rtc
0080-008f : dma page reg
00a0-00a1 : pic2
00c0-00df : dma2
00f0-00ff : fpu
0170-0177 : ide1
01f0-01f7 : ide0
0213-0213 : ISAPnP
0240-025f : smc-ultra
02f8-02ff : serial
0376-0376 : ide1
0378-037a : parport0
03c0-03df : vga+
03f6-03f6 : ide0
03f8-03ff : serial
0778-077a : parport0
0a79-0a79 : isapnp write
0cf8-0cff : PCI conf1
1000-100f : 0000:00:04.1
  1000-1007 : ide0
  1008-100f : ide1
1020-103f : 0000:00:04.2
  1020-103f : uhci_hcd
1040-104f : 0000:00:04.3
  1040-104f : motherboard
    1040-1047 : piix4_smbus
1080-10ff : 0000:00:0e.0
1400-147f : 0000:00:10.0
8000-803f : 0000:00:04.3
  8000-803f : motherboard
    8000-8003 : PM1a_EVT_BLK
    8004-8005 : PM1a_CNT_BLK
    8008-800b : PM_TMR
    800c-800f : GPE0_BLK
    8010-8015 : ACPI CPU throttle
ulysses:/data/root/scratch# 
Script done on Sun 28 May 2006 04:17:42 PM EDT


	Further poking through the logs shows isa-pnp detecting the SMC
board during boot, and printing log messages stating that IRQ 5 was assigned
to the board.  But we don't see that reflected in /proc/interrupts after the
driver quit working.

---------------------------------------------------------------------------

	To rule out hardware problems, I rebooted the machine with Sarge. 
The disk is partitioned for multiple booting, with Sarge and Etch presently
installed.
	It was possible to install all drivers with modprobe commands, and
bring up all interfaces with ifconfig commands.  (The Sarge install doesn't
have /etc/modules and /etc/network/interfaces configured to do this at the
moment.)  All interfaces sent and received pings properly.



Reply to: