NForce2 pseudoscience stability testing (2.6.0-test11)

NForce2 pseudoscience stability testing (2.6.0-test11)

[ross.alexander]

Brendan et al,

I have been test various kernel parameter combinations to test stability.

Basic scenario is default IDE driver, AIC7xxx PCI SCSI connected to HP 
externel DVD.
Using grip (CDDA ripper) to test if system locks up.  Unstable systems 
will normally lock up
around track two or three.  Stable systems are those which haven't locked 
up after half
a dozen different CDs have been ripped.

MB: ASUS A7N8X
CPU: Athlon XP 2700+
Memory: 1.5GB (3 x 512MB DIMMs)
Disk: Internal 80GB IDE

COMPILE         SMP     ACPI    PCI     LAPIC   APIC    RESULT  NOTE
SMP,PREM                ON                              F
SMP,PREM                ON      NOACPI                  F
SMP,PREM                OFF                             F
SMP,PREM                OFF             NO      NO      S
SMP,PREM                OFF                     NO      F
SMP,PREM                OFF             NO              S
SMP,PREM                ON              NO      NO      F       1
SMP                     ON              NO              F       2
SMP                                                     F       3
APIC,LAPIC                                              S
PREM,APIC,LAPIC                                         S

* SMP = On (if compiled it) unless nosmp set.  Using nosmp with smp kernel 
causes very odd results.
* ACPI = Compiled by default.  Set off using kernel paramter acpi=off.
* PCI = Kernel parameter.  Only used to turn APCI routing off.
* LAPIC = Kernel paramter to turn it off (nolapic).
* APIC = Kernel paramter to turn it off (noapic).

1. Using APCI PCI routing and nolapic gives very odd results.  As soon as 
the network tries
to configure itself it simple hangs (but C-Alt-Del will reboot it).

2. Using the nolapic kernel parameter without disabling ACPI does nothing.

3. Using kernel parameter nosmp on and SMP kernel causes all the lower 16 
IRQs to work in XT-PIC
mode and the PCI network card to use IRQ 21 with IO-APIC-level.  Trying to 
modprobe aic7xxx hung
modprobe but not system.

The conclusion to this is the problem is in Local APIC with SMP.  I'm not 
saying this is actually true
only that is what the data suggests.  If anybody wants me to try some 
other stuff feel free to suggest
ideas.

Cheers,

Ross

---------------------------------------------------------------------------------
Ross Alexander                           "We demand clearly defined
MIS - NEC Europe Limited            boundaries of uncertainty and
Work ph: +44 20 8752 3394         doubt."

Re: NForce2 pseudoscience stability testing (2.6.0-test11)

[Alistair John Strachan]

On Friday 28 November 2003 15:13, ross.alexander@uk.neceur.com wrote:
[snip]
> 
> The conclusion to this is the problem is in Local APIC with SMP.  I'm not 
> saying this is actually true
> only that is what the data suggests.  If anybody wants me to try some 
> other stuff feel free to suggest
> ideas.
> 
> Cheers,
> 
> Ross
> 

It's evidently a configuration problem, albeit BIOS, mainboard revision, 
memory quality, etc. because I and many others like me are able to run Linux 
2.4/2.6 with all the options you tested and still achieve absolute stability, 
on the nForce 2 platform.

My system is an EPOX 8RDA+, with an Athlon 2500+ (Barton) overclocked to 
2.2Ghz, and 2x256MB TwinMOS PC3200 dimms. FSB is at 400Mhz, and the ram 
timings are 4,2,2,2. One might expect such a configuration to be unstable, 
but it is not.

I'm currently running 2.6.0-test10-mm1 with full ACPI (+ routing), APIC and 
local APIC, no preempt, UP, and everything has been rock-solid, despite the 
machine being under constant 100% CPU load and fairly active IO load.

Also, many others have found that just disabling local apic (and the MPS 
setting in the BIOS) as well as ACPI solves their problem, so I'm skeptical 
that SMP really causes *nForce 2 specific* instability.

-- 
Cheers,
Alistair.

personal:   alistair()devzero!co!uk
university: s0348365()sms!ed!ac!uk
student:    CS/AI Undergraduate
contact:    7/10 Darroch Court,
            University of Edinburgh.

Re: NForce2 pseudoscience stability testing (2.6.0-test11)

[Julien Oster]

Alistair John Strachan <s0348365@sms.ed.ac.uk> writes:

Hello Alistair,

> It's evidently a configuration problem, albeit BIOS, mainboard revision,
> memory quality, etc. because I and many others like me are able to run Linux
> 2.4/2.6 with all the options you tested and still achieve absolute stability,
> on the nForce 2 platform.

No, it's most evidently a mainboard problem, as everybody using an
ASUS A7N8X (Deluxe) reported so far that the mainboard will lock up
completely unless you turn of ACPI, APIC and local APIC. There is no
other possibility to work this lockup madness around, as many users of
that mainboard including me really tried *everything*.

We know that other NForce2 Mainboards don't have this kind of problem,
but sadly that isn't of any help whatsoever for us A7N8X users.

Unfortunately, my onboard SATA controller is significantly slower when
using XT-PIC interrupts (and I don't have many of them which aren't
crowded anyway). I can verify this by booting with ACPI and APIC
enabled and doing a simple hdparm -t multiple times on my SATA
softraid. I won't have much time to do this, though, since the
mainboard loves locking up very soon especially by doing hdparm -t.

HOWEVER, I tested it several times under Windows 2000 (I installed it
solely for this purpose, my machine used to be completely Redmond
free), and although Windows 2000 also routes the PCI interrupts via
APIC and ACPI, there's no such lockup occuring.

So, somehow, Linux should be able to allow the Asus A7N8X operate with
APIC and ACPI and any help in finally getting it in an usable state
would be strongly appreciated. I would have hacked the kernel myself,
but unfortunately I have no clue of the ACPI and APIC/local APIC stuff
in the kernel source.

Regards,
Julien

Re: NForce2 pseudoscience stability testing (2.6.0-test11)

[Prakash K. Cheemplavam]

Julien Oster wrote:
> Alistair John Strachan <s0348365@sms.ed.ac.uk> writes:
> 
> Hello Alistair,
> 
> 
>>It's evidently a configuration problem, albeit BIOS, mainboard revision,
>>memory quality, etc. because I and many others like me are able to run Linux
>>2.4/2.6 with all the options you tested and still achieve absolute stability,
>>on the nForce 2 platform.
> No, it's most evidently a mainboard problem, as everybody using an
> ASUS A7N8X (Deluxe) reported so far that the mainboard will lock up
> completely unless you turn of ACPI, APIC and local APIC. There is no
> other possibility to work this lockup madness around, as many users of
> that mainboard including me really tried *everything*.

At least since kernel 2.6-test8, I thin,k ACPI works with my Abit 
nforce2 mobo. Before it crapped out.


> Unfortunately, my onboard SATA controller is significantly slower when

> HOWEVER, I tested it several times under Windows 2000 (I installed it
> solely for this purpose, my machine used to be completely Redmond
> free), and although Windows 2000 also routes the PCI interrupts via
> APIC and ACPI, there's no such lockup occuring.


Intersting. My Windows locks up, as written in the other post, though 
this seldomly occurs. Sometimes the system runs for days (using s3 and 
s4). Then it could lock-up within minutes after boot-up.

kernel26 though locks up pretty fast when apic is enbled.

What kind of SATA Adapter hat the Asus? I have a Silicon image Si3112A. 
Maybe this is the root of all evil. ItÄs driver sucks hard, as doing a 
hdparm -d1 /dev/hde craps my drive up. (Though hdparm claims the drive 
is already running in DMA mode.)

What kind of SATA controller do the Epox users have? Or don't they have 
SATA onbaord?

I know that SiI Image produced corruption with early bioses, so maybe 
this really is the weak spot.


Prakash

Re: NForce2 pseudoscience stability testing (2.6.0-test11)

[Josh McKinney]

On approximately Fri, Nov 28, 2003 at 07:13:23PM +0100, Julien Oster wrote:
> Alistair John Strachan <s0348365@sms.ed.ac.uk> writes:
> 
> Hello Alistair,
> 
> > It's evidently a configuration problem, albeit BIOS, mainboard revision,
> > memory quality, etc. because I and many others like me are able to run Linux
> > 2.4/2.6 with all the options you tested and still achieve absolute stability,
> > on the nForce 2 platform.
> 
> No, it's most evidently a mainboard problem, as everybody using an
> ASUS A7N8X (Deluxe) reported so far that the mainboard will lock up
> completely unless you turn of ACPI, APIC and local APIC. There is no
> other possibility to work this lockup madness around, as many users of
> that mainboard including me really tried *everything*.
> 
> We know that other NForce2 Mainboards don't have this kind of problem,
> but sadly that isn't of any help whatsoever for us A7N8X users.
> 
<snip>

I have also been using a A7N8X deluxe and saw lockups when I first
recieved the board.  Booting with noapic nolapic solved the problems.
Later after reading some threads about it I decided to add some stuff to
a bugzilla that someone else already filed.  After doing this I decided
to try to crash it like it used to to with apic and lapic but it DID NOT
CRASH!  This may be due to an updated BIOS, I am using the 1007 Uber
BIOS, or some updates with the kernel, but I am running 2.6.0-test9-mm3
rock solid with ACPI, APIC, and local APIC.

Here is dmesg and /proc/interrupts

nformation
Building zonelist for node : 0
Kernel command line: vga=0x31A video=vesafb:mttr,pmipal,pro,ywrap root=/dev/hdc5 ro
current: c02f3a60
current->thread_info: c035c000
Initializing CPU#0
PID hash table entries: 2048 (order 11: 16384 bytes)
Detected 2205.273 MHz processor.
Using tsc for high-res timesource
Console: colour dummy device 80x25
Memory: 515516k/524224k available (1712k kernel code, 7964k reserved, 701k data, 144k init, 0k highmem)
zapping low mappings.
Calibrating delay loop... 4358.14 BogoMIPS
Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
Mount-cache hash table entries: 512 (order: 0, 4096 bytes)
CPU:     After generic identify, caps: 0383fbff c1c3fbff 00000000 00000000
CPU:     After vendor identify, caps: 0383fbff c1c3fbff 00000000 00000000
CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
CPU: L2 Cache: 512K (64 bytes/line)
CPU:     After all inits, caps: 0383fbff c1c3fbff 00000000 00000020
CPU: AMD Athlon(tm) XP 3200+ stepping 00
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Checking 'hlt' instruction... OK.
POSIX conformance testing by UNIFIX
enabled ExtINT on CPU#0
ESR value before enabling vector: 00000000
ESR value after enabling vector: 00000000
ENABLING IO-APIC IRQs
init IO_APIC IRQs
 IO-APIC (apicid-pin) 2-0, 2-16, 2-17, 2-18, 2-19, 2-20, 2-21, 2-22, 2-23 not connected.
..TIMER: vector=0x31 pin1=2 pin2=-1
..MP-BIOS bug: 8254 timer not connected to IO-APIC
...trying to set up timer (IRQ0) through the 8259A ...  failed.
...trying to set up timer as Virtual Wire IRQ... failed.
...trying to set up timer as ExtINT IRQ... works.
number of MP IRQ sources: 15.
number of IO-APIC #2 registers: 24.
testing the IO APIC.......................
IO APIC #2......
.... register #00: 02000000
.......    : physical APIC id: 02
.......    : Delivery Type: 0
.......    : LTS          : 0
.... register #01: 00170011
.......     : max redirection entries: 0017
.......     : PRQ implemented: 0
.......     : IO APIC version: 0011
.... register #02: 00000000
.......     : arbitration: 00
.... 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 001 01  0    0    0   0   0    1    1    39
 02 000 00  1    0    0   0   0    0    0    00
 03 001 01  0    0    0   0   0    1    1    41
 04 001 01  0    0    0   0   0    1    1    49
 05 001 01  0    0    0   0   0    1    1    51
 06 001 01  0    0    0   0   0    1    1    59
 07 001 01  1    0    0   0   0    1    1    61
 08 001 01  0    0    0   0   0    1    1    69
 09 001 01  1    1    0   0   0    1    1    71
 0a 001 01  0    0    0   0   0    1    1    79
 0b 001 01  0    0    0   0   0    1    1    81
 0c 001 01  0    0    0   0   0    1    1    89
 0d 001 01  0    0    0   0   0    1    1    91
 0e 001 01  0    0    0   0   0    1    1    99
 0f 001 01  0    0    0   0   0    1    1    A1
 10 000 00  1    0    0   0   0    0    0    00
 11 000 00  1    0    0   0   0    0    0    00
 12 000 00  1    0    0   0   0    0    0    00
 13 000 00  1    0    0   0   0    0    0    00
 14 000 00  1    0    0   0   0    0    0    00
 15 000 00  1    0    0   0   0    0    0    00
 16 000 00  1    0    0   0   0    0    0    00
 17 000 00  1    0    0   0   0    0    0    00
IRQ to pin mappings:
IRQ0 -> 0:2
IRQ1 -> 0:1
IRQ3 -> 0:3
IRQ4 -> 0:4
IRQ5 -> 0:5
IRQ6 -> 0:6
IRQ7 -> 0:7
IRQ8 -> 0:8
IRQ9 -> 0:9
IRQ10 -> 0:10
IRQ11 -> 0:11
IRQ12 -> 0:12
IRQ13 -> 0:13
IRQ14 -> 0:14
IRQ15 -> 0:15
.................................... done.
Using local APIC timer interrupts.
calibrating APIC timer ...
..... CPU clock speed is 2204.0700 MHz.
..... host bus clock speed is 400.0854 MHz.
NET: Registered protocol family 16
PCI: PCI BIOS revision 2.10 entry at 0xfb490, last bus=3
PCI: Using configuration type 1
mtrr: v2.0 (20020519)
ACPI: Subsystem revision 20031002
IOAPIC[0]: Set PCI routing entry (2-9 -> 0x71 -> IRQ 9 Mode:1 Active:0)
ACPI: Interpreter enabled
ACPI: Using IOAPIC for interrupt routing
ACPI: PCI Root Bridge [PCI0] (00:00)
PCI: Probing PCI hardware (bus 00)
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.HUB0._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.AGPB._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.HUB1._PRT]
ACPI: PCI Interrupt Link [LNK1] (IRQs 3 4 5 6 7 10 11 12 14 15)
ACPI: PCI Interrupt Link [LNK2] (IRQs 3 4 5 6 7 10 11 12 14 15)
ACPI: PCI Interrupt Link [LNK3] (IRQs 3 4 5 6 7 10 11 12 14 15)
ACPI: PCI Interrupt Link [LNK4] (IRQs 3 4 *5 6 7 10 11 12 14 15)
ACPI: PCI Interrupt Link [LNK5] (IRQs 3 4 5 6 7 10 11 12 14 15)
ACPI: PCI Interrupt Link [LUBA] (IRQs 3 4 5 6 7 10 *11 12 14 15)
ACPI: PCI Interrupt Link [LUBB] (IRQs 3 4 5 6 7 10 11 *12 14 15)
ACPI: PCI Interrupt Link [LMAC] (IRQs 3 4 5 6 7 10 11 *12 14 15)
ACPI: PCI Interrupt Link [LAPU] (IRQs 3 4 5 6 7 10 11 *12 14 15)
ACPI: PCI Interrupt Link [LACI] (IRQs 3 4 5 6 7 10 *11 12 14 15)
ACPI: PCI Interrupt Link [LMCI] (IRQs 3 4 5 6 7 10 11 12 14 15)
ACPI: PCI Interrupt Link [LSMB] (IRQs 3 4 *5 6 7 10 11 12 14 15)
ACPI: PCI Interrupt Link [LUB2] (IRQs 3 4 5 6 7 10 *11 12 14 15)
ACPI: PCI Interrupt Link [LFIR] (IRQs 3 4 *5 6 7 10 11 12 14 15)
ACPI: PCI Interrupt Link [L3CM] (IRQs 3 4 5 6 7 10 *11 12 14 15)
ACPI: PCI Interrupt Link [LIDE] (IRQs 3 4 5 6 7 10 11 12 14 15)
ACPI: PCI Interrupt Link [APC1] (IRQs 16)
ACPI: PCI Interrupt Link [APC2] (IRQs 17)
ACPI: PCI Interrupt Link [APC3] (IRQs 18)
ACPI: PCI Interrupt Link [APC4] (IRQs *19)
ACPI: PCI Interrupt Link [APC5] (IRQs 16)
ACPI: PCI Interrupt Link [APCF] (IRQs 20 21 22)
ACPI: PCI Interrupt Link [APCG] (IRQs 20 21 22)
ACPI: PCI Interrupt Link [APCH] (IRQs 20 21 22)
ACPI: PCI Interrupt Link [APCI] (IRQs 20 21 22)
ACPI: PCI Interrupt Link [APCJ] (IRQs 20 21 22)
ACPI: PCI Interrupt Link [APCK] (IRQs 20 21 22)
ACPI: PCI Interrupt Link [APCS] (IRQs *23)
ACPI: PCI Interrupt Link [APCL] (IRQs 20 21 22)
ACPI: PCI Interrupt Link [APCM] (IRQs 20 21 22)
ACPI: PCI Interrupt Link [AP3C] (IRQs 20 21 22)
ACPI: PCI Interrupt Link [APCZ] (IRQs 20 21 22)
ACPI: PCI Interrupt Link [APCS] enabled at IRQ 23
IOAPIC[0]: Set PCI routing entry (2-23 -> 0xa9 -> IRQ 23 Mode:1 Active:0)
00:00:01[A] -> 2-23 -> IRQ 23
Pin 2-23 already programmed
ACPI: PCI Interrupt Link [APCF] enabled at IRQ 20
IOAPIC[0]: Set PCI routing entry (2-20 -> 0xb1 -> IRQ 20 Mode:1 Active:0)
00:00:02[A] -> 2-20 -> IRQ 20
ACPI: PCI Interrupt Link [APCG] enabled at IRQ 22
IOAPIC[0]: Set PCI routing entry (2-22 -> 0xb9 -> IRQ 22 Mode:1 Active:0)
00:00:02[B] -> 2-22 -> IRQ 22
ACPI: PCI Interrupt Link [APCL] enabled at IRQ 21
IOAPIC[0]: Set PCI routing entry (2-21 -> 0xc1 -> IRQ 21 Mode:1 Active:0)
00:00:02[C] -> 2-21 -> IRQ 21
ACPI: PCI Interrupt Link [APCH] enabled at IRQ 20
Pin 2-20 already programmed
ACPI: PCI Interrupt Link [APCI] enabled at IRQ 22
Pin 2-22 already programmed
ACPI: PCI Interrupt Link [APCJ] enabled at IRQ 21
Pin 2-21 already programmed
ACPI: PCI Interrupt Link [APCK] enabled at IRQ 20
Pin 2-20 already programmed
ACPI: PCI Interrupt Link [APCM] enabled at IRQ 22
Pin 2-22 already programmed
ACPI: PCI Interrupt Link [AP3C] enabled at IRQ 21
Pin 2-21 already programmed
ACPI: PCI Interrupt Link [APCZ] enabled at IRQ 20
Pin 2-20 already programmed
ACPI: PCI Interrupt Link [APC1] enabled at IRQ 16
IOAPIC[0]: Set PCI routing entry (2-16 -> 0xc9 -> IRQ 16 Mode:1 Active:0)
00:01:06[A] -> 2-16 -> IRQ 16
ACPI: PCI Interrupt Link [APC2] enabled at IRQ 17
IOAPIC[0]: Set PCI routing entry (2-17 -> 0xd1 -> IRQ 17 Mode:1 Active:0)
00:01:06[B] -> 2-17 -> IRQ 17
ACPI: PCI Interrupt Link [APC3] enabled at IRQ 18
IOAPIC[0]: Set PCI routing entry (2-18 -> 0xd9 -> IRQ 18 Mode:1 Active:0)
00:01:06[C] -> 2-18 -> IRQ 18
ACPI: PCI Interrupt Link [APC4] enabled at IRQ 19
IOAPIC[0]: Set PCI routing entry (2-19 -> 0xe1 -> IRQ 19 Mode:1 Active:0)
00:01:06[D] -> 2-19 -> IRQ 19
Pin 2-19 already programmed
Pin 2-16 already programmed
Pin 2-17 already programmed
Pin 2-18 already programmed
Pin 2-18 already programmed
Pin 2-19 already programmed
Pin 2-16 already programmed
Pin 2-17 already programmed
Pin 2-17 already programmed
Pin 2-18 already programmed
Pin 2-19 already programmed
Pin 2-16 already programmed
Pin 2-16 already programmed
Pin 2-17 already programmed
Pin 2-18 already programmed
Pin 2-19 already programmed
Pin 2-18 already programmed
Pin 2-18 already programmed
Pin 2-18 already programmed
Pin 2-18 already programmed
Pin 2-19 already programmed
Pin 2-21 already programmed
Pin 2-21 already programmed
Pin 2-21 already programmed
Pin 2-21 already programmed
PCI: Using ACPI for IRQ routing
PCI: if you experience problems, try using option 'pci=noacpi' or even 'acpi=off'
vesafb: framebuffer at 0xd8000000, mapped to 0xe080c000, size 16384k
vesafb: mode is 1280x1024x16, linelength=2560, pages=1
vesafb: protected mode interface info at c000:e710
vesafb: pmi: set display start = c00ce755, set palette = c00ce7da
vesafb: pmi: ports = b4c3 b503 ba03 c003 c103 c403 c503 c603 c703 c803 c903 cc03 ce03 cf03 d003 d103 d203 d303 d403 d503 da03 ff03 
vesafb: scrolling: ywrap using protected mode interface, yres_virtual=6553
vesafb: directcolor: size=0:5:6:5, shift=0:11:5:0
fb0: VESA VGA frame buffer device
ikconfig 0.7 with /proc/config*
Initializing Cryptographic API
Console: switching to colour frame buffer device 160x64
pty: 256 Unix98 ptys configured
Linux agpgart interface v0.100 (c) Dave Jones
Serial: 8250/16550 driver $Revision: 1.90 $ 8 ports, IRQ sharing disabled
ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
Using anticipatory io scheduler
Floppy drive(s): fd0 is 1.44M
FDC 0 is a post-1991 82077
loop: loaded (max 8 devices)
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
NFORCE2: IDE controller at PCI slot 0000:00:09.0
NFORCE2: chipset revision 162
NFORCE2: not 100% native mode: will probe irqs later
NFORCE2: BIOS didn't set cable bits correctly. Enabling workaround.
NFORCE2: BIOS didn't set cable bits correctly. Enabling workaround.
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
NFORCE2: 0000:00:09.0 (rev a2) UDMA133 controller
    ide0: BM-DMA at 0xf000-0xf007, BIOS settings: hda:DMA, hdb:DMA
    ide1: BM-DMA at 0xf008-0xf00f, BIOS settings: hdc:DMA, hdd:DMA
hda: IBM-DTLA-307015, ATA DISK drive
hdb: CD-ROM 45X, ATAPI CD/DVD-ROM drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
hdc: WDC WD600BB-32CXA0, ATA DISK drive
hdd: AOPEN CRW1232, ATAPI CD/DVD-ROM drive
ide1 at 0x170-0x177,0x376 on irq 15
hda: max request size: 128KiB
hda: 30003120 sectors (15361 MB) w/1916KiB Cache, CHS=31749/15/63, UDMA(100)
 hda: hda1
hdc: max request size: 128KiB
hdc: 117231408 sectors (60022 MB) w/2048KiB Cache, CHS=65535/16/63, UDMA(100)
 hdc: hdc1 hdc2 hdc3 < hdc5 hdc6 hdc7 hdc8 hdc9 hdc10 hdc11 > hdc4
hdb: ATAPI 45X CD-ROM drive, 128kB Cache, UDMA(33)
Uniform CD-ROM driver Revision: 3.12
hdd: ATAPI 32X CD-ROM CD-R/RW drive, 4096kB Cache, DMA
ide-floppy driver 0.99.newide
Console: switching to colour frame buffer device 160x64
mice: PS/2 mouse device common for all mice
input: PC Speaker
serio: i8042 AUX port at 0x60,0x64 irq 12
input: AT Translated Set 2 keyboard on isa0060/serio0
serio: i8042 KBD port at 0x60,0x64 irq 1
NET: Registered protocol family 2
IP: routing cache hash table of 4096 buckets, 32Kbytes
TCP: Hash tables configured (established 32768 bind 65536)
NET: Registered protocol family 1
NET: Registered protocol family 17
NET: Registered protocol family 15
ACPI: (supports S0 S1 S4 S4bios S5)
kjournald starting.  Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
VFS: Mounted root (ext3 filesystem) readonly.
Freeing unused kernel memory: 144k freed
Adding 497972k swap on /dev/hdc11.  Priority:-1 extents:1
EXT3 FS on hdc5, internal journal
forcedeth.c: Reverse Engineered nForce ethernet driver. Version 0.18.
PCI: Setting latency timer of device 0000:00:04.0 to 64
eth0: forcedeth.c: subsystem: 01043:80a7
i2c /dev entries driver
nvidia: module license 'NVIDIA' taints kernel.
0: nvidia: loading NVIDIA Linux x86 nvidia.o Kernel Module  1.0-4496  Wed Jul 16 19:03:09 PDT 2003
kjournald starting.  Commit interval 5 seconds
EXT3 FS on hdc6, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS on hdc1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS on hdc7, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS on hdc8, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS on hdc9, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS on hdc2, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
drivers/usb/core/usb.c: registered new driver usbfs
drivers/usb/core/usb.c: registered new driver hub
ehci_hcd 0000:00:02.2: EHCI Host Controller
PCI: Setting latency timer of device 0000:00:02.2 to 64
ehci_hcd 0000:00:02.2: irq 21, pci mem e1854000
ehci_hcd 0000:00:02.2: new USB bus registered, assigned bus number 1
PCI: cache line size of 64 is not supported by device 0000:00:02.2
ehci_hcd 0000:00:02.2: USB 2.0 enabled, EHCI 1.00, driver 2003-Jun-13
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 6 ports detected
ohci_hcd: 2003 Oct 13 USB 1.1 'Open' Host Controller (OHCI) Driver (PCI)
ohci_hcd: block sizes: ed 64 td 64
ohci_hcd 0000:00:02.0: OHCI Host Controller
PCI: Setting latency timer of device 0000:00:02.0 to 64
ohci_hcd 0000:00:02.0: irq 20, pci mem e1856000
ohci_hcd 0000:00:02.0: new USB bus registered, assigned bus number 2
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 3 ports detected
ohci_hcd 0000:00:02.1: OHCI Host Controller
PCI: Setting latency timer of device 0000:00:02.1 to 64
ohci_hcd 0000:00:02.1: irq 22, pci mem e1858000
ohci_hcd 0000:00:02.1: new USB bus registered, assigned bus number 3
hub 3-0:1.0: USB hub found
hub 3-0:1.0: 3 ports detected
hub 3-0:1.0: new USB device on port 1, assigned address 2
Real Time Clock Driver v1.12
drivers/usb/core/usb.c: registered new driver hiddev
input: USB HID v1.10 Mouse [Logitech USB Receiver] on usb-0000:00:02.1-1
drivers/usb/core/usb.c: registered new driver hid
drivers/usb/input/hid-core.c: v2.0:USB HID core driver
PCI: Setting latency timer of device 0000:00:06.0 to 64
intel8x0_measure_ac97_clock: measured 50436 usecs
intel8x0: clocking to 47469
NET: Registered protocol family 10

           CPU0       
  0:   26210201          XT-PIC  timer
  1:      13262    IO-APIC-edge  i8042
  2:          0          XT-PIC  cascade
  8:          1    IO-APIC-edge  rtc
  9:          0   IO-APIC-level  acpi
 14:         54    IO-APIC-edge  ide0
 15:      55490    IO-APIC-edge  ide1
 19:    1970612   IO-APIC-level  nvidia
 20:      24241   IO-APIC-level  ohci_hcd, eth0
 21:     172362   IO-APIC-level  ehci_hcd, NVidia nForce2
 22:      17657   IO-APIC-level  ohci_hcd
NMI:          0 
LOC:   26209970 
ERR:          0
MIS:          0


 


-- 
Josh McKinney		     |	Webmaster: http://joshandangie.org
--------------------------------------------------------------------------
                             | They that can give up essential liberty
Linux, the choice       -o)  | to obtain a little temporary safety deserve 
of the GNU generation    /\  | neither liberty or safety. 
                        _\_v |                          -Benjamin Franklin

Re: NForce2 pseudoscience stability testing (2.6.0-test11)

[Julien Oster]

Josh McKinney <forming@charter.net> writes:

Hello Josh,

> I have also been using a A7N8X deluxe and saw lockups when I first
> recieved the board.  Booting with noapic nolapic solved the problems.
> Later after reading some threads about it I decided to add some stuff to
> a bugzilla that someone else already filed.  After doing this I decided
> to try to crash it like it used to to with apic and lapic but it DID NOT
> CRASH!  This may be due to an updated BIOS, I am using the 1007 Uber
> BIOS, or some updates with the kernel, but I am running 2.6.0-test9-mm3
> rock solid with ACPI, APIC, and local APIC.

Oh! That sounds nice. I also run the latest 1007 BIOS, but that
doesn't help at all. In crontrary, I almost have the impression that
the lockups got worse, but that may be just subjective. But what do
you mean with "1007 Uber BIOS"? What is this "Uber"? Is that a special
BIOS Version?

However, 2.6.0-test9-mm3 might be the key. I'll test this immediately.

Thanks,
Julien

Re: NForce2 pseudoscience stability testing (2.6.0-test11)

[Josh McKinney]

On approximately Sat, Nov 29, 2003 at 05:33:08PM +0100, Julien Oster wrote:
> Josh McKinney <forming@charter.net> writes:
> 
> Hello Josh,
> 
> > I have also been using a A7N8X deluxe and saw lockups when I first
> > recieved the board.  Booting with noapic nolapic solved the problems.
> > Later after reading some threads about it I decided to add some stuff to
> > a bugzilla that someone else already filed.  After doing this I decided
> > to try to crash it like it used to to with apic and lapic but it DID NOT
> > CRASH!  This may be due to an updated BIOS, I am using the 1007 Uber
> > BIOS, or some updates with the kernel, but I am running 2.6.0-test9-mm3
> > rock solid with ACPI, APIC, and local APIC.
> 
> Oh! That sounds nice. I also run the latest 1007 BIOS, but that
> doesn't help at all. In crontrary, I almost have the impression that
> the lockups got worse, but that may be just subjective. But what do
> you mean with "1007 Uber BIOS"? What is this "Uber"? Is that a special
> BIOS Version?
> 

I should have given more info.  It is a custom made BIOS made by a guy
at nforcershq.com

http://homepage.ntlworld.com/michael.mcclay/ 

It is strange to me that it doesn't crash anymore either.  I am going to
boot test11 when I get the chance later today and will see if it still works.

-- 
Josh McKinney		     |	Webmaster: http://joshandangie.org
--------------------------------------------------------------------------
                             | They that can give up essential liberty
Linux, the choice       -o)  | to obtain a little temporary safety deserve 
of the GNU generation    /\  | neither liberty or safety. 
                        _\_v |                          -Benjamin Franklin

Re: NForce2 pseudoscience stability testing (2.6.0-test11)

[ross.alexander]

Alistair,

I upgraded the BIOS about a week ago to 1007.  I personally found it to be 
less
stable than 1006.  I don't believe it is a problem with my hardware 
combination
since it has been stable for long periods of time.  I was running the SMP 
kernel
simply because I (wrongly) presumed a) you needed it to get the IO-APIC 
working,
and b) it didn't do any harm.

It is clear that the UP kernel is considerable more stable than the SMP 
kernel.  This
is a very useful fact since it suggests that it is not a problem with the 
IDE device
driver per se.  The whole purpose of my testing is to try to determine 
which options
increased the stability and hence highlight where the problem could be.

One of the reasons I don't like ACPI is the huge amount of additional 
complexity
it adds and the amount of stuff it could screw up.  Now I have not heard 
that any
of the VIA KTxxx based motherboards have any problems.  If this is true 
then the
problem does not lie with the LAPIC, since that is in the processor, not 
the MB.
The fact that it seems to only occur with the NForce2 chipset means it 
could
well be some interrupt coming into the LAPIC from Interrupt Bus.  However
I certainly don't claim to be an expert on this so I could well be talking 
complete
crap.

Conclusion: More testing required.

Cheers,

Ross

---------------------------------------------------------------------------------
Ross Alexander                           "We demand clearly defined
MIS - NEC Europe Limited            boundaries of uncertainty and
Work ph: +44 20 8752 3394         doubt."




Alistair John Strachan <s0348365@sms.ed.ac.uk>
28/11/2003 04:46 p.m.
 
        To:     ross.alexander@uk.neceur.com, "Brendan Howes" 
<brendan@netzentry.com>
        cc:     linux-kernel@vger.kernel.org
        Subject:        Re: NForce2 pseudoscience stability testing 
(2.6.0-test11)


On Friday 28 November 2003 15:13, ross.alexander@uk.neceur.com wrote:
[snip]
> 
> The conclusion to this is the problem is in Local APIC with SMP.  I'm 
not 
> saying this is actually true
> only that is what the data suggests.  If anybody wants me to try some 
> other stuff feel free to suggest
> ideas.
> 
> Cheers,
> 
> Ross
> 

It's evidently a configuration problem, albeit BIOS, mainboard revision, 
memory quality, etc. because I and many others like me are able to run 
Linux 
2.4/2.6 with all the options you tested and still achieve absolute 
stability, 
on the nForce 2 platform.

My system is an EPOX 8RDA+, with an Athlon 2500+ (Barton) overclocked to 
2.2Ghz, and 2x256MB TwinMOS PC3200 dimms. FSB is at 400Mhz, and the ram 
timings are 4,2,2,2. One might expect such a configuration to be unstable, 

but it is not.

I'm currently running 2.6.0-test10-mm1 with full ACPI (+ routing), APIC 
and 
local APIC, no preempt, UP, and everything has been rock-solid, despite 
the 
machine being under constant 100% CPU load and fairly active IO load.

Also, many others have found that just disabling local apic (and the MPS 
setting in the BIOS) as well as ACPI solves their problem, so I'm 
skeptical 
that SMP really causes *nForce 2 specific* instability.

-- 
Cheers,
Alistair.

personal:   alistair()devzero!co!uk
university: s0348365()sms!ed!ac!uk
student:    CS/AI Undergraduate
contact:    7/10 Darroch Court,
            University of Edinburgh.

Re: NForce2 pseudoscience stability testing (2.6.0-test11)

[Josh McKinney]

To me the strangest thing is that when I first got this board a month or
so ago it would hang with APIC or LAPIC enabled.  Now it works fine
without disabling APIC.  All I did was update the BIOS and use it for a
while with APIC disabled.  2.6.0-test9-mm through 2.6.0-test11 all work
just fine.  Still at the same time some people are reporting that it
works, some are reporting that it doesn't.  I probably wouldn't think to
much of this except I was one of the ones that said APIC causes crashes
with IDE load, but now it doesn't?

On approximately Tue, Dec 02, 2003 at 10:13:46AM +0000, ross.alexander@uk.neceur.com wrote:
> Alistair,
> 
> I upgraded the BIOS about a week ago to 1007.  I personally found it to be 
> less
> stable than 1006.  I don't believe it is a problem with my hardware 
> combination
> since it has been stable for long periods of time.  I was running the SMP 
> kernel
> simply because I (wrongly) presumed a) you needed it to get the IO-APIC 
> working,
> and b) it didn't do any harm.
> 
> It is clear that the UP kernel is considerable more stable than the SMP 
> kernel.  This
> is a very useful fact since it suggests that it is not a problem with the 
> IDE device
> driver per se.  The whole purpose of my testing is to try to determine 
> which options
> increased the stability and hence highlight where the problem could be.
> 
> One of the reasons I don't like ACPI is the huge amount of additional 
> complexity
> it adds and the amount of stuff it could screw up.  Now I have not heard 
> that any
> of the VIA KTxxx based motherboards have any problems.  If this is true 
> then the
> problem does not lie with the LAPIC, since that is in the processor, not 
> the MB.
> The fact that it seems to only occur with the NForce2 chipset means it 
> could
> well be some interrupt coming into the LAPIC from Interrupt Bus.  However
> I certainly don't claim to be an expert on this so I could well be talking 
> complete
> crap.
> 
> Conclusion: More testing required.
> 
> Cheers,
> 
> Ross
> 
> ---------------------------------------------------------------------------------
> Ross Alexander                           "We demand clearly defined
> MIS - NEC Europe Limited            boundaries of uncertainty and
> Work ph: +44 20 8752 3394         doubt."
> 
> 
> 
> 
> Alistair John Strachan <s0348365@sms.ed.ac.uk>
> 28/11/2003 04:46 p.m.
>  
>         To:     ross.alexander@uk.neceur.com, "Brendan Howes" 
> <brendan@netzentry.com>
>         cc:     linux-kernel@vger.kernel.org
>         Subject:        Re: NForce2 pseudoscience stability testing 
> (2.6.0-test11)
> 
> 
> On Friday 28 November 2003 15:13, ross.alexander@uk.neceur.com wrote:
> [snip]
> > 
> > The conclusion to this is the problem is in Local APIC with SMP.  I'm 
> not 
> > saying this is actually true
> > only that is what the data suggests.  If anybody wants me to try some 
> > other stuff feel free to suggest
> > ideas.
> > 
> > Cheers,
> > 
> > Ross
> > 
> 
> It's evidently a configuration problem, albeit BIOS, mainboard revision, 
> memory quality, etc. because I and many others like me are able to run 
> Linux 
> 2.4/2.6 with all the options you tested and still achieve absolute 
> stability, 
> on the nForce 2 platform.
> 
> My system is an EPOX 8RDA+, with an Athlon 2500+ (Barton) overclocked to 
> 2.2Ghz, and 2x256MB TwinMOS PC3200 dimms. FSB is at 400Mhz, and the ram 
> timings are 4,2,2,2. One might expect such a configuration to be unstable, 
> 
> but it is not.
> 
> I'm currently running 2.6.0-test10-mm1 with full ACPI (+ routing), APIC 
> and 
> local APIC, no preempt, UP, and everything has been rock-solid, despite 
> the 
> machine being under constant 100% CPU load and fairly active IO load.
> 
> Also, many others have found that just disabling local apic (and the MPS 
> setting in the BIOS) as well as ACPI solves their problem, so I'm 
> skeptical 
> that SMP really causes *nForce 2 specific* instability.
> 
> -- 
> Cheers,
> Alistair.
> 
> personal:   alistair()devzero!co!uk
> university: s0348365()sms!ed!ac!uk
> student:    CS/AI Undergraduate
> contact:    7/10 Darroch Court,
>             University of Edinburgh.
> 
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/

-- 
Josh McKinney		     |	Webmaster: http://joshandangie.org
--------------------------------------------------------------------------
                             | They that can give up essential liberty
Linux, the choice       -o)  | to obtain a little temporary safety deserve 
of the GNU generation    /\  | neither liberty or safety. 
                        _\_v |                          -Benjamin Franklin

Re: NForce2 pseudoscience stability testing (2.6.0-test11)

[Julien Oster]

ross.alexander@uk.neceur.com writes:

Hello Ross,

> I upgraded the BIOS about a week ago to 1007.  I personally found it
> to be less stable than 1006.

Yes, I can confirm that. With 1006, I could run 2.4.22-ac4 sometimes
for minutes, sometimes for several hours (2.6 however crashed right
away almost every time while still booting). With 1007, 2.4.22-ac4 is
also unstable.

> I don't believe it is a problem with my hardware combination since
> it has been stable for long periods of time.

Well, I tried everything with my hardware. Removing all cards,
disabling all onboard devices in BIOS setup etc... the only thing that
I didn't try yet was disabling the IDE controller, since I need the
PATA controller for booting.

> It is clear that the UP kernel is considerable more stable than the
> SMP kernel.  This is a very useful fact since it suggests that it is
> not a problem with the IDE device driver per se.  The whole purpose
> of my testing is to try to determine which options increased the
> stability and hence highlight where the problem could be.

Yes, you're right. Additionally, it's also very interesting that, at
least with BIOS 1006, 2.4.22-ac4 was much more stable with
APIC/LAPIC/ACPI enabled. It would at least run several hours.

> One of the reasons I don't like ACPI is the huge amount of
> additional complexity it adds and the amount of stuff it could screw
> up.

Unfortunately, I seem to need it to be able to use APIC (instead of
XT-PIC) interrupts. And my interrupts really are crowded, so finally
being able to enable the APIC would be a great thing. I already tested
it sometimes with interrupts on APIC, SATA definitely *is* faster (but
not for very long time, since it'll crash very soon :) )

> Now I have not heard that any of the VIA KTxxx based
> motherboards have any problems.

I had a VIA KT333, everything was fine. Then I bought the two SATA
drives and the ASUS A7N8X Deluxe v2.0. I changed nothing else. Now it
sucks.

> If this is true then the problem
> does not lie with the LAPIC, since that is in the processor, not the
> MB.

I can confirm that. My processor's very fine, it doesn't lockup with
the VIA board.

> The fact that it seems to only occur with the NForce2 chipset
> means it could well be some interrupt coming into the LAPIC from
> Interrupt Bus.  However I certainly don't claim to be an expert on
> this so I could well be talking complete crap.

I'm also far away from being an expert with that stuff. I would have
no problem to get some specific knowledge on APIC, but even then I
would simply have no clue where the problem might be in the kernel.

> Conclusion: More testing required.

Hmm, are you really sure? I mean, we tested *everything*, didn't we?
:-)

The only thing left is the removal of the onboard (PATA) IDE
controller. I can't do that, because my SATA disks have no bootable
system and my workstation is in heavy use for work at the
moment. However, it would be very interesting to see if it still locks
up.

Regards,
Julien

Re: NForce2 pseudoscience stability testing (2.6.0-test11)

[Julien Oster]

ross.alexander@uk.neceur.com writes:

Hello Ross,

> I have been test various kernel parameter combinations to test stability.

Thanks, that's quite a nice overview.

But something seems strange:

> APIC,LAPIC                                              S
> PREM,APIC,LAPIC                                         S

Does those two lines mean, that using ACPI, APIC and local APIC
enabled is stable, as long as your kernel is not an SMP kernel? If
yes, then I can't confirm this. I run strictly non-SMP kernels and
they always crash if APIC (or local APIC?) is enabled.

BTW, I use a very quick test to see if the system is stable, that also
can be performed when booting with a "read-only init=/bin/bash" LILO
command line (so that no filesystem will need to fsck after a crash):
just type hdparm -t /dev/hd<someharddrive> several times.

Regards,
Julien

Re: NForce2 pseudoscience stability testing (2.6.0-test11)

[Prakash K. Cheemplavam]

Julien Oster wrote:
> ross.alexander@uk.neceur.com writes:
>>I have been test various kernel parameter combinations to test stability.
> 
> 
> Thanks, that's quite a nice overview.
> 
> But something seems strange:
> 
> 
>>APIC,LAPIC                                              S
>>PREM,APIC,LAPIC                                         S
> 
> 
> Does those two lines mean, that using ACPI, APIC and local APIC
> enabled is stable, as long as your kernel is not an SMP kernel? If
> yes, then I can't confirm this. I run strictly non-SMP kernels and
> they always crash if APIC (or local APIC?) is enabled.

I also have the same problem on an Abit NF7-S V2.0: I think I tested 
(non-SMP always) with kernel 2.6-test8 last: With Apic (and/or local 
apic) system locks up. Without it is now rock-solid with ACPI. But it 
seems to be a BIOS issue, as Windows locks up with APIC use, as well. 
Well I am using latest BIOS and hope that Abit gets this fixed...

BTW, why would someone want an SMP kernel for a 1-CPU system?

Prakash

bug in -test11 make xconfig

[Christopher Sawtell]

Greets to linux-kernel people,

  I have noticed that it is not possible to configure the kernel to use the 
xfs file system using the 'make xconfig' command.

  'make menuconfig' and 'make gconfig' appear to work correctly.

 No need to reply, & I'm not worth to be be subscribed because of insufficient 
knowledge.

Re: NForce2 pseudoscience stability testing (2.6.0-test11)

[Craig Bradney]

I am also using a 2 week old A7N8X Deluxe, v2 with the latest 1007 BIOS.
I AM able to run 2.6 Test 11 with APIC, Local APIC and ACPI support
turned on (SMP off, Preemptible Kernel off).

Although the PC hasnt been under constant stress, uptime is over 12
hours and its not the first time its been up for 12 or more with test 11
(which was my first 2.6 kernel). Running Gentoo Linux btw.

 dmesg output follows:

  HighMem zone: 0 pages, LIFO batch:1
DMI 2.2 present.
ACPI: RSDP (v000 Nvidia                                    ) @
0x000f75e0
ACPI: RSDT (v001 Nvidia AWRDACPI 0x42302e31 AWRD 0x00000000) @
0x1fff3000
ACPI: FADT (v001 Nvidia AWRDACPI 0x42302e31 AWRD 0x00000000) @
0x1fff3040
ACPI: MADT (v001 Nvidia AWRDACPI 0x42302e31 AWRD 0x00000000) @
0x1fff74c0
ACPI: DSDT (v001 NVIDIA AWRDACPI 0x00001000 MSFT 0x0100000e) @
0x00000000
ACPI: Local APIC address 0xfee00000
ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
Processor #0 6:10 APIC version 16
ACPI: LAPIC_NMI (acpi_id[0x00] polarity[0x1] trigger[0x1] lint[0x1])
ACPI: IOAPIC (id[0x02] address[0xfec00000] global_irq_base[0x0])
IOAPIC[0]: Assigned apic_id 2
IOAPIC[0]: apic_id 2, version 17, address 0xfec00000, IRQ 0-23
ACPI: INT_SRC_OVR (bus[0] irq[0x0] global_irq[0x2] polarity[0x0]
trigger[0x0])
ACPI: INT_SRC_OVR (bus[0] irq[0x9] global_irq[0x9] polarity[0x1]
trigger[0x3])
ACPI: INT_SRC_OVR (bus[0] irq[0xe] global_irq[0xe] polarity[0x1]
trigger[0x1])
ACPI: INT_SRC_OVR (bus[0] irq[0xf] global_irq[0xf] polarity[0x1]
trigger[0x1])
Enabling APIC mode:  Flat.  Using 1 I/O APICs
Using ACPI (MADT) for SMP configuration information
Building zonelist for node : 0
Kernel command line: root=/dev/hda6
Initializing CPU#0
PID hash table entries: 2048 (order 11: 16384 bytes)
Detected 1913.623 MHz processor.
Console: colour VGA+ 80x25
Memory: 514544k/524224k available (2443k kernel code, 8932k reserved,
933k data, 168k init, 0k highmem)
Calibrating delay loop... 3784.70 BogoMIPS
Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
Mount-cache hash table entries: 512 (order: 0, 4096 bytes)
CPU:     After generic identify, caps: 0383fbff c1c3fbff 00000000
00000000
CPU:     After vendor identify, caps: 0383fbff c1c3fbff 00000000
00000000
CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
CPU: L2 Cache: 512K (64 bytes/line)
CPU:     After all inits, caps: 0383fbff c1c3fbff 00000000 00000020
Intel machine check architecture supported.
Intel machine check reporting enabled on CPU#0.
CPU: AMD Athlon(tm) XP 2600+ stepping 00
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Checking 'hlt' instruction... OK.
POSIX conformance testing by UNIFIX
enabled ExtINT on CPU#0
ESR value before enabling vector: 00000000
ESR value after enabling vector: 00000000
ENABLING IO-APIC IRQs
init IO_APIC IRQs
 IO-APIC (apicid-pin) 2-0, 2-16, 2-17, 2-18, 2-19, 2-20, 2-21, 2-22,
2-23 not connected.
..TIMER: vector=0x31 pin1=2 pin2=-1
..MP-BIOS bug: 8254 timer not connected to IO-APIC
...trying to set up timer (IRQ0) through the 8259A ...  failed.
...trying to set up timer as Virtual Wire IRQ... failed.
...trying to set up timer as ExtINT IRQ... works.
number of MP IRQ sources: 15.
number of IO-APIC #2 registers: 24.
testing the IO APIC.......................
IO APIC #2......
.... register #00: 02000000
.......    : physical APIC id: 02
.......    : Delivery Type: 0
.......    : LTS          : 0
.... register #01: 00170011
.......     : max redirection entries: 0017
.......     : PRQ implemented: 0
.......     : IO APIC version: 0011
.... register #02: 00000000
.......     : arbitration: 00
.... 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 001 01  0    0    0   0   0    1    1    39
 02 000 00  1    0    0   0   0    0    0    00
 03 001 01  0    0    0   0   0    1    1    41
 04 001 01  0    0    0   0   0    1    1    49
 05 001 01  0    0    0   0   0    1    1    51
 06 001 01  0    0    0   0   0    1    1    59
 07 001 01  1    0    0   0   0    1    1    61
 08 001 01  0    0    0   0   0    1    1    69
 09 001 01  1    1    0   0   0    1    1    71
 0a 001 01  0    0    0   0   0    1    1    79
 0b 001 01  0    0    0   0   0    1    1    81
 0c 001 01  0    0    0   0   0    1    1    89
 0d 001 01  0    0    0   0   0    1    1    91
 0e 001 01  0    0    0   0   0    1    1    99
 0f 001 01  0    0    0   0   0    1    1    A1
 10 000 00  1    0    0   0   0    0    0    00
 11 000 00  1    0    0   0   0    0    0    00
 12 000 00  1    0    0   0   0    0    0    00
 13 000 00  1    0    0   0   0    0    0    00
 14 000 00  1    0    0   0   0    0    0    00
 15 000 00  1    0    0   0   0    0    0    00
 16 000 00  1    0    0   0   0    0    0    00
 17 000 00  1    0    0   0   0    0    0    00
IRQ to pin mappings:
IRQ0 -> 0:2
IRQ1 -> 0:1
IRQ3 -> 0:3
IRQ4 -> 0:4
IRQ5 -> 0:5
IRQ6 -> 0:6
IRQ7 -> 0:7
IRQ8 -> 0:8
IRQ9 -> 0:9
IRQ10 -> 0:10
IRQ11 -> 0:11
IRQ12 -> 0:12
IRQ13 -> 0:13
IRQ14 -> 0:14
IRQ15 -> 0:15
.................................... done.
Using local APIC timer interrupts.
calibrating APIC timer ...
..... CPU clock speed is 1912.0910 MHz.
..... host bus clock speed is 332.0680 MHz.
NET: Registered protocol family 16
PCI: PCI BIOS revision 2.10 entry at 0xfb490, last bus=3
PCI: Using configuration type 1
mtrr: v2.0 (20020519)
ACPI: Subsystem revision 20031002
IOAPIC[0]: Set PCI routing entry (2-9 -> 0x71 -> IRQ 9 Mode:1 Active:0)
ACPI: Interpreter enabled
ACPI: Using IOAPIC for interrupt routing
ACPI: PCI Root Bridge [PCI0] (00:00)
PCI: Probing PCI hardware (bus 00)
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.HUB0._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.AGPB._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.HUB1._PRT]
ACPI: PCI Interrupt Link [LNK1] (IRQs 3 4 5 6 7 10 11 12 14 15)
ACPI: PCI Interrupt Link [LNK2] (IRQs 3 4 5 6 7 10 11 12 14 15)
ACPI: PCI Interrupt Link [LNK3] (IRQs 3 4 5 6 7 10 11 12 14 15)
ACPI: PCI Interrupt Link [LNK4] (IRQs 3 4 *5 6 7 10 11 12 14 15)
ACPI: PCI Interrupt Link [LNK5] (IRQs 3 4 5 6 7 10 11 12 14 15)
ACPI: PCI Interrupt Link [LUBA] (IRQs 3 4 5 6 7 10 *11 12 14 15)
ACPI: PCI Interrupt Link [LUBB] (IRQs 3 4 5 6 7 10 *11 12 14 15)
ACPI: PCI Interrupt Link [LMAC] (IRQs 3 4 5 6 7 10 11 12 14 15)
ACPI: PCI Interrupt Link [LAPU] (IRQs 3 4 *5 6 7 10 11 12 14 15)
ACPI: PCI Interrupt Link [LACI] (IRQs 3 4 5 6 7 10 *11 12 14 15)
ACPI: PCI Interrupt Link [LMCI] (IRQs 3 4 5 6 7 10 11 12 14 15)
ACPI: PCI Interrupt Link [LSMB] (IRQs 3 4 *5 6 7 10 11 12 14 15)
ACPI: PCI Interrupt Link [LUB2] (IRQs 3 4 *5 6 7 10 11 12 14 15)
ACPI: PCI Interrupt Link [LFIR] (IRQs 3 4 5 6 7 10 *11 12 14 15)
ACPI: PCI Interrupt Link [L3CM] (IRQs 3 4 5 6 7 10 *11 12 14 15)
ACPI: PCI Interrupt Link [LIDE] (IRQs 3 4 5 6 7 10 11 12 14 15)
ACPI: PCI Interrupt Link [APC1] (IRQs 16)
ACPI: PCI Interrupt Link [APC2] (IRQs 17)
ACPI: PCI Interrupt Link [APC3] (IRQs 18)
ACPI: PCI Interrupt Link [APC4] (IRQs *19)
ACPI: PCI Interrupt Link [APC5] (IRQs 16)
ACPI: PCI Interrupt Link [APCF] (IRQs 20 21 22)
ACPI: PCI Interrupt Link [APCG] (IRQs 20 21 22)
ACPI: PCI Interrupt Link [APCH] (IRQs 20 21 22)
ACPI: PCI Interrupt Link [APCI] (IRQs 20 21 22)
ACPI: PCI Interrupt Link [APCJ] (IRQs 20 21 22)
ACPI: PCI Interrupt Link [APCK] (IRQs 20 21 22)
ACPI: PCI Interrupt Link [APCS] (IRQs *23)
ACPI: PCI Interrupt Link [APCL] (IRQs 20 21 22)
ACPI: PCI Interrupt Link [APCM] (IRQs 20 21 22)
ACPI: PCI Interrupt Link [AP3C] (IRQs 20 21 22)
ACPI: PCI Interrupt Link [APCZ] (IRQs 20 21 22)
Linux Plug and Play Support v0.97 (c) Adam Belay
SCSI subsystem initialized
drivers/usb/core/usb.c: registered new driver usbfs
drivers/usb/core/usb.c: registered new driver hub
ACPI: PCI Interrupt Link [APCS] enabled at IRQ 23
IOAPIC[0]: Set PCI routing entry (2-23 -> 0xa9 -> IRQ 23 Mode:1
Active:0)
00:00:01[A] -> 2-23 -> IRQ 23
Pin 2-23 already programmed
ACPI: PCI Interrupt Link [APCF] enabled at IRQ 20
IOAPIC[0]: Set PCI routing entry (2-20 -> 0xb1 -> IRQ 20 Mode:1
Active:0)
00:00:02[A] -> 2-20 -> IRQ 20
ACPI: PCI Interrupt Link [APCG] enabled at IRQ 22
IOAPIC[0]: Set PCI routing entry (2-22 -> 0xb9 -> IRQ 22 Mode:1
Active:0)
00:00:02[B] -> 2-22 -> IRQ 22
ACPI: PCI Interrupt Link [APCL] enabled at IRQ 21
IOAPIC[0]: Set PCI routing entry (2-21 -> 0xc1 -> IRQ 21 Mode:1
Active:0)
00:00:02[C] -> 2-21 -> IRQ 21
ACPI: PCI Interrupt Link [APCH] enabled at IRQ 20
Pin 2-20 already programmed
ACPI: PCI Interrupt Link [APCI] enabled at IRQ 22
Pin 2-22 already programmed
ACPI: PCI Interrupt Link [APCJ] enabled at IRQ 21
Pin 2-21 already programmed
ACPI: PCI Interrupt Link [APCK] enabled at IRQ 20
Pin 2-20 already programmed
ACPI: PCI Interrupt Link [APCM] enabled at IRQ 22
Pin 2-22 already programmed
ACPI: PCI Interrupt Link [AP3C] enabled at IRQ 21
Pin 2-21 already programmed
ACPI: PCI Interrupt Link [APCZ] enabled at IRQ 20
Pin 2-20 already programmed
ACPI: PCI Interrupt Link [APC1] enabled at IRQ 16
IOAPIC[0]: Set PCI routing entry (2-16 -> 0xc9 -> IRQ 16 Mode:1
Active:0)
00:01:06[A] -> 2-16 -> IRQ 16
ACPI: PCI Interrupt Link [APC2] enabled at IRQ 17
IOAPIC[0]: Set PCI routing entry (2-17 -> 0xd1 -> IRQ 17 Mode:1
Active:0)
00:01:06[B] -> 2-17 -> IRQ 17
ACPI: PCI Interrupt Link [APC3] enabled at IRQ 18
IOAPIC[0]: Set PCI routing entry (2-18 -> 0xd9 -> IRQ 18 Mode:1
Active:0)
00:01:06[C] -> 2-18 -> IRQ 18
ACPI: PCI Interrupt Link [APC4] enabled at IRQ 19
IOAPIC[0]: Set PCI routing entry (2-19 -> 0xe1 -> IRQ 19 Mode:1
Active:0)
00:01:06[D] -> 2-19 -> IRQ 19
Pin 2-19 already programmed
Pin 2-16 already programmed
Pin 2-17 already programmed
Pin 2-18 already programmed
Pin 2-18 already programmed
Pin 2-19 already programmed
Pin 2-16 already programmed
Pin 2-17 already programmed
Pin 2-17 already programmed
Pin 2-18 already programmed
Pin 2-19 already programmed
Pin 2-16 already programmed
Pin 2-16 already programmed
Pin 2-17 already programmed
Pin 2-18 already programmed
Pin 2-19 already programmed
Pin 2-18 already programmed
Pin 2-18 already programmed
Pin 2-18 already programmed
Pin 2-18 already programmed
Pin 2-19 already programmed
Pin 2-21 already programmed
Pin 2-21 already programmed
Pin 2-21 already programmed
Pin 2-21 already programmed
PCI: Using ACPI for IRQ routing
PCI: if you experience problems, try using option 'pci=noacpi' or even
'acpi=off'
Machine check exception polling timer started.
devfs: v1.22 (20021013) Richard Gooch (rgooch@atnf.csiro.au)
devfs: boot_options: 0x1
Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
udf: registering filesystem
Supermount version 2.0.2a for kernel 2.6
ACPI: Power Button (FF) [PWRF]
ACPI: Processor [CPU0] (supports C1)
pty: 256 Unix98 ptys configured
request_module: failed /sbin/modprobe -- parport_lowlevel. error = -16
lp: driver loaded but no devices found
Real Time Clock Driver v1.12
Linux agpgart interface v0.100 (c) Dave Jones
agpgart: Detected NVIDIA nForce2 chipset
agpgart: Maximum main memory to use for agp memory: 439M
agpgart: AGP aperture is 64M @ 0xd0000000
[drm] Initialized radeon 1.9.0 20020828 on minor 0
Serial: 8250/16550 driver $Revision: 1.90 $ 8 ports, IRQ sharing
disabled
ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
parport0: PC-style at 0x378 (0x778) [PCSPP(,...)]
parport0: irq 7 detected
lp0: using parport0 (polling).
Using anticipatory io scheduler
Floppy drive(s): fd0 is 1.44M
FDC 0 is a post-1991 82077
loop: loaded (max 8 devices)
3c59x: Donald Becker and others. www.scyld.com/network/vortex.html
0000:02:01.0: 3Com PCI 3c920 Tornado at 0x9000. Vers LK1.1.19
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with
idebus=xx
NFORCE2: IDE controller at PCI slot 0000:00:09.0
NFORCE2: chipset revision 162
NFORCE2: not 100% native mode: will probe irqs later
NFORCE2: BIOS didn't set cable bits correctly. Enabling workaround.
ide: Assuming 33MHz system bus speed for PIO modes; override with
idebus=xx
NFORCE2: 0000:00:09.0 (rev a2) UDMA133 controller
    ide0: BM-DMA at 0xf000-0xf007, BIOS settings: hda:DMA, hdb:DMA
    ide1: BM-DMA at 0xf008-0xf00f, BIOS settings: hdc:DMA, hdd:DMA
