You are not logged in.
Hey guys. Like a lot of people with nVidia graphics cards and chipsets, I've been having serious issues with my computer freezing. Well, I was browsing through /var/log/everything.log and I came across this:
Aug 17 12:50:21 xvarmobile logger: cannot find module dmi:bvnPhoenixTechnologiesLtd.:bvr79.12:bd05/07/2007:svnGATEWAY:pnMT3421:pvrREFERENCE:rvnGATEWAY:rn:rvrREFERENCE:cvnGateway:ct8:cvrN/A:
Aug 17 12:50:22 xvarmobile logger: cannot find module acpi:LNXSYSTM:
Aug 17 12:50:22 xvarmobile logger: cannot find module pci:v000010DEd000002F3sv0000107Bsd00000317bc05sc00i00
Aug 17 12:50:22 xvarmobile logger: cannot find module pci:v000010DEd000002FAsv0000107Bsd00000317bc05sc00i00
Aug 17 12:50:22 xvarmobile logger: cannot find module pci:v000010DEd000002FEsv0000107Bsd00000317bc05sc00i00
Aug 17 12:50:22 xvarmobile logger: cannot find module pci:v000010DEd000002F8sv0000107Bsd00000317bc05sc00i00
Aug 17 12:50:22 xvarmobile logger: cannot find module pci:v000010DEd000002F9sv0000107Bsd00000317bc05sc00i00
Aug 17 12:50:22 xvarmobile logger: cannot find module pci:v000010DEd000002FFsv0000107Bsd00000317bc05sc00i00
Aug 17 12:50:22 xvarmobile logger: cannot find module pci:v000010DEd0000027Fsv0000107Bsd00000317bc05sc00i00
Aug 17 12:50:22 xvarmobile logger: cannot find module acpi:PNP0C01:
Aug 17 12:50:22 xvarmobile logger: cannot find module pci:v000010DEd0000027Esv0000107Bsd00000317bc05sc00i00
Aug 17 12:50:22 xvarmobile logger: cannot find module acpi:PNP0000:
Aug 17 12:50:22 xvarmobile logger: cannot find module acpi:PNP0100:
Aug 17 12:50:23 xvarmobile logger: cannot find module acpi:PNP0103:
Aug 17 12:50:23 xvarmobile logger: cannot find module acpi:PNP0200:
Aug 17 12:50:23 xvarmobile logger: cannot find module acpi:PNP0303:
Aug 17 12:50:23 xvarmobile logger: cannot find module acpi:PNP0800:
Aug 17 12:50:23 xvarmobile logger: cannot find module acpi:PNP0B00:
Aug 17 12:50:23 xvarmobile logger: cannot find module acpi:PNP0C02:
Aug 17 12:50:23 xvarmobile logger: cannot find module acpi:PNP0C02:
Aug 17 12:50:23 xvarmobile logger: cannot find module acpi:PNP0C02:
Aug 17 12:50:23 xvarmobile logger: cannot find module acpi:PNP0C04:
Aug 17 12:50:23 xvarmobile logger: cannot find module acpi:SYN0B01:SYN0B00:SYN0002:PNP0F13:
Aug 17 12:50:23 xvarmobile logger: cannot find module pci:v000010DEd00000247sv0000107Bsd00000317bc03sc00i00
Aug 17 12:50:23 xvarmobile logger: cannot find module pci:v000010DEd00000270sv0000107Bsd00000317bc05sc00i00
Aug 17 12:50:23 xvarmobile logger: cannot find module pci:v000010DEd00000260sv0000107Bsd00000317bc06sc01i00
Aug 17 12:50:23 xvarmobile logger: cannot find module pci:v000010DEd00000271sv0000107Bsd00000317bc0Bsc40i00
Aug 17 12:50:23 xvarmobile logger: cannot find module pci:v000010DEd0000026Fsv00000000sd00000000bc06sc04i01
Aug 17 12:50:23 xvarmobile logger: cannot find module pci:v00001022d00001100sv00000000sd00000000bc06sc00i00
Aug 17 12:50:23 xvarmobile logger: cannot find module pci:v00001022d00001101sv00000000sd00000000bc06sc00i00
Aug 17 12:50:23 xvarmobile logger: cannot find module pci:v00001022d00001102sv00000000sd00000000bc06sc00i00
Aug 17 12:50:23 xvarmobile logger: cannot find module pnp:dPNP0a03
Aug 17 12:50:23 xvarmobile logger: cannot find module pnp:cPNP0a03
Aug 17 12:50:23 xvarmobile logger: cannot find module pnp:dPNP0200
Aug 17 12:50:23 xvarmobile logger: cannot find module pnp:dPNP0c04
Aug 17 12:50:24 xvarmobile logger: cannot find module pnp:dPNP0103
Aug 17 12:50:24 xvarmobile logger: cannot find module pnp:cPNP0200
Aug 17 12:50:24 xvarmobile logger: cannot find module pnp:dPNP0800
Aug 17 12:50:24 xvarmobile logger: cannot find module pnp:cPNP0103
Aug 17 12:50:24 xvarmobile logger: cannot find module pnp:cPNP0800
Aug 17 12:50:24 xvarmobile logger: cannot find module pnp:cPNP0c04
Aug 17 12:50:28 xvarmobile init: Entering runlevel: 3
What follows before and after that is the usual booting procedure, ending with network config, etc.
Now, I could be wrong, but that looks like that all might be something of a problem
A test of 'modprobe acpi' resulted in:
FATAL: Error inserting acpi_cpureq (/lib/modules/2.6.26-ARCH/kernel/arch/x86/kernel/cpu/cpufreq/acpi-cpufreq.ko): No such device
First of all, why is it looking in the x86 kernel arch when I'm running a x86_64 kernel?
Also (and definitely related), the daemon acpid will not run.
Booting with pnpbios=off in menu.1st does nothing, and the freezes continue. Hope someone can help with this. I'll try blacklisting cpufreq for now.
Edit: Just found something else interesting, but this might not be important. A run of 'pacman -Qs kernel' results in:
local/kernel-headers 2.6.25.8-1 (base)
Kernel headers sanitized for use in userspace
local/kernel26 2.6.26.2-1 (base)
The Linux Kernel and modules
Any reason why we have kernel headers which are a version behind our kernel??
Edit2: A quick check of /lib/modules/2.6.26-ARCH/kernel/arch reveals that I dont even HAVE a x86_64 arch directory. What is up with that?
Last edited by l33tunderground (2008-08-17 17:38:34)
Offline
Confirmed. It may be useful to file a bug report here.
Offline
Hahaha
This is going to sound really silly, but which part are you confirming. I don't want to file a bug report for some random occurance on my computer.
Offline
I believe he's confirming that it with Arch64 that folder shows up as x86, as it's the same on my system.
Offline
Ok. I'll still wait for his conformation on that before I file the report. Thanks though, kett.
Any idea if this affects system stability? I don't know what it is, but on both x32 and x64 my system locks up. It doesn't do that with every distro though (Wolvix and PCLinuxOS run fine), so I'm convinced it must just be a module error. I have no clue which one though
Offline
Just for reference, I'll post some ls* stuff here
lsmod:
Module Size Used by
ipv6 308744 8
ext2 74000 1
joydev 14208 0
serio_raw 8324 0
psmouse 44828 0
pcspkr 4992 0
ehci_hcd 40076 0
k8temp 7296 0
ohci_hcd 25732 0
usbcore 154520 3 ehci_hcd,ohci_hcd
sg 34400 0
evdev 13568 5
thermal 20512 0
processor 39744 2 thermal
fan 7176 0
button 9504 0
battery 14728 0
ac 7304 0
amd74xx 12168 0 [permanent]
ide_core 131868 1 amd74xx
i2c_nforce2 8960 0
i2c_core 24352 1 i2c_nforce2
snd_seq_oss 35712 0
snd_seq_midi_event 9472 1 snd_seq_oss
snd_seq 58464 4 snd_seq_oss,snd_seq_midi_event
snd_seq_device 9492 2 snd_seq_oss,snd_seq
snd_hda_intel 459064 0
snd_hwdep 10760 1 snd_hda_intel
snd_pcm_oss 45696 0
snd_pcm 82440 2 snd_hda_intel,snd_pcm_oss
snd_timer 24848 2 snd_seq,snd_pcm
snd_page_alloc 10768 2 snd_hda_intel,snd_pcm
snd_mixer_oss 19072 1 snd_pcm_oss
snd 64968 9 snd_seq_oss,snd_seq,snd_seq_device,snd_hda_intel,snd_hwdep,snd_pcm_oss,snd_pcm,snd_timer,snd_mixer_oss
soundcore 9632 1 snd
arc4 4224 2
ecb 5376 2
rtl8180 33024 0
mac80211 184368 1 rtl8180
eeprom_93cx6 4480 1 rtl8180
cfg80211 30096 2 rtl8180,mac80211
forcedeth 55952 0
rtc_cmos 13112 0
rtc_core 21060 1 rtc_cmos
rtc_lib 4992 1 rtc_core
ext3 140176 2
jbd 55848 1 ext3
mbcache 10372 2 ext2,ext3
sr_mod 18884 0
cdrom 39592 1 sr_mod
sd_mod 27328 5
ata_generic 8196 0
pata_amd 15748 4
pata_acpi 7296 0
libata 167648 3 ata_generic,pata_amd,pata_acpi
scsi_mod 112504 4 sg,sr_mod,sd_mod,libata
dock 11296 1 libata
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:03.0 PCI bridge: nVidia Corporation C51 PCI Express Bridge (rev a1)
00:05.0 VGA compatible controller: nVidia Corporation MCP51 PCI-X GeForce Go 6100 (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: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
06:09.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8185 IEEE 802.11a/b/g Wireless LAN Controller (rev 20)
lshwd:
00:00.0 Class 0500: nVidia Corp.|C51 Host Bridge (unknown)
00:00.1 Class 0500: nVidia Corp.|C51 Memory Controller 0 (unknown)
00:00.2 Class 0500: nVidia Corp.|C51 Memory Controller 1 (unknown)
00:00.3 Class 0500: nVidia Corp.|C51 Memory Controller 5 (unknown)
00:00.4 Class 0500: nVidia Corp.|C51 Memory Controller 4 (unknown)
00:00.5 Class 0500: nVidia Corp.|C51 Host Bridge (unknown)
00:00.6 Class 0500: nVidia Corp.|C51 Memory Controller 3 (unknown)
00:00.7 Class 0500: nVidia Corp.|C51 Memory Controller 2 (unknown)
00:03.0 Class 0604: nVidia Corp.|C51 PCI Express Bridge (unknown)
00:05.0 Class 0300: nVidia Corp.|GeForce Go 6100 (nv)
00:09.0 Class 0500: nVidia Corp.|MCP51 Host Bridge (unknown)
00:0a.0 Class 0601: nVidia Corp.|MCP51 LPC Bridge (unknown)
00:0a.1 Class 0c05: nVidia Corp.|MCP51 SMBus (i2c-nforce2)
00:0a.3 Class 0b40: nVidia Corp.|MCP51 PMU (unknown)
00:0b.0 Class 0c03: nVidia Corp.|MCP51 USB Controller (unknown)
00:0b.1 Class 0c03: nVidia Corp.|MCP51 USB Controller (unknown)
00:0d.0 Class 0101: nVidia Corp.|MCP51 IDE (amd74xx)
00:10.0 Class 0604: nVidia Corp.|MCP51 PCI Bridge (unknown)
00:10.1 Class 0403: nVidia Corp.|MCP51 High Definition Audio (snd-hda-intel)
00:14.0 Class 0680: nVidia Corp.|MCP51 Ethernet Controller (forcedeth)
00:18.0 Class 0600: Advanced Micro Devices|K8 [Athlon64/Opteron] HyperTransport Technology Configuration (unknown)
00:18.1 Class 0600: Advanced Micro Devices|K8 [Athlon64/Opteron] Address Map (unknown)
00:18.2 Class 0600: Advanced Micro Devices|K8 [Athlon64/Opteron] DRAM Controller (unknown)
00:18.3 Class 0600: Advanced Micro Devices|K8 [Athlon64/Opteron] Miscellaneous Control (amd64-agp)
06:09.0 Class 0200: Realtek Semiconductor|RTL8185 Realtek RTL8185 Wireless LAN (Mini-)PCI NIC (r8180)
---:--- Mouse: Generic PS/2 Wheel Mouse [/dev/psaux] (msintellips/2)
The only module I am not able to load is amd64-agp I'm not sure exactly what it does, but every other module listed there is now in my rc.conf. Some I just put there after looking at this output so we'll see what happens.
I'll try and recreate the freeze to see if that didn't fix it, but it's very finicky. It usually only happens when firefox is open, so this all could be just some issue related to firefox or one of its dependencies. Regardless, I don't know if firefox is the issue, or if it's just creating enough CPU load to unleash the bad effects of the errors I'm getting above, so I'll continue trying to see if I can get them fixed, even if the freeze doesn't reoccur.
Last edited by l33tunderground (2008-08-17 20:24:38)
Offline
Hahaha
This is going to sound really silly, but which part are you confirming. I don't want to file a bug report for some random occurance on my computer.
Makes sense to me. And, all of the above:
[skottish@iasE ~]$ sudo cat /var/log/everything.log | grep -i cannot
Aug 17 07:15:51 iasE logger: cannot find module dmi:bvnAwardSoftwareInternational,Inc.:bvrF5:bd08/09/2006:svn:pn:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-M55PLUS-S3G:rvrx.x:cvn:ct3:cvr:
Aug 17 07:15:51 iasE logger: cannot find module acpi:LNXSYSTM:
Aug 17 07:15:51 iasE logger: cannot find module pci:v000010DEd000002F9sv00001458sd00005000bc05sc00i00
Aug 17 07:15:51 iasE logger: cannot find module pci:v000010DEd000002FEsv00001458sd00005000bc05sc00i00
Aug 17 07:15:51 iasE logger: cannot find module pci:v000010DEd000002F5sv00001458sd00005000bc05sc00i00
Aug 17 07:15:51 iasE logger: cannot find module pci:v000010DEd000002F8sv00001458sd00005000bc05sc00i00
Aug 17 07:15:51 iasE logger: cannot find module pci:v000010DEd000002FAsv00001458sd00005000bc05sc00i00
Aug 17 07:15:51 iasE logger: cannot find module acpi:PNP0C01:
Aug 17 07:15:51 iasE logger: cannot find module pci:v000010DEd000002FFsv00001458sd00005000bc05sc00i00
Aug 17 07:15:52 iasE logger: cannot find module acpi:PNP0400:
Aug 17 07:15:52 iasE logger: cannot find module acpi:PNP0000:
Aug 17 07:15:52 iasE logger: cannot find module acpi:PNP0200:
Aug 17 07:15:52 iasE logger: cannot find module acpi:PNP0501:
Aug 17 07:15:52 iasE logger: cannot find module acpi:PNP0800:
Aug 17 07:15:52 iasE logger: cannot find module acpi:PNP0C02:
Aug 17 07:15:52 iasE logger: cannot find module acpi:PNP0C04:
Aug 17 07:15:52 iasE logger: cannot find module acpi:PNP0100:
Aug 17 07:15:52 iasE logger: cannot find module acpi:PNP0B00:
Aug 17 07:15:52 iasE logger: cannot find module acpi:PNP0C02:
Aug 17 07:15:52 iasE logger: cannot find module pci:v000010DEd0000027Fsv00001458sd00005000bc05sc00i00
Aug 17 07:15:52 iasE logger: cannot find module pci:v000010DEd0000027Esv00001458sd00005000bc05sc00i00
Aug 17 07:15:52 iasE logger: cannot find module pci:v000010DEd00000260sv00001458sd00005001bc06sc01i00
Aug 17 07:15:52 iasE logger: cannot find module pci:v000010DEd00000270sv00001458sd00005001bc05sc00i00
Aug 17 07:15:52 iasE logger: cannot find module pci:v000010DEd00000272sv00001458sd00000264bc05sc00i00
Aug 17 07:15:52 iasE logger: cannot find module pci:v000010DEd0000026Fsv00000000sd00000000bc06sc04i01
Aug 17 07:15:52 iasE logger: cannot find module pci:v00001022d00001100sv00000000sd00000000bc06sc00i00
Aug 17 07:15:52 iasE logger: cannot find module pci:v00001022d00001101sv00000000sd00000000bc06sc00i00
Aug 17 07:15:52 iasE logger: cannot find module pci:v00001022d00001102sv00000000sd00000000bc06sc00i00
Aug 17 07:15:52 iasE logger: cannot find module serio:ty06pr00id00ex00
Aug 17 07:15:52 iasE logger: cannot find module platform:vesafb
Aug 17 07:15:52 iasE logger: cannot find module pnp:dPNP0a08
Aug 17 07:15:52 iasE logger: cannot find module pnp:dPNP0c04
Aug 17 07:15:52 iasE logger: cannot find module pnp:dPNP0200
Aug 17 07:15:52 iasE logger: cannot find module pnp:cPNP0a08
Aug 17 07:15:52 iasE logger: cannot find module pnp:cPNP0c04
Aug 17 07:15:52 iasE logger: cannot find module pnp:dPNP0a03
Aug 17 07:15:52 iasE logger: cannot find module pnp:cPNP0200
Aug 17 07:15:52 iasE logger: cannot find module pnp:cPNP0a03
Aug 17 07:15:52 iasE logger: cannot find module pnp:dPNP0800
Aug 17 07:15:52 iasE logger: cannot find module pnp:cPNP0800
Aug 17 07:15:53 iasE logger: cannot find module platform:parport_pc
Aug 17 07:15:53 iasE logger: cannot find module platform:parport_pc
Aug 17 07:15:53 iasE logger: cannot find module pnp:cPNP0400
[skottish@iasE ~]$ sudo modprobe acpi
FATAL: Error inserting acpi_cpufreq (/lib/modules/2.6.26-ARCH/kernel/arch/x86/kernel/cpu/cpufreq/acpi-cpufreq.ko): No such device
[skottish@iasE ~]$ ls /lib/modules/2.6.26-ARCH/kernel/arch
x86
Offline
skottish, could you post some of your ls{mod,pci,hwd}? I want to see how similar of hardware we have. Also, do you suppose that this means we're running a 32 bit kernel instead of 64? I don't imagine that it does, seeing how we're installing other x86_64 packages.
Edit: never mind, uname -a lists the kernel as x86_64... I guess it just compiled the x86 modules, then?
Last edited by l33tunderground (2008-08-17 23:24:59)
Offline
Bug report submitted. http://bugs.archlinux.org/task/11244
I listed all of this under the same bug, since I believe that the fact that acpi cannot be properly loaded is a result of this kernel issue.
Offline
Ok, so I'm looking at the PKGBUILD for kernel26, and I've got a couple questions. I'm going to try and rebuild it anyway, but I'll post them for record keeping's sake. There's a variable in the build() section called KARCH, and it's set to x86.
build() {
KARCH=x86
Also, on the 45th line there's a reference to a variable $CARCH, which is not declared or referred to earlier in the PKGBUILD. I'm assuming that means it's a variable used at some point in one of the kernel's build files, but I just thought I'd mention it. This is the first time it's mentioned.
if [ "$CARCH" = "x86_64" ]; then
cat ../config.x86_64 >./.config
else
cat ../config >./.config
fi
So, I'm gonna play around with this package a bit and see what happens
Offline
Yeah, I'm pretty sure it's having KARCH set to x86. There's a section in the pkgbuild
mkdir -p $startdir/pkg/usr/src/linux-${_kernver}/arch/$KARCH/kernel
cp arch/$KARCH/Makefile $startdir/pkg/usr/src/linux-${_kernver}/arch/$KARCH/
if [ "$CARCH" = "i686" ]; then
cp arch/$KARCH/Makefile_32.cpu $startdir/pkg/usr/src/linux-${_kernver}/arch/$KARCH/
fi
cp arch/$KARCH/kernel/asm-offsets.s $startdir/pkg/usr/src/linux-${_kernver}/arch/$KARCH/kernel/
that seems to imply that as long as KARCH is always x86 there will never be a x86_64 folder. I don't know if this is what the Arch developers want, but the package is building now so we'll see what happens
Offline
Ok, so after reading some of the Changelogs from the kernel repositories, it would seem there there is not an issue with the x86 directory. At some point (I couldn't find exactly when, but I believe it was between 2.6.23 and 2.6.24) the i386 and x86_64 directories were merged into x86. So, that in and of itself is not inherently the issue. I have not requested that the bug report be removed, since there is still some issue with the ACPI module that may stem from this package. The topic remains UNSOLVED.
Offline
Well, I'm going to request closure on the bug that I submitted as it is. I just installed Arch64 on my desktop and there are no error messages of the sort like we have. This is not a kernel package issue; it is a hardware issue. This topic will stay open, but I don't want to distract anyone with the bugreport. The error about acpi_cpufreq still exists, but 1. The file does exist in the said directory, it's just not the right module for my system. You can check this by navigating to the directory in the modprobe error and try to insmod the file. It complains about the device not being there. The proper module for my machines is powernow-k8, so that error is not critical either. The only thing that is weird is the first error -- the one from everything.log. That one is serious and this topic will remain unsolved until I can get those to go away, or figure out that I can't.
Offline