Failing back to INSANE timesource :) Time stopped today.

Failing back to INSANE timesource :) Time stopped today.

[Niclas Gustafsson]

Hi,

I'm running Linux 2.6.5  on a IBM xSeries 305 with a Intel P4 2.8Ghz.

And something is very very wrong, I'm getting the following last
messages in dmesg:

------
set_rtc_mmss: can't update from 52 to 0
set_rtc_mmss: can't update from 53 to 1
set_rtc_mmss: can't update from 54 to 2
set_rtc_mmss: can't update from 55 to 3
set_rtc_mmss: can't update from 56 to 4
set_rtc_mmss: can't update from 57 to 5
set_rtc_mmss: can't update from 58 to 6
Losing too many ticks!
TSC cannot be used as a timesource.  <4>Possible reasons for this are:
  You're running with Speedstep,
  You don't have DMA enabled for your hard disk (see hdparm),
  Incorrect TSC synchronization on an SMP system (see dmesg).
------

The problem seesm to be related to heavy loads.
I experienced a similar problem yesterday. The machine completly hung
after that and i had to cut the power to reboot it. Now however it is
responsive and I can log on to it through ssh.

Problem is that the clock stopped completly! - I've never seen anything
like this before. 

Local time is about 11 am here and a time gives me:

[root@s151 root]# date
Thu Apr  8 03:51:21 CEST 2004

...10 s later, using my wristwatch, not sleep 10 ;)

[root@s151 root]# date
Thu Apr  8 03:51:21 CEST 2004


Any ideas anyone, I'd really like to know why it is behaving this way.


Other usful(?) info from dmesg:
---
Detected 2800.731 MHz processor.
Using tsc for high-res timesource
...
init IO_APIC IRQs
 IO-APIC (apicid-pin) 1-0, 2-0, 2-1, 2-2, 2-3, 2-4, 2-5, 2-6, 2-7, 2-8,
2-9, 2-10, 2-11, 2-12, 2-13, 2-14, 2-15, 3-0, 3-1, 3-2, 3-3, 3-4, 3-5,
3-6, 3-7, 3-8, 3-9, 3-10, 3-11, 3-12, 3-13, 3-14, 3-15 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... works.
Using local APIC timer interrupts.
calibrating APIC timer ...
..... CPU clock speed is 2798.0750 MHz.
...
----

Oh, yeah, I'm running NTP on the machine, however the client seems to be
sleeping for the next time-poll.
I'm also using this machine as a ntp server and one client has the
following to say:

[root@s131 tmp]# ntpdc
ntpdc> peers
     remote           local      st poll reach  delay   offset    disp
=======================================================================
*time2 192.168.4.131  2 1024  377 0.00067  0.004991 0.01482
=time1 192.168.4.131  2 1024  377 0.00085  0.000558 0.01485
=s151  192.168.4.131  3 1024  377 0.00021 -25494.16 0.01482

Where s151 is the machine that is on freeze.



Cheers,

Niclas

Re: Failing back to INSANE timesource :) Time stopped today.

[Niclas Gustafsson]

Running multiple date commands ( ~ 1s apart ), shows that something is
going on...

[root@s151 root]# date "+%X %N"
03:51:21 AM 262889000
[root@s151 root]# date "+%X %N"
03:51:21 AM 263185000
[root@s151 root]# date "+%X %N"
03:51:21 AM 262383000
[root@s151 root]# date "+%X %N"
03:51:21 AM 263328000
[root@s151 root]# date "+%X %N"
03:51:21 AM 263237000
[root@s151 root]# date "+%X %N"
03:51:21 AM 263049000
[root@s151 root]# date "+%X %N"
03:51:21 AM 262941000


... And a couple of hours later:

[root@s151 root]# date "+%X  %N"
03:51:21 AM  348003000

Regards,

Niclas

tor 2004-04-08 klockan 11.21 skrev Niclas Gustafsson:
> Hi,
> 
> I'm running Linux 2.6.5  on a IBM xSeries 305 with a Intel P4 2.8Ghz.
> 
> And something is very very wrong, I'm getting the following last
> messages in dmesg:
> 
> ------
> set_rtc_mmss: can't update from 52 to 0
> set_rtc_mmss: can't update from 53 to 1
> set_rtc_mmss: can't update from 54 to 2
> set_rtc_mmss: can't update from 55 to 3
> set_rtc_mmss: can't update from 56 to 4
> set_rtc_mmss: can't update from 57 to 5
> set_rtc_mmss: can't update from 58 to 6
> Losing too many ticks!
> TSC cannot be used as a timesource.  <4>Possible reasons for this are:
>   You're running with Speedstep,
>   You don't have DMA enabled for your hard disk (see hdparm),
>   Incorrect TSC synchronization on an SMP system (see dmesg).
> ------
> 
> The problem seesm to be related to heavy loads.
> I experienced a similar problem yesterday. The machine completly hung
> after that and i had to cut the power to reboot it. Now however it is
> responsive and I can log on to it through ssh.
> 
> Problem is that the clock stopped completly! - I've never seen anything
> like this before. 
> 
> Local time is about 11 am here and a time gives me:
> 
> [root@s151 root]# date
> Thu Apr  8 03:51:21 CEST 2004
> 
> ...10 s later, using my wristwatch, not sleep 10 ;)
> 
> [root@s151 root]# date
> Thu Apr  8 03:51:21 CEST 2004
> 
> 
> Any ideas anyone, I'd really like to know why it is behaving this way.
> 
> 
> Other usful(?) info from dmesg:
> ---
> Detected 2800.731 MHz processor.
> Using tsc for high-res timesource
> ...
> init IO_APIC IRQs
>  IO-APIC (apicid-pin) 1-0, 2-0, 2-1, 2-2, 2-3, 2-4, 2-5, 2-6, 2-7, 2-8,
> 2-9, 2-10, 2-11, 2-12, 2-13, 2-14, 2-15, 3-0, 3-1, 3-2, 3-3, 3-4, 3-5,
> 3-6, 3-7, 3-8, 3-9, 3-10, 3-11, 3-12, 3-13, 3-14, 3-15 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... works.
> Using local APIC timer interrupts.
> calibrating APIC timer ...
> ..... CPU clock speed is 2798.0750 MHz.
> ...
> ----
> 
> Oh, yeah, I'm running NTP on the machine, however the client seems to be
> sleeping for the next time-poll.
> I'm also using this machine as a ntp server and one client has the
> following to say:
> 
> [root@s131 tmp]# ntpdc
> ntpdc> peers
>      remote           local      st poll reach  delay   offset    disp
> =======================================================================
> *time2 192.168.4.131  2 1024  377 0.00067  0.004991 0.01482
> =time1 192.168.4.131  2 1024  377 0.00085  0.000558 0.01485
> =s151  192.168.4.131  3 1024  377 0.00021 -25494.16 0.01482
> 
> Where s151 is the machine that is on freeze.
> 
> 
> 
> Cheers,
> 
> Niclas
> 
> 
> 
> 
> 

Re: Failing back to INSANE timesource :) Time stopped today.

[john stultz]

On Thu, 2004-04-08 at 02:21, Niclas Gustafsson wrote:
> Hi,
> 
> I'm running Linux 2.6.5  on a IBM xSeries 305 with a Intel P4 2.8Ghz.
> 
> And something is very very wrong, I'm getting the following last
> messages in dmesg:
> 
> ------
> set_rtc_mmss: can't update from 52 to 0
> set_rtc_mmss: can't update from 53 to 1
> set_rtc_mmss: can't update from 54 to 2
> set_rtc_mmss: can't update from 55 to 3
> set_rtc_mmss: can't update from 56 to 4
> set_rtc_mmss: can't update from 57 to 5
> set_rtc_mmss: can't update from 58 to 6
> Losing too many ticks!
> TSC cannot be used as a timesource.  <4>Possible reasons for this are:
>   You're running with Speedstep,
>   You don't have DMA enabled for your hard disk (see hdparm),
>   Incorrect TSC synchronization on an SMP system (see dmesg).
> ------
> 
> The problem seesm to be related to heavy loads.
> I experienced a similar problem yesterday. The machine completly hung
> after that and i had to cut the power to reboot it. Now however it is
> responsive and I can log on to it through ssh.
> 
> Problem is that the clock stopped completly! - I've never seen anything
> like this before. 
> 
> Local time is about 11 am here and a time gives me:
> 
> [root@s151 root]# date
> Thu Apr  8 03:51:21 CEST 2004
> 
> ...10 s later, using my wristwatch, not sleep 10 ;)
> 
> [root@s151 root]# date
> Thu Apr  8 03:51:21 CEST 2004
> 
> 
> Any ideas anyone, I'd really like to know why it is behaving this way.

Huh. Very very odd.  

Does /proc/interrupts show timer ticks increasing? 
Does setting the date change anything? 

Would you mind sending me your complete dmesg? 

I'll look into reproducing the error here if you can give me a better
description of what triggers it and how frequently you see the problem.

thanks
-john

Re: Failing back to INSANE timesource :) Time stopped today.

[Niclas Gustafsson]

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

Hi,

Sorry for the late reply I was away on Easter holidays.

I'm attaching both the dmesg output (dmesg.265-IBM305_2) and the
unpacked /proc/config.gz (config.gz.IBM_265_2)

However the last lines from dmesg:
---
> set_rtc_mmss: can't update from 52 to 0
> > set_rtc_mmss: can't update from 53 to 1
> > set_rtc_mmss: can't update from 54 to 2
> > set_rtc_mmss: can't update from 55 to 3
> > set_rtc_mmss: can't update from 56 to 4
> > set_rtc_mmss: can't update from 57 to 5
> > set_rtc_mmss: can't update from 58 to 6
> > Losing too many ticks!
> > TSC cannot be used as a timesource.  <4>Possible reasons for this are:
> >   You're running with Speedstep,
> >   You don't have DMA enabled for your hard disk (see hdparm),
> >   Incorrect TSC synchronization on an SMP system (see dmesg).
---

Were not synched to disk before I rebooted the system.


I've compiled a new kernel that seems to be working better although I
need to run some more tests to be sure.


Regards,

