[Bug 302327] New: x86_64 intermittent lockups with post beta1 kernels from factory
https://bugzilla.novell.com/show_bug.cgi?id=302327 Summary: x86_64 intermittent lockups with post beta1 kernels from factory Product: openSUSE 10.3 Version: Beta 2 Platform: x86-64 OS/Version: Other Status: NEW Severity: Critical Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers@forge.provo.novell.com ReportedBy: wns@comcast.net QAContact: qa@suse.de Found By: Beta-Customer The 2.6.22.3-*-default kernels that where sync'd out since Friday (17 Aug) are causing intermittent lockups on a HP dv6400 laptop with a Turion64 X2 TL-56 processor. The beta1 kernel (kernel-default-2.6.22.1-16) did not exhibit the problem. The problem is not present running a vanilla kernel (kernel-vanilla-2.6.22.3-20070818105014) The problem results in a hard hang. No oops is ever recorded in any of the log files. I have also been unable to catch any Oops message on the F10 screen. # cat /proc/cpuinfo processor : 0 vendor_id : AuthenticAMD cpu family : 15 model : 72 model name : AMD Turion(tm) 64 X2 Mobile Technology TL-56 stepping : 2 cpu MHz : 800.000 cache size : 512 KB physical id : 0 siblings : 2 core id : 0 cpu cores : 2 fpu : yes fpu_exception : yes cpuid level : 1 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt rdtscp lm 3dno wext 3dnow pni cx16 lahf_lm cmp_legacy svm extapic cr8_legacy bogomips : 1608.66 TLB size : 1024 4K pages clflush size : 64 cache_alignment : 64 address sizes : 40 bits physical, 48 bits virtual power management: ts fid vid ttp tm stc processor : 1 vendor_id : AuthenticAMD cpu family : 15 model : 72 model name : AMD Turion(tm) 64 X2 Mobile Technology TL-56 stepping : 2 cpu MHz : 800.000 cache size : 512 KB physical id : 0 siblings : 2 core id : 1 cpu cores : 2 fpu : yes fpu_exception : yes cpuid level : 1 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt rdtscp lm 3dno wext 3dnow pni cx16 lahf_lm cmp_legacy svm extapic cr8_legacy bogomips : 1608.66 TLB size : 1024 4K pages clflush size : 64 cache_alignment : 64 address sizes : 40 bits physical, 48 bits virtual power management: ts fid vid ttp tm stc # lspci 00:00.0 RAM memory: nVidia Corporation C51 Host Bridge (rev a2) 00:00.1 RAM memory: nVidia Corporation C51 Memory Controller 0 (rev a2) 00:00.2 RAM memory: nVidia Corporation C51 Memory Controller 1 (rev a2) 00:00.3 RAM memory: nVidia Corporation C51 Memory Controller 5 (rev a2) 00:00.4 RAM memory: nVidia Corporation C51 Memory Controller 4 (rev a2) 00:00.5 RAM memory: nVidia Corporation C51 Host Bridge (rev a2) 00:00.6 RAM memory: nVidia Corporation C51 Memory Controller 3 (rev a2) 00:00.7 RAM memory: nVidia Corporation C51 Memory Controller 2 (rev a2) 00:02.0 PCI bridge: nVidia Corporation C51 PCI Express Bridge (rev a1) 00:03.0 PCI bridge: nVidia Corporation C51 PCI Express Bridge (rev a1) 00:05.0 VGA compatible controller: nVidia Corporation C51 [Geforce 6150 Go] (rev a2) 00:09.0 RAM memory: nVidia Corporation MCP51 Host Bridge (rev a2) 00:0a.0 ISA bridge: nVidia Corporation MCP51 LPC Bridge (rev a3) 00:0a.1 SMBus: nVidia Corporation MCP51 SMBus (rev a3) 00:0a.3 Co-processor: nVidia Corporation MCP51 PMU (rev a3) 00:0b.0 USB Controller: nVidia Corporation MCP51 USB Controller (rev a3) 00:0b.1 USB Controller: nVidia Corporation MCP51 USB Controller (rev a3) 00:0d.0 IDE interface: nVidia Corporation MCP51 IDE (rev f1) 00:0e.0 IDE interface: nVidia Corporation MCP51 Serial ATA Controller (rev f1) 00:10.0 PCI bridge: nVidia Corporation MCP51 PCI Bridge (rev a2) 00:10.1 Audio device: nVidia Corporation MCP51 High Definition Audio (rev a2) 00:14.0 Bridge: nVidia Corporation MCP51 Ethernet Controller (rev a3) 00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration 00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map 00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller 00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control 03:00.0 Network controller: Broadcom Corporation BCM94311MCG wlan mini-PCI (rev 02) 07:05.0 FireWire (IEEE 1394): Ricoh Co Ltd R5C832 IEEE 1394 Controller 07:05.1 Generic system peripheral [Class 0805]: Ricoh Co Ltd R5C822 SD/SDIO/MMC/MS/MSPro Host Adapter (rev 19) 07:05.2 System peripheral: Ricoh Co Ltd R5C843 MMC Host Controller (rev 01) 07:05.3 System peripheral: Ricoh Co Ltd R5C592 Memory Stick Bus Host Adapter (rev 0a) 07:05.4 System peripheral: Ricoh Co Ltd xD-Picture Card Controller (rev 05) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=302327#c1 Jeff Mahoney <jeffm@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |wns@comcast.net --- Comment #1 from Jeff Mahoney <jeffm@novell.com> 2007-08-25 09:35:58 MST --- More information on this report can be found on the opensuse-kernel mailing list, here: http://lists.opensuse.org/opensuse-kernel/2007-08/msg00070.html The key thing from that discussion is that the vanilla 2.6.22.3 doesn't exhibit the lockups that the openSUSE kernel does. Warren, have you had any luck setting up a console mechanism? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=302327#c2 Warren Stockton <wns@comcast.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|wns@comcast.net | --- Comment #2 from Warren Stockton <wns@comcast.net> 2007-08-25 10:39:57 MST --- I setup netconsole in /etc/init.d/boot.local with: /sbin/insmod /lib/modules/`uname -r`/kernel/drivers/net/netconsole.ko netconsole=4444@192.168.10.100/eth0,9353@192.168.10.1/00:03:47:23:e3:df On the remote machine, I ran the netcat to capture the console: nodhup netcat -u -l -p 9353 >netconsole.log 2>&1 & The netconsole.log only captures the following output: netconsole: local port 4444 netconsole: local IP 192.168.... netconsole: interface eth0 netconsole: remote port 9353 netconsole: remote IP 192.168.... netconsole: remote ethernet address 00:03:47:23:e3:df netconsole: device eth0 not up yet, forcing it netconsole: carrier detect appears untrustworthy, waiting 4 seconds netconsole: network logging started Disabling IRQ #7 The "Disabling IRQ" message appears about 1 to 2 minutes after netconsole is initialized and the hang (with no messages) occurs several minutes later, typically 15 to 30 minutes after booting. The excessive IRQ #7 activity is associated with sdhci. I have blacklisted the sdhci driver in /etc/modprobe.d but the lookups still occur with -default. If I load sdhci manually, it does not receive interrupts unless I access the SD card. The "excessive" interrupts only occur if the sdhci is auto loaded. This probably a different issue, but I leave that for someone else to decide. Since writing the BUG, I have updated to the "official" Beta2 binaries. The issue is still seen with kernel-default-2.6.22.3-7 Yesterday, I ran kernel-vanilla-2.6.22.3-7 for over 14 hours with no problems. (I only have the "standard" boot arguments root= vga= resume= splash=). I will try leave this running all weekend with -vanilla to make sure that this is solid. I have tried several boot options with the -default kernel: pollirq can delay the hang with -default for some time but it still occurs (It also seems to cause repeated characters when typing.) nohpet does not prevent the hang on -default. I am willing to try firescope (hardware/cables should not be a problem). I just need setup instructions as I have yet to find any sort of HOWTO. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=302327#c3 Stephan Kulow <coolo@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |coolo@novell.com Status|NEW |NEEDINFO Info Provider| |wns@comcast.net Flag| |SHIP_STOPPER- --- Comment #3 from Stephan Kulow <coolo@novell.com> 2007-09-14 06:55:23 MST --- is this fixed in later beta releases? Because I know several installations of x86_64 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=302327#c4 Warren Stockton <wns@comcast.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|wns@comcast.net | --- Comment #4 from Warren Stockton <wns@comcast.net> 2007-09-14 08:47:17 MST --- Unfortunaly not. I have updated each time factory has been sync out. I currently have Beta3plus # rpm -qa kernel* -last kernel-vanilla-2.6.22.5-16 Wed 12 Sep 2007 08:03:44 PM MDT kernel-default-2.6.22.5-16 Wed 12 Sep 2007 08:02:22 PM MDT kernel-source-2.6.22.5-16 Wed 12 Sep 2007 07:43:00 PM MDT The last time I booted kernel-default, it ran about 20 minutes before a hard hang. I use this laptop daily and only with 10.3 (since about 10.3Alpha4). Since Beta1Plus, in order to get any work done, I either run the latest kernel-vanilla (when I have no need for kmp packages) or the kernel-default from Beta1 (with the kmp packages) (I installed kernel-default-2.6.22.1-16 and then did a "rpm -e --justdb" on the Beta1 kernel and kmps so that they would not be removed during updates) I have diff'd the Beta1 kernel source and tried to back out some of the later patches, but have not been able to isolate the troublesome code. My wife has my previous Turion64 X2 laptop (with a TL-52 processor) and it does not exhibit the problem. It only has 10.3 installed and is typically only updated via DVD. (That laptop is nearly identical to this one, just 14 months older and nearly all the chipsets are one stepping earlier that this one.) This bug will probably only effect X2 laptops that are a couple months old or newer. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=302327#c5 --- Comment #5 from Warren Stockton <wns@comcast.net> 2007-09-20 23:02:16 MST --- I have updated to 10.3RC1 but the update kernels were also installed (so I don't know if the kernel-default-2.6.22.5-23 had the problem): # rpm -qa kernel-* kernel-source-2.6.22.5-25 kernel-vanilla-2.6.22.5-23 kernel-default-2.6.22.5-25 I still get the hang with the latest kernel. I have noticed that if I set the RTC via the BIOS setup to the correct time and then run the -default kernel until it hangs, I find than when I reboot the RTC has a wrong (corrupted) time. The RTC date appears to still be correct. I am running ntpd and wondering if this has anything to do with the kernel's sync_cmos_clock() I don't know if this ties back to issues I encounter with hwclock where it can also hang then system just reading the RTC: # hwclock --hctosys -u --test --debug hwclock from util-linux-2.13-rc2 Using /dev interface to clock. Assuming hardware clock is kept in UTC time. Waiting for clock tick... /dev/rtc does not have interrupt functions. Waiting in loop for time from /dev/rtc to change <<< hang will intermittently occur here >>> ..got clock tick Time read from Hardware Clock: 2007/10/21 00:55:51 Hw clock time : 2007/10/21 00:55:51 = 1192928151 seconds since 1969 Calling settimeofday: tv.tv_sec = 1192928151, tv.tv_usec = 0 tz.tz_minuteswest = 360 Not setting system clock because running in test mode. (intermittent hangs are encountered with both --localtime or --utc) Comparing /boot/config-2.6.22.1-16-default (which works) and /boot/config-2.6.22.5-25-default (which hangs), I notice that CONFIG_HPET_EMULATE_RTC=y is defined in 2.6.22.1-16-default This laptop (TL-56) is using hpet: # cat /sys/devices/system/clocksource/clocksource0/current_clocksource hpet The "older" laptop (TL-52) does not have hpet and uses acpi_pm as a clocksource. Booting the TL-56 with "clocksource=acpi_pm" and -default kernel does not avoid the hang. I plan to build a 2.6.22.5-25-default kernel that defines CONFIG_HPET_EMULATE_RTC=y to see if this narrows down the problem, but this will have to wait for tomorrow. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=302327#c6 Jeff Mahoney <jeffm@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jeffm@novell.com Status|NEW |NEEDINFO Info Provider| |wns@comcast.net --- Comment #6 from Jeff Mahoney <jeffm@novell.com> 2007-10-18 14:34:20 MST --- Have you tried the latest update kernel now? I'd like to verify this bug still occurs. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=302327#c7 Warren Stockton <wns@comcast.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|wns@comcast.net | --- Comment #7 from Warren Stockton <wns@comcast.net> 2007-10-18 15:04:54 MST --- Yes. I found that this lookup occurred with all the kernel-default-2.6.22.x kernels that have been released for 10.3 (After updating to the 10.3-GM, I would run the kernel-default from the 10.3-Beta1 media to avoid the problem.) The last 2.6.22 kernel that I ran that still encountered the problem was: ftp://ftp.suse.com/pub/projects/kernel/kotd/HEAD/x86_64/kernel-default-2.6.22.10-20071011115904.x86_64.rpm I have recently updated to 10.3.1 (on Oct 15) along with the kernel from http://download.opensuse.org/repositories/Kernel:/HEAD/openSUSE_Factory # cat /proc/version Linux version 2.6.23.1-62-default (geeko@buildhost) (gcc version 4.2.1 (SUSE Linux)) #1 SMP 2007/10/17 17:52:09 UTC As I type up this response, I have the following uptime: # uptime 3:00pm up 5:55, 2 users, load average: 0.61, 0.34, 0.17 This kernel appears to be quite stable and appears to avoid the lockup. I wish I could be more positive but I never found a test case that can reproduce the hang at will. The previous 2.6.23.1-46-default was the first 2.6.23 kernel I tried and it also appeared to avoid the lockup. I can drop back to 10.3-GM and any other other kernel if I need to try some tests. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=302327#c8 Jeff Mahoney <jeffm@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |wns@comcast.net --- Comment #8 from Jeff Mahoney <jeffm@novell.com> 2007-10-23 11:58:08 MST --- Ok, would you be willing to test a few kernels that I'll generate to narrow down where between beta1 and beta2 the problem occured? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=302327#c9 Warren Stockton <wns@comcast.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|wns@comcast.net | --- Comment #9 from Warren Stockton <wns@comcast.net> 2007-10-23 12:55:43 MST --- Sure. Andi previously built 5 kernels that I tried:
0 is the kernel with all patches for a control run, 1-4 are without ACPI, libata, ALSA, ieee1394 respectively. All of these still encountered the lockup.
I did notice that it requires runlevel 5 to expose this issue. I booted to runlevel 1 and left the system for about two hours and it was still OK, but within 15 minutes of switching to runlevel 5, it had locked up. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=302327#c10 Jeff Mahoney <jeffm@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |wns@comcast.net --- Comment #10 from Jeff Mahoney <jeffm@novell.com> 2007-10-23 13:59:32 MST --- Ok, I'm actually not going to alter the configs at all - just try different CVS snapshots to try to bisect which change caused the problem. Please try the kernel at ftp://ftp.suse.com/pub/people/jeffm/suse/testpkgs/302327 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=302327#c11 Warren Stockton <wns@comcast.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|wns@comcast.net | --- Comment #11 from Warren Stockton <wns@comcast.net> 2007-10-23 14:18:36 MST --- Umm... That is an i586 kernel!!! At least as far as the filename is concerned. I will download and confirm. Can you provide and x86_64 kernel? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=302327#c12 --- Comment #12 from Jeff Mahoney <jeffm@novell.com> 2007-10-23 14:21:25 MST --- Oh, my mistake. I've been looking through a lot of bugs today. I'll post an x86_64 kernel shortly. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=302327#c13 Jeff Mahoney <jeffm@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |wns@comcast.net --- Comment #13 from Jeff Mahoney <jeffm@novell.com> 2007-10-23 14:58:35 MST --- Ok, updated. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=302327#c14 Warren Stockton <wns@comcast.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|wns@comcast.net | --- Comment #14 from Warren Stockton <wns@comcast.net> 2007-10-23 23:10:26 MST --- Installed the x86_64 kernel and it has been running without problems... Linux version 2.6.22.1-jeffm.7b6a622a1113763b1c6231ab0c7da16d4015e5e0-default (geeko@buildhost) (gcc version 4.2.1 (SUSE Linux)) #1 SMP 2007/08/10 02:30:26 UTC Uptime is 8 hours and still going strong -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=302327#c15 Jeff Mahoney <jeffm@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |wns@comcast.net --- Comment #15 from Jeff Mahoney <jeffm@novell.com> 2007-11-07 14:15:51 MST --- Ok, let's try a newer version then. I've updated the RPMs in the URL from comment #10. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=302327#c16 Warren Stockton <wns@comcast.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|wns@comcast.net | --- Comment #16 from Warren Stockton <wns@comcast.net> 2007-11-08 09:58:18 MST --- I ran 2.6.22.2-jeffm.87ba3819bc3e37bafa5a549d376285d030c4a4a8 for just over 9 hours yesterday before I had to call it a night. So by my reckoning, that narrows the window to between Aug 15 and Aug 18 where something questionable entered the code. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=302327#c17 Jeff Mahoney <jeffm@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |wns@comcast.net --- Comment #17 from Jeff Mahoney <jeffm@novell.com> 2007-11-08 11:28:51 MST --- Ok, that eliminates most of them. I expect that this kernel is probably the one which will end up not working for you: ftp://ftp.suse.com/pub/people/jeffm/suse/testpkgs/302327/10.3-x86_64/kernel-default-2.6.22.2-jeffm.e5e61a519e4f860c4595f966ecb897e5eb294d19.x86_64.rpm -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=302327#c18 Warren Stockton <wns@comcast.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|wns@comcast.net | --- Comment #18 from Warren Stockton <wns@comcast.net> 2007-11-08 11:54:52 MST --- Kernel 2.6.22.2-jeffm.e5e61a519e4f860c4595f966ecb897e5eb294d19 did not even make it 4 minutes before htop stop updating. Same silent death with no relevant output from netconsole. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=302327#c19 Jeff Mahoney <jeffm@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |wns@comcast.net --- Comment #19 from Jeff Mahoney <jeffm@novell.com> 2007-11-08 12:09:49 MST --- Ok, that corresponds to this change: Wed Aug 15 15:16:04 CEST 2007 - ak@suse.de - patches.arch/x86-early-quirks-unificiation: x86: Unify i386 and x86-64 early quirks. - patches.arch/x86-nvidia-timer-quirk: Replace nvidia timer override quirk with pci id list and unify quirks. - patches.arch/x86-fam10-l3cache: i386: Add L3 cache support to AMD CPUID4 emulation. - patches.arch/i386-compat-vdso: i386: allow debuggers to access the vsyscall page with compat vDSO. - patches.xen/xen3-auto-arch-i386.diff: Merge - patches.xen/xen-x86-no-lapic: Merge - patches.xen/xen3-x86-early-quirks-unificiation: x86: Unify i386 and x86-64 early quirks. - patches.xen/xen3-x86-fam10-l3cache: i386: Add L3 cache support to AMD CPUID4 emulation. Given your hardware, it's probably patches.arch/x86-nvidia-timer-quirk. Can you attach the full output of 'hwinfo' using a working kernel? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=302327#c20 --- Comment #20 from Jeff Mahoney <jeffm@novell.com> 2007-11-08 12:54:14 MST --- Also, could you test if ftp://ftp.suse.com/pub/people/jeffm/suse/testpkgs/302327/10.3-x86_64/kernel-default-2.6.22.2-jeffm.test1.x86_64.rpm works for you? That disables patches.arch/x86-nvidia-timer-quirk. I'll still need the hwinfo output so I can correct that patch. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=302327#c21 --- Comment #21 from Warren Stockton <wns@comcast.net> 2007-11-08 12:56:09 MST --- Created an attachment (id=182707) --> (https://bugzilla.novell.com/attachment.cgi?id=182707) Output of hwinfo (while running kernel-default-2.6.23.1-12.x86_64) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=302327#c22 --- Comment #22 from Jeff Mahoney <jeffm@novell.com> 2007-11-08 13:34:00 MST --- Vendor: pci 0x10de "nVidia Corporation" Device: pci 0x02f0 "C51 Host Bridge" These ids are covered by the PCI ID portion of the patch. Could you try booting a failing kernel with acpi_use_timer_override on the command line? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=302327#c23 Warren Stockton <wns@comcast.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|wns@comcast.net | --- Comment #23 from Warren Stockton <wns@comcast.net> 2007-11-09 09:51:11 MST --- Kernel 2.6.22.2-jeffm.test1 ran fine with over 9 hours of uptime. I am currently running 2.6.22.2-jeffm.e5e61a519e4f860c4595f966ecb897e5eb294d19 w/ acpi_use_timer_override and have over an hour of uptime, which (as per comment #18) didn't survive 5 minutes w/o acpi_use_timer_override. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=302327#c24 Jeff Mahoney <jeffm@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|kernel-maintainers@forge.provo.novell.com |ak@novell.com --- Comment #24 from Jeff Mahoney <jeffm@novell.com> 2007-11-09 09:57:03 MST --- That's good news! Can you try using the latest official release kernel and boot with acpi_use_timer_override? I think we've found a workaround for your problem. I'm going to pass this one off to Andi, since it's his patch, but I'll remain in the Cc. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=302327#c25 --- Comment #25 from Warren Stockton <wns@comcast.net> 2007-11-09 15:02:20 MST --- kernel-default-2.6.22.12-0.1.x86_64.rpm from 10.3/update has now been running for 2 hours w/ acpi_use_timer_override. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=302327 User ak@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=302327#c26 Andi Kleen <ak@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED --- Comment #26 from Andi Kleen <ak@novell.com> 2008-03-03 03:52:21 MST --- Revisiting. I think the hangs were because the pci id lists are not complete. Anyways since the systems where this happens are getting more and more rare (should be without Vista certification) it's probably best to revert it. Done for HEAD and 10.3 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com