hda: Maxtor 6Y080P0, ATA DISK drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
hdc: SONY DVD RW DRU-510A, ATAPI CD/DVD-ROM drive
hdd: SAMSUNG CD-ROM SC-152C, ATAPI CD/DVD-ROM drive
ide1 at 0x170-0x177,0x376 on irq 15
hda: max request size: 128KiB
hda: 160086528 sectors (81964 MB) w/7936KiB Cache, CHS=65535/16/63,
UDMA(133)
 /dev/ide/host0/bus0/target0/lun0: p1 p2 < p5 p6 p7 p8 >
hdc: ATAPI 32X DVD-ROM DVD-R CD-R/RW drive, 8192kB Cache, UDMA(33)
Uniform CD-ROM driver Revision: 3.12
hdd: ATAPI 52X CD-ROM drive, 128kB Cache, DMA
ohci1394: $Rev: 1045 $ Ben Collins <bcollins@debian.org>
PCI: Setting latency timer of device 0000:00:0d.0 to 64
ohci1394_0: OHCI-1394 1.1 (PCI): IRQ=[22]  MMIO=[e0083000-e00837ff]  Max
Packet=[2048]
ohci1394_0: SelfID received outside of bus reset sequence
ehci_hcd 0000:00:02.2: EHCI Host Controller
PCI: Setting latency timer of device 0000:00:02.2 to 64
ehci_hcd 0000:00:02.2: irq 21, pci mem e0848000
ehci_hcd 0000:00:02.2: new USB bus registered, assigned bus number 1
PCI: cache line size of 64 is not supported by device 0000:00:02.2
ehci_hcd 0000:00:02.2: USB 2.0 enabled, EHCI 1.00, driver 2003-Jun-13
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 6 ports detected
drivers/usb/host/uhci-hcd.c: USB Universal Host Controller Interface
driver v2.1
drivers/usb/core/usb.c: registered new driver usblp
drivers/usb/class/usblp.c: v0.13: USB Printer Device Class driver
Initializing USB Mass Storage driver...
drivers/usb/core/usb.c: registered new driver usb-storage
USB Mass Storage support registered.
drivers/usb/core/usb.c: registered new driver hid
drivers/usb/input/hid-core.c: v2.0:USB HID core driver
mice: PS/2 mouse device common for all mice
input: ImExPS/2 Logitech Explorer Mouse on isa0060/serio1
serio: i8042 AUX port at 0x60,0x64 irq 12
input: AT Translated Set 2 keyboard on isa0060/serio0
serio: i8042 KBD port at 0x60,0x64 irq 1
Advanced Linux Sound Architecture Driver Version 0.9.7 (Thu Sep 25
19:16:36 2003 UTC).
request_module: failed /sbin/modprobe -- snd-card-0. error = -16
ALSA device list:
  No soundcards found.
NET: Registered protocol family 2
IP: routing cache hash table of 4096 buckets, 32Kbytes
TCP: Hash tables configured (established 32768 bind 65536)
NET: Registered protocol family 1
NET: Registered protocol family 17
kjournald starting.  Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
VFS: Mounted root (ext3 filesystem) readonly.
Mounted devfs on /dev
Freeing unused kernel memory: 168k freed
ieee1394: Host added: ID:BUS[0-00:1023]  GUID[00e018000044dec8]
Adding 2008084k swap on /dev/hda5.  Priority:-1 extents:1
EXT3 FS on hda6, internal journal
i2c_adapter i2c-0: nForce2 SMBus adapter at 0x5000
i2c_adapter i2c-1: nForce2 SMBus adapter at 0x5500
registering 1-002d
registering 1-0049
registering 1-0048
kjournald starting.  Commit interval 5 seconds
EXT3 FS on hda7, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS on hda8, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
PCI: Setting latency timer of device 0000:00:06.0 to 64
intel8x0: clocking to 47451
agpgart: Found an AGP 2.0 compliant device at 0000:00:00.0.
agpgart: Putting AGP V2 device at 0000:00:00.0 into 1x mode
agpgart: Putting AGP V2 device at 0000:03:00.0 into 1x mode
agpgart: Putting AGP V2 device at 0000:03:00.1 into 1x mode
[drm] Loading R200 Microcode

Re: NForce2 pseudoscience stability testing (2.6.0-test11)

[Julien Oster]

Craig Bradney <cbradney@zip.com.au> writes:

Hello Craig,

> I am also using a 2 week old A7N8X Deluxe, v2 with the latest 1007 BIOS.
> I AM able to run 2.6 Test 11 with APIC, Local APIC and ACPI support
> turned on (SMP off, Preemptible Kernel off).

Unfortunately, I have the exact same configuration, with massive
lockups. Could you try executing "hdparm -t /dev/<someharddisk>"
several times and see if it lockups?

Regards,
Julien

Re: NForce2 pseudoscience stability testing (2.6.0-test11)

[Craig Bradney]

Hi Julien

> > I am also using a 2 week old A7N8X Deluxe, v2 with the latest 1007 BIOS.
> > I AM able to run 2.6 Test 11 with APIC, Local APIC and ACPI support
> > turned on (SMP off, Preemptible Kernel off).
> 
> Unfortunately, I have the exact same configuration, with massive
> lockups. Could you try executing "hdparm -t /dev/<someharddisk>"
> several times and see if it lockups?
> 

I just ran it 20 times non stop, also compiling in the background..  +
evolution, apache2, mysql, xchat, mozilla.. gkrellm.. etc No hassles.
Uptime is now over 18 hours.

Spec is:
a7n8x deluxe
2600+ 333mhz (not overclocked)
2x256ddr 400mhz running in dual ddr mode
80gb 8mb cache maxtor (hda) and a dvd rw (hdc) and cd rom (hdd)
radeon 9000 pro

regards
Craig

Re: NForce2 pseudoscience stability testing (2.6.0-test11)

[Craig Bradney]

On Sat, 2003-11-29 at 17:47, Craig Bradney wrote:
> Hi Julien
> 
> > > I am also using a 2 week old A7N8X Deluxe, v2 with the latest 1007 BIOS.
> > > I AM able to run 2.6 Test 11 with APIC, Local APIC and ACPI support
> > > turned on (SMP off, Preemptible Kernel off).
> > 
> > Unfortunately, I have the exact same configuration, with massive
> > lockups. Could you try executing "hdparm -t /dev/<someharddisk>"
> > several times and see if it lockups?
> > 
> 
> I just ran it 20 times non stop, also compiling in the background..  +
> evolution, apache2, mysql, xchat, mozilla.. gkrellm.. etc No hassles.
> Uptime is now over 18 hours.
> 
> Spec is:
> a7n8x deluxe
> 2600+ 333mhz (not overclocked)
> 2x256ddr 400mhz running in dual ddr mode
> 80gb 8mb cache maxtor (hda) and a dvd rw (hdc) and cd rom (hdd)
> radeon 9000 pro
> 

I have the SATA controller disabled by jumper on the motherboard if that
could be one of the differences as I notice you are posting about SATA
too.

Craig

Re: NForce2 pseudoscience stability testing (2.6.0-test11)

[Jussi Laako]

On Sat, 2003-11-29 at 18:34, Julien Oster wrote:

> > I am also using a 2 week old A7N8X Deluxe, v2 with the latest 1007 BIOS.
> > I AM able to run 2.6 Test 11 with APIC, Local APIC and ACPI support
> > turned on (SMP off, Preemptible Kernel off).
> 
> Unfortunately, I have the exact same configuration, with massive
> lockups. Could you try executing "hdparm -t /dev/<someharddisk>"
> several times and see if it lockups?

I don't think this is Linux-related. None of the NForce2 motherboards
with chipset revision same as the one on A7N8X Deluxe rev2 is able to
run memtest86 for 72 hours without errors with any memory tested (about
20 different DIMMs). NForce2 chipset is just broken.


-- 
Jussi Laako <jussi@sonarnerd.net>

Re: NForce2 pseudoscience stability testing (2.6.0-test11)

[Prakash K. Cheemplavam]

Jussi Laako wrote:
> On Sat, 2003-11-29 at 18:34, Julien Oster wrote:
> 
> 
>>>I am also using a 2 week old A7N8X Deluxe, v2 with the latest 1007 BIOS.
>>>I AM able to run 2.6 Test 11 with APIC, Local APIC and ACPI support
>>>turned on (SMP off, Preemptible Kernel off).
>>
>>Unfortunately, I have the exact same configuration, with massive
>>lockups. Could you try executing "hdparm -t /dev/<someharddisk>"
>>several times and see if it lockups?
> 
> 
> I don't think this is Linux-related. None of the NForce2 motherboards
> with chipset revision same as the one on A7N8X Deluxe rev2 is able to
> run memtest86 for 72 hours without errors with any memory tested (about
> 20 different DIMMs). NForce2 chipset is just broken.


Have you taken a look into the other nforce2 thread? A possible 
solution/Patch has been posted.

Re: NForce2 pseudoscience stability testing (2.6.0-test11)

[Pavel Machek]

Hi!

> I am also using a 2 week old A7N8X Deluxe, v2 with the latest 1007 BIOS.
> I AM able to run 2.6 Test 11 with APIC, Local APIC and ACPI support
> turned on (SMP off, Preemptible Kernel off).
> 
> Although the PC hasnt been under constant stress, uptime is over 12
> hours and its not the first time its been up for 12 or more with test 11
> (which was my first 2.6 kernel). Running Gentoo Linux btw.

Try noapic.
								Pavel

-- 
When do you have a heart between your knees?
[Johanka's followup: and *two* hearts?]

Re: NForce2 pseudoscience stability testing (2.6.0-test11)

[Craig Bradney]

Hi,

On Mon, 2003-12-01 at 19:30, Pavel Machek wrote:
> Hi!
> 
> > I am also using a 2 week old A7N8X Deluxe, v2 with the latest 1007 BIOS.
> > I AM able to run 2.6 Test 11 with APIC, Local APIC and ACPI support
> > turned on (SMP off, Preemptible Kernel off).
> > 
> > Although the PC hasnt been under constant stress, uptime is over 12
> > hours and its not the first time its been up for 12 or more with test 11
> > (which was my first 2.6 kernel). Running Gentoo Linux btw.
> 
> Try noapic.
> 								Pavel

To see if it breaks? 
Im on just about 3 days uptime here with 2.6 test 11.. 

Craig

Re: NForce2 pseudoscience stability testing (2.6.0-test11)

[Lenar Lõhmus]

Hello,

Julien Oster wrote:

> No, it's most evidently a mainboard problem, as everybody using an
> ASUS A7N8X (Deluxe) reported so far that the mainboard will lock up
> completely unless you turn of ACPI, APIC and local APIC. There is no
> other possibility to work this lockup madness around, as many users of
> that mainboard including me really tried *everything*.
> 
> We know that other NForce2 Mainboards don't have this kind of problem,
> but sadly that isn't of any help whatsoever for us A7N8X users.

I can't agree. I've had experiences with two Epox mobos - 8RDA+ running
2.6-test kernels and 8RDA3+ running 2.4.22 kernel.

Both of them locked completely up sometimes (that was after week or so
without reboot). It seems that compiling Local-APIC out of kernel has
stopped this behaviour. It's been about a month without lockups for 2.4
machine. 2.6 hasn't locked up either but it gets a new kernel and a reboot
every week anyway.

Actually the machine with 2.4 kernel run initially 1.5 months without a
glitch (and Local-APIC compiled in) before it started to lock up weekly. I
don't know why. Anyway as I said disabling Local-APIC has stopped all those
lockups.

Lenar

Re: NForce2 pseudoscience stability testing (2.6.0-test11)

[Craig Bradney]

Jump down for my replies..


On Wed, 2003-12-03 at 00:36, b@netzentry.com wrote:
> Regardless of BIOS version, doesn’t the kernel get to
> fix values if things are "wrong?" I've seen this message
> on several boards where various tables and ACPI and APIC
> things are "fixed up." The only reason I want to find out so bad
> is that board survives unusual amounts of abuse on Windows 2000. (I 
> havent been able to hang Windows as Prakash had.)
> 
> Right now I can't even afford to test 2.6.0.test11 in terms
> of time but very similar problems exist in 2.4, suggesting
> something fundamental?
> 
> About the IDE, it seems to be the easiest way to promote the
> problem but time seems to be the biggest factor. Some have
> suggested wrt this NFORCE2 problem that idle time makes it
> worse, but I've seen the hang under both conditions.

Not idle time.. my PC idles (with KDE/xchat/evolution running , if that
is idling :)) while i am out or sleeping.. thats at least 4 hours non
stop per day...

> I have a very minimal set of things running on this board, I
> shut off the USB1.x and 2.0 controller, jumpered the Si SATA
> off and turned of Audio and the NVIDIA Lan. (Prakash suggested
> the Si SATA was the evil but I have it jumpered off.)

Audio on and used, USB 2.0, 1.x on but nothing plugged, NVIDIA lan off,
3com lan on and connected at 100Mbit.

> For me the formula to reproduce this problem is this simple:
> - Do anything (including passing the noapic nolapix noapixio etc)
> in a UP-kernel with APIC compiled in, get hang.
> - To avoid the problem, recompile the UP-kernel with APIC turned
> off.
> 
> What probably isnt the problem:
> - Motherboard flavor (This problem has cropped up on all nforce2 boards)

 a7n8x deluxe v2 with standard clocked athlon xp 2600+

> - BIOS (This problem can change nature with a BIOS rev, but I havent 
> seen it go away and I tried several).

 bios 1007.

> - SATA - problem appears even if SATA is shut off via jumper, as does Craig.

SATA is shut off on jumper. no SATA in kernel

> - Memory - I swapped memory in a test to see. I also tried the dual 
> channel and the single channel mode. No change.

dual channel 2x256mb

> - SMP / UP / passed flags Julien said: "I run strictly non-SMP kernels 
> and they always crash if APIC (or local APIC?) is enabled." - I see the 
> same things.

smp off, preempt off. lapic on, apic on, acpi on

> (Julien also suggest a quick way to see if the system is stable: type 
> hdparm -t /dev/hd<someharddrive> several times).

as my uptime below suggests.. that didnt hurt a thing. I havent rebooted
since that test.

> - ASUS. I have a rev2.0 PCB, and several rev 1.x PCB, and they all 
> suffer. Others also report boards from different manufacturers hanging 
> with the NFORCE2. (Prakash: Abit NF7-S V2.0), Lenar (Epox 8RDA+ , 8RDA3+  )
> - Kernel 2.4 or 2.6 specifically. This problem occurs both in later 2.6 
> builds and 2.4.23 (and below)
> - IDE (NFORCE/AMD IDE driver in kernel) It seems the problem is easily 
> exacerbated by IDE, but I think that this is not the root cause. In 
> NO-APIC mode the IDE behaves reliably.
> 
> 
> Craig said he ran it for 18 hours with abuse, including Juliens hdparm 
> test.


Uptime is 4 days 1:55 and counting...


Things I can remember running in that time:
apache, mysql, proftpd, kde, evolution, xchat2, mozilla, konsole,
scribus, any updates including gcc 3.2.3 from 3.2.2 that came through
gentoo's portage system, gcc recompilation of scribus quite often (cvs
updates and own coding), gdb for about 3 hours finding one scribus
segfault testing over and over again with many crashes (fixed now btw
for those scribus users out there :)) 


> -> Craig, which kernel are you using? Distro (RedHat Taroon's kernel has 
> LAPIC turned off)? PCB Rev of motherboard? Bios revision? Whats the 
> lspci, cat /proc/interrupts look like? dmesg?

I'm using Gentoo's gentoo-dev-sources 2.6.0_beta11 which is 2.6 test11
plus the patches to be found at:
http://dev.gentoo.org/~brad_mssw/kernel_patches/2.6.0/genpatches-0.6/

They have released a 2.6_beta11-r1 that I ahvent upgraded to which uses 
http://dev.gentoo.org/~brad_mssw/kernel_patches/2.6.0/genpatches-0.7/

and i notice there is a 0.8 directory.


So.. sorry if my comments have misled.. its not exactly standard 2.6 now
that I do check it. There is one nvidia nforce network patch. 

As above, PCB is 2.0, BIOS is standard 1007 from ASUS.

lspci and proc/interrupts follow. dmesg has been wiped out by some
packet command errors with drive seek errors on hdc (dvdrw) from when i
was playing music with that drive.

-----
lspci:
00:00.0 Host bridge: nVidia Corporation nForce2 AGP (different version?)
(rev c1)
00:00.1 RAM memory: nVidia Corporation nForce2 Memory Controller 1 (rev
c1)
00:00.2 RAM memory: nVidia Corporation nForce2 Memory Controller 4 (rev
c1)
00:00.3 RAM memory: nVidia Corporation nForce2 Memory Controller 3 (rev
c1)
00:00.4 RAM memory: nVidia Corporation nForce2 Memory Controller 2 (rev
c1)
00:00.5 RAM memory: nVidia Corporation nForce2 Memory Controller 5 (rev
c1)
00:01.0 ISA bridge: nVidia Corporation nForce2 ISA Bridge (rev a4)
00:01.1 SMBus: nVidia Corporation nForce2 SMBus (MCP) (rev a2)
00:02.0 USB Controller: nVidia Corporation nForce2 USB Controller (rev
a4)
00:02.1 USB Controller: nVidia Corporation nForce2 USB Controller (rev
a4)
00:02.2 USB Controller: nVidia Corporation nForce2 USB Controller (rev
a4)
00:05.0 Multimedia audio controller: nVidia Corporation nForce
MultiMedia audio [Via VT82C686B] (rev a2)
00:06.0 Multimedia audio controller: nVidia Corporation nForce2 AC97
Audio Controler (MCP) (rev a1)
00:08.0 PCI bridge: nVidia Corporation nForce2 External PCI Bridge (rev
a3)
00:09.0 IDE interface: nVidia Corporation nForce2 IDE (rev a2)
00:0c.0 PCI bridge: nVidia Corporation nForce2 PCI Bridge (rev a3)
00:0d.0 FireWire (IEEE 1394): nVidia Corporation nForce2 FireWire (IEEE
1394) Controller (rev a3)
00:1e.0 PCI bridge: nVidia Corporation nForce2 AGP (rev c1)
02:01.0 Ethernet controller: 3Com Corporation 3C920B-EMB Integrated Fast
Ethernet Controller (rev 40)
03:00.0 VGA compatible controller: ATI Technologies Inc Radeon R250 If
[Radeon 9000] (rev 01)
03:00.1 Display controller: ATI Technologies Inc Radeon R250 [Radeon
9000] (Secondary) (rev 01)
-----
cat /proc/interrupts
           CPU0
  0:  350520478          XT-PIC  timer
  1:     346366    IO-APIC-edge  i8042
  2:          0          XT-PIC  cascade
  8:          2    IO-APIC-edge  rtc
  9:          0   IO-APIC-level  acpi
 12:    3568875    IO-APIC-edge  i8042
 14:    2286009    IO-APIC-edge  ide0
 15:     153023    IO-APIC-edge  ide1
 19:   26315864   IO-APIC-level  radeon@PCI:3:0:0
 21:     855007   IO-APIC-level  ehci_hcd, NVidia nForce2, eth0
 22:          3   IO-APIC-level  ohci1394
NMI:          0
LOC:  350520402
ERR:          0
MIS:          0
-----
> -> Josh, Craig & anyone else who gets this working on 2.6.test11 or some 
> other fork of 2.6 can they please try 2.4.23-release as well and see if 
> the machine hangs as well?

I was running gentoo's 2.4.23 pre 8 before this.. its still on the
machine. I get no hangs with it.

This machine has never run Win* (its only 3 weeks old). Wouldnt go near
an Uber BIOS on a still warranted motherboard.

Hope some of it helps.

Craig


> The Linux APIC code generically works on most other hardware. Something 
> specific to the NFORCE2 chips and its interaction with Linux's APIC code 
> causes the hard hangs. The Windows 2000's APIC code was made before the 
> NFORCE2 existed, and it seems to run fine there.
> 
> - About that Uber BIOS bios for the Asus Deluxe board, Anyone running 
> this: a) do you really want to run a hacked bios when other OS run fine 
> on the unhacked BIOS b) do you believe that any of the un-hidden 
> settings the uber bios or settings you may have changed helps solve this 
> problem?
> 
> These bugs on the LK Bugzilla seem related:
> http://bugme.osdl.org/show_bug.cgi?id=1203
> 
> Loosely related:
> http://bugme.osdl.org/show_bug.cgi?id=1530
> http://bugme.osdl.org/show_bug.cgi?id=1440
> http://bugme.osdl.org/show_bug.cgi?id=1269
> 
> 
> Does anyone know which developers would be interested in looking at 
> this? I think it would be better if a specific
> patch fixed this problem than try a kernel from bitkeeper
> on a daily basis and wait for the problem to go away without
> ever knowing what caused it.
> 
> 
> 
> 
> 
>  > To me the strangest thing is that when I first got this
>  > board a month or so ago it would hang with APIC or LAPIC
>  > enabled. Now it works fine without disabling APIC. All I
>  > did was update the BIOS and use it for a while with APIC
>  > disabled. 2.6.0-test9-mm through 2.6.0-test11 all work just
>  > fine. Still at the same time some people are reporting that
>  > it works, some are reporting that it doesn't. I probably
>  > wouldn't think to much of this except I was one of the ones
>  > that said APIC causes crashes with IDE load, but now it
>  > doesn't?
>  >
> 
> 
> 
>  > On approximately Tue, Dec 02, 2003 at 10:13:46AM +0000,
>  > ross.alexander wrote: Alistair,
>  >
>  > I upgraded the BIOS about a week ago to 1007. I personally
>  > found it to be less stable than 1006. I don't believe it is
>  > a problem with my hardware combination since it has been
>  > stable for long periods of time. I was running the SMP
>  > kernel simply because I (wrongly) presumed a) you needed it
>  > to get the IO-APIC working, and b) it didn't do any harm.
>  >
>  > It is clear that the UP kernel is considerable more stable
>  > than the SMP kernel. This is a very useful fact since it
>  > suggests that it is not a problem with the IDE device
>  > driver per se. The whole purpose of my testing is to try to
>  > determine which options increased the stability and hence
>  > highlight where the problem could be.
>  >
>  > One of the reasons I don't like ACPI is the huge amount of
>  > additional complexity it adds and the amount of stuff it
>  > could screw up. Now I have not heard that any of the VIA
>  > KTxxx based motherboards have any problems. If this is true
>  > then the problem does not lie with the LAPIC, since that is
>  > in the processor, not the MB. The fact that it seems to
>  > only occur with the NForce2 chipset means it could well be
>  > some interrupt coming into the LAPIC from Interrupt Bus.
>  > However I certainly don't claim to be an expert on this so
>  > I could well be talking complete crap.
>  >
>  > Conclusion: More testing required.
>  >
>  > Cheers,
>  >
>  > Ross
>  >
>  > Alistair John Strachan <s0348365 28/11/2003
>  > 04:46 p.m.
>  >
>  > To: ross.alexander
>  > <brendan cc: linux-kernel
>  > Subject: Re: NForce2 pseudoscience stability testing
>  > (2.6.0-test11)
>  >
>  > On Friday 28 November 2003 15:13,
>  > ross.alexander
>  >
>  > The conclusion to this is the problem is in Local APIC with
>  > SMP. I'm not saying this is actually true only that is what
>  > the data suggests. If anybody wants me to try some other
>  > stuff feel free to suggest ideas.
>  >
>  > Cheers,
>  >
>  > Ross
>  >
>  > It's evidently a configuration problem, albeit BIOS,
>  > mainboard revision, memory quality, etc. because I and many
>  > others like me are able to run Linux 2.4/2.6 with all the
>  > options you tested and still achieve absolute stability, on
>  > the nForce 2 platform.
>  >
>  > My system is an EPOX 8RDA+, with an Athlon 2500+ (Barton)
>  > overclocked to 2.2Ghz, and 2x256MB TwinMOS PC3200 dimms.
>  > FSB is at 400Mhz, and the ram timings are 4,2,2,2. One
>  > might expect such a configuration to be unstable,
>  >
>  > but it is not.
>  >
>  > I'm currently running 2.6.0-test10-mm1 with full ACPI (+
>  > routing), APIC and local APIC, no preempt, UP, and
>  > everything has been rock-solid, despite the machine being
>  > under constant 100% CPU load and fairly active IO load.
>  >
>  > Also, many others have found that just disabling local apic
>  > (and the MPS setting in the BIOS) as well as ACPI solves
>  > their problem, so I'm skeptical that SMP really causes
>  > *nForce 2 specific* instability.
>  >
>  > -- Cheers, Alistair.
>  >
>  > personal: alistair()devzero!co!uk university:
>  > s0348365()sms!ed!ac!uk student: CS/AI Undergraduate
>  > contact: 7/10 Darroch Court, University of Edinburgh.
>  >
>  > - To unsubscribe from this list: send the line "unsubscribe
>  > linux-kernel" in the body of a message to
>  > majordomo@vger.kernel.org More majordomo info at
>  > http://vger.kernel.org/majordomo-info.html Please read the
>  > FAQ at http://www.tux.org/lkml/
> 

Re: NForce2 pseudoscience stability testing (2.6.0-test11)

[Prakash K. Cheemplavam]

> smp off, preempt off. lapic on, apic on, acpi on

Why haven't you enabled preempt? Does it lock with preempt on?

Prakash

Re: NForce2 pseudoscience stability testing (2.6.0-test11)

[Craig Bradney]

On Wed, 2003-12-03 at 01:48, Prakash K. Cheemplavam wrote:
> > smp off, preempt off. lapic on, apic on, acpi on
> 
> Why haven't you enabled preempt? Does it lock with preempt on?
> 

Having been more a lurker on the list before this issue, I had read that
there were some preempt issues with 2.6.. so I turned it off. No idea if
it locks with preempt on. Next time I do a recompile Ill try it out.

Craig

> Prakash
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
> 

Re: NForce2 pseudoscience stability testing (2.6.0-test11)

[bill davidsen]

In article <3FCD32F5.2050002@gmx.de>,
Prakash K. Cheemplavam <prakashkc@gmx.de> wrote:
| > smp off, preempt off. lapic on, apic on, acpi on
| 
| Why haven't you enabled preempt? Does it lock with preempt on?

I haven't found preempt to cause problems with my applications, but
neither have I seen any significant gain in throughput or responsiveness
in 2.6. I did see small gains in 2.4, but not enough to motivate me to
add the feature as a patch or even, in 2.6, enable it as an option.

I don't know about the original poster, but the reports of problems
discourage exploration unless the application is likely to benefit from
slight gains in response and to have multiple tasks of different
priority running.

Have you seen a benefit from preempt? And if so, what application and
how much? I may not be doing anything which benefits from preempt enough
to notice (news, mail and dns servers, desktops), but other than dns on
2.4 I haven't seen improvement.

enlightenmet, please?
-- 
bill davidsen <davidsen@tmr.com>
  CTO, TMR Associates, Inc
Doing interesting things with little computers since 1979.

Re: NForce2 pseudoscience stability testing (2.6.0-test11)

[Prakash K. Cheemplavam]

bill davidsen wrote:
> In article <3FCD32F5.2050002@gmx.de>,
> Prakash K. Cheemplavam <prakashkc@gmx.de> wrote:
> | > smp off, preempt off. lapic on, apic on, acpi on
> | 
> | Why haven't you enabled preempt? Does it lock with preempt on?
> 
[snip]
> Have you seen a benefit from preempt? And if so, what application and
> how much? I may not be doing anything which benefits from preempt enough
> to notice (news, mail and dns servers, desktops), but other than dns on
> 2.4 I haven't seen improvement.
> 
> enlightenmet, please?

Well, I am fairly new to Linux. Only since a month or so I am regurlarly 
using Linux and only since 2.6 kernel. I always used preempt and had no 
problems. The only problem I have, is with APIC. 2.6 is very smooth for 
me. I don't know whether it is because of preempt or not. I just was 
curious, why Craig didn't use it and whether the is a connection.

Prakash

Re: NForce2 pseudoscience stability testing (2.6.0-test11)

[Ian Kumlien]

[-- Attachment #1: Type: text/plain, Size: 1832 bytes --]

On Wed, 2003-12-03 at 00:36, b@netzentry.com wrote:
> Right now I can't even afford to test 2.6.0.test11 in terms
> of time but very similar problems exist in 2.4, suggesting
> something fundamental?

2.6.0-test11 deadlocked after less than a hour here.

> About the IDE, it seems to be the easiest way to promote the
> problem but time seems to be the biggest factor. Some have
> suggested wrt this NFORCE2 problem that idle time makes it
> worse, but I've seen the hang under both conditions.

Well, IDE is what i'd blame. My original experience about lost
interrupts leads me to ide. Since i never loose interrupts without
io-apic.

Also, i tried to get it running with the ide cable that came with the
board but that caused my 60 gig Quantum and my 80 gig Seagate disks to
show up as 8mb disks with garbled names so i skipped that =)
(2.6 also mentions something about cable info bits not set properly)

I use USB 2.0 and 1.1. I have also disabled audio and lan.
A7N8X-X Bios 1007 (Nforce2-400).

> The Linux APIC code generically works on most other hardware. Something 
> specific to the NFORCE2 chips and its interaction with Linux's APIC code 
> causes the hard hangs. The Windows 2000's APIC code was made before the 
> NFORCE2 existed, and it seems to run fine there.

Well, IO-APIC without the amd/nvidia driver works, although a lost
interrupt stalls the machine for a annoying-ammount-of-time.

> - About that Uber BIOS bios for the Asus Deluxe board, Anyone running 
> this: a) do you really want to run a hacked bios when other OS run fine 
> on the unhacked BIOS b) do you believe that any of the un-hidden 
> settings the uber bios or settings you may have changed helps solve this 
> problem?

Yeah, anyone that has checked the changes?

-- 
Ian Kumlien <pomac@vapor.com>

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