Niclas Gustafsson

 
fre 2004-04-09 klockan 00.58 skrev john stultz:
> On Thu, 2004-04-08 at 02:21, Niclas Gustafsson wrote:
> > Hi,
> > 
> > I'm running Linux 2.6.5  on a IBM xSeries 305 with a Intel P4 2.8Ghz.
> > 
> > And something is very very wrong, I'm getting the following last
> > messages in dmesg:
> > 
> > ------
> > set_rtc_mmss: can't update from 52 to 0
> > set_rtc_mmss: can't update from 53 to 1
> > set_rtc_mmss: can't update from 54 to 2
> > set_rtc_mmss: can't update from 55 to 3
> > set_rtc_mmss: can't update from 56 to 4
> > set_rtc_mmss: can't update from 57 to 5
> > set_rtc_mmss: can't update from 58 to 6
> > Losing too many ticks!
> > TSC cannot be used as a timesource.  <4>Possible reasons for this are:
> >   You're running with Speedstep,
> >   You don't have DMA enabled for your hard disk (see hdparm),
> >   Incorrect TSC synchronization on an SMP system (see dmesg).
> > ------
> > 
> > The problem seesm to be related to heavy loads.
> > I experienced a similar problem yesterday. The machine completly hung
> > after that and i had to cut the power to reboot it. Now however it is
> > responsive and I can log on to it through ssh.
> > 
> > Problem is that the clock stopped completly! - I've never seen anything
> > like this before. 
> > 
> > Local time is about 11 am here and a time gives me:
> > 
> > [root@s151 root]# date
> > Thu Apr  8 03:51:21 CEST 2004
> > 
> > ...10 s later, using my wristwatch, not sleep 10 ;)
> > 
> > [root@s151 root]# date
> > Thu Apr  8 03:51:21 CEST 2004
> > 
> > 
> > Any ideas anyone, I'd really like to know why it is behaving this way.
> 
> Huh. Very very odd.  
> 
> Does /proc/interrupts show timer ticks increasing? 
> Does setting the date change anything? 
> 
> Would you mind sending me your complete dmesg? 
> 
> I'll look into reproducing the error here if you can give me a better
> description of what triggers it and how frequently you see the problem.
> 
> thanks
> -john
> 
> 
> 

[-- Attachment #2: dmesg.265-IBM305_2 --]
[-- Type: text/plain, Size: 15409 bytes --]

 IBM                                       ) @ 0x000fe030
ACPI: RSDT (v001 IBM    M51SL    0x00000001 IBM  0x00000000) @ 0x3ffe0000
ACPI: FADT (v001 IBM    M51SL    0x00000001 IBM  0x00000000) @ 0x3ffe014b
ACPI: ASF! (v016    IBM          0x01000000  0x00000000) @ 0x3ffe0030
ACPI: MADT (v001 IBM    M51SL    0x00000001 IBM  0x00000000) @ 0x3ffe00e3
ACPI: DSDT (v001   IBM    M51SL  0x00001000 MSFT 0x0100000d) @ 0x00000000
ACPI: Local APIC address 0xfee00000
ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
Processor #0 15:2 APIC version 20
ACPI: LAPIC_NMI (acpi_id[0xff] high edge lint[0x1])
ACPI: IOAPIC (id[0x01] address[0xfec00000] global_irq_base[0x0])
IOAPIC[0]: Assigned apic_id 1
IOAPIC[0]: apic_id 1, version 17, address 0xfec00000, GSI 0-15
ACPI: IOAPIC (id[0x02] address[0xfec01000] global_irq_base[0x10])
IOAPIC[1]: Assigned apic_id 2
IOAPIC[1]: apic_id 2, version 17, address 0xfec01000, GSI 16-31
ACPI: IOAPIC (id[0x03] address[0xfec02000] global_irq_base[0x20])
IOAPIC[2]: Assigned apic_id 3
IOAPIC[2]: apic_id 3, version 17, address 0xfec02000, GSI 32-47
ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
Enabling APIC mode:  Flat.  Using 3 I/O APICs
Using ACPI (MADT) for SMP configuration information
Built 1 zonelists
Kernel command line: root=/dev/sda2
Initializing CPU#0
PID hash table entries: 4096 (order 12: 32768 bytes)
Detected 2800.545 MHz processor.
Using tsc for high-res timesource
Console: colour VGA+ 80x25
Memory: 1033864k/1048448k available (1981k kernel code, 13688k reserved, 749k data, 344k init, 130944k highmem)
Checking if this processor honours the WP bit even in supervisor mode... Ok.
Calibrating delay loop... 5505.02 BogoMIPS
Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
Mount-cache hash table entries: 512 (order: 0, 4096 bytes)
CPU:     After generic identify, caps: bfebfbff 00000000 00000000 00000000
CPU:     After vendor identify, caps: bfebfbff 00000000 00000000 00000000
CPU: Trace cache: 12K uops, L1 D cache: 8K
CPU: L2 cache: 512K
CPU:     After all inits, caps: bfebfbff 00000000 00000000 00000080
Intel machine check architecture supported.
Intel machine check reporting enabled on CPU#0.
CPU#0: Intel P4/Xeon Extended MCE MSRs (12) available
CPU: Intel(R) Pentium(R) 4 CPU 2.80GHz stepping 09
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) 1-0, 2-0, 2-1, 2-2, 2-3, 2-4, 2-5, 2-6, 2-7, 2-8, 2-9, 2-10, 2-11, 2-12, 2-13, 2-14, 2-15, 3-0, 3-1, 3-2, 3-3, 3-4, 3-5, 3-6, 3-7, 3-8, 3-9, 3-10, 3-11, 3-12, 3-13, 3-14, 3-15 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... works.
Using local APIC timer interrupts.
calibrating APIC timer ...
..... CPU clock speed is 2798.0746 MHz.
..... host bus clock speed is 133.0273 MHz.
NET: Registered protocol family 16
PCI: PCI BIOS revision 2.10 entry at 0xf0220, last bus=2
PCI: Using configuration type 1
mtrr: v2.0 (20020519)
ACPI: Subsystem revision 20040326
 tbxface-0117 [03] acpi_load_tables      : ACPI Tables successfully acquired
Parsing all Control Methods:............................................................................................................................................................................................
Table [DSDT](id F004) - 618 Objects with 53 Devices 188 Methods 27 Regions
ACPI Namespace successfully loaded at root c041873c
evxfevnt-0093 [04] acpi_enable           : Transition to ACPI mode successful
evgpeblk-0867 [06] ev_create_gpe_block   : GPE 00 to 31 [_GPE] 4 regs at 0000000000000428 on int 9
evgpeblk-0925 [06] ev_create_gpe_block   : Found 0 Wake, Enabled 1 Runtime GPEs in this block
evgpeblk-0867 [06] ev_create_gpe_block   : GPE 32 to 63 [_GPE] 4 regs at 0000000000000528 on int 9
evgpeblk-0925 [06] ev_create_gpe_block   : Found 0 Wake, Enabled 7 Runtime GPEs in this block
Completing Region/Field/Buffer/Package initialization:.....................................................
Initialized 27/27 Regions 0/0 Fields 14/14 Buffers 12/12 Packages (627 nodes)
Executing all Device _STA and_INI methods:.......................................................
55 Devices found containing: 55 _STA, 1 _INI methods
ACPI: Interpreter enabled
ACPI: Using IOAPIC for interrupt routing
ACPI: PCI Interrupt Link [PII0] (IRQs 3 4 5 6 7 9 10 11 12 14 15)
ACPI: PCI Interrupt Link [PII1] (IRQs 3 4 5 6 7 *9 10 11 12 14 15)
ACPI: PCI Interrupt Link [PII2] (IRQs 3 4 5 6 7 9 10 11 12 14 15)
ACPI: PCI Interrupt Link [PII3] (IRQs 3 4 5 6 7 9 10 11 12 14 15)
ACPI: PCI Interrupt Link [PII4] (IRQs 3 4 5 6 7 9 10 *11 12 14 15)
ACPI: PCI Interrupt Link [PII5] (IRQs 3 4 5 6 7 9 10 11 12 14 15)
ACPI: PCI Interrupt Link [PII6] (IRQs 3 4 5 6 *7 9 10 11 12 14 15)
ACPI: PCI Interrupt Link [PII7] (IRQs 3 4 *5 6 7 9 10 11 12 14 15)
ACPI: PCI Interrupt Link [PII8] (IRQs 3 4 5 6 7 9 10 11 12 14 15)
ACPI: PCI Interrupt Link [PII9] (IRQs 3 4 5 6 7 9 10 11 12 14 15)
ACPI: PCI Interrupt Link [PIIA] (IRQs 3 4 5 6 7 9 10 11 12 14 15)
ACPI: PCI Interrupt Link [PIIB] (IRQs 3 4 5 6 7 9 10 11 12 14 15)
ACPI: PCI Interrupt Link [PIIC] (IRQs 3 4 5 6 7 9 10 11 12 14 15)
ACPI: PCI Interrupt Link [PIID] (IRQs 3 4 5 6 7 9 10 11 12 14 15)
ACPI: PCI Interrupt Link [PIIE] (IRQs 3 4 5 6 7 9 10 11 12 14 15)
ACPI: PCI Interrupt Link [PIIF] (IRQs 3 4 5 6 7 9 10 11 12 14 15)
ACPI: PCI Interrupt Link [PI10] (IRQs 3 4 5 6 7 9 10 11 12 14 15)
ACPI: PCI Interrupt Link [PI11] (IRQs 3 4 5 6 7 9 10 11 12 14 15)
ACPI: PCI Interrupt Link [PI12] (IRQs 3 4 5 6 7 9 10 11 12 14 15)
ACPI: PCI Interrupt Link [PI13] (IRQs 3 4 5 6 7 9 10 11 12 14 15)
ACPI: PCI Interrupt Link [PI14] (IRQs 3 4 5 6 7 9 10 11 12 14 15)
ACPI: PCI Interrupt Link [PI15] (IRQs 3 4 5 6 7 9 10 11 12 14 15)
ACPI: PCI Interrupt Link [PIIU] (IRQs 3 4 5 6 7 9 *10 11 12 14 15)
ACPI: PCI Root Bridge [PCI0] (00:00)
PCI: Probing PCI hardware (bus 00)
PCI: Ignoring BAR0-3 of IDE controller 0000:00:0f.1
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
ACPI: PCI Root Bridge [PCI1] (00:01)
PCI: Probing PCI hardware (bus 01)
ACPI: PCI Interrupt Routing Table [\_SB_.PCI1._PRT]
ACPI: PCI Root Bridge [PCI2] (00:02)
PCI: Probing PCI hardware (bus 02)
ACPI: PCI Interrupt Routing Table [\_SB_.PCI2._PRT]
SCSI subsystem initialized
/usr/src/linux-2.6.5/drivers/usb/core/usb.c: registered new driver usbfs
/usr/src/linux-2.6.5/drivers/usb/core/usb.c: registered new driver hub
IOAPIC[1]: Set PCI routing entry (2-1 -> 0xa9 -> IRQ 17 Mode:1 Active:1)
00:00:03[A] -> 2-1 -> IRQ 17
ACPI: PCI Interrupt Link [PIIU] enabled at IRQ 10
IOAPIC[0]: Set PCI routing entry (1-10 -> 0x79 -> IRQ 10 Mode:1 Active:1)
00:00:0f[A] -> 1-10 -> IRQ 10
IOAPIC[1]: Set PCI routing entry (2-0 -> 0xb1 -> IRQ 16 Mode:1 Active:1)
00:00:02[A] -> 2-0 -> IRQ 16
IOAPIC[1]: Set PCI routing entry (2-2 -> 0xb9 -> IRQ 18 Mode:1 Active:1)
00:01:02[A] -> 2-2 -> IRQ 18
IOAPIC[1]: Set PCI routing entry (2-3 -> 0xc1 -> IRQ 19 Mode:1 Active:1)
00:01:02[B] -> 2-3 -> IRQ 19
IOAPIC[1]: Set PCI routing entry (2-4 -> 0xc9 -> IRQ 20 Mode:1 Active:1)
00:01:03[A] -> 2-4 -> IRQ 20
IOAPIC[1]: Set PCI routing entry (2-5 -> 0xd1 -> IRQ 21 Mode:1 Active:1)
00:01:03[B] -> 2-5 -> IRQ 21
IOAPIC[1]: Set PCI routing entry (2-6 -> 0xd9 -> IRQ 22 Mode:1 Active:1)
00:02:04[A] -> 2-6 -> IRQ 22
IOAPIC[1]: Set PCI routing entry (2-7 -> 0xe1 -> IRQ 23 Mode:1 Active:1)
00:02:05[A] -> 2-7 -> IRQ 23
number of MP IRQ sources: 15.
number of IO-APIC #1 registers: 16.
number of IO-APIC #2 registers: 16.
number of IO-APIC #3 registers: 16.
testing the IO APIC.......................
IO APIC #1......
.... register #00: 01000000
.......    : physical APIC id: 01
.......    : Delivery Type: 0
.......    : LTS          : 0
.... register #01: 000F0011
.......     : max redirection entries: 000F
.......     : PRQ implemented: 0
.......     : IO APIC version: 0011
.... register #02: 01000000
.......     : arbitration: 01
.... 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  0    0    0   0   0    1    1    61
 08 001 01  0    0    0   0   0    1    1    69
 09 001 01  0    1    0   1   0    1    1    71
 0a 001 01  1    1    0   1   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
