Linux-2.4.22

Linux-2.4.22

[Richard B. Johnson]

[-- Attachment #1: Type: TEXT/PLAIN, Size: 2037 bytes --]


I configured, built and booted Linux-2.4.22. There are
some problems.

(1) `dmesg` fails to read the first part of the buffered
kernel log. I have attached two files, dmesg-20 (normal)
and dmesg-22 (bad). File dmesg-22 is from Linux-2.4.22
and dmesg-20 is from Linux-2.4.20. To save space, I
snip everything after 'NET4'.

(2)  The ipx module fails to load with undefined symbols.
This module loads fine in Linux-2.4.20.

depmod: *** Unresolved symbols in /lib/modules/2.4.22/kernel/net/ipx/ipx.o
depmod: 	unregister_8022_client
depmod: 	make_EII_client
depmod: 	register_8022_client
depmod: 	register_snap_client
depmod: 	make_8023_client
depmod: 	destroy_8023_client
depmod: 	destroy_EII_client
depmod: 	unregister_snap_client

(3)  When umounting the root file-system, the machine usually
hangs. The result is a long `fsck` on the next boot. The problem
seems to be that sendmail doesn't get killed during the `init 0`
sequence. It remains with a file open and the root file-system isn't
unmounted. A temporary work-round is to `ifconfig eth0 down` before
starting shutdown. Otherwise, sendmail remains stuck in the 'D' state.

(4)  When mounting the DOS file-systems during startup, the echo
on the screen shows about 15 lines of white-space. This never
happened before. When mounting /proc, there are 6 lines of
white-space, also strange.
#
# /etc/fstab
#
# device			directory	type	options	freq pass
# -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
/dev/sdb1			/		ext2	rw,noatime  0   1
/dev/sdc1			/alt		ext2	rw,noatime  0   2
/dev/sdb2			none		swap	defaults    0	2
/dev/sdc2			none		swap	defaults    0	2
/dev/sdc3			/home/users	ext2	rw,noatime  0	2
none				/proc		proc	defaults  0	2
/dev/sda1			/dos/drive_C	msdos	defaults  0     2
/dev/sda5			/dos/drive_D	msdos	defaults  0     2


Otherwise it works. I am using it now so I can test any possible
fixes.

Cheers,
Dick Johnson
Penguin : Linux version 2.4.22 on an i686 machine (797.90 BogoMips).
            Note 96.31% of all statistics are fiction.


[-- Attachment #2: Type: TEXT/PLAIN, Size: 4144 bytes --]

>Page-cache hash table entries: 131072 (order: 7, 524288 bytes)
CPU: L1 I cache: 16K, L1 D cache: 16K
CPU: L2 cache: 512K
CPU:     After generic, caps: 0183fbff 00000000 00000000 00000000
CPU:             Common caps: 0183fbff 00000000 00000000 00000000
Enabling fast FPU save and restore... done.
Checking 'hlt' instruction... OK.
POSIX conformance testing by UNIFIX
CPU: L1 I cache: 16K, L1 D cache: 16K
CPU: L2 cache: 512K
CPU:     After generic, caps: 0183fbff 00000000 00000000 00000000
CPU:             Common caps: 0183fbff 00000000 00000000 00000000
CPU0: Intel Pentium II (Deschutes) stepping 01
per-CPU timeslice cutoff: 1464.17 usecs.
enabled ExtINT on CPU#0
ESR value before enabling vector: 00000000
ESR value after enabling vector: 00000000
Booting processor 1/0 eip 2000
Initializing CPU#1
masked ExtINT on CPU#1
ESR value before enabling vector: 00000000
ESR value after enabling vector: 00000000
Calibrating delay loop... 797.14 BogoMIPS
CPU: L1 I cache: 16K, L1 D cache: 16K
CPU: L2 cache: 512K
CPU:     After generic, caps: 0183fbff 00000000 00000000 00000000
CPU:             Common caps: 0183fbff 00000000 00000000 00000000
CPU1: Intel Pentium II (Deschutes) stepping 01
Total of 2 processors activated (1592.88 BogoMIPS).
ENABLING IO-APIC IRQs
Setting 2 in the phys_id_present_map
...changing IO-APIC physical APIC ID to 2 ... ok.
init IO_APIC IRQs
 IO-APIC (apicid-pin) 2-0, 2-10, 2-11, 2-12, 2-13, 2-15, 2-20, 2-21, 2-22, 2-23 not connected.
..TIMER: vector=0x31 pin1=2 pin2=0
number of MP IRQ sources: 15.
number of IO-APIC #2 registers: 24.
testing the IO APIC.......................

IO APIC #2......
.... register #00: 02000000
.......    : physical APIC id: 02
.... register #01: 00170011
.......     : max redirection entries: 0017
.......     : PRQ implemented: 0
.......     : IO APIC version: 0011
.... register #02: 00000000
.......     : arbitration: 00
.... IRQ redirection table:
 NR Log Phy Mask Trig IRR Pol Stat Dest Deli Vect:   
 00 000 00  1    0    0   0   0    0    0    00
 01 003 03  0    0    0   0   0    1    1    39
 02 003 03  0    0    0   0   0    1    1    31
 03 003 03  0    0    0   0   0    1    1    41
 04 003 03  0    0    0   0   0    1    1    49
 05 003 03  0    0    0   0   0    1    1    51
 06 003 03  0    0    0   0   0    1    1    59
 07 003 03  0    0    0   0   0    1    1    61
 08 003 03  0    0    0   0   0    1    1    69
 09 003 03  0    0    0   0   0    1    1    71
 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 003 03  0    0    0   0   0    1    1    79
 0f 000 00  1    0    0   0   0    0    0    00
 10 003 03  1    1    0   1   0    1    1    81
 11 003 03  1    1    0   1   0    1    1    89
 12 003 03  1    1    0   1   0    1    1    91
 13 003 03  1    1    0   1   0    1    1    99
 14 000 00  1    0    0   0   0    0    0    00
 15 000 00  1    0    0   0   0    0    0    00
 16 000 00  1    0    0   0   0    0    0    00
 17 000 00  1    0    0   0   0    0    0    00
IRQ to pin mappings:
IRQ0 -> 0:2
IRQ1 -> 0:1
IRQ3 -> 0:3
IRQ4 -> 0:4
IRQ5 -> 0:5
IRQ6 -> 0:6
IRQ7 -> 0:7
IRQ8 -> 0:8
IRQ9 -> 0:9
IRQ10 -> 0:17
IRQ11 -> 0:16
IRQ12 -> 0:18
IRQ14 -> 0:14
IRQ15 -> 0:19
.................................... done.
Using local APIC timer interrupts.
calibrating APIC timer ...
..... CPU clock speed is 399.1381 MHz.
..... host bus clock speed is 99.2219 MHz.
cpu: 0, clocks: 249719, slice: 83239
CPU0<T0:249712,T1:166464,D:9,S:83239,C:249719>
cpu: 1, clocks: 249719, slice: 83239
CPU1<T0:249712,T1:83232,D:2,S:83239,C:249719>
checking TSC synchronization across CPUs: passed.
Waiting on wait_init_idle (map = 0x2)
All processors have done init_idle
PCI: PCI BIOS revision 2.10 entry at 0xf0750, last bus=1
PCI: Using configuration type 1
PCI: Probing PCI hardware
PCI: Using IRQ router PIIX [8086/7110] at 00:04.0
Limiting direct PCI/PCI transfers.
Linux NET4.0 for Linux 2.4
[SNIPPED]

[-- Attachment #3: Type: TEXT/PLAIN, Size: 3595 bytes --]

s.
enabled ExtINT on CPU#0
ESR value before enabling vector: 00000000
ESR value after enabling vector: 00000000
Booting processor 1/0 eip 2000
Initializing CPU#1
masked ExtINT on CPU#1
ESR value before enabling vector: 00000000
ESR value after enabling vector: 00000000
Calibrating delay loop... 797.90 BogoMIPS
CPU: L1 I cache: 16K, L1 D cache: 16K
CPU: L2 cache: 512K
CPU:     After generic, caps: 0183fbff 00000000 00000000 00000000
CPU:             Common caps: 0183fbff 00000000 00000000 00000000
CPU1: Intel Pentium II (Deschutes) stepping 01
Total of 2 processors activated (1595.80 BogoMIPS).
ENABLING IO-APIC IRQs
Setting 2 in the phys_id_present_map
...changing IO-APIC physical APIC ID to 2 ... ok.
init IO_APIC IRQs
 IO-APIC (apicid-pin) 2-0, 2-10, 2-11, 2-12, 2-13, 2-15, 2-20, 2-21, 2-22, 2-23 not connected.
..TIMER: vector=0x31 pin1=2 pin2=0
number of MP IRQ sources: 15.
number of IO-APIC #2 registers: 24.
testing the IO APIC.......................

IO APIC #2......
.... register #00: 02000000
.......    : physical APIC id: 02
.......    : Delivery Type: 0
.......    : LTS          : 0
.... register #01: 00170011
.......     : max redirection entries: 0017
.......     : PRQ implemented: 0
.......     : IO APIC version: 0011
.... register #02: 00000000
.......     : arbitration: 00
.... IRQ redirection table:
 NR Log Phy Mask Trig IRR Pol Stat Dest Deli Vect:   
 00 000 00  1    0    0   0   0    0    0    00
 01 003 03  0    0    0   0   0    1    1    39
 02 003 03  0    0    0   0   0    1    1    31
 03 003 03  0    0    0   0   0    1    1    41
 04 003 03  0    0    0   0   0    1    1    49
 05 003 03  0    0    0   0   0    1    1    51
 06 003 03  0    0    0   0   0    1    1    59
 07 003 03  0    0    0   0   0    1    1    61
 08 003 03  0    0    0   0   0    1    1    69
 09 003 03  0    0    0   0   0    1    1    71
 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 003 03  0    0    0   0   0    1    1    79
 0f 000 00  1    0    0   0   0    0    0    00
 10 003 03  1    1    0   1   0    1    1    81
 11 003 03  1    1    0   1   0    1    1    89
 12 003 03  1    1    0   1   0    1    1    91
 13 003 03  1    1    0   1   0    1    1    99
 14 000 00  1    0    0   0   0    0    0    00
 15 000 00  1    0    0   0   0    0    0    00
 16 000 00  1    0    0   0   0    0    0    00
 17 000 00  1    0    0   0   0    0    0    00
IRQ to pin mappings:
IRQ0 -> 0:2
IRQ1 -> 0:1
IRQ3 -> 0:3
IRQ4 -> 0:4
IRQ5 -> 0:5
IRQ6 -> 0:6
IRQ7 -> 0:7
IRQ8 -> 0:8
IRQ9 -> 0:9
IRQ10 -> 0:17
IRQ11 -> 0:16
IRQ12 -> 0:18
IRQ14 -> 0:14
IRQ15 -> 0:19
.................................... done.
Using local APIC timer interrupts.
calibrating APIC timer ...
..... CPU clock speed is 399.5606 MHz.
..... host bus clock speed is 99.8899 MHz.
cpu: 0, clocks: 998899, slice: 332966
CPU0<T0:998896,T1:665920,D:10,S:332966,C:998899>
cpu: 1, clocks: 998899, slice: 332966
CPU1<T0:998896,T1:332960,D:4,S:332966,C:998899>
checking TSC synchronization across CPUs: passed.
Waiting on wait_init_idle (map = 0x2)
All processors have done init_idle
PCI: PCI BIOS revision 2.10 entry at 0xf0750, last bus=1
PCI: Using configuration type 1
PCI: Probing PCI hardware
PCI: Probing PCI hardware (bus 00)
PCI: Using IRQ router PIIX [8086/7110] at 00:04.0
Limiting direct PCI/PCI transfers.
Linux NET4.0 for Linux 2.4
[SNIPPED...]

Re: Linux-2.4.22

[Jason Baron]

On Tue, 26 Aug 2003, Richard B. Johnson wrote:

> 
> I configured, built and booted Linux-2.4.22. There are
> some problems.
> 
> (1) `dmesg` fails to read the first part of the buffered
> kernel log. I have attached two files, dmesg-20 (normal)

sounds like the log buffer wrapped around from a lot of printks

> (3)  When umounting the root file-system, the machine usually
> hangs. The result is a long `fsck` on the next boot. The problem
> seems to be that sendmail doesn't get killed during the `init 0`
> sequence. It remains with a file open and the root file-system isn't
> unmounted. A temporary work-round is to `ifconfig eth0 down` before
> starting shutdown. Otherwise, sendmail remains stuck in the 'D' state.

this is likely the unshare_files change, which has been mentioned in
several threads as causing similar type issues...i posted a patch that
solves the issue, and Alan included a patch in his -ac series, which 
also addresses this issue.  

-Jason

Re: Linux-2.4.22

[Richard B. Johnson]

On Wed, 27 Aug 2003, Jason Baron wrote:

>
> On Tue, 26 Aug 2003, Richard B. Johnson wrote:
>
> >
> > I configured, built and booted Linux-2.4.22. There are
> > some problems.
> >
> > (1) `dmesg` fails to read the first part of the buffered
> > kernel log. I have attached two files, dmesg-20 (normal)
>
> sounds like the log buffer wrapped around from a lot of printks
>

Perhaps the buffer size was changed??  I'll look at the printks()
I think there are the same number as before.

> > (3)  When umounting the root file-system, the machine usually
> > hangs. The result is a long `fsck` on the next boot. The problem
> > seems to be that sendmail doesn't get killed during the `init 0`
> > sequence. It remains with a file open and the root file-system isn't
> > unmounted. A temporary work-round is to `ifconfig eth0 down` before
> > starting shutdown. Otherwise, sendmail remains stuck in the 'D' state.
>
> this is likely the unshare_files change, which has been mentioned in
> several threads as causing similar type issues...i posted a patch that
> solves the issue, and Alan included a patch in his -ac series, which
> also addresses this issue.
>
> -Jason
>

Thanks, I'll check into it.


Cheers,
Dick Johnson
Penguin : Linux version 2.4.22 on an i686 machine (794.73 BogoMips).
            Note 96.31% of all statistics are fiction.

Re: Linux-2.4.22

[Richard B. Johnson]

On Wed, 27 Aug 2003, Richard B. Johnson wrote:

> On Wed, 27 Aug 2003, Jason Baron wrote:
>
> >
> > On Tue, 26 Aug 2003, Richard B. Johnson wrote:
> >
> > >
> > > I configured, built and booted Linux-2.4.22. There are
> > > some problems.
> > >
> > > (1) `dmesg` fails to read the first part of the buffered
> > > kernel log. I have attached two files, dmesg-20 (normal)
> >
> > sounds like the log buffer wrapped around from a lot of printks
> >
>

I looked into this. The problem I am seeing is not in printk().
It may, therefore, be in klogd.

I replaced the linux-2.4.22 printk() with the one that worked from
2.4.20. The problem presists!

The log-file, when booting the SMP machine is 7,653 bytes when
using 2.4.20. With linux-2.4.22, the first 33 bytes are missing.

Cheers,
Dick Johnson
Penguin : Linux version 2.4.22 on an i686 machine (794.73 BogoMips).
            Note 96.31% of all statistics are fiction.

Re: Linux-2.4.22

[Marcelo Tosatti]

On Tue, 26 Aug 2003, Richard B. Johnson wrote:

> 
> I configured, built and booted Linux-2.4.22. There are
> some problems.
> 
> (1) `dmesg` fails to read the first part of the buffered
> kernel log. I have attached two files, dmesg-20 (normal)
> and dmesg-22 (bad). File dmesg-22 is from Linux-2.4.22
> and dmesg-20 is from Linux-2.4.20. To save space, I
> snip everything after 'NET4'.
> 
> (2)  The ipx module fails to load with undefined symbols.
> This module loads fine in Linux-2.4.20.
> 
> depmod: *** Unresolved symbols in /lib/modules/2.4.22/kernel/net/ipx/ipx.o
> depmod: 	unregister_8022_client
> depmod: 	make_EII_client
> depmod: 	register_8022_client
> depmod: 	register_snap_client
> depmod: 	make_8023_client
> depmod: 	destroy_8023_client
> depmod: 	destroy_EII_client
> depmod: 	unregister_snap_client

> (3)  When umounting the root file-system, the machine usually
> hangs. The result is a long `fsck` on the next boot. The problem
> seems to be that sendmail doesn't get killed during the `init 0`
> sequence. It remains with a file open and the root file-system isn't
> unmounted. A temporary work-round is to `ifconfig eth0 down` before
> starting shutdown. Otherwise, sendmail remains stuck in the 'D' state.

Which previous kernel didnt show this behaviour? 

> 
> (4)  When mounting the DOS file-systems during startup, the echo
> on the screen shows about 15 lines of white-space. This never
> happened before. When mounting /proc, there are 6 lines of
> white-space, also strange.

Again, which kernel doesnt show that behaviour? 

Thanks

Re: Linux-2.4.22

[Marcelo Tosatti]

On Mon, 1 Sep 2003, Marcelo Tosatti wrote:

> 
> 
> On Tue, 26 Aug 2003, Richard B. Johnson wrote:
> 
> > 
> > I configured, built and booted Linux-2.4.22. There are
> > some problems.
> > 
> > (1) `dmesg` fails to read the first part of the buffered
> > kernel log. I have attached two files, dmesg-20 (normal)
> > and dmesg-22 (bad). File dmesg-22 is from Linux-2.4.22
> > and dmesg-20 is from Linux-2.4.20. To save space, I
> > snip everything after 'NET4'.
> > 
> > (2)  The ipx module fails to load with undefined symbols.
> > This module loads fine in Linux-2.4.20.
> > 
> > depmod: *** Unresolved symbols in /lib/modules/2.4.22/kernel/net/ipx/ipx.o
> > depmod: 	unregister_8022_client
> > depmod: 	make_EII_client
> > depmod: 	register_8022_client
> > depmod: 	register_snap_client
> > depmod: 	make_8023_client
> > depmod: 	destroy_8023_client
> > depmod: 	destroy_EII_client
> > depmod: 	unregister_snap_client
> 
> > (3)  When umounting the root file-system, the machine usually
> > hangs. The result is a long `fsck` on the next boot. The problem
> > seems to be that sendmail doesn't get killed during the `init 0`
> > sequence. It remains with a file open and the root file-system isn't
> > unmounted. A temporary work-round is to `ifconfig eth0 down` before
> > starting shutdown. Otherwise, sendmail remains stuck in the 'D' state.
> 
> Which previous kernel didnt show this behaviour? 
> 
> > 
> > (4)  When mounting the DOS file-systems during startup, the echo
> > on the screen shows about 15 lines of white-space. This never
> > happened before. When mounting /proc, there are 6 lines of
> > white-space, also strange.
> 
> Again, which kernel doesnt show that behaviour? 

Oh, Jason already answered. The fix he talks about is already in 
2.4.23-pre. 

Re: Linux-2.4.22

[Richard B. Johnson]

On Mon, 1 Sep 2003, Marcelo Tosatti wrote:

>
>
> On Tue, 26 Aug 2003, Richard B. Johnson wrote:
>
> >
> > I configured, built and booted Linux-2.4.22. There are
> > some problems.
> >
> > (1) `dmesg` fails to read the first part of the buffered
> > kernel log. I have attached two files, dmesg-20 (normal)
> > and dmesg-22 (bad). File dmesg-22 is from Linux-2.4.22
> > and dmesg-20 is from Linux-2.4.20. To save space, I
> > snip everything after 'NET4'.
> >
> > (2)  The ipx module fails to load with undefined symbols.
> > This module loads fine in Linux-2.4.20.
> >
> > depmod: *** Unresolved symbols in /lib/modules/2.4.22/kernel/net/ipx/ipx.o
> > depmod: 	unregister_8022_client
> > depmod: 	make_EII_client
> > depmod: 	register_8022_client
> > depmod: 	register_snap_client
> > depmod: 	make_8023_client
> > depmod: 	destroy_8023_client
> > depmod: 	destroy_EII_client
> > depmod: 	unregister_snap_client
>
> > (3)  When umounting the root file-system, the machine usually
> > hangs. The result is a long `fsck` on the next boot. The problem
> > seems to be that sendmail doesn't get killed during the `init 0`
> > sequence. It remains with a file open and the root file-system isn't
> > unmounted. A temporary work-round is to `ifconfig eth0 down` before
> > starting shutdown. Otherwise, sendmail remains stuck in the 'D' state.
>
> Which previous kernel didnt show this behaviour?
>

Previous kernel was linux-2.4.20. Linux-2.4.21 would never complete
a boot on my system so I gave up on that one.

> >
> > (4)  When mounting the DOS file-systems during startup, the echo
> > on the screen shows about 15 lines of white-space. This never
> > happened before. When mounting /proc, there are 6 lines of
> > white-space, also strange.
>
> Again, which kernel doesnt show that behaviour?
>

Also, I replaced linux-2.4.22/kernel/prink.c with the one from
linux-2.4.21 and it did not help the missing boot data problem.
I also changed the buffer size to 131,072 and it didn't help
either so the problem is not in printk.c, but somewhere else,
perhaps klogd.

> Thanks
>

Cheers,
Dick Johnson
Penguin : Linux version 2.4.22 on an i686 machine (794.73 BogoMips).
            Note 96.31% of all statistics are fiction.


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/
On Mon, 1 Sep 2003, Marcelo Tosatti wrote:

>
>
> On Tue, 26 Aug 2003, Richard B. Johnson wrote:
>
> >
> > I configured, built and booted Linux-2.4.22. There are
> > some problems.
> >
> > (1) `dmesg` fails to read the first part of the buffered
> > kernel log. I have attached two files, dmesg-20 (normal)
> > and dmesg-22 (bad). File dmesg-22 is from Linux-2.4.22
> > and dmesg-20 is from Linux-2.4.20. To save space, I
> > snip everything after 'NET4'.
> >
> > (2)  The ipx module fails to load with undefined symbols.
> > This module loads fine in Linux-2.4.20.
> >
> > depmod: *** Unresolved symbols in /lib/modules/2.4.22/kernel/net/ipx/ipx.o
> > depmod: 	unregister_8022_client
> > depmod: 	make_EII_client
> > depmod: 	register_8022_client
> > depmod: 	register_snap_client
> > depmod: 	make_8023_client
> > depmod: 	destroy_8023_client
> > depmod: 	destroy_EII_client
> > depmod: 	unregister_snap_client
>
> > (3)  When umounting the root file-system, the machine usually
> > hangs. The result is a long `fsck` on the next boot. The problem
> > seems to be that sendmail doesn't get killed during the `init 0`
> > sequence. It remains with a file open and the root file-system isn't
> > unmounted. A temporary work-round is to `ifconfig eth0 down` before
> > starting shutdown. Otherwise, sendmail remains stuck in the 'D' state.
>
> Which previous kernel didnt show this behaviour?
>

Previous kernel was linux-2.4.20. Linux-2.4.21 would never complete
a boot on my system so I gave up on that one.

> >
> > (4)  When mounting the DOS file-systems during startup, the echo
> > on the screen shows about 15 lines of white-space. This never
> > happened before. When mounting /proc, there are 6 lines of
> > white-space, also strange.
>
> Again, which kernel doesnt show that behaviour?
>

Also, I replaced linux-2.4.22/kernel/prink.c with the one from
linux-2.4.21 and it did not help the missing boot data problem.
I also changed the buffer size to 131,072 and it didn't help
either so the problem is not in printk.c, but somewhere else,
perhaps klogd.

> Thanks
>

Cheers,
Dick Johnson
Penguin : Linux version 2.4.22 on an i686 machine (794.73 BogoMips).
            Note 96.31% of all statistics are fiction.