Q: new kernel not booting (init segfaults) : how to debug ?
System: firewall -Epia 5000 via c3 system -bios 2.07 (latest available, upgraded from 1.09 with same behaviour) -128Mb flash memory (ide emulation) -256mb ram -voyage linux (debian based) Runs "standard" kernel just fine, 2.6.22.17 also compiles/runs where as 2.6.23-rcX wont Typed over from screenshot: --- NET: Registered protocol family 1 NET: Registered protocol family 17 Using IPI Shortcut mode Freeing unused kernel memory: 148k freed init[1]: segfault at 8589 eip 8589 esp bfcfcb8c error 4 init[1]: segfault at 8589 eip 8589 esp bfcfcb8c error 4 init[1]: segfault at 8589 eip 8589 esp bfcfcb8c error 4 init[1]: segfault at 8589 eip 8589 esp bfcfcb8c error 4 init[1]: segfault at 8589 eip 8589 esp bfcfcb8c error 4 init[1]: segfault at 8589 eip 8589 esp bfcfcb8c error 4 init[1]: segfault at 8589 eip 8589 esp bfcfcb8c error 4 init[1]: segfault at 8589 eip 8589 esp bfcfcb8c error 4 init[1]: segfault at 8589 eip 8589 esp bfcfcb8c error 4 init[1]: segfault at 8589 eip 8589 esp bfcfcb8c error 4 printk: 788820 messages suppressed. --- The only thing changed is the kernel. I'm just plain flabbergasted about why this occurs and complete lost how to debug/persue this any further. Kernel config/systemmap etc at http://www.dth.net/kernel/c3/ Danny - 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/
Q: new kernel not booting (init segfaults) : how to debug ?
System: firewall -Epia 5000 via c3 system -bios 2.07 (latest available, upgraded from 1.09 with same behaviour) -128Mb flash memory (ide emulation) -256mb ram -voyage linux (debian based) Runs standard kernel just fine, 2.6.22.17 also compiles/runs where as 2.6.23-rcX wont Typed over from screenshot: --- NET: Registered protocol family 1 NET: Registered protocol family 17 Using IPI Shortcut mode Freeing unused kernel memory: 148k freed init[1]: segfault at 8589 eip 8589 esp bfcfcb8c error 4 init[1]: segfault at 8589 eip 8589 esp bfcfcb8c error 4 init[1]: segfault at 8589 eip 8589 esp bfcfcb8c error 4 init[1]: segfault at 8589 eip 8589 esp bfcfcb8c error 4 init[1]: segfault at 8589 eip 8589 esp bfcfcb8c error 4 init[1]: segfault at 8589 eip 8589 esp bfcfcb8c error 4 init[1]: segfault at 8589 eip 8589 esp bfcfcb8c error 4 init[1]: segfault at 8589 eip 8589 esp bfcfcb8c error 4 init[1]: segfault at 8589 eip 8589 esp bfcfcb8c error 4 init[1]: segfault at 8589 eip 8589 esp bfcfcb8c error 4 printk: 788820 messages suppressed. --- The only thing changed is the kernel. I'm just plain flabbergasted about why this occurs and complete lost how to debug/persue this any further. Kernel config/systemmap etc at http://www.dth.net/kernel/c3/ Danny - 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/
typo fix Kernel config option
--- lib/Kconfig.debug.orig 2007-09-21 20:40:08.544353283 +0200 +++ lib/Kconfig.debug 2007-09-21 20:40:33.478816660 +0200 @@ -284,7 +284,7 @@ select KALLSYMS_ALL config LOCK_STAT - bool "Lock usage statisitics" + bool "Lock usage statistics" depends on DEBUG_KERNEL && TRACE_IRQFLAGS_SUPPORT && STACKTRACE_SUPPORT && LOCKDEP_SUPPORT select LOCKDEP select DEBUG_SPINLOCK -- The five R's of windows tech support: Retry, Reboot, Reinstall, Replace & Resign - 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/
typo fix Kernel config option
--- lib/Kconfig.debug.orig 2007-09-21 20:40:08.544353283 +0200 +++ lib/Kconfig.debug 2007-09-21 20:40:33.478816660 +0200 @@ -284,7 +284,7 @@ select KALLSYMS_ALL config LOCK_STAT - bool Lock usage statisitics + bool Lock usage statistics depends on DEBUG_KERNEL TRACE_IRQFLAGS_SUPPORT STACKTRACE_SUPPORT LOCKDEP_SUPPORT select LOCKDEP select DEBUG_SPINLOCK -- The five R's of windows tech support: Retry, Reboot, Reinstall, Replace Resign - 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: [2/4] 2.6.23-rc4: known regressions
Quoting Michal Piotrowski ([EMAIL PROTECTED]): > Here is a list of some known regressions in 2.6.23-rc4. > CPUFREQ > Subject : ide problems: 2.6.22-git17 working, 2.6.23-rc1* is not > References : http://lkml.org/lkml/2007/7/27/298 > http://lkml.org/lkml/2007/7/29/371 > Last known good : ? > Submitter : dth <[EMAIL PROTECTED]> > Caused-By : Len Brown <[EMAIL PROTECTED]> > commit f79e3185dd0f8650022518d7624c876d8929061b > Handled-By : Len Brown <[EMAIL PROTECTED]> > Status : problem is being debugged I just compiled 2.6.23-rc4 on this setup to check if we made any progress. After reboot i see: [SNIP] NET: Registered protocol family 17 Using IPI Shortcut mode Freeing unused kernel memory: 148 freed init[1]: segfault at 8589 eip 8589 esp bfcfcb8c error 4 init[1]: segfault at 8589 eip 8589 esp bfcfcb8c error 4 init[1]: segfault at 8589 eip 8589 esp bfcfcb8c error 4 init[1]: segfault at 8589 eip 8589 esp bfcfcb8c error 4 init[1]: segfault at 8589 eip 8589 esp bfcfcb8c error 4 init[1]: segfault at 8589 eip 8589 esp bfcfcb8c error 4 init[1]: segfault at 8589 eip 8589 esp bfcfcb8c error 4 init[1]: segfault at 8589 eip 8589 esp bfcfcb8c error 4 init[1]: segfault at 8589 eip 8589 esp bfcfcb8c error 4 init[1]: segfault at 8589 eip 8589 esp bfcfcb8c error 4 input: AT Translated Set 2 keyboard as /devices/platform/i8042/ printk: 7888020 messages suppressed init[1]: segfault at 8589 eip 8589 esp bfcfcb8c error 4 [more of the last 2 lines repeated over and over] Am i doing something wrong (very possible) or am i bitten by another/new phenomena ? Danny -- - 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: [2/4] 2.6.23-rc4: known regressions
Quoting Michal Piotrowski ([EMAIL PROTECTED]): Here is a list of some known regressions in 2.6.23-rc4. CPUFREQ Subject : ide problems: 2.6.22-git17 working, 2.6.23-rc1* is not References : http://lkml.org/lkml/2007/7/27/298 http://lkml.org/lkml/2007/7/29/371 Last known good : ? Submitter : dth [EMAIL PROTECTED] Caused-By : Len Brown [EMAIL PROTECTED] commit f79e3185dd0f8650022518d7624c876d8929061b Handled-By : Len Brown [EMAIL PROTECTED] Status : problem is being debugged I just compiled 2.6.23-rc4 on this setup to check if we made any progress. After reboot i see: [SNIP] NET: Registered protocol family 17 Using IPI Shortcut mode Freeing unused kernel memory: 148 freed init[1]: segfault at 8589 eip 8589 esp bfcfcb8c error 4 init[1]: segfault at 8589 eip 8589 esp bfcfcb8c error 4 init[1]: segfault at 8589 eip 8589 esp bfcfcb8c error 4 init[1]: segfault at 8589 eip 8589 esp bfcfcb8c error 4 init[1]: segfault at 8589 eip 8589 esp bfcfcb8c error 4 init[1]: segfault at 8589 eip 8589 esp bfcfcb8c error 4 init[1]: segfault at 8589 eip 8589 esp bfcfcb8c error 4 init[1]: segfault at 8589 eip 8589 esp bfcfcb8c error 4 init[1]: segfault at 8589 eip 8589 esp bfcfcb8c error 4 init[1]: segfault at 8589 eip 8589 esp bfcfcb8c error 4 input: AT Translated Set 2 keyboard as /devices/platform/i8042/ printk: 7888020 messages suppressed init[1]: segfault at 8589 eip 8589 esp bfcfcb8c error 4 [more of the last 2 lines repeated over and over] Am i doing something wrong (very possible) or am i bitten by another/new phenomena ? Danny -- - 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: Update: ACPI problems: 2.6.22-git17 working, 2.6.23-rc1* is not: (was ide not working)
Okay Redid git bisect from start: git bisect log git-bisect start # good: [098fd16f5f665d3baa7e682d8cb3d7c0fe6f] Linux 2.6.22 git-bisect good 098fd16f5f665d3baa7e682d8cb3d7c0fe6f # good: [098fd16f5f665d3baa7e682d8cb3d7c0fe6f] Linux 2.6.22 git-bisect good 098fd16f5f665d3baa7e682d8cb3d7c0fe6f # bad: [7d57c74238cdf570bca20b711b2c0b31a553c1e5] Linux 2.6.23-rc1 git-bisect bad 7d57c74238cdf570bca20b711b2c0b31a553c1e5 # good: [1f1c2881f673671539b25686df463518d69c4649] Merge branch # 'upstream-linus' of # master.kernel.org:/pub/scm/linux/kernel/git/jgarzik/netdev-2.6 git-bisect good 1f1c2881f673671539b25686df463518d69c4649 # good: [5b7f13bd26a0c1d394a1a1f2bb6de5130c3a3843] coda: update module # information git-bisect good 5b7f13bd26a0c1d394a1a1f2bb6de5130c3a3843 # good: [74889e41d9a1f80928130a02af9b010673bc5ba7] [CELL] cbe_cpufreq: # reorganize code git-bisect good 74889e41d9a1f80928130a02af9b010673bc5ba7 # good: [bdda1561ffda764583a295229db66d94cf6038a3] x86_64: x86_64 - Use # non locked version for local_cmpxchg() git-bisect good bdda1561ffda764583a295229db66d94cf6038a3 # bad: [d7f5e3df3574c6e38b99f5fe22f15540b2b9811d] Merge branch # 'for-linus' of git://git.o-hand.com/linux-rpurdie-leds git-bisect bad d7f5e3df3574c6e38b99f5fe22f15540b2b9811d # bad: [08e31686d6d119ba26bf0690f5f872f6f5bd1a97] Pull thinkpad into # release branch git-bisect bad 08e31686d6d119ba26bf0690f5f872f6f5bd1a97 # bad: [f79e3185dd0f8650022518d7624c876d8929061b] Pull misc into release # branch git-bisect bad f79e3185dd0f8650022518d7624c876d8929061b # good: [22aadf8a07067644e101267ed5003043f2ad05bf] Pull bugzilla-7880 # into release branch git-bisect good 22aadf8a07067644e101267ed5003043f2ad05bf # good: [e8b495fe09bc793ae26774e7b2667f7f658d56e2] Pull dock-bay into # release branch git-bisect good e8b495fe09bc793ae26774e7b2667f7f658d56e2 # good: [18eab8550397f1f3d4b8b2c5257c88dae25d58ed] ACPI: Enable C3 even # when PM2_control is zero git-bisect good 18eab8550397f1f3d4b8b2c5257c88dae25d58ed # good: [7a9b9068b8c7b526894904c0b9b90354825b8fbd] ACPI: update # feature-removal-schedule.txt, /sys/firmware/acpi/namespace is gone git-bisect good 7a9b9068b8c7b526894904c0b9b90354825b8fbd # good: [8b8eb7d8cfc6cd95ed00cd58754e8493322505bd] ACPI: update ACPI # proc I/F removal schedule git-bisect good 8b8eb7d8cfc6cd95ed00cd58754e8493322505bd f79e3185dd0f8650022518d7624c876d8929061b is first bad commit I will store this particular firewall setup friday (will go into storage for 2 months), if somebody would like more info, me to try something, please send it to me asap. Thanks for looking at this. Danny -- - 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: Update: ACPI problems: 2.6.22-git17 working, 2.6.23-rc1* is not: (was ide not working)
Okay Redid git bisect from start: git bisect log git-bisect start # good: [098fd16f5f665d3baa7e682d8cb3d7c0fe6f] Linux 2.6.22 git-bisect good 098fd16f5f665d3baa7e682d8cb3d7c0fe6f # good: [098fd16f5f665d3baa7e682d8cb3d7c0fe6f] Linux 2.6.22 git-bisect good 098fd16f5f665d3baa7e682d8cb3d7c0fe6f # bad: [7d57c74238cdf570bca20b711b2c0b31a553c1e5] Linux 2.6.23-rc1 git-bisect bad 7d57c74238cdf570bca20b711b2c0b31a553c1e5 # good: [1f1c2881f673671539b25686df463518d69c4649] Merge branch # 'upstream-linus' of # master.kernel.org:/pub/scm/linux/kernel/git/jgarzik/netdev-2.6 git-bisect good 1f1c2881f673671539b25686df463518d69c4649 # good: [5b7f13bd26a0c1d394a1a1f2bb6de5130c3a3843] coda: update module # information git-bisect good 5b7f13bd26a0c1d394a1a1f2bb6de5130c3a3843 # good: [74889e41d9a1f80928130a02af9b010673bc5ba7] [CELL] cbe_cpufreq: # reorganize code git-bisect good 74889e41d9a1f80928130a02af9b010673bc5ba7 # good: [bdda1561ffda764583a295229db66d94cf6038a3] x86_64: x86_64 - Use # non locked version for local_cmpxchg() git-bisect good bdda1561ffda764583a295229db66d94cf6038a3 # bad: [d7f5e3df3574c6e38b99f5fe22f15540b2b9811d] Merge branch # 'for-linus' of git://git.o-hand.com/linux-rpurdie-leds git-bisect bad d7f5e3df3574c6e38b99f5fe22f15540b2b9811d # bad: [08e31686d6d119ba26bf0690f5f872f6f5bd1a97] Pull thinkpad into # release branch git-bisect bad 08e31686d6d119ba26bf0690f5f872f6f5bd1a97 # bad: [f79e3185dd0f8650022518d7624c876d8929061b] Pull misc into release # branch git-bisect bad f79e3185dd0f8650022518d7624c876d8929061b # good: [22aadf8a07067644e101267ed5003043f2ad05bf] Pull bugzilla-7880 # into release branch git-bisect good 22aadf8a07067644e101267ed5003043f2ad05bf # good: [e8b495fe09bc793ae26774e7b2667f7f658d56e2] Pull dock-bay into # release branch git-bisect good e8b495fe09bc793ae26774e7b2667f7f658d56e2 # good: [18eab8550397f1f3d4b8b2c5257c88dae25d58ed] ACPI: Enable C3 even # when PM2_control is zero git-bisect good 18eab8550397f1f3d4b8b2c5257c88dae25d58ed # good: [7a9b9068b8c7b526894904c0b9b90354825b8fbd] ACPI: update # feature-removal-schedule.txt, /sys/firmware/acpi/namespace is gone git-bisect good 7a9b9068b8c7b526894904c0b9b90354825b8fbd # good: [8b8eb7d8cfc6cd95ed00cd58754e8493322505bd] ACPI: update ACPI # proc I/F removal schedule git-bisect good 8b8eb7d8cfc6cd95ed00cd58754e8493322505bd f79e3185dd0f8650022518d7624c876d8929061b is first bad commit I will store this particular firewall setup friday (will go into storage for 2 months), if somebody would like more info, me to try something, please send it to me asap. Thanks for looking at this. Danny -- - 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: Update: ide problems: 2.6.22-git17 working, 2.6.23-rc1* is not:
Quoting Len Brown ([EMAIL PROTECTED]): > Also, please test with CONFIG_X86_ACPI_CPUFREQ=n > to remove the acpi-cpufreq driver (and thus this patch) > from your kernel. If it still fails, then we know > that this driver (and this patch) are not related > to the failure. It wasn't enabled in any of the kernels i ran: # grep X86_ACPI ../configs/config* ../configs/config-2.6.22-git14-c3-via5000-firewall:# CONFIG_X86_ACPI_CPUFREQ is not set ../configs/config-2.6.22-git17-c3-via5000-firewall:# CONFIG_X86_ACPI_CPUFREQ is not set ../configs/config-2.6.23-rc1-git5:# CONFIG_X86_ACPI_CPUFREQ is not set ../configs/config-2.6.23-rc1-git6:# CONFIG_X86_ACPI_CPUFREQ is not set ../configs/config-2.6.23-rc1-git9:# CONFIG_X86_ACPI_CPUFREQ is not set ../configs/config-2.6.23-rc1-mm1-c3-firewall:# CONFIG_X86_ACPI_CPUFREQ is not set > Hmmm, okay, the "big hammer" works. Please see > if any of these smaller hammers work: > > pnpacpi=off > acpi=noirq > notsc _none_ of these options will work. The machine locks up solid. And that's what i'm the most surprised about. The last time i withnessed a solid kernel lockup without any panic/notification is _years_ ago. I also tried a kernel without "CPU Frequency scaling", so it is not the scaling up/down in Mhz of the cpu. I've even just compiled/run a kernel with libata and even that one still locks up. New round of git bisects i guess (this time powercycle instead of reboot and wait few hours before ginving it "bisect good" ) Will report back. Danny -- - 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: Update: ide problems: 2.6.22-git17 working, 2.6.23-rc1* is not:
Quoting Len Brown ([EMAIL PROTECTED]): > Hmmm, okay, the "big hammer" works. Please see > if any of these smaller hammers work: > acpi=noirq died within 2 minutes > notsc After 36 minutes -- - 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: Update: ide problems: 2.6.22-git17 working, 2.6.23-rc1* is not:
Quoting Len Brown ([EMAIL PROTECTED]): Hmmm, okay, the big hammer works. Please see if any of these smaller hammers work: acpi=noirq died within 2 minutes notsc After 36 minutes -- - 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: Update: ide problems: 2.6.22-git17 working, 2.6.23-rc1* is not:
Quoting Len Brown ([EMAIL PROTECTED]): Also, please test with CONFIG_X86_ACPI_CPUFREQ=n to remove the acpi-cpufreq driver (and thus this patch) from your kernel. If it still fails, then we know that this driver (and this patch) are not related to the failure. It wasn't enabled in any of the kernels i ran: # grep X86_ACPI ../configs/config* ../configs/config-2.6.22-git14-c3-via5000-firewall:# CONFIG_X86_ACPI_CPUFREQ is not set ../configs/config-2.6.22-git17-c3-via5000-firewall:# CONFIG_X86_ACPI_CPUFREQ is not set ../configs/config-2.6.23-rc1-git5:# CONFIG_X86_ACPI_CPUFREQ is not set ../configs/config-2.6.23-rc1-git6:# CONFIG_X86_ACPI_CPUFREQ is not set ../configs/config-2.6.23-rc1-git9:# CONFIG_X86_ACPI_CPUFREQ is not set ../configs/config-2.6.23-rc1-mm1-c3-firewall:# CONFIG_X86_ACPI_CPUFREQ is not set Hmmm, okay, the big hammer works. Please see if any of these smaller hammers work: pnpacpi=off acpi=noirq notsc _none_ of these options will work. The machine locks up solid. And that's what i'm the most surprised about. The last time i withnessed a solid kernel lockup without any panic/notification is _years_ ago. I also tried a kernel without CPU Frequency scaling, so it is not the scaling up/down in Mhz of the cpu. I've even just compiled/run a kernel with libata and even that one still locks up. New round of git bisects i guess (this time powercycle instead of reboot and wait few hours before ginving it bisect good ) Will report back. Danny -- - 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: Update: ide problems: 2.6.22-git17 working, 2.6.23-rc1* is not:
Quoting Len Brown ([EMAIL PROTECTED]): > Hmmm, okay, the "big hammer" works. Please see > if any of these smaller hammers work: > > pnpacpi=off Went out for dinner, machine was frozen on return. One less on the checklist .. -- - 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: Update: ide problems: 2.6.22-git17 working, 2.6.23-rc1* is not:
Quoting Len Brown ([EMAIL PROTECTED]): > Please attach the output from acpidump to > http://bugzilla.kernel.org/show_bug.cgi?id=7880 done also on : http://www.dth.net/kernel/acpidump_output_via_c3_5000 > We'll likely be able to tell from it if that patch > has any real effect on your system, or if you test > result was from some unrelated event. Reverting the patch didn't make a real difference, it only took longer (eg 16 minutes before lockup in stead of 2-3 minutes) > Also, please test with CONFIG_X86_ACPI_CPUFREQ=n > to remove the acpi-cpufreq driver (and thus this patch) > from your kernel. If it still fails, then we know > that this driver (and this patch) are not related > to the failure. Will do. This machine(firewall) is solar powered so i tried to let it consume as less power as possible This is in my startup script at the moment: echo ondemand > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor > Hmmm, okay, the "big hammer" works. Please see > if any of these smaller hammers work: > > pnpacpi=off > acpi=noirq > notsc More testing to do, however, sunday i'm going abroad for a while, all stuff will be in storage. If i cant find in the next few days (packing everything in moving boxes) it might take a while before i can test again. Sorry for that. Danny -- - 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: Update: ide problems: 2.6.22-git17 working, 2.6.23-rc1* is not:
Quoting Len Brown ([EMAIL PROTECTED]): Please attach the output from acpidump to http://bugzilla.kernel.org/show_bug.cgi?id=7880 done also on : http://www.dth.net/kernel/acpidump_output_via_c3_5000 We'll likely be able to tell from it if that patch has any real effect on your system, or if you test result was from some unrelated event. Reverting the patch didn't make a real difference, it only took longer (eg 16 minutes before lockup in stead of 2-3 minutes) Also, please test with CONFIG_X86_ACPI_CPUFREQ=n to remove the acpi-cpufreq driver (and thus this patch) from your kernel. If it still fails, then we know that this driver (and this patch) are not related to the failure. Will do. This machine(firewall) is solar powered so i tried to let it consume as less power as possible This is in my startup script at the moment: echo ondemand /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor Hmmm, okay, the big hammer works. Please see if any of these smaller hammers work: pnpacpi=off acpi=noirq notsc More testing to do, however, sunday i'm going abroad for a while, all stuff will be in storage. If i cant find in the next few days (packing everything in moving boxes) it might take a while before i can test again. Sorry for that. Danny -- - 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: Update: ide problems: 2.6.22-git17 working, 2.6.23-rc1* is not:
Quoting Len Brown ([EMAIL PROTECTED]): Hmmm, okay, the big hammer works. Please see if any of these smaller hammers work: pnpacpi=off Went out for dinner, machine was frozen on return. One less on the checklist .. -- - 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: Update: ide problems: 2.6.22-git17 working, 2.6.23-rc1* is not:
Quoting Gabriel C ([EMAIL PROTECTED]):
> Now while we think is ACPI this should be easy for you to bisect.
> This commit
> http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=39804b20f62532fa05c2a8c3e2d1ae551fd0327b
> merged ACPI so this one should be your first bad one.
> Maybe Len has some idea and you don't need to bisect :)
Thanks to personal coaching of Gabriel i bisected the last few days.
It looked like this was the cullprit:
22aadf8a07067644e101267ed5003043f2ad05bf is first bad commit
2.6.23-rc1-git[1-6] all lockup solid after either direct or
within a couple of minutes (less than 2) after reboot.
They all run fine with "acpi=off" as boot argument.
However, i'm currently running 2.6.23-rc1-git6 with this reverted:
diff --git a/arch/i386/kernel/cpu/cpufreq/acpi-cpufreq.c
b/arch/i386/kernel/cpu/cpufreq/acpi-cpufreq.c
index 18c8b67..6f846be 100644 (file)
--- a/arch/i386/kernel/cpu/cpufreq/acpi-cpufreq.c
+++ b/arch/i386/kernel/cpu/cpufreq/acpi-cpufreq.c
@@ -665,8 +665,8 @@ static int acpi_cpufreq_cpu_init(struct cpufreq_policy
*policy)
data->max_freq = perf->states[0].core_frequency * 1000;
/* table init */
for (i=0; istate_count; i++) {
- if (i>0 && perf->states[i].core_frequency ==
- perf->states[i-1].core_frequency)
+ if (i>0 && perf->states[i].core_frequency >=
+ data->freq_table[valid_states-1].frequency / 1000)
continue;
---
I could hardly believe this could be the cause.
And indeed after about 16 minutes the kernel froze again, though longer
uptime than other kernels :-(
This hardware is a via epia 5000 with latest bios available (2.07)
It's remarkable that with acpi=off the machine is rocksolid.
As is with 2.6.22* kernels _with_ acpi enabled!
weeks of uptime before i wanted to upgrade to a new kernel ;-)
I'm thinking of redoing the git disect but this time really powercycle
the unit between kernels since it "seems/feels" like a timer which
really counts to 0 and then locks the machine.
After a lockup/freeze i cant boot the kernel another time with acpi
enabled: it will simply hang after booting init.
And again nobody home: no keyboard activity whatsoever.
I've put the dmesg of 2.6.23-rc1-git6 with and without acpi=off online:
http://www.dth.net/kernel/via_output_2.6.23-rc1-git6-acpi_off
http://www.dth.net/kernel/via_output_2.6.23-rc1-git6-acpi_on
I would like to hear if someone has an idea how to tackle this problem.
Danny
--
-
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: Update: ide problems: 2.6.22-git17 working, 2.6.23-rc1* is not:
Quoting Gabriel C ([EMAIL PROTECTED]):
Now while we think is ACPI this should be easy for you to bisect.
This commit
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=39804b20f62532fa05c2a8c3e2d1ae551fd0327b
merged ACPI so this one should be your first bad one.
Maybe Len has some idea and you don't need to bisect :)
Thanks to personal coaching of Gabriel i bisected the last few days.
It looked like this was the cullprit:
22aadf8a07067644e101267ed5003043f2ad05bf is first bad commit
2.6.23-rc1-git[1-6] all lockup solid after either direct or
within a couple of minutes (less than 2) after reboot.
They all run fine with acpi=off as boot argument.
However, i'm currently running 2.6.23-rc1-git6 with this reverted:
diff --git a/arch/i386/kernel/cpu/cpufreq/acpi-cpufreq.c
b/arch/i386/kernel/cpu/cpufreq/acpi-cpufreq.c
index 18c8b67..6f846be 100644 (file)
--- a/arch/i386/kernel/cpu/cpufreq/acpi-cpufreq.c
+++ b/arch/i386/kernel/cpu/cpufreq/acpi-cpufreq.c
@@ -665,8 +665,8 @@ static int acpi_cpufreq_cpu_init(struct cpufreq_policy
*policy)
data-max_freq = perf-states[0].core_frequency * 1000;
/* table init */
for (i=0; iperf-state_count; i++) {
- if (i0 perf-states[i].core_frequency ==
- perf-states[i-1].core_frequency)
+ if (i0 perf-states[i].core_frequency =
+ data-freq_table[valid_states-1].frequency / 1000)
continue;
---
I could hardly believe this could be the cause.
And indeed after about 16 minutes the kernel froze again, though longer
uptime than other kernels :-(
This hardware is a via epia 5000 with latest bios available (2.07)
It's remarkable that with acpi=off the machine is rocksolid.
As is with 2.6.22* kernels _with_ acpi enabled!
weeks of uptime before i wanted to upgrade to a new kernel ;-)
I'm thinking of redoing the git disect but this time really powercycle
the unit between kernels since it seems/feels like a timer which
really counts to 0 and then locks the machine.
After a lockup/freeze i cant boot the kernel another time with acpi
enabled: it will simply hang after booting init.
And again nobody home: no keyboard activity whatsoever.
I've put the dmesg of 2.6.23-rc1-git6 with and without acpi=off online:
http://www.dth.net/kernel/via_output_2.6.23-rc1-git6-acpi_off
http://www.dth.net/kernel/via_output_2.6.23-rc1-git6-acpi_on
I would like to hear if someone has an idea how to tackle this problem.
Danny
--
-
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: ide problems: 2.6.22-git17 working, 2.6.23-rc1* is not
Quoting Gabriel C ([EMAIL PROTECTED]): > Maybe try to : > disable BSG ( maybe some leftover bug ) > boot acpi=off ( that got merged kind late ) My first git disected kernel wouldn't boot, but with acpi=off it would indeed boot! As did the 2.6.23-rc1-git5 kernel... I will bisect further to find out exactly what patch is playing up in my particular setup. thanks for the tip! ;-) Danny -- - 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: ide problems: 2.6.22-git17 working, 2.6.23-rc1* is not
Quoting Bartlomiej Zolnierkiewicz ([EMAIL PROTECTED]): > Please retry with the latest -git kernel and if the problem is still > there install git, get kernel tree and run git-bisect. I ran over "make menuconfig" and did a few changes. http://www.dth.net/kernel/config-2.6.23-rc1-git5 It boots, but freezes solid before doing any "work" as a firewall. I was able to catch boot messages with netconsole http://www.dth.net/kernel/via_output_2.6.23-rc1-git5 It didn't respond after the last line. magig sysrq etc, all nada. Will start to get acquainted with git ;-) Danny -- - 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: ide problems: 2.6.22-git17 working, 2.6.23-rc1* is not
Quoting Bartlomiej Zolnierkiewicz ([EMAIL PROTECTED]):
> Should be harmless for now but we would like to fix it the long-term,
> please send "hdparm --Istdout /dev/hda" output.
I allready made that available in the same subdir:
http://www.dth.net/kernel/
Output repeated here:
voyage:~# hdparm -I /dev/hda
/dev/hda:
ATA device, with non-removable media
Model Number: PQI IDE DiskOnModule
Serial Number:
Firmware Revision: db01.20a
Standards:
Likely used: 1
Configuration:
hard sectored
not MFM encoded
head switch time > 15us
fixed drive
disk xfer rate > 5Mbs
Logical max current
cylinders 500 500
heads 16 16
sectors/track 32 32
--
bytes/track: 0 bytes/sector: 528
CHS current addressable sectors: 256000
LBAuser addressable sectors: 256000
device size with M = 1024*1024: 125 MBytes
device size with M = 1000*1000: 131 MBytes
Capabilities:
LBA, IORDY not likely
Buffer type: 0002: dual port, multi-sector
Buffer size: 1.0kB bytes avail on r/w long: 4
Cannot perform double-word IO
R/W multiple sector transfer: Max = 1 Current = 0
DMA: not supported
PIO: pio0 pio1 pio2
voyage:~# hdparm -tT /dev/hda
/dev/hda:
Timing cached reads: 116 MB in 2.00 seconds = 57.92 MB/sec
Timing buffered disk reads: 16 MB in 3.01 seconds = 5.32 MB/sec
# hdparm --Istdout /dev/hda
/dev/hda:
045a 01f4 0010 0210 0020 0003
e800 2020 2020 2020 2020 2020 2020
2020 2020 2020 2020 0002 0002 0004 6462
3031 2e32 3061 5051 4920 4944 4520 4469
736b 4f6e 4d6f 6475 6c65 2020 2020 2020
2020 2020 2020 2020 2020 2020 2020 0001
0200 0200 0001 01f4 0010
0020 e800 0003 0100 e800 0003
> No IDE changes yet after 2.6.22-git17 so something else must have broke down.
darn
I also tried with libata driver on the 2.6.22 series but that wouldn't
work as well. I contacted Alan Cox and he made some patches/suggestions
that made 2.6.22-git16 with libata work!
I hope his patch will make it into mainline soon.
For the dmesg output of this kernel
http://www.dth.net/kernel/via_output_2.6.22-git16-libata_fix_alan_cox
> Please retry with the latest -git kernel and if the problem is still
> there install git, get kernel tree and run git-bisect.
>
> Since 2.6.22-git17 works fine the initial "good" commit would be
> e51f802babc5e368c60fbfd08c6c11269c9253b0 and the initial "bad" one
> f695baf2df9e0413d3521661070103711545207a (for 2.6.23-rc1).
>
> If you need some practical examples on using git-bisect, this one
>
> http://www.reactivated.net/weblog/archives/2006/01/using-git-bisect-to-find-buggy-kernel-patches/
>
> is a very good one (IMO).
I will certainly will read/try that.
> > VP_IDE: VIA vt8231 (rev 10) IDE UDMA100 controller on pci:00:11.1
> > ide0: BM-DMA at 0xd000-0xd007, BIOS settings: hda:pio, hdb:pio
> > ide1: BM-DMA at 0xd008-0xd00f, BIOS settings: hdc:pio, hdd:pio
> > Marking TSC unstable due to: possible TSC halt in C2.
> > Time: acpi_pm clocksource has been installed.
> > hda: PQI IDE DiskOnModule, ATA DISK drive
> > hda: IRQ probe failed (0xfff2)
>
> This message would indicate broken IRQ routing, however it is no
> longer present in the log for the kernel 2.6.23-rc1-git4 ([3]).
i booted with routeirq=pci but gave the same negative result.
> Interesting that the kernel 2.6.22-git17 (log [2]) doesn't use via82cxxx
> IDE host driver while the kernel 2.6.23-rc1-git4 (log [3]) does...?
kernel configs are also in above mentioned webdir
basically copied the 2.6.22-git17 and ran a make oldconfig.
Did a diff -u on those config files and there is really a lot different:
[snip]
-# ATA/IDE/MFM/RLL support
+# Device Drivers
#
[snip]
#
# IDE chipset support/bugfixes
#
+# CONFIG_BLK_DEV_TRM290 is not set
Re: ide problems: 2.6.22-git17 working, 2.6.23-rc1* is not
Quoting Bartlomiej Zolnierkiewicz ([EMAIL PROTECTED]):
Should be harmless for now but we would like to fix it the long-term,
please send hdparm --Istdout /dev/hda output.
I allready made that available in the same subdir:
http://www.dth.net/kernel/
Output repeated here:
voyage:~# hdparm -I /dev/hda
/dev/hda:
ATA device, with non-removable media
Model Number: PQI IDE DiskOnModule
Serial Number:
Firmware Revision: db01.20a
Standards:
Likely used: 1
Configuration:
hard sectored
not MFM encoded
head switch time 15us
fixed drive
disk xfer rate 5Mbs
Logical max current
cylinders 500 500
heads 16 16
sectors/track 32 32
--
bytes/track: 0 bytes/sector: 528
CHS current addressable sectors: 256000
LBAuser addressable sectors: 256000
device size with M = 1024*1024: 125 MBytes
device size with M = 1000*1000: 131 MBytes
Capabilities:
LBA, IORDY not likely
Buffer type: 0002: dual port, multi-sector
Buffer size: 1.0kB bytes avail on r/w long: 4
Cannot perform double-word IO
R/W multiple sector transfer: Max = 1 Current = 0
DMA: not supported
PIO: pio0 pio1 pio2
voyage:~# hdparm -tT /dev/hda
/dev/hda:
Timing cached reads: 116 MB in 2.00 seconds = 57.92 MB/sec
Timing buffered disk reads: 16 MB in 3.01 seconds = 5.32 MB/sec
# hdparm --Istdout /dev/hda
/dev/hda:
045a 01f4 0010 0210 0020 0003
e800 2020 2020 2020 2020 2020 2020
2020 2020 2020 2020 0002 0002 0004 6462
3031 2e32 3061 5051 4920 4944 4520 4469
736b 4f6e 4d6f 6475 6c65 2020 2020 2020
2020 2020 2020 2020 2020 2020 2020 0001
0200 0200 0001 01f4 0010
0020 e800 0003 0100 e800 0003
No IDE changes yet after 2.6.22-git17 so something else must have broke down.
darn
I also tried with libata driver on the 2.6.22 series but that wouldn't
work as well. I contacted Alan Cox and he made some patches/suggestions
that made 2.6.22-git16 with libata work!
I hope his patch will make it into mainline soon.
For the dmesg output of this kernel
http://www.dth.net/kernel/via_output_2.6.22-git16-libata_fix_alan_cox
Please retry with the latest -git kernel and if the problem is still
there install git, get kernel tree and run git-bisect.
Since 2.6.22-git17 works fine the initial good commit would be
e51f802babc5e368c60fbfd08c6c11269c9253b0 and the initial bad one
f695baf2df9e0413d3521661070103711545207a (for 2.6.23-rc1).
If you need some practical examples on using git-bisect, this one
http://www.reactivated.net/weblog/archives/2006/01/using-git-bisect-to-find-buggy-kernel-patches/
is a very good one (IMO).
I will certainly will read/try that.
VP_IDE: VIA vt8231 (rev 10) IDE UDMA100 controller on pci:00:11.1
ide0: BM-DMA at 0xd000-0xd007, BIOS settings: hda:pio, hdb:pio
ide1: BM-DMA at 0xd008-0xd00f, BIOS settings: hdc:pio, hdd:pio
Marking TSC unstable due to: possible TSC halt in C2.
Time: acpi_pm clocksource has been installed.
hda: PQI IDE DiskOnModule, ATA DISK drive
hda: IRQ probe failed (0xfff2)
This message would indicate broken IRQ routing, however it is no
longer present in the log for the kernel 2.6.23-rc1-git4 ([3]).
i booted with routeirq=pci but gave the same negative result.
Interesting that the kernel 2.6.22-git17 (log [2]) doesn't use via82cxxx
IDE host driver while the kernel 2.6.23-rc1-git4 (log [3]) does...?
kernel configs are also in above mentioned webdir
basically copied the 2.6.22-git17 and ran a make oldconfig.
Did a diff -u on those config files and there is really a lot different:
[snip]
-# ATA/IDE/MFM/RLL support
+# Device Drivers
#
[snip]
#
# IDE chipset support/bugfixes
#
+# CONFIG_BLK_DEV_TRM290 is not set
CONFIG_BLK_DEV_VIA82CXXX=y
-# CONFIG_IDE_CHIPSETS is not
Re: ide problems: 2.6.22-git17 working, 2.6.23-rc1* is not
Quoting Bartlomiej Zolnierkiewicz ([EMAIL PROTECTED]): Please retry with the latest -git kernel and if the problem is still there install git, get kernel tree and run git-bisect. I ran over make menuconfig and did a few changes. http://www.dth.net/kernel/config-2.6.23-rc1-git5 It boots, but freezes solid before doing any work as a firewall. I was able to catch boot messages with netconsole http://www.dth.net/kernel/via_output_2.6.23-rc1-git5 It didn't respond after the last line. magig sysrq etc, all nada. Will start to get acquainted with git ;-) Danny -- - 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: ide problems: 2.6.22-git17 working, 2.6.23-rc1* is not
Quoting Gabriel C ([EMAIL PROTECTED]): Maybe try to : disable BSG ( maybe some leftover bug ) boot acpi=off ( that got merged kind late ) My first git disected kernel wouldn't boot, but with acpi=off it would indeed boot! As did the 2.6.23-rc1-git5 kernel... I will bisect further to find out exactly what patch is playing up in my particular setup. thanks for the tip! ;-) Danny -- - 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: Linux-2.6.13-rc7
I hate responding to myself but it's necessary: >RC7-GIT7 barfed on me after some 20 hours: complete serial console message before it reset is on: http://newsgate.newsserver.nl/kernel/ as is config-file. Hardware: AMD64 running pure-64 debian ony tyan motherboard with opteron 250 cpu. Danny - 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: Linux-2.6.13-rc7
>I Wrote:
>After 53 hours and 31 minutes it crashed.
>dth pts/1zaphod.dth.net Wed Aug 24 09:54 - crash (2+05:31)
>reboot system boot 2.6.13-rc7 Wed Aug 24 09:51 (2+05:41)
>
>Prior to this kernel it had been running 2.6.12-mm1 without problems:
>reboot system boot 2.6.12-mm1 Sun Aug 14 12:13 (9+21:36)
>
>I will now compile & run rc7-git1.
RC7-GIT7 barfed on me after some 20 hours:
root ttyS0 Fri Aug 26 16:32 - crash (20:44)
reboot system boot 2.6.13-rc7-git1 Fri Aug 26 16:32 (20:59)
I managed to get some information from the serial console:
scsi0: SCBPTR == 0x55, SCB_NEXT == 0xff80, SCB_NEXT2 == 0xff6e
CDB 0 0 0 0 0 0
STACK: 0x10c 0x0 0x0 0x0 0x0 0x0 0x0 0x0
< Dump Card State Ends >>
DevQ(0:0:0): 0 waiting
DevQ(0:1:0): NMI Watchdog detected LOCKUP on CPU0CPU 0
Modules linked in: rawfs rtc evdev hw_random i2c_amd8111 tg3 e100 mii w83627hf
eeprom lm85 i2c_sensor i2c_isa i2c_amd756 i2c_core psmouse
Pid: 168, comm: scsi_eh_0 Not tainted 2.6.13-rc7-git1
RIP: 0010:[] {serial_in+105}
RSP: 0018:81007fc17b80 EFLAGS: 0002
RAX: RBX: RCX:
RDX: 03fd RSI: 0005 RDI: 80473a40
RBP: 2705 R08: 0020 R09: 7930
R10: 0034 R11: 000a R12: 80473a40
R13: 8045f6fe R14: 000d R15: 000d
FS: 2b3cbe90() GS:80485800() knlGS:556ada40
CS: 0010 DS: 0018 ES: 0018 CR0: 8005003b
CR2: 00515970 CR3: 7dc27000 CR4: 06e0
Process scsi_eh_0 (pid: 168, threadinfo 81007fc16000, task 8100033607c0)
Stack: 8026682d 00050002 803ebc60 7931
000d 0096 0010 0046
8012ed9c 793e
Call Trace:{serial8250_console_write+413}
{__call_console_drivers+76}
{release_console_sem+339}
{vprintk+601}
{vprintk+601} {printk+78}
{thread_return+0} {printk+78}
{ahd_print_register+261}
{ahd_platform_dump_card_state+100}
{ahd_dump_card_state+8973}
{ahd_linux_abort+624}
{ahd_linux_sem_timeout+0}
{scsi_error_handler+1324}
{child_rip+8} {scsi_error_handler+0}
{child_rip+0}
Code: 0f b6 c0 c3 66 66 90 41 57 49 89 f7 41 56 41 55 41 bd 00 01
console shuts up ...
<0>Kernel panic - not syncing: Aiee, killing interrupt handler!
I don't know if this is enough information for the developers to go on.
For me it's back to 2.6.12-mm1 *snif*
Danny
-
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: Linux-2.6.13-rc7
I Wrote:
After 53 hours and 31 minutes it crashed.
dth pts/1zaphod.dth.net Wed Aug 24 09:54 - crash (2+05:31)
reboot system boot 2.6.13-rc7 Wed Aug 24 09:51 (2+05:41)
Prior to this kernel it had been running 2.6.12-mm1 without problems:
reboot system boot 2.6.12-mm1 Sun Aug 14 12:13 (9+21:36)
I will now compile run rc7-git1.
RC7-GIT7 barfed on me after some 20 hours:
root ttyS0 Fri Aug 26 16:32 - crash (20:44)
reboot system boot 2.6.13-rc7-git1 Fri Aug 26 16:32 (20:59)
I managed to get some information from the serial console:
scsi0: SCBPTR == 0x55, SCB_NEXT == 0xff80, SCB_NEXT2 == 0xff6e
CDB 0 0 0 0 0 0
STACK: 0x10c 0x0 0x0 0x0 0x0 0x0 0x0 0x0
Dump Card State Ends
DevQ(0:0:0): 0 waiting
DevQ(0:1:0): NMI Watchdog detected LOCKUP on CPU0CPU 0
Modules linked in: rawfs rtc evdev hw_random i2c_amd8111 tg3 e100 mii w83627hf
eeprom lm85 i2c_sensor i2c_isa i2c_amd756 i2c_core psmouse
Pid: 168, comm: scsi_eh_0 Not tainted 2.6.13-rc7-git1
RIP: 0010:[802644f9] 802644f9{serial_in+105}
RSP: 0018:81007fc17b80 EFLAGS: 0002
RAX: RBX: RCX:
RDX: 03fd RSI: 0005 RDI: 80473a40
RBP: 2705 R08: 0020 R09: 7930
R10: 0034 R11: 000a R12: 80473a40
R13: 8045f6fe R14: 000d R15: 000d
FS: 2b3cbe90() GS:80485800() knlGS:556ada40
CS: 0010 DS: 0018 ES: 0018 CR0: 8005003b
CR2: 00515970 CR3: 7dc27000 CR4: 06e0
Process scsi_eh_0 (pid: 168, threadinfo 81007fc16000, task 8100033607c0)
Stack: 8026682d 00050002 803ebc60 7931
000d 0096 0010 0046
8012ed9c 793e
Call Trace:8026682d{serial8250_console_write+413}
8012ed9c{__call_console_drivers+76}
8012f053{release_console_sem+339}
8012fbc9{vprintk+601}
8012fbc9{vprintk+601} 8012fc3e{printk+78}
80325a40{thread_return+0} 8012fc3e{printk+78}
8028c235{ahd_print_register+261}
802abc34{ahd_platform_dump_card_state+100}
80296b0d{ahd_dump_card_state+8973}
802ad320{ahd_linux_abort+624}
802aa590{ahd_linux_sem_timeout+0}
80284f5c{scsi_error_handler+1324}
8010e396{child_rip+8} 80284a30{scsi_error_handler+0}
8010e38e{child_rip+0}
Code: 0f b6 c0 c3 66 66 90 41 57 49 89 f7 41 56 41 55 41 bd 00 01
console shuts up ...
0Kernel panic - not syncing: Aiee, killing interrupt handler!
I don't know if this is enough information for the developers to go on.
For me it's back to 2.6.12-mm1 *snif*
Danny
-
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: Linux-2.6.13-rc7
I hate responding to myself but it's necessary: RC7-GIT7 barfed on me after some 20 hours: complete serial console message before it reset is on: http://newsgate.newsserver.nl/kernel/ as is config-file. Hardware: AMD64 running pure-64 debian ony tyan motherboard with opteron 250 cpu. Danny - 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: Linux-2.6.13-rc7
Danny ter Haar <[EMAIL PROTECTED]> wrote: >Of course it will probably reboot just after sending this message. Me and my big mouth... If there is a god he is making fun of me right now ;-) After 53 hours and 31 minutes it crashed. dth pts/1zaphod.dth.net Wed Aug 24 09:54 - crash (2+05:31) reboot system boot 2.6.13-rc7 Wed Aug 24 09:51 (2+05:41) Prior to this kernel it had been running 2.6.12-mm1 without problems: reboot system boot 2.6.12-mm1 Sun Aug 14 12:13 (9+21:36) I will now compile & run rc7-git1. This machine has serial console but only for bootpurpose (no logging possible) Wil try and setup some telnet capture service to try and fetch error. Danny - 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: Linux-2.6.13-rc7
Linus Torvalds <[EMAIL PROTECTED]> wrote: > I really wanted to release a 2.6.13, but there's been enough changes >while we've been waiting for other issues to resolve that I think it's >best to do a -rc7 first. > >Most of the -rc7 changes are pretty trivial, either one-liners or >affecting some particular specific driver or unusual configuration. The >shortlog (appended) should give a pretty good idea of what's up. > > Linus OK, i tried rc7 on my newsgateway and so far it keeps running after 50+ hours of 200megabit in & 200 megabitoutgoing network traffic and sufficient storage to the scsi system. Of course it will probably reboot just after sending this message. If it stays up after 5 days of pounding it will get _my_ stamp of aproval ;-) -- Linux 2.6.13-rc7 ([EMAIL PROTECTED]) (gcc [can't parse]) #??? 1CPU [newsgate.(none)] Memory: TotalUsedFree Shared Buffers Mem: 2058040 2041552 16488 0 616 Swap:0 0 0 Bootup: Wed Aug 24 09:50:30 2005Load average: 3.39 3.25 3.16 2/80 12244 user : 5:06:34.95 10.0% page in :0 nice : 0:42:50.54 1.4% page out:0 system: 16:22:48.44 32.2% swap in :0 idle : 0:25:08.22 0.8% swap out:0 uptime: 2d 2:53:38.68 context :592311164 irq 0: 45792855 timer irq 12: 3 irq 1: 8 i8042 irq 24: 56420796 aic79xx irq 2: 0 cascade [4] irq 25: 479838182 aic79xx, eth3 irq 4: 369 serialirq 28:1007452070 acenic irq 8: 0 rtc -- Danny - 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: Linux-2.6.13-rc7
Linus Torvalds [EMAIL PROTECTED] wrote: I really wanted to release a 2.6.13, but there's been enough changes while we've been waiting for other issues to resolve that I think it's best to do a -rc7 first. Most of the -rc7 changes are pretty trivial, either one-liners or affecting some particular specific driver or unusual configuration. The shortlog (appended) should give a pretty good idea of what's up. Linus OK, i tried rc7 on my newsgateway and so far it keeps running after 50+ hours of 200megabit in 200 megabitoutgoing network traffic and sufficient storage to the scsi system. Of course it will probably reboot just after sending this message. If it stays up after 5 days of pounding it will get _my_ stamp of aproval ;-) -- Linux 2.6.13-rc7 ([EMAIL PROTECTED]) (gcc [can't parse]) #??? 1CPU [newsgate.(none)] Memory: TotalUsedFree Shared Buffers Mem: 2058040 2041552 16488 0 616 Swap:0 0 0 Bootup: Wed Aug 24 09:50:30 2005Load average: 3.39 3.25 3.16 2/80 12244 user : 5:06:34.95 10.0% page in :0 nice : 0:42:50.54 1.4% page out:0 system: 16:22:48.44 32.2% swap in :0 idle : 0:25:08.22 0.8% swap out:0 uptime: 2d 2:53:38.68 context :592311164 irq 0: 45792855 timer irq 12: 3 irq 1: 8 i8042 irq 24: 56420796 aic79xx irq 2: 0 cascade [4] irq 25: 479838182 aic79xx, eth3 irq 4: 369 serialirq 28:1007452070 acenic irq 8: 0 rtc -- Danny - 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: Linux-2.6.13-rc7
Danny ter Haar [EMAIL PROTECTED] wrote: Of course it will probably reboot just after sending this message. Me and my big mouth... If there is a god he is making fun of me right now ;-) After 53 hours and 31 minutes it crashed. dth pts/1zaphod.dth.net Wed Aug 24 09:54 - crash (2+05:31) reboot system boot 2.6.13-rc7 Wed Aug 24 09:51 (2+05:41) Prior to this kernel it had been running 2.6.12-mm1 without problems: reboot system boot 2.6.12-mm1 Sun Aug 14 12:13 (9+21:36) I will now compile run rc7-git1. This machine has serial console but only for bootpurpose (no logging possible) Wil try and setup some telnet capture service to try and fetch error. Danny - 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: 2.6.13-rcX really this bad ?
Alexey Dobriyan <[EMAIL PROTECTED]> wrote: >> Is the machine running X? We need some output from it so we can debug >> what's going on, the info should be printed to the console. It would >> be great if you could run the latest kernel and see if you get any >> output. Also add nmi_watchdog=2 to the boot command line. No, it's not running X. It's running debian (amd64) I allready posted more details http://newsgate.newsserver.nl/kernel/ including problems with SCSI. _my_ guess it's an IRQ problem (acpi related) ? >> You can also set up a serial console or netconsole to capture the output >> from the server with the help of another machine, described in >> Documentation/serial-console.txt >> Documentation/networking/netconsole.txt As stated before, it's connected to a sercon, but not with capture capabilities. I've a program that captured a few panics/resets >Danny, could you please go to http://bugme.osdl.org/show_bug.cgi?id=4982 >and fill new info there. I certainly will! >Alexander, could you please forward this email to Danny if you don't get >bounces from him. I got this when tried to reply that his bug was sucked >into bugzilla. > [EMAIL PROTECTED] >Technical details of permanent failure: >TEMP_FAILURE: Could not initiate SMTP conversation with any hosts: >[bitbucket.cistron.nl (100): Connection timed out] Ouch, wil look into this ... Danny [EMAIL PROTECTED] - 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/
2.6.13-rcX really this bad ?
I've posted a couple of times than my newsserver is not stable with any 2.6.13-rcX kernels. Last kernel that survived is 2.6.12-mm1 (18+days) Of course i can just stick with that kernel, but i thought it would be wise to live on the edge and run a reasonable loaded server with the latest/greatest. This ends in disaster though... These are last uptimes, all reset by panic on reset. reboot system boot 2.6.13-rc6-git5 Sun Aug 14 02:56(09:07) reboot system boot 2.6.13-rc6-git4 Fri Aug 12 16:50(1+19:13) reboot system boot 2.6.13-rc6-git3 Fri Aug 12 12:32(04:16) reboot system boot 2.6.13-rc6-git3 Thu Aug 11 13:18(1+03:29) reboot system boot 2.6.13-rc6-git2 Thu Aug 11 12:40(00:35) reboot system boot 2.6.13-rc6-git1 Wed Aug 10 13:24(23:52) reboot system boot 2.6.13-rc6 Wed Aug 10 02:46(10:35) reboot system boot 2.6.13-rc6 Mon Aug 8 16:52(1+20:29) reboot system boot 2.6.13-rc6 Sun Aug 7 22:07(2+15:14) Since i got no feedback on my previous posts, i either bring it the wrong way, or people don't care and i ought to shut up. I think however that just before releasing a new stable kernel these kind of feedback could be healthy to ironout some bugs. For now i'll switch back to 2.6.12-mm1 and follow this mailling list and try again when i the problems seem to have been solved. Danny - 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/
2.6.13-rcX really this bad ?
I've posted a couple of times than my newsserver is not stable with any 2.6.13-rcX kernels. Last kernel that survived is 2.6.12-mm1 (18+days) Of course i can just stick with that kernel, but i thought it would be wise to live on the edge and run a reasonable loaded server with the latest/greatest. This ends in disaster though... These are last uptimes, all reset by panic on reset. reboot system boot 2.6.13-rc6-git5 Sun Aug 14 02:56(09:07) reboot system boot 2.6.13-rc6-git4 Fri Aug 12 16:50(1+19:13) reboot system boot 2.6.13-rc6-git3 Fri Aug 12 12:32(04:16) reboot system boot 2.6.13-rc6-git3 Thu Aug 11 13:18(1+03:29) reboot system boot 2.6.13-rc6-git2 Thu Aug 11 12:40(00:35) reboot system boot 2.6.13-rc6-git1 Wed Aug 10 13:24(23:52) reboot system boot 2.6.13-rc6 Wed Aug 10 02:46(10:35) reboot system boot 2.6.13-rc6 Mon Aug 8 16:52(1+20:29) reboot system boot 2.6.13-rc6 Sun Aug 7 22:07(2+15:14) Since i got no feedback on my previous posts, i either bring it the wrong way, or people don't care and i ought to shut up. I think however that just before releasing a new stable kernel these kind of feedback could be healthy to ironout some bugs. For now i'll switch back to 2.6.12-mm1 and follow this mailling list and try again when i the problems seem to have been solved. Danny - 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: 2.6.13-rcX really this bad ?
Alexey Dobriyan [EMAIL PROTECTED] wrote: Is the machine running X? We need some output from it so we can debug what's going on, the info should be printed to the console. It would be great if you could run the latest kernel and see if you get any output. Also add nmi_watchdog=2 to the boot command line. No, it's not running X. It's running debian (amd64) I allready posted more details http://newsgate.newsserver.nl/kernel/ including problems with SCSI. _my_ guess it's an IRQ problem (acpi related) ? You can also set up a serial console or netconsole to capture the output from the server with the help of another machine, described in Documentation/serial-console.txt Documentation/networking/netconsole.txt As stated before, it's connected to a sercon, but not with capture capabilities. I've a program that captured a few panics/resets Danny, could you please go to http://bugme.osdl.org/show_bug.cgi?id=4982 and fill new info there. I certainly will! Alexander, could you please forward this email to Danny if you don't get bounces from him. I got this when tried to reply that his bug was sucked into bugzilla. [EMAIL PROTECTED] Technical details of permanent failure: TEMP_FAILURE: Could not initiate SMTP conversation with any hosts: [bitbucket.cistron.nl (100): Connection timed out] Ouch, wil look into this ... Danny [EMAIL PROTECTED] - 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: [GIT PATCH] final SCSI bug fixes before 2.6.13
James Bottomley <[EMAIL PROTECTED]> wrote: >This tree represents the final bug fixes, both for oopses seen by >various people. One is for the dual binding of the i2o drivers and the >other is for an oops adding and removing devices from the lpfc and >qlogic fibre drivers. > >The tree is at >www.kernel.org:/pub/scm/linux/kernel/git/jejb/scsi-rc-fixes-2.6.git Is this patch allready included in the 2.6.13-rc6-git1 patch ? I compiled/installed that kernel now over 6 hours ago reboot system boot 2.6.13-rc6-git1 Wed Aug 10 13:24 (06:04) Prior to that 2.6.13-rc6 crashed on me twice: reboot system boot 2.6.13-rc6 Mon Aug 8 16:52 (1+20:29) reboot system boot 2.6.13-rc6 Sun Aug 7 22:07 (2+15:14) Although it managed to receive 1.8 and sent 3.6TB in 24 hours! Danny - 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: [GIT PATCH] final SCSI bug fixes before 2.6.13
James Bottomley [EMAIL PROTECTED] wrote: This tree represents the final bug fixes, both for oopses seen by various people. One is for the dual binding of the i2o drivers and the other is for an oops adding and removing devices from the lpfc and qlogic fibre drivers. The tree is at www.kernel.org:/pub/scm/linux/kernel/git/jejb/scsi-rc-fixes-2.6.git Is this patch allready included in the 2.6.13-rc6-git1 patch ? I compiled/installed that kernel now over 6 hours ago reboot system boot 2.6.13-rc6-git1 Wed Aug 10 13:24 (06:04) Prior to that 2.6.13-rc6 crashed on me twice: reboot system boot 2.6.13-rc6 Mon Aug 8 16:52 (1+20:29) reboot system boot 2.6.13-rc6 Sun Aug 7 22:07 (2+15:14) Although it managed to receive 1.8 and sent 3.6TB in 24 hours! Danny - 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: Linux-2.6.13-rc6: aic7xxx testers please..
Linus Torvalds <[EMAIL PROTECTED]> wrote: >James and gang found the aic7xxx slowdown that happened after 2.6.12, and >we'd like to get particular testing that it's fixed, so if you have a >relevant machine, please do test this. with me, rc6 lasted 18 hours: reboot system boot 2.6.13-rc6 Mon Aug 8 16:52 (00:11) dth pts/0zaphod.dth.net Sun Aug 7 22:14 - crash (18:37) scsi1:0:14:0: Attempting to abort cmd 810038f6dd40: 0x2a 0x0 0x3 0x91 0x45 0x10 0x0 0x0 0x1 0x0 scsi1: At time of recovery, card was not paused >> Dump Card State Begins < scsi1: Dumping Card State at program address 0x13 Mode 0x11 Card was paused For more info regarding kern.log etc: http://newsgate.newsserver.nl/kernel/ 2.6.12-mm1 survived 18+ days ! Can it be something with acpi that somehow loses an interrupt ? This machine really does some heavy network/disktraffic. Danny - 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: rc5 seemed to kill a disk that rc4-mm1 likes. Also some X trouble.
Helge Hafting <[EMAIL PROTECTED]> wrote: >Danny ter Haar wrote: >>What i dont "get" is that ethernet also goes down when the scsi >>controller goes bezerk. >>I'm pretty sure it's not a hardware problem since 2.6.12-mm1 survives >>and brings this usenet host in the worldwide top 1000. >Interesting. >I have no idea what the core problem is, but one problem will often lead >to others. My scsi problem froze some apps that couldn't be paged in >from the "failing" disk, for example. I found out in the mean time that ethernet controller share the same IRQ, so it's even sort op logical i guess irq 25: aic79xx, eth3 (although ath0 was complaining) >rc5 is no good for amd64, and it doesn't need power management to go wrong. rc6 [KNOCK WOOD] seems to work just (so far) [EMAIL PROTECTED]:~$ procinfo Linux 2.6.13-rc6 ([EMAIL PROTECTED]) (gcc [can't parse]) #??? 1CPU [newsgate.(none)] Memory: TotalUsedFree Shared Buffers Mem: 2058040 2040104 17936 0 476 Swap:0 0 0 Bootup: Sun Aug 7 22:06:08 2005Load average: 3.62 3.64 3.55 4/66 1277 user : 1:44:42.21 10.8% page in :0 nice : 0:11:21.95 1.2% page out:0 system: 4:56:19.28 30.7% swap in :0 idle : 0:06:15.61 0.6% swap out:0 uptime: 16:06:08.94 context :169218538 irq 0: 14486202 timer irq 12: 3 irq 1: 8 i8042 irq 24: 18536343 aic79xx irq 2: 0 cascade [4] irq 25: 175472322 aic79xx, eth3 irq 4: 350 serialirq 28: 286219024 acenic --- Linux newsgate 2.6.13-rc6 #1 Sun Aug 7 21:27:42 CEST 2005 x86_64 GNU/Linux Gnu C 4.0.2 Gnu make 3.80 binutils 2.16.1 util-linux 2.12p mount 2.12p module-init-tools 3.2-pre1 e2fsprogs 1.38 reiserfsprogs line reiser4progs line nfs-utils 1.0.7 Linux C Library2.3.5 Dynamic linker (ldd) 2.3.2 Procps 3.2.5 Net-tools 1.60 Console-tools 0.2.3 Sh-utils 5.2.1 Modules Loaded genrtc evdev hw_random i2c_amd8111 tg3 e100 mii w83627hf eeprom lm85 i2c_sensor i2c_isa i2c_amd756 i2c_core rawfs psmouse Looks promissing. Danny - 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: rc5 seemed to kill a disk that rc4-mm1 likes. Also some X trouble.
Helge Hafting [EMAIL PROTECTED] wrote: Danny ter Haar wrote: What i dont get is that ethernet also goes down when the scsi controller goes bezerk. I'm pretty sure it's not a hardware problem since 2.6.12-mm1 survives and brings this usenet host in the worldwide top 1000. Interesting. I have no idea what the core problem is, but one problem will often lead to others. My scsi problem froze some apps that couldn't be paged in from the failing disk, for example. I found out in the mean time that ethernetscsi controller share the same IRQ, so it's even sort op logical i guess irq 25: aic79xx, eth3 (although ath0 was complaining) rc5 is no good for amd64, and it doesn't need power management to go wrong. rc6 [KNOCK WOOD] seems to work just (so far) [EMAIL PROTECTED]:~$ procinfo Linux 2.6.13-rc6 ([EMAIL PROTECTED]) (gcc [can't parse]) #??? 1CPU [newsgate.(none)] Memory: TotalUsedFree Shared Buffers Mem: 2058040 2040104 17936 0 476 Swap:0 0 0 Bootup: Sun Aug 7 22:06:08 2005Load average: 3.62 3.64 3.55 4/66 1277 user : 1:44:42.21 10.8% page in :0 nice : 0:11:21.95 1.2% page out:0 system: 4:56:19.28 30.7% swap in :0 idle : 0:06:15.61 0.6% swap out:0 uptime: 16:06:08.94 context :169218538 irq 0: 14486202 timer irq 12: 3 irq 1: 8 i8042 irq 24: 18536343 aic79xx irq 2: 0 cascade [4] irq 25: 175472322 aic79xx, eth3 irq 4: 350 serialirq 28: 286219024 acenic --- Linux newsgate 2.6.13-rc6 #1 Sun Aug 7 21:27:42 CEST 2005 x86_64 GNU/Linux Gnu C 4.0.2 Gnu make 3.80 binutils 2.16.1 util-linux 2.12p mount 2.12p module-init-tools 3.2-pre1 e2fsprogs 1.38 reiserfsprogs line reiser4progs line nfs-utils 1.0.7 Linux C Library2.3.5 Dynamic linker (ldd) 2.3.2 Procps 3.2.5 Net-tools 1.60 Console-tools 0.2.3 Sh-utils 5.2.1 Modules Loaded genrtc evdev hw_random i2c_amd8111 tg3 e100 mii w83627hf eeprom lm85 i2c_sensor i2c_isa i2c_amd756 i2c_core rawfs psmouse Looks promissing. Danny - 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: Linux-2.6.13-rc6: aic7xxx testers please..
Linus Torvalds [EMAIL PROTECTED] wrote: James and gang found the aic7xxx slowdown that happened after 2.6.12, and we'd like to get particular testing that it's fixed, so if you have a relevant machine, please do test this. with me, rc6 lasted 18 hours: reboot system boot 2.6.13-rc6 Mon Aug 8 16:52 (00:11) dth pts/0zaphod.dth.net Sun Aug 7 22:14 - crash (18:37) scsi1:0:14:0: Attempting to abort cmd 810038f6dd40: 0x2a 0x0 0x3 0x91 0x45 0x10 0x0 0x0 0x1 0x0 scsi1: At time of recovery, card was not paused Dump Card State Begins scsi1: Dumping Card State at program address 0x13 Mode 0x11 Card was paused For more info regarding kern.log etc: http://newsgate.newsserver.nl/kernel/ 2.6.12-mm1 survived 18+ days ! Can it be something with acpi that somehow loses an interrupt ? This machine really does some heavy network/disktraffic. Danny - 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: rc5 seemed to kill a disk that rc4-mm1 likes. Also some X trouble.
Andrew Morton <[EMAIL PROTECTED]> wrote: >Helge Hafting <[EMAIL PROTECTED]> wrote: >> 2.6.13-rc5 seemed to kill a scsi disk (sdb) for me, where 2.6.13-rc4-mm1 >> have no problems with the same disk. Sort of same with me: 2.6.12-mm1 runs for _weeks_ where others keep crashing: >The latest -git kernel (or 2.6.13-rc6 if it's there) with APCI enabled is >the one to test, please. no rc6 yet, i did however experience the following: reboot system boot 2.6.12-mm1 Sun Aug 7 18:20 (00:36) dth pts/1zaphod.dth.net Sun Aug 7 15:41 - crash (02:38) reboot system boot 2.6.13-rc5-git5 Sun Aug 7 14:04 (04:52) reboot system boot 2.6.13-rc5-git4 Sun Aug 7 10:05 (03:43) reboot system boot 2.6.13-rc5-git3 Fri Aug 5 16:55 (1+17:07) git3 lasted near 2 days git4 ran for nearly 5 hours than i upgraded to git5 didn't last longer than 2.5 hours Fortunatly some info was found in the log files. What i dont "get" is that ethernet also goes down when the scsi controller goes bezerk. I'm pretty sure it's not a hardware problem since 2.6.12-mm1 survives and brings this usenet host in the worldwide top 1000. >From the log files: scsi1: Transmission error detected LQISTAT1[0x8]:(LQICRCI_NLQ) LASTPHASE[0x1]:(P_DATAOUT|P_BUSFREE) SCSISIGI[0x60]:(P_DATAIN_DT) PERRDIAG[0x4]:(CRCERR) >> Dump Card State Begins < scsi1: Dumping Card State at program address 0x11 Mode 0x33 Card was paused HS_MAILBOX[0x0] INTCTL[0xc0]:(SWTMINTEN|SWTMINTMASK) SEQINTSTAT[0x10]:(SEQ_SWTMRTO) SAVED_MODE[0x11] DFFSTAT[0x24]:(CURRFIFO_0|FIFO1FREE) SCSISIGI[0xb6]:(P_MESGOUT|REQI|BSYI|ATNI) SCSIPHASE[0x4]:(MSG_OUT_PHASE) SCSIBUS[0xff] LASTPHASE[0x1]:(P_DATAOUT|P_BUSFREE) SCSISEQ0[0x0] SCSISEQ1[0x12]:(ENAUTOATNP|ENRSELI) SEQCTL0[0x0] SEQINTCTL[0x0] SEQ_FLAGS[0x0] SEQ_FLAGS2[0x0] SSTAT0[0x2]:(SPIORDY) SSTAT1[0x19]:(REQINIT|BUSFREE|PHASEMIS) SSTAT2[0x20]:(NONPACKREQ) SSTAT3[0x0] PERRDIAG[0x0] SIMODE1[0xa4]:(ENSCSIPERR|ENSCSIRST|ENSELTIMO) LQISTAT0[0x0] LQISTAT1[0x8]:(LQICRCI_NLQ) LQISTAT2[0xc0]:(LQIPHASE_OUTPKT|PACKETIZED) LQOSTAT0[0x0] LQOSTAT1[0x0] LQOSTAT2[0xe1]:(LQOSTOP0|LQOPKT) SCB Count = 128 CMDS_PENDING = 2 LASTSCB 0x34 CURRSCB 0x8 NEXTSCB 0xffc0 qinstart = 15426 qinfifonext = 15426 QINFIFO: WAITING_TID_QUEUES: Pending list: 8 FIFO_USE[0x0] SCB_CONTROL[0x60]:(TAG_ENB|DISCENB) SCB_SCSIID[0x47] 66 FIFO_USE[0x0] SCB_CONTROL[0x60]:(TAG_ENB|DISCENB) SCB_SCSIID[0x47] Total 2 Kernel Free SCB list: 53 94 52 127 115 73 21 114 63 37 22 117 93 92 64 1 41 88 43 121 68 50 91 46 122 56 80 30 104 116 34 48 7 105 3 39 58 81 112 119 28 27 62 4 17 120 24 103 0 49 101 106 32 47 75 69 11 95 42 65 96 14 67 72 89 108 13 36 125 44 51 71 20 54 38 90 82 85 31 59 76 60 6 97 33 5 124 16 25 111 18 15 19 87 107 23 123 99 110 10 84 29 100 74 55 118 40 9 126 113 12 61 77 98 79 109 2 78 102 57 70 35 83 45 86 26 Sequencer Complete DMA-inprog list: Sequencer Complete list: Sequencer DMA-Up and Complete list: scsi1: FIFO0 Active, LONGJMP == 0x232, SCB 0x42 SEQIMODE[0x3f]:(ENCFG4TCMD|ENCFG4ICMD|ENCFG4TSTAT|ENCFG4ISTAT|ENCFG4DATA|ENSAVEPTRS) SEQINTSRC[0x0] DFCNTRL[0x8]:(HDMAEN) DFSTATUS[0xc9]:(FIFOEMP|HDONE|PKT_PRELOAD_AVAIL|PRELOAD_AVAIL) SG_CACHE_SHADOW[0x78] SG_STATE[0x3]:(SEGS_AVAIL|LOADING_NEEDED) DFFSXFRCTL[0x0] SOFFCNT[0x0] MDFFSTAT[0x6]:(DATAINFIFO|DLZERO) SHADDR = 0x048b4000, SHCNT = 0x0 HADDR = 0x048b4000, HCNT = 0x0 CCSGCTL[0x10]:(SG_CACHE_AVAIL) scsi1: FIFO1 Free, LONGJMP == 0x8063, SCB 0x3 SEQIMODE[0x3f]:(ENCFG4TCMD|ENCFG4ICMD|ENCFG4TSTAT|ENCFG4ISTAT|ENCFG4DATA|ENSAVEPTRS) SEQINTSRC[0x0] DFCNTRL[0x0] DFSTATUS[0x89]:(FIFOEMP|HDONE|PRELOAD_AVAIL) SG_CACHE_SHADOW[0x2]:(LAST_SEG) SG_STATE[0x0] DFFSXFRCTL[0x0] SOFFCNT[0x0] MDFFSTAT[0x5]:(FIFOFREE|DLZERO) SHADDR = 0x00, SHCNT = 0x0 HADDR = 0x00, HCNT = 0x0 CCSGCTL[0x0] LQIN: 0x4 0x0 0x0 0x42 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x28 0x0 0x0 0x0 0x2 0x0 scsi1: LQISTATE = 0x2b, LQOSTATE = 0x0, OPTIONMODE = 0x52 scsi1: OS_SPACE_CNT = 0x20 MAXCMDCNT = 0x1 SIMODE0[0xc]:(ENOVERRUN|ENIOERR) CCSCBCTL[0x0] scsi1: REG0 == 0x42, SINDEX = 0x178, DINDEX = 0x10a scsi1: SCBPTR == 0x35, SCB_NEXT == 0xff00, SCB_NEXT2 == 0xff39 CDB 28 0 c 80 70 a4 STACK: 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 < Dump Card State Ends >> DevQ(0:4:0): 0 waiting DevQ(0:5:0): 0 waiting DevQ(0:14:0): 0 waiting DevQ(0:15:0): 0 waiting LQICRC_NLQ eth0: Optical link DOWN eth0: Optical link UP (Full Duplex, Flow Control: TX RX) scsi1: Unexpected PKT busfree condition >> Dump Card State Begins < scsi1: Dumping Card State at program address 0x11 Mode 0x33 Card was paused HS_MAILBOX[0x0] INTCTL[0xc0]:(SWTMINTEN|SWTMINTMASK) SEQINTSTAT[0x10]:(SEQ_SWTMRTO) SAVED_MODE[0x11] DFFSTAT[0x24]:(CURRFIFO_0|FIFO1FREE) SCSISIGI[0xb6]:(P_MESGOUT|REQI|BSYI|ATNI) SCSIPHASE[0x4]:(MSG_OUT_PHASE) SCSIBUS[0xff] LASTPHASE[0x1]:(P_DATAOUT|P_BUSFREE) SCSISEQ0[0x0]
Re: rc5 seemed to kill a disk that rc4-mm1 likes. Also some X trouble.
Andrew Morton [EMAIL PROTECTED] wrote: Helge Hafting [EMAIL PROTECTED] wrote: 2.6.13-rc5 seemed to kill a scsi disk (sdb) for me, where 2.6.13-rc4-mm1 have no problems with the same disk. Sort of same with me: 2.6.12-mm1 runs for _weeks_ where others keep crashing: The latest -git kernel (or 2.6.13-rc6 if it's there) with APCI enabled is the one to test, please. no rc6 yet, i did however experience the following: reboot system boot 2.6.12-mm1 Sun Aug 7 18:20 (00:36) dth pts/1zaphod.dth.net Sun Aug 7 15:41 - crash (02:38) reboot system boot 2.6.13-rc5-git5 Sun Aug 7 14:04 (04:52) reboot system boot 2.6.13-rc5-git4 Sun Aug 7 10:05 (03:43) reboot system boot 2.6.13-rc5-git3 Fri Aug 5 16:55 (1+17:07) git3 lasted near 2 days git4 ran for nearly 5 hours than i upgraded to git5 didn't last longer than 2.5 hours Fortunatly some info was found in the log files. What i dont get is that ethernet also goes down when the scsi controller goes bezerk. I'm pretty sure it's not a hardware problem since 2.6.12-mm1 survives and brings this usenet host in the worldwide top 1000. From the log files: scsi1: Transmission error detected LQISTAT1[0x8]:(LQICRCI_NLQ) LASTPHASE[0x1]:(P_DATAOUT|P_BUSFREE) SCSISIGI[0x60]:(P_DATAIN_DT) PERRDIAG[0x4]:(CRCERR) Dump Card State Begins scsi1: Dumping Card State at program address 0x11 Mode 0x33 Card was paused HS_MAILBOX[0x0] INTCTL[0xc0]:(SWTMINTEN|SWTMINTMASK) SEQINTSTAT[0x10]:(SEQ_SWTMRTO) SAVED_MODE[0x11] DFFSTAT[0x24]:(CURRFIFO_0|FIFO1FREE) SCSISIGI[0xb6]:(P_MESGOUT|REQI|BSYI|ATNI) SCSIPHASE[0x4]:(MSG_OUT_PHASE) SCSIBUS[0xff] LASTPHASE[0x1]:(P_DATAOUT|P_BUSFREE) SCSISEQ0[0x0] SCSISEQ1[0x12]:(ENAUTOATNP|ENRSELI) SEQCTL0[0x0] SEQINTCTL[0x0] SEQ_FLAGS[0x0] SEQ_FLAGS2[0x0] SSTAT0[0x2]:(SPIORDY) SSTAT1[0x19]:(REQINIT|BUSFREE|PHASEMIS) SSTAT2[0x20]:(NONPACKREQ) SSTAT3[0x0] PERRDIAG[0x0] SIMODE1[0xa4]:(ENSCSIPERR|ENSCSIRST|ENSELTIMO) LQISTAT0[0x0] LQISTAT1[0x8]:(LQICRCI_NLQ) LQISTAT2[0xc0]:(LQIPHASE_OUTPKT|PACKETIZED) LQOSTAT0[0x0] LQOSTAT1[0x0] LQOSTAT2[0xe1]:(LQOSTOP0|LQOPKT) SCB Count = 128 CMDS_PENDING = 2 LASTSCB 0x34 CURRSCB 0x8 NEXTSCB 0xffc0 qinstart = 15426 qinfifonext = 15426 QINFIFO: WAITING_TID_QUEUES: Pending list: 8 FIFO_USE[0x0] SCB_CONTROL[0x60]:(TAG_ENB|DISCENB) SCB_SCSIID[0x47] 66 FIFO_USE[0x0] SCB_CONTROL[0x60]:(TAG_ENB|DISCENB) SCB_SCSIID[0x47] Total 2 Kernel Free SCB list: 53 94 52 127 115 73 21 114 63 37 22 117 93 92 64 1 41 88 43 121 68 50 91 46 122 56 80 30 104 116 34 48 7 105 3 39 58 81 112 119 28 27 62 4 17 120 24 103 0 49 101 106 32 47 75 69 11 95 42 65 96 14 67 72 89 108 13 36 125 44 51 71 20 54 38 90 82 85 31 59 76 60 6 97 33 5 124 16 25 111 18 15 19 87 107 23 123 99 110 10 84 29 100 74 55 118 40 9 126 113 12 61 77 98 79 109 2 78 102 57 70 35 83 45 86 26 Sequencer Complete DMA-inprog list: Sequencer Complete list: Sequencer DMA-Up and Complete list: scsi1: FIFO0 Active, LONGJMP == 0x232, SCB 0x42 SEQIMODE[0x3f]:(ENCFG4TCMD|ENCFG4ICMD|ENCFG4TSTAT|ENCFG4ISTAT|ENCFG4DATA|ENSAVEPTRS) SEQINTSRC[0x0] DFCNTRL[0x8]:(HDMAEN) DFSTATUS[0xc9]:(FIFOEMP|HDONE|PKT_PRELOAD_AVAIL|PRELOAD_AVAIL) SG_CACHE_SHADOW[0x78] SG_STATE[0x3]:(SEGS_AVAIL|LOADING_NEEDED) DFFSXFRCTL[0x0] SOFFCNT[0x0] MDFFSTAT[0x6]:(DATAINFIFO|DLZERO) SHADDR = 0x048b4000, SHCNT = 0x0 HADDR = 0x048b4000, HCNT = 0x0 CCSGCTL[0x10]:(SG_CACHE_AVAIL) scsi1: FIFO1 Free, LONGJMP == 0x8063, SCB 0x3 SEQIMODE[0x3f]:(ENCFG4TCMD|ENCFG4ICMD|ENCFG4TSTAT|ENCFG4ISTAT|ENCFG4DATA|ENSAVEPTRS) SEQINTSRC[0x0] DFCNTRL[0x0] DFSTATUS[0x89]:(FIFOEMP|HDONE|PRELOAD_AVAIL) SG_CACHE_SHADOW[0x2]:(LAST_SEG) SG_STATE[0x0] DFFSXFRCTL[0x0] SOFFCNT[0x0] MDFFSTAT[0x5]:(FIFOFREE|DLZERO) SHADDR = 0x00, SHCNT = 0x0 HADDR = 0x00, HCNT = 0x0 CCSGCTL[0x0] LQIN: 0x4 0x0 0x0 0x42 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x28 0x0 0x0 0x0 0x2 0x0 scsi1: LQISTATE = 0x2b, LQOSTATE = 0x0, OPTIONMODE = 0x52 scsi1: OS_SPACE_CNT = 0x20 MAXCMDCNT = 0x1 SIMODE0[0xc]:(ENOVERRUN|ENIOERR) CCSCBCTL[0x0] scsi1: REG0 == 0x42, SINDEX = 0x178, DINDEX = 0x10a scsi1: SCBPTR == 0x35, SCB_NEXT == 0xff00, SCB_NEXT2 == 0xff39 CDB 28 0 c 80 70 a4 STACK: 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 Dump Card State Ends DevQ(0:4:0): 0 waiting DevQ(0:5:0): 0 waiting DevQ(0:14:0): 0 waiting DevQ(0:15:0): 0 waiting LQICRC_NLQ eth0: Optical link DOWN eth0: Optical link UP (Full Duplex, Flow Control: TX RX) scsi1: Unexpected PKT busfree condition Dump Card State Begins scsi1: Dumping Card State at program address 0x11 Mode 0x33 Card was paused HS_MAILBOX[0x0] INTCTL[0xc0]:(SWTMINTEN|SWTMINTMASK) SEQINTSTAT[0x10]:(SEQ_SWTMRTO) SAVED_MODE[0x11] DFFSTAT[0x24]:(CURRFIFO_0|FIFO1FREE) SCSISIGI[0xb6]:(P_MESGOUT|REQI|BSYI|ATNI) SCSIPHASE[0x4]:(MSG_OUT_PHASE) SCSIBUS[0xff] LASTPHASE[0x1]:(P_DATAOUT|P_BUSFREE) SCSISEQ0[0x0] SCSISEQ1[0x12]:(ENAUTOATNP|ENRSELI) SEQCTL0[0x0] SEQINTCTL[0x0] SEQ_FLAGS[0x0] SEQ_FLAGS2[0x0] SSTAT0[0x2]:(SPIORDY)
Re: 2.6.13-rc5-git2 does not boot on (my) amd64
Martin J. Bligh <[EMAIL PROTECTED]> wrote: > VM: killing process hotplug > Unable to handle kernel paging request at fff28017b5be RIP: > [] >-git3 works! whe! thanks guys. ACK! The newsgateway is pounding on git3 as well ;-) # procinfo Linux 2.6.13-rc5-git3 ([EMAIL PROTECTED]) Memory: TotalUsedFree Shared Buffers Mem: 2058040 2041800 16240 0 464 Swap:0 0 0 Bootup: Fri Aug 5 16:54:42 2005Load average: 3.10 3.29 3.31 1/65 9610 user : 0:10:28.91 8.7% page in :0 nice : 0:01:18.71 1.1% page out:0 system: 0:31:07.22 26.0% swap in :0 idle : 0:04:34.04 3.8% swap out:0 uptime: 1:59:55.23 context : 18646886 irq 0: 1795085 timer irq 12: 3 irq 1: 8 i8042 irq 24: 1981124 aic79xx irq 2: 0 cascade [4] irq 25: 17270208 aic79xx, eth3 irq 4: 771 serialirq 28: 3420 acenic Let's see if this survives longer than 30 hours ! ;-) Danny - 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: 2.6.13-rc5-git2 does not boot on (my) amd64
Martin J. Bligh [EMAIL PROTECTED] wrote: VM: killing process hotplug Unable to handle kernel paging request at fff28017b5be RIP: [fff28017b5be] -git3 works! whe! thanks guys. ACK! The newsgateway is pounding on git3 as well ;-) # procinfo Linux 2.6.13-rc5-git3 ([EMAIL PROTECTED]) Memory: TotalUsedFree Shared Buffers Mem: 2058040 2041800 16240 0 464 Swap:0 0 0 Bootup: Fri Aug 5 16:54:42 2005Load average: 3.10 3.29 3.31 1/65 9610 user : 0:10:28.91 8.7% page in :0 nice : 0:01:18.71 1.1% page out:0 system: 0:31:07.22 26.0% swap in :0 idle : 0:04:34.04 3.8% swap out:0 uptime: 1:59:55.23 context : 18646886 irq 0: 1795085 timer irq 12: 3 irq 1: 8 i8042 irq 24: 1981124 aic79xx irq 2: 0 cascade [4] irq 25: 17270208 aic79xx, eth3 irq 4: 771 serialirq 28: 3420 acenic Let's see if this survives longer than 30 hours ! ;-) Danny - 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/
2.6.13-rc5-git2 does not boot on (my) amd64
This is as far as it comes:
Freeing unused kernel memory: 248k freed
VM: killing process hotplug
VM: killing process hotplug
VM: killing process hotplug
VM: killing process hotplug
Unable to handle kernel paging request at fff28017b5be RIP:
[]
PGD 103027 PUD 0
Oops: 0010 [1]
CPU 0
Modules linked in:
Pid: 1, comm: init Not tainted 2.6.13-rc5-git2
RIP: 0010:[] []
RSP: :81007ffa3d38 EFLAGS: 00010296
RAX: RBX: 81007f450005 RCX: 0013
RDX: 81007ffe0ec0 RSI: 81007f42e560 RDI: 81007ffa3d48
RBP: R08: R09:
R10: 81007f463a90 R11: 81007f454130 R12: 81007fc639e8
R13: 81007ffa3ed8 R14: fff27f45 R15: 0310
FS: 2ae00640() GS:80485800() knlGS:
CS: 0010 DS: ES: CR0: 8005003b
CR2: fff28017b5be CR3: 7fc77000 CR4: 06e0
Process init (pid: 1, threadinfo 81007ffa2000, task 81007ffa14a0)
Stack: 00030029ab98 81007f450001 81007ffe0ec0 81007f42e560
0001 81007ffe0ec0 81007f45 8100033a8900
81007ffa3ed8 81007f45
Call Trace:{link_path_walk+135}
{get_unused_ fd+90}
{path_lookup+380} {open_namei+205}
{__vma_link+75} {filp_open+45}
{get_unused_fd+90} {sys_open+84}
{system_call+126}
Code: Bad RIP value.
RIP [] RSP
CR2: fff28017b5be
<0>Kernel panic - not syncing: Attempted to kill init!
<0>Rebooting in 30 seconds..
2.6.13-rc5 (vanilla) does work/boot but gave me scsi error after 24+ hours
(log/config file is @ http://newsgate.newsserver.nl/kernel )
Danny
-
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/
2.6.13-rc5-git2 does not boot on (my) amd64
This is as far as it comes:
Freeing unused kernel memory: 248k freed
VM: killing process hotplug
VM: killing process hotplug
VM: killing process hotplug
VM: killing process hotplug
Unable to handle kernel paging request at fff28017b5be RIP:
[fff28017b5be]
PGD 103027 PUD 0
Oops: 0010 [1]
CPU 0
Modules linked in:
Pid: 1, comm: init Not tainted 2.6.13-rc5-git2
RIP: 0010:[fff28017b5be] [fff28017b5be]
RSP: :81007ffa3d38 EFLAGS: 00010296
RAX: RBX: 81007f450005 RCX: 0013
RDX: 81007ffe0ec0 RSI: 81007f42e560 RDI: 81007ffa3d48
RBP: R08: R09:
R10: 81007f463a90 R11: 81007f454130 R12: 81007fc639e8
R13: 81007ffa3ed8 R14: fff27f45 R15: 0310
FS: 2ae00640() GS:80485800() knlGS:
CS: 0010 DS: ES: CR0: 8005003b
CR2: fff28017b5be CR3: 7fc77000 CR4: 06e0
Process init (pid: 1, threadinfo 81007ffa2000, task 81007ffa14a0)
Stack: 00030029ab98 81007f450001 81007ffe0ec0 81007f42e560
0001 81007ffe0ec0 81007f45 8100033a8900
81007ffa3ed8 81007f45
Call Trace:8017bff7{link_path_walk+135}
8016bd2a{get_unused_ fd+90}
8017c57c{path_lookup+380} 8017d7ed{open_namei+205}
8015f68b{__vma_link+75} 8016cb1d{filp_open+45}
8016bd2a{get_unused_fd+90} 8016cbd4{sys_open+84}
8010d91e{system_call+126}
Code: Bad RIP value.
RIP [fff28017b5be] RSP 81007ffa3d38
CR2: fff28017b5be
0Kernel panic - not syncing: Attempted to kill init!
0Rebooting in 30 seconds..
2.6.13-rc5 (vanilla) does work/boot but gave me scsi error after 24+ hours
(log/config file is @ http://newsgate.newsserver.nl/kernel )
Danny
-
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/
busy usenet server: only stable kernel is 2.6.12-mm1, rest (including 2.6.13-rc4*) barfs within a few days
I'm going nuts... A tyan AMD64 opteron machine functioning as a usenet gateway really pumps some traffic a day (http://newsgate.newsserver.nl) Incoming traffic comes through a optical gig-E card (acenic) and local traffic is fed to our spool boxes through cupper gig-E (tigon3). Machine uses adaptec onboard scsi disks. At first i thought i had a hardware problem since no kernel would survive longer than 30 hours. Ofcourse i ran memtest for a couple of days. Than i compiled 2.6.12-mm1 and this kernel surviced 18 days without a problem. But of course you now and then want to try bigger(tm) kernels ;-) reboot system boot 2.6.12-mm1 Sun Jul 31 09:47 (01:48) reboot system boot 2.6.13-rc4-git2 Sat Jul 30 18:29 (17:07) reboot system boot 2.6.12-mm1 Sat Jul 30 14:12 (04:14) reboot system boot 2.6.13-rc4 Fri Jul 29 14:16(1+04:10) reboot system boot 2.6.13-rc3-mm3 Fri Jul 29 12:17 (01:50) reboot system boot 2.6.12-mm1 Thu Jul 28 00:06(1+12:09) reboot system boot 2.6.13-rc3-mm2 Wed Jul 27 22:27 (01:36) reboot system boot 2.6.13-rc3-mm1 Wed Jul 27 11:22 (12:41) reboot system boot 2.6.12-mm1 Sun Jul 17 15:51(9+19:29) Machine dus have serial console (and remote powerboot) but no logging posibility (portmaster1). When it crashes i think most of the times it has something to do with IRQ. 2.6.13-rc4-git2 stopped working with the following notice: Jul 31 03:28:18 newsgate kernel: hw tcp v4 csum failed Jul 31 05:56:59 newsgate kernel: NETDEV WATCHDOG: eth3: transmit timed out Jul 31 05:56:59 newsgate kernel: tg3: eth3: transmit timed out, resetting Serial console kept spitting those messages but it gave no prompt anymore. remote powercycle was needed to get it back. More info/config can be found at: http://newsgate.newsserver.nl/kernel/ Any feedback/suggestions welcome. Danny - 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/
busy usenet server: only stable kernel is 2.6.12-mm1, rest (including 2.6.13-rc4*) barfs within a few days
I'm going nuts... A tyan AMD64 opteron machine functioning as a usenet gateway really pumps some traffic a day (http://newsgate.newsserver.nl) Incoming traffic comes through a optical gig-E card (acenic) and local traffic is fed to our spool boxes through cupper gig-E (tigon3). Machine uses adaptec onboard scsi disks. At first i thought i had a hardware problem since no kernel would survive longer than 30 hours. Ofcourse i ran memtest for a couple of days. Than i compiled 2.6.12-mm1 and this kernel surviced 18 days without a problem. But of course you now and then want to try biggerbetter(tm) kernels ;-) reboot system boot 2.6.12-mm1 Sun Jul 31 09:47 (01:48) reboot system boot 2.6.13-rc4-git2 Sat Jul 30 18:29 (17:07) reboot system boot 2.6.12-mm1 Sat Jul 30 14:12 (04:14) reboot system boot 2.6.13-rc4 Fri Jul 29 14:16(1+04:10) reboot system boot 2.6.13-rc3-mm3 Fri Jul 29 12:17 (01:50) reboot system boot 2.6.12-mm1 Thu Jul 28 00:06(1+12:09) reboot system boot 2.6.13-rc3-mm2 Wed Jul 27 22:27 (01:36) reboot system boot 2.6.13-rc3-mm1 Wed Jul 27 11:22 (12:41) reboot system boot 2.6.12-mm1 Sun Jul 17 15:51(9+19:29) Machine dus have serial console (and remote powerboot) but no logging posibility (portmaster1). When it crashes i think most of the times it has something to do with IRQ. 2.6.13-rc4-git2 stopped working with the following notice: Jul 31 03:28:18 newsgate kernel: hw tcp v4 csum failed Jul 31 05:56:59 newsgate kernel: NETDEV WATCHDOG: eth3: transmit timed out Jul 31 05:56:59 newsgate kernel: tg3: eth3: transmit timed out, resetting Serial console kept spitting those messages but it gave no prompt anymore. remote powercycle was needed to get it back. More info/config can be found at: http://newsgate.newsserver.nl/kernel/ Any feedback/suggestions welcome. Danny - 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: Linux 2.4.6-preX and MediaGX
Thibaut LAURENT <[EMAIL PROTECTED]> wrote: >Any idea ? Try without APIC support compiled into the kernel. I've seen too many different setup's barf on that! ;-) Danny -- Holland Hosting www.hoho.nl [EMAIL PROTECTED] - 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: Linux 2.4.6-preX and MediaGX
Thibaut LAURENT [EMAIL PROTECTED] wrote: Any idea ? Try without APIC support compiled into the kernel. I've seen too many different setup's barf on that! ;-) Danny -- Holland Hosting www.hoho.nl [EMAIL PROTECTED] - 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: halting does not shutdown with 2.4.6pre3 (neither on 2.4.5-acxx)
<[EMAIL PROTECTED]> wrote: >with 2.4.6pre3 or not. I have >also applied the latest patch from reiserfs.org >I have intel i810, celeron 566, 384MB i also use reiserfs (only) on my systems and experience samen problems with 2.4.5-ac11 and up. Somehow the machine seems to "hang" on unmounting the filessystems. I'm happy to have RemotePowerBoots on some machines ;-) Danny -- Holland Hosting www.hoho.nl [EMAIL PROTECTED] - 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: halting does not shutdown with 2.4.6pre3 (neither on 2.4.5-acxx)
[EMAIL PROTECTED] wrote: with 2.4.6pre3 or not. I have also applied the latest patch from reiserfs.org I have intel i810, celeron 566, 384MB i also use reiserfs (only) on my systems and experience samen problems with 2.4.5-ac11 and up. Somehow the machine seems to hang on unmounting the filessystems. I'm happy to have RemotePowerBoots on some machines ;-) Danny -- Holland Hosting www.hoho.nl [EMAIL PROTECTED] - 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/
www.bzimage.org: bad intermediate patch 2.4.5-ac9-ac10
We had for an hour or so a bad intermediate diff going from kernel 2.4.5-ac9 to ac10. The size of the patch was 800+ kilobyte. The new "good" one is about 163 kilobyte. If you try to apply the wrong patch, it complains about scsidrivers beeing reversed. Sorry for the troubles. Danny -- Holland Hosting www.hoho.nl [EMAIL PROTECTED] - 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/
www.bzimage.org: bad intermediate patch 2.4.5-ac9-ac10
We had for an hour or so a bad intermediate diff going from kernel 2.4.5-ac9 to ac10. The size of the patch was 800+ kilobyte. The new good one is about 163 kilobyte. If you try to apply the wrong patch, it complains about scsidrivers beeing reversed. Sorry for the troubles. Danny -- Holland Hosting www.hoho.nl [EMAIL PROTECTED] - 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: Intellimouse in 2.4.5-ac7
Robert Love <[EMAIL PROTECTED]> wrote: >i am running ac7 right now (and was running ac6 with the patch) and my >IntelliMouse works fine. SOmetimes my laptop doesn't see my intellithingy as well (ac5) Reconnecting the mouse helpes to force recognising it. Mayby the same with ac6 ? Danny -- Holland Hosting www.hoho.nl [EMAIL PROTECTED] - 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: Intellimouse in 2.4.5-ac7
Robert Love [EMAIL PROTECTED] wrote: i am running ac7 right now (and was running ac6 with the patch) and my IntelliMouse works fine. SOmetimes my laptop doesn't see my intellithingy as well (ac5) Reconnecting the mouse helpes to force recognising it. Mayby the same with ac6 ? Danny -- Holland Hosting www.hoho.nl [EMAIL PROTECTED] - 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: international patches from kerneli far behind
L Larssen <[EMAIL PROTECTED]> wrote: >At this moment the latest patches are 2.2.18.3 and 2.4.3.1 while the kernel at >now is at 2.2.19 and 2.4.5. I try and keep a crypto up-to-date with the latest ac-tree: www.bzimage.org/kernel-patches/v2.4/alan/v2.4.5/ currently: against 2.4.5-ac6 (268 kilobyte) Will make an entry in the main page of www.bzimage.org next week. Danny -- Holland Hosting www.hoho.nl [EMAIL PROTECTED] - 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: ethernet still quits
Jeff Garzik <[EMAIL PROTECTED]> wrote: >Working on the problem. You'll need to downgrade the 8139too driver to >the current 'ac' patches or a previous version on >http://sf.net/projects/gkernel/ temporarily. also on : www.bzimage.org/kernel-patches/v2.4/alan/v2.4.5/ 8139_too_work.c (62kB) And also there: patch-2.4.5-ac6-crypto.bz2 (268kB) Danny -- Holland Hosting www.hoho.nl [EMAIL PROTECTED] - 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: ethernet still quits
Jeff Garzik [EMAIL PROTECTED] wrote: Working on the problem. You'll need to downgrade the 8139too driver to the current 'ac' patches or a previous version on http://sf.net/projects/gkernel/ temporarily. also on : www.bzimage.org/kernel-patches/v2.4/alan/v2.4.5/ 8139_too_work.c (62kB) And also there: patch-2.4.5-ac6-crypto.bz2 (268kB) Danny -- Holland Hosting www.hoho.nl [EMAIL PROTECTED] - 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: international patches from kerneli far behind
L Larssen [EMAIL PROTECTED] wrote: At this moment the latest patches are 2.2.18.3 and 2.4.3.1 while the kernel at now is at 2.2.19 and 2.4.5. I try and keep a crypto up-to-date with the latest ac-tree: www.bzimage.org/kernel-patches/v2.4/alan/v2.4.5/ currently: against 2.4.5-ac6 (268 kilobyte) Will make an entry in the main page of www.bzimage.org next week. Danny -- Holland Hosting www.hoho.nl [EMAIL PROTECTED] - 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: BUG REPORT: 2.4.4 hang on large network transfers with RTL-8139
Anton Voloshin <[EMAIL PROTECTED]> wrote: >2.4.3 works Ok, 2.4.4 and 2.4.5 both has this problem. >Lamer's assumption: maybe troubles with sendfile() after zero-copy patches? no, the patch in 2.4.3-ac7 caused a lot of problems for a lot of people. Simply compile 8139too.c from an old kernel on to the latest/greatest and you have best of both worlds ;-) People are working on this issue! Danny -- Holland Hosting www.hoho.nl [EMAIL PROTECTED] - 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: BUG REPORT: 2.4.4 hang on large network transfers with RTL-8139
Anton Voloshin [EMAIL PROTECTED] wrote: 2.4.3 works Ok, 2.4.4 and 2.4.5 both has this problem. Lamer's assumption: maybe troubles with sendfile() after zero-copy patches? no, the patch in 2.4.3-ac7 caused a lot of problems for a lot of people. Simply compile 8139too.c from an old kernel on to the latest/greatest and you have best of both worlds ;-) People are working on this issue! Danny -- Holland Hosting www.hoho.nl [EMAIL PROTECTED] - 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: Linux 2.4.4-ac7
In article <[EMAIL PROTECTED]>, >is the EXTRAVERSION set properly in Makefile? I use the http://www.bzim= >age.org >intermediate diff (chosen ~40K to ~2M) from ac6 nd I still have >2.4.4-ac6 login prompt (and Makefile says: EXTRAVERSION =3D -ac6). >From the original patch (agains vanilla 2.4.4) diff -u --new-file --recursive --exclude-from /usr/src/exclude linux.vanilla/Make file linux.ac/Makefile --- linux.vanilla/Makefile Mon Apr 30 15:13:07 2001 +++ linux.ac/Makefile Wed May 9 21:45:31 2001 @@ -1,11 +1,18 @@ VERSION = 2 PATCHLEVEL = 4 SUBLEVEL = 4 -EXTRAVERSION = +EXTRAVERSION = -ac6 So yeah, Alan forgot to increment the Makefile I happen to make the intermediate diffs on bzimage.org by hand. If i bump it now, next patch won't apply clean. So i'll leave it like this. ;-) Danny -- Holland Hosting www.hoho.nl [EMAIL PROTECTED] - 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: Linux 2.4.4-ac7
In article [EMAIL PROTECTED], is the EXTRAVERSION set properly in Makefile? I use the http://www.bzim= age.org intermediate diff (chosen ~40K to ~2M) from ac6 nd I still have 2.4.4-ac6 login prompt (and Makefile says: EXTRAVERSION =3D -ac6). From the original patch (agains vanilla 2.4.4) diff -u --new-file --recursive --exclude-from /usr/src/exclude linux.vanilla/Make file linux.ac/Makefile --- linux.vanilla/Makefile Mon Apr 30 15:13:07 2001 +++ linux.ac/Makefile Wed May 9 21:45:31 2001 @@ -1,11 +1,18 @@ VERSION = 2 PATCHLEVEL = 4 SUBLEVEL = 4 -EXTRAVERSION = +EXTRAVERSION = -ac6 So yeah, Alan forgot to increment the Makefile I happen to make the intermediate diffs on bzimage.org by hand. If i bump it now, next patch won't apply clean. So i'll leave it like this. ;-) Danny -- Holland Hosting www.hoho.nl [EMAIL PROTECTED] - 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: 2.4.4-ac[356]: network (8139too) related crashes
Andris Pavenis <[EMAIL PROTECTED]> wrote: >With kernels 2.4.4-ac[356] I'm getting system freezing on FTP transfer after >some time. I'm trying to upload about 6.5Mb file using MC (transfer speed > about 300-1000Kb/s). With these kernel versions I'm getting random total >freezing system (no any kernel error messages, no reaction to keyboard, > no response to ping from other machine). The same seems to happen also >when transfer speed is slower (I left wget downloading many files 2 nights > and both times system was hanged in morning) I have similar problems on my sony vaio laptop (pcmcia ethernet card that works with the 8139too driver) I send detailed info to Jeff & Alan weeks ago. >Kernel 2.4.3-ac3 seems to be Ok. Problems started with the change in 2.4.3-ac7. So up to 2.4.3-ac6 it's fine. >PS. I'm not subscribed to kernel mailing list If you post it here, read it here! Danny -- Holland Hosting www.hoho.nl [EMAIL PROTECTED] - 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: 2.4.4-ac[356]: network (8139too) related crashes
Andris Pavenis [EMAIL PROTECTED] wrote: With kernels 2.4.4-ac[356] I'm getting system freezing on FTP transfer after some time. I'm trying to upload about 6.5Mb file using MC (transfer speed about 300-1000Kb/s). With these kernel versions I'm getting random total freezing system (no any kernel error messages, no reaction to keyboard, no response to ping from other machine). The same seems to happen also when transfer speed is slower (I left wget downloading many files 2 nights and both times system was hanged in morning) I have similar problems on my sony vaio laptop (pcmcia ethernet card that works with the 8139too driver) I send detailed info to Jeff Alan weeks ago. Kernel 2.4.3-ac3 seems to be Ok. Problems started with the change in 2.4.3-ac7. So up to 2.4.3-ac6 it's fine. PS. I'm not subscribed to kernel mailing list If you post it here, read it here! Danny -- Holland Hosting www.hoho.nl [EMAIL PROTECTED] - 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: Linux 2.4.3-ac2
In article <9ae3qj$pc9$[EMAIL PROTECTED]>, I wrote: >It's still done manually, and now with the 2.4.3 series we >have to adjust the scripts a bit. Scripts adjusted, time for some sleep ;-) Danny -- Holland Hosting www.hoho.nl [EMAIL PROTECTED] - 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: Linux 2.4.3-ac2
Miles Lane <[EMAIL PROTECTED]> wrote: >You still have the URL for www.bzimage.org in this announcement, >but there are no incremental patches there for either 2.4.3-ac1 >or 2.4.3-ac2. They're made as i type ;-) It's still done manually, and now with the 2.4.3 series we have to adjust the scripts a bit. For now look at the "overview" link and follow the 2.4.3 link. Regards, Danny -- Holland Hosting www.hoho.nl [EMAIL PROTECTED] - 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: Linux 2.4.3-ac2
Miles Lane [EMAIL PROTECTED] wrote: You still have the URL for www.bzimage.org in this announcement, but there are no incremental patches there for either 2.4.3-ac1 or 2.4.3-ac2. They're made as i type ;-) It's still done manually, and now with the 2.4.3 series we have to adjust the scripts a bit. For now look at the "overview" link and follow the 2.4.3 link. Regards, Danny -- Holland Hosting www.hoho.nl [EMAIL PROTECTED] - 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: Linux 2.4.3-ac2
In article 9ae3qj$pc9$[EMAIL PROTECTED], I wrote: It's still done manually, and now with the 2.4.3 series we have to adjust the scripts a bit. Scripts adjusted, time for some sleep ;-) Danny -- Holland Hosting www.hoho.nl [EMAIL PROTECTED] - 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: Where's Alan?
alterity <[EMAIL PROTECTED]> wrote: >Haven't seen a post for sometime from the usually prolific Mr Cox. >What's the gossip? Don't worry, missed him as well, but he's been posting comments since yesterday. His personal webpage hasn't been updated since 13th of this month though... Danny -- Holland Hosting www.hoho.nl [EMAIL PROTECTED] - 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: making menuconfig on a 2.4.2-ac6 kernel :-)
Lombardo, Federico <[EMAIL PROTECTED]> wrote: >Please report alan :-) patch has already been posted here. Incremental ac patches are available at: www.bzimage.org ac5-ac6 is patched with right EXTRAVERSION and make menuconfig patch. Danny - 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: making menuconfig on a 2.4.2-ac6 kernel :-)
Lombardo, Federico [EMAIL PROTECTED] wrote: Please report alan :-) patch has already been posted here. Incremental ac patches are available at: www.bzimage.org ac5-ac6 is patched with right EXTRAVERSION and make menuconfig patch. Danny - 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: Linux 2.4.2-ac4
Alan Cox <[EMAIL PROTECTED]> wrote: > For the moment get it from > ftp://ftp.linux.org.uk/pub/linux/alan/2.4-ac or get it from: www.bzimage.org/kernel-patches/alan/v2.4.2 where also incremental patches are available eg: 94691 Feb 26 07:41 patch-2.4.2-ac3-ac4.bz2 Danny - 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: Linux 2.4.2-ac4
Alan Cox [EMAIL PROTECTED] wrote: For the moment get it from ftp://ftp.linux.org.uk/pub/linux/alan/2.4-ac or get it from: www.bzimage.org/kernel-patches/alan/v2.4.2 where also incremental patches are available eg: 94691 Feb 26 07:41 patch-2.4.2-ac3-ac4.bz2 Danny - 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: PRoblem with pcnet32 under 2.4.0 , was :Drivers under 2.4
I experimented some further today. using some printk i found out is was setting Fullduplex, hardcoded that to half-duplex (mine is connected to a hub and not a switch) , and it's configuration was 100Mbit as it was supposed to. Then i started looking at the start_xmit code and got lost :-))) Hope this helpes to pin-point the problem. Danny - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: PRoblem with pcnet32 under 2.4.0 , was :Drivers under 2.4
I experimented some further today. using some printk i found out is was setting Fullduplex, hardcoded that to half-duplex (mine is connected to a hub and not a switch) , and it's configuration was 100Mbit as it was supposed to. Then i started looking at the start_xmit code and got lost :-))) Hope this helpes to pin-point the problem. Danny - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: PRoblem with pcnet32 under 2.4.0 , was :Drivers under 2.4
Hans Grobler <[EMAIL PROTECTED]> wrote: >> lspci -vx output: >What about the other devices? ok, here's the full listing : 00:00.0 Host bridge: Cyrix Corporation PCI Master Flags: bus master, medium devsel, latency 0 00: 78 10 01 00 07 00 80 02 00 00 00 06 00 00 00 00 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00:0e.0 VGA compatible controller: Intergraphics Systems CyberPro 5000 (rev 02) (prog-if 00 [VGA]) Subsystem: Unknown device 0280:7000 Flags: medium devsel, IRQ 11 Memory at fd00 (32-bit, non-prefetchable) [size=16M] Expansion ROM at [disabled] [size=64K] 00: ea 10 00 50 03 00 00 02 02 00 00 03 04 40 00 00 10: 00 00 00 fd 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 80 02 00 70 30: 00 00 00 00 00 00 00 00 00 00 00 00 0b 01 00 00 00:0f.0 Ethernet controller: Advanced Micro Devices [AMD] 79c970 [PCnet LANCE] ( rev 42) Subsystem: Advanced Micro Devices [AMD]: Unknown device 2000 Flags: bus master, medium devsel, latency 64, IRQ 9 I/O ports at fce0 [size=32] Memory at fedffc00 (32-bit, non-prefetchable) [size=32] Expansion ROM at [disabled] [size=1M] Capabilities: [40] Power Management version 1 00: 22 10 00 20 07 00 90 02 42 00 00 02 00 40 00 00 10: e1 fc 00 00 00 fc df fe 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 22 10 00 20 30: 00 00 00 00 40 00 00 00 00 00 00 00 09 01 18 18 00:12.1 Bridge: Cyrix Corporation 5530 SMI [Kahlua] Flags: medium devsel Memory at 40012000 (32-bit, non-prefetchable) [size=256] 00: 78 10 01 01 02 00 80 02 00 00 80 06 00 00 00 00 10: 00 20 01 40 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00:12.2 IDE interface: Cyrix Corporation 5530 IDE [Kahlua] (prog-if 00 []) Flags: medium devsel I/O ports at fc00 [size=16] 00: 78 10 02 01 01 00 80 02 00 00 01 01 00 00 00 00 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20: 01 fc 00 00 00 00 00 00 00 00 00 00 00 00 00 00 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00:12.3 Multimedia audio controller: Cyrix Corporation 5530 Audio [Kahlua] Flags: bus master, medium devsel, latency 0 Memory at 40011000 (32-bit, non-prefetchable) [size=128] 00: 78 10 03 01 06 00 80 02 00 00 01 04 00 00 00 00 10: 00 10 01 40 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00:13.0 USB Controller: Compaq Computer Corporation: Unknown device a0f8 (rev 06 ) (prog-if 10 [OHCI]) Subsystem: Compaq Computer Corporation: Unknown device a0f8 Flags: medium devsel, IRQ 10 Memory at fedfe000 (32-bit, non-prefetchable) [size=4K] 00: 11 0e f8 a0 13 00 80 02 06 10 03 0c 00 40 00 00 10: 00 e0 df fe 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 11 0e f8 a0 30: 00 00 00 00 00 00 00 00 00 00 00 00 0a 01 00 50 00:14.0 Multimedia video controller: Zoran
PRoblem with pcnet32 under 2.4.0 , was :Drivers under 2.4
According to Hans Grobler: > If you're willing, would you please follow "REPORTING-BUGS" and send some > more info. Also cat /proc/interrupts. This one's intriging... In short: Cyrix Multimedia box Everything onboard, including ethernet. Works as supposed to under 2.2.x (including 2.2.19pre7) installing 2.4.0 kernel recognises the driver but no byte is passed over the ethernet. Kernel: Linux version 2.4.0-ac7 (root@multimedia) (gcc version 2.95.3 20001229 (prerelea se)) #2 Fri Jan 12 11:17:47 CET 2001 Distribution: Debian unstable (sid) Output of loading the pcnet32 module: pcnet32_probe_pci: found device 0x001022.0x002000 ioaddr=0x00fce0 resource_flags=0x000101 PCI: Found IRQ 9 for device 00:0f.0 eth0: PCnet/FAST III 79C973 at 0xfce0, 00 00 e2 24 41 1d pcnet32: pcnet32_private lp=c3c42000 lp_dma_addr=0x3c42000 assigned IRQ 9. pcnet32.c:v1.25kf 26.9.1999 [EMAIL PROTECTED] lspci -vx output: 00:0f.0 Ethernet controller: Advanced Micro Devices [AMD] 79c970 [PCnet LANCE] ( rev 42) Subsystem: Advanced Micro Devices [AMD]: Unknown device 2000 Flags: bus master, medium devsel, latency 64, IRQ 9 I/O ports at fce0 [size=32] Memory at fedffc00 (32-bit, non-prefetchable) [size=32] Expansion ROM at [disabled] [size=1M] Capabilities: [40] Power Management version 1 00: 22 10 00 20 07 00 90 02 42 00 00 02 00 40 00 00 10: e1 fc 00 00 00 fc df fe 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 22 10 00 20 30: 00 00 00 00 40 00 00 00 00 00 00 00 09 01 18 18 The machine is connected to a 3com 8ports 100Mbit hub no additional parameters when the module is loaded, except i tried debug=7 which gave verbose output After bootup this is the situation: multimedia:~# ifconfig eth0 Link encap:Ethernet HWaddr 00:00:E2:24:41:1D inet addr:192.168.1.51 Bcast:192.168.1.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:100 Interrupt:9 Base address:0xfce0 procinfo: multimedia:~# procinfo Linux 2.4.0-ac7 (root@multimedia) (gcc 2.95.3 20001229 ) #2 Fri Jan 12 11:17:47 CET 2001 1CPU [multimedia.(none)] Memory: TotalUsedFree Shared Buffers Cached Mem: 62308 12596 49712 0 6366636 Swap: 184708 0 184708 Bootup: Fri Jan 12 12:30:22 2001Load average: 0.02 0.03 0.01 1/28 229 user : 0:00:05.32 3.2% page in : 5744 nice : 0:00:00.00 0.0% page out: 354 system: 0:00:09.31 5.5% swap in :1 idle : 0:02:33.77 91.3% swap out:0 uptime: 0:02:48.38 context : 2940 irq 0: 16840 timer irq 9: 0 acpi, PCnet/FAST III irq 1: 3 keyboard irq 12: 0 PS/2 Mouse irq 2: 0 cascade [4] irq 14: 1640 ide0 irq 4: 127 serialirq 15: 3 ide1 irq 8: 1 rtc after trying to ping -c10 a host in it's own range (default gw in fact): Jan 12 12:30:36 multimedia kernel: eth0: pcnet32_open() irq 9 tx/rx rings 0x3c41 200/0x3c41000 init 0x3c41300. Jan 12 12:30:36 multimedia kernel: eth0: pcnet32 open after 5 ticks, init block 0x3c41300 csr0 01f3. Jan 12 12:30:38 multimedia kernel: eth0: pcnet32_start_xmit()
PRoblem with pcnet32 under 2.4.0 , was :Drivers under 2.4
According to Hans Grobler: If you're willing, would you please follow "REPORTING-BUGS" and send some more info. Also cat /proc/interrupts. This one's intriging... In short: Cyrix Multimedia box Everything onboard, including ethernet. Works as supposed to under 2.2.x (including 2.2.19pre7) installing 2.4.0 kernel recognises the driver but no byte is passed over the ethernet. Kernel: Linux version 2.4.0-ac7 (root@multimedia) (gcc version 2.95.3 20001229 (prerelea se)) #2 Fri Jan 12 11:17:47 CET 2001 Distribution: Debian unstable (sid) Output of loading the pcnet32 module: pcnet32_probe_pci: found device 0x001022.0x002000 ioaddr=0x00fce0 resource_flags=0x000101 PCI: Found IRQ 9 for device 00:0f.0 eth0: PCnet/FAST III 79C973 at 0xfce0, 00 00 e2 24 41 1d pcnet32: pcnet32_private lp=c3c42000 lp_dma_addr=0x3c42000 assigned IRQ 9. pcnet32.c:v1.25kf 26.9.1999 [EMAIL PROTECTED] lspci -vx output: 00:0f.0 Ethernet controller: Advanced Micro Devices [AMD] 79c970 [PCnet LANCE] ( rev 42) Subsystem: Advanced Micro Devices [AMD]: Unknown device 2000 Flags: bus master, medium devsel, latency 64, IRQ 9 I/O ports at fce0 [size=32] Memory at fedffc00 (32-bit, non-prefetchable) [size=32] Expansion ROM at unassigned [disabled] [size=1M] Capabilities: [40] Power Management version 1 00: 22 10 00 20 07 00 90 02 42 00 00 02 00 40 00 00 10: e1 fc 00 00 00 fc df fe 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 22 10 00 20 30: 00 00 00 00 40 00 00 00 00 00 00 00 09 01 18 18 The machine is connected to a 3com 8ports 100Mbit hub no additional parameters when the module is loaded, except i tried debug=7 which gave verbose output After bootup this is the situation: multimedia:~# ifconfig eth0 Link encap:Ethernet HWaddr 00:00:E2:24:41:1D inet addr:192.168.1.51 Bcast:192.168.1.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:100 Interrupt:9 Base address:0xfce0 procinfo: multimedia:~# procinfo Linux 2.4.0-ac7 (root@multimedia) (gcc 2.95.3 20001229 ) #2 Fri Jan 12 11:17:47 CET 2001 1CPU [multimedia.(none)] Memory: TotalUsedFree Shared Buffers Cached Mem: 62308 12596 49712 0 6366636 Swap: 184708 0 184708 Bootup: Fri Jan 12 12:30:22 2001Load average: 0.02 0.03 0.01 1/28 229 user : 0:00:05.32 3.2% page in : 5744 nice : 0:00:00.00 0.0% page out: 354 system: 0:00:09.31 5.5% swap in :1 idle : 0:02:33.77 91.3% swap out:0 uptime: 0:02:48.38 context : 2940 irq 0: 16840 timer irq 9: 0 acpi, PCnet/FAST III irq 1: 3 keyboard irq 12: 0 PS/2 Mouse irq 2: 0 cascade [4] irq 14: 1640 ide0 irq 4: 127 serialirq 15: 3 ide1 irq 8: 1 rtc after trying to ping -c10 a host in it's own range (default gw in fact): Jan 12 12:30:36 multimedia kernel: eth0: pcnet32_open() irq 9 tx/rx rings 0x3c41 200/0x3c41000 init 0x3c41300. Jan 12 12:30:36 multimedia kernel: eth0: pcnet32 open after 5 ticks, init block 0x3c41300 csr0 01f3. Jan 12 12:30:38 multimedia kernel: eth0:
Re: PRoblem with pcnet32 under 2.4.0 , was :Drivers under 2.4
Hans Grobler [EMAIL PROTECTED] wrote: lspci -vx output: What about the other devices? ok, here's the full listing : 00:00.0 Host bridge: Cyrix Corporation PCI Master Flags: bus master, medium devsel, latency 0 00: 78 10 01 00 07 00 80 02 00 00 00 06 00 00 00 00 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00:0e.0 VGA compatible controller: Intergraphics Systems CyberPro 5000 (rev 02) (prog-if 00 [VGA]) Subsystem: Unknown device 0280:7000 Flags: medium devsel, IRQ 11 Memory at fd00 (32-bit, non-prefetchable) [size=16M] Expansion ROM at unassigned [disabled] [size=64K] 00: ea 10 00 50 03 00 00 02 02 00 00 03 04 40 00 00 10: 00 00 00 fd 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 80 02 00 70 30: 00 00 00 00 00 00 00 00 00 00 00 00 0b 01 00 00 00:0f.0 Ethernet controller: Advanced Micro Devices [AMD] 79c970 [PCnet LANCE] ( rev 42) Subsystem: Advanced Micro Devices [AMD]: Unknown device 2000 Flags: bus master, medium devsel, latency 64, IRQ 9 I/O ports at fce0 [size=32] Memory at fedffc00 (32-bit, non-prefetchable) [size=32] Expansion ROM at unassigned [disabled] [size=1M] Capabilities: [40] Power Management version 1 00: 22 10 00 20 07 00 90 02 42 00 00 02 00 40 00 00 10: e1 fc 00 00 00 fc df fe 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 22 10 00 20 30: 00 00 00 00 40 00 00 00 00 00 00 00 09 01 18 18 00:12.1 Bridge: Cyrix Corporation 5530 SMI [Kahlua] Flags: medium devsel Memory at 40012000 (32-bit, non-prefetchable) [size=256] 00: 78 10 01 01 02 00 80 02 00 00 80 06 00 00 00 00 10: 00 20 01 40 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00:12.2 IDE interface: Cyrix Corporation 5530 IDE [Kahlua] (prog-if 00 []) Flags: medium devsel I/O ports at fc00 [size=16] 00: 78 10 02 01 01 00 80 02 00 00 01 01 00 00 00 00 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20: 01 fc 00 00 00 00 00 00 00 00 00 00 00 00 00 00 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00:12.3 Multimedia audio controller: Cyrix Corporation 5530 Audio [Kahlua] Flags: bus master, medium devsel, latency 0 Memory at 40011000 (32-bit, non-prefetchable) [size=128] 00: 78 10 03 01 06 00 80 02 00 00 01 04 00 00 00 00 10: 00 10 01 40 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00:13.0 USB Controller: Compaq Computer Corporation: Unknown device a0f8 (rev 06 ) (prog-if 10 [OHCI]) Subsystem: Compaq Computer Corporation: Unknown device a0f8 Flags: medium devsel, IRQ 10 Memory at fedfe000 (32-bit, non-prefetchable) [size=4K] 00: 11 0e f8 a0 13 00 80 02 06 10 03 0c 00 40 00 00 10: 00 e0 df fe 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 11 0e f8 a0 30: 00 00 00 00 00 00 00 00 00 00 00 00 0a 01 00 50 00:14.0 Multimedia video
Re: Drivers under 2.4
Jeff Garzik <[EMAIL PROTECTED]> wrote: >Does this patch help at all? Nope, unfortunatly it didn't > filename="pcnet32.patch" pcnet32_probe_pci: found device 0x001022.0x002000 ioaddr=0x00fce0 resource_flags=0x000101 PCI: Found IRQ 9 for device 00:0f.0 PCnet chip version is 0x22625003. eth0: PCnet/FAST III 79C973 at 0xfce0, 00 00 e2 24 41 1d<6>pcnet32: pcnet32_priv ate lp=c3fb8d40 lp_dma_addr=0x3bf1000 assigned IRQ 9. pcnet32.c:v1.25smp Nov 11, 2000 [EMAIL PROTECTED] eth0: pcnet32_open() irq 9 tx/rx rings 0x3bf1200/0x3bf1000 init 0x3bf1300. eth0: pcnet32 open after 5 ticks, init block 0x3bf1300 csr0 01f3. eth0: pcnet32_start_xmit() called, csr0 01f3. multimedia:~# ping -c5 192.168.1.1 PING 192.168.1.1 (192.168.1.1): 56 data bytes --- 192.168.1.1 ping statistics --- 5 packets transmitted, 0 packets received, 100% packet loss multimedia:~# arp -an ? (192.168.1.2) at on eth0 ? (192.168.1.1) at on eth0 multimedia:~# ifconfig eth0 eth0 Link encap:Ethernet HWaddr 00:00:E2:24:41:1D inet addr:192.168.1.51 Bcast:192.168.1.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:100 Interrupt:9 Base address:0xfce0 Danny - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Drivers under 2.4
>Jan 11 12:45:49 multimedia kernel: eth0: pcnet32_start_xmit() called, csr0 07f3. >Jan 11 12:46:01 multimedia last message repeated 12 times hot from the ethernet wire: more info just arrived: NETDEV WATCHDOG: eth0: transmit timed out eth0: transmit timed out, status 07f3, resetting. Ring data dump: dirty_tx 0 cur_tx 16 (full) cur_rx 0. 03b2f012 0608 0040 0310 03b2f812 0608 0040 0310 03b2e012 0608 0040 0310 03b2e812 0608 0040 0310 03b2d012 0608 0040 0310 03b2d812 0608 0040 0310 03b2c012 0608 0040 0310 03b2c812 0608 0040 0310 03b2b012 0608 0040 0310 03b2b812 0608 0040 0310 03b2a012 0608 0040 0310 03b2a812 0608 0040 0310 03b29012 0608 0040 0310 03b29812 0608 0040 0310 03b28012 0608 0040 0310 03b28812 0608 0111 0310 03b3f012 0608 00fc 0310 03b3f812 0608 006a 0310 03b3e012 0608 0040 0310 03b3e812 0608 0040 0310 03b3d012 0608 0040 0310 03b3d812 0608 0040 0310 03b3c012 0608 0040 0310 03b3c812 0608 0040 0310 03b3a012 0608 0040 0310 03b3a812 0608 0040 0310 03b39012 0608 0040 0310 03b39812 0608 0040 0340 03b38012 0608 0040 0340 03b38812 0608 0040 0340 03b4f012 0608 0040 0340 03b4f812 0608 0040 0340 03f9a782 0066 0300 03b4e222 002a 0300 03b4e2a2 002a 0300 03b4e322 002a 0300 03b4e3a2 002a 0300 03b4e422 002a 0300 03b4e4a2 002a 0300 03b4e522 002a 0300 03b4e5a2 002a 0300 03b4e622 002a 0300 03b4e6a2 002a 0300 03b4eea2 002a 0300 03b4ef22 002a 0300 03f9a882 007e 0300 03f9a982 007e 0300 03f9aa82 007e 0300 eth0: pcnet32_start_xmit() called, csr0 05f3. eth0: pcnet32_start_xmit() called, csr0 07f3. etc... Danny - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Drivers under 2.4
Andrew Morton <[EMAIL PROTECTED]> wrote: >There's a "reporting problems" section at the end >of Documentation/networking/vortex.txt. Should help. okidoki, have read it, thanks >Probably the most important thing is inserting the driver >module with `debug=7', opening the device, sending some >traffic and then sending us the logs. pcnet32_probe_pci: found device 0x001022.0x002000 ioaddr=0x00fce0 resource_flags=0x000101 PCI: Found IRQ 9 for device 00:0f.0 PCnet chip version is 0x22625003. eth0: PCnet/FAST III 79C973 at 0xfce0, 00 00 e2 24 41 1d pcnet32: pcnet32_private lp=c3bf6000 lp_dma_addr=0x3bf6000 assigned IRQ 9. pcnet32.c:v1.25kf 26.9.1999 [EMAIL PROTECTED] eth0: pcnet32_open() irq 9 tx/rx rings 0x3bf6200/0x3bf6000 init 0x3bf6300. eth0: pcnet32 open after 5 ticks, init block 0x3bf6300 csr0 01f3. eth0: pcnet32_start_xmit() called, csr0 01f3. this after bootup, static ip adress multimedia:~# ifconfig eth0 eth0 Link encap:Ethernet HWaddr 00:00:E2:24:41:1D inet addr:192.168.1.51 Bcast:192.168.1.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:100 Interrupt:9 Base address:0xfce0 multimedia:~# ping -c10 192.168.1.1 PING 192.168.1.1 (192.168.1.1): 56 data bytes --- 192.168.1.1 ping statistics --- 10 packets transmitted, 0 packets received, 100% packet loss after this the following messages in dmesg: Jan 11 12:45:49 multimedia kernel: eth0: pcnet32_start_xmit() called, csr0 07f3. Jan 11 12:46:01 multimedia last message repeated 12 times Danny - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Drivers under 2.4
According to Andi Kleen: > "Doesn't work" isn't a very useful bug report. What happens exactly? > Do the RX/TX/error counters increase when you try to send packets? no, the counters you see with ifconfig eth0 are set to zero for rx and to 1 for tx. So it's trying to send out data but somehow it doesn't work. Since the driver version is the same (althoud the output is slihtly different which seems odd) i suspect the PCI probing to be folded somewhere. How could i provide people with more info ? Thanks, Danny - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Drivers under 2.4
Hans Grobler <[EMAIL PROTECTED]> wrote: >The softnet changes are most likely the primary source of breakage (for >network drivers). I happen to have a multimedia box from siemens/fujitsu with a cyrix processor, chipset and amd/lance ethernet chipset onboard. It' working fine with 2.2.x but not with 2.4.x kernels with the same driver version of the pcnet32 networkdriver. 2.4.0-ac4 Jan 9 17:09:53 multimedia kernel: Linux version 2.4.0-ac4 (root@ws1) (gcc version 2.95.3 20001229 (prerelease)) #2 Tue Jan 9 16:22:08 CET 2001 Jan 9 17:09:53 multimedia kernel: PCI: Found IRQ 9 for device 00:0f.0 Jan 9 17:09:53 multimedia kernel: eth0: PCnet/FAST III 79C973 at 0xfce0, 00 00 e2 24 41 1d Jan 9 17:09:53 multimedia kernel: pcnet32: pcnet32_private lp=c3c8 lp_dma_addr=0x3c8 assigned IRQ 9. Jan 9 17:09:53 multimedia kernel: pcnet32.c:v1.25kf 26.9.1999 [EMAIL PROTECTED] and 2.2.19pre7 Jan 10 20:46:15 multimedia kernel: Linux version 2.2.19pre7 (root@multimedia) (gcc version 2.95.3 20001229 (prerelease)) #2 Wed Jan 10 20:13:57 CET 2001 Jan 10 20:46:15 multimedia kernel: pcnet32.c: PCI bios is present, checking for devices... Jan 10 20:46:15 multimedia kernel: Found PCnet/PCI at 0xfce0, irq 9. Jan 10 20:46:15 multimedia kernel: eth0: PCnet/FAST III 79C973 at 0xfce0, 00 00 e2 24 41 1d assigned IRQ 9. Jan 10 20:46:15 multimedia kernel: pcnet32.c:v1.25kf 26.9.1999 [EMAIL PROTECTED] Version number of the driver is the same but it doesn't work. Any thoughts anyone ? Danny - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Drivers under 2.4
Hans Grobler [EMAIL PROTECTED] wrote: The softnet changes are most likely the primary source of breakage (for network drivers). I happen to have a multimedia box from siemens/fujitsu with a cyrix processor, chipset and amd/lance ethernet chipset onboard. It' working fine with 2.2.x but not with 2.4.x kernels with the same driver version of the pcnet32 networkdriver. 2.4.0-ac4 Jan 9 17:09:53 multimedia kernel: Linux version 2.4.0-ac4 (root@ws1) (gcc version 2.95.3 20001229 (prerelease)) #2 Tue Jan 9 16:22:08 CET 2001 Jan 9 17:09:53 multimedia kernel: PCI: Found IRQ 9 for device 00:0f.0 Jan 9 17:09:53 multimedia kernel: eth0: PCnet/FAST III 79C973 at 0xfce0, 00 00 e2 24 41 1d Jan 9 17:09:53 multimedia kernel: pcnet32: pcnet32_private lp=c3c8 lp_dma_addr=0x3c8 assigned IRQ 9. Jan 9 17:09:53 multimedia kernel: pcnet32.c:v1.25kf 26.9.1999 [EMAIL PROTECTED] and 2.2.19pre7 Jan 10 20:46:15 multimedia kernel: Linux version 2.2.19pre7 (root@multimedia) (gcc version 2.95.3 20001229 (prerelease)) #2 Wed Jan 10 20:13:57 CET 2001 Jan 10 20:46:15 multimedia kernel: pcnet32.c: PCI bios is present, checking for devices... Jan 10 20:46:15 multimedia kernel: Found PCnet/PCI at 0xfce0, irq 9. Jan 10 20:46:15 multimedia kernel: eth0: PCnet/FAST III 79C973 at 0xfce0, 00 00 e2 24 41 1d assigned IRQ 9. Jan 10 20:46:15 multimedia kernel: pcnet32.c:v1.25kf 26.9.1999 [EMAIL PROTECTED] Version number of the driver is the same but it doesn't work. Any thoughts anyone ? Danny - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Drivers under 2.4
According to Andi Kleen: "Doesn't work" isn't a very useful bug report. What happens exactly? Do the RX/TX/error counters increase when you try to send packets? no, the counters you see with ifconfig eth0 are set to zero for rx and to 1 for tx. So it's trying to send out data but somehow it doesn't work. Since the driver version is the same (althoud the output is slihtly different which seems odd) i suspect the PCI probing to be folded somewhere. How could i provide people with more info ? Thanks, Danny - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Drivers under 2.4
Andrew Morton [EMAIL PROTECTED] wrote: There's a "reporting problems" section at the end of Documentation/networking/vortex.txt. Should help. okidoki, have read it, thanks Probably the most important thing is inserting the driver module with `debug=7', opening the device, sending some traffic and then sending us the logs. pcnet32_probe_pci: found device 0x001022.0x002000 ioaddr=0x00fce0 resource_flags=0x000101 PCI: Found IRQ 9 for device 00:0f.0 PCnet chip version is 0x22625003. eth0: PCnet/FAST III 79C973 at 0xfce0, 00 00 e2 24 41 1d pcnet32: pcnet32_private lp=c3bf6000 lp_dma_addr=0x3bf6000 assigned IRQ 9. pcnet32.c:v1.25kf 26.9.1999 [EMAIL PROTECTED] eth0: pcnet32_open() irq 9 tx/rx rings 0x3bf6200/0x3bf6000 init 0x3bf6300. eth0: pcnet32 open after 5 ticks, init block 0x3bf6300 csr0 01f3. eth0: pcnet32_start_xmit() called, csr0 01f3. this after bootup, static ip adress multimedia:~# ifconfig eth0 eth0 Link encap:Ethernet HWaddr 00:00:E2:24:41:1D inet addr:192.168.1.51 Bcast:192.168.1.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:100 Interrupt:9 Base address:0xfce0 multimedia:~# ping -c10 192.168.1.1 PING 192.168.1.1 (192.168.1.1): 56 data bytes --- 192.168.1.1 ping statistics --- 10 packets transmitted, 0 packets received, 100% packet loss after this the following messages in dmesg: Jan 11 12:45:49 multimedia kernel: eth0: pcnet32_start_xmit() called, csr0 07f3. Jan 11 12:46:01 multimedia last message repeated 12 times Danny - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Drivers under 2.4
Jan 11 12:45:49 multimedia kernel: eth0: pcnet32_start_xmit() called, csr0 07f3. Jan 11 12:46:01 multimedia last message repeated 12 times hot from the ethernet wire: more info just arrived: NETDEV WATCHDOG: eth0: transmit timed out eth0: transmit timed out, status 07f3, resetting. Ring data dump: dirty_tx 0 cur_tx 16 (full) cur_rx 0. 03b2f012 0608 0040 0310 03b2f812 0608 0040 0310 03b2e012 0608 0040 0310 03b2e812 0608 0040 0310 03b2d012 0608 0040 0310 03b2d812 0608 0040 0310 03b2c012 0608 0040 0310 03b2c812 0608 0040 0310 03b2b012 0608 0040 0310 03b2b812 0608 0040 0310 03b2a012 0608 0040 0310 03b2a812 0608 0040 0310 03b29012 0608 0040 0310 03b29812 0608 0040 0310 03b28012 0608 0040 0310 03b28812 0608 0111 0310 03b3f012 0608 00fc 0310 03b3f812 0608 006a 0310 03b3e012 0608 0040 0310 03b3e812 0608 0040 0310 03b3d012 0608 0040 0310 03b3d812 0608 0040 0310 03b3c012 0608 0040 0310 03b3c812 0608 0040 0310 03b3a012 0608 0040 0310 03b3a812 0608 0040 0310 03b39012 0608 0040 0310 03b39812 0608 0040 0340 03b38012 0608 0040 0340 03b38812 0608 0040 0340 03b4f012 0608 0040 0340 03b4f812 0608 0040 0340 03f9a782 0066 0300 03b4e222 002a 0300 03b4e2a2 002a 0300 03b4e322 002a 0300 03b4e3a2 002a 0300 03b4e422 002a 0300 03b4e4a2 002a 0300 03b4e522 002a 0300 03b4e5a2 002a 0300 03b4e622 002a 0300 03b4e6a2 002a 0300 03b4eea2 002a 0300 03b4ef22 002a 0300 03f9a882 007e 0300 03f9a982 007e 0300 03f9aa82 007e 0300 eth0: pcnet32_start_xmit() called, csr0 05f3. eth0: pcnet32_start_xmit() called, csr0 07f3. etc... Danny - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Drivers under 2.4
Jeff Garzik [EMAIL PROTECTED] wrote: Does this patch help at all? Nope, unfortunatly it didn't filename="pcnet32.patch" pcnet32_probe_pci: found device 0x001022.0x002000 ioaddr=0x00fce0 resource_flags=0x000101 PCI: Found IRQ 9 for device 00:0f.0 PCnet chip version is 0x22625003. eth0: PCnet/FAST III 79C973 at 0xfce0, 00 00 e2 24 41 1d6pcnet32: pcnet32_priv ate lp=c3fb8d40 lp_dma_addr=0x3bf1000 assigned IRQ 9. pcnet32.c:v1.25smp Nov 11, 2000 [EMAIL PROTECTED] eth0: pcnet32_open() irq 9 tx/rx rings 0x3bf1200/0x3bf1000 init 0x3bf1300. eth0: pcnet32 open after 5 ticks, init block 0x3bf1300 csr0 01f3. eth0: pcnet32_start_xmit() called, csr0 01f3. multimedia:~# ping -c5 192.168.1.1 PING 192.168.1.1 (192.168.1.1): 56 data bytes --- 192.168.1.1 ping statistics --- 5 packets transmitted, 0 packets received, 100% packet loss multimedia:~# arp -an ? (192.168.1.2) at incomplete on eth0 ? (192.168.1.1) at incomplete on eth0 multimedia:~# ifconfig eth0 eth0 Link encap:Ethernet HWaddr 00:00:E2:24:41:1D inet addr:192.168.1.51 Bcast:192.168.1.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:100 Interrupt:9 Base address:0xfce0 Danny - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
