Re: Regress for 8139too in 2.6.20
Andrew Morton wrote: >> > > That's a bit surprising - the initcall levels don't affect modules. > Presumably something went wrong in core kernel which later caused yenta > and/or 8139too to fail. > > Have you tried diffing the before- and after-dmesgs to see if that particular > commit has caused any interesting differences? > > And are you able to test any other cardbus devices to see whether it's > specific to 8139too? No devices would work until I manually loaded yenta_socket. Before the change, the PCMCIA bridge was discovered earlier, and yenta_socket was automatically loaded. Now I need to add it to the list of modules to be loaded at bootup. With that change, everyting is OK. The diff between yenta as a module and yenta built is follows. Thanks, Larry --- --- /ide/dmesg_with_yenta_module2007-02-12 18:51:35.0 -0600 +++ /ide/dmesg_with_yenta_builtin 2007-02-12 16:25:24.0 -0600 @@ -1,4 +1,4 @@ -Linux version 2.6.20-default-g7096ede5-dirty ([EMAIL PROTECTED]) (gcc version 4.0.2 20050901 (prerelease) (SUSE Linux)) #119 Mon Feb 12 18:40:07 CST 2007 +Linux version 2.6.20-default-g7096ede5 ([EMAIL PROTECTED]) (gcc version 4.0.2 20050901 (prerelease) (SUSE Linux)) #116 Sun Feb 11 14:27:53 CST 2007 BIOS-provided physical RAM map: sanitize start sanitize end @@ -39,28 +39,28 @@ ACPI: FACS 07C0, 0040 ACPI: Disabling ACPI support Allocating PCI resources starting at 1000 (gap: 0800:f7fea400) -Detected 331.611 MHz processor. +Detected 331.592 MHz processor. Built 1 zonelists. Total pages: 32497 Kernel command line: root=/dev/hda3 vga=0x314 selinux=0resume=/dev/hda2 splash=silent showopts Local APIC disabled by BIOS -- you can enable it with "lapic" mapped APIC to d000 (01101000) Enabling fast FPU save and restore... done. Initializing CPU#0 -CPU 0 irqstacks, hard=c0421000 soft=c0422000 +CPU 0 irqstacks, hard=c0432000 soft=c0433000 PID hash table entries: 512 (order: 9, 2048 bytes) Console: colour dummy device 80x25 Dentry cache hash table entries: 16384 (order: 4, 65536 bytes) Inode-cache hash table entries: 8192 (order: 3, 32768 bytes) -Memory: 124256k/131008k available (2092k kernel code, 6220k reserved, 886k data, 200k init, 0k highmem) +Memory: 124188k/131008k available (2137k kernel code, 6288k reserved, 909k data, 200k init, 0k highmem) virtual kernel memory layout: fixmap : 0xfffb6000 - 0xf000 ( 292 kB) vmalloc : 0xc880 - 0xfffb4000 ( 887 MB) lowmem : 0xc000 - 0xc7ff ( 127 MB) - .init : 0xc03ea000 - 0xc041c000 ( 200 kB) - .data : 0xc030b24b - 0xc03e8c48 ( 886 kB) - .text : 0xc010 - 0xc030b24b (2092 kB) + .init : 0xc03fb000 - 0xc042d000 ( 200 kB) + .data : 0xc031653b - 0xc03f9c48 ( 909 kB) + .text : 0xc010 - 0xc031653b (2137 kB) Checking if this processor honours the WP bit even in supervisor mode... Ok. -Calibrating delay using timer specific routine.. 664.03 BogoMIPS (lpj=1328067) +Calibrating delay using timer specific routine.. 664.05 BogoMIPS (lpj=1328111) Mount-cache hash table entries: 512 CPU: After generic identify, caps: 0183f9ff CPU: L1 I cache: 16K, L1 D cache: 16K @@ -104,8 +104,10 @@ MEM window: 1c00-1fff PCI: Found IRQ 9 for device :00:0a.0 PCI: Sharing IRQ 9 with :00:08.1 +PCI: Setting latency timer of device :00:0a.0 to 64 PCI: Assigned IRQ 9 for device :00:0a.1 PCI: Sharing IRQ 9 with :00:09.0 +PCI: Setting latency timer of device :00:0a.1 to 64 NET: Registered protocol family 2 IP route cache hash table entries: 1024 (order: 0, 4096 bytes) TCP established hash table entries: 4096 (order: 4, 81920 bytes) @@ -115,7 +117,7 @@ checking if image is initramfs... it is Freeing initrd memory: 1564k freed audit: initializing netlink socket (disabled) -audit(1171306196.744:1): initialized +audit(1171277305.752:1): initialized io scheduler noop registered io scheduler anticipatory registered (default) io scheduler deadline registered @@ -138,25 +140,33 @@ FDC 0 is a post-1991 82077 RAMDISK driver initialized: 16 RAM disks of 64000K size 1024 blocksize loop: loaded (max 8 devices) +Yenta: CardBus bridge found at :00:0a.0 [104d:8042] +Yenta: ISA IRQ mask 0x0cb8, PCI irq 9 +Socket status: 3410 +Yenta: CardBus bridge found at :00:0a.1 [104d:8042] +Yenta: ISA IRQ mask 0x0cb8, PCI irq 9 +Socket status: 3820 PNP: No PS/2 controller found. Probing ports directly. serio: i8042 KBD port at 0x60,0x64 irq 1 serio: i8042 AUX port at 0x60,0x64 irq 12 mice: PS/2 mouse device common for all mice input: AT Translated Set 2 keyboard as /class/input/input0 input: PC Speaker as /class/input/input1 +pccard: PCMCIA card inserted into slot 0 input: PS/2 Mouse as /class/input/input2 input: AlpsPS/2 ALPS GlidePoint as /class/input/input3 NET: Registered protocol family 1 Using IPI Shortcut mode Freeing unused
Re: Regress for 8139too in 2.6.20
> On Sun, 11 Feb 2007 18:03:33 -0600 Larry Finger <[EMAIL PROTECTED]> wrote: > In kernel version 2.6.20, my network interface, a Uniden PCN 300 PCMCIA card > that uses the 8139too > driver fails to initialize with Yenta and 8139too as modules. It worked > correctly in 2.6.19. Using > git bisect, the bad commit is shown below: > > [EMAIL PROTECTED]:~/linux-2.6> git bisect good > 8d610dd52dd1da696e199e4b4545f33a2a5de5c6 is first bad commit > commit 8d610dd52dd1da696e199e4b4545f33a2a5de5c6 > Author: Linus Torvalds <[EMAIL PROTECTED]> > Date: Mon Dec 11 12:12:04 2006 -0800 > > Make sure we populate the initroot filesystem late enough > > We should not initialize rootfs before all the core initializers have > run. So do it as a separate stage just before starting the regular > driver initializers. > > Signed-off-by: Linus Torvalds <[EMAIL PROTECTED]> > > :04 04 12bc13def90d15921d41d2b285854b3e157a970f > f936e01f6b1b2b75478484861d34e81830c73860 M > include > :04 04 5673719c3f6b47b329cfc9554c112077634a9b19 > 9c2e768964af1500d62849836b9f8e801fe7f29e M > init > > > If Yenta is built into the kernel, rather than a module, it works again with > 2.6.20. > That's a bit surprising - the initcall levels don't affect modules. Presumably something went wrong in core kernel which later caused yenta and/or 8139too to fail. Have you tried diffing the before- and after-dmesgs to see if that particular commit has caused any interesting differences? And are you able to test any other cardbus devices to see whether it's specific to 8139too? - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Regress for 8139too in 2.6.20
On Sun, 11 Feb 2007 18:03:33 -0600 Larry Finger [EMAIL PROTECTED] wrote: In kernel version 2.6.20, my network interface, a Uniden PCN 300 PCMCIA card that uses the 8139too driver fails to initialize with Yenta and 8139too as modules. It worked correctly in 2.6.19. Using git bisect, the bad commit is shown below: [EMAIL PROTECTED]:~/linux-2.6 git bisect good 8d610dd52dd1da696e199e4b4545f33a2a5de5c6 is first bad commit commit 8d610dd52dd1da696e199e4b4545f33a2a5de5c6 Author: Linus Torvalds [EMAIL PROTECTED] Date: Mon Dec 11 12:12:04 2006 -0800 Make sure we populate the initroot filesystem late enough We should not initialize rootfs before all the core initializers have run. So do it as a separate stage just before starting the regular driver initializers. Signed-off-by: Linus Torvalds [EMAIL PROTECTED] :04 04 12bc13def90d15921d41d2b285854b3e157a970f f936e01f6b1b2b75478484861d34e81830c73860 M include :04 04 5673719c3f6b47b329cfc9554c112077634a9b19 9c2e768964af1500d62849836b9f8e801fe7f29e M init If Yenta is built into the kernel, rather than a module, it works again with 2.6.20. That's a bit surprising - the initcall levels don't affect modules. Presumably something went wrong in core kernel which later caused yenta and/or 8139too to fail. Have you tried diffing the before- and after-dmesgs to see if that particular commit has caused any interesting differences? And are you able to test any other cardbus devices to see whether it's specific to 8139too? - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Regress for 8139too in 2.6.20
Andrew Morton wrote: That's a bit surprising - the initcall levels don't affect modules. Presumably something went wrong in core kernel which later caused yenta and/or 8139too to fail. Have you tried diffing the before- and after-dmesgs to see if that particular commit has caused any interesting differences? And are you able to test any other cardbus devices to see whether it's specific to 8139too? No devices would work until I manually loaded yenta_socket. Before the change, the PCMCIA bridge was discovered earlier, and yenta_socket was automatically loaded. Now I need to add it to the list of modules to be loaded at bootup. With that change, everyting is OK. The diff between yenta as a module and yenta built is follows. Thanks, Larry --- --- /ide/dmesg_with_yenta_module2007-02-12 18:51:35.0 -0600 +++ /ide/dmesg_with_yenta_builtin 2007-02-12 16:25:24.0 -0600 @@ -1,4 +1,4 @@ -Linux version 2.6.20-default-g7096ede5-dirty ([EMAIL PROTECTED]) (gcc version 4.0.2 20050901 (prerelease) (SUSE Linux)) #119 Mon Feb 12 18:40:07 CST 2007 +Linux version 2.6.20-default-g7096ede5 ([EMAIL PROTECTED]) (gcc version 4.0.2 20050901 (prerelease) (SUSE Linux)) #116 Sun Feb 11 14:27:53 CST 2007 BIOS-provided physical RAM map: sanitize start sanitize end @@ -39,28 +39,28 @@ ACPI: FACS 07C0, 0040 ACPI: Disabling ACPI support Allocating PCI resources starting at 1000 (gap: 0800:f7fea400) -Detected 331.611 MHz processor. +Detected 331.592 MHz processor. Built 1 zonelists. Total pages: 32497 Kernel command line: root=/dev/hda3 vga=0x314 selinux=0resume=/dev/hda2 splash=silent showopts Local APIC disabled by BIOS -- you can enable it with lapic mapped APIC to d000 (01101000) Enabling fast FPU save and restore... done. Initializing CPU#0 -CPU 0 irqstacks, hard=c0421000 soft=c0422000 +CPU 0 irqstacks, hard=c0432000 soft=c0433000 PID hash table entries: 512 (order: 9, 2048 bytes) Console: colour dummy device 80x25 Dentry cache hash table entries: 16384 (order: 4, 65536 bytes) Inode-cache hash table entries: 8192 (order: 3, 32768 bytes) -Memory: 124256k/131008k available (2092k kernel code, 6220k reserved, 886k data, 200k init, 0k highmem) +Memory: 124188k/131008k available (2137k kernel code, 6288k reserved, 909k data, 200k init, 0k highmem) virtual kernel memory layout: fixmap : 0xfffb6000 - 0xf000 ( 292 kB) vmalloc : 0xc880 - 0xfffb4000 ( 887 MB) lowmem : 0xc000 - 0xc7ff ( 127 MB) - .init : 0xc03ea000 - 0xc041c000 ( 200 kB) - .data : 0xc030b24b - 0xc03e8c48 ( 886 kB) - .text : 0xc010 - 0xc030b24b (2092 kB) + .init : 0xc03fb000 - 0xc042d000 ( 200 kB) + .data : 0xc031653b - 0xc03f9c48 ( 909 kB) + .text : 0xc010 - 0xc031653b (2137 kB) Checking if this processor honours the WP bit even in supervisor mode... Ok. -Calibrating delay using timer specific routine.. 664.03 BogoMIPS (lpj=1328067) +Calibrating delay using timer specific routine.. 664.05 BogoMIPS (lpj=1328111) Mount-cache hash table entries: 512 CPU: After generic identify, caps: 0183f9ff CPU: L1 I cache: 16K, L1 D cache: 16K @@ -104,8 +104,10 @@ MEM window: 1c00-1fff PCI: Found IRQ 9 for device :00:0a.0 PCI: Sharing IRQ 9 with :00:08.1 +PCI: Setting latency timer of device :00:0a.0 to 64 PCI: Assigned IRQ 9 for device :00:0a.1 PCI: Sharing IRQ 9 with :00:09.0 +PCI: Setting latency timer of device :00:0a.1 to 64 NET: Registered protocol family 2 IP route cache hash table entries: 1024 (order: 0, 4096 bytes) TCP established hash table entries: 4096 (order: 4, 81920 bytes) @@ -115,7 +117,7 @@ checking if image is initramfs... it is Freeing initrd memory: 1564k freed audit: initializing netlink socket (disabled) -audit(1171306196.744:1): initialized +audit(1171277305.752:1): initialized io scheduler noop registered io scheduler anticipatory registered (default) io scheduler deadline registered @@ -138,25 +140,33 @@ FDC 0 is a post-1991 82077 RAMDISK driver initialized: 16 RAM disks of 64000K size 1024 blocksize loop: loaded (max 8 devices) +Yenta: CardBus bridge found at :00:0a.0 [104d:8042] +Yenta: ISA IRQ mask 0x0cb8, PCI irq 9 +Socket status: 3410 +Yenta: CardBus bridge found at :00:0a.1 [104d:8042] +Yenta: ISA IRQ mask 0x0cb8, PCI irq 9 +Socket status: 3820 PNP: No PS/2 controller found. Probing ports directly. serio: i8042 KBD port at 0x60,0x64 irq 1 serio: i8042 AUX port at 0x60,0x64 irq 12 mice: PS/2 mouse device common for all mice input: AT Translated Set 2 keyboard as /class/input/input0 input: PC Speaker as /class/input/input1 +pccard: PCMCIA card inserted into slot 0 input: PS/2 Mouse as /class/input/input2 input: AlpsPS/2 ALPS GlidePoint as /class/input/input3 NET: Registered protocol family 1 Using IPI Shortcut mode Freeing unused kernel memory:
