Box from hell testing for FC3t2

[Alan Cox]

I loaded FC3 test2 onto the box from hell which is my distribution
torture tester. It failed with flying colours

- FC3t2 base kernel would not boot in standard configuration because
  someone enabled EDD support which crashes it
- The SCSI layer blew up in several ways (#133998, #134001)
- The HAL layer goes bananas (#130649)
- The 3c59x driver breaks (#134000)
- Several of the USB hubs fail to initialize (not bugzilla'd yet need to
   do some debugging).
- Badness in interruptible_sleep_on from lock_down
- PS/2 mouse does not work
- hal_lpadmin is segfaulting randomly
- PCI allocation produced unhappy looking messages
Sep 28 19:27:48 localhost kernel: PCI: Failed to allocate I/O resource #0:80@b000 for
0000:05:0c.0

etc

It even managed to rename my loopback device eth0 and create devices with
names like dev1536.

To be fair its a pretty brutal test box but the results are not so good as I'd
hoped. Upgrading to a 2.6.9rc2 kernel fixes nothing but breaks r8169 and
via-velocity ethernet drivers too

Alan

[Harald Hoyer]

Alan Cox wrote:
>  It even managed to rename my loopback device eth0 and create devices
> with
>  names like dev1536.
>   
devices or network interfaces?? Did _you_ do that, or did that just happen?

[Alan Cox]

On Wed, Sep 29, 2004 at 11:43:33AM +0200, Harald Hoyer wrote:
>  Alan Cox wrote:
>  >It even managed to rename my loopback device eth0 and create devices with
>  >names like dev1536.
>  
>  devices or network interfaces?? Did _you_ do that, or did that just happen? 
network interface, and it did it not me. I think this was all part of the
fallout when loopback got renamed eth0 because it thought it was a 3com
3c59x that probed with a MAC of 00:00:00:00:00:00

apparently our code is not robust in this case

[Stephen John Smoogen]

On Wed, 29 Sep 2004 08:06:13 -0400, Alan Cox <alan(a)redhat.com&gt; wrote:
>  On Wed, Sep 29, 2004 at 11:43:33AM +0200, Harald Hoyer wrote:
>  > Alan Cox wrote:
>  > >It even managed to rename my loopback device eth0 and create devices with
>  > >names like dev1536.
>  >
>  > devices or network interfaces?? Did _you_ do that, or did that just happen?
>  
>  network interface, and it did it not me. I think this was all part of the
>  fallout when loopback got renamed eth0 because it thought it was a 3com
>  3c59x that probed with a MAC of 00:00:00:00:00:00
>  
>  apparently our code is not robust in this case
>  
Does it broadcast a MAC address of that on the wire.. if so that is evil.

[Alan Cox]

On Wed, Sep 29, 2004 at 09:36:17AM -0600, Stephen J. Smoogen wrote:
>  > network interface, and it did it not me. I think this was all
> part of the
>  > fallout when loopback got renamed eth0 because it thought it was a 3com
>  > 3c59x that probed with a MAC of 00:00:00:00:00:00
>  > 
>  > apparently our code is not robust in this case
>  
>  Does it broadcast a MAC address of that on the wire.. if so that is evil. 
Sniffing it - no

[Lamar Owen]

On Tuesday 28 September 2004 18:06, Alan Cox wrote:
>  I loaded FC3 test2 onto the box from hell which is my distribution
>  torture tester. It failed with flying colours 
Can you refresh our memory about the configuration of this frankenbox? (This 
way we know what not to get.... :-))
-- 
Lamar Owen
Director of Information Technology
Pisgah Astronomical Research Institute
1 PARI Drive
Rosman, NC  28772
[phone]
www.pari.edu

[Alan Cox]

On Wed, Sep 29, 2004 at 12:46:53PM -0400, Lamar Owen wrote:
>  Can you refresh our memory about the configuration of this
> frankenbox? (This 
>  way we know what not to get.... :-)) 

00:00.0 Host bridge: VIA Technologies, Inc.: Unknown device 0282
00:00.1 Host bridge: VIA Technologies, Inc.: Unknown device 1282
00:00.2 Host bridge: VIA Technologies, Inc.: Unknown device 2282
00:00.3 Host bridge: VIA Technologies, Inc.: Unknown device 3282
00:00.4 Host bridge: VIA Technologies, Inc.: Unknown device 4282
00:00.7 Host bridge: VIA Technologies, Inc.: Unknown device 7282
00:01.0 PCI bridge: VIA Technologies, Inc. VT8237 PCI bridge [K8T800 South]
00:09.0 CardBus bridge: Ricoh Co Ltd RL5c475 (rev 80)
00:0a.0 PCI bridge: MOBILITY Electronics EV1000 bridge
00:0b.0 SCSI storage controller: Artop Electronic Corp AEC6712U SCSI (rev 01)
00:0c.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8169 Gigabit Ethernet
(rev 10)
00:0e.0 Ethernet controller: VIA Technologies, Inc. VT6120/VT6121/VT6122 Gigabit Ethernet
Adapter (rev 11)
00:0f.0 IDE interface: VIA Technologies, Inc. VIA VT6420 SATA RAID Controller (rev 80)
00:0f.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus
Master IDE (rev 06)
00:10.0 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81)
00:10.1 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81)
00:10.2 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81)
00:10.3 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81)
00:10.4 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 86)
00:11.0 ISA bridge: VIA Technologies, Inc. VT8237 ISA bridge [K8T800 South]
00:11.5 Multimedia audio controller: VIA Technologies, Inc. VT8233/A/8235/8237 AC97 Audio
Controller (rev 60)
00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport
Technology Configuration
00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map
00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller
00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous
Control
01:00.0 VGA compatible controller: ATI Technologies Inc Radeon RV250 If [Radeon 9000] (rev
01)
03:00.0 Parallel controller: MOBILITY Electronics EV1000 Parallel port
03:00.1 Serial controller: MOBILITY Electronics EV1000 Serial port
03:00.2 Keyboard controller: MOBILITY Electronics EV1000 Keyboard controller
03:00.3 Mouse controller: MOBILITY Electronics EV1000 Mouse controller
03:01.0 RAID bus controller: Silicon Image, Inc. (formerly CMD Technology Inc) PCI0646
(rev 07)
03:04.0 Multimedia audio controller: Trident Microsystems 4DWave DX (rev 02)
03:05.0 Multimedia video controller: Auravision VxP524
03:08.0 Multimedia video controller: 3Dfx Interactive, Inc. Voodoo 2 (rev 02)
03:09.0 USB Controller: OPTi Inc. 82C861 (rev 10)
04:00.0 PCI bridge: MOBILITY Electronics EV1000 bridge
05:00.0 Parallel controller: MOBILITY Electronics EV1000 Parallel port
05:00.1 Serial controller: MOBILITY Electronics EV1000 Serial port
05:00.2 Keyboard controller: MOBILITY Electronics EV1000 Keyboard controller
05:00.3 Mouse controller: MOBILITY Electronics EV1000 Mouse controller
05:04.0 USB Controller: OPTi Inc. 82C861 (rev 10)
05:08.0 USB Controller: OPTi Inc. 82C861 (rev 10)
05:0c.0 Ethernet controller: 3Com Corporation 3c905B 100BaseTX [Cyclone] (rev 30)

[Francois Romieu]

Alan Cox <alan(a)redhat.com&gt; :
[...]
>  To be fair its a pretty brutal test box but the results are not so
> good as I'd
>  hoped. Upgrading to a 2.6.9rc2 kernel fixes nothing but breaks r8169 and
>  via-velocity ethernet drivers too 
r8169 should be fine in further -rc2-bk for the amd64 box.

Tejun Heo has posted some patches on netdev which fixes several issues with the
via-velocity driver.

Single file patch:
http://www.fr.zoreil.com/people/francois/misc/2004-09-29-2.6.9-rc2-bk15-v...

Split patches:
http://www.fr.zoreil.com/linux/kernel/2.6.x/2.6.9-rc2-bk15/

--
Ueimor

[Alan Cox]

On Wed, Sep 29, 2004 at 11:06:38PM +0200, Francois Romieu wrote:
>  r8169 should be fine in further -rc2-bk for the amd64 box.
>  Tejun Heo has posted some patches on netdev which fixes several issues with the
>  via-velocity driver. 
I need to look at those. I've got received some patches from J Jiang of VIA
for the driver. 

Alan