RE: NForce2 pseudoscience stability testing (2.6.0-test11)

[Allen Martin]

> -----Original Message-----
> From: Ian Kumlien [mailto:pomac@vapor.com] 
> Sent: Tuesday, December 02, 2003 4:47 PM
>
> On Wed, 2003-12-03 at 00:36, b@netzentry.com wrote:
> > About the IDE, it seems to be the easiest way to promote the
> > problem but time seems to be the biggest factor. Some have
> > suggested wrt this NFORCE2 problem that idle time makes it
> > worse, but I've seen the hang under both conditions.
> 
> Well, IDE is what i'd blame. My original experience about lost
> interrupts leads me to ide. Since i never loose interrupts without
> io-apic.

Can someone who has a system showing this problem try booting from a PCI IDE
card to see if it makes any difference?  I'd try the experiemnt here, but I
can't reproduce the hanging that's being reported.

-Allen

RE: NForce2 pseudoscience stability testing (2.6.0-test11)

[Ian Kumlien]

[-- Attachment #1: Type: text/plain, Size: 684 bytes --]

On Wed, 2003-12-03 at 01:58, Allen Martin wrote:
> > -----Original Message-----
> > From: Ian Kumlien [mailto:pomac@vapor.com] 
> > Sent: Tuesday, December 02, 2003 4:47 PM

>  
> > Well, IDE is what i'd blame. My original experience about lost
> > interrupts leads me to ide. Since i never loose interrupts without
> > io-apic.
> 
> Can someone who has a system showing this problem try booting from a PCI IDE
> card to see if it makes any difference?  I'd try the experiemnt here, but I
> can't reproduce the hanging that's being reported.

Or just to verify boot a kernel without the nvidia/amd ide driver and
io-apic enabled.

-- 
Ian Kumlien <pomac@vapor.com>

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: NForce2 pseudoscience stability testing (2.6.0-test11)

[b]

How is the performance of the generic IDE driver?

My experience that it was almost unusable (kernel 2.4.22,
2.4.23) (fsck taking hours, etc)

 >>>On Wed, 2003-12-03 at 01:58, Allen Martin wrote: -----Original
 >>>Message----- From: Ian Kumlien [mailto:pomac@vapor.com] Sent:
 >>>Tuesday, December 02, 2003 4:47 PM
 >>>
 >>>Well, IDE is what i'd blame. My original experience about lost
 >>>interrupts leads me to ide. Since i never loose interrupts
 >>>without io-apic.
 >>
 >>Can someone who has a system showing this problem try booting
 >>from  a PCI IDE card to see if it makes any difference? I'd try
 >>the experiment here, but I can't reproduce the hanging that's
 >>being reported.

 >Or just to verify boot a kernel without the nvidia/amd ide driver
 >and io-apic enabled.
 >
 > -- Ian Kumlien

Re: NForce2 pseudoscience stability testing (2.6.0-test11)

[Ian Kumlien]

[-- Attachment #1: Type: text/plain, Size: 659 bytes --]

On Wed, 2003-12-03 at 02:23, b@netzentry.com wrote:
> How is the performance of the generic IDE driver?
> 
> My experience that it was almost unusable (kernel 2.4.22,
> 2.4.23) (fsck taking hours, etc)

Thats not the issue... The issue is if the machine survives or crashes.
Again, it locks up for quite some time but it always comes back. And you
get a "hda lost interrupt" message in dmesg.

If we all have that, and deadlock when using the amd/nvidia driver..
then we know that that might be the fault. The machine still locks for a
while so, it's not just the ide, but it might be a good place to start.

-- 
Ian Kumlien <pomac@vapor.com>

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

RE: NForce2 pseudoscience stability testing (2.6.0-test11)

[Allen Martin]

> -----Original Message-----
> From: b@netzentry.com [mailto:b@netzentry.com] 
> Sent: Tuesday, December 02, 2003 5:23 PM
> How is the performance of the generic IDE driver?
> 
> My experience that it was almost unusable (kernel 2.4.22,
> 2.4.23) (fsck taking hours, etc)
> 

You won't be able to use DMA without the AMD/nForce driver, so yes it will
be very slow.  I'd try the add-in card if you have one available, it will be
more similar to the config that fails but just with a different controller.

-Allen

Re: NForce2 pseudoscience stability testing (2.6.0-test11)

[walt]

Josh McKinney wrote:
> To me the strangest thing is that when I first got this board a month or
> so ago it would hang with APIC or LAPIC enabled.  Now it works fine
> without disabling APIC.  All I did was update the BIOS and use it for a
> while with APIC disabled...

Does the new BIOS use different defaults for memory timing, bus speed, etc?
Did you change any of the default settings in the BIOS?

RE: NForce2 pseudoscience stability testing (2.6.0-test11)

[b]

 >Subject: Re: NForce2 pseudoscience stability testing (2.6.0-test11)
 >>Josh McKinney wrote:
 >> To me the strangest thing is that when I first got this
 >>board a month or
 >> so ago it would hang with APIC or LAPIC enabled.  Now it works
 >>fine
 >> without disabling APIC.  All I did was update the BIOS and
 >>use it for a
 >> while with APIC disabled...
 >
 >Does the new BIOS use different defaults for memory timing,
 >bus speed, etc?
 >Did you change any of the default settings in the BIOS?
 >
-- I don't think this issue has anything to do with motherboard
maker or BIOS rev. Most of the people with this problem are
not overclocking and have stable machines with other OSes or
under certain conditions namely:

* In general NForce2 boards are stable under windows 2000
- a far as I can tell

* The boards are stable under certain conditions. The final
test for this (Proposed by Allen Martin
[AMartin at nvidia ! com] is to get a stable well supported
PCI-IDE add in card and ignore the "AMD/NVIDIA" IDE onboard.
(First pointed out by Ian Kumlien I believe)
"If we all have that, and deadlock when using the amd/nvidia
driver.. then we know that that might be the fault. The
machine still locks for a while so, it's not just the ide,
  but it might be a good place to start."

* NForce2 boards are stable when using APIC and using generic
IDE driver. This is painfully slow but is stable.

-- In general: I dont think it should be so easy to blame
the BIOS. If one isnt overclocking and using the SPD on the
memory and using conservative settings, what difference
should that make? And if the board is stable with another
OS I take this "BIOS blaming" and basically throw it out. BIOS
is a deprecated arcane ridiculous thing and should never be
trusted. I have seen on several nicer dual SCSI based
machines messages on boot about certain values being changed
or fixed up.

-- Fixing this for 2.4.x too is important so be sure to try
and find out if 2.4.23 hangs if you get a stable 2.6 thing
going.

Thanks everyone for your continued interest in this, I'll
try and test the no-onboard-PATA + UP LAPIC and IOAPIC and
add-in-card-PATA with no onboard PATA + + UP LAPIC and IOAPIC
when I get a spare moment which is rare.


PS: If you are being CCed and dont want to be, let me know
Some people arent on the list.

Re: NForce2 pseudoscience stability testing (2.6.0-test11)

[Jesse Allen]

On Wed, Dec 03, 2003 at 05:41:33PM -0800, b@netzentry.com wrote:
> >Subject: Re: NForce2 pseudoscience stability testing (2.6.0-test11)
> >>Josh McKinney wrote:
> >> To me the strangest thing is that when I first got this
> >>board a month or
> >> so ago it would hang with APIC or LAPIC enabled.

I have just bought an nForce2 board - a Shuttle AN35N Ultra.  I just got it and set it up just yesterday and found the same thing with linux kernel 2.6.0-test11.  It is simple to trigger it too.  I just do a large recursive grep:  "grep -R any ~/linux-source/*"  deadlocks almost immediately.  Starting a kernel compile, the same occurs (which is how I discovered it in the first place).


> >>  Now it works
> >>fine
> >> without disabling APIC.  All I did was update the BIOS and
> >>use it for a
> >> while with APIC disabled...
> >
> >Does the new BIOS use different defaults for memory timing,
> >bus speed, etc?
> >Did you change any of the default settings in the BIOS?
> >
...
> -- In general: I dont think it should be so easy to blame
> the BIOS. If one isnt overclocking and using the SPD on the
> memory and using conservative settings, what difference
> should that make? And if the board is stable with another
> OS I take this "BIOS blaming" and basically throw it out. BIOS
> is a deprecated arcane ridiculous thing and should never be
> trusted.

I don't think it could be the BIOS either, as this occurs on boards from different manufacturers.  But like you say, the BIOS is old stuff, and linux pretty much handles on its own after it gets running.


> 
> * The boards are stable under certain conditions. The final
> test for this (Proposed by Allen Martin
> [AMartin at nvidia ! com] is to get a stable well supported
> PCI-IDE add in card and ignore the "AMD/NVIDIA" IDE onboard.
...
> 
> Thanks everyone for your continued interest in this, I'll
> try and test the no-onboard-PATA + UP LAPIC and IOAPIC and
> add-in-card-PATA with no onboard PATA + + UP LAPIC and IOAPIC
> when I get a spare moment which is rare.

I suppose I could try right now.  I don't have a pci ide with me right now, but I do have pci scsi cards.  But doesn't running with the generic ide driver basically prove the same thing?  APIC & Generic IDE: works, PIC & nForce IDE: works, APIC & nForce IDE: deadlocks.  It's not like we are expecting faulty nforce ide hardware, or are we?


Jesse

Re: NForce2 pseudoscience stability testing (2.6.0-test11)

[Prakash K. Cheemplavam]

> 
>>Thanks everyone for your continued interest in this, I'll
>>try and test the no-onboard-PATA + UP LAPIC and IOAPIC and
>>add-in-card-PATA with no onboard PATA + + UP LAPIC and IOAPIC
>>when I get a spare moment which is rare.

I don't think that the AMD IDE is the problem. I have compiled it in, as 
well, but I am using the onboard SATA. Since this can be considered as 
an pci-card (the chip is connected to the pci bridge) I think ölocking 
occurs on high traffic on PCI bus. Like now I get over 60mb/s with my 
HD. Formerly I got only 25mb/s. BEfore I could do some rounds of hdparm 
-t, before it locks. Now it locks immediatly when doing hdparm -t when 
APIC is enabled.

SO, I think it is not IDE specific. DOes anybody have gigabit network 
card? MAybe that oe should try to push something big through it (without 
reading from hd). If that leads to lock up we have a semi proof that it 
is due to high traffic on pci-bus.

Re: NForce2 pseudoscience stability testing (2.6.0-test11)

[Josh McKinney]

On approximately Wed, Dec 03, 2003 at 05:41:33PM -0800, b@netzentry.com wrote:

Comments Below

> >Subject: Re: NForce2 pseudoscience stability testing (2.6.0-test11)
> >
> -- I don't think this issue has anything to do with motherboard
> maker or BIOS rev. Most of the people with this problem are
> not overclocking and have stable machines with other OSes or
> under certain conditions namely:
> 
> * In general NForce2 boards are stable under windows 2000
> - a far as I can tell
> 
> * The boards are stable under certain conditions. The final
> test for this (Proposed by Allen Martin
> [AMartin at nvidia ! com] is to get a stable well supported
> PCI-IDE add in card and ignore the "AMD/NVIDIA" IDE onboard.
> (First pointed out by Ian Kumlien I believe)
> "If we all have that, and deadlock when using the amd/nvidia
> driver.. then we know that that might be the fault. The
> machine still locks for a while so, it's not just the ide,
>  but it might be a good place to start."
> 
> * NForce2 boards are stable when using APIC and using generic
> IDE driver. This is painfully slow but is stable.

I am running rock solid here with APIC and amd ide driver:

           CPU0       
  0:   29098620          XT-PIC  timer
  1:      45842    IO-APIC-edge  i8042
  2:          0          XT-PIC  cascade
  8:          1    IO-APIC-edge  rtc
  9:          0   IO-APIC-level  acpi
 14:         54    IO-APIC-edge  ide0
 15:     122855    IO-APIC-edge  ide1
 19:    2202635   IO-APIC-level  nvidia
 20:     138501   IO-APIC-level  ohci_hcd, eth0
 21:     206273   IO-APIC-level  ehci_hcd, NVidia nForce2
 22:     233751   IO-APIC-level  ohci_hcd
NMI:          0 
LOC:   29097603 
ERR:          0
MIS:          0

Any number of kernel compiles, grep, finds, hdparm -t's etc don't crash.

> 
> -- In general: I dont think it should be so easy to blame
> the BIOS. If one isnt overclocking and using the SPD on the
> memory and using conservative settings, what difference
> should that make? And if the board is stable with another
> OS I take this "BIOS blaming" and basically throw it out. BIOS
> is a deprecated arcane ridiculous thing and should never be
> trusted. I have seen on several nicer dual SCSI based
> machines messages on boot about certain values being changed
> or fixed up.
> 

I am running the "Uber" BIOS just for fun, but I don't think that it has
anything that would address this issue.  I am also running a 400FSB with
mem at the same speed, 5-2-2-2 timings.

> -- Fixing this for 2.4.x too is important so be sure to try
> and find out if 2.4.23 hangs if you get a stable 2.6 thing
> going.

vanilla 2.4.23 also works just the same as 2.6, no crashes or hangs.  I
am not using the SATA so it is jumpered off, that may be a factor.

Here is my .config for 2.6 if it might help.

#
# Automatically generated make config: don't edit
#
CONFIG_X86=y
CONFIG_MMU=y
CONFIG_UID16=y
CONFIG_GENERIC_ISA_DMA=y

#
# Code maturity level options
#
CONFIG_EXPERIMENTAL=y
CONFIG_CLEAN_COMPILE=y
CONFIG_STANDALONE=y
CONFIG_BROKEN_ON_SMP=y

#
# General setup
#
CONFIG_SWAP=y
CONFIG_SYSVIPC=y
# CONFIG_BSD_PROCESS_ACCT is not set
CONFIG_SYSCTL=y
CONFIG_LOG_BUF_SHIFT=14
CONFIG_IKCONFIG=y
CONFIG_IKCONFIG_PROC=y
# CONFIG_EMBEDDED is not set
CONFIG_KALLSYMS=y
CONFIG_FUTEX=y
CONFIG_EPOLL=y
CONFIG_IOSCHED_NOOP=y
CONFIG_IOSCHED_AS=y
CONFIG_IOSCHED_DEADLINE=y
CONFIG_IOSCHED_CFQ=y
# CONFIG_CC_OPTIMIZE_FOR_SIZE is not set

#
# Loadable module support
#
CONFIG_MODULES=y
CONFIG_MODULE_UNLOAD=y
CONFIG_MODULE_FORCE_UNLOAD=y
CONFIG_OBSOLETE_MODPARM=y
# CONFIG_MODVERSIONS is not set
CONFIG_KMOD=y

#
# Processor type and features
#
CONFIG_X86_PC=y
# CONFIG_X86_VOYAGER is not set
# CONFIG_X86_NUMAQ is not set
# CONFIG_X86_SUMMIT is not set
# CONFIG_X86_BIGSMP is not set
# CONFIG_X86_VISWS is not set
# CONFIG_X86_GENERICARCH is not set
# CONFIG_X86_ES7000 is not set
# CONFIG_M386 is not set
# CONFIG_M486 is not set
# CONFIG_M586 is not set
# CONFIG_M586TSC is not set
# CONFIG_M586MMX is not set
# CONFIG_M686 is not set
# CONFIG_MPENTIUMII is not set
# CONFIG_MPENTIUMIII is not set
# CONFIG_MPENTIUM4 is not set
# CONFIG_MK6 is not set
CONFIG_MK7=y
# CONFIG_MK8 is not set
# CONFIG_MELAN is not set
# CONFIG_MCRUSOE is not set
# CONFIG_MWINCHIPC6 is not set
# CONFIG_MWINCHIP2 is not set
# CONFIG_MWINCHIP3D is not set
# CONFIG_MCYRIXIII is not set
# CONFIG_MVIAC3_2 is not set
# CONFIG_X86_GENERIC is not set
CONFIG_X86_CMPXCHG=y
CONFIG_X86_XADD=y
CONFIG_X86_L1_CACHE_SHIFT=6
CONFIG_RWSEM_XCHGADD_ALGORITHM=y
CONFIG_X86_WP_WORKS_OK=y
CONFIG_X86_INVLPG=y
CONFIG_X86_BSWAP=y
CONFIG_X86_POPAD_OK=y
CONFIG_X86_GOOD_APIC=y
CONFIG_X86_INTEL_USERCOPY=y
CONFIG_X86_USE_PPRO_CHECKSUM=y
CONFIG_X86_USE_3DNOW=y
# CONFIG_X86_4G is not set
# CONFIG_X86_SWITCH_PAGETABLES is not set
# CONFIG_X86_4G_VM_LAYOUT is not set
# CONFIG_X86_UACCESS_INDIRECT is not set
# CONFIG_X86_HIGH_ENTRY is not set
# CONFIG_HPET_TIMER is not set
# CONFIG_HPET_EMULATE_RTC is not set
# CONFIG_SMP is not set
CONFIG_PREEMPT=y
CONFIG_X86_UP_APIC=y
CONFIG_X86_UP_IOAPIC=y
CONFIG_X86_LOCAL_APIC=y
CONFIG_X86_IO_APIC=y
CONFIG_X86_TSC=y
# CONFIG_X86_MCE is not set
# CONFIG_TOSHIBA is not set
# CONFIG_I8K is not set
# CONFIG_MICROCODE is not set
# CONFIG_X86_MSR is not set
CONFIG_X86_CPUID=y
# CONFIG_EDD is not set
CONFIG_NOHIGHMEM=y
# CONFIG_HIGHMEM4G is not set
# CONFIG_HIGHMEM64G is not set
# CONFIG_MATH_EMULATION is not set
CONFIG_MTRR=y
# CONFIG_EFI is not set
CONFIG_HAVE_DEC_LOCK=y

#
# Power management options (ACPI, APM)
#
CONFIG_PM=y
# CONFIG_SOFTWARE_SUSPEND is not set
# CONFIG_PM_DISK is not set

#
# ACPI (Advanced Configuration and Power Interface) Support
#
CONFIG_ACPI=y
CONFIG_ACPI_BOOT=y
CONFIG_ACPI_INTERPRETER=y
CONFIG_ACPI_SLEEP=y
CONFIG_ACPI_SLEEP_PROC_FS=y
CONFIG_ACPI_AC=m
CONFIG_ACPI_BATTERY=m
CONFIG_ACPI_BUTTON=m
CONFIG_ACPI_FAN=m
CONFIG_ACPI_PROCESSOR=m
CONFIG_ACPI_THERMAL=m
# CONFIG_ACPI_ASUS is not set
# CONFIG_ACPI_TOSHIBA is not set
# CONFIG_ACPI_DEBUG is not set
CONFIG_ACPI_BUS=y
CONFIG_ACPI_EC=y
CONFIG_ACPI_POWER=y
CONFIG_ACPI_PCI=y
CONFIG_ACPI_SYSTEM=y
# CONFIG_ACPI_RELAXED_AML is not set
# CONFIG_X86_PM_TIMER is not set

#
# APM (Advanced Power Management) BIOS Support
#
# CONFIG_APM is not set

#
# CPU Frequency scaling
#
# CONFIG_CPU_FREQ is not set

#
# Bus options (PCI, PCMCIA, EISA, MCA, ISA)
#
CONFIG_PCI=y
# CONFIG_PCI_GOBIOS is not set
# CONFIG_PCI_GODIRECT is not set
CONFIG_PCI_GOANY=y
CONFIG_PCI_BIOS=y
CONFIG_PCI_DIRECT=y
# CONFIG_PCI_USE_VECTOR is not set
# CONFIG_PCI_LEGACY_PROC is not set
CONFIG_PCI_NAMES=y
# CONFIG_ISA is not set
# CONFIG_MCA is not set
# CONFIG_SCx200 is not set
CONFIG_HOTPLUG=y

#
# PCMCIA/CardBus support
#
# CONFIG_PCMCIA is not set

#
# PCI Hotplug Support
#
# CONFIG_HOTPLUG_PCI is not set

#
# Executable file formats
#
CONFIG_BINFMT_ELF=y
CONFIG_BINFMT_AOUT=y
CONFIG_BINFMT_MISC=y

#
# Device Drivers
#

#
# Generic Driver Options
#
# CONFIG_FW_LOADER is not set

#
# Memory Technology Devices (MTD)
#
# CONFIG_MTD is not set

#
# Parallel port support
#
# CONFIG_PARPORT is not set

#
# Plug and Play support
#
# CONFIG_PNP is not set

#
# Block devices
#
CONFIG_BLK_DEV_FD=y
# CONFIG_BLK_CPQ_DA is not set
# CONFIG_BLK_CPQ_CISS_DA is not set
# CONFIG_BLK_DEV_DAC960 is not set
# CONFIG_BLK_DEV_UMEM is not set
CONFIG_BLK_DEV_LOOP=y
# CONFIG_BLK_DEV_CRYPTOLOOP is not set
# CONFIG_BLK_DEV_NBD is not set
# CONFIG_BLK_DEV_RAM is not set
# CONFIG_BLK_DEV_INITRD is not set
# CONFIG_LBD is not set

#
# ATA/ATAPI/MFM/RLL support
#
CONFIG_IDE=y
CONFIG_BLK_DEV_IDE=y

#
# Please see Documentation/ide.txt for help/info on IDE drives
#
# CONFIG_BLK_DEV_HD_IDE is not set
CONFIG_BLK_DEV_IDEDISK=y
# CONFIG_IDEDISK_MULTI_MODE is not set
# CONFIG_IDEDISK_STROKE is not set
CONFIG_BLK_DEV_IDECD=y
# CONFIG_BLK_DEV_IDETAPE is not set
CONFIG_BLK_DEV_IDEFLOPPY=y
# CONFIG_BLK_DEV_IDESCSI is not set
# CONFIG_IDE_TASK_IOCTL is not set
CONFIG_IDE_TASKFILE_IO=y

#
# IDE chipset support/bugfixes
#
# CONFIG_BLK_DEV_CMD640 is not set
CONFIG_BLK_DEV_IDEPCI=y
# CONFIG_IDEPCI_SHARE_IRQ is not set
# CONFIG_BLK_DEV_OFFBOARD is not set
# CONFIG_BLK_DEV_GENERIC is not set
# CONFIG_BLK_DEV_OPTI621 is not set
# CONFIG_BLK_DEV_RZ1000 is not set
CONFIG_BLK_DEV_IDEDMA_PCI=y
# CONFIG_BLK_DEV_IDEDMA_FORCED is not set
CONFIG_IDEDMA_PCI_AUTO=y
# CONFIG_IDEDMA_ONLYDISK is not set
# CONFIG_IDEDMA_PCI_WIP is not set
CONFIG_BLK_DEV_ADMA=y
# CONFIG_BLK_DEV_AEC62XX is not set
# CONFIG_BLK_DEV_ALI15X3 is not set
CONFIG_BLK_DEV_AMD74XX=y
# CONFIG_BLK_DEV_CMD64X is not set
# CONFIG_BLK_DEV_TRIFLEX is not set
# CONFIG_BLK_DEV_CY82C693 is not set
# CONFIG_BLK_DEV_CS5520 is not set
# CONFIG_BLK_DEV_CS5530 is not set
# CONFIG_BLK_DEV_HPT34X is not set
# CONFIG_BLK_DEV_HPT366 is not set
# CONFIG_BLK_DEV_SC1200 is not set
# CONFIG_BLK_DEV_PIIX is not set
# CONFIG_BLK_DEV_NS87415 is not set
# CONFIG_BLK_DEV_PDC202XX_OLD is not set
# CONFIG_BLK_DEV_PDC202XX_NEW is not set
# CONFIG_BLK_DEV_SVWKS is not set
# CONFIG_BLK_DEV_SIIMAGE is not set
# CONFIG_BLK_DEV_SIS5513 is not set
# CONFIG_BLK_DEV_SLC90E66 is not set
# CONFIG_BLK_DEV_TRM290 is not set
# CONFIG_BLK_DEV_VIA82CXXX is not set
CONFIG_BLK_DEV_IDEDMA=y
# CONFIG_IDEDMA_IVB is not set
CONFIG_IDEDMA_AUTO=y
# CONFIG_DMA_NONPCI is not set
# CONFIG_BLK_DEV_HD is not set

#
# SCSI device support
#
CONFIG_SCSI=m
# CONFIG_SCSI_PROC_FS is not set

#
# SCSI support type (disk, tape, CD-ROM)
#
# CONFIG_BLK_DEV_SD is not set
# CONFIG_CHR_DEV_ST is not set
# CONFIG_CHR_DEV_OSST is not set
# CONFIG_BLK_DEV_SR is not set
# CONFIG_CHR_DEV_SG is not set

#
# Some SCSI devices (e.g. CD jukebox) support multiple LUNs
#
# CONFIG_SCSI_MULTI_LUN is not set
# CONFIG_SCSI_REPORT_LUNS is not set
# CONFIG_SCSI_CONSTANTS is not set
# CONFIG_SCSI_LOGGING is not set

#
# SCSI low-level drivers
#
# CONFIG_BLK_DEV_3W_XXXX_RAID is not set
# CONFIG_SCSI_ACARD is not set
# CONFIG_SCSI_AACRAID is not set
# CONFIG_SCSI_AIC7XXX is not set
# CONFIG_SCSI_AIC7XXX_OLD is not set
# CONFIG_SCSI_AIC79XX is not set
# CONFIG_SCSI_ADVANSYS is not set
# CONFIG_SCSI_MEGARAID is not set
# CONFIG_SCSI_SATA is not set
# CONFIG_SCSI_BUSLOGIC is not set
# CONFIG_SCSI_CPQFCTS is not set
# CONFIG_SCSI_DMX3191D is not set
# CONFIG_SCSI_EATA is not set
# CONFIG_SCSI_EATA_PIO is not set
# CONFIG_SCSI_FUTURE_DOMAIN is not set
# CONFIG_SCSI_GDTH is not set
# CONFIG_SCSI_IPS is not set
# CONFIG_SCSI_INIA100 is not set
# CONFIG_SCSI_SYM53C8XX_2 is not set
# CONFIG_SCSI_QLOGIC_ISP is not set
# CONFIG_SCSI_QLOGIC_FC is not set
# CONFIG_SCSI_QLOGIC_1280 is not set
# CONFIG_SCSI_DC395x is not set
# CONFIG_SCSI_NSP32 is not set
# CONFIG_SCSI_DEBUG is not set

#
# Multi-device support (RAID and LVM)
#
# CONFIG_MD is not set

#
# Fusion MPT device support
#

#
# IEEE 1394 (FireWire) support (EXPERIMENTAL)
#
# CONFIG_IEEE1394 is not set

#
# I2O device support
#
# CONFIG_I2O is not set

#
# Networking support
#
CONFIG_NET=y

#
# Networking options
#
CONFIG_PACKET=y
# CONFIG_PACKET_MMAP is not set
CONFIG_NETLINK_DEV=y
CONFIG_UNIX=y
CONFIG_NET_KEY=y
CONFIG_INET=y
# CONFIG_IP_MULTICAST is not set
# CONFIG_IP_ADVANCED_ROUTER is not set
# CONFIG_IP_PNP is not set
# CONFIG_NET_IPIP is not set
# CONFIG_NET_IPGRE is not set
# CONFIG_ARPD is not set
# CONFIG_INET_ECN is not set
# CONFIG_SYN_COOKIES is not set
CONFIG_INET_AH=m
CONFIG_INET_ESP=m
CONFIG_INET_IPCOMP=m
CONFIG_IPV6=m
# CONFIG_IPV6_PRIVACY is not set
# CONFIG_INET6_AH is not set
# CONFIG_INET6_ESP is not set
# CONFIG_INET6_IPCOMP is not set
# CONFIG_IPV6_TUNNEL is not set
# CONFIG_DECNET is not set
# CONFIG_BRIDGE is not set
# CONFIG_NETFILTER is not set
CONFIG_XFRM=y
# CONFIG_XFRM_USER is not set

#
# SCTP Configuration (EXPERIMENTAL)
#
CONFIG_IPV6_SCTP__=m
# CONFIG_IP_SCTP is not set
# CONFIG_ATM is not set
# CONFIG_VLAN_8021Q is not set
# CONFIG_LLC2 is not set
# CONFIG_IPX is not set
# CONFIG_ATALK is not set
# CONFIG_X25 is not set
# CONFIG_LAPB is not set
# CONFIG_NET_DIVERT is not set
# CONFIG_ECONET is not set
# CONFIG_WAN_ROUTER is not set
# CONFIG_NET_FASTROUTE is not set
# CONFIG_NET_HW_FLOWCONTROL is not set

#
# QoS and/or fair queueing
#
# CONFIG_NET_SCHED is not set

#
# Network testing
#
# CONFIG_NET_PKTGEN is not set
CONFIG_NETDEVICES=y

#
# ARCnet devices
#
# CONFIG_ARCNET is not set
CONFIG_DUMMY=y
# CONFIG_BONDING is not set
# CONFIG_EQUALIZER is not set
# CONFIG_TUN is not set
# CONFIG_ETHERTAP is not set

#
# Ethernet (10 or 100Mbit)
#
CONFIG_NET_ETHERNET=y
CONFIG_MII=y
# CONFIG_HAPPYMEAL is not set
# CONFIG_SUNGEM is not set
CONFIG_NET_VENDOR_3COM=y
CONFIG_VORTEX=m
# CONFIG_TYPHOON is not set

#
# Tulip family network device support
#
CONFIG_NET_TULIP=y
# CONFIG_DE2104X is not set
CONFIG_TULIP=m
# CONFIG_TULIP_MWI is not set
# CONFIG_TULIP_MMIO is not set
# CONFIG_TULIP_NAPI is not set
# CONFIG_DE4X5 is not set
# CONFIG_WINBOND_840 is not set
# CONFIG_DM9102 is not set
# CONFIG_HP100 is not set
CONFIG_NET_PCI=y
# CONFIG_PCNET32 is not set
# CONFIG_AMD8111_ETH is not set
# CONFIG_ADAPTEC_STARFIRE is not set
# CONFIG_B44 is not set
CONFIG_FORCEDETH=m
# CONFIG_DGRS is not set
# CONFIG_EEPRO100 is not set
# CONFIG_E100 is not set
# CONFIG_FEALNX is not set
# CONFIG_NATSEMI is not set
# CONFIG_NE2K_PCI is not set
# CONFIG_8139CP is not set
# CONFIG_8139TOO is not set
# CONFIG_SIS900 is not set
# CONFIG_EPIC100 is not set
# CONFIG_SUNDANCE is not set
# CONFIG_TLAN is not set
# CONFIG_VIA_RHINE is not set

#
# Ethernet (1000 Mbit)
#
# CONFIG_ACENIC is not set
# CONFIG_DL2K is not set
# CONFIG_E1000 is not set
# CONFIG_NS83820 is not set
# CONFIG_HAMACHI is not set
# CONFIG_YELLOWFIN is not set
# CONFIG_R8169 is not set
# CONFIG_SIS190 is not set
# CONFIG_SK98LIN is not set
# CONFIG_TIGON3 is not set

#
# Ethernet (10000 Mbit)
#
# CONFIG_IXGB is not set
# CONFIG_FDDI is not set
# CONFIG_HIPPI is not set
# CONFIG_PPP is not set
# CONFIG_SLIP is not set

#
# Wireless LAN (non-hamradio)
#
# CONFIG_NET_RADIO is not set

#
# Token Ring devices
#
# CONFIG_TR is not set
# CONFIG_NET_FC is not set
# CONFIG_RCPCI is not set
# CONFIG_SHAPER is not set
# CONFIG_NET_POLL_CONTROLLER is not set

#
# Wan interfaces
#
# CONFIG_WAN is not set

#
# Amateur Radio support
#
# CONFIG_HAMRADIO is not set

#
# IrDA (infrared) support
#
# CONFIG_IRDA is not set

#
# Bluetooth support
#
# CONFIG_BT is not set

#
# ISDN subsystem
#
# CONFIG_ISDN_BOOL is not set

#
# Telephony Support
#
# CONFIG_PHONE is not set

#
# Input device support
#
CONFIG_INPUT=y

#
# Userland interfaces
#
CONFIG_INPUT_MOUSEDEV=y
CONFIG_INPUT_MOUSEDEV_PSAUX=y
CONFIG_INPUT_MOUSEDEV_SCREEN_X=1024
CONFIG_INPUT_MOUSEDEV_SCREEN_Y=768
# CONFIG_INPUT_JOYDEV is not set
# CONFIG_INPUT_TSDEV is not set
# CONFIG_INPUT_EVDEV is not set
# CONFIG_INPUT_EVBUG is not set

#
# Input I/O drivers
#
# CONFIG_GAMEPORT is not set
CONFIG_SOUND_GAMEPORT=y
CONFIG_SERIO=y
CONFIG_SERIO_I8042=y
CONFIG_SERIO_SERPORT=y
# CONFIG_SERIO_CT82C710 is not set
# CONFIG_SERIO_PCIPS2 is not set

#
# Input Device Drivers
#
CONFIG_INPUT_KEYBOARD=y
CONFIG_KEYBOARD_ATKBD=y
# CONFIG_KEYBOARD_SUNKBD is not set
# CONFIG_KEYBOARD_XTKBD is not set
# CONFIG_KEYBOARD_NEWTON is not set
CONFIG_INPUT_MOUSE=y
CONFIG_MOUSE_PS2=y
# CONFIG_MOUSE_PS2_SYNAPTICS is not set
# CONFIG_MOUSE_SERIAL is not set
# CONFIG_INPUT_JOYSTICK is not set
# CONFIG_INPUT_TOUCHSCREEN is not set
CONFIG_INPUT_MISC=y
CONFIG_INPUT_PCSPKR=y
# CONFIG_INPUT_UINPUT is not set

#
# Character devices
#
CONFIG_VT=y
CONFIG_VT_CONSOLE=y
CONFIG_HW_CONSOLE=y
# CONFIG_SERIAL_NONSTANDARD is not set

#
# Serial drivers
#
CONFIG_SERIAL_8250=y
# CONFIG_SERIAL_8250_CONSOLE is not set
# CONFIG_SERIAL_8250_ACPI is not set
CONFIG_SERIAL_8250_NR_UARTS=4
# CONFIG_SERIAL_8250_EXTENDED is not set

#
# Non-8250 serial port support
#
CONFIG_SERIAL_CORE=y
CONFIG_UNIX98_PTYS=y
CONFIG_UNIX98_PTY_COUNT=256

#
# I2C support
#
CONFIG_I2C=m
CONFIG_I2C_CHARDEV=m

#
# I2C Algorithms
#
CONFIG_I2C_ALGOBIT=m
CONFIG_I2C_ALGOPCF=m

#
# I2C Hardware Bus support
#
# CONFIG_I2C_ALI1535 is not set
# CONFIG_I2C_ALI15X3 is not set
# CONFIG_I2C_AMD756 is not set
# CONFIG_I2C_AMD8111 is not set
# CONFIG_I2C_ELEKTOR is not set
# CONFIG_I2C_I801 is not set
# CONFIG_I2C_I810 is not set
CONFIG_I2C_NFORCE2=m
# CONFIG_I2C_PIIX4 is not set
# CONFIG_I2C_PROSAVAGE is not set
# CONFIG_I2C_SAVAGE4 is not set
# CONFIG_SCx200_ACB is not set
# CONFIG_I2C_SIS5595 is not set
# CONFIG_I2C_SIS630 is not set
# CONFIG_I2C_SIS96X is not set
# CONFIG_I2C_VIA is not set
# CONFIG_I2C_VIAPRO is not set
# CONFIG_I2C_VOODOO3 is not set

#
# I2C Hardware Sensors Chip support
#
CONFIG_I2C_SENSOR=m
# CONFIG_SENSORS_ADM1021 is not set
# CONFIG_SENSORS_EEPROM is not set
# CONFIG_SENSORS_IT87 is not set
# CONFIG_SENSORS_LM75 is not set
# CONFIG_SENSORS_LM78 is not set
# CONFIG_SENSORS_LM85 is not set
# CONFIG_SENSORS_VIA686A is not set
CONFIG_SENSORS_W83781D=m

#
# Mice
#
# CONFIG_BUSMOUSE is not set
# CONFIG_QIC02_TAPE is not set

#
# IPMI
#
# CONFIG_IPMI_HANDLER is not set

#
# Watchdog Cards
#
# CONFIG_WATCHDOG is not set
# CONFIG_HW_RANDOM is not set
# CONFIG_NVRAM is not set
CONFIG_RTC=m
# CONFIG_GEN_RTC is not set
# CONFIG_DTLK is not set
# CONFIG_R3964 is not set
# CONFIG_APPLICOM is not set
# CONFIG_SONYPI is not set

#
# Ftape, the floppy tape device driver
#
# CONFIG_FTAPE is not set
CONFIG_AGP=y
# CONFIG_AGP_ALI is not set
# CONFIG_AGP_ATI is not set
# CONFIG_AGP_AMD is not set
# CONFIG_AGP_AMD64 is not set
# CONFIG_AGP_INTEL is not set
CONFIG_AGP_NVIDIA=m
# CONFIG_AGP_SIS is not set
# CONFIG_AGP_SWORKS is not set
# CONFIG_AGP_VIA is not set
# CONFIG_DRM is not set
# CONFIG_MWAVE is not set
# CONFIG_RAW_DRIVER is not set
# CONFIG_HANGCHECK_TIMER is not set

#
# Multimedia devices
#
# CONFIG_VIDEO_DEV is not set

#
# Digital Video Broadcasting Devices
#
# CONFIG_DVB is not set

#
# Graphics support
#
CONFIG_FB=y
# CONFIG_FB_CYBER2000 is not set
# CONFIG_FB_IMSTT is not set
# CONFIG_FB_VGA16 is not set
CONFIG_FB_VESA=y
CONFIG_VIDEO_SELECT=y
# CONFIG_FB_HGA is not set
# CONFIG_FB_RIVA is not set
# CONFIG_FB_MATROX is not set
# CONFIG_FB_RADEON is not set
# CONFIG_FB_ATY128 is not set
# CONFIG_FB_ATY is not set
# CONFIG_FB_SIS is not set
# CONFIG_FB_NEOMAGIC is not set
# CONFIG_FB_3DFX is not set
# CONFIG_FB_VOODOO1 is not set
# CONFIG_FB_TRIDENT is not set
# CONFIG_FB_VIRTUAL is not set

#
# Console display driver support
#
CONFIG_VGA_CONSOLE=y
# CONFIG_MDA_CONSOLE is not set
CONFIG_DUMMY_CONSOLE=y
CONFIG_FRAMEBUFFER_CONSOLE=y
CONFIG_PCI_CONSOLE=y
# CONFIG_FONTS is not set
CONFIG_FONT_8x8=y
CONFIG_FONT_8x16=y

#
# Logo configuration
#
CONFIG_LOGO=y
# CONFIG_LOGO_LINUX_MONO is not set
# CONFIG_LOGO_LINUX_VGA16 is not set
CONFIG_LOGO_LINUX_CLUT224=y

#
# Sound
#
CONFIG_SOUND=y

#
# Advanced Linux Sound Architecture
#
CONFIG_SND=m
# CONFIG_SND_SEQUENCER is not set
CONFIG_SND_OSSEMUL=y
CONFIG_SND_MIXER_OSS=m
CONFIG_SND_PCM_OSS=m
# CONFIG_SND_RTCTIMER is not set
# CONFIG_SND_VERBOSE_PRINTK is not set
# CONFIG_SND_DEBUG is not set

#
# Generic devices
#
# CONFIG_SND_DUMMY is not set
# CONFIG_SND_MTPAV is not set
# CONFIG_SND_SERIAL_U16550 is not set
# CONFIG_SND_MPU401 is not set

#
# PCI devices
#
# CONFIG_SND_ALI5451 is not set
# CONFIG_SND_AZT3328 is not set
# CONFIG_SND_CS46XX is not set
# CONFIG_SND_CS4281 is not set
# CONFIG_SND_EMU10K1 is not set
# CONFIG_SND_KORG1212 is not set
# CONFIG_SND_NM256 is not set
# CONFIG_SND_RME32 is not set
# CONFIG_SND_RME96 is not set
# CONFIG_SND_RME9652 is not set
# CONFIG_SND_HDSP is not set
# CONFIG_SND_TRIDENT is not set
# CONFIG_SND_YMFPCI is not set
# CONFIG_SND_ALS4000 is not set
# CONFIG_SND_CMIPCI is not set
# CONFIG_SND_ENS1370 is not set
# CONFIG_SND_ENS1371 is not set
# CONFIG_SND_ES1938 is not set
# CONFIG_SND_ES1968 is not set
# CONFIG_SND_MAESTRO3 is not set
# CONFIG_SND_FM801 is not set
# CONFIG_SND_ICE1712 is not set
# CONFIG_SND_ICE1724 is not set
CONFIG_SND_INTEL8X0=m
# CONFIG_SND_SONICVIBES is not set
# CONFIG_SND_VIA82XX is not set
# CONFIG_SND_VX222 is not set

#
# ALSA USB devices
#
# CONFIG_SND_USB_AUDIO is not set

#
# Open Sound System
#
# CONFIG_SOUND_PRIME is not set

#
# USB support
#
CONFIG_USB=m
# CONFIG_USB_DEBUG is not set

#
# Miscellaneous USB options
#
CONFIG_USB_DEVICEFS=y
CONFIG_USB_BANDWIDTH=y
# CONFIG_USB_DYNAMIC_MINORS is not set

#
# USB Host Controller Drivers
#
CONFIG_USB_EHCI_HCD=m
CONFIG_USB_OHCI_HCD=m
# CONFIG_USB_UHCI_HCD is not set

#
# USB Device Class drivers
#
# CONFIG_USB_AUDIO is not set
# CONFIG_USB_BLUETOOTH_TTY is not set
# CONFIG_USB_MIDI is not set
# CONFIG_USB_ACM is not set
# CONFIG_USB_PRINTER is not set
CONFIG_USB_STORAGE=m
# CONFIG_USB_STORAGE_DEBUG is not set
# CONFIG_USB_STORAGE_DATAFAB is not set
# CONFIG_USB_STORAGE_FREECOM is not set
# CONFIG_USB_STORAGE_ISD200 is not set
# CONFIG_USB_STORAGE_DPCM is not set
# CONFIG_USB_STORAGE_HP8200e is not set
# CONFIG_USB_STORAGE_SDDR09 is not set
# CONFIG_USB_STORAGE_SDDR55 is not set
# CONFIG_USB_STORAGE_JUMPSHOT is not set

#
# USB Human Interface Devices (HID)
#
CONFIG_USB_HID=m
CONFIG_USB_HIDINPUT=y
# CONFIG_HID_FF is not set
CONFIG_USB_HIDDEV=y

#
# USB HID Boot Protocol drivers
#
# CONFIG_USB_KBD is not set
# CONFIG_USB_MOUSE is not set
# CONFIG_USB_AIPTEK is not set
# CONFIG_USB_WACOM is not set
# CONFIG_USB_KBTAB is not set
# CONFIG_USB_POWERMATE is not set
# CONFIG_USB_XPAD is not set

#
# USB Imaging devices
#
# CONFIG_USB_MDC800 is not set
CONFIG_USB_SCANNER=m
# CONFIG_USB_MICROTEK is not set
# CONFIG_USB_HPUSBSCSI is not set

#
# USB Multimedia devices
#
# CONFIG_USB_DABUSB is not set

#
# Video4Linux support is needed for USB Multimedia device support
#

#
# USB Network adaptors
#
# CONFIG_USB_CATC is not set
# CONFIG_USB_KAWETH is not set
# CONFIG_USB_PEGASUS is not set
# CONFIG_USB_RTL8150 is not set
# CONFIG_USB_USBNET is not set

#
# USB port drivers
#

#
# USB Serial Converter support
#
# CONFIG_USB_SERIAL is not set

#
# USB Miscellaneous drivers
#
# CONFIG_USB_TIGL is not set
# CONFIG_USB_AUERSWALD is not set
# CONFIG_USB_RIO500 is not set
# CONFIG_USB_BRLVGER is not set
# CONFIG_USB_LCD is not set
# CONFIG_USB_TEST is not set
# CONFIG_USB_GADGET is not set

#
# File systems
#
CONFIG_EXT2_FS=y
# CONFIG_EXT2_FS_XATTR is not set
CONFIG_EXT3_FS=y
CONFIG_EXT3_FS_XATTR=y
# CONFIG_EXT3_FS_POSIX_ACL is not set
# CONFIG_EXT3_FS_SECURITY is not set
CONFIG_JBD=y
# CONFIG_JBD_DEBUG is not set
CONFIG_FS_MBCACHE=y
# CONFIG_REISERFS_FS is not set
# CONFIG_JFS_FS is not set
# CONFIG_XFS_FS is not set
# CONFIG_MINIX_FS is not set
# CONFIG_ROMFS_FS is not set
# CONFIG_QUOTA is not set
# CONFIG_AUTOFS_FS is not set
# CONFIG_AUTOFS4_FS is not set

#
# CD-ROM/DVD Filesystems
#
CONFIG_ISO9660_FS=m
CONFIG_JOLIET=y
# CONFIG_ZISOFS is not set
# CONFIG_UDF_FS is not set

#
# DOS/FAT/NT Filesystems
#
CONFIG_FAT_FS=m
# CONFIG_MSDOS_FS is not set
CONFIG_VFAT_FS=m
CONFIG_NTFS_FS=m
# CONFIG_NTFS_DEBUG is not set
# CONFIG_NTFS_RW is not set

#
# Pseudo filesystems
#
CONFIG_PROC_FS=y
CONFIG_PROC_KCORE=y
# CONFIG_DEVFS_FS is not set
CONFIG_DEVPTS_FS=y
# CONFIG_DEVPTS_FS_XATTR is not set
# CONFIG_TMPFS is not set
# CONFIG_HUGETLBFS is not set
# CONFIG_HUGETLB_PAGE is not set
CONFIG_RAMFS=y

#
# Miscellaneous filesystems
#
# CONFIG_ADFS_FS is not set
# CONFIG_AFFS_FS is not set
# CONFIG_HFS_FS is not set
# CONFIG_BEFS_FS is not set
# CONFIG_BFS_FS is not set
# CONFIG_EFS_FS is not set
# CONFIG_CRAMFS is not set
# CONFIG_VXFS_FS is not set
# CONFIG_HPFS_FS is not set
# CONFIG_QNX4FS_FS is not set
# CONFIG_SYSV_FS is not set
# CONFIG_UFS_FS is not set

#
# Network File Systems
#
# CONFIG_NFS_FS is not set
# CONFIG_NFSD is not set
# CONFIG_EXPORTFS is not set
# CONFIG_SMB_FS is not set
# CONFIG_CIFS is not set
# CONFIG_NCP_FS is not set
# CONFIG_CODA_FS is not set
# CONFIG_INTERMEZZO_FS is not set
# CONFIG_AFS_FS is not set

#
# Partition Types
#
# CONFIG_PARTITION_ADVANCED is not set
CONFIG_MSDOS_PARTITION=y

#
# Native Language Support
#
CONFIG_NLS=y
CONFIG_NLS_DEFAULT="iso8859-1"
# CONFIG_NLS_CODEPAGE_437 is not set
# CONFIG_NLS_CODEPAGE_737 is not set
# CONFIG_NLS_CODEPAGE_775 is not set
# CONFIG_NLS_CODEPAGE_850 is not set
# CONFIG_NLS_CODEPAGE_852 is not set
# CONFIG_NLS_CODEPAGE_855 is not set
# CONFIG_NLS_CODEPAGE_857 is not set
# CONFIG_NLS_CODEPAGE_860 is not set
# CONFIG_NLS_CODEPAGE_861 is not set
# CONFIG_NLS_CODEPAGE_862 is not set
# CONFIG_NLS_CODEPAGE_863 is not set
# CONFIG_NLS_CODEPAGE_864 is not set
# CONFIG_NLS_CODEPAGE_865 is not set
# CONFIG_NLS_CODEPAGE_866 is not set
# CONFIG_NLS_CODEPAGE_869 is not set
# CONFIG_NLS_CODEPAGE_936 is not set
# CONFIG_NLS_CODEPAGE_950 is not set
# CONFIG_NLS_CODEPAGE_932 is not set
# CONFIG_NLS_CODEPAGE_949 is not set
# CONFIG_NLS_CODEPAGE_874 is not set
# CONFIG_NLS_ISO8859_8 is not set
# CONFIG_NLS_CODEPAGE_1250 is not set
# CONFIG_NLS_CODEPAGE_1251 is not set
# CONFIG_NLS_ISO8859_1 is not set
# CONFIG_NLS_ISO8859_2 is not set
# CONFIG_NLS_ISO8859_3 is not set
# CONFIG_NLS_ISO8859_4 is not set
# CONFIG_NLS_ISO8859_5 is not set
# CONFIG_NLS_ISO8859_6 is not set
# CONFIG_NLS_ISO8859_7 is not set
# CONFIG_NLS_ISO8859_9 is not set
# CONFIG_NLS_ISO8859_13 is not set
# CONFIG_NLS_ISO8859_14 is not set
# CONFIG_NLS_ISO8859_15 is not set
# CONFIG_NLS_KOI8_R is not set
# CONFIG_NLS_KOI8_U is not set
# CONFIG_NLS_UTF8 is not set

#
# Profiling support
#
# CONFIG_PROFILING is not set

#
# Kernel hacking
#
CONFIG_DEBUG_KERNEL=y
# CONFIG_DEBUG_STACKOVERFLOW is not set
# CONFIG_DEBUG_SLAB is not set
# CONFIG_DEBUG_IOVIRT is not set
CONFIG_MAGIC_SYSRQ=y
# CONFIG_DEBUG_SPINLOCK is not set
# CONFIG_DEBUG_PAGEALLOC is not set
# CONFIG_SPINLINE is not set
# CONFIG_DEBUG_INFO is not set
# CONFIG_DEBUG_SPINLOCK_SLEEP is not set
# CONFIG_KGDB is not set
# CONFIG_FRAME_POINTER is not set
CONFIG_X86_EXTRA_IRQS=y
CONFIG_X86_FIND_SMP_CONFIG=y
CONFIG_X86_MPPARSE=y

#
# Security options
#
# CONFIG_SECURITY is not set

#
# Cryptographic options
#
CONFIG_CRYPTO=y
CONFIG_CRYPTO_HMAC=y
# CONFIG_CRYPTO_NULL is not set
# CONFIG_CRYPTO_MD4 is not set
CONFIG_CRYPTO_MD5=m
CONFIG_CRYPTO_SHA1=m
# CONFIG_CRYPTO_SHA256 is not set
# CONFIG_CRYPTO_SHA512 is not set
CONFIG_CRYPTO_DES=m
# CONFIG_CRYPTO_BLOWFISH is not set
# CONFIG_CRYPTO_TWOFISH is not set
# CONFIG_CRYPTO_SERPENT is not set
# CONFIG_CRYPTO_AES is not set
# CONFIG_CRYPTO_CAST5 is not set
# CONFIG_CRYPTO_CAST6 is not set
CONFIG_CRYPTO_DEFLATE=m
# CONFIG_CRYPTO_TEST is not set

#
# Library routines
#
CONFIG_CRC32=m
CONFIG_ZLIB_INFLATE=m
CONFIG_ZLIB_DEFLATE=m
CONFIG_X86_BIOS_REBOOT=y
CONFIG_PC=y

> 
> Thanks everyone for your continued interest in this, I'll
> try and test the no-onboard-PATA + UP LAPIC and IOAPIC and
> add-in-card-PATA with no onboard PATA + + UP LAPIC and IOAPIC
> when I get a spare moment which is rare.
> 
> 
> PS: If you are being CCed and dont want to be, let me know
> Some people arent on the list.
> 
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/

-- 
Josh McKinney		     |	Webmaster: http://joshandangie.org
--------------------------------------------------------------------------
                             | They that can give up essential liberty
Linux, the choice       -o)  | to obtain a little temporary safety deserve 
of the GNU generation    /\  | neither liberty or safety. 
                        _\_v |                          -Benjamin Franklin

RE: NForce2 pseudoscience stability testing (2.6.0-test11)

[ross.alexander]

Hi all,

I have been experimenting with different options and force reading APIC 
documentation
and I have noticed that running 2.6.0-test11-bk1 with ACPI disabled (not 
compiled in) and
with LAPIC compiled and enabled and IOAPIC compiled in but not enabled 
causes a vast
number of IRQ errors.  Below is all the relevant info.  Can anybody 
duplicate this and
have any idea as to what is causing it.  I don't get this problem in 
2.4.23 BTW.  This is
the same on 2.6.0-test11 and this is without any significant disk 
activity.

Cheers,

Ross

Thu Dec  4 10:32:32 2003

Linux mig27 2.6.0-test11-bk1 #10 Thu Dec 4 08:11:46 GMT 2003 i686 unknown 
unknown GNU/Linux

**** hdparm -I /dev/hda ****

/dev/hda:

ATA device, with non-removable media
        Model Number:       ST380021A 
        Serial Number:      3HV4HP3X 
        Firmware Revision:  3.19 
Standards:
        Supported: 5 4 3 2 
        Likely used: 6
Configuration:
        Logical         max     current
        cylinders       16383   16383
        heads           16      16
        sectors/track   63      63
        --
        CHS current addressable sectors:   16514064
        LBA    user addressable sectors:  156301488
        device size with M = 1024*1024:       76319 MBytes
        device size with M = 1000*1000:       80026 MBytes (80 GB)
Capabilities:
        LBA, IORDY(can be disabled)
        bytes avail on r/w long: 4      Queue depth: 1
        Standby timer values: spec'd by Standard
        R/W multiple sector transfer: Max = 16  Current = 16
        Recommended acoustic management value: 128, current value: 128
        DMA: mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 udma4 *udma5 
             Cycle time: min=120ns recommended=120ns
        PIO: pio0 pio1 pio2 pio3 pio4 
             Cycle time: no flow control=240ns  IORDY flow control=120ns
Commands/features:
        Enabled Supported:
           *    READ BUFFER cmd
           *    WRITE BUFFER cmd
           *    Host Protected Area feature set
           *    Look-ahead
           *    Write cache
           *    Power Management feature set
                Security Mode feature set
                SMART feature set
                Device Configuration Overlay feature set 
           *    Automatic Acoustic Management feature set 
                SET MAX security extension
           *    DOWNLOAD MICROCODE cmd
Security: 
        Master password revision code = 65534
                supported
        not     enabled
        not     locked
        not     frozen
        not     expired: security count
        not     supported: enhanced erase
HW reset results:
        CBLID- above Vih
        Device num = 1
Checksum: correct

**** hdparm -I /dev/hdc ****

**** hdparm -I /dev/hdd ****

**** /proc/interrupts ****

           CPU0 
  0:    1701302          XT-PIC  timer
  1:       2502          XT-PIC  i8042
  2:          0          XT-PIC  cascade
 12:         89          XT-PIC  i8042
 14:       1070          XT-PIC  ide0
 15:          1          XT-PIC  ide1
NMI:          0 
LOC:    1700964 
ERR:    1612328
MIS:          0

**** /proc/ide/ide*/config

(none)
(none)

**** /proc/modules ****


**** dmesg ****

Linux version 2.6.0-test11-bk1 (root@(none)) (gcc version 3.3.2) #10 Thu 
Dec 4 08:11:46 GMT 2003
BIOS-provided physical RAM map:
 BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
 BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)
 BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
 BIOS-e820: 0000000000100000 - 000000005fff0000 (usable)
 BIOS-e820: 000000005fff0000 - 000000005fff3000 (ACPI NVS)
 BIOS-e820: 000000005fff3000 - 0000000060000000 (ACPI data)
 BIOS-e820: 00000000fec00000 - 00000000fec01000 (reserved)
 BIOS-e820: 00000000fee00000 - 00000000fee01000 (reserved)
 BIOS-e820: 00000000ffff0000 - 0000000100000000 (reserved)
user-defined physical RAM map:
 user: 0000000000000000 - 000000000009fc00 (usable)
 user: 000000000009fc00 - 00000000000a0000 (reserved)
 user: 00000000000f0000 - 0000000000100000 (reserved)
 user: 0000000000100000 - 000000005fff0000 (usable)
639MB HIGHMEM available.
896MB LOWMEM available.
On node 0 totalpages: 393200
  DMA zone: 4096 pages, LIFO batch:1
  Normal zone: 225280 pages, LIFO batch:16
  HighMem zone: 163824 pages, LIFO batch:16
DMI 2.2 present.
Building zonelist for node : 0
Kernel command line: root=/dev/hda4 vga=773 acpi=off noapic mem=1572800K
Found and enabled local APIC!
Initializing CPU#0
PID hash table entries: 4096 (order 12: 32768 bytes)
Detected 2162.613 MHz processor.
Console: colour dummy device 80x25
Memory: 1553700k/1572800k available (1427k kernel code, 17980k reserved, 
645k data, 132k init, 655296k highmem)
Calibrating delay loop... 4276.22 BogoMIPS
Dentry cache hash table entries: 262144 (order: 8, 1048576 bytes)
Inode-cache hash table entries: 131072 (order: 7, 524288 bytes)
Mount-cache hash table entries: 512 (order: 0, 4096 bytes)
CPU:     After generic identify, caps: 0383fbff c1c3fbff 00000000 00000000
CPU:     After vendor identify, caps: 0383fbff c1c3fbff 00000000 00000000
CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
CPU: L2 Cache: 256K (64 bytes/line)
CPU:     After all inits, caps: 0383fbff c1c3fbff 00000000 00000020
Intel machine check architecture supported.
Intel machine check reporting enabled on CPU#0.
CPU: AMD Athlon(tm) XP 2700+ stepping 01
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Checking 'hlt' instruction... OK.
POSIX conformance testing by UNIFIX
enabled ExtINT on CPU#0
ESR value before enabling vector: 00000000
ESR value after enabling vector: 00000000
Using local APIC timer interrupts.
calibrating APIC timer ...
..... CPU clock speed is 2162.0397 MHz.
..... host bus clock speed is 332.0676 MHz.
NET: Registered protocol family 16
PCI: PCI BIOS revision 2.10 entry at 0xfb490, last bus=4
PCI: Using configuration type 1
mtrr: v2.0 (20020519)
ACPI: Subsystem revision 20031002
ACPI: Interpreter disabled.
Linux Plug and Play Support v0.97 (c) Adam Belay
ACPI: ACPI tables contain no PCI IRQ routing entries
PCI: Invalid ACPI-PCI IRQ routing table
PCI: Probing PCI hardware
PCI: Probing PCI hardware (bus 00)
PCI: Using IRQ router default [10de/01e0] at 0000:00:00.0
spurious 8259A interrupt: IRQ7.
vesafb: framebuffer at 0xd0000000, mapped to 0xf8800000, size 16384k
vesafb: mode is 1024x768x8, linelength=1024, pages=4
vesafb: protected mode interface info at c000:c2c0
vesafb: scrolling: redraw
fb0: VESA VGA frame buffer device
Machine check exception polling timer started.
ikconfig 0.7 with /proc/config*
highmem bounce pool size: 64 pages
Console: switching to colour frame buffer device 128x48
pty: 256 Unix98 ptys configured
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with 
idebus=xx
hda: ST380021A, ATA DISK drive
hda: IRQ probe failed (0xfffffffa)
hdb: IRQ probe failed (0xfffffffa)
hdb: IRQ probe failed (0xfffffffa)
hdc: _NEC CD-ROM CD-3002A, ATAPI CD/DVD-ROM drive
hdd: _NEC DVD_RW ND-1300A, ATAPI CD/DVD-ROM drive
Using anticipatory io scheduler
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
ide1 at 0x170-0x177,0x376 on irq 15
hda: max request size: 128KiB
hda: 156301488 sectors (80026 MB) w/2048KiB Cache, CHS=65535/16/63
 hda: hda1 hda2 < hda5 > hda3 hda4
Console: switching to colour frame buffer device 128x48
mice: PS/2 mouse device common for all mice
input: PS/2 Logitech Mouse on isa0060/serio1
serio: i8042 AUX port at 0x60,0x64 irq 12
input: AT Translated Set 2 keyboard on isa0060/serio0
serio: i8042 KBD port at 0x60,0x64 irq 1
NET: Registered protocol family 2
IP: routing cache hash table of 16384 buckets, 128Kbytes
TCP: Hash tables configured (established 524288 bind 65536)
NET: Registered protocol family 1
NET: Registered protocol family 17
VFS: Mounted root (ext2 filesystem) readonly.
Freeing unused kernel memory: 132k freed
**** /proc/config ****

#
# Automatically generated make config: don't edit
#
CONFIG_X86=y
CONFIG_MMU=y
CONFIG_UID16=y
CONFIG_GENERIC_ISA_DMA=y

#
# Code maturity level options
#
CONFIG_EXPERIMENTAL=y
CONFIG_CLEAN_COMPILE=y
CONFIG_STANDALONE=y
CONFIG_BROKEN_ON_SMP=y

#
# General setup
#
CONFIG_SWAP=y
CONFIG_SYSVIPC=y
# CONFIG_BSD_PROCESS_ACCT is not set
CONFIG_SYSCTL=y
CONFIG_LOG_BUF_SHIFT=14
CONFIG_IKCONFIG=y
CONFIG_IKCONFIG_PROC=y
# CONFIG_EMBEDDED is not set
CONFIG_KALLSYMS=y
CONFIG_FUTEX=y
CONFIG_EPOLL=y
CONFIG_IOSCHED_NOOP=y
CONFIG_IOSCHED_AS=y
CONFIG_IOSCHED_DEADLINE=y

#
# Loadable module support
#
CONFIG_MODULES=y
CONFIG_MODULE_UNLOAD=y
# CONFIG_MODULE_FORCE_UNLOAD is not set
CONFIG_OBSOLETE_MODPARM=y
# CONFIG_MODVERSIONS is not set
CONFIG_KMOD=y

#
# Processor type and features
#
CONFIG_X86_PC=y
# CONFIG_X86_VOYAGER is not set
# CONFIG_X86_NUMAQ is not set
# CONFIG_X86_SUMMIT is not set
# CONFIG_X86_BIGSMP is not set
# CONFIG_X86_VISWS is not set
# CONFIG_X86_GENERICARCH is not set
# CONFIG_X86_ES7000 is not set
# CONFIG_M386 is not set
# CONFIG_M486 is not set
# CONFIG_M586 is not set
# CONFIG_M586TSC is not set
# CONFIG_M586MMX is not set
# CONFIG_M686 is not set
# CONFIG_MPENTIUMII is not set
# CONFIG_MPENTIUMIII is not set
# CONFIG_MPENTIUM4 is not set
# CONFIG_MK6 is not set
CONFIG_MK7=y
# CONFIG_MK8 is not set
# CONFIG_MELAN is not set
# CONFIG_MCRUSOE is not set
# CONFIG_MWINCHIPC6 is not set
# CONFIG_MWINCHIP2 is not set
# CONFIG_MWINCHIP3D is not set
# CONFIG_MCYRIXIII is not set
# CONFIG_MVIAC3_2 is not set
# CONFIG_X86_GENERIC is not set
CONFIG_X86_CMPXCHG=y
CONFIG_X86_XADD=y
CONFIG_X86_L1_CACHE_SHIFT=6
CONFIG_RWSEM_XCHGADD_ALGORITHM=y
CONFIG_X86_WP_WORKS_OK=y
CONFIG_X86_INVLPG=y
CONFIG_X86_BSWAP=y
CONFIG_X86_POPAD_OK=y
CONFIG_X86_GOOD_APIC=y
CONFIG_X86_INTEL_USERCOPY=y
CONFIG_X86_USE_PPRO_CHECKSUM=y
CONFIG_X86_USE_3DNOW=y
# CONFIG_HPET_TIMER is not set
# CONFIG_HPET_EMULATE_RTC is not set
# CONFIG_SMP is not set
# CONFIG_PREEMPT is not set
CONFIG_X86_UP_APIC=y
CONFIG_X86_UP_IOAPIC=y
CONFIG_X86_LOCAL_APIC=y
CONFIG_X86_IO_APIC=y
CONFIG_X86_TSC=y
CONFIG_X86_MCE=y
CONFIG_X86_MCE_NONFATAL=y
CONFIG_X86_MCE_P4THERMAL=y
# CONFIG_TOSHIBA is not set
# CONFIG_I8K is not set
# CONFIG_MICROCODE is not set
# CONFIG_X86_MSR is not set
# CONFIG_X86_CPUID is not set
# CONFIG_EDD is not set
# CONFIG_NOHIGHMEM is not set
CONFIG_HIGHMEM4G=y
# CONFIG_HIGHMEM64G is not set
CONFIG_HIGHMEM=y
# CONFIG_HIGHPTE is not set
# CONFIG_MATH_EMULATION is not set
CONFIG_MTRR=y

#
# Power management options (ACPI, APM)
#
CONFIG_PM=y
# CONFIG_SOFTWARE_SUSPEND is not set
# CONFIG_PM_DISK is not set

#
# ACPI (Advanced Configuration and Power Interface) Support
#
CONFIG_ACPI=y
CONFIG_ACPI_BOOT=y
CONFIG_ACPI_INTERPRETER=y
CONFIG_ACPI_SLEEP=y
CONFIG_ACPI_SLEEP_PROC_FS=y
CONFIG_ACPI_AC=y
CONFIG_ACPI_BATTERY=y
CONFIG_ACPI_BUTTON=y
CONFIG_ACPI_FAN=y
CONFIG_ACPI_PROCESSOR=y
CONFIG_ACPI_THERMAL=y
# CONFIG_ACPI_ASUS is not set
# CONFIG_ACPI_TOSHIBA is not set
# CONFIG_ACPI_DEBUG is not set
CONFIG_ACPI_BUS=y
CONFIG_ACPI_EC=y
CONFIG_ACPI_POWER=y
CONFIG_ACPI_PCI=y
CONFIG_ACPI_SYSTEM=y
# CONFIG_ACPI_RELAXED_AML is not set

#
# APM (Advanced Power Management) BIOS Support
#
# CONFIG_APM is not set

#
# CPU Frequency scaling
#
# CONFIG_CPU_FREQ is not set

#
# Bus options (PCI, PCMCIA, EISA, MCA, ISA)
#
CONFIG_PCI=y
# CONFIG_PCI_GOBIOS is not set
# CONFIG_PCI_GODIRECT is not set
CONFIG_PCI_GOANY=y
CONFIG_PCI_BIOS=y
CONFIG_PCI_DIRECT=y
CONFIG_PCI_LEGACY_PROC=y
CONFIG_PCI_NAMES=y
CONFIG_ISA=y
# CONFIG_EISA is not set
# CONFIG_MCA is not set
# CONFIG_SCx200 is not set
CONFIG_HOTPLUG=y

#
# PCMCIA/CardBus support
#
# CONFIG_PCMCIA is not set
CONFIG_PCMCIA_PROBE=y

#
# PCI Hotplug Support
#
# CONFIG_HOTPLUG_PCI is not set

#
# Executable file formats
#
CONFIG_BINFMT_ELF=y
# CONFIG_BINFMT_AOUT is not set
# CONFIG_BINFMT_MISC is not set

#
# Device Drivers
#

#
# Generic Driver Options
#
# CONFIG_FW_LOADER is not set

#
# Memory Technology Devices (MTD)
#
# CONFIG_MTD is not set

#
# Parallel port support
#
# CONFIG_PARPORT is not set

#
# Plug and Play support
#
CONFIG_PNP=y
# CONFIG_PNP_DEBUG is not set

#
# Protocols
#
# CONFIG_ISAPNP is not set
# CONFIG_PNPBIOS is not set

#
# Block devices
#
CONFIG_BLK_DEV_FD=m
# CONFIG_BLK_DEV_XD is not set
# CONFIG_BLK_CPQ_DA is not set
# CONFIG_BLK_CPQ_CISS_DA is not set
# CONFIG_BLK_DEV_DAC960 is not set
# CONFIG_BLK_DEV_UMEM is not set
CONFIG_BLK_DEV_LOOP=m
# CONFIG_BLK_DEV_CRYPTOLOOP is not set
# CONFIG_BLK_DEV_NBD is not set
# CONFIG_BLK_DEV_RAM is not set
# CONFIG_BLK_DEV_INITRD is not set
CONFIG_LBD=y

#
# ATA/ATAPI/MFM/RLL support
#
CONFIG_IDE=y
CONFIG_BLK_DEV_IDE=y

#
# Please see Documentation/ide.txt for help/info on IDE drives
#
# CONFIG_BLK_DEV_HD_IDE is not set
CONFIG_BLK_DEV_IDEDISK=y
CONFIG_IDEDISK_MULTI_MODE=y
# CONFIG_IDEDISK_STROKE is not set
CONFIG_BLK_DEV_IDECD=m
# CONFIG_BLK_DEV_IDETAPE is not set
CONFIG_BLK_DEV_IDEFLOPPY=m
CONFIG_BLK_DEV_IDESCSI=m
# CONFIG_IDE_TASK_IOCTL is not set
CONFIG_IDE_TASKFILE_IO=y

#
# IDE chipset support/bugfixes
#
# CONFIG_BLK_DEV_CMD640 is not set
# CONFIG_BLK_DEV_IDEPNP is not set
CONFIG_BLK_DEV_IDEPCI=y
CONFIG_IDEPCI_SHARE_IRQ=y
# CONFIG_BLK_DEV_OFFBOARD is not set
CONFIG_BLK_DEV_GENERIC=y
# CONFIG_BLK_DEV_OPTI621 is not set
# CONFIG_BLK_DEV_RZ1000 is not set
CONFIG_BLK_DEV_IDEDMA_PCI=y
# CONFIG_BLK_DEV_IDEDMA_FORCED is not set
CONFIG_IDEDMA_PCI_AUTO=y
# CONFIG_IDEDMA_ONLYDISK is not set
# CONFIG_IDEDMA_PCI_WIP is not set
CONFIG_BLK_DEV_ADMA=y
# CONFIG_BLK_DEV_AEC62XX is not set
# CONFIG_BLK_DEV_ALI15X3 is not set
# CONFIG_BLK_DEV_AMD74XX is not set
# CONFIG_BLK_DEV_CMD64X is not set
# CONFIG_BLK_DEV_TRIFLEX is not set
# CONFIG_BLK_DEV_CY82C693 is not set
# CONFIG_BLK_DEV_CS5520 is not set
# CONFIG_BLK_DEV_CS5530 is not set
# CONFIG_BLK_DEV_HPT34X is not set
# CONFIG_BLK_DEV_HPT366 is not set
# CONFIG_BLK_DEV_SC1200 is not set
# CONFIG_BLK_DEV_PIIX is not set
# CONFIG_BLK_DEV_NS87415 is not set
# CONFIG_BLK_DEV_PDC202XX_OLD is not set
# CONFIG_BLK_DEV_PDC202XX_NEW is not set
# CONFIG_BLK_DEV_SVWKS is not set
# CONFIG_BLK_DEV_SIIMAGE is not set
# CONFIG_BLK_DEV_SIS5513 is not set
# CONFIG_BLK_DEV_SLC90E66 is not set
# CONFIG_BLK_DEV_TRM290 is not set
# CONFIG_BLK_DEV_VIA82CXXX is not set
# CONFIG_IDE_CHIPSETS is not set
CONFIG_BLK_DEV_IDEDMA=y
# CONFIG_IDEDMA_IVB is not set
CONFIG_IDEDMA_AUTO=y
# CONFIG_DMA_NONPCI is not set
# CONFIG_BLK_DEV_HD is not set

#
# SCSI device support
#
CONFIG_SCSI=m
CONFIG_SCSI_PROC_FS=y

#
# SCSI support type (disk, tape, CD-ROM)
#
CONFIG_BLK_DEV_SD=m
CONFIG_CHR_DEV_ST=m
# CONFIG_CHR_DEV_OSST is not set
CONFIG_BLK_DEV_SR=m
# CONFIG_BLK_DEV_SR_VENDOR is not set
CONFIG_CHR_DEV_SG=m

#
# Some SCSI devices (e.g. CD jukebox) support multiple LUNs
#
# CONFIG_SCSI_MULTI_LUN is not set
CONFIG_SCSI_REPORT_LUNS=y
# CONFIG_SCSI_CONSTANTS is not set
# CONFIG_SCSI_LOGGING is not set

#
# SCSI low-level drivers
#
# CONFIG_BLK_DEV_3W_XXXX_RAID is not set
# CONFIG_SCSI_7000FASST is not set
# CONFIG_SCSI_ACARD is not set
# CONFIG_SCSI_AHA152X is not set
# CONFIG_SCSI_AHA1542 is not set
# CONFIG_SCSI_AACRAID is not set
CONFIG_SCSI_AIC7XXX=m
CONFIG_AIC7XXX_CMDS_PER_DEVICE=32
CONFIG_AIC7XXX_RESET_DELAY_MS=15000
# CONFIG_AIC7XXX_PROBE_EISA_VL is not set
# CONFIG_AIC7XXX_BUILD_FIRMWARE is not set
CONFIG_AIC7XXX_DEBUG_ENABLE=y
CONFIG_AIC7XXX_DEBUG_MASK=0
CONFIG_AIC7XXX_REG_PRETTY_PRINT=y
# CONFIG_SCSI_AIC7XXX_OLD is not set
# CONFIG_SCSI_AIC79XX is not set
# CONFIG_SCSI_ADVANSYS is not set
# CONFIG_SCSI_IN2000 is not set
# CONFIG_SCSI_MEGARAID is not set
# CONFIG_SCSI_SATA is not set
# CONFIG_SCSI_BUSLOGIC is not set
# CONFIG_SCSI_CPQFCTS is not set
# CONFIG_SCSI_DMX3191D is not set
# CONFIG_SCSI_DTC3280 is not set
# CONFIG_SCSI_EATA is not set
# CONFIG_SCSI_EATA_PIO is not set
# CONFIG_SCSI_FUTURE_DOMAIN is not set
# CONFIG_SCSI_GDTH is not set
# CONFIG_SCSI_GENERIC_NCR5380 is not set
# CONFIG_SCSI_GENERIC_NCR5380_MMIO is not set
# CONFIG_SCSI_IPS is not set
# CONFIG_SCSI_INIA100 is not set
# CONFIG_SCSI_NCR53C406A is not set
# CONFIG_SCSI_SYM53C8XX_2 is not set
# CONFIG_SCSI_PAS16 is not set
# CONFIG_SCSI_PSI240I is not set
# CONFIG_SCSI_QLOGIC_FAS is not set
# CONFIG_SCSI_QLOGIC_ISP is not set
# CONFIG_SCSI_QLOGIC_FC is not set
# CONFIG_SCSI_QLOGIC_1280 is not set
# CONFIG_SCSI_SYM53C416 is not set
# CONFIG_SCSI_DC395x is not set
# CONFIG_SCSI_T128 is not set
# CONFIG_SCSI_U14_34F is not set
# CONFIG_SCSI_ULTRASTOR is not set
# CONFIG_SCSI_NSP32 is not set
# CONFIG_SCSI_DEBUG is not set

#
# Old CD-ROM drivers (not SCSI, not IDE)
#
# CONFIG_CD_NO_IDESCSI is not set

#
# Multi-device support (RAID and LVM)
#
CONFIG_MD=y
# CONFIG_BLK_DEV_MD is not set
CONFIG_BLK_DEV_DM=m
CONFIG_DM_IOCTL_V4=y

#
# Fusion MPT device support
#
# CONFIG_FUSION is not set

#
# IEEE 1394 (FireWire) support (EXPERIMENTAL)
#
CONFIG_IEEE1394=m

#
# Subsystem Options
#
# CONFIG_IEEE1394_VERBOSEDEBUG is not set
# CONFIG_IEEE1394_OUI_DB is not set

#
# Device Drivers
#

#
# Texas Instruments PCILynx requires I2C bit-banging
#
CONFIG_IEEE1394_OHCI1394=m

#
# Protocol Drivers
#
# CONFIG_IEEE1394_VIDEO1394 is not set
# CONFIG_IEEE1394_SBP2 is not set
# CONFIG_IEEE1394_ETH1394 is not set
# CONFIG_IEEE1394_DV1394 is not set
# CONFIG_IEEE1394_RAWIO is not set
# CONFIG_IEEE1394_CMP is not set

#
# I2O device support
#
# CONFIG_I2O is not set

#
# Networking support
#
CONFIG_NET=y

#
# Networking options
#
CONFIG_PACKET=y
# CONFIG_PACKET_MMAP is not set
# CONFIG_NETLINK_DEV is not set
CONFIG_UNIX=y
# CONFIG_NET_KEY is not set
CONFIG_INET=y
CONFIG_IP_MULTICAST=y
# CONFIG_IP_ADVANCED_ROUTER is not set
# CONFIG_IP_PNP is not set
# CONFIG_NET_IPIP is not set
# CONFIG_NET_IPGRE is not set
# CONFIG_IP_MROUTE is not set
# CONFIG_ARPD is not set
# CONFIG_INET_ECN is not set
# CONFIG_SYN_COOKIES is not set
# CONFIG_INET_AH is not set
# CONFIG_INET_ESP is not set
# CONFIG_INET_IPCOMP is not set
CONFIG_IPV6=m
# CONFIG_IPV6_PRIVACY is not set
# CONFIG_INET6_AH is not set
# CONFIG_INET6_ESP is not set
# CONFIG_INET6_IPCOMP is not set
# CONFIG_IPV6_TUNNEL is not set
# CONFIG_DECNET is not set
# CONFIG_BRIDGE is not set
# CONFIG_NETFILTER is not set

#
# SCTP Configuration (EXPERIMENTAL)
#
CONFIG_IPV6_SCTP__=m
# CONFIG_IP_SCTP is not set
# CONFIG_ATM is not set
# CONFIG_VLAN_8021Q is not set
# CONFIG_LLC2 is not set
# CONFIG_IPX is not set
# CONFIG_ATALK is not set
# CONFIG_X25 is not set
# CONFIG_LAPB is not set
# CONFIG_NET_DIVERT is not set
# CONFIG_ECONET is not set
# CONFIG_WAN_ROUTER is not set
# CONFIG_NET_FASTROUTE is not set
# CONFIG_NET_HW_FLOWCONTROL is not set

#
# QoS and/or fair queueing
#
# CONFIG_NET_SCHED is not set

#
# Network testing
#
# CONFIG_NET_PKTGEN is not set
CONFIG_NETDEVICES=y

#
# ARCnet devices
#
# CONFIG_ARCNET is not set
CONFIG_DUMMY=m
# CONFIG_BONDING is not set
# CONFIG_EQUALIZER is not set
# CONFIG_TUN is not set
# CONFIG_NET_SB1000 is not set

#
# Ethernet (10 or 100Mbit)
#
CONFIG_NET_ETHERNET=y
# CONFIG_MII is not set
# CONFIG_HAPPYMEAL is not set
# CONFIG_SUNGEM is not set
CONFIG_NET_VENDOR_3COM=y
# CONFIG_EL1 is not set
# CONFIG_EL2 is not set
# CONFIG_ELPLUS is not set
# CONFIG_EL16 is not set
# CONFIG_EL3 is not set
# CONFIG_3C515 is not set
CONFIG_VORTEX=m
# CONFIG_TYPHOON is not set
# CONFIG_LANCE is not set
# CONFIG_NET_VENDOR_SMC is not set
# CONFIG_NET_VENDOR_RACAL is not set

#
# Tulip family network device support
#
CONFIG_NET_TULIP=y
# CONFIG_DE2104X is not set
CONFIG_TULIP=m
# CONFIG_TULIP_MWI is not set
# CONFIG_TULIP_MMIO is not set
# CONFIG_DE4X5 is not set
# CONFIG_WINBOND_840 is not set
# CONFIG_DM9102 is not set
# CONFIG_AT1700 is not set
# CONFIG_DEPCA is not set
# CONFIG_HP100 is not set
# CONFIG_NET_ISA is not set
# CONFIG_NET_PCI is not set
# CONFIG_NET_POCKET is not set

#
# Ethernet (1000 Mbit)
#
# CONFIG_ACENIC is not set
# CONFIG_DL2K is not set
# CONFIG_E1000 is not set
# CONFIG_NS83820 is not set
# CONFIG_HAMACHI is not set
# CONFIG_YELLOWFIN is not set
# CONFIG_R8169 is not set
# CONFIG_SIS190 is not set
# CONFIG_SK98LIN is not set
# CONFIG_TIGON3 is not set

#
# Ethernet (10000 Mbit)
#
# CONFIG_IXGB is not set
# CONFIG_FDDI is not set
# CONFIG_HIPPI is not set
# CONFIG_PPP is not set
# CONFIG_SLIP is not set

#
# Wireless LAN (non-hamradio)
#
# CONFIG_NET_RADIO is not set

#
# Token Ring devices
#
# CONFIG_TR is not set
# CONFIG_NET_FC is not set
# CONFIG_RCPCI is not set
# CONFIG_SHAPER is not set

#
# Wan interfaces
#
# CONFIG_WAN is not set

#
# Amateur Radio support
#
# CONFIG_HAMRADIO is not set

#
# IrDA (infrared) support
#
# CONFIG_IRDA is not set

#
# Bluetooth support
#
# CONFIG_BT is not set

#
# ISDN subsystem
#
# CONFIG_ISDN_BOOL is not set

#
# Telephony Support
#
# CONFIG_PHONE is not set

#
# Input device support
#
CONFIG_INPUT=y

#
# Userland interfaces
#
CONFIG_INPUT_MOUSEDEV=y
CONFIG_INPUT_MOUSEDEV_PSAUX=y
CONFIG_INPUT_MOUSEDEV_SCREEN_X=1024
CONFIG_INPUT_MOUSEDEV_SCREEN_Y=768
# CONFIG_INPUT_JOYDEV is not set
# CONFIG_INPUT_TSDEV is not set
# CONFIG_INPUT_EVDEV is not set
# CONFIG_INPUT_EVBUG is not set

#
# Input I/O drivers
#
# CONFIG_GAMEPORT is not set
CONFIG_SOUND_GAMEPORT=y
CONFIG_SERIO=y
CONFIG_SERIO_I8042=y
# CONFIG_SERIO_SERPORT is not set
# CONFIG_SERIO_CT82C710 is not set
# CONFIG_SERIO_PCIPS2 is not set

#
# Input Device Drivers
#
CONFIG_INPUT_KEYBOARD=y
CONFIG_KEYBOARD_ATKBD=y
# CONFIG_KEYBOARD_SUNKBD is not set
# CONFIG_KEYBOARD_XTKBD is not set
# CONFIG_KEYBOARD_NEWTON is not set
CONFIG_INPUT_MOUSE=y
CONFIG_MOUSE_PS2=y
# CONFIG_MOUSE_PS2_SYNAPTICS is not set
# CONFIG_MOUSE_SERIAL is not set
# CONFIG_MOUSE_INPORT is not set
# CONFIG_MOUSE_LOGIBM is not set
# CONFIG_MOUSE_PC110PAD is not set
# CONFIG_INPUT_JOYSTICK is not set
# CONFIG_INPUT_TOUCHSCREEN is not set
# CONFIG_INPUT_MISC is not set

#
# Character devices
#
CONFIG_VT=y
CONFIG_VT_CONSOLE=y
CONFIG_HW_CONSOLE=y
# CONFIG_SERIAL_NONSTANDARD is not set

#
# Serial drivers
#
CONFIG_SERIAL_8250=m
# CONFIG_SERIAL_8250_ACPI is not set
CONFIG_SERIAL_8250_NR_UARTS=4
# CONFIG_SERIAL_8250_EXTENDED is not set

#
# Non-8250 serial port support
#
CONFIG_SERIAL_CORE=m
CONFIG_UNIX98_PTYS=y
CONFIG_UNIX98_PTY_COUNT=256

#
# I2C support
#
# CONFIG_I2C is not set

#
# I2C Algorithms
#

#
# I2C Hardware Bus support
#

#
# I2C Hardware Sensors Chip support
#
# CONFIG_I2C_SENSOR is not set

#
# Mice
#
# CONFIG_BUSMOUSE is not set
# CONFIG_QIC02_TAPE is not set

#
# IPMI
#
# CONFIG_IPMI_HANDLER is not set

#
# Watchdog Cards
#
# CONFIG_WATCHDOG is not set
CONFIG_HW_RANDOM=m
CONFIG_NVRAM=m
CONFIG_RTC=m
CONFIG_GEN_RTC=m
CONFIG_GEN_RTC_X=y
# CONFIG_DTLK is not set
# CONFIG_R3964 is not set
# CONFIG_APPLICOM is not set
# CONFIG_SONYPI is not set

#
# Ftape, the floppy tape device driver
#
# CONFIG_FTAPE is not set
CONFIG_AGP=m
# CONFIG_AGP_ALI is not set
# CONFIG_AGP_ATI is not set
# CONFIG_AGP_AMD is not set
# CONFIG_AGP_AMD64 is not set
# CONFIG_AGP_INTEL is not set
CONFIG_AGP_NVIDIA=m
# CONFIG_AGP_SIS is not set
# CONFIG_AGP_SWORKS is not set
# CONFIG_AGP_VIA is not set
# CONFIG_DRM is not set
# CONFIG_MWAVE is not set
# CONFIG_RAW_DRIVER is not set
# CONFIG_HANGCHECK_TIMER is not set

#
# Multimedia devices
#
# CONFIG_VIDEO_DEV is not set

#
# Digital Video Broadcasting Devices
#
# CONFIG_DVB is not set

#
# Graphics support
#
CONFIG_FB=y
# CONFIG_FB_CYBER2000 is not set
# CONFIG_FB_IMSTT is not set
# CONFIG_FB_VGA16 is not set
CONFIG_FB_VESA=y
CONFIG_VIDEO_SELECT=y
# CONFIG_FB_HGA is not set
CONFIG_FB_RIVA=m
# CONFIG_FB_MATROX is not set
# CONFIG_FB_RADEON is not set
# CONFIG_FB_ATY128 is not set
# CONFIG_FB_ATY is not set
# CONFIG_FB_SIS is not set
# CONFIG_FB_NEOMAGIC is not set
# CONFIG_FB_3DFX is not set
# CONFIG_FB_VOODOO1 is not set
# CONFIG_FB_TRIDENT is not set
# CONFIG_FB_VIRTUAL is not set

#
# Console display driver support
#
CONFIG_VGA_CONSOLE=y
# CONFIG_MDA_CONSOLE is not set
CONFIG_DUMMY_CONSOLE=y
CONFIG_FRAMEBUFFER_CONSOLE=y
CONFIG_PCI_CONSOLE=y
CONFIG_FONTS=y
CONFIG_FONT_8x8=y
CONFIG_FONT_8x16=y
# CONFIG_FONT_6x11 is not set
# CONFIG_FONT_PEARL_8x8 is not set
# CONFIG_FONT_ACORN_8x8 is not set
# CONFIG_FONT_MINI_4x6 is not set
# CONFIG_FONT_SUN8x16 is not set
# CONFIG_FONT_SUN12x22 is not set

#
# Logo configuration
#
# CONFIG_LOGO is not set

#
# Sound
#
CONFIG_SOUND=m

#
# Advanced Linux Sound Architecture
#
CONFIG_SND=m
CONFIG_SND_SEQUENCER=m
# CONFIG_SND_SEQ_DUMMY is not set
CONFIG_SND_OSSEMUL=y
CONFIG_SND_MIXER_OSS=m
CONFIG_SND_PCM_OSS=m
CONFIG_SND_SEQUENCER_OSS=y
# CONFIG_SND_RTCTIMER is not set
# CONFIG_SND_VERBOSE_PRINTK is not set
# CONFIG_SND_DEBUG is not set

#
# Generic devices
#
# CONFIG_SND_DUMMY is not set
# CONFIG_SND_VIRMIDI is not set
# CONFIG_SND_MTPAV is not set
# CONFIG_SND_SERIAL_U16550 is not set
# CONFIG_SND_MPU401 is not set

#
# ISA devices
#
# CONFIG_SND_AD1848 is not set
# CONFIG_SND_CS4231 is not set
# CONFIG_SND_CS4232 is not set
# CONFIG_SND_CS4236 is not set
# CONFIG_SND_ES1688 is not set
# CONFIG_SND_ES18XX is not set
# CONFIG_SND_GUSCLASSIC is not set
# CONFIG_SND_GUSEXTREME is not set
# CONFIG_SND_GUSMAX is not set
# CONFIG_SND_INTERWAVE is not set
# CONFIG_SND_INTERWAVE_STB is not set
# CONFIG_SND_OPTI92X_AD1848 is not set
# CONFIG_SND_OPTI92X_CS4231 is not set
# CONFIG_SND_OPTI93X is not set
# CONFIG_SND_SB8 is not set
# CONFIG_SND_SB16 is not set
# CONFIG_SND_SBAWE is not set
# CONFIG_SND_WAVEFRONT is not set
# CONFIG_SND_CMI8330 is not set
# CONFIG_SND_OPL3SA2 is not set
# CONFIG_SND_SGALAXY is not set
# CONFIG_SND_SSCAPE is not set

#
# PCI devices
#
# CONFIG_SND_ALI5451 is not set
# CONFIG_SND_AZT3328 is not set
# CONFIG_SND_CS46XX is not set
# CONFIG_SND_CS4281 is not set
# CONFIG_SND_EMU10K1 is not set
# CONFIG_SND_KORG1212 is not set
# CONFIG_SND_NM256 is not set
# CONFIG_SND_RME32 is not set
# CONFIG_SND_RME96 is not set
# CONFIG_SND_RME9652 is not set
# CONFIG_SND_HDSP is not set
# CONFIG_SND_TRIDENT is not set
# CONFIG_SND_YMFPCI is not set
# CONFIG_SND_ALS4000 is not set
# CONFIG_SND_CMIPCI is not set
# CONFIG_SND_ENS1370 is not set
# CONFIG_SND_ENS1371 is not set
# CONFIG_SND_ES1938 is not set
# CONFIG_SND_ES1968 is not set
# CONFIG_SND_MAESTRO3 is not set
# CONFIG_SND_FM801 is not set
# CONFIG_SND_ICE1712 is not set
# CONFIG_SND_ICE1724 is not set
CONFIG_SND_INTEL8X0=m
# CONFIG_SND_SONICVIBES is not set
# CONFIG_SND_VIA82XX is not set
# CONFIG_SND_VX222 is not set

#
# ALSA USB devices
#
# CONFIG_SND_USB_AUDIO is not set

#
# Open Sound System
#
# CONFIG_SOUND_PRIME is not set

#
# USB support
#
CONFIG_USB=m
# CONFIG_USB_DEBUG is not set

#
# Miscellaneous USB options
#
CONFIG_USB_DEVICEFS=y
# CONFIG_USB_BANDWIDTH is not set
# CONFIG_USB_DYNAMIC_MINORS is not set

#
# USB Host Controller Drivers
#
CONFIG_USB_EHCI_HCD=m
CONFIG_USB_OHCI_HCD=m
CONFIG_USB_UHCI_HCD=m

#
# USB Device Class drivers
#
# CONFIG_USB_AUDIO is not set
# CONFIG_USB_BLUETOOTH_TTY is not set
# CONFIG_USB_MIDI is not set
# CONFIG_USB_ACM is not set
# CONFIG_USB_PRINTER is not set
CONFIG_USB_STORAGE=m
# CONFIG_USB_STORAGE_DEBUG is not set
# CONFIG_USB_STORAGE_DATAFAB is not set
# CONFIG_USB_STORAGE_FREECOM is not set
# CONFIG_USB_STORAGE_ISD200 is not set
# CONFIG_USB_STORAGE_DPCM is not set
# CONFIG_USB_STORAGE_HP8200e is not set
# CONFIG_USB_STORAGE_SDDR09 is not set
# CONFIG_USB_STORAGE_SDDR55 is not set
# CONFIG_USB_STORAGE_JUMPSHOT is not set

#
# USB Human Interface Devices (HID)
#
CONFIG_USB_HID=m
CONFIG_USB_HIDINPUT=y
# CONFIG_HID_FF is not set
# CONFIG_USB_HIDDEV is not set

#
# USB HID Boot Protocol drivers
#
# CONFIG_USB_KBD is not set
# CONFIG_USB_MOUSE is not set
# CONFIG_USB_AIPTEK is not set
# CONFIG_USB_WACOM is not set
# CONFIG_USB_KBTAB is not set
# CONFIG_USB_POWERMATE is not set
# CONFIG_USB_XPAD is not set

#
# USB Imaging devices
#
# CONFIG_USB_MDC800 is not set
# CONFIG_USB_SCANNER is not set
# CONFIG_USB_MICROTEK is not set
# CONFIG_USB_HPUSBSCSI is not set

#
# USB Multimedia devices
#
# CONFIG_USB_DABUSB is not set

#
# Video4Linux support is needed for USB Multimedia device support
#

#
# USB Network adaptors
#
# CONFIG_USB_CATC is not set
# CONFIG_USB_KAWETH is not set
# CONFIG_USB_PEGASUS is not set
# CONFIG_USB_RTL8150 is not set
# CONFIG_USB_USBNET is not set

#
# USB port drivers
#

#
# USB Serial Converter support
#
# CONFIG_USB_SERIAL is not set

#
# USB Miscellaneous drivers
#
# CONFIG_USB_TIGL is not set
# CONFIG_USB_AUERSWALD is not set
# CONFIG_USB_RIO500 is not set
# CONFIG_USB_BRLVGER is not set
# CONFIG_USB_LCD is not set
# CONFIG_USB_TEST is not set
# CONFIG_USB_GADGET is not set

#
# File systems
#
CONFIG_EXT2_FS=y
# CONFIG_EXT2_FS_XATTR is not set
CONFIG_EXT3_FS=y
CONFIG_EXT3_FS_XATTR=y
# CONFIG_EXT3_FS_POSIX_ACL is not set
# CONFIG_EXT3_FS_SECURITY is not set
CONFIG_JBD=y
# CONFIG_JBD_DEBUG is not set
CONFIG_FS_MBCACHE=y
# CONFIG_REISERFS_FS is not set
# CONFIG_JFS_FS is not set
# CONFIG_XFS_FS is not set
# CONFIG_MINIX_FS is not set
# CONFIG_ROMFS_FS is not set
# CONFIG_QUOTA is not set
# CONFIG_AUTOFS_FS is not set
# CONFIG_AUTOFS4_FS is not set

#
# CD-ROM/DVD Filesystems
#
CONFIG_ISO9660_FS=m
CONFIG_JOLIET=y
# CONFIG_ZISOFS is not set
CONFIG_UDF_FS=m

#
# DOS/FAT/NT Filesystems
#
CONFIG_FAT_FS=m
CONFIG_MSDOS_FS=m
CONFIG_VFAT_FS=m
# CONFIG_NTFS_FS is not set

#
# Pseudo filesystems
#
CONFIG_PROC_FS=y
CONFIG_PROC_KCORE=y
# CONFIG_DEVFS_FS is not set
CONFIG_DEVPTS_FS=y
# CONFIG_DEVPTS_FS_XATTR is not set
CONFIG_TMPFS=y
# CONFIG_HUGETLBFS is not set
# CONFIG_HUGETLB_PAGE is not set
CONFIG_RAMFS=y

#
# Miscellaneous filesystems
#
# CONFIG_ADFS_FS is not set
# CONFIG_AFFS_FS is not set
# CONFIG_HFS_FS is not set
# CONFIG_BEFS_FS is not set
# CONFIG_BFS_FS is not set
# CONFIG_EFS_FS is not set
# CONFIG_CRAMFS is not set
# CONFIG_VXFS_FS is not set
# CONFIG_HPFS_FS is not set
# CONFIG_QNX4FS_FS is not set
# CONFIG_SYSV_FS is not set
# CONFIG_UFS_FS is not set

#
# Network File Systems
#
# CONFIG_NFS_FS is not set
# CONFIG_NFSD is not set
# CONFIG_EXPORTFS is not set
# CONFIG_SMB_FS is not set
# CONFIG_CIFS is not set
# CONFIG_NCP_FS is not set
# CONFIG_CODA_FS is not set
# CONFIG_INTERMEZZO_FS is not set
# CONFIG_AFS_FS is not set

#
# Partition Types
#
# CONFIG_PARTITION_ADVANCED is not set
CONFIG_MSDOS_PARTITION=y
CONFIG_NLS=y

#
# Native Language Support
#
CONFIG_NLS_DEFAULT="iso8859-1"
CONFIG_NLS_CODEPAGE_437=y
# CONFIG_NLS_CODEPAGE_737 is not set
# CONFIG_NLS_CODEPAGE_775 is not set
# CONFIG_NLS_CODEPAGE_850 is not set
# CONFIG_NLS_CODEPAGE_852 is not set
# CONFIG_NLS_CODEPAGE_855 is not set
# CONFIG_NLS_CODEPAGE_857 is not set
# CONFIG_NLS_CODEPAGE_860 is not set
# CONFIG_NLS_CODEPAGE_861 is not set
# CONFIG_NLS_CODEPAGE_862 is not set
# CONFIG_NLS_CODEPAGE_863 is not set
# CONFIG_NLS_CODEPAGE_864 is not set
# CONFIG_NLS_CODEPAGE_865 is not set
# CONFIG_NLS_CODEPAGE_866 is not set
# CONFIG_NLS_CODEPAGE_869 is not set
# CONFIG_NLS_CODEPAGE_936 is not set
# CONFIG_NLS_CODEPAGE_950 is not set
# CONFIG_NLS_CODEPAGE_932 is not set
# CONFIG_NLS_CODEPAGE_949 is not set
# CONFIG_NLS_CODEPAGE_874 is not set
# CONFIG_NLS_ISO8859_8 is not set
# CONFIG_NLS_CODEPAGE_1250 is not set
# CONFIG_NLS_CODEPAGE_1251 is not set
CONFIG_NLS_ISO8859_1=y
# CONFIG_NLS_ISO8859_2 is not set
# CONFIG_NLS_ISO8859_3 is not set
# CONFIG_NLS_ISO8859_4 is not set
# CONFIG_NLS_ISO8859_5 is not set
# CONFIG_NLS_ISO8859_6 is not set
# CONFIG_NLS_ISO8859_7 is not set
# CONFIG_NLS_ISO8859_9 is not set
# CONFIG_NLS_ISO8859_13 is not set
# CONFIG_NLS_ISO8859_14 is not set
# CONFIG_NLS_ISO8859_15 is not set
# CONFIG_NLS_KOI8_R is not set
# CONFIG_NLS_KOI8_U is not set
# CONFIG_NLS_UTF8 is not set

#
# Profiling support
#
# CONFIG_PROFILING is not set

#
# Kernel hacking
#
# CONFIG_DEBUG_KERNEL is not set
CONFIG_DEBUG_SPINLOCK_SLEEP=y
CONFIG_FRAME_POINTER=y
CONFIG_X86_EXTRA_IRQS=y
CONFIG_X86_FIND_SMP_CONFIG=y
CONFIG_X86_MPPARSE=y

#
# Security options
#
# CONFIG_SECURITY is not set

#
# Cryptographic options
#
# CONFIG_CRYPTO is not set

#
# Library routines
#
CONFIG_CRC32=m
CONFIG_X86_BIOS_REBOOT=y
CONFIG_PC=y


---------------------------------------------------------------------------------
Ross Alexander                           "We demand clearly defined
MIS - NEC Europe Limited            boundaries of uncertainty and
Work ph: +44 20 8752 3394         doubt."




"b@netzentry.com" <b
04/12/2003 01:41 a.m.
Please respond to b
 
        To:     wa1ter@myrealbox.com
        cc:     linux-kernel@vger.kernel.org
        Subject:        RE: NForce2 pseudoscience stability testing 
(2.6.0-test11)


 >Subject: Re: NForce2 pseudoscience stability testing (2.6.0-test11)
 >>Josh McKinney wrote:
 >> To me the strangest thing is that when I first got this
 >>board a month or
 >> so ago it would hang with APIC or LAPIC enabled.  Now it works
 >>fine
 >> without disabling APIC.  All I did was update the BIOS and
 >>use it for a
 >> while with APIC disabled...
 >
 >Does the new BIOS use different defaults for memory timing,
 >bus speed, etc?
 >Did you change any of the default settings in the BIOS?
 >
-- I don't think this issue has anything to do with motherboard
maker or BIOS rev. Most of the people with this problem are
not overclocking and have stable machines with other OSes or
under certain conditions namely:

* In general NForce2 boards are stable under windows 2000
- a far as I can tell

* The boards are stable under certain conditions. The final
test for this (Proposed by Allen Martin
[AMartin at nvidia ! com] is to get a stable well supported
PCI-IDE add in card and ignore the "AMD/NVIDIA" IDE onboard.
(First pointed out by Ian Kumlien I believe)
"If we all have that, and deadlock when using the amd/nvidia
driver.. then we know that that might be the fault. The
machine still locks for a while so, it's not just the ide,
  but it might be a good place to start."

* NForce2 boards are stable when using APIC and using generic
IDE driver. This is painfully slow but is stable.

-- In general: I dont think it should be so easy to blame
the BIOS. If one isnt overclocking and using the SPD on the
memory and using conservative settings, what difference
should that make? And if the board is stable with another
OS I take this "BIOS blaming" and basically throw it out. BIOS
is a deprecated arcane ridiculous thing and should never be
trusted. I have seen on several nicer dual SCSI based
machines messages on boot about certain values being changed
or fixed up.

-- Fixing this for 2.4.x too is important so be sure to try
and find out if 2.4.23 hangs if you get a stable 2.6 thing
going.

Thanks everyone for your continued interest in this, I'll
try and test the no-onboard-PATA + UP LAPIC and IOAPIC and
add-in-card-PATA with no onboard PATA + + UP LAPIC and IOAPIC
when I get a spare moment which is rare.


PS: If you are being CCed and dont want to be, let me know
Some people arent on the list.

Re: NForce2 pseudoscience stability testing (2.6.0-test11)

[b]

 >Bob wrote:
 >Local APIC locked up with nforce2 and VIA,
 >impossibly serious with nforce2 and non-amd
 >offboard ide controller cards. BIOS flash made
 >problems go away.
 >
 >I experienced the lockups when using promise and
 >siig sis ide hd controller pci cards. I still had problems
 >with a 3ware card.
 >
 >Flashing the bios solved all problems. Now I run
 >both the via and nforce2 mboards with APIC and
 >Local APIC on in kernel. I'm running six ide drives,
 >four on a 3ware pci hd controller card using ide-scsi.
 >
 >I got sound working on nforce2, and nvidia ti4200
 >agp8 vid card(nvidia drivers crash X but agpgart
 >with X "nv" instead of "nvidia" works in 2D well),
 >but not usb. The sound config problem was fixed
 >by "ln -s sound/dsp2 /dev/dsp". The apps only
 >look for /dev/dsp.
 >
 >-Bob

Do you think that motherboard maker was really at fault or
did they genuinely fix a grotesque error. Were any changes
in the BIOS-change-list relevant to fixing up this APIC
problem in Linux?

Can you provide the following:
- which motherboard
- which bios revs (the broken one and the fixed one)
- which kernel are you running (is it vanilla, from a dist,
recompiled)
- lspci
- cat /proc/interrupts
- dmesg
- .config from kernel (if not stock from dist)

I really, really hope this problem can be solved without
a BIOS upgrade because getting board manufacturers to do
anything is very difficult.

RE: NForce2 pseudoscience stability testing (2.6.0-test11)

[Allen Martin]

> -----Original Message-----
> From: Jesse Allen [mailto:the3dfxdude@hotmail.com] 
> Sent: Wednesday, December 03, 2003 6:46 PM
> To: b@netzentry.com
> Cc: linux-kernel@vger.kernel.org
> Subject: Re: NForce2 pseudoscience stability testing (2.6.0-test11)
> 
> I suppose I could try right now.  I don't have a pci ide with 
> me right now, but I do have pci scsi cards.  But doesn't 
> running with the generic ide driver basically prove the same 
> thing?  APIC & Generic IDE: works, PIC & nForce IDE: works, 
> APIC & nForce IDE: deadlocks.  It's not like we are expecting 
> faulty nforce ide hardware, or are we?

I don't think there's any faulty nForce IDE hardware or we would have heard
about it from windows users (and we haven't).  

The problem with comparing the nForce IDE driver against the generic IDE
driver is that the generic IDE driver won't enable DMA, so the interrupt
rate will be much different.  If there's some interrupt race condition in
APIC mode, disabling DMA may mask it.

Also are people who are having problems using rounded or flat cables?  It's
possible the problem could be related to DMA CRC errors.  Switching to flat
cables can help with that.

-Allen

Re: NForce2 pseudoscience stability testing (2.6.0-test11)

[Jesse Allen]

On Wed, Dec 03, 2003 at 09:11:37PM -0800, Allen Martin wrote:
> I don't think there's any faulty nForce IDE hardware or we would have heard
> about it from windows users (and we haven't).  

Ok.  I have never tested a motherboard driver for a problem like this.  But I'm starting to understand more.

I went ahead and tried more configurations.  I wish I had a pci ide card with 
udma 100, but the one I have is being used =(.  So I just had to make do with 
what I have.  The test is very simple, because it is very simple to trigger it. 
I just grep something very large.  It locks up almost immediately with 2.6 + 
apic + nvidia ide with dma enabled.

I ran grep on these devices:
IDE hard disk at UDMA 100, 100 MB/s, flat cable, 80w.  grep on kernel source.
same IDE hard disk with DMA disabled, 16 MB/s. grep on kernel source.
SCSI hard disk at 20 MB/s. grep on kernel source.
IDE 24x cdrom, 11 MB/s.  grepped whole cd-rom fs, about 300 MB.

During the test runs, I tried:
bios update -- no difference (same results no matter what)
preempt on/off -- no difference (same results)

The results (uniprocessor system):
1. under 2.6.0-test11 with nvidia ide, dma enabled, apic
grep on IDE hard disk at UDMA 100 -- locks nearly immediately
and later attempt, grep on cdrom -- doesn't lock up (still will lock up with 
hard disk though)

2. under 2.6.0-test11 with nvidia ide, dma, pic
grep on IDE hard disk at UDMA 100 -- doesn't lock up

3. under 2.4.23, with nvidia ide, dma enabled, apic
grep on IDE hard disk at UDMA 100 -- doesn't lock up

4. under 2.6.0-test11 with aic7xxx, ide completely disabled, apic
grep on SCSI disk -- doesn't lock up

5. under 2.6.0-test11 with nvidia ide, dma disabled, apic
grep on IDE hard disk at 16 MB/s -- doesn't lock up


So basically, I conclude that UDMA 100 will cause a lockup nearly immediately. 
The slower interfaces speeds don't cause a lockup during the test, but that 
doesn't mean the kernel will never lock up.  So DMA does produce a lockup 
faster.  Either longer stresses are required (which means spending more time =( 
I've only had the board for two days - heh heh), or more preferably, I need to
test with another pci ide controller.  Whatever it is, it seems to be the high
speeds like UDMA 100 or perhaps similarly stressing pci devices that will do it.


> 
> The problem with comparing the nForce IDE driver against the generic IDE
> driver is that the generic IDE driver won't enable DMA, so the interrupt
> rate will be much different.  If there's some interrupt race condition in
> APIC mode, disabling DMA may mask it.
> 

Yep, you're right.


Jesse

Re: NForce2 pseudoscience stability testing (2.6.0-test11)

[Craig Bradney]

The biggest problem is we are getting very different results here
(understatement!).

I'm running UDMA 133 on round 80w cables.

I can do a grep on kernel source, eg from /usr/src/linux
grep -R linus *
grep -R kernel *
and it happily returns all information I asked for.

Right now, I am also running grep over a 4gb dvd I recently wrote from
within 2.6. No crash.. in fact.. its still going as I type this. I can
run hdparm -I while its grepping and see its on udma2.


The one thing I DID notice when I was testing with preempt on was the
something similar to the following from the dmesg that Ross Alexander
sent (dont have the dmesg output anymore :( ):

hda: IRQ probe failed (0xfffffffa)
hdb: IRQ probe failed (0xfffffffa)
hdb: IRQ probe failed (0xfffffffa)


Now it all runs through ok as shown below.

NFORCE2: IDE controller at PCI slot 0000:00:09.0
NFORCE2: chipset revision 162
NFORCE2: not 100% native mode: will probe irqs later
NFORCE2: BIOS didn't set cable bits correctly. Enabling workaround.
ide: Assuming 33MHz system bus speed for PIO modes; override with
idebus=xx
NFORCE2: 0000:00:09.0 (rev a2) UDMA133 controller
    ide0: BM-DMA at 0xf000-0xf007, BIOS settings: hda:DMA, hdb:DMA
    ide1: BM-DMA at 0xf008-0xf00f, BIOS settings: hdc:DMA, hdd:DMA
hda: Maxtor 6Y080P0, ATA DISK drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
hdc: SONY DVD RW DRU-510A, ATAPI CD/DVD-ROM drive
hdd: SAMSUNG CD-ROM SC-152C, ATAPI CD/DVD-ROM drive
ide1 at 0x170-0x177,0x376 on irq 15
hda: max request size: 128KiB
hda: 160086528 sectors (81964 MB) w/7936KiB Cache, CHS=65535/16/63,
UDMA(133)
 /dev/ide/host0/bus0/target0/lun0: p1 p2 < p5 p6 p7 p8 >
hdc: ATAPI 32X DVD-ROM DVD-R CD-R/RW drive, 8192kB Cache, UDMA(33)
Uniform CD-ROM driver Revision: 3.12
hdd: ATAPI 52X CD-ROM drive, 128kB Cache, DMA

In answer to Bob's email that has just come in.. I see no IRQ7 disabled
messages.. just IRQ7 -> 0:7

Uptime is now over 5 hours with a decent amount of time idling and being
busy. 

Craig

PS.
cat /proc/interrupts
           CPU0
  0:   20104881          XT-PIC  timer
  1:      21139    IO-APIC-edge  i8042
  2:          0          XT-PIC  cascade
  8:          2    IO-APIC-edge  rtc
  9:          0   IO-APIC-level  acpi
 12:     192779    IO-APIC-edge  i8042
 14:     171638    IO-APIC-edge  ide0
 15:     101036    IO-APIC-edge  ide1
 19:    1507163   IO-APIC-level  radeon@PCI:3:0:0
 21:     276278   IO-APIC-level  ehci_hcd, NVidia nForce2, eth0
 22:          3   IO-APIC-level  ohci1394
NMI:          0
LOC:   20104718
ERR:          0
MIS:          0


On Thu, 2003-12-04 at 21:04, Jesse Allen wrote:
> On Wed, Dec 03, 2003 at 09:11:37PM -0800, Allen Martin wrote:
> > I don't think there's any faulty nForce IDE hardware or we would have heard
> > about it from windows users (and we haven't).  
> 
> Ok.  I have never tested a motherboard driver for a problem like this.  But I'm starting to understand more.
> 
> I went ahead and tried more configurations.  I wish I had a pci ide card with 
> udma 100, but the one I have is being used =(.  So I just had to make do with 
> what I have.  The test is very simple, because it is very simple to trigger it. 
> I just grep something very large.  It locks up almost immediately with 2.6 + 
> apic + nvidia ide with dma enabled.
> 
> I ran grep on these devices:
> IDE hard disk at UDMA 100, 100 MB/s, flat cable, 80w.  grep on kernel source.
> same IDE hard disk with DMA disabled, 16 MB/s. grep on kernel source.
> SCSI hard disk at 20 MB/s. grep on kernel source.
> IDE 24x cdrom, 11 MB/s.  grepped whole cd-rom fs, about 300 MB.
> 
> During the test runs, I tried:
> bios update -- no difference (same results no matter what)
> preempt on/off -- no difference (same results)
> 
> The results (uniprocessor system):
> 1. under 2.6.0-test11 with nvidia ide, dma enabled, apic
> grep on IDE hard disk at UDMA 100 -- locks nearly immediately
> and later attempt, grep on cdrom -- doesn't lock up (still will lock up with 
> hard disk though)
> 
> 2. under 2.6.0-test11 with nvidia ide, dma, pic
> grep on IDE hard disk at UDMA 100 -- doesn't lock up
> 
> 3. under 2.4.23, with nvidia ide, dma enabled, apic
> grep on IDE hard disk at UDMA 100 -- doesn't lock up
> 
> 4. under 2.6.0-test11 with aic7xxx, ide completely disabled, apic
> grep on SCSI disk -- doesn't lock up
> 
> 5. under 2.6.0-test11 with nvidia ide, dma disabled, apic
> grep on IDE hard disk at 16 MB/s -- doesn't lock up
> 
> 
> So basically, I conclude that UDMA 100 will cause a lockup nearly immediately. 
> The slower interfaces speeds don't cause a lockup during the test, but that 
> doesn't mean the kernel will never lock up.  So DMA does produce a lockup 
> faster.  Either longer stresses are required (which means spending more time =( 
> I've only had the board for two days - heh heh), or more preferably, I need to
> test with another pci ide controller.  Whatever it is, it seems to be the high
> speeds like UDMA 100 or perhaps similarly stressing pci devices that will do it.
> 
> 
> > 
> > The problem with comparing the nForce IDE driver against the generic IDE
> > driver is that the generic IDE driver won't enable DMA, so the interrupt
> > rate will be much different.  If there's some interrupt race condition in
> > APIC mode, disabling DMA may mask it.
> > 
> 
> Yep, you're right.
> 
> 
> Jesse
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
> 

Re: NForce2 pseudoscience stability testing (2.6.0-test11)

[Craig Bradney]

Then again.. returned to konsole to run dmesg.. bang.. dead.

This is ALL over the place

Craig

On Thu, 2003-12-04 at 21:41, Craig Bradney wrote:
> The biggest problem is we are getting very different results here
> (understatement!).
> 
> I'm running UDMA 133 on round 80w cables.
> 
> I can do a grep on kernel source, eg from /usr/src/linux
> grep -R linus *
> grep -R kernel *
> and it happily returns all information I asked for.
> 
> Right now, I am also running grep over a 4gb dvd I recently wrote from
> within 2.6. No crash.. in fact.. its still going as I type this. I can
> run hdparm -I while its grepping and see its on udma2.
> 
> 
> The one thing I DID notice when I was testing with preempt on was the
> something similar to the following from the dmesg that Ross Alexander
> sent (dont have the dmesg output anymore :( ):
> 
> hda: IRQ probe failed (0xfffffffa)
> hdb: IRQ probe failed (0xfffffffa)
> hdb: IRQ probe failed (0xfffffffa)
> 
> 
> Now it all runs through ok as shown below.
> 
> NFORCE2: IDE controller at PCI slot 0000:00:09.0
> NFORCE2: chipset revision 162
> NFORCE2: not 100% native mode: will probe irqs later
> NFORCE2: BIOS didn't set cable bits correctly. Enabling workaround.
> ide: Assuming 33MHz system bus speed for PIO modes; override with
> idebus=xx
> NFORCE2: 0000:00:09.0 (rev a2) UDMA133 controller
>     ide0: BM-DMA at 0xf000-0xf007, BIOS settings: hda:DMA, hdb:DMA
>     ide1: BM-DMA at 0xf008-0xf00f, BIOS settings: hdc:DMA, hdd:DMA
> hda: Maxtor 6Y080P0, ATA DISK drive
> ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
> hdc: SONY DVD RW DRU-510A, ATAPI CD/DVD-ROM drive
> hdd: SAMSUNG CD-ROM SC-152C, ATAPI CD/DVD-ROM drive
> ide1 at 0x170-0x177,0x376 on irq 15
> hda: max request size: 128KiB
> hda: 160086528 sectors (81964 MB) w/7936KiB Cache, CHS=65535/16/63,
> UDMA(133)
>  /dev/ide/host0/bus0/target0/lun0: p1 p2 < p5 p6 p7 p8 >
> hdc: ATAPI 32X DVD-ROM DVD-R CD-R/RW drive, 8192kB Cache, UDMA(33)
> Uniform CD-ROM driver Revision: 3.12
> hdd: ATAPI 52X CD-ROM drive, 128kB Cache, DMA
> 
> In answer to Bob's email that has just come in.. I see no IRQ7 disabled
> messages.. just IRQ7 -> 0:7
> 
> Uptime is now over 5 hours with a decent amount of time idling and being
> busy. 
> 
> Craig
> 
> PS.
> cat /proc/interrupts
>            CPU0
>   0:   20104881          XT-PIC  timer
>   1:      21139    IO-APIC-edge  i8042
>   2:          0          XT-PIC  cascade
>   8:          2    IO-APIC-edge  rtc
>   9:          0   IO-APIC-level  acpi
>  12:     192779    IO-APIC-edge  i8042
>  14:     171638    IO-APIC-edge  ide0
>  15:     101036    IO-APIC-edge  ide1
>  19:    1507163   IO-APIC-level  radeon@PCI:3:0:0
>  21:     276278   IO-APIC-level  ehci_hcd, NVidia nForce2, eth0
>  22:          3   IO-APIC-level  ohci1394
> NMI:          0
> LOC:   20104718
> ERR:          0
> MIS:          0
> 
> 
> On Thu, 2003-12-04 at 21:04, Jesse Allen wrote:
> > On Wed, Dec 03, 2003 at 09:11:37PM -0800, Allen Martin wrote:
> > > I don't think there's any faulty nForce IDE hardware or we would have heard
> > > about it from windows users (and we haven't).  
> > 
> > Ok.  I have never tested a motherboard driver for a problem like this.  But I'm starting to understand more.
> > 
> > I went ahead and tried more configurations.  I wish I had a pci ide card with 
> > udma 100, but the one I have is being used =(.  So I just had to make do with 
> > what I have.  The test is very simple, because it is very simple to trigger it. 
> > I just grep something very large.  It locks up almost immediately with 2.6 + 
> > apic + nvidia ide with dma enabled.
> > 
> > I ran grep on these devices:
> > IDE hard disk at UDMA 100, 100 MB/s, flat cable, 80w.  grep on kernel source.
> > same IDE hard disk with DMA disabled, 16 MB/s. grep on kernel source.
> > SCSI hard disk at 20 MB/s. grep on kernel source.
> > IDE 24x cdrom, 11 MB/s.  grepped whole cd-rom fs, about 300 MB.
> > 
> > During the test runs, I tried:
> > bios update -- no difference (same results no matter what)
> > preempt on/off -- no difference (same results)
> > 
> > The results (uniprocessor system):
> > 1. under 2.6.0-test11 with nvidia ide, dma enabled, apic
> > grep on IDE hard disk at UDMA 100 -- locks nearly immediately
> > and later attempt, grep on cdrom -- doesn't lock up (still will lock up with 
> > hard disk though)
> > 
> > 2. under 2.6.0-test11 with nvidia ide, dma, pic
> > grep on IDE hard disk at UDMA 100 -- doesn't lock up
> > 
> > 3. under 2.4.23, with nvidia ide, dma enabled, apic
> > grep on IDE hard disk at UDMA 100 -- doesn't lock up
> > 
> > 4. under 2.6.0-test11 with aic7xxx, ide completely disabled, apic
> > grep on SCSI disk -- doesn't lock up
> > 
> > 5. under 2.6.0-test11 with nvidia ide, dma disabled, apic
> > grep on IDE hard disk at 16 MB/s -- doesn't lock up
> > 
> > 
> > So basically, I conclude that UDMA 100 will cause a lockup nearly immediately. 
> > The slower interfaces speeds don't cause a lockup during the test, but that 
> > doesn't mean the kernel will never lock up.  So DMA does produce a lockup 
> > faster.  Either longer stresses are required (which means spending more time =( 
> > I've only had the board for two days - heh heh), or more preferably, I need to
> > test with another pci ide controller.  Whatever it is, it seems to be the high
> > speeds like UDMA 100 or perhaps similarly stressing pci devices that will do it.
> > 
> > 
> > > 
> > > The problem with comparing the nForce IDE driver against the generic IDE
> > > driver is that the generic IDE driver won't enable DMA, so the interrupt
> > > rate will be much different.  If there's some interrupt race condition in
> > > APIC mode, disabling DMA may mask it.
> > > 
> > 
> > Yep, you're right.
> > 
> > 
> > Jesse
> > -
> > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at  http://vger.kernel.org/majordomo-info.html
> > Please read the FAQ at  http://www.tux.org/lkml/
> > 
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
> 

Re: NForce2 pseudoscience stability testing (2.6.0-test11)

[Bob]

Craig Bradney wrote:

>Then again.. returned to konsole to run dmesg.. bang.. dead.
>
>This is ALL over the place
>
>Craig
>
>On Thu, 2003-12-04 at 21:41, Craig Bradney wrote:
>  
>
>>The biggest problem is we are getting very different results here
>>(understatement!).
>>
>>I'm running UDMA 133 on round 80w cables
>>    
>>
Pre-emptive kernel, apic lapic, anticipatory scheduling,
udma133 on round cables, four ide drives linux softw
raid0 on a 3ware card, two cd's on the onboard
amd controller. I can copy from my cd to my cdr
(through pipes) with no loopback file, compile kernel
while copying /usr/src/linux between partitions, htdig
index hundreds of megs while slicing and dicing
something else. The sound works.

Before a bios flash I had problems with anything
involving the pci bus(fsck, cp, compile, wav to mp3)
though not necessarily ide, and onboard amd ide was
much more stable. Now I am only lacking the usb and
onboard ethernet. Even though I have a dozen unused
interrupts, bios stupidly puts two or three things on one
interrupt and says "IRQ7 Disabled" if I turn on the ethernet
onboard chip. nforce2 ethernet is actually an intel chip, and
linux has a driver, but it doesn't work for me.

1) Bios update made cmos apic kernel ioapic lapic work,
probably due to new id info but the bios site doc does
not say ANYTHING, sorry!

2) Despite a dozen unused interrupts, two or more
agp and pci cards are assigned to the same interrupt,
which might cause problems. Stubborn-ness displayed
in assigning two or three cards including agp to the
same interrupt when a dozen irq's are free just might
be a sign of pseudo-idealogy displacing logic. Why
push it with agp8 and four hard drives on one irq,
or four hard drives and 802.11 and ethernet on one?
Why have 21 irq's but foot-binding to size 5 fits all?

>>I can do a grep on kernel source, eg from /usr/src/linux
>>grep -R linus *
>>grep -R kernel *
>>and it happily returns all information I asked for.
>>
>>Right now, I am also running grep over a 4gb dvd I recently wrote from
>>within 2.6. No crash.. in fact.. its still going as I type this. I can
>>run hdparm -I while its grepping and see its on udma2.
>>
>>
>>The one thing I DID notice when I was testing with preempt on was the
>>something similar to the following from the dmesg that Ross Alexander
>>sent (dont have the dmesg output anymore :( ):
>>
>>hda: IRQ probe failed (0xfffffffa)
>>hdb: IRQ probe failed (0xfffffffa)
>>hdb: IRQ probe failed (0xfffffffa)
>>
>>
>>Now it all runs through ok as shown below.
>>
>>NFORCE2: IDE controller at PCI slot 0000:00:09.0
>>NFORCE2: chipset revision 162
>>NFORCE2: not 100% native mode: will probe irqs later
>>NFORCE2: BIOS didn't set cable bits correctly. Enabling workaround.
>>ide: Assuming 33MHz system bus speed for PIO modes; override with
>>idebus=xx
>>NFORCE2: 0000:00:09.0 (rev a2) UDMA133 controller
>>    ide0: BM-DMA at 0xf000-0xf007, BIOS settings: hda:DMA, hdb:DMA
>>    ide1: BM-DMA at 0xf008-0xf00f, BIOS settings: hdc:DMA, hdd:DMA
>>hda: Maxtor 6Y080P0, ATA DISK drive
>>ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
>>hdc: SONY DVD RW DRU-510A, ATAPI CD/DVD-ROM drive
>>hdd: SAMSUNG CD-ROM SC-152C, ATAPI CD/DVD-ROM drive
>>ide1 at 0x170-0x177,0x376 on irq 15
>>hda: max request size: 128KiB
>>hda: 160086528 sectors (81964 MB) w/7936KiB Cache, CHS=65535/16/63,
>>UDMA(133)
>> /dev/ide/host0/bus0/target0/lun0: p1 p2 < p5 p6 p7 p8 >
>>hdc: ATAPI 32X DVD-ROM DVD-R CD-R/RW drive, 8192kB Cache, UDMA(33)
>>Uniform CD-ROM driver Revision: 3.12
>>hdd: ATAPI 52X CD-ROM drive, 128kB Cache, DMA
>>
>>In answer to Bob's email that has just come in.. I see no IRQ7 disabled
>>messages.. just IRQ7 -> 0:7
>>
>>Uptime is now over 5 hours with a decent amount of time idling and being
>>busy. 
>>
>>Craig
>>
>>PS.
>>cat /proc/interrupts
>>           CPU0
>>  0:   20104881          XT-PIC  timer
>>  1:      21139    IO-APIC-edge  i8042
>>  2:          0          XT-PIC  cascade
>>  8:          2    IO-APIC-edge  rtc
>>  9:          0   IO-APIC-level  acpi
>> 12:     192779    IO-APIC-edge  i8042
>> 14:     171638    IO-APIC-edge  ide0
>> 15:     101036    IO-APIC-edge  ide1
>> 19:    1507163   IO-APIC-level  radeon@PCI:3:0:0
>> 21:     276278   IO-APIC-level  ehci_hcd, NVidia nForce2, eth0
>> 22:          3   IO-APIC-level  ohci1394
>>NMI:          0
>>LOC:   20104718
>>ERR:          0
>>MIS:          0
>>
>>
>>On Thu, 2003-12-04 at 21:04, Jesse Allen wrote:
>>    
>>
>>>On Wed, Dec 03, 2003 at 09:11:37PM -0800, Allen Martin wrote:
>>>      
>>>
>>>>I don't think there's any faulty nForce IDE hardware or we would have heard
>>>>about it from windows users (and we haven't).  
>>>>        
>>>>
>>>Ok.  I have never tested a motherboard driver for a problem like this.  But I'm starting to understand more.
>>>
>>>I went ahead and tried more configurations.  I wish I had a pci ide card with 
>>>udma 100, but the one I have is being used =(.  So I just had to make do with 
>>>what I have.  The test is very simple, because it is very simple to trigger it. 
>>>I just grep something very large.  It locks up almost immediately with 2.6 + 
>>>apic + nvidia ide with dma enabled.
>>>
>>>I ran grep on these devices:
>>>IDE hard disk at UDMA 100, 100 MB/s, flat cable, 80w.  grep on kernel source.
>>>same IDE hard disk with DMA disabled, 16 MB/s. grep on kernel source.
>>>SCSI hard disk at 20 MB/s. grep on kernel source.
>>>IDE 24x cdrom, 11 MB/s.  grepped whole cd-rom fs, about 300 MB.
>>>
>>>During the test runs, I tried:
>>>bios update -- no difference (same results no matter what)
>>>preempt on/off -- no difference (same results)
>>>
>>>The results (uniprocessor system):
>>>1. under 2.6.0-test11 with nvidia ide, dma enabled, apic
>>>grep on IDE hard disk at UDMA 100 -- locks nearly immediately
>>>and later attempt, grep on cdrom -- doesn't lock up (still will lock up with 
>>>hard disk though)
>>>
>>>2. under 2.6.0-test11 with nvidia ide, dma, pic
>>>grep on IDE hard disk at UDMA 100 -- doesn't lock up
>>>
>>>3. under 2.4.23, with nvidia ide, dma enabled, apic
>>>grep on IDE hard disk at UDMA 100 -- doesn't lock up
>>>
>>>4. under 2.6.0-test11 with aic7xxx, ide completely disabled, apic
>>>grep on SCSI disk -- doesn't lock up
>>>
>>>5. under 2.6.0-test11 with nvidia ide, dma disabled, apic
>>>grep on IDE hard disk at 16 MB/s -- doesn't lock up
>>>
>>>
>>>So basically, I conclude that UDMA 100 will cause a lockup nearly immediately. 
>>>The slower interfaces speeds don't cause a lockup during the test, but that 
>>>doesn't mean the kernel will never lock up.  So DMA does produce a lockup 
>>>faster.  Either longer stresses are required (which means spending more time =( 
>>>I've only had the board for two days - heh heh), or more preferably, I need to
>>>test with another pci ide controller.  Whatever it is, it seems to be the high
>>>speeds like UDMA 100 or perhaps similarly stressing pci devices that will do it.
>>>
>>>
>>>      
>>>
>>>>The problem with comparing the nForce IDE driver against the generic IDE
>>>>driver is that the generic IDE driver won't enable DMA, so the interrupt
>>>>rate will be much different.  If there's some interrupt race condition in
>>>>APIC mode, disabling DMA may mask it.
>>>>
>>>>        
>>>>
>>>Yep, you're right.
>>>
>>>
>>>Jesse
>>>-
>>>To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
>>>the body of a message to majordomo@vger.kernel.org
>>>More majordomo info at  http://vger.kernel.org/majordomo-info.html
>>>Please read the FAQ at  http://www.tux.org/lkml/
>>>
>>>      
>>>
>>-
>>To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
>>the body of a message to majordomo@vger.kernel.org
>>More majordomo info at  http://vger.kernel.org/majordomo-info.html
>>Please read the FAQ at  http://www.tux.org/lkml/
>>
>>    
>>
>
>-
>To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
>the body of a message to majordomo@vger.kernel.org
>More majordomo info at  http://vger.kernel.org/majordomo-info.html
>Please read the FAQ at  http://www.tux.org/lkml/
>
>  
>

RE: NForce2 pseudoscience stability testing (2.6.0-test11)

[b]

Allen Martin wrote:
 >Also are people who are having problems using rounded or flat
 >cables?  It's
 >possible the problem could be related to DMA CRC errors.
 >Switching to flat
 >cables can help with that.
 >
 >-Allen

I'm using the one that came with the board, flat 80 wire. It
works under extreme stress in Windows 2000. It doesnt work
in Linux.


(I generated millions of interrupts from IDE and network
(dual gigabit) in Windows 2000 on this very hardware for
3 days - thats why I came to the LKML, I did an empirical
test that indicated Linux, and did some reading and others
have had similar problems.)

RE: NForce2 pseudoscience stability testing (2.6.0-test11)

[Craig Bradney]

Ok folks.. 

first crash here.. complete lockup. No idea how related it was to the
ones others are experiencing. 

Uptime at that point was 5 days 8:07. 

I was just running an emerge sync on Gentoo. I had been away from the PC
for a few hours (it had been recompiling mozilla in that time) but I had
woken it up for at least 20 mins before the crash.

So now the uptime run has died.. is there anything people want me to
test re kernel config?

I'm running round 80 wire IDE cables btw.

Craig


On Thu, 2003-12-04 at 06:37, b@netzentry.com wrote:
> Allen Martin wrote:
>  >Also are people who are having problems using rounded or flat
>  >cables?  It's
>  >possible the problem could be related to DMA CRC errors.
>  >Switching to flat
>  >cables can help with that.
>  >
>  >-Allen
> 
> I'm using the one that came with the board, flat 80 wire. It
> works under extreme stress in Windows 2000. It doesnt work
> in Linux.
> 
> 
> (I generated millions of interrupts from IDE and network
> (dual gigabit) in Windows 2000 on this very hardware for
> 3 days - thats why I came to the LKML, I did an empirical
> test that indicated Linux, and did some reading and others
> have had similar problems.)
> 
> 
> 
> 
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
> 

RE: NForce2 pseudoscience stability testing (2.6.0-test11)

[b]

This is the nature of this problem. I have seen reports
it can hold out for sometimes a week.

We need patches to try on 2.6 and 2.4 bad.

Craig Bradney wrote
 >Ok folks..
 >
 >first crash here.. complete lockup. No idea how related it was to
 > the ones others are experiencing.
 >
 >Uptime at that point was 5 days 8:07.
 >
 >I was just running an emerge sync on Gentoo. I had been away
 >from the PC
 >for a few hours (it had been recompiling mozilla in that time)
 >but I had
 >woken it up for at least 20 mins before the crash.
 >
 >So now the uptime run has died.. is there anything people want me
 > to test re kernel config?
 >
 >I'm running round 80 wire IDE cables btw.
 >
 >Craig
 >
 >
 >On Thu, 2003-12-04 at 06:37, b@netzentry.com wrote:
 >> Allen Martin wrote:
 >>  >Also are people who are having problems using rounded or flat
 >>  >cables?  It's
 >>  >possible the problem could be related to DMA CRC errors.
 >>  >Switching to flat
 >>  >cables can help with that.
 >>  >
 >>  >-Allen
 >>
 >> I'm using the one that came with the board, flat 80 wire. It
 >> works under extreme stress in Windows 2000. It doesnt work
 >> in Linux.
 >>
 >>
 >> (I generated millions of interrupts from IDE and network
 >> (dual gigabit) in Windows 2000 on this very hardware for
 >> 3 days - thats why I came to the LKML, I did an empirical
 >> test that indicated Linux, and did some reading and others
 >> have had similar problems.)

RE: NForce2 pseudoscience stability testing (2.6.0-test11)

[b]

Prakash Cheemplavam wrote
 >>>Thanks everyone for your continued interest in this, I'll
 >>>try and test the no-onboard-PATA + UP LAPIC and IOAPIC and
 >>>add-in-card-PATA with no onboard PATA + + UP LAPIC and IOAPIC
 >>>when I get a spare moment which is rare.
 >
 >I don't think that the AMD IDE is the problem. I have compiled
 >it in, as
 >well, but I am using the onboard SATA. Since this can be
 >considered as  >an pci-card (the chip is connected to the pci
 > bridge) I think ölocking occurs on high traffic on PCI bus.
 > Like now I get over 60mb/s with my >HD. Formerly I got only
 > 25mb/s. before I could do some rounds of hdparm -t, before it
 > locks. Now it locks immediately when doing hdparm -t
 > when  APIC is enabled.
 >
 >SO, I think it is not IDE specific. Does anybody have gigabit
 > network card? Maybe that we should try to push something big
 > through it (without reading from hd). If that leads to lock
 > up we have a semi proof that it is due to high traffic on
 > pci-bus.

I was thinking that myself (PCI activity triggering this).
The first time I hit this problem was with a card with two
ACENics/tigon2 (acenic.o) sniffing traffic at high rates
(100,000pps+) with most file i/o going over NFS on the
integrated 3com interface.

I ran for three days 200,000+pps sniffing with tethereal on
windows2000 on both acenics and never a lockup.

The AMD-Nvidia PATA does seem to be a very common in this
problem, but everyone at least has a CD-ROM and most
have a PATA hard disk so its going to be there every time
a problems crops up. I think we need to prove that an
solid add-in PCI PATA card that takes the CD and the
and the PATA disk and shut off the onboard ATA and torture
test again. I havent had time to yet.

RE: NForce2 pseudoscience stability testing (2.6.0-test11)

[b]

Dan Creswell wrote:

Thanks for the input, I'll pass it to the list.

Most of these Athlon victims are UP users, in fact, I
believe they are exclusively UP. Does MPS 1.1/1.4 play a role
in a UP system ever? I dont think the NForce2 chipset,
where we are seeing these hard hangs (no ping, no screen,
no blinking cursor, no toggling the caps lock, nothing) is
capable of SMP operation.

Now whats interesting is you finger the IDE as a potential
culprit and think its very low level. Interesting.

By the way, I've had trouble with SMP on a Tyan board with an
i840 chipset with Linux before - I was never able to resolve
the issue and had to return the board.

I've beaten on an Intel SR1300 and SR2300 dual Xeon (aka
Micron's Netframe 1610/2610 aka Sun 60x / 65x) and never run
into these hangs with kernels up to 2.4.22. The motherboard
is an Intel SE7501WV2 .


 >Hi,
 >Been following this thread silently for a while and thought
 >I'd drop you
 >a line as I have some other data you may find useful.
 >
 >My machine is a dual Xeon with 2Gb, E1000 NIC, MPT LSI SCSI
 >disks and an
 >IDE CDROM.
 >
 >2.6-test9 is only stable on this machine with noapic passed in the
 >kernel parameters - otherwise, it lock's up in no time flat.
 >I can also
 >run this kernel in single-processor mode with the APIC enabled and
 >that's stable.
 >
 >2.4.23-rc2 runs fine on the same machine with the APIC enabled
 >in SMP mode.
 >
 >2.4.23-rc5 locks up on this machine if I use the same .config as
for
 >-rc2.  However, if I disable ACPI and pass "pci=noacpi" to the
kernel,
 >this too runs fine.
 >    - Seems like the ACPI changes in -rc3 are a problem for my
machine.
 >
 >All of these behaviors have been observed with MPS 1.4 (I've
changed
 >that BIOS setting to 1.1 today in preparation for more testing of
the
 >above to see if that makes a difference).
 >
 >I mention all of this because none of my lock-ups have happened
whilst
 >accessing the IDE subsystem.  I *have* had lockups with
simultaneous
 >network and disk access and I've also seen it with simply
 >mouse-waggling.  I suspect that the problem is *very* low-level
and
 >likely related to the interrupt load.  In my case, the problems
only
 >seem to occur with SMP configurations which makes me suspect there
may
 >be a locking/simultaneous update problem.
 >
 >Oh, forgot to say, my motherboard is a Tyan Thunder S2665
 >(based on the
 >intel E7505 chipset).
 >
 >Hope that helps,
 >
 >Dan.

RE: NForce2 pseudoscience stability testing (2.6.0-test11)

[Craig Bradney]

As reported earlier today I had the first lockup this morning in over 5
days uptime. Having had that, I decided to go for the latest gentoo 2.6
test 11-r1 kernel. This means I was now running the following patches:
http://dev.gentoo.org/~brad_mssw/kernel_patches/2.6.0/genpatches-0.7/
instead of
http://dev.gentoo.org/~brad_mssw/kernel_patches/2.6.0/genpatches-0.6/
on top of vanilla test 11.

Anyway.. my two changes on rebuilding the kernel were initially:
-Add in preempt (because there were questions asked here) 
-Remove generic IDE support (I know I have Nvidia IDE so lets only have
that one).

In that configuration the "multiple hdparm -t /dev/hda" test hung my
system.

Rebuilt kernel without preempt.. no hang on hdparm test. 

So in summary, apart from the patch changes as above, the only
difference is to my 5 day kernel I now dont have generic IDE support
included.

So now, I'll leave it on and see how far it goes.. 13 mins so far :).

regards
Craig


On Thu, 2003-12-04 at 13:17, b@netzentry.com wrote:
> Dan Creswell wrote:
> 
> Thanks for the input, I'll pass it to the list.
> 
> Most of these Athlon victims are UP users, in fact, I
> believe they are exclusively UP. Does MPS 1.1/1.4 play a role
> in a UP system ever? I dont think the NForce2 chipset,
> where we are seeing these hard hangs (no ping, no screen,
> no blinking cursor, no toggling the caps lock, nothing) is
> capable of SMP operation.
> 
> Now whats interesting is you finger the IDE as a potential
> culprit and think its very low level. Interesting.
> 
> By the way, I've had trouble with SMP on a Tyan board with an
> i840 chipset with Linux before - I was never able to resolve
> the issue and had to return the board.
> 
> I've beaten on an Intel SR1300 and SR2300 dual Xeon (aka
> Micron's Netframe 1610/2610 aka Sun 60x / 65x) and never run
> into these hangs with kernels up to 2.4.22. The motherboard
> is an Intel SE7501WV2 .
> 
> 
>  >Hi,
>  >Been following this thread silently for a while and thought
>  >I'd drop you
>  >a line as I have some other data you may find useful.
>  >
>  >My machine is a dual Xeon with 2Gb, E1000 NIC, MPT LSI SCSI
>  >disks and an
>  >IDE CDROM.
>  >
>  >2.6-test9 is only stable on this machine with noapic passed in the
>  >kernel parameters - otherwise, it lock's up in no time flat.
>  >I can also
>  >run this kernel in single-processor mode with the APIC enabled and
>  >that's stable.
>  >
>  >2.4.23-rc2 runs fine on the same machine with the APIC enabled
>  >in SMP mode.
>  >
>  >2.4.23-rc5 locks up on this machine if I use the same .config as
> for
>  >-rc2.  However, if I disable ACPI and pass "pci=noacpi" to the
> kernel,
>  >this too runs fine.
>  >    - Seems like the ACPI changes in -rc3 are a problem for my
> machine.
>  >
>  >All of these behaviors have been observed with MPS 1.4 (I've
> changed
>  >that BIOS setting to 1.1 today in preparation for more testing of
> the
>  >above to see if that makes a difference).
>  >
>  >I mention all of this because none of my lock-ups have happened
> whilst
>  >accessing the IDE subsystem.  I *have* had lockups with
> simultaneous
>  >network and disk access and I've also seen it with simply
>  >mouse-waggling.  I suspect that the problem is *very* low-level
> and
>  >likely related to the interrupt load.  In my case, the problems
> only
>  >seem to occur with SMP configurations which makes me suspect there
> may
>  >be a locking/simultaneous update problem.
>  >
>  >Oh, forgot to say, my motherboard is a Tyan Thunder S2665
>  >(based on the
>  >intel E7505 chipset).
>  >
>  >Hope that helps,
>  >
>  >Dan.
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
> 

Re: NForce2 pseudoscience stability testing (2.6.0-test11)

[Josh McKinney]

On approximately Thu, Dec 04, 2003 at 04:19:10PM +0100, Craig Bradney wrote:
> As reported earlier today I had the first lockup this morning in over 5
> days uptime. Having had that, I decided to go for the latest gentoo 2.6
> test 11-r1 kernel. This means I was now running the following patches:
> http://dev.gentoo.org/~brad_mssw/kernel_patches/2.6.0/genpatches-0.7/
> instead of
> http://dev.gentoo.org/~brad_mssw/kernel_patches/2.6.0/genpatches-0.6/
> on top of vanilla test 11.
> 
> Anyway.. my two changes on rebuilding the kernel were initially:
> -Add in preempt (because there were questions asked here) 
> -Remove generic IDE support (I know I have Nvidia IDE so lets only have
> that one).
> 
> In that configuration the "multiple hdparm -t /dev/hda" test hung my
> system.
> 
> Rebuilt kernel without preempt.. no hang on hdparm test. 
> 
> So in summary, apart from the patch changes as above, the only
> difference is to my 5 day kernel I now dont have generic IDE support
> included.
> 
> So now, I'll leave it on and see how far it goes.. 13 mins so far :).
> 
> regards
> Craig
> 
> 

Just to add more inconsistency into the mix, I am running with preempt
enabled, generic ide disabled, and can't make it crash.  Ran netperf for
an hour over a crossover cable on 100mbit, a couple make -j 30 kernel
compiles, dbench, and playing some mp3's all at the same time and
nothing happens despite load average reaching over 100.  Maybe I am just
lucky.


-- 
Josh McKinney		     |	Webmaster: http://joshandangie.org
--------------------------------------------------------------------------
                             | They that can give up essential liberty
Linux, the choice       -o)  | to obtain a little temporary safety deserve 
of the GNU generation    /\  | neither liberty or safety. 
                        _\_v |                          -Benjamin Franklin

Re: NForce2 pseudoscience stability testing (2.6.0-test11)

[Julien Oster]

Josh McKinney <forming@charter.net> writes:

Hello Josh,

> Just to add more inconsistency into the mix, I am running with preempt
> enabled, generic ide disabled, and can't make it crash.  Ran netperf for
> an hour over a crossover cable on 100mbit, a couple make -j 30 kernel
> compiles, dbench, and playing some mp3's all at the same time and
> nothing happens despite load average reaching over 100.  Maybe I am just
> lucky.

Or maybe not.

In the very beginning, 1 or 2 months ago right after I bought the
board, it did crash but it actually didn't crash very often. In fact,
most of the time (not every time, but most!) it crashed while the
system being rather idle. To add even more perplexity to it: I could
work on the system for hours and then leave the computer half an hour
alone for talking a walk or jogging or whatever and, after coming
back, run across a complete lockup. Normally, the clock applet on my
desktop told me that the box crashed several minutes after I went out,
since the clock of course froze with the mainboard as well.

A lot changed by now, hardware and software, and now I'm hardly able
to run the system with ACPI/APIC enabled at all. If the boot procedure
goes fine, it locks up shortly after. If fsck decides to check the
disks, the mainboard is doomed to lock up away immediately.

That really is a nasty problem.

Regards,
Julien

Re: NForce2 pseudoscience stability testing (2.6.0-test11)

[Josh McKinney]

On approximately Thu, Dec 04, 2003 at 06:08:29PM +0100, Julien Oster wrote:
> Josh McKinney <forming@charter.net> writes:
> 
> Hello Josh,
> 
> > Just to add more inconsistency into the mix, I am running with preempt
> > enabled, generic ide disabled, and can't make it crash.  Ran netperf for
> > an hour over a crossover cable on 100mbit, a couple make -j 30 kernel
> > compiles, dbench, and playing some mp3's all at the same time and
> > nothing happens despite load average reaching over 100.  Maybe I am just
> > lucky.
> 
> Or maybe not.
> 
> In the very beginning, 1 or 2 months ago right after I bought the
> board, it did crash but it actually didn't crash very often. In fact,
> most of the time (not every time, but most!) it crashed while the
> system being rather idle. To add even more perplexity to it: I could
> work on the system for hours and then leave the computer half an hour
> alone for talking a walk or jogging or whatever and, after coming
> back, run across a complete lockup. Normally, the clock applet on my
> desktop told me that the box crashed several minutes after I went out,
> since the clock of course froze with the mainboard as well.
> 
> A lot changed by now, hardware and software, and now I'm hardly able
> to run the system with ACPI/APIC enabled at all. If the boot procedure
> goes fine, it locks up shortly after. If fsck decides to check the
> disks, the mainboard is doomed to lock up away immediately.
> 
> That really is a nasty problem.
> 

This issue seems to be funny like that.  When I first recieved this
mobo I too had crashes like you say you are having now.  Doing
practically anything would make it crash, passing noapic and nolapic
on boot solved the problems.  Now, as I said, stable with all ACPI
APIC LAPIC enabled.  I haven't changed any hardware or anything
either, except for now I am using the nvidia ethernet with the
forcedeth driver, but I somehow don't think that has anything to do
with it, maybe it is worth looking into. 

-- 
Josh McKinney		     |	Webmaster: http://joshandangie.org
--------------------------------------------------------------------------
                             | They that can give up essential liberty
Linux, the choice       -o)  | to obtain a little temporary safety deserve 
of the GNU generation    /\  | neither liberty or safety. 
                        _\_v |                          -Benjamin Franklin

Re: NForce2 pseudoscience stability testing (2.6.0-test11)

[Pat Erley]

I'm going to add my AMD/Nvidia IDE experiences as well as my current nforce2 experience.

Firstly, aside from the forcedeth module vs. nvnet hacked, I have never even known of problems with nforce2 systems.  I have a shuttle mn31/n (micro ATX) and I can use firewire, ide hd running udma5, ide cd running udma2, and the only thing I can do to crash/hang the system is to force unload a module.  It's running apic, lapic, acpi quite happily, no preempt, run every test since around 2.5.75.

noteing that.  I have to run my FSB underclocked by 1 mhz.

my cpu claims to be an xp2400(133/266fsb) but I run it at 132/264.  It was hanging/rebooting due to heat.

my other system (a little off topic here)  is a dual athlon athlon-mp tyan thunder k7 system.  will NOT run with apic and the amd ide driver.

pat erley

Re: NForce2 pseudoscience stability testing (2.6.0-test11)

[Dan Creswell]

Sorry, should've sent this CC'd to list first time (time to make some 
more coffee :)


-------- Original Message --------
Subject: 	Re: NForce2 pseudoscience stability testing (2.6.0-test11)
Date: 	Thu, 04 Dec 2003 12:38:21 +0000
From: 	Dan Creswell <dan@dcrdev.demon.co.uk>
To: 	b@netzentry.com
References: 	<3FCF25F2.6060008@netzentry.com>



b@netzentry.com wrote:

> Dan Creswell wrote:
>
> Thanks for the input, I'll pass it to the list.
>
You're welcome.

> Most of these Athlon victims are UP users, in fact, I
> believe they are exclusively UP. Does MPS 1.1/1.4 play a role
> in a UP system ever? I dont think the NForce2 chipset,

No, MPS shouldn't matter on a UP system.

> where we are seeing these hard hangs (no ping, no screen,
> no blinking cursor, no toggling the caps lock, nothing) is
> capable of SMP operation.
>
> Now whats interesting is you finger the IDE as a potential
> culprit and think its very low level. Interesting.
>
Well, I actually finger heavy duty disk access - my system locks under 
*SCSI* load (via a PCI-card - the motherboard doesn't have built in 
SCSI), I've not had it happen with my CDROM which is on the IDE 
subsystem.  This leads me to my conclusion in respect of interrupt 
load.  It seems to be an issue with simultaneous interrupts from another 
source but that's subjective......

> By the way, I've had trouble with SMP on a Tyan board with an
> i840 chipset with Linux before - I was never able to resolve
> the issue and had to return the board.
>
Interesting - I've had a number of Tyan boards and this is the first one 
I've had any issues with.  What bugs me more is that 2.4 seems fine 
(caveat 2.4.23-rc5 - wondering if the ACPI changes here are back-ported 
from 2.6) whilst 2.6 is horrid.  This is the only thing changing in the 
system which implies that something different goes on in 2.6 from 2.4 
and that it break's things.  Now it could be 2.6 is using some 
additional features - but the problem (once located) would be simply 
removed by providing an "off" switch to stop usage of those features.

> I've beaten on an Intel SR1300 and SR2300 dual Xeon (aka
> Micron's Netframe 1610/2610 aka Sun 60x / 65x) and never run
> into these hangs with kernels up to 2.4.22. The motherboard
> is an Intel SE7501WV2 .
>
Okay - well my Tyan also runs on kernels up to 2.4.22 no problem - 
useful information though.

Thanks,

Dan.