Re: NO ADSL with kernel-smp 2.6.12-1.1376_FC3

[Antonio Montagnani]

Bob Chiodini said the following on 31/08/2005 12:53:
> On Wed, 2005-08-31 at 11:47 +0200, Antonio Montagnani wrote:
> > Bob Chiodini said the following on 31/08/2005 11:33:
> > > On Wed, 2005-08-31 at 07:52 +0200, Antonio Montagnani wrote:
> > > > Edward Dekkers said the following on 31/08/2005 06:26:
> > > > > Antonio Montagnani wrote:
> > > > > > Antonio Montagnani said the following on 30/08/2005 09:16:
> > > > > >
> > > > > > >Edward Dekkers said the following on 30/08/2005 09:06:
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >>Antonio Montagnani wrote:
> > > > > > >>
> > > > > > >>
> > > > > > >>
> > > > > > >>>I cannot connect to my ADSL Internet if I use SMP kernel, while 
> > > > > > >>>with standard 2.6.12-1.1376 kernel on same machine, it works 
> > > > > > >>>flawlessly.
> > > > > > >>>The modem works, Ethernet network is on but connection is refused
> > > > > > >>>Shall I file a bug??
> > > > > > >>
> > > > > > >>
> > > > > > >>
> > > > > > >>
> > > > > > >>
> > > > > > >>No,
> > > > > > >>
> > > > > > >>There is no real difference between running a standard kernel or an 
> > > > > > >>SMP one. Bar the fact that SMP will actually use the two processors 
> > > > > > >>in your machine that is. I run SMP myself, and it makes no 
> > > > > > >>difference to my connection running standard or SMP kernel.
> > > > > > >>
> > > > > > >>I'd look at doing some other diagnostic work before filing a report.
> > > > > > >>
> > > > > > >>We can't help you for the rest because you don't explain your set up.
> > > > > > >>
> > > > > > >>Regards,
> > > > > > >>Ed.
> > > > > > >>
> > > > > > >
> > > > > > >My setup is very standard, a Pentium 4 Asus motherboard P5P800, 1 GB, 
> > > > > > >two network cards (the integrated is connected to my network, the 
> > > > > > >Realtek 8029 to my ethernet modem).
> > > > > > >Which diagnostic shall I check??
> > > > > > >
> > > > > >
> > > > > > upgraded to FC4, same behaviour also with 2.6.12-1.447smp
> > > > > >
> > > > > > where to look???
> > > > >
> > > > > Number one would be to see if the Realtek interface actually comes up - 
> > > > > then there's a whole slew of tools like ifconfig, ping, iptraf, dhclient 
> > > > > etc. to be used one by one to see where the problem lies.
> > > > >
> > > > > When I asked you to provide more details, I wasn't really after 
> > > > > motherboard and stuff like that, I was after your internet connection 
> > > > > details of course. This is how I would describe one for example:
> > > > >
> > > > > Maestro Woomera Serial modem connected to /dev/ttyS0
> > > > > Using pppd on demand/wvdial to make a connection
> > > > > The IP address on that interface (ppp0) is assigned dynamically by my isp.
> > > > > The log shows dialling to be ok, and pppd taking over the connection 
> > > > > once wvdial has established it.
> > > > > ifconfig shows an IP allocated to me ip address: 203.0.178.191 with 
> > > > > netmask 255.255.255.0.
> > > > > I can ping internal addresses and external ones by name 
> > > > > (www.microsoft.com) and number (207.46.199.60).
> > > > >
> > > > > This is in the case of dial-up. Your trace will be different.
> > > > >
> > > > > Really, you have provided nothing of use in diagnosing this problem. I'm 
> > > > > assuming your modem takes care of the connection and just gives you an 
> > > > > internal IP address which you set to the gateway? or do you need to run 
> > > > > PPPoE or some other protocol manually?
> > > > >
> > > > > You must assume we know nothing about your set-up when posting to this 
> > > > > list.
> > > > >
> > > > > Regards,
> > > > > Ed.
> > > >
> > > > Ed,
> > > >
> > > > it seems that I can't ping the Ethernet modem when using SMP 
> > > > kernel(destination unreachable), if I connet to ist internal webpage I 
> > > > get a message of no routing.
> > > > I have iptables running: and everything is o.k on standard kernel!!!
> > > > What is happening???
> > > >
> > > > -- 
> > > > Antonio
> > >
> > > Anything relevant in /var/log/messages?  What is the output of route -n?
> > >
> > > Bob...
> >
> > I had a look at /var/log/messages (that I attach, only as e-mail to 
> > you...), but I am not very expert.
> > I see a timeout transmit on eth0 repeated many times when using SMP 
> > kernel at about 6.35 at the end.
> > I see also many errors conencted to ACPI (on both kernels) that I am not 
> > able to decode
> >
> > Tnx
>
> Antonio,
>
> I culled the messages down into a SMP boot and a UP boot.  A quick look
> indicates one message is missing in the SMP boot log.  It's marked with
> an arrow and indicates that the eth0 device interrupt was detected as
> IRQ 11 (UP only).  Hopefully someone can shed some light on this.  Some
> other information that might help:
>
> cat /proc/interrupts for both the UP and SMP.
>
> Also, do you have the latest BIOS installed for your motherboard?  What
> kind of motherboard is this?

An Asus P5P800, Bios updated in July

Check the IO-APIC options in the BIOS
> setup.
>
> You might try moving the realtek NIC to another slot.  That's a shot in
> the dark, but it's pretty early and I'm only into my first cup of
> coffee!
>
> Bob...

Standard
       CPU0
   0:   20180445          XT-PIC  timer
   1:       5563          XT-PIC  i8042
   2:          0          XT-PIC  cascade
   5:     701131          XT-PIC  SysKonnect SK-98xx, Intel ICH5, 
ehci_hcd:usb1, uhci_hcd:usb3
   8:          1          XT-PIC  rtc
  11:     380784          XT-PIC  uhci_hcd:usb2, uhci_hcd:usb4, 
uhci_hcd:usb5, eth0
  12:     801086          XT-PIC  i8042
  14:     112972          XT-PIC  ide0
  15:     358109          XT-PIC  ide1
NMI:          0
ERR:          0

SMP
        CPU0       CPU1
   0:     137004      48896    IO-APIC-edge  timer
   1:         29         27    IO-APIC-edge  i8042
   5:          0          0    IO-APIC-edge  SysKonnect SK-98xx, Intel 
ICH5, ehci _hcd:usb1, uhci_hcd:usb3
   8:          1          0    IO-APIC-edge  rtc
  11:          0          0    IO-APIC-edge  uhci_hcd:usb2, 
uhci_hcd:usb4, uhci_h cd:usb5, eth0
  12:       1146        836    IO-APIC-edge  i8042
  14:       9294       5957    IO-APIC-edge  ide0
  15:        440        568    IO-APIC-edge  ide1
NMI:          0          0
LOC:     181971     182055
ERR:          0
MIS:          0

I am wondering if the two kernels have different management of iptables, 
in particular IPv4 or IPv6, another shot in the dark, even if is 
afternoon here

tnx

NO ADSL with kernel-smp 2.6.12-1.1376_FC3

[Bob Chiodini]