IO APIC #2......
.... register #00: 02000000
.......    : physical APIC id: 02
.......    : Delivery Type: 0
.......    : LTS          : 0
.... register #01: 000F0011
.......     : max redirection entries: 000F
.......     : PRQ implemented: 0
.......     : IO APIC version: 0011
.... register #02: 02000000
.......     : arbitration: 02
.... IRQ redirection table:
 NR Log Phy Mask Trig IRR Pol Stat Dest Deli Vect:   
 00 001 01  1    1    0   1   0    1    1    B1
 01 001 01  1    1    0   1   0    1    1    A9
 02 001 01  1    1    0   1   0    1    1    B9
 03 001 01  1    1    0   1   0    1    1    C1
 04 001 01  1    1    0   1   0    1    1    C9
 05 001 01  1    1    0   1   0    1    1    D1
 06 001 01  1    1    0   1   0    1    1    D9
 07 001 01  1    1    0   1   0    1    1    E1
 08 023 03  1    0    0   0   0    0    2    00
 09 00C 0C  1    0    0   0   0    0    2    08
 0a 000 00  1    0    0   0   0    0    0    00
 0b 000 00  1    0    0   0   0    0    0    00
 0c 000 00  1    0    0   0   0    0    0    00
 0d 000 00  1    0    0   0   0    0    0    00
 0e 000 00  1    0    0   0   0    0    0    00
 0f 000 00  1    0    0   0   0    0    0    00
IO APIC #3......
.... register #00: 03000000
.......    : physical APIC id: 03
.......    : Delivery Type: 0
.......    : LTS          : 0
.... register #01: 000F0011
.......     : max redirection entries: 000F
.......     : PRQ implemented: 0
.......     : IO APIC version: 0011
.... register #02: 03000000
.......     : arbitration: 03
.... IRQ redirection table:
 NR Log Phy Mask Trig IRR Pol Stat Dest Deli Vect:   
 00 000 00  1    0    0   0   0    0    0    00
 01 000 00  1    0    0   0   0    0    0    00
 02 000 00  1    0    0   0   0    0    0    00
 03 000 00  1    0    0   0   0    0    0    00
 04 000 00  1    0    0   0   0    0    0    00
 05 000 00  1    0    0   0   0    0    0    00
 06 000 00  1    0    0   0   0    0    0    00
 07 060 00  1    0    0   0   0    0    2    44
 08 000 00  1    0    0   0   0    0    0    00
 09 000 00  1    0    0   0   0    0    0    00
 0a 000 00  1    0    0   0   0    0    0    00
 0b 000 00  1    0    0   0   0    0    0    00
 0c 000 00  1    0    0   0   0    0    0    00
 0d 000 00  1    0    0   0   0    0    0    00
 0e 000 00  1    0    0   0   0    0    0    00
 0f 000 00  1    0    0   0   0    0    0    00
IRQ to pin mappings:
IRQ0 -> 0: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
IRQ16 -> 1:0
IRQ17 -> 1:1
IRQ18 -> 1:2
IRQ19 -> 1:3
IRQ20 -> 1:4
IRQ21 -> 1:5
IRQ22 -> 1:6
IRQ23 -> 1:7
.................................... done.
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.
ikconfig 0.7 with /proc/config*
highmem bounce pool size: 64 pages
Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
Initializing Cryptographic API
lp: driver loaded but no devices found
Serial: 8250/16550 driver $Revision: 1.90 $ 8 ports, IRQ sharing disabled
ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
Using anticipatory io scheduler
Floppy drive(s): fd0 is 1.44M
FDC 0 is a National Semiconductor PC87306
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
hdb: CD-224E, ATAPI CD/DVD-ROM drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
hdb: ATAPI 24X CD-ROM drive, 128kB Cache
Uniform CD-ROM driver Revision: 3.20
scsi0 : Adaptec AIC7XXX EISA/VLB/PCI SCSI HBA DRIVER, Rev 6.2.36
        <Adaptec 29160B Ultra160 SCSI adapter>
        aic7892: Ultra160 Wide Channel A, SCSI Id=7, 32/253 SCBs

(scsi0:A:0): 160.000MB/s transfers (80.000MHz DT, offset 127, 16bit)
  Vendor: IBM-ESXS  Model: DTN018W3UWDY10FN  Rev: S23J
  Type:   Direct-Access                      ANSI SCSI revision: 03
scsi0:A:0:0: Tagged Queuing enabled.  Depth 32
SCSI device sda: 35548320 512-byte hdwr sectors (18201 MB)
SCSI device sda: drive cache: write through
 sda: sda1 sda2 sda3
Attached scsi disk sda at scsi0, channel 0, id 0, lun 0
Fusion MPT base driver 3.01.01
Copyright (c) 1999-2004 LSI Logic Corporation
Fusion MPT SCSI Host driver 3.01.01
ohci_hcd: 2004 Feb 02 USB 1.1 'Open' Host Controller (OHCI) Driver (PCI)
ohci_hcd: block sizes: ed 64 td 64
ohci_hcd 0000:00:0f.2: ServerWorks OSB4/CSB5 OHCI USB Controller
ohci_hcd 0000:00:0f.2: irq 10, pci mem f880b000
ohci_hcd 0000:00:0f.2: new USB bus registered, assigned bus number 1
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 2 ports detected
/usr/src/linux-2.6.5/drivers/usb/core/usb.c: registered new driver hid
/usr/src/linux-2.6.5/drivers/usb/input/hid-core.c: v2.0:USB HID core driver
mice: PS/2 mouse device common for all mice
serio: i8042 AUX port at 0x60,0x64 irq 12
serio: i8042 KBD port at 0x60,0x64 irq 1
NET: Registered protocol family 2
IP: routing cache hash table of 8192 buckets, 64Kbytes
TCP: Hash tables configured (established 262144 bind 65536)
NET: Registered protocol family 1
NET: Registered protocol family 17
EXT3-fs: INFO: recovery required on readonly filesystem.
EXT3-fs: write access will be enabled during recovery.
kjournald starting.  Commit interval 5 seconds
EXT3-fs: sda2: orphan cleanup on readonly fs
ext3_orphan_cleanup: deleting unreferenced inode 213361
ext3_orphan_cleanup: deleting unreferenced inode 213364
EXT3-fs: sda2: 2 orphan inodes deleted
EXT3-fs: recovery complete.
EXT3-fs: mounted filesystem with ordered data mode.
VFS: Mounted root (ext3 filesystem) readonly.
Freeing unused kernel memory: 344k freed
EXT3 FS on sda2, internal journal
Adding 522104k swap on /dev/sda3.  Priority:-1 extents:1
kjournald starting.  Commit interval 5 seconds
EXT3 FS on sda1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
tg3.c:v2.9 (March 8, 2004)
eth0: Tigon3 [partno(BCM95703A30) rev 1002 PHY(5703)] (PCIX:100MHz:64-bit) 10/100/1000BaseT Ethernet 00:0d:60:0f:5f:7a
eth1: Tigon3 [partno(BCM95703A30) rev 1002 PHY(5703)] (PCIX:100MHz:64-bit) 10/100/1000BaseT Ethernet 00:0d:60:0f:5f:7b
tg3: eth0: Link is up at 100 Mbps, full duplex.
tg3: eth0: Flow control is on for TX and on for RX.

[-- Attachment #3: config.gz.IBM-265_2 --]
[-- Type: application/x-gzip, Size: 5221 bytes --]

Re: Failing back to INSANE timesource :) Time stopped today.

[Niclas Gustafsson]

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

Hi again, 

Now it happened again, with my newly compiled kernel, I've attached the
config file and dmesg for this kernel.

Watching the /proc/interrupts with 10s apart after the "stop".

[root@s151 root]# more /proc/interrupts
           CPU0
  0:   66413955  local-APIC-edge  timer
  2:          0          XT-PIC  cascade
  9:          1   IO-APIC-level  acpi
 10:          0   IO-APIC-level  ohci_hcd
 14:         24    IO-APIC-edge  ide0
 20:      31244   IO-APIC-level  aic7xxx
 22:   19641795   IO-APIC-level  eth0
NMI:          0
LOC:   67355837
ERR:          0
MIS:          0
[root@s151 root]# more /proc/interrupts
           CPU0
  0:   66413955  local-APIC-edge  timer
  2:          0          XT-PIC  cascade
  9:          1   IO-APIC-level  acpi
 10:          0   IO-APIC-level  ohci_hcd
 14:         24    IO-APIC-edge  ide0
 20:      31244   IO-APIC-level  aic7xxx
 22:   19652139   IO-APIC-level  eth0
NMI:          0
LOC:   67379568
ERR:          0
MIS:          0

And some 10-15 min later:

[root@s151 root]# cat /proc/interrupts
           CPU0
  0:   66413964  local-APIC-edge  timer
  2:          0          XT-PIC  cascade
  9:          1   IO-APIC-level  acpi
 10:          0   IO-APIC-level  ohci_hcd
 14:         24    IO-APIC-edge  ide0
 20:      31245   IO-APIC-level  aic7xxx
 22:   19754446   IO-APIC-level  eth0
NMI:          0
LOC:   68366976
ERR:          0
MIS:          0



Last vmstat (and /proc/loadavg intermixed):

(Rows like 3.48 1.70 2.12 2/114 13232 are loadavg, the other are
linewrapped vmstats.)
 
   procs                      memory      swap          io    
system      cpu
 r  b  w   swpd   free   buff  cache   si   so    bi    bo   in    cs us
sy id
 1  0  0      0 686752  48412  59104    0    0     0     0 2112   898
19  1 80
3.48 1.70 2.12 2/114 13232
 0  0  0      0 686832  48412  59104    0    0     0     0 2093   688
12  1 87
 0  0  0      0 686768  48416  59104    0    0     0   140 1623   998
15  1 84
3.20 1.67 2.11 2/114 13235
 0  0  0      0 686848  48416  59104    0    0     0     0 2128   960
16  1 83
3.20 1.67 2.11 2/114 13238
 0  0  0      0 686912  48416  59104    0    0     0     0 1597   809
11  1 88
 0  0  0      0 686880  48420  59104    0    0     0    22 2164   959
13  1 86
2.94 1.64 2.09 2/114 13241
 0  0  0      0 686816  48420  59104    0    0     0     0 2089   748
14  1 85
2.94 1.64 2.09 2/114 13244
 0  0  0      0 686640  48420  59104    0    0     0     0 2465  1170 20
21 59
   procs                      memory      swap          io    
system      cpu
 r  b  w   swpd   free   buff  cache   si   so    bi    bo   in    cs us
sy id
 1  0  0      0 649904  48420  59104    0    0     0    24 87091 90759
29 66  5
2.87 1.65 2.09 3/114 13247


Worth noticing is the extreme increase in interrupts and context
switches on the last output line from vmstat, however if this is a true
picture of what happened or not I cannot say. Maybe this is just a
result of timing problems?

However I see an increase in network activity just before the stop, the
system goes from 2 Mbps output to about 55 Mbps on the last read. (Also
read from this machine so I don't know about it's validity)


cpuinfo, if useful is:
   
[root@s151 root]# cat /proc/cpuinfo
processor       : 0
vendor_id       : GenuineIntel
cpu family      : 15
model           : 2
model name      : Intel(R) Pentium(R) 4 CPU 2.80GHz
stepping        : 9
cpu MHz         : 2800.731
cache size      : 512 KB
fdiv_bug        : no
hlt_bug         : no
f00f_bug        : no
coma_bug        : no
fpu             : yes
fpu_exception   : yes
cpuid level     : 2
wp              : yes
flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge
mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe cid
bogomips        : 5505.02
 


Where can I see what the system is currently using as a timing source
(TSC/HPET/PIT etc.)?



Cheers,

Niclas


fre 2004-04-09 klockan 00.58 skrev john stultz:
> On Thu, 2004-04-08 at 02:21, Niclas Gustafsson wrote:
> > Hi,
> > 
> > I'm running Linux 2.6.5  on a IBM xSeries 305 with a Intel P4 2.8Ghz.
> > 
> > And something is very very wrong, I'm getting the following last
> > messages in dmesg:
> > 
> > ------
> > set_rtc_mmss: can't update from 52 to 0
> > set_rtc_mmss: can't update from 53 to 1
> > set_rtc_mmss: can't update from 54 to 2
> > set_rtc_mmss: can't update from 55 to 3
> > set_rtc_mmss: can't update from 56 to 4
> > set_rtc_mmss: can't update from 57 to 5
> > set_rtc_mmss: can't update from 58 to 6
> > Losing too many ticks!
> > TSC cannot be used as a timesource.  <4>Possible reasons for this are:
> >   You're running with Speedstep,
> >   You don't have DMA enabled for your hard disk (see hdparm),
> >   Incorrect TSC synchronization on an SMP system (see dmesg).
> > ------
> > 
> > The problem seesm to be related to heavy loads.
> > I experienced a similar problem yesterday. The machine completly hung
> > after that and i had to cut the power to reboot it. Now however it is
> > responsive and I can log on to it through ssh.
> > 
> > Problem is that the clock stopped completly! - I've never seen anything
> > like this before. 
> > 
> > Local time is about 11 am here and a time gives me:
> > 
> > [root@s151 root]# date
> > Thu Apr  8 03:51:21 CEST 2004
> > 
> > ...10 s later, using my wristwatch, not sleep 10 ;)
> > 
> > [root@s151 root]# date
> > Thu Apr  8 03:51:21 CEST 2004
> > 
> > 
> > Any ideas anyone, I'd really like to know why it is behaving this way.
> 
> Huh. Very very odd.  
> 
> Does /proc/interrupts show timer ticks increasing? 
> Does setting the date change anything? 
> 
> Would you mind sending me your complete dmesg? 
> 
> I'll look into reproducing the error here if you can give me a better
> description of what triggers it and how frequently you see the problem.
> 
> thanks
> -john
> 
> 
> 

[-- Attachment #2: dmesg.265-IBM305_3 --]
[-- Type: text/plain, Size: 15403 bytes --]

230
On node 0 totalpages: 262112
  DMA zone: 4096 pages, LIFO batch:1
  Normal zone: 225280 pages, LIFO batch:16
  HighMem zone: 32736 pages, LIFO batch:7
DMI 2.3 present.
IBM machine detected. Enabling interrupts during APM calls.
IBM machine detected. Disabling SMBus accesses.
ACPI: RSDP (v000 IBM                                       ) @ 0x000fe030
ACPI: RSDT (v001 IBM    M51SL    0x00000001 IBM  0x00000000) @ 0x3ffe0000
ACPI: FADT (v001 IBM    M51SL    0x00000001 IBM  0x00000000) @ 0x3ffe014b
ACPI: ASF! (v016    IBM          0x01000000  0x00000000) @ 0x3ffe0030
ACPI: MADT (v001 IBM    M51SL    0x00000001 IBM  0x00000000) @ 0x3ffe00e3
ACPI: DSDT (v001   IBM    M51SL  0x00001000 MSFT 0x0100000d) @ 0x00000000
ACPI: Local APIC address 0xfee00000
ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
Processor #0 15:2 APIC version 20
ACPI: LAPIC_NMI (acpi_id[0xff] high edge lint[0x1])
ACPI: IOAPIC (id[0x01] address[0xfec00000] global_irq_base[0x0])
IOAPIC[0]: Assigned apic_id 1
IOAPIC[0]: apic_id 1, version 17, address 0xfec00000, GSI 0-15
ACPI: IOAPIC (id[0x02] address[0xfec01000] global_irq_base[0x10])
IOAPIC[1]: Assigned apic_id 2
IOAPIC[1]: apic_id 2, version 17, address 0xfec01000, GSI 16-31
ACPI: IOAPIC (id[0x03] address[0xfec02000] global_irq_base[0x20])
IOAPIC[2]: Assigned apic_id 3
IOAPIC[2]: apic_id 3, version 17, address 0xfec02000, GSI 32-47
ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
Enabling APIC mode:  Flat.  Using 3 I/O APICs
Using ACPI (MADT) for SMP configuration information
Built 1 zonelists
Kernel command line: root=/dev/sda2
Initializing CPU#0
PID hash table entries: 4096 (order 12: 32768 bytes)
Detected 2800.832 MHz processor.
Using tsc for high-res timesource
Console: colour VGA+ 80x25
Memory: 1033872k/1048448k available (1976k kernel code, 13680k reserved, 746k data, 344k init, 130944k highmem)
Checking if this processor honours the WP bit even in supervisor mode... Ok.
Calibrating delay loop... 5505.02 BogoMIPS
Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
Mount-cache hash table entries: 512 (order: 0, 4096 bytes)
CPU:     After generic identify, caps: bfebfbff 00000000 00000000 00000000
CPU:     After vendor identify, caps: bfebfbff 00000000 00000000 00000000
CPU: Trace cache: 12K uops, L1 D cache: 8K
CPU: L2 cache: 512K
CPU:     After all inits, caps: bfebfbff 00000000 00000000 00000080
Intel machine check architecture supported.
Intel machine check reporting enabled on CPU#0.
CPU#0: Intel P4/Xeon Extended MCE MSRs (12) available
CPU#0: Thermal monitoring enabled
CPU: Intel(R) Pentium(R) 4 CPU 2.80GHz stepping 09
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) 1-0, 2-0, 2-1, 2-2, 2-3, 2-4, 2-5, 2-6, 2-7, 2-8, 2-9, 2-10, 2-11, 2-12, 2-13, 2-14, 2-15, 3-0, 3-1, 3-2, 3-3, 3-4, 3-5, 3-6, 3-7, 3-8, 3-9, 3-10, 3-11, 3-12, 3-13, 3-14, 3-15 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... works.
Using local APIC timer interrupts.
calibrating APIC timer ...
..... CPU clock speed is 2798.0748 MHz.
..... host bus clock speed is 133.0273 MHz.
NET: Registered protocol family 16
PCI: PCI BIOS revision 2.10 entry at 0xf0220, last bus=2
PCI: Using configuration type 1
mtrr: v2.0 (20020519)
ACPI: Subsystem revision 20040326
 tbxface-0117 [03] acpi_load_tables      : ACPI Tables successfully acquired