On Wed, 2005-08-31 at 14:09 +0200, Antonio Montagnani wrote:
> Bob Chiodini said the following on 31/08/2005 12:53:
> > On Wed, 2005-08-31 at 11:47 +0200, Antonio Montagnani wrote:
> > > Bob Chiodini said the following on 31/08/2005 11:33:
> > > > On Wed, 2005-08-31 at 07:52 +0200, Antonio Montagnani wrote:
> > > > > Edward Dekkers said the following on 31/08/2005 06:26:
> > > > > > Antonio Montagnani wrote:
> > > > > >
> > > > > > >Antonio Montagnani said the following on 30/08/2005 09:16:
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >>Edward Dekkers said the following on 30/08/2005 09:06:
> > > > > > >>
> > > > > > >>
> > > > > > >>
> > > > > > >>>Antonio Montagnani wrote:
> > > > > > >>>
> > > > > > >>>
> > > > > > >>>
> > > > > > >>>>I cannot connect to my ADSL Internet if I use SMP kernel, while 
> > > > > > >>>>with standard 2.6.12-1.1376 kernel on same machine, it works 
> > > > > > >>>>flawlessly.
> > > > > > >>>>The modem works, Ethernet network is on but connection is refused
> > > > > > >>>>Shall I file a bug??
> > > > > > >>>
> > > > > > >>>
> > > > > > >>>
> > > > > > >>>
> > > > > > >>>
> > > > > > >>>No,
> > > > > > >>>
> > > > > > >>>There is no real difference between running a standard kernel or an 
> > > > > > >>>SMP one. Bar the fact that SMP will actually use the two processors 
> > > > > > >>>in your machine that is. I run SMP myself, and it makes no 
> > > > > > >>>difference to my connection running standard or SMP kernel.
> > > > > > >>>
> > > > > > >>>I'd look at doing some other diagnostic work before filing a report.
> > > > > > >>>
> > > > > > >>>We can't help you for the rest because you don't explain your set up.
> > > > > > >>>
> > > > > > >>>Regards,
> > > > > > >>>Ed.
> > > > > > >>>
> > > > > > >>
> > > > > > >>My setup is very standard, a Pentium 4 Asus motherboard P5P800, 1 GB, 
> > > > > > >>two network cards (the integrated is connected to my network, the 
> > > > > > >>Realtek 8029 to my ethernet modem).
> > > > > > >>Which diagnostic shall I check??
> > > > > > >>
> > > > > > >
> > > > > > >upgraded to FC4, same behaviour also with 2.6.12-1.447smp
> > > > > > >
> > > > > > >where to look???
> > > > > > >
> > > > > >
> > > > > > Number one would be to see if the Realtek interface actually comes up - 
> > > > > > then there's a whole slew of tools like ifconfig, ping, iptraf, dhclient 
> > > > > > etc. to be used one by one to see where the problem lies.
> > > > > >
> > > > > > When I asked you to provide more details, I wasn't really after 
> > > > > > motherboard and stuff like that, I was after your internet connection 
> > > > > > details of course. This is how I would describe one for example:
> > > > > >
> > > > > > Maestro Woomera Serial modem connected to /dev/ttyS0
> > > > > > Using pppd on demand/wvdial to make a connection
> > > > > > The IP address on that interface (ppp0) is assigned dynamically by my isp.
> > > > > > The log shows dialling to be ok, and pppd taking over the connection 
> > > > > > once wvdial has established it.
> > > > > > ifconfig shows an IP allocated to me ip address: 203.0.178.191 with 
> > > > > > netmask 255.255.255.0.
> > > > > > I can ping internal addresses and external ones by name 
> > > > > > (www.microsoft.com) and number (207.46.199.60).
> > > > > >
> > > > > > This is in the case of dial-up. Your trace will be different.
> > > > > >
> > > > > > Really, you have provided nothing of use in diagnosing this problem. I'm 
> > > > > > assuming your modem takes care of the connection and just gives you an 
> > > > > > internal IP address which you set to the gateway? or do you need to run 
> > > > > > PPPoE or some other protocol manually?
> > > > > >
> > > > > > You must assume we know nothing about your set-up when posting to this 
> > > > > > list.
> > > > > >
> > > > > > Regards,
> > > > > > Ed.
> > > > >
> > > > > Ed,
> > > > >
> > > > > it seems that I can't ping the Ethernet modem when using SMP 
> > > > > kernel(destination unreachable), if I connet to ist internal webpage I 
> > > > > get a message of no routing.
> > > > > I have iptables running: and everything is o.k on standard kernel!!!
> > > > > What is happening???
> > > > >
> > > > > -- 
> > > > > Antonio
> > > >
> > > > Anything relevant in /var/log/messages?  What is the output of route -n?
> > > >
> > > > Bob...
> > >
> > > I had a look at /var/log/messages (that I attach, only as e-mail to 
> > > you...), but I am not very expert.
> > > I see a timeout transmit on eth0 repeated many times when using SMP 
> > > kernel at about 6.35 at the end.
> > > I see also many errors conencted to ACPI (on both kernels) that I am not 
> > > able to decode
> > >
> > > Tnx
> >
> > Antonio,
> >
> > I culled the messages down into a SMP boot and a UP boot.  A quick look
> > indicates one message is missing in the SMP boot log.  It's marked with
> > an arrow and indicates that the eth0 device interrupt was detected as
> > IRQ 11 (UP only).  Hopefully someone can shed some light on this.  Some
> > other information that might help:
> >
> > cat /proc/interrupts for both the UP and SMP.
> >
> > Also, do you have the latest BIOS installed for your motherboard?  What
> > kind of motherboard is this?
>
> An Asus P5P800, Bios updated in July
>
> Check the IO-APIC options in the BIOS
> > setup.
> >
> > You might try moving the realtek NIC to another slot.  That's a shot in
> > the dark, but it's pretty early and I'm only into my first cup of
> > coffee!
> >
> > Bob...
> Standard
>    CPU0
>
> 0:   20180445          XT-PIC  timer
>    1:       5563          XT-PIC  i8042
>    2:          0          XT-PIC  cascade
>    5:     701131          XT-PIC  SysKonnect SK-98xx, Intel ICH5, 
> ehci_hcd:usb1, uhci_hcd:usb3
>    8:          1          XT-PIC  rtc
>   11:     380784          XT-PIC  uhci_hcd:usb2, uhci_hcd:usb4, 
> uhci_hcd:usb5, eth0
>   12:     801086          XT-PIC  i8042
>   14:     112972          XT-PIC  ide0
>   15:     358109          XT-PIC  ide1
> NMI:          0
> ERR:          0
>
> SMP
>         CPU0       CPU1
>    0:     137004      48896    IO-APIC-edge  timer
>    1:         29         27    IO-APIC-edge  i8042
>    5:          0          0    IO-APIC-edge  SysKonnect SK-98xx, Intel 
> ICH5, ehci _hcd:usb1, uhci_hcd:usb3
>    8:          1          0    IO-APIC-edge  rtc
>   11:          0          0    IO-APIC-edge  uhci_hcd:usb2, 
> uhci_hcd:usb4, uhci_h cd:usb5, eth0
>   12:       1146        836    IO-APIC-edge  i8042
>   14:       9294       5957    IO-APIC-edge  ide0
>   15:        440        568    IO-APIC-edge  ide1
> NMI:          0          0
> LOC:     181971     182055
> ERR:          0
> MIS:          0
>
> I am wondering if the two kernels have different management of iptables, 
> in particular IPv4 or IPv6, another shot in the dark, even if is 
> afternoon here
>
> tnx

Antonio,

service iptables stop.  I suspect that the IRQ for eth0 is not getting
properly registered and thus the timeouts.

Does specifying acpi=ht on the SMP kernel command line make any
difference?  It probably defeats the purpose of SMP.

Bob...

NO ADSL with kernel-smp 2.6.12-1.1376_FC3

[Antonio Montagnani]

Bob Chiodini said the following on 31/08/2005 14:18:
> > >
> >
> > Standard
> >       CPU0
> >   0:   20180445          XT-PIC  timer
> >   1:       5563          XT-PIC  i8042
> >   2:          0          XT-PIC  cascade
> >   5:     701131          XT-PIC  SysKonnect SK-98xx, Intel ICH5, 
> > ehci_hcd:usb1, uhci_hcd:usb3
> >   8:          1          XT-PIC  rtc
> >  11:     380784          XT-PIC  uhci_hcd:usb2, uhci_hcd:usb4, 
> > uhci_hcd:usb5, eth0
> >  12:     801086          XT-PIC  i8042
> >  14:     112972          XT-PIC  ide0
> >  15:     358109          XT-PIC  ide1
> > NMI:          0
> > ERR:          0
> >
> > SMP
> >        CPU0       CPU1
> >   0:     137004      48896    IO-APIC-edge  timer
> >   1:         29         27    IO-APIC-edge  i8042
> >   5:          0          0    IO-APIC-edge  SysKonnect SK-98xx, Intel 
> > ICH5, ehci _hcd:usb1, uhci_hcd:usb3
> >   8:          1          0    IO-APIC-edge  rtc
> >  11:          0          0    IO-APIC-edge  uhci_hcd:usb2, 
> > uhci_hcd:usb4, uhci_h cd:usb5, eth0
> >  12:       1146        836    IO-APIC-edge  i8042
> >  14:       9294       5957    IO-APIC-edge  ide0
> >  15:        440        568    IO-APIC-edge  ide1
> > NMI:          0          0
> > LOC:     181971     182055
> > ERR:          0
> > MIS:          0
> >
> > I am wondering if the two kernels have different management of iptables, 
> > in particular IPv4 or IPv6, another shot in the dark, even if is 
> > afternoon here
> >
> > tnx
>
> Antonio,
>
> service iptables stop.  I suspect that the IRQ for eth0 is not getting
> properly registered and thus the timeouts.
>
> Does specifying acpi=ht on the SMP kernel command line make any
> difference?  It probably defeats the purpose of SMP.

It works now, with acpi=ht.
But is SMP working??

This is the output of var/log/messages, it seems that also errors on 
ACPI have been deletd!!!
Shall I include same option in the standard kernel???

Aug 31 15:05:36 Casa kernel: Linux version 2.6.12-1.1447_FC4smp 
([e-mail]) (gcc version 4.0.1 20050727 (Red 
Hat 4.0.1-5)) #1 SMP Fri Aug 26 20:57:13 EDT 2005
Aug 31 15:05:36 Casa kernel: BIOS-provided physical RAM map:
Aug 31 15:05:36 Casa kernel:  BIOS-e820: 0000000000000000 - 
000000000009fc00 (usable)
Aug 31 15:05:36 Casa kernel:  BIOS-e820: 000000000009fc00 - 
00000000000a0000 (reserved)
Aug 31 15:05:36 Casa kernel:  BIOS-e820: 00000000000e0000 - 
0000000000100000 (reserved)
Aug 31 15:05:36 Casa kernel:  BIOS-e820: 0000000000100000 - 
000000003ffb0000 (usable)
Aug 31 15:05:36 Casa kernel:  BIOS-e820: 000000003ffb0000 - 
000000003ffc0000 (ACPI data)
Aug 31 15:05:36 Casa kernel:  BIOS-e820: 000000003ffc0000 - 
000000003fff0000 (ACPI NVS)
Aug 31 15:05:36 Casa kernel:  BIOS-e820: 000000003fff0000 - 
0000000040000000 (reserved)
Aug 31 15:05:36 Casa kernel:  BIOS-e820: 00000000ffb80000 - 
0000000100000000 (reserved)
Aug 31 15:05:36 Casa kernel: 127MB HIGHMEM available.
Aug 31 15:05:36 Casa kernel: 896MB LOWMEM available.
Aug 31 15:05:36 Casa kernel: found SMP MP-table at 000ff780
Aug 31 15:05:36 Casa kernel: Using x86 segment limits to approximate NX 
protection
Aug 31 15:05:36 Casa kernel: DMI 2.3 present.
Aug 31 15:05:36 Casa kernel: Using APIC driver default
Aug 31 15:05:37 Casa kernel: ACPI: PM-Timer IO Port: 0x808
Aug 31 15:05:37 Casa kernel: ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] 
enabled)
Aug 31 15:05:37 Casa kernel: Processor #0 15:4 APIC version 20
Aug 31 15:05:37 Casa kernel: ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] 
enabled)
Aug 31 15:05:37 Casa kernel: Processor #1 15:4 APIC version 20
Aug 31 15:05:37 Casa kernel: Using ACPI for processor (LAPIC) 
configuration information
Aug 31 15:05:37 Casa kernel: Intel MultiProcessor Specification v1.1
Aug 31 15:05:37 Casa kernel:     Virtual Wire compatibility mode.
Aug 31 15:05:37 Casa kernel: OEM ID: ASUSTeK  Product ID:  APIC at: 
0xFEE00000
Aug 31 15:05:37 Casa kernel: I/O APIC #2 Version 32 at 0xFEC00000.
Aug 31 15:05:37 Casa kernel: Enabling APIC mode:  Flat.  Using 1 I/O APICs
Aug 31 15:05:37 Casa kernel: Processors: 2
Aug 31 15:05:37 Casa kernel: Allocating PCI resources starting at 
40000000 (gap: 40000000:bfb80000)
Aug 31 15:05:37 Casa kernel: Built 1 zonelists
Aug 31 15:05:37 Casa kernel: Kernel command line: ro 
root=/dev/VolGroup00/LogVol00 rhgb quiet acpi=ht
Aug 31 15:05:37 Casa kernel: Initializing CPU#0
Aug 31 15:05:37 Casa kernel: CPU 0 irqstacks, hard=c042d000 soft=c040d000
Aug 31 15:05:37 Casa kernel: PID hash table entries: 4096 (order: 12, 
65536 bytes)
Aug 31 15:05:37 Casa kernel: Detected 3007.774 MHz processor.
Aug 31 15:05:37 Casa kernel: Using pmtmr for high-res timesource
Aug 31 15:05:37 Casa kernel: Console: colour VGA+ 80x25
Aug 31 15:05:37 Casa kernel: Dentry cache hash table entries: 131072 
(order: 7, 524288 bytes)
Aug 31 15:05:37 Casa kernel: Inode-cache hash table entries: 65536 
(order: 6, 262144 bytes)
Aug 31 15:05:37 Casa kernel: Memory: 1031872k/1048256k available (2087k 
kernel code, 15492k reserved, 775k data, 236k init, 130752k highmem)
Aug 31 15:05:37 Casa kernel: Checking if this processor honours the WP 
bit even in supervisor mode... Ok.
Aug 31 15:05:37 Casa kernel: Security Framework v1.0.0 initialized
Aug 31 15:05:37 Casa kernel: SELinux:  Initializing.
Aug 31 15:05:37 Casa kernel: SELinux:  Starting in permissive mode
Aug 31 15:05:37 Casa kernel: selinux_register_security:  Registering 
secondary module capability
Aug 31 15:05:37 Casa kernel: Capability LSM initialized as secondary
Aug 31 15:05:37 Casa kernel: Mount-cache hash table entries: 512
Aug 31 15:05:37 Casa kernel: monitor/mwait feature present.
Aug 31 15:05:37 Casa kernel: using mwait in idle threads.
Aug 31 15:05:37 Casa kernel: CPU: Trace cache: 12K uops, L1 D cache: 16K
Aug 31 15:05:37 Casa kernel: CPU: L2 cache: 1024K
Aug 31 15:05:37 Casa kernel: CPU: Physical Processor ID: 0
Aug 31 15:05:37 Casa kernel: Intel machine check architecture supported.
Aug 31 15:05:37 Casa kernel: Intel machine check reporting enabled on CPU#0.
Aug 31 15:05:37 Casa kernel: CPU0: Intel P4/Xeon Extended MCE MSRs (12) 
available
Aug 31 15:05:37 Casa rpc.statd[2018]: Version 1.0.7 Starting
Aug 31 15:05:37 Casa kernel: CPU0: Thermal monitoring enabled
Aug 31 15:05:37 Casa kernel: Enabling fast FPU save and restore... done.
Aug 31 15:05:37 Casa kernel: Enabling unmasked SIMD FPU exception 
support... done.
Aug 31 15:05:37 Casa kernel: Checking 'hlt' instruction... OK.
Aug 31 15:05:37 Casa kernel: CPU0: Intel(R) Pentium(R) 4 CPU 3.00GHz 
stepping 01
Aug 31 15:05:37 Casa kernel: Booting processor 1/1 eip 3000
Aug 31 15:05:37 Casa kernel: CPU 1 irqstacks, hard=c042e000 soft=c040e000
Aug 31 15:05:37 Casa kernel: Initializing CPU#1
Aug 31 15:05:37 Casa kernel: monitor/mwait feature present.
Aug 31 15:05:37 Casa kernel: CPU: Trace cache: 12K uops, L1 D cache: 16K
Aug 31 15:05:37 Casa kernel: CPU: L2 cache: 1024K
Aug 31 15:05:37 Casa kernel: CPU: Physical Processor ID: 0
Aug 31 15:05:37 Casa kernel: Intel machine check architecture supported.
Aug 31 15:05:37 Casa kernel: Intel machine check reporting enabled on CPU#1.
Aug 31 15:05:37 Casa kernel: CPU1: Intel P4/Xeon Extended MCE MSRs (12) 
available
Aug 31 15:05:37 Casa kernel: CPU1: Thermal monitoring enabled
Aug 31 15:05:37 Casa kernel: CPU1: Intel(R) Pentium(R) 4 CPU 3.00GHz 
stepping 01
Aug 31 15:05:37 Casa kernel: Total of 2 processors activated (11960.32 
BogoMIPS).
Aug 31 15:05:37 Casa kernel: ENABLING IO-APIC IRQs
Aug 31 15:05:37 Casa kernel: ..TIMER: vector=0x31 pin1=2 pin2=0
Aug 31 15:05:37 Casa kernel: checking TSC synchronization across 2 CPUs: 
passed.
Aug 31 15:05:37 Casa kernel: Brought up 2 CPUs
Aug 31 15:05:37 Casa auditd[2032]: Init complete, auditd 1.0.3 listening 
for events
Aug 31 15:05:37 Casa kernel: checking if image is initramfs... it is
Aug 31 15:05:37 Casa kernel: Freeing initrd memory: 1657k freed
Aug 31 15:05:37 Casa kernel: NET: Registered protocol family 16
Aug 31 15:05:37 Casa kernel: PCI: PCI BIOS revision 2.10 entry at 
0xf0031, last bus=2
Aug 31 15:05:37 Casa kernel: PCI: Using configuration type 1
Aug 31 15:05:37 Casa kernel: mtrr: v2.0 (20020519)
Aug 31 15:05:37 Casa kernel: ACPI: Subsystem revision 20050729
Aug 31 15:05:37 Casa kernel: ACPI: Interpreter disabled.
Aug 31 15:05:37 Casa kernel: Linux Plug and Play Support v0.97 (c) Adam 
Belay
Aug 31 15:05:37 Casa kernel: pnp: PnP ACPI: disabled
Aug 31 15:05:37 Casa kernel: usbcore: registered new driver usbfs
Aug 31 15:05:37 Casa kernel: usbcore: registered new driver hub
Aug 31 15:05:37 Casa kernel: PCI: Probing PCI hardware
Aug 31 15:05:38 Casa kernel: PCI: Probing PCI hardware (bus 00)
Aug 31 15:05:38 Casa kernel: PCI: Ignoring BAR0-3 of IDE controller 
0000:00:1f.1
Aug 31 15:05:38 Casa kernel: PCI: Transparent bridge - 0000:00:1e.0
Aug 31 15:05:38 Casa kernel: PCI: Discovered primary peer bus ff [IRQ]
Aug 31 15:05:38 Casa kernel: PCI: Using IRQ router PIIX/ICH [8086/24d0] 
at 0000:00:1f.0
Aug 31 15:05:38 Casa kernel: PCI->APIC IRQ transform: 0000:00:1d.0[A] -> 
IRQ 169
Aug 31 15:05:38 Casa kernel: PCI->APIC IRQ transform: 0000:00:1d.1[B] -> 
IRQ 193
Aug 31 15:05:38 Casa kernel: PCI->APIC IRQ transform: 0000:00:1d.2[C] -> 
IRQ 185
Aug 31 15:05:38 Casa kernel: PCI->APIC IRQ transform: 0000:00:1d.3[A] -> 
IRQ 169
Aug 31 15:05:38 Casa kernel: PCI->APIC IRQ transform: 0000:00:1d.7[D] -> 
IRQ 225
Aug 31 15:05:38 Casa kernel: PCI->APIC IRQ transform: 0000:00:1f.1[A] -> 
IRQ 185
Aug 31 15:05:38 Casa kernel: PCI->APIC IRQ transform: 0000:00:1f.5[B] -> 
IRQ 177
Aug 31 15:05:38 Casa kernel: PCI->APIC IRQ transform: 0000:01:00.0[A] -> 
IRQ 169
Aug 31 15:05:38 Casa kernel: PCI->APIC IRQ transform: 0000:02:05.0[A] -> 
IRQ 217
Aug 31 15:05:38 Casa kernel: PCI->APIC IRQ transform: 0000:02:0c.0[A] -> 
IRQ 201
Aug 31 15:05:38 Casa kernel: PCI->APIC IRQ transform: 0000:02:0d.0[A] -> 
IRQ 209
Aug 31 15:05:38 Casa kernel: apm: BIOS version 1.2 Flags 0x03 (Driver 
version 1.16ac)
Aug 31 15:05:38 Casa kernel: apm: disabled - APM is not SMP safe.
Aug 31 15:05:38 Casa kernel: audit: initializing netlink socket (disabled)
Aug 31 15:05:38 Casa kernel: audit(1125500686.707:1): initialized
Aug 31 15:05:38 Casa kernel: highmem bounce pool size: 64 pages
Aug 31 15:05:38 Casa kernel: Total HugeTLB memory allocated, 0
Aug 31 15:05:38 Casa kernel: VFS: Disk quotas dquot_6.5.1
Aug 31 15:05:38 Casa kernel: Dquot-cache hash table entries: 1024 (order 
0, 4096 bytes)
Aug 31 15:05:38 Casa kernel: SELinux:  Registering netfilter hooks
Aug 31 15:05:38 Casa kernel: Initializing Cryptographic API
Aug 31 15:05:38 Casa kernel: ksign: Installing public key data
Aug 31 15:05:38 Casa kernel: Loading keyring
Aug 31 15:05:38 Casa kernel: - Added public key 1C1942C715575330
Aug 31 15:05:38 Casa kernel: - User ID: Red Hat, Inc. (Kernel Module GPG 
key)
Aug 31 15:05:38 Casa kernel: pci_hotplug: PCI Hot Plug PCI Core version: 0.5
Aug 31 15:05:38 Casa kernel: isapnp: Scanning for PnP cards...
Aug 31 15:05:38 Casa kernel: isapnp: No Plug & Play device found
Aug 31 15:05:38 Casa kernel: Real Time Clock Driver v1.12
Aug 31 15:05:38 Casa kernel: Linux agpgart interface v0.101 (c) Dave Jones
Aug 31 15:05:38 Casa kernel: agpgart: Detected an Intel 865 Chipset.
Aug 31 15:05:38 Casa kernel: agpgart: AGP aperture is 64M @ 0xdc000000
Aug 31 15:05:38 Casa kernel: PNP: No PS/2 controller found. Probing 
ports directly.
Aug 31 15:05:38 Casa kernel: serio: i8042 AUX port at 0x60,0x64 irq 12
Aug 31 15:05:38 Casa kernel: serio: i8042 KBD port at 0x60,0x64 irq 1
Aug 31 15:05:38 Casa kernel: Serial: 8250/16550 driver $Revision: 1.90 $ 
76 ports, IRQ sharing enabled
Aug 31 15:05:38 Casa kernel: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
Aug 31 15:05:38 Casa kernel: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
Aug 31 15:05:38 Casa kernel: io scheduler noop registered
Aug 31 15:05:38 Casa kernel: io scheduler anticipatory registered
Aug 31 15:05:38 Casa kernel: io scheduler deadline registered
Aug 31 15:05:38 Casa kernel: io scheduler cfq registered
Aug 31 15:05:38 Casa kernel: RAMDISK driver initialized: 16 RAM disks of 
16384K size 1024 blocksize
Aug 31 15:05:38 Casa kernel: Uniform Multi-Platform E-IDE driver 
Revision: 7.00alpha2
Aug 31 15:05:38 Casa kernel: ide: Assuming 33MHz system bus speed for 
PIO modes; override with idebus=xx
Aug 31 15:05:38 Casa kernel: ICH5: IDE controller at PCI slot 0000:00:1f.1
Aug 31 15:05:38 Casa kernel: PCI: Enabling device 0000:00:1f.1 (0005 -> 
0007)
Aug 31 15:05:38 Casa kernel: ICH5: chipset revision 2
Aug 31 15:05:38 Casa kernel: ICH5: not 100% native mode: will probe irqs 
later
Aug 31 15:05:38 Casa kernel:     ide0: BM-DMA at 0xfc00-0xfc07, BIOS 
settings: hda:DMA, hdb:pio
Aug 31 15:05:38 Casa kernel:     ide1: BM-DMA at 0xfc08-0xfc0f, BIOS 
settings: hdc:DMA, hdd:DMA
Aug 31 15:05:38 Casa kernel: hda: Maxtor 6L200P0, ATA DISK drive
Aug 31 15:05:38 Casa kernel: ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
Aug 31 15:05:38 Casa kernel: hdc: HL-DT-ST DVDRAM GSA-4163B, ATAPI 
CD/DVD-ROM drive
Aug 31 15:05:38 Casa kernel: hdd: Hewlett-Packard CD-Writer Plus 7500, 
ATAPI CD/DVD-ROM drive
Aug 31 15:05:38 Casa kernel: ide1 at 0x170-0x177,0x376 on irq 15
Aug 31 15:05:38 Casa kernel: hda: max request size: 1024KiB
Aug 31 15:05:38 Casa kernel: hda: 398297088 sectors (203928 MB) 
w/8192KiB Cache, CHS=24792/255/63, UDMA(100)
Aug 31 15:05:38 Casa kernel: hda: cache flushes supported
Aug 31 15:05:38 Casa kernel:  hda: hda1 hda2
Aug 31 15:05:38 Casa kernel: hdc: ATAPI 40X DVD-ROM DVD-R-RAM CD-R/RW 
drive, 2048kB Cache, UDMA(33)
Aug 31 15:05:38 Casa kernel: Uniform CD-ROM driver Revision: 3.20
Aug 31 15:05:38 Casa kernel: hdd: ATAPI 24X CD-ROM CD-R/RW drive, 1024kB 
Cache, DMA
Aug 31 15:05:38 Casa kernel: ide-floppy driver 0.99.newide
Aug 31 15:05:38 Casa kernel: usbcore: registered new driver hiddev
Aug 31 15:05:38 Casa kernel: usbcore: registered new driver usbhid
Aug 31 15:05:38 Casa kernel: drivers/usb/input/hid-core.c: v2.01:USB HID 
core driver
Aug 31 15:05:38 Casa kernel: mice: PS/2 mouse device common for all mice
Aug 31 15:05:38 Casa kernel: md: md driver 0.90.1 MAX_MD_DEVS=256, 
MD_SB_DISKS=27
Aug 31 15:05:38 Casa kernel: NET: Registered protocol family 2
Aug 31 15:05:38 Casa kernel: IP: routing cache hash table of 4096 
buckets, 64Kbytes
Aug 31 15:05:38 Casa kernel: TCP established hash table entries: 262144 
(order: 10, 4194304 bytes)
Aug 31 15:05:38 Casa kernel: TCP bind hash table entries: 65536 (order: 
7, 786432 bytes)
Aug 31 15:05:38 Casa kernel: TCP: Hash tables configured (established 
262144 bind 65536)
Aug 31 15:05:38 Casa kernel: Initializing IPsec netlink socket
Aug 31 15:05:38 Casa kernel: NET: Registered protocol family 1
Aug 31 15:05:38 Casa kernel: NET: Registered protocol family 17
Aug 31 15:05:38 Casa kernel: Freeing unused kernel memory: 236k freed
Aug 31 15:05:38 Casa kernel: input: AT Translated Set 2 keyboard on 
isa0060/serio0
Aug 31 15:05:38 Casa kernel: device-mapper: 4.4.0-ioctl (2005-01-12) 
initialised: [e-mail]
Aug 31 15:05:38 Casa kernel: input: ImPS/2 Generic Wheel Mouse on 
isa0060/serio1
Aug 31 15:05:38 Casa kernel: kjournald starting.  Commit interval 5 seconds
Aug 31 15:05:38 Casa kernel: EXT3-fs: mounted filesystem with ordered 
data mode.
Aug 31 15:05:38 Casa kernel: SELinux:  Disabled at runtime.
Aug 31 15:05:38 Casa kernel: SELinux:  Unregistering netfilter hooks
Aug 31 15:05:38 Casa kernel: Floppy drive(s): fd0 is 1.44M
Aug 31 15:05:38 Casa kernel: FDC 0 is a post-1991 82077
Aug 31 15:05:38 Casa kernel: ne2k-pci.c:v1.03 9/22/2003 D. Becker/P. 
Gortmaker
Aug 31 15:05:38 Casa kernel:   http://www.scyld.com/network/ne2k-pci.html
Aug 31 15:05:38 Casa kernel: eth0: RealTek RTL-8029 found at 0xec00, IRQ 
201, 52:54:05:E5:82:46.
Aug 31 15:05:38 Casa kernel: eth1: Yukon Gigabit Ethernet 
10/100/1000Base-T Adapter
Aug 31 15:05:38 Casa kernel:       PrefPort:A  RlmtMode:Check Link State
Aug 31 15:05:39 Casa kernel: AC'97 0 analog subsections not ready
Aug 31 15:05:39 Casa kernel: intel8x0_measure_ac97_clock: measured 50014 
usecs
Aug 31 15:05:39 Casa kernel: intel8x0: clocking to 48000
Aug 31 15:05:39 Casa kernel: hw_random hardware driver 1.0.0 loaded
Aug 31 15:05:39 Casa kernel: shpchp: acpi_shpchprm:get_device PCI ROOT 
HID fail=0x1001
Aug 31 15:05:39 Casa kernel: ehci_hcd 0000:00:1d.7: EHCI Host Controller
Aug 31 15:05:39 Casa kernel: ehci_hcd 0000:00:1d.7: debug port 1
Aug 31 15:05:39 Casa kernel: ehci_hcd 0000:00:1d.7: new USB bus 
registered, assigned bus number 1
Aug 31 15:05:39 Casa kernel: ehci_hcd 0000:00:1d.7: irq 225, io mem 
0xf9fffc00
Aug 31 15:05:39 Casa kernel: ehci_hcd 0000:00:1d.7: USB 2.0 initialized, 
EHCI 1.00, driver 10 Dec 2004
Aug 31 15:05:39 Casa kernel: hub 1-0:1.0: USB hub found
Aug 31 15:05:39 Casa kernel: hub 1-0:1.0: 8 ports detected
Aug 31 15:05:39 Casa kernel: USB Universal Host Controller Interface 
driver v2.2
Aug 31 15:05:39 Casa kernel: uhci_hcd 0000:00:1d.0: UHCI Host Controller
Aug 31 15:05:39 Casa kernel: uhci_hcd 0000:00:1d.0: new USB bus 
registered, assigned bus number 2
Aug 31 15:05:39 Casa kernel: uhci_hcd 0000:00:1d.0: irq 169, io base 
0x0000c480
Aug 31 15:05:39 Casa kernel: hub 2-0:1.0: USB hub found
Aug 31 15:05:39 Casa kernel: hub 2-0:1.0: 2 ports detected
Aug 31 15:05:39 Casa kernel: uhci_hcd 0000:00:1d.1: UHCI Host Controller
Aug 31 15:05:39 Casa kernel: uhci_hcd 0000:00:1d.1: new USB bus 
registered, assigned bus number 3
Aug 31 15:05:39 Casa kernel: uhci_hcd 0000:00:1d.1: irq 193, io base 
0x0000c800
Aug 31 15:05:39 Casa kernel: hub 3-0:1.0: USB hub found
Aug 31 15:05:39 Casa kernel: hub 3-0:1.0: 2 ports detected
Aug 31 15:05:39 Casa kernel: uhci_hcd 0000:00:1d.2: UHCI Host Controller
Aug 31 15:05:39 Casa kernel: uhci_hcd 0000:00:1d.2: new USB bus 
registered, assigned bus number 4
Aug 31 15:05:39 Casa kernel: uhci_hcd 0000:00:1d.2: irq 185, io base 
0x0000c880
Aug 31 15:05:39 Casa kernel: hub 4-0:1.0: USB hub found
Aug 31 15:05:39 Casa kernel: hub 4-0:1.0: 2 ports detected
Aug 31 15:05:39 Casa kernel: uhci_hcd 0000:00:1d.3: UHCI Host Controller
Aug 31 15:05:39 Casa kernel: uhci_hcd 0000:00:1d.3: new USB bus 
registered, assigned bus number 5
Aug 31 15:05:39 Casa kernel: uhci_hcd 0000:00:1d.3: irq 169, io base 
0x0000cc00
Aug 31 15:05:39 Casa kernel: hub 5-0:1.0: USB hub found
Aug 31 15:05:39 Casa kernel: hub 5-0:1.0: 2 ports detected
Aug 31 15:05:39 Casa kernel: usb 3-2: new full speed USB device using 
uhci_hcd and address 2
Aug 31 15:05:39 Casa kernel: NET: Registered protocol family 10
Aug 31 15:05:39 Casa kernel: Disabled Privacy Extensions on device 
c037e860(lo)
Aug 31 15:05:39 Casa kernel: IPv6 over IPv4 tunneling driver
Aug 31 15:05:39 Casa kernel: md: Autodetecting RAID arrays.
Aug 31 15:05:39 Casa kernel: md: autorun ...
Aug 31 15:05:39 Casa kernel: md: ... autorun DONE.
Aug 31 15:05:39 Casa kernel: EXT3 FS on dm-0, internal journal
Aug 31 15:05:39 Casa kernel: kjournald starting.  Commit interval 5 seconds
Aug 31 15:05:39 Casa kernel: EXT3 FS on hda1, internal journal
Aug 31 15:05:39 Casa kernel: EXT3-fs: mounted filesystem with ordered 
data mode.
Aug 31 15:05:39 Casa kernel: Adding 2031608k swap on 
/dev/VolGroup00/LogVol01.  Priority:-1 extents:1
Aug 31 15:05:39 Casa kernel: CSLIP: code copyright 1989 Regents of the 
University of California
Aug 31 15:05:39 Casa kernel: ISDN subsystem Rev: 
1.1.2.3/1.1.2.3/1.1.2.2/1.1.2.3/1.1.2.2/1.1.2.2 loaded
Aug 31 15:05:39 Casa kernel: HiSax: Linux Driver for passive ISDN cards
Aug 31 15:05:39 Casa kernel: HiSax: Version 3.5 (module)
Aug 31 15:05:39 Casa kernel: HiSax: Layer1 Revision 2.46.2.5
Aug 31 15:05:39 Casa kernel: HiSax: Layer2 Revision 2.30.2.4
Aug 31 15:05:39 Casa kernel: HiSax: TeiMgr Revision 2.20.2.3
Aug 31 15:05:39 Casa kernel: HiSax: Layer3 Revision 2.22.2.3
Aug 31 15:05:39 Casa kernel: HiSax: LinkLayer Revision 2.59.2.4
Aug 31 15:05:39 Casa kernel: HiSax module removed
Aug 31 15:05:39 Casa kernel: ISDN-subsystem unloaded
Aug 31 15:05:39 Casa kernel: ip_tables: (C) 2000-2002 Netfilter core team
Aug 31 15:05:39 Casa kernel: ip_conntrack version 2.1 (8189 buckets, 
65512 max) - 256 bytes per conntrack
Aug 31 15:05:39 Casa kernel: eth1: network connection up using port A
Aug 31 15:05:39 Casa kernel:     speed:           100
Aug 31 15:05:39 Casa kernel:     autonegotiation: yes
Aug 31 15:05:39 Casa kernel:     duplex mode:     full
Aug 31 15:05:39 Casa kernel:     flowctrl:        symmetric
Aug 31 15:05:39 Casa kernel:     irq moderation:  disabled
Aug 31 15:05:39 Casa kernel:     scatter-gather:  enabled
Aug 31 15:05:39 Casa kernel: CSLIP: code copyright 1989 Regents of the 
University of California
Aug 31 15:05:39 Casa kernel: PPP generic driver version 2.4.2
Aug 31 15:05:39 Casa kernel: i2c /dev entries driver
Aug 31 15:05:40 Casa smartd[2298]: smartd version 5.33 
[i386-redhat-linux-gnu] Copyright (C) 2002-4 Bruce Allen
Aug 31 15:05:40 Casa smartd[2298]: Home page is 
http://smartmontools.sourceforge.net/
Aug 31 15:05:40 Casa smartd[2298]: Opened configuration file 
/etc/smartd.conf
Aug 31 15:05:40 Casa smartd[2298]: Configuration file /etc/smartd.conf 
parsed.
Aug 31 15:05:40 Casa smartd[2298]: Device: /dev/hda, opened
Aug 31 15:05:40 Casa smartd[2298]: Device: /dev/hda, not found in smartd 
database.
Aug 31 15:05:41 Casa smartd[2298]: Device: /dev/hda, is SMART capable. 
Adding to "monitor" list.
Aug 31 15:05:41 Casa smartd[2298]: Monitoring 1 ATA and 0 SCSI devices
Aug 31 15:05:41 Casa smartd[2300]: smartd has fork()ed into background 
mode. New PID=2300.
Aug 31 15:05:43 Casa kernel: parport0: PC-style at 0x378 (0x778) 
[PCSPP,TRISTATE,EPP]
Aug 31 15:05:43 Casa kernel: parport0: irq 7 detected
Aug 31 15:05:43 Casa kernel: lp0: using parport0 (polling).
Aug 31 15:05:43 Casa kernel: lp0: console ready
Aug 31 15:05:44 Casa ntpd[2372]: ntpd 4.2.0a@1.1190-r Thu Apr 14 
07:47:25 EDT 2005 (1)
Aug 31 15:05:45 Casa xinetd[2361]: xinetd Version 2.3.13 started with 
libwrap loadavg options compiled in.
Aug 31 15:05:45 Casa xinetd[2361]: Started working: 1 available service
Aug 31 15:05:45 Casa ntpd[2372]: precision = 3.000 usec
Aug 31 15:05:45 Casa ntpd[2372]: Listening on interface wildcard, 
0.0.0.0#123
Aug 31 15:05:45 Casa ntpd[2372]: Listening on interface wildcard, ::#123
Aug 31 15:05:45 Casa ntpd[2372]: Listening on interface lo, 127.0.0.1#123
Aug 31 15:05:45 Casa ntpd[2372]: Listening on interface eth0, 
192.168.254.1#123
Aug 31 15:05:45 Casa ntpd[2372]: Listening on interface eth1, 
192.168.0.1#123
Aug 31 15:05:45 Casa ntpd[2372]: Listening on interface ppp0, 
80.117.47.95#123
Aug 31 15:05:45 Casa ntpd[2372]: kernel time sync status 0040
Aug 31 15:05:47 Casa kernel: Installing knfsd (copyright (C) 1996 
[e-mail]).
Aug 31 15:05:48 Casa rpc.idmapd: nfsdreopen: Opening '' failed: errno 2 
(No such file or directory)
Aug 31 15:05:48 Casa gpm[2487]: *** info [startup.c(95)]:
Aug 31 15:05:48 Casa gpm[2487]: Started gpm successfully. Entered daemon 
mode.
Aug 31 15:05:48 Casa gpm[2487]: *** info [mice.c(1766)]:
Aug 31 15:05:48 Casa gpm[2487]: imps2: Auto-detected intellimouse PS/2
Aug 31 15:05:49 Casa squid[2507]: Squid Parent: child process 2509 started
Aug 31 15:05:50 Casa ntpd[2372]: frequency initialized 74.522 PPM from 
/var/lib/ntp/drift
Aug 31 15:05:54 Casa fstab-sync[2602]: removed all generated mount points
Aug 31 15:05:55 Casa fstab-sync[2609]: added mount point /media/floppy2 
for /dev/fd0
Aug 31 15:05:55 Casa fstab-sync[2612]: added mount point 
/media/cdrecorder for /dev/hdd
Aug 31 15:05:55 Casa fstab-sync[2616]: added mount point 
/media/cdrecorder1 for /dev/hdc
Aug 31 15:05:57 Casa webmin(pam_unix)[2629]: authentication failure; 
logname= uid=0 euid=0 tty= ruser= rhost=  user=root
Aug 31 15:06:13 Casa gdm(pam_unix)[2851]: session opened for user 
antonio by (uid=0)
Aug 31 15:06:14 Casa gconfd (antonio-2951): Inizializzazione (versione 
2.10.0), pid 2951, utente 'antonio'
Aug 31 15:06:14 Casa gconfd (antonio-2951): L'indirizzo 
"xml:readonly:/etc/gconf/gconf.xml.mandatory" Ú stato risolta ad una 
fonte di configurazione in sola lettura in posizione 0
Aug 31 15:06:14 Casa gconfd (antonio-2951): L'indirizzo 
"xml:readwrite:/home/antonio/.gconf" Ú stato risolto ad una fonte di 
configurazione scrivibile in posizione 1
Aug 31 15:06:14 Casa gconfd (antonio-2951): L'indirizzo 
"xml:readonly:/etc/gconf/gconf.xml.defaults" Ú stato risolta ad una 
fonte di configurazione in sola lettura in posizione 2
Aug 31 15:06:17 Casa gconfd (antonio-2951): L'indirizzo 
"xml:readwrite:/home/antonio/.gconf" Ú stato risolto ad una fonte di 
configurazione scrivibile in posizione 0
Aug 31 15:08:07 Casa gconfd (antonio-2951): Uscita
Aug 31 15:08:08 Casa gdm(pam_unix)[2851]: session closed for user antonio
Aug 31 15:08:14 Casa gdm(pam_unix)[2851]: session opened for user root 
by (uid=0)
Aug 31 15:08:14 Casa gconfd (root-3203): Inizializzazione (versione 
2.10.0), pid 3203, utente 'root'
Aug 31 15:08:14 Casa gconfd (root-3203): L'indirizzo 
"xml:readonly:/etc/gconf/gconf.xml.mandatory" Ú stato risolta ad una 
fonte di configurazione in sola lettura in posizione 0
Aug 31 15:08:14 Casa gconfd (root-3203): L'indirizzo 
"xml:readwrite:/root/.gconf" Ú stato risolto ad una fonte di 
configurazione scrivibile in posizione 1
Aug 31 15:08:14 Casa gconfd (root-3203): L'indirizzo 
"xml:readonly:/etc/gconf/gconf.xml.defaults" Ú stato risolta ad una 
fonte di configurazione in sola lettura in posizione 2
Aug 31 15:08:15 Casa gconfd (root-3203): L'indirizzo 
"xml:readwrite:/root/.gconf" Ú stato risolto ad una fonte di 
configurazione scrivibile in posizione 0
> Bob...

NO ADSL with kernel-smp 2.6.12-1.1376_FC3

[Antonio Montagnani]

Bob Chiodini said the following on 31/08/2005 14:18:
> > > > > Anything relevant in /var/log/messages?  What is the output of route -n?
> > > > >
> > > > > Bob...
> > > >
> > > > I had a look at /var/log/messages (that I attach, only as e-mail to 
> > > > you...), but I am not very expert.
> > > > I see a timeout transmit on eth0 repeated many times when using SMP 
> > > > kernel at about 6.35 at the end.
> > > > I see also many errors conencted to ACPI (on both kernels) that I am not 
> > > > able to decode
> > > >
> > > > Tnx
> > >
> > > Antonio,
> > >
> > > I culled the messages down into a SMP boot and a UP boot.  A quick look
> > > indicates one message is missing in the SMP boot log.  It's marked with
> > > an arrow and indicates that the eth0 device interrupt was detected as
> > > IRQ 11 (UP only).  Hopefully someone can shed some light on this.  Some
> > > other information that might help:
> > >
> > > cat /proc/interrupts for both the UP and SMP.
> > >
> > > Also, do you have the latest BIOS installed for your motherboard?  What
> > > kind of motherboard is this?
> >
> > An Asus P5P800, Bios updated in July
> >
> > Check the IO-APIC options in the BIOS
> > > setup.
> > >
> > > You might try moving the realtek NIC to another slot.  That's a shot in
> > > the dark, but it's pretty early and I'm only into my first cup of
> > > coffee!
> > >
> > > Bob...
> >
> > Standard
> >       CPU0
> >   0:   20180445          XT-PIC  timer
> >   1:       5563          XT-PIC  i8042
> >   2:          0          XT-PIC  cascade
> >   5:     701131          XT-PIC  SysKonnect SK-98xx, Intel ICH5, 
> > ehci_hcd:usb1, uhci_hcd:usb3
> >   8:          1          XT-PIC  rtc
> >  11:     380784          XT-PIC  uhci_hcd:usb2, uhci_hcd:usb4, 
> > uhci_hcd:usb5, eth0
> >  12:     801086          XT-PIC  i8042
> >  14:     112972          XT-PIC  ide0
> >  15:     358109          XT-PIC  ide1
> > NMI:          0
> > ERR:          0
> >
> > SMP
> >        CPU0       CPU1
> >   0:     137004      48896    IO-APIC-edge  timer
> >   1:         29         27    IO-APIC-edge  i8042
> >   5:          0          0    IO-APIC-edge  SysKonnect SK-98xx, Intel 
> > ICH5, ehci _hcd:usb1, uhci_hcd:usb3
> >   8:          1          0    IO-APIC-edge  rtc
> >  11:          0          0    IO-APIC-edge  uhci_hcd:usb2, 
> > uhci_hcd:usb4, uhci_h cd:usb5, eth0
> >  12:       1146        836    IO-APIC-edge  i8042
> >  14:       9294       5957    IO-APIC-edge  ide0
> >  15:        440        568    IO-APIC-edge  ide1
> > NMI:          0          0
> > LOC:     181971     182055
> > ERR:          0
> > MIS:          0
> >
> > I am wondering if the two kernels have different management of iptables, 
> > in particular IPv4 or IPv6, another shot in the dark, even if is 
> > afternoon here
> >
> > tnx
>
> Antonio,
>
> service iptables stop.  I suspect that the IRQ for eth0 is not getting
> properly registered and thus the timeouts.
>
> Does specifying acpi=ht on the SMP kernel command line make any
> difference?  It probably defeats the purpose of SMP.
>
> Bob...

and furthermore prevents from poweroff .... :-(

NO ADSL with kernel-smp 2.6.12-1.1376_FC3

[James Wilkinson]

Antonio Montagnani wrote:
> Does specifying acpi=ht on the SMP kernel command line make any
> difference?  It probably defeats the purpose of SMP.

and:
> and furthermore prevents from poweroff .... :-(

Shouldn't do. In general, one doesn't need ACPI for SMP.

You probably don't, either. You can check /proc/cpuinfo: it should show
two CPUs if you've got SMP working.

acpi=ht turns ACPI off for most things, but keeps enough to enable
hyperthreading. It sounds like there's a bug somewhere in ACPI (probably
in your motherboard support).

Stupid idea: I forget whether your Ethenet card is built-in or a
physical card. If it's physically separate, try it in different PCI
slots. That should get it different PCI level IRQs: the ACPI IRQ routing
might work for a different PCI IRQ.

As for the poweroff, you need APM or ACPI for this to work. APM doesn't
work in SMP mode (there's a line in the kernel messages you posted
saying as much), and you've just turned off ACPI for nearly everything.

You will probably have turned off hibernation support and *possibly*
some power-saving support when you disabled ACPI. Otherwise, you really
don't need it unless you've got *really* unusual kit.[1]

James.
[1] I think some Itanium servers rely on it...

NO ADSL with kernel-smp 2.6.12-1.1376_FC3

[Antonio Montagnani]

James Wilkinson said the following on 31/08/2005 18:49:
> Antonio Montagnani wrote:
> > Does specifying acpi=ht on the SMP kernel command line make any
> > difference?  It probably defeats the purpose of SMP.
>
> and:
> > and furthermore prevents from poweroff .... :-(
>
> Shouldn't do. In general, one doesn't need ACPI for SMP.
>
> You probably don't, either. You can check /proc/cpuinfo: it should show
> two CPUs if you've got SMP working.
>
> acpi=ht turns ACPI off for most things, but keeps enough to enable
> hyperthreading. It sounds like there's a bug somewhere in ACPI (probably
> in your motherboard support).

I agree, I have seen many warnings saying that can't load ACPI table, 
etc, etc, untill I put acpi=ht, and same errors are also on standar 
kernel (pls. have a look to the part of /var/log/messages already posted)
> Stupid idea: I forget whether your Ethenet card is built-in or a
> physical card. If it's physically separate, try it in different PCI
> slots. That should get it different PCI level IRQs: the ACPI IRQ routing
> might work for a different PCI IRQ.

It is a separate card, I will switch to a different slot, when I have 
some spare time, but this should not remove all warning/errors about 
ACPI, should it?
> As for the poweroff, you need APM or ACPI for this to work. APM doesn't
> work in SMP mode (there's a line in the kernel messages you posted
> saying as much), and you've just turned off ACPI for nearly everything.
>
> You will probably have turned off hibernation support and *possibly*
> some power-saving support when you disabled ACPI.

no idea how I could have disabled any flag to disable poweroff, any 
suggestion?
  Otherwise, you really
> don't need it unless you've got *really* unusual kit.[1]
>
> James.
> [1] I think some Itanium servers rely on it...

You need ACPI or APM for soft power-down.

[James Wilkinson]

I wrote:
> As for the poweroff, you need APM or ACPI for this to work. APM doesn't
> work in SMP mode (there's a line in the kernel messages you posted
> saying as much), and you've just turned off ACPI for nearly everything.
>
> You will probably have turned off hibernation support and *possibly*
> some power-saving support when you disabled ACPI.

Antonio Montagnani wrote:
> no idea how I could have disabled any flag to disable poweroff, any 
> suggestion?

Um. Let me try again.

Soft power-down isn't a standard part of a PC. Linux doesn't know how to
do it without APM or ACPI.

APM is out the question on SMP, due to the way it's designed.

So you need ACPI properly working for soft power-down.

You've added acpi=ht to the kernel boot flags.

This is defined as "ht -- run only enough ACPI to enable Hyper
Threading" (in /usr/src/linux/Documentation/kernel-parameters.txt). In
other words -- not enough to do soft power-down.

James.

You need ACPI or APM for soft power-down.

[Antonio Montagnani]

James Wilkinson said the following on 01/09/2005 02:41:
> I wrote:
> > As for the poweroff, you need APM or ACPI for this to work. APM doesn't
> > work in SMP mode (there's a line in the kernel messages you posted
> > saying as much), and you've just turned off ACPI for nearly everything.
> >
> > You will probably have turned off hibernation support and *possibly*
> > some power-saving support when you disabled ACPI.
>
> Antonio Montagnani wrote:
> > no idea how I could have disabled any flag to disable poweroff, any 
> > suggestion?
>
> Um. Let me try again.
>
> Soft power-down isn't a standard part of a PC. Linux doesn't know how to
> do it without APM or ACPI.
>
> APM is out the question on SMP, due to the way it's designed.
>
> So you need ACPI properly working for soft power-down.
>
> You've added acpi=ht to the kernel boot flags.
>
> This is defined as "ht -- run only enough ACPI to enable Hyper
> Threading" (in /usr/src/linux/Documentation/kernel-parameters.txt). In
> other words -- not enough to do soft power-down.
>
> James.

Tnx James

I have moved the additional card to another PCI slot, but behaviour is 
similar with same warnings/errors at start-up in var/log/messages and dmesg

I made also a trial stopping iptables and trying to connect with the SMP 
kernel (and no acpi=ht option) but no connection established.

Now I have the following options:

1) use the standard kernel
2) use the SMP kernel with no internet connection (!!!!!)
3) use the SMP kernel with acpi=ht option at boot-time but no soft power-off

Of course option 2 is out of discussion

Shall I file a bug???