Parsing all Control Methods:............................................................................................................................................................................................
Table [DSDT](id F004) - 618 Objects with 53 Devices 188 Methods 27 Regions
ACPI Namespace successfully loaded at root c041673c
evxfevnt-0093 [04] acpi_enable           : Transition to ACPI mode successful
evgpeblk-0867 [06] ev_create_gpe_block   : GPE 00 to 31 [_GPE] 4 regs at 0000000000000428 on int 9
evgpeblk-0925 [06] ev_create_gpe_block   : Found 0 Wake, Enabled 1 Runtime GPEs in this block
evgpeblk-0867 [06] ev_create_gpe_block   : GPE 32 to 63 [_GPE] 4 regs at 0000000000000528 on int 9
evgpeblk-0925 [06] ev_create_gpe_block   : Found 0 Wake, Enabled 7 Runtime GPEs in this block
Completing Region/Field/Buffer/Package initialization:.....................................................
Initialized 27/27 Regions 0/0 Fields 14/14 Buffers 12/12 Packages (627 nodes)
Executing all Device _STA and_INI methods:.......................................................
55 Devices found containing: 55 _STA, 1 _INI methods
ACPI: Interpreter enabled
ACPI: Using IOAPIC for interrupt routing
ACPI: PCI Interrupt Link [PII0] (IRQs 3 4 5 6 7 9 10 11 12 14 15)
ACPI: PCI Interrupt Link [PII1] (IRQs 3 4 5 6 7 *9 10 11 12 14 15)
ACPI: PCI Interrupt Link [PII2] (IRQs 3 4 5 6 7 9 10 11 12 14 15)
ACPI: PCI Interrupt Link [PII3] (IRQs 3 4 5 6 7 9 10 11 12 14 15)
ACPI: PCI Interrupt Link [PII4] (IRQs 3 4 5 6 7 9 10 *11 12 14 15)
ACPI: PCI Interrupt Link [PII5] (IRQs 3 4 5 6 7 9 10 11 12 14 15)
ACPI: PCI Interrupt Link [PII6] (IRQs 3 4 5 6 *7 9 10 11 12 14 15)
ACPI: PCI Interrupt Link [PII7] (IRQs 3 4 *5 6 7 9 10 11 12 14 15)
ACPI: PCI Interrupt Link [PII8] (IRQs 3 4 5 6 7 9 10 11 12 14 15)
ACPI: PCI Interrupt Link [PII9] (IRQs 3 4 5 6 7 9 10 11 12 14 15)
ACPI: PCI Interrupt Link [PIIA] (IRQs 3 4 5 6 7 9 10 11 12 14 15)
ACPI: PCI Interrupt Link [PIIB] (IRQs 3 4 5 6 7 9 10 11 12 14 15)
ACPI: PCI Interrupt Link [PIIC] (IRQs 3 4 5 6 7 9 10 11 12 14 15)
ACPI: PCI Interrupt Link [PIID] (IRQs 3 4 5 6 7 9 10 11 12 14 15)
ACPI: PCI Interrupt Link [PIIE] (IRQs 3 4 5 6 7 9 10 11 12 14 15)
ACPI: PCI Interrupt Link [PIIF] (IRQs 3 4 5 6 7 9 10 11 12 14 15)
ACPI: PCI Interrupt Link [PI10] (IRQs 3 4 5 6 7 9 10 11 12 14 15)
ACPI: PCI Interrupt Link [PI11] (IRQs 3 4 5 6 7 9 10 11 12 14 15)
ACPI: PCI Interrupt Link [PI12] (IRQs 3 4 5 6 7 9 10 11 12 14 15)
ACPI: PCI Interrupt Link [PI13] (IRQs 3 4 5 6 7 9 10 11 12 14 15)
ACPI: PCI Interrupt Link [PI14] (IRQs 3 4 5 6 7 9 10 11 12 14 15)
ACPI: PCI Interrupt Link [PI15] (IRQs 3 4 5 6 7 9 10 11 12 14 15)
ACPI: PCI Interrupt Link [PIIU] (IRQs 3 4 5 6 7 9 *10 11 12 14 15)
ACPI: PCI Root Bridge [PCI0] (00:00)
PCI: Probing PCI hardware (bus 00)
PCI: Ignoring BAR0-3 of IDE controller 0000:00:0f.1
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
ACPI: PCI Root Bridge [PCI1] (00:01)
PCI: Probing PCI hardware (bus 01)
ACPI: PCI Interrupt Routing Table [\_SB_.PCI1._PRT]
ACPI: PCI Root Bridge [PCI2] (00:02)
PCI: Probing PCI hardware (bus 02)
ACPI: PCI Interrupt Routing Table [\_SB_.PCI2._PRT]
SCSI subsystem initialized
/usr/src/linux-2.6.5/drivers/usb/core/usb.c: registered new driver usbfs
/usr/src/linux-2.6.5/drivers/usb/core/usb.c: registered new driver hub
IOAPIC[1]: Set PCI routing entry (2-1 -> 0xa9 -> IRQ 17 Mode:1 Active:1)
00:00:03[A] -> 2-1 -> IRQ 17
ACPI: PCI Interrupt Link [PIIU] enabled at IRQ 10
IOAPIC[0]: Set PCI routing entry (1-10 -> 0x79 -> IRQ 10 Mode:1 Active:1)
00:00:0f[A] -> 1-10 -> IRQ 10
IOAPIC[1]: Set PCI routing entry (2-0 -> 0xb1 -> IRQ 16 Mode:1 Active:1)
00:00:02[A] -> 2-0 -> IRQ 16
IOAPIC[1]: Set PCI routing entry (2-2 -> 0xb9 -> IRQ 18 Mode:1 Active:1)
00:01:02[A] -> 2-2 -> IRQ 18
IOAPIC[1]: Set PCI routing entry (2-3 -> 0xc1 -> IRQ 19 Mode:1 Active:1)
00:01:02[B] -> 2-3 -> IRQ 19
IOAPIC[1]: Set PCI routing entry (2-4 -> 0xc9 -> IRQ 20 Mode:1 Active:1)
00:01:03[A] -> 2-4 -> IRQ 20
IOAPIC[1]: Set PCI routing entry (2-5 -> 0xd1 -> IRQ 21 Mode:1 Active:1)
00:01:03[B] -> 2-5 -> IRQ 21
IOAPIC[1]: Set PCI routing entry (2-6 -> 0xd9 -> IRQ 22 Mode:1 Active:1)
00:02:04[A] -> 2-6 -> IRQ 22
IOAPIC[1]: Set PCI routing entry (2-7 -> 0xe1 -> IRQ 23 Mode:1 Active:1)
00:02:05[A] -> 2-7 -> IRQ 23
number of MP IRQ sources: 15.
number of IO-APIC #1 registers: 16.
number of IO-APIC #2 registers: 16.
number of IO-APIC #3 registers: 16.
testing the IO APIC.......................
IO APIC #1......
.... register #00: 01000000
.......    : physical APIC id: 01
.......    : Delivery Type: 0
.......    : LTS          : 0
.... register #01: 000F0011
.......     : max redirection entries: 000F
.......     : PRQ implemented: 0
.......     : IO APIC version: 0011
.... register #02: 01000000
.......     : arbitration: 01
.... 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  0    0    0   0   0    1    1    61
 08 001 01  0    0    0   0   0    1    1    69
 09 001 01  0    1    0   1   0    1    1    71
 0a 001 01  1    1    0   1   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
IO APIC #2......
.... register #00: 02000000
.......    : physical APIC id: 02
.......    : Delivery Type: 0
.......    : LTS          : 0
.... register #01: 000F0011
.......     : max redirection entries: 000F
.......     : PRQ implemented: 0
.......     : IO APIC version: 0011
.... register #02: 02000000
.......     : arbitration: 02
.... IRQ redirection table:
 NR Log Phy Mask Trig IRR Pol Stat Dest Deli Vect:   
 00 001 01  1    1    0   1   0    1    1    B1
 01 001 01  1    1    0   1   0    1    1    A9
 02 001 01  1    1    0   1   0    1    1    B9
 03 001 01  1    1    0   1   0    1    1    C1
 04 001 01  1    1    0   1   0    1    1    C9
 05 001 01  1    1    0   1   0    1    1    D1
 06 001 01  1    1    0   1   0    1    1    D9
 07 001 01  1    1    0   1   0    1    1    E1
 08 023 03  1    0    0   0   0    0    2    00
 09 00C 0C  1    0    0   0   0    0    2    08
 0a 000 00  1    0    0   0   0    0    0    00
 0b 000 00  1    0    0   0   0    0    0    00
 0c 000 00  1    0    0   0   0    0    0    00
 0d 000 00  1    0    0   0   0    0    0    00
 0e 000 00  1    0    0   0   0    0    0    00
 0f 000 00  1    0    0   0   0    0    0    00
IO APIC #3......
.... register #00: 03000000
.......    : physical APIC id: 03
.......    : Delivery Type: 0
.......    : LTS          : 0
.... register #01: 000F0011
.......     : max redirection entries: 000F
.......     : PRQ implemented: 0
.......     : IO APIC version: 0011
.... register #02: 03000000
.......     : arbitration: 03
.... IRQ redirection table:
 NR Log Phy Mask Trig IRR Pol Stat Dest Deli Vect:   
 00 000 00  1    0    0   0   0    0    0    00
 01 000 00  1    0    0   0   0    0    0    00
 02 000 00  1    0    0   0   0    0    0    00
 03 000 00  1    0    0   0   0    0    0    00
 04 000 00  1    0    0   0   0    0    0    00
 05 000 00  1    0    0   0   0    0    0    00
 06 000 00  1    0    0   0   0    0    0    00
 07 060 00  1    0    0   0   0    0    2    44
 08 000 00  1    0    0   0   0    0    0    00
 09 000 00  1    0    0   0   0    0    0    00
 0a 000 00  1    0    0   0   0    0    0    00
 0b 000 00  1    0    0   0   0    0    0    00
 0c 000 00  1    0    0   0   0    0    0    00
 0d 000 00  1    0    0   0   0    0    0    00
 0e 000 00  1    0    0   0   0    0    0    00
 0f 000 00  1    0    0   0   0    0    0    00
IRQ to pin mappings:
IRQ0 -> 0: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
IRQ16 -> 1:0
IRQ17 -> 1:1
IRQ18 -> 1:2
IRQ19 -> 1:3
IRQ20 -> 1:4
IRQ21 -> 1:5
IRQ22 -> 1:6
IRQ23 -> 1:7
.................................... done.
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.
ikconfig 0.7 with /proc/config*
highmem bounce pool size: 64 pages
Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
Initializing Cryptographic API
lp: driver loaded but no devices found
Serial: 8250/16550 driver $Revision: 1.90 $ 8 ports, IRQ sharing disabled
ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
Using anticipatory io scheduler
Floppy drive(s): fd0 is 1.44M
FDC 0 is a National Semiconductor PC87306
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
hdb: CD-224E, ATAPI CD/DVD-ROM drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
hdb: ATAPI 24X CD-ROM drive, 128kB Cache
Uniform CD-ROM driver Revision: 3.20
scsi0 : Adaptec AIC7XXX EISA/VLB/PCI SCSI HBA DRIVER, Rev 6.2.36
        <Adaptec 29160B Ultra160 SCSI adapter>
        aic7892: Ultra160 Wide Channel A, SCSI Id=7, 32/253 SCBs

(scsi0:A:0): 160.000MB/s transfers (80.000MHz DT, offset 127, 16bit)
  Vendor: IBM-ESXS  Model: DTN018W3UWDY10FN  Rev: S23J
  Type:   Direct-Access                      ANSI SCSI revision: 03
scsi0:A:0:0: Tagged Queuing enabled.  Depth 32
SCSI device sda: 35548320 512-byte hdwr sectors (18201 MB)
SCSI device sda: drive cache: write through
 sda: sda1 sda2 sda3
Attached scsi disk sda at scsi0, channel 0, id 0, lun 0
Fusion MPT base driver 3.01.01
Copyright (c) 1999-2004 LSI Logic Corporation
Fusion MPT SCSI Host driver 3.01.01
ohci_hcd: 2004 Feb 02 USB 1.1 'Open' Host Controller (OHCI) Driver (PCI)
ohci_hcd: block sizes: ed 64 td 64
ohci_hcd 0000:00:0f.2: ServerWorks OSB4/CSB5 OHCI USB Controller
ohci_hcd 0000:00:0f.2: irq 10, pci mem f880b000
ohci_hcd 0000:00:0f.2: new USB bus registered, assigned bus number 1
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 2 ports detected
/usr/src/linux-2.6.5/drivers/usb/core/usb.c: registered new driver hid
/usr/src/linux-2.6.5/drivers/usb/input/hid-core.c: v2.0:USB HID core driver
mice: PS/2 mouse device common for all mice
serio: i8042 AUX port at 0x60,0x64 irq 12
serio: i8042 KBD port at 0x60,0x64 irq 1
NET: Registered protocol family 2
IP: routing cache hash table of 8192 buckets, 64Kbytes
TCP: Hash tables configured (established 262144 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.
Freeing unused kernel memory: 344k freed
EXT3 FS on sda2, internal journal
Adding 522104k swap on /dev/sda3.  Priority:-1 extents:1
kjournald starting.  Commit interval 5 seconds
EXT3 FS on sda1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
tg3.c:v2.9 (March 8, 2004)
eth0: Tigon3 [partno(BCM95703A30) rev 1002 PHY(5703)] (PCIX:100MHz:64-bit) 10/100/1000BaseT Ethernet 00:0d:60:0f:5f:7a
eth1: Tigon3 [partno(BCM95703A30) rev 1002 PHY(5703)] (PCIX:100MHz:64-bit) 10/100/1000BaseT Ethernet 00:0d:60:0f:5f:7b
tg3: eth0: Link is up at 100 Mbps, full duplex.
tg3: eth0: Flow control is on for TX and on for RX.

[-- Attachment #3: config.IBM-265_3 --]
[-- Type: text/plain, Size: 18642 bytes --]

#
# 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 is not set
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_HOTPLUG is not set
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_CC_OPTIMIZE_FOR_SIZE is not set

#
# Loadable module support
#
CONFIG_MODULES=y
CONFIG_MODULE_UNLOAD=y
CONFIG_OBSOLETE_MODPARM=y
CONFIG_KMOD=y

#
# Processor type and features
#
CONFIG_X86_PC=y
# CONFIG_X86_ELAN is not set
# 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_MPENTIUMM is not set
CONFIG_MPENTIUM4=y
# CONFIG_MK6 is not set
# CONFIG_MK7 is not set
# CONFIG_MK8 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=7
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_HPET_TIMER=y
# 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

#
# Firmware Drivers
#
# 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
# CONFIG_EFI is not set

#
# Power management options (ACPI, APM)
#
# CONFIG_PM is not set

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

#
# 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_GOMMCONFIG is not set
# CONFIG_PCI_GODIRECT is not set
CONFIG_PCI_GOANY=y
CONFIG_PCI_BIOS=y
CONFIG_PCI_DIRECT=y
CONFIG_PCI_MMCONFIG=y
# CONFIG_PCI_USE_VECTOR is not set
CONFIG_PCI_LEGACY_PROC=y
CONFIG_PCI_NAMES=y
# CONFIG_ISA is not set
# CONFIG_MCA is not set
# CONFIG_SCx200 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
#

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

#
# Parallel port support
#
CONFIG_PARPORT=y
CONFIG_PARPORT_PC=y
CONFIG_PARPORT_PC_CML1=y
# CONFIG_PARPORT_SERIAL is not set
# CONFIG_PARPORT_OTHER is not set
# CONFIG_PARPORT_1284 is not set

#
# Plug and Play support
#

#
# Block devices
#
CONFIG_BLK_DEV_FD=y
# CONFIG_PARIDE 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_LOOP is not set
# CONFIG_BLK_DEV_NBD is not set
# CONFIG_BLK_DEV_CARMEL is not set
# CONFIG_BLK_DEV_RAM 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 is not set
CONFIG_BLK_DEV_IDECD=y
# CONFIG_BLK_DEV_IDEFLOPPY is not set
# CONFIG_BLK_DEV_IDESCSI is not set
# CONFIG_IDE_TASK_IOCTL is not set

#
# IDE chipset support/bugfixes
#
CONFIG_IDE_GENERIC=y
CONFIG_BLK_DEV_CMD640=y
# CONFIG_BLK_DEV_CMD640_ENHANCED is not set
# CONFIG_BLK_DEV_IDEPCI is not set
# CONFIG_BLK_DEV_IDEDMA is not set
# CONFIG_IDEDMA_AUTO is not set
# CONFIG_BLK_DEV_HD is not set

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

#
# SCSI support type (disk, tape, CD-ROM)
#
CONFIG_BLK_DEV_SD=y
# 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=y
# CONFIG_SCSI_CONSTANTS is not set
# CONFIG_SCSI_LOGGING is not set

#
# SCSI Transport Attributes
#
# CONFIG_SCSI_SPI_ATTRS is not set
# CONFIG_SCSI_FC_ATTRS is not set

#
# SCSI low-level drivers
#
# CONFIG_BLK_DEV_3W_XXXX_RAID is not set
# CONFIG_SCSI_ACARD is not set
CONFIG_SCSI_AIC7XXX=y
CONFIG_AIC7XXX_CMDS_PER_DEVICE=32
CONFIG_AIC7XXX_RESET_DELAY_MS=15000
# CONFIG_AIC7XXX_BUILD_FIRMWARE is not set
# CONFIG_AIC7XXX_DEBUG_ENABLE is not set
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_MEGARAID 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_PPA is not set
# CONFIG_SCSI_IMM 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_QLA2XXX=y
# CONFIG_SCSI_QLA21XX is not set
# CONFIG_SCSI_QLA22XX is not set
# CONFIG_SCSI_QLA2300 is not set
# CONFIG_SCSI_QLA2322 is not set
# CONFIG_SCSI_QLA6312 is not set
# CONFIG_SCSI_QLA6322 is not set
# CONFIG_SCSI_DC390T 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
#
CONFIG_FUSION=y
CONFIG_FUSION_MAX_SGE=40
CONFIG_FUSION_ISENSE=m
CONFIG_FUSION_CTL=m

#
# IEEE 1394 (FireWire) support
#
# 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=y
# 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=m
# CONFIG_NET_IPGRE is not set
# CONFIG_IP_MROUTE is not set
CONFIG_SYN_COOKIES=y
# CONFIG_INET_AH is not set
# CONFIG_INET_ESP is not set
# CONFIG_INET_IPCOMP is not set

#
# IP: Virtual Server Configuration
#
# CONFIG_IP_VS is not set
# CONFIG_DECNET is not set
# CONFIG_BRIDGE is not set
CONFIG_NETFILTER=y
# CONFIG_NETFILTER_DEBUG is not set

#
# IP: Netfilter Configuration
#
CONFIG_IP_NF_CONNTRACK=m
CONFIG_IP_NF_FTP=m
CONFIG_IP_NF_IRC=m
CONFIG_IP_NF_TFTP=m
CONFIG_IP_NF_AMANDA=m
CONFIG_IP_NF_QUEUE=m
CONFIG_IP_NF_IPTABLES=m
CONFIG_IP_NF_MATCH_LIMIT=m
CONFIG_IP_NF_MATCH_IPRANGE=m
CONFIG_IP_NF_MATCH_MAC=m
CONFIG_IP_NF_MATCH_PKTTYPE=m
CONFIG_IP_NF_MATCH_MARK=m
CONFIG_IP_NF_MATCH_MULTIPORT=m
CONFIG_IP_NF_MATCH_TOS=m
CONFIG_IP_NF_MATCH_RECENT=m
CONFIG_IP_NF_MATCH_ECN=m
CONFIG_IP_NF_MATCH_DSCP=m
CONFIG_IP_NF_MATCH_AH_ESP=m
CONFIG_IP_NF_MATCH_LENGTH=m
CONFIG_IP_NF_MATCH_TTL=m
CONFIG_IP_NF_MATCH_TCPMSS=m
CONFIG_IP_NF_MATCH_HELPER=m
CONFIG_IP_NF_MATCH_STATE=m
CONFIG_IP_NF_MATCH_CONNTRACK=m
CONFIG_IP_NF_MATCH_OWNER=m
CONFIG_IP_NF_FILTER=m
CONFIG_IP_NF_TARGET_REJECT=m
CONFIG_IP_NF_NAT=m
CONFIG_IP_NF_NAT_NEEDED=y
CONFIG_IP_NF_TARGET_MASQUERADE=m
CONFIG_IP_NF_TARGET_REDIRECT=m
CONFIG_IP_NF_TARGET_NETMAP=m
CONFIG_IP_NF_TARGET_SAME=m
CONFIG_IP_NF_NAT_LOCAL=y
CONFIG_IP_NF_NAT_IRC=m
CONFIG_IP_NF_NAT_FTP=m
CONFIG_IP_NF_NAT_TFTP=m
CONFIG_IP_NF_NAT_AMANDA=m
CONFIG_IP_NF_MANGLE=m
CONFIG_IP_NF_TARGET_TOS=m
CONFIG_IP_NF_TARGET_ECN=m
CONFIG_IP_NF_TARGET_DSCP=m
CONFIG_IP_NF_TARGET_MARK=m
CONFIG_IP_NF_TARGET_CLASSIFY=m
CONFIG_IP_NF_TARGET_LOG=m
CONFIG_IP_NF_TARGET_ULOG=m
CONFIG_IP_NF_TARGET_TCPMSS=m
CONFIG_IP_NF_ARPTABLES=m
CONFIG_IP_NF_ARPFILTER=m
CONFIG_IP_NF_ARP_MANGLE=m
# CONFIG_IP_NF_COMPAT_IPCHAINS is not set
# CONFIG_IP_NF_COMPAT_IPFWADM is not set
CONFIG_XFRM=y
# CONFIG_XFRM_USER is not set
# CONFIG_VLAN_8021Q is not set
# CONFIG_LLC2 is not set
# CONFIG_IPX is not set
# CONFIG_ATALK is not set

#
# QoS and/or fair queueing
#
CONFIG_NET_SCHED=y
CONFIG_NET_SCH_CBQ=m
CONFIG_NET_SCH_HTB=m
CONFIG_NET_SCH_HFSC=m
CONFIG_NET_SCH_CSZ=m
CONFIG_NET_SCH_PRIO=m
CONFIG_NET_SCH_RED=m
CONFIG_NET_SCH_SFQ=m
CONFIG_NET_SCH_TEQL=m
CONFIG_NET_SCH_TBF=m
CONFIG_NET_SCH_GRED=m
CONFIG_NET_SCH_DSMARK=m
CONFIG_NET_SCH_DELAY=m
# CONFIG_NET_SCH_INGRESS is not set
# CONFIG_NET_QOS is not set
# CONFIG_NET_CLS 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

#
# Ethernet (10 or 100Mbit)
#
# CONFIG_NET_ETHERNET 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_R8169 is not set
# CONFIG_SK98LIN is not set
CONFIG_TIGON3=m

#
# Ethernet (10000 Mbit)
#
# CONFIG_IXGB is not set
# CONFIG_FDDI is not set
# CONFIG_PLIP 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

#
# 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
# CONFIG_NETPOLL is not set
# CONFIG_NET_POLL_CONTROLLER is not set

#
# ISDN subsystem
#
# CONFIG_ISDN 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=m
# 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_PARKBD 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_LKKBD 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_SERIAL is not set
# CONFIG_MOUSE_VSXXXAA 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=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_LEGACY_PTYS=y
CONFIG_LEGACY_PTY_COUNT=256
CONFIG_PRINTER=y
# CONFIG_LP_CONSOLE is not set
# CONFIG_PPDEV is not set
# CONFIG_TIPAR 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 is not set
# CONFIG_RTC is not set
# CONFIG_GEN_RTC is not set
# CONFIG_DTLK is not set
# CONFIG_R3964 is not set
# CONFIG_APPLICOM is not set

#
# Ftape, the floppy tape device driver
#
# CONFIG_FTAPE is not set
# CONFIG_AGP 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

#
# I2C support
#
# CONFIG_I2C is not set

#
# Misc devices
#
# CONFIG_IBM_ASM is not set

#
# Multimedia devices
#
# CONFIG_VIDEO_DEV is not set

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

#
# Graphics support
#
# CONFIG_FB is not set
# CONFIG_VIDEO_SELECT is not set

#
# Console display driver support
#
CONFIG_VGA_CONSOLE=y
# CONFIG_MDA_CONSOLE is not set
CONFIG_DUMMY_CONSOLE=y

#
# Sound
#
CONFIG_SOUND=y

#
# Advanced Linux Sound Architecture
#
# CONFIG_SND is not set

#
# Open Sound System
#
# CONFIG_SOUND_PRIME is not set

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

#
# Miscellaneous USB options
#
CONFIG_USB_DEVICEFS=y

#
# USB Host Controller Drivers
#
# CONFIG_USB_EHCI_HCD is not set
CONFIG_USB_OHCI_HCD=y
# 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 is not set

#
# USB Human Interface Devices (HID)
#
CONFIG_USB_HID=y
CONFIG_USB_HIDINPUT=y
# CONFIG_USB_HIDDEV 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_MTOUCH is not set
# CONFIG_USB_XPAD is not set
# CONFIG_USB_ATI_REMOTE is not set

#
# USB Imaging devices
#
# CONFIG_USB_MICROTEK 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_KAWETH is not set
# CONFIG_USB_USBNET is not set

#
# USB port drivers
#
# CONFIG_USB_USS720 is not set

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

#
# USB Miscellaneous drivers
#
# CONFIG_USB_EMI62 is not set
# CONFIG_USB_EMI26 is not set
# CONFIG_USB_TIGL is not set
# CONFIG_USB_LCD is not set
# CONFIG_USB_LED is not set

#
# USB Gadget Support
#
# 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=y

#
# CD-ROM/DVD Filesystems
#
CONFIG_ISO9660_FS=y
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=m
CONFIG_VFAT_FS=m
# CONFIG_NTFS_FS is not set

#
# Pseudo filesystems
#
CONFIG_PROC_FS=y
CONFIG_PROC_KCORE=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_HFSPLUS_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=y
# CONFIG_NFS_V3 is not set
CONFIG_NFSD=y
# CONFIG_NFSD_V3 is not set
CONFIG_LOCKD=y
CONFIG_EXPORTFS=y
CONFIG_SUNRPC=y
# CONFIG_SMB_FS is not set
# CONFIG_CIFS is not set
# CONFIG_NCP_FS is not set
# CONFIG_CODA_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=m
# CONFIG_NLS_CODEPAGE_737 is not set
# CONFIG_NLS_CODEPAGE_775 is not set
CONFIG_NLS_CODEPAGE_850=m
# 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=m
# 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=m
# CONFIG_NLS_KOI8_R is not set
# CONFIG_NLS_KOI8_U is not set
CONFIG_NLS_UTF8=m

#
# Kernel hacking
#
# CONFIG_DEBUG_KERNEL is not set
CONFIG_EARLY_PRINTK=y
# CONFIG_DEBUG_SPINLOCK_SLEEP is not set
# CONFIG_FRAME_POINTER is not set
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 is not set
# CONFIG_CRYPTO_NULL is not set
# CONFIG_CRYPTO_MD4 is not set
# CONFIG_CRYPTO_MD5 is not set
# CONFIG_CRYPTO_SHA1 is not set
# CONFIG_CRYPTO_SHA256 is not set
# CONFIG_CRYPTO_SHA512 is not set
# CONFIG_CRYPTO_DES is not set
# 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_ARC4 is not set
# CONFIG_CRYPTO_DEFLATE is not set
# CONFIG_CRYPTO_MICHAEL_MIC is not set
# CONFIG_CRYPTO_TEST is not set

#
# Library routines
#
# CONFIG_CRC32 is not set
CONFIG_X86_BIOS_REBOOT=y
CONFIG_PC=y

Re: Failing back to INSANE timesource :) Time stopped today.

[john stultz]

On Wed, 2004-04-14 at 01:54, Niclas Gustafsson wrote:
> Now it happened again, with my newly compiled kernel, I've attached the
> config file and dmesg for this kernel.
> 
> Watching the /proc/interrupts with 10s apart after the "stop".
> 
> [root@s151 root]# more /proc/interrupts
>            CPU0
>   0:   66413955  local-APIC-edge  timer
>   2:          0          XT-PIC  cascade
>   9:          1   IO-APIC-level  acpi
>  10:          0   IO-APIC-level  ohci_hcd
>  14:         24    IO-APIC-edge  ide0
>  20:      31244   IO-APIC-level  aic7xxx
>  22:   19652139   IO-APIC-level  eth0
> NMI:          0
> LOC:   67379568
> ERR:          0
> MIS:          0
> 
> And some 10-15 min later:
> 
> [root@s151 root]# cat /proc/interrupts
>            CPU0
>   0:   66413964  local-APIC-edge  timer
>   2:          0          XT-PIC  cascade
>   9:          1   IO-APIC-level  acpi
>  10:          0   IO-APIC-level  ohci_hcd
>  14:         24    IO-APIC-edge  ide0
>  20:      31245   IO-APIC-level  aic7xxx
>  22:   19754446   IO-APIC-level  eth0
> NMI:          0
> LOC:   68366976
> ERR:          0
> MIS:          0

Wow, clearly something is going wrong with interrupt delivery. You only
received 9 timer interrupts in 10 seconds!

> Worth noticing is the extreme increase in interrupts and context
> switches on the last output line from vmstat, however if this is a true
> picture of what happened or not I cannot say. Maybe this is just a
> result of timing problems?
> 
> However I see an increase in network activity just before the stop, the
> system goes from 2 Mbps output to about 55 Mbps on the last read. (Also
> read from this machine so I don't know about it's validity)

Yea, those values are both junk as the X/sec ratio is totally skewed. 

> Where can I see what the system is currently using as a timing source
> (TSC/HPET/PIT etc.)?

Note the "Using tsc for high-res timesource" in your dmesg. 

I'm working now to reproduce this w/ a 2G system here in our lab, and
just for completeness, could you also send me your BIOS revision number?

thanks
-john

Re: Failing back to INSANE timesource :) Time stopped today.

[Niclas Gustafsson]

ons 2004-04-14 klockan 20.36 skrev john stultz:

> > Where can I see what the system is currently using as a timing source
> > (TSC/HPET/PIT etc.)?
> 
> Note the "Using tsc for high-res timesource" in your dmesg. 
> 
Yes, I noticed that, however, when it stops using tsc, is there a way to
see what the current strategy is?  I.e. to what time source it is
falling back to? Or perhaps this is always the same? And because of this
not implemented into the proc-fs?  I have just briefly looked at the
kernel source for this, I'll have a closer look today if I can find the
time.

> I'm working now to reproduce this w/ a 2G system here in our lab, and
> just for completeness, could you also send me your BIOS revision number?
> 
Sure, Here is some info from bios:

Machine Type:  867373X
Flash EEPROM Revision Level: PLE161AUS
System Board Identifier: NA60B7Y0S3Q
System Serial Number: KDZZ6FC
Bios Date: 09/10/03

Some more info from Advanced/Cpu Frequency:
Bus: 133  MHz
Cpu Multiplier: 18 X
Processor Speed: 2.8 GHz
Single processor MP Table: Enabled
MP Table Version: 1.4
Hyper-Threading technology: ----------


Just a thought, how much if any, increase in performance can one gain
when disabling the Single processor MP Table option? It says, in the
help on that options, that one can benefit from disabling it on a
UP-system if I don't remember wrong now.

 
 
Cheers,

Niclas

Re: Failing back to INSANE timesource :) Time stopped today.

[Maciej W. Rozycki]

On Wed, 14 Apr 2004, Niclas Gustafsson wrote:

> Watching the /proc/interrupts with 10s apart after the "stop".
> 
> [root@s151 root]# more /proc/interrupts
>            CPU0
>   0:   66413955  local-APIC-edge  timer
[...]
> LOC:   67355837
> ERR:          0
> MIS:          0
> [root@s151 root]# more /proc/interrupts
>            CPU0
>   0:   66413955  local-APIC-edge  timer
[...]
> LOC:   67379568
> ERR:          0
> MIS:          0

 This may be because buggy SMM firmware messes with the 8259A (configured
for a transparent mode -- yes that rare "local-APIC-edge" mode is tricky
;-) ) insanely.  You've written this is an IBM box previously -- this 
would be no surprise.  The following patch should help -- I think it's 
already included in the -mm series.

-- 
+  Maciej W. Rozycki, Technical University of Gdansk, Poland   +
+--------------------------------------------------------------+
+        e-mail: macro@ds2.pg.gda.pl, PGP key available        +

patch-2.6.5-timer_ack-2
--- linux.macro/arch/i386/kernel/io_apic.c	Wed Apr 14 03:57:24 2004
+++ linux/arch/i386/kernel/io_apic.c	Thu Apr 15 14:41:10 2004
@@ -2152,6 +2152,10 @@ static inline void check_timer(void)
 {
 	int pin1, pin2;
 	int vector;
+	unsigned int ver;
+
+	ver = apic_read(APIC_LVR);
+	ver = GET_APIC_VERSION(ver);
 
 	/*
 	 * get/set the timer IRQ vector:
@@ -2165,11 +2169,15 @@ static inline void check_timer(void)
 	 * mode for the 8259A whenever interrupts are routed
 	 * through I/O APICs.  Also IRQ0 has to be enabled in
 	 * the 8259A which implies the virtual wire has to be
-	 * disabled in the local APIC.
+	 * disabled in the local APIC.  Finally timer interrupts
+	 * need to be acknowledged manually in the 8259A for
+	 * do_slow_timeoffset() and for the i82489DX when using
+	 * the NMI watchdog.
 	 */
 	apic_write_around(APIC_LVT0, APIC_LVT_MASKED | APIC_DM_EXTINT);
 	init_8259A(1);
-	timer_ack = 1;
+	timer_ack = !cpu_has_tsc;
+	timer_ack |= nmi_watchdog == NMI_IO_APIC && !APIC_INTEGRATED(ver);
 	enable_8259A_irq(0);
 
 	pin1 = find_isa_irq_pin(0, mp_INT);
@@ -2187,7 +2195,8 @@ static inline void check_timer(void)
 				disable_8259A_irq(0);
 				setup_nmi();
 				enable_8259A_irq(0);
-				check_nmi_watchdog();
+				if (check_nmi_watchdog() < 0)
+					timer_ack = !cpu_has_tsc;
 			}
 			return;
 		}
@@ -2210,7 +2219,8 @@ static inline void check_timer(void)
 				add_pin_to_irq(0, 0, pin2);
 			if (nmi_watchdog == NMI_IO_APIC) {
 				setup_nmi();
-				check_nmi_watchdog();
+				if (check_nmi_watchdog() < 0)
+					timer_ack = !cpu_has_tsc;
 			}
 			return;
 		}

Re: Failing back to INSANE timesource :) Time stopped today.

[Niclas Gustafsson]

Hello and thanks,

I've compiled and deployed a kernel with the patch below.
I'm about to start some more tests on the machine - it's going to be
interesting to see how it works out, I'll let you know.


Cheers,

Niclas
  

tor 2004-04-15 klockan 16.47 skrev Maciej W. Rozycki:
> On Wed, 14 Apr 2004, Niclas Gustafsson wrote:
> 
> > Watching the /proc/interrupts with 10s apart after the "stop".
> > 
> > [root@s151 root]# more /proc/interrupts
> >            CPU0
> >   0:   66413955  local-APIC-edge  timer
> [...]
> > LOC:   67355837
> > ERR:          0
> > MIS:          0
> > [root@s151 root]# more /proc/interrupts
> >            CPU0
> >   0:   66413955  local-APIC-edge  timer
> [...]
> > LOC:   67379568
> > ERR:          0
> > MIS:          0
> 
>  This may be because buggy SMM firmware messes with the 8259A (configured
> for a transparent mode -- yes that rare "local-APIC-edge" mode is tricky
> ;-) ) insanely.  You've written this is an IBM box previously -- this 
> would be no surprise.  The following patch should help -- I think it's 
> already included in the -mm series.

Re: Failing back to INSANE timesource :) Time stopped today.

[Niclas Gustafsson]

Hi again,

I've now been running the system since last week, about 6 days now with
sometimes quite high load, both in regard to CPU usage and network
traffic.
And it seems to be running just fine with the patch from Maciej.

I've got a couple of questions, 

When was this bug introduced? Was it 2.6.1 ( or rather somewhere in
2.5)? Or was it already present in 2.4?

When will this patch be merged into the 2.6-tree?  I don't have to
stress the impact of this problem on IBM servers as they are rendered
quite useless.

Which other IBM models are affected? Can I run 2.6.5 on my 345:s or
335:s?  Do they use the same buggy SMM firmware?




Cheers,

Niclas 


tor 2004-04-15 klockan 18.57 skrev Niclas Gustafsson:
> Hello and thanks,
> 
> I've compiled and deployed a kernel with the patch below.
> I'm about to start some more tests on the machine - it's going to be
> interesting to see how it works out, I'll let you know.
> 
> 
> Cheers,
> 
> Niclas
>   
> 
> tor 2004-04-15 klockan 16.47 skrev Maciej W. Rozycki:
> > On Wed, 14 Apr 2004, Niclas Gustafsson wrote:
> > 
> > > Watching the /proc/interrupts with 10s apart after the "stop".
> > > 
> > > [root@s151 root]# more /proc/interrupts
> > >            CPU0
> > >   0:   66413955  local-APIC-edge  timer
> > [...]
> > > LOC:   67355837
> > > ERR:          0
> > > MIS:          0
> > > [root@s151 root]# more /proc/interrupts
> > >            CPU0
> > >   0:   66413955  local-APIC-edge  timer
> > [...]
> > > LOC:   67379568
> > > ERR:          0
> > > MIS:          0
> > 
> >  This may be because buggy SMM firmware messes with the 8259A (configured
> > for a transparent mode -- yes that rare "local-APIC-edge" mode is tricky
> > ;-) ) insanely.  You've written this is an IBM box previously -- this 
> > would be no surprise.  The following patch should help -- I think it's 
> > already included in the -mm series.

Re: Failing back to INSANE timesource :) Time stopped today.

[Maciej W. Rozycki]

On Tue, 20 Apr 2004, Niclas Gustafsson wrote:

> I've now been running the system since last week, about 6 days now with
> sometimes quite high load, both in regard to CPU usage and network
> traffic.
> And it seems to be running just fine with the patch from Maciej.

 I'm glad to read this.

> I've got a couple of questions, 
> 
> When was this bug introduced? Was it 2.6.1 ( or rather somewhere in
> 2.5)? Or was it already present in 2.4?

 Well, the bug has been introduced by IBM in their firmware (SMM code).  
;-)  The patch only works it around.  Functionally the changed code is the
same for your configuration.

 If you are asking about the problematic code, then it's there since
2.3.x, so it's in 2.4, too.  It's a part of the NMI watchdog support,
though it's used for ordinary timer interrupts for certain systems as
well.

> When will this patch be merged into the 2.6-tree?  I don't have to
> stress the impact of this problem on IBM servers as they are rendered
> quite useless.

 Apparently there are problems with the workaround on certain AMD
Athlon-based systems.  I suppose they need to be resolved somehow first.

> Which other IBM models are affected? Can I run 2.6.5 on my 345:s or
> 335:s?  Do they use the same buggy SMM firmware?

 Ask IBM.  The reason is an incorrect handling of PIC (8259A) state
saving/restoration.

-- 
+  Maciej W. Rozycki, Technical University of Gdansk, Poland   +
+--------------------------------------------------------------+
+        e-mail: macro@ds2.pg.gda.pl, PGP key available        +

Re: Failing back to INSANE timesource :) Time stopped today.

[john stultz]

On Tue, 2004-04-20 at 05:40, Maciej W. Rozycki wrote:
> On Tue, 20 Apr 2004, Niclas Gustafsson wrote:
> 
> > I've now been running the system since last week, about 6 days now with
> > sometimes quite high load, both in regard to CPU usage and network
> > traffic.
> > And it seems to be running just fine with the patch from Maciej.
> 
>  I'm glad to read this.

It appears to be working here in our labs as well.


> > I've got a couple of questions, 
> > 
> > When was this bug introduced? Was it 2.6.1 ( or rather somewhere in
> > 2.5)? Or was it already present in 2.4?
> 
>  Well, the bug has been introduced by IBM in their firmware (SMM code).  
> ;-)  The patch only works it around.  Functionally the changed code is the
> same for your configuration.
> 
>  If you are asking about the problematic code, then it's there since
> 2.3.x, so it's in 2.4, too.  It's a part of the NMI watchdog support,
> though it's used for ordinary timer interrupts for certain systems as
> well.

Are you saying that 2.4 will exhibit this problem as well, or that 2.4
already has an equivalent workaround?


> > When will this patch be merged into the 2.6-tree?  I don't have to
> > stress the impact of this problem on IBM servers as they are rendered
> > quite useless.
> 
>  Apparently there are problems with the workaround on certain AMD
> Athlon-based systems.  I suppose they need to be resolved somehow first.

Can you point me to any threads on this issue. I'd like to do what I can
to help get this workaround in.

> > Which other IBM models are affected? Can I run 2.6.5 on my 345:s or
> > 335:s?  Do they use the same buggy SMM firmware?
> 
>  Ask IBM.  The reason is an incorrect handling of PIC (8259A) state
> saving/restoration.

I'm following up w/ our hardware group about this issue.

Thanks so much for the help!
-john

Re: Failing back to INSANE timesource :) Time stopped today.

[Maciej W. Rozycki]

On Tue, 20 Apr 2004, john stultz wrote:

> >  If you are asking about the problematic code, then it's there since
> > 2.3.x, so it's in 2.4, too.  It's a part of the NMI watchdog support,
> > though it's used for ordinary timer interrupts for certain systems as
> > well.
> 
> Are you saying that 2.4 will exhibit this problem as well, or that 2.4
> already has an equivalent workaround?

 The former.

> >  Apparently there are problems with the workaround on certain AMD
> > Athlon-based systems.  I suppose they need to be resolved somehow first.
> 
> Can you point me to any threads on this issue. I'd like to do what I can
> to help get this workaround in.

 Here's my reply to a report which seems not to have reached LKML archives
for some reason:  
"http://www.uwsg.indiana.edu/hypermail/linux/kernel/0403.2/0384".  The
important part of the original mail is quoted.

-- 
+  Maciej W. Rozycki, Technical University of Gdansk, Poland   +
+--------------------------------------------------------------+
+        e-mail: macro@ds2.pg.gda.pl, PGP key available        +

Re: Failing back to INSANE timesource :) Time stopped today.

[john stultz]

On Thu, 2004-04-15 at 07:47, Maciej W. Rozycki wrote:
>  This may be because buggy SMM firmware messes with the 8259A (configured
> for a transparent mode -- yes that rare "local-APIC-edge" mode is tricky
> ;-) ) insanely.  You've written this is an IBM box previously -- this 
> would be no surprise.  The following patch should help -- I think it's 
> already included in the -mm series.

Just a FYI: I opened bugme bug #2544 to track this issue. 
http://bugme.osdl.org/show_bug.cgi?id=2544

thanks
-john