Re: OOPS on 2.4.4-ac4
> update to 2.4.4-ac8 today. In regards to the module the source code is > available from nvidia for inspection. The library that they want you to Its unreadable and the binary stuff touches hardware directly. Nvidia driver loaded - bugs to nvidia. vmware loaded bugs to vmware, both loaded, god help you, nobody else will - 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: OOPS on 2.4.4-ac4
The nvidia driver has been fine for me up to 2.4.2-ac20. I am going to update to 2.4.4-ac8 today. In regards to the module the source code is available from nvidia for inspection. The library that they want you to use with it is binary only. The library should be source code as well but the powers that be have said otherwise. I will keep tabs on the release for kernel oops as well. I am using XFree 4.0.3 with NVIDIA-0.9-769 Stephen On Sat, 12 May 2001, Alan Cox wrote: > > > Ok, I will remove vmware and switch from the nvidia driver the nv > driver from > XFree 4.3. Maybe I get the oops again. > > Let me know if you do. I've got some other dmfe reports I'm looking at so its > quite possible that is the trigger, but this time I'll be able to know its not > giant binary stuff 8) > - > 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/ > -- --- Buyer's Guide for a Operating System: Don't care to know: Mac Don't mind knowing but not too much: Windows Hit me! I can take it!: Linux - 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: OOPS on 2.4.4-ac4
The nvidia driver has been fine for me up to 2.4.2-ac20. I am going to update to 2.4.4-ac8 today. In regards to the module the source code is available from nvidia for inspection. The library that they want you to use with it is binary only. The library should be source code as well but the powers that be have said otherwise. I will keep tabs on the release for kernel oops as well. I am using XFree 4.0.3 with NVIDIA-0.9-769 Stephen On Sat, 12 May 2001, Alan Cox wrote: Ok, I will remove vmware and switch from the nvidia driver the nv driver from XFree 4.3. Maybe I get the oops again. Let me know if you do. I've got some other dmfe reports I'm looking at so its quite possible that is the trigger, but this time I'll be able to know its not giant binary stuff 8) - 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/ -- --- Buyer's Guide for a Operating System: Don't care to know: Mac Don't mind knowing but not too much: Windows Hit me! I can take it!: Linux - 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: OOPS on 2.4.4-ac4
update to 2.4.4-ac8 today. In regards to the module the source code is available from nvidia for inspection. The library that they want you to Its unreadable and the binary stuff touches hardware directly. Nvidia driver loaded - bugs to nvidia. vmware loaded bugs to vmware, both loaded, god help you, nobody else will - 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: OOPS on 2.4.4-ac4
Hi, so I removed the binary modules and one day got by without oops. So I inserted my TV Card Askey CPH051 and tried to record a videostream with kwintv. After a while I got an oops 0002 (prev was ) saying Unable to handle kernel paging request at virtual address ... which I also found in the previous oops. I hope this time the oops report is usefull for you. On 12-May-01 Alan Cox wrote: >> >> Ok, I will remove vmware and switch from the nvidia driver the nv driver >> from >> XFree 4.3. Maybe I get the oops again. > > Let me know if you do. I've got some other dmfe reports I'm looking at so its > quite possible that is the trigger, but this time I'll be able to know its > not > giant binary stuff 8) Ciao, Ingo "Here you will see the heart and soul of Babylon 5...also its spleen, its kidneys, a veritable parade of internal organs." -- Londo (to Lennier), "The Quality of Mercy" ksymoops 2.4.1 on i686 2.4.4-ac4. Options used -V (default) -k /proc/ksyms (default) -l /proc/modules (default) -o /lib/modules/2.4.4-ac4/ (default) -m /usr/src/linux/System.map (default) Warning: You did not tell me where to find symbol information. I will assume that the log matches the kernel and modules that are running right now and I'll use the default options above for symbol resolution. If the current kernel and/or modules do not match the log, you can get more accurate output by telling me the kernel version and where to find map, modules, ksyms etc. ksymoops -h explains the options. May 12 18:13:19 lara kernel: ac97_codec: AC97 Audio codec, id: 0x4943:0x4511 (IC E1232) May 13 03:46:14 lara kernel: ac97_codec: AC97 Audio codec, id: 0x4943:0x4511 (IC E1232) May 13 11:27:29 lara kernel: ac97_codec: AC97 Audio codec, id: 0x4943:0x4511 (IC E1232) May 13 11:51:11 lara kernel: ac97_codec: AC97 Audio codec, id: 0x4943:0x4511 (IC E1232) May 13 12:47:24 lara kernel: ac97_codec: AC97 Audio codec, id: 0x4943:0x4511 (IC E1232) May 13 12:55:45 lara kernel: Unable to handle kernel paging request at virtual a ddress 00050311 May 13 12:55:45 lara kernel: c012010b May 13 12:55:45 lara kernel: Oops: 0002 May 13 12:55:45 lara kernel: CPU:0 May 13 12:55:45 lara kernel: EIP:0010:[do_mmap_pgoff+475/1040] May 13 12:55:45 lara kernel: EFLAGS: 00010206 May 13 12:55:45 lara kernel: eax: c8914228 ebx: c1081014 ecx: c1080ff8 edx : 00050311 May 13 12:55:45 lara kernel: esi: c1080ff8 edi: c8914228 ebp: 01e9 esp : c8e4def4 May 13 12:55:45 lara kernel: ds: 0018 es: 0018 ss: 0018 May 13 12:55:45 lara kernel: Process kwintv (pid: 666, stackpage=c8e4d000) May 13 12:55:45 lara kernel: Stack: c0126476 c1080ff8 c0280938 c0280b10 0001 c01277fd c0280938 May 13 12:55:45 lara kernel: c0280b18 d3f97f14 c01278f2 c0280b0c 0001 May 13 12:55:45 lara kernel:0001 c8e4df94 0001f628 d3f97f14 0005 0001 c0280b0c May 13 12:55:45 lara kernel: Call Trace: [kmem_cache_shrink+6/64] [swap_out_vma+ 141/224] [swap_out+66/176] [filemap_sync+162/544] [shmem_parse_options+6/464] May 13 12:55:45 lara kernel: Code: 89 02 8b 41 10 8b 51 34 c7 41 08 00 00 00 00 85 c0 74 03 89 Using defaults from ksymoops -t elf32-i386 -a i386 Code; Before first symbol <_EIP>: Code; Before first symbol 0: 89 02 mov%eax,(%edx) Code; 0002 Before first symbol 2: 8b 41 10 mov0x10(%ecx),%eax Code; 0005 Before first symbol 5: 8b 51 34 mov0x34(%ecx),%edx Code; 0008 Before first symbol 8: c7 41 08 00 00 00 00 movl $0x0,0x8(%ecx) Code; 000f Before first symbol f: 85 c0 test %eax,%eax Code; 0011 Before first symbol 11: 74 03 je 16 <_EIP+0x16> 0016 Before first sy mbol Code; 0013 Before first symbol 13: 89 00 mov%eax,(%eax) 1 warning issued. Results may not be reliable.
Re: OOPS on 2.4.4-ac4
Hi, so I removed the binary modules and one day got by without oops. So I inserted my TV Card Askey CPH051 and tried to record a videostream with kwintv. After a while I got an oops 0002 (prev was ) saying Unable to handle kernel paging request at virtual address ... which I also found in the previous oops. I hope this time the oops report is usefull for you. On 12-May-01 Alan Cox wrote: Ok, I will remove vmware and switch from the nvidia driver the nv driver from XFree 4.3. Maybe I get the oops again. Let me know if you do. I've got some other dmfe reports I'm looking at so its quite possible that is the trigger, but this time I'll be able to know its not giant binary stuff 8) Ciao, Ingo Here you will see the heart and soul of Babylon 5...also its spleen, its kidneys, a veritable parade of internal organs. -- Londo (to Lennier), The Quality of Mercy ksymoops 2.4.1 on i686 2.4.4-ac4. Options used -V (default) -k /proc/ksyms (default) -l /proc/modules (default) -o /lib/modules/2.4.4-ac4/ (default) -m /usr/src/linux/System.map (default) Warning: You did not tell me where to find symbol information. I will assume that the log matches the kernel and modules that are running right now and I'll use the default options above for symbol resolution. If the current kernel and/or modules do not match the log, you can get more accurate output by telling me the kernel version and where to find map, modules, ksyms etc. ksymoops -h explains the options. May 12 18:13:19 lara kernel: ac97_codec: AC97 Audio codec, id: 0x4943:0x4511 (IC E1232) May 13 03:46:14 lara kernel: ac97_codec: AC97 Audio codec, id: 0x4943:0x4511 (IC E1232) May 13 11:27:29 lara kernel: ac97_codec: AC97 Audio codec, id: 0x4943:0x4511 (IC E1232) May 13 11:51:11 lara kernel: ac97_codec: AC97 Audio codec, id: 0x4943:0x4511 (IC E1232) May 13 12:47:24 lara kernel: ac97_codec: AC97 Audio codec, id: 0x4943:0x4511 (IC E1232) May 13 12:55:45 lara kernel: Unable to handle kernel paging request at virtual a ddress 00050311 May 13 12:55:45 lara kernel: c012010b May 13 12:55:45 lara kernel: Oops: 0002 May 13 12:55:45 lara kernel: CPU:0 May 13 12:55:45 lara kernel: EIP:0010:[do_mmap_pgoff+475/1040] May 13 12:55:45 lara kernel: EFLAGS: 00010206 May 13 12:55:45 lara kernel: eax: c8914228 ebx: c1081014 ecx: c1080ff8 edx : 00050311 May 13 12:55:45 lara kernel: esi: c1080ff8 edi: c8914228 ebp: 01e9 esp : c8e4def4 May 13 12:55:45 lara kernel: ds: 0018 es: 0018 ss: 0018 May 13 12:55:45 lara kernel: Process kwintv (pid: 666, stackpage=c8e4d000) May 13 12:55:45 lara kernel: Stack: c0126476 c1080ff8 c0280938 c0280b10 0001 c01277fd c0280938 May 13 12:55:45 lara kernel: c0280b18 d3f97f14 c01278f2 c0280b0c 0001 May 13 12:55:45 lara kernel:0001 c8e4df94 0001f628 d3f97f14 0005 0001 c0280b0c May 13 12:55:45 lara kernel: Call Trace: [kmem_cache_shrink+6/64] [swap_out_vma+ 141/224] [swap_out+66/176] [filemap_sync+162/544] [shmem_parse_options+6/464] May 13 12:55:45 lara kernel: Code: 89 02 8b 41 10 8b 51 34 c7 41 08 00 00 00 00 85 c0 74 03 89 Using defaults from ksymoops -t elf32-i386 -a i386 Code; Before first symbol _EIP: Code; Before first symbol 0: 89 02 mov%eax,(%edx) Code; 0002 Before first symbol 2: 8b 41 10 mov0x10(%ecx),%eax Code; 0005 Before first symbol 5: 8b 51 34 mov0x34(%ecx),%edx Code; 0008 Before first symbol 8: c7 41 08 00 00 00 00 movl $0x0,0x8(%ecx) Code; 000f Before first symbol f: 85 c0 test %eax,%eax Code; 0011 Before first symbol 11: 74 03 je 16 _EIP+0x16 0016 Before first sy mbol Code; 0013 Before first symbol 13: 89 00 mov%eax,(%eax) 1 warning issued. Results may not be reliable.
Re: OOPS on 2.4.4-ac4
> > Ok, I will remove vmware and switch from the nvidia driver the nv driver from > XFree 4.3. Maybe I get the oops again. Let me know if you do. I've got some other dmfe reports I'm looking at so its quite possible that is the trigger, but this time I'll be able to know its not giant binary stuff 8) - 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: OOPS on 2.4.4-ac4
On 12-May-01 Alan Cox wrote: >> computer during this time.=20 >> So I don't know if this has to do with the new networkcard, the new NVIDIA >> Driver 0.9-769 I installed yesterday with XFree 4.3 or something else. The = > >> --- >> Module Size Used by >> via82cxxx_audio16800 2 (autoclean) >> soundcore 3600 2 (autoclean) [via82cxxx_audio] >> ac97_codec 8560 0 (autoclean) [via82cxxx_audio] >> NVdriver 626480 12 (autoclean) >> vmnet 16224 3 >> vmmon 18224 0 >> dmfe9408 1 (autoclean) > > You are using binary only drivers. We can't debug them (least of all a 625K > module thats almost the size of the kernel). Duplicate the problems on a > boot > that never loaded vmware or nvdriver and its interesting, otherwise take it > up with vmware and nvidia - they have our source we dont have theirs Ok, I will remove vmware and switch from the nvidia driver the nv driver from XFree 4.3. Maybe I get the oops again. Ciao, Ingo "The war has already begun, Captain. All that remains now is honor and death." -- Deeron, "Points of Departure" - 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: OOPS on 2.4.4-ac4
> computer during this time.=20 > So I don't know if this has to do with the new networkcard, the new NVIDIA > Driver 0.9-769 I installed yesterday with XFree 4.3 or something else. The = > --- > Module Size Used by > via82cxxx_audio16800 2 (autoclean) > soundcore 3600 2 (autoclean) [via82cxxx_audio] > ac97_codec 8560 0 (autoclean) [via82cxxx_audio] > NVdriver 626480 12 (autoclean) > vmnet 16224 3 > vmmon 18224 0 > dmfe9408 1 (autoclean) You are using binary only drivers. We can't debug them (least of all a 625K module thats almost the size of the kernel). Duplicate the problems on a boot that never loaded vmware or nvdriver and its interesting, otherwise take it up with vmware and nvidia - they have our source we dont have theirs - 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/
OOPS on 2.4.4-ac4
Hello, I have the following Hardware installed: Epox EP-8KTA2 with Athlon 800 onboard sound enabled with kernel driver cat /proc/pci PCI devices found: Bus 0, device 0, function 0: Host bridge: VIA Technologies, Inc. VT8363/8365 [KT133/KM133] (rev 2). Master Capable. Latency=8. Prefetchable 32 bit memory at 0xd000 [0xd3ff]. Bus 0, device 1, function 0: PCI bridge: VIA Technologies, Inc. VT8363/8365 [KT133/KM133 AGP] (rev 0). Master Capable. No bursts. Min Gnt=12. Bus 0, device 7, function 0: ISA bridge: VIA Technologies, Inc. VT82C686 [Apollo Super South] (rev 64). Bus 0, device 7, function 4: Bridge: VIA Technologies, Inc. VT82C686 [Apollo Super ACPI] (rev 64). Bus 0, device 7, function 5: Multimedia audio controller: VIA Technologies, Inc. AC97 Audio Controller (rev 80). IRQ 15. I/O at 0x9c00 [0x9cff]. I/O at 0xa000 [0xa003]. I/O at 0xa400 [0xa403]. Bus 0, device 9, function 0: Unknown mass storage controller: Triones Technologies, Inc. HPT366 (rev 3). IRQ 11. Master Capable. Latency=120. Min Gnt=8.Max Lat=8. I/O at 0xa800 [0xa807]. I/O at 0xac00 [0xac03]. I/O at 0xb000 [0xb007]. I/O at 0xb400 [0xb403]. I/O at 0xb800 [0xb8ff]. Bus 0, device 10, function 0: SCSI storage controller: Adaptec AIC-7881U (rev 0). IRQ 15. Master Capable. Latency=32. Min Gnt=8.Max Lat=8. I/O at 0xbc00 [0xbcff]. Non-prefetchable 32 bit memory at 0xd800 [0xd8000fff]. Bus 0, device 13, function 0: Ethernet controller: Davicom Semiconductor, Inc. Ethernet 100/10 MBit (rev 49). IRQ 10. Master Capable. Latency=32. Min Gnt=20.Max Lat=40. I/O at 0xc000 [0xc0ff]. Non-prefetchable 32 bit memory at 0xd8001000 [0xd80010ff]. Bus 1, device 0, function 0: VGA compatible controller: nVidia Corporation Riva TnT 128 [NV04] (rev 4). IRQ 12. Master Capable. Latency=248. Min Gnt=5.Max Lat=1. Non-prefetchable 32 bit memory at 0xd400 [0xd4ff]. Prefetchable 32 bit memory at 0xd600 [0xd6ff]. I had trouble with a Networkcard with Realtek RTL 8139A Chip wich does not work proper with the via Chip. So today I changed the card with one from Fiober Line wich has a Davicom DM 9102AF Chip. After some stress test I thought this card was doing fine. Now I had to leave and prepared the computer for my Girlfried. Loggin in under her account, starting KDE 2.1.2 under Suse 7.1 and switched of the Monitor. 6 Hours later I found this oops and my girlfriend hasn't used the computer during this time. So I don't know if this has to do with the new networkcard, the new NVIDIA Driver 0.9-769 I installed yesterday with XFree 4.3 or something else. The only thing I know is, that I never had this oops before. If there is something more I can do to help to find the reason please tell me, but please more than three words, I'm no kernel Hacker, I just like to help. I included the part of /var/log/messages. I left between the May 11 17:33:44 lara -- MARK -- and May 11 17:53:44 lara -- MARK -- entry and came back at May 12 00:43:36 vmware -version VMware Workstation protocol=6 build=build-1118 product='2.0.4 build-1118' My modules: --- Module Size Used by via82cxxx_audio16800 2 (autoclean) soundcore 3600 2 (autoclean) [via82cxxx_audio] ac97_codec 8560 0 (autoclean) [via82cxxx_audio] NVdriver 626480 12 (autoclean) vmnet 16224 3 vmmon 18224 0 dmfe9408 1 (autoclean) --- ksymoops 2.4.1 on i686 2.4.4-ac4. Options used -V (default) -k /proc/ksyms (default) -l /proc/modules (default) -o /lib/modules/2.4.4-ac4/ (default) -m /usr/src/linux/System.map (default) Warning: You did not tell me where to find symbol information. I will assume that the log matches the kernel and modules that are running right now and I'll use the default options above for symbol resolution. If the current kernel and/or modules do not match the log, you can get more accurate output by telling me the kernel version and where to find map, modules, ksyms etc. ksymoops -h explains the options. May 12 00:15:50 lara kernel: Unable to handle kernel paging request at virtual address 417563e8 May 12 00:15:50 lara kernel: c012ffb4 May 12 00:15:50 lara kernel: Oops: May 12 00:15:50 lara kernel: CPU:0 May 12 00:15:50 lara kernel: EIP:0010:[set_blocksize+404/544] May 12 00:15:50 lara kernel: EFLAGS: 00010a87 May 12 00:15:50 lara kernel: eax: 417563c0 ebx: ecx: c11956bc edx: May 12 00:15:50 lara kernel: esi: 417563c0 edi: c17563c0 ebp: c11956a0 esp: c356fda0 May 12 00:15:50 lara kernel: ds: 0018 es: 0018 ss:
OOPS on 2.4.4-ac4
Hello, I have the following Hardware installed: Epox EP-8KTA2 with Athlon 800 onboard sound enabled with kernel driver cat /proc/pci PCI devices found: Bus 0, device 0, function 0: Host bridge: VIA Technologies, Inc. VT8363/8365 [KT133/KM133] (rev 2). Master Capable. Latency=8. Prefetchable 32 bit memory at 0xd000 [0xd3ff]. Bus 0, device 1, function 0: PCI bridge: VIA Technologies, Inc. VT8363/8365 [KT133/KM133 AGP] (rev 0). Master Capable. No bursts. Min Gnt=12. Bus 0, device 7, function 0: ISA bridge: VIA Technologies, Inc. VT82C686 [Apollo Super South] (rev 64). Bus 0, device 7, function 4: Bridge: VIA Technologies, Inc. VT82C686 [Apollo Super ACPI] (rev 64). Bus 0, device 7, function 5: Multimedia audio controller: VIA Technologies, Inc. AC97 Audio Controller (rev 80). IRQ 15. I/O at 0x9c00 [0x9cff]. I/O at 0xa000 [0xa003]. I/O at 0xa400 [0xa403]. Bus 0, device 9, function 0: Unknown mass storage controller: Triones Technologies, Inc. HPT366 (rev 3). IRQ 11. Master Capable. Latency=120. Min Gnt=8.Max Lat=8. I/O at 0xa800 [0xa807]. I/O at 0xac00 [0xac03]. I/O at 0xb000 [0xb007]. I/O at 0xb400 [0xb403]. I/O at 0xb800 [0xb8ff]. Bus 0, device 10, function 0: SCSI storage controller: Adaptec AIC-7881U (rev 0). IRQ 15. Master Capable. Latency=32. Min Gnt=8.Max Lat=8. I/O at 0xbc00 [0xbcff]. Non-prefetchable 32 bit memory at 0xd800 [0xd8000fff]. Bus 0, device 13, function 0: Ethernet controller: Davicom Semiconductor, Inc. Ethernet 100/10 MBit (rev 49). IRQ 10. Master Capable. Latency=32. Min Gnt=20.Max Lat=40. I/O at 0xc000 [0xc0ff]. Non-prefetchable 32 bit memory at 0xd8001000 [0xd80010ff]. Bus 1, device 0, function 0: VGA compatible controller: nVidia Corporation Riva TnT 128 [NV04] (rev 4). IRQ 12. Master Capable. Latency=248. Min Gnt=5.Max Lat=1. Non-prefetchable 32 bit memory at 0xd400 [0xd4ff]. Prefetchable 32 bit memory at 0xd600 [0xd6ff]. I had trouble with a Networkcard with Realtek RTL 8139A Chip wich does not work proper with the via Chip. So today I changed the card with one from Fiober Line wich has a Davicom DM 9102AF Chip. After some stress test I thought this card was doing fine. Now I had to leave and prepared the computer for my Girlfried. Loggin in under her account, starting KDE 2.1.2 under Suse 7.1 and switched of the Monitor. 6 Hours later I found this oops and my girlfriend hasn't used the computer during this time. So I don't know if this has to do with the new networkcard, the new NVIDIA Driver 0.9-769 I installed yesterday with XFree 4.3 or something else. The only thing I know is, that I never had this oops before. If there is something more I can do to help to find the reason please tell me, but please more than three words, I'm no kernel Hacker, I just like to help. I included the part of /var/log/messages. I left between the May 11 17:33:44 lara -- MARK -- and May 11 17:53:44 lara -- MARK -- entry and came back at May 12 00:43:36 vmware -version VMware Workstation protocol=6 build=build-1118 product='2.0.4 build-1118' My modules: --- Module Size Used by via82cxxx_audio16800 2 (autoclean) soundcore 3600 2 (autoclean) [via82cxxx_audio] ac97_codec 8560 0 (autoclean) [via82cxxx_audio] NVdriver 626480 12 (autoclean) vmnet 16224 3 vmmon 18224 0 dmfe9408 1 (autoclean) --- ksymoops 2.4.1 on i686 2.4.4-ac4. Options used -V (default) -k /proc/ksyms (default) -l /proc/modules (default) -o /lib/modules/2.4.4-ac4/ (default) -m /usr/src/linux/System.map (default) Warning: You did not tell me where to find symbol information. I will assume that the log matches the kernel and modules that are running right now and I'll use the default options above for symbol resolution. If the current kernel and/or modules do not match the log, you can get more accurate output by telling me the kernel version and where to find map, modules, ksyms etc. ksymoops -h explains the options. May 12 00:15:50 lara kernel: Unable to handle kernel paging request at virtual address 417563e8 May 12 00:15:50 lara kernel: c012ffb4 May 12 00:15:50 lara kernel: Oops: May 12 00:15:50 lara kernel: CPU:0 May 12 00:15:50 lara kernel: EIP:0010:[set_blocksize+404/544] May 12 00:15:50 lara kernel: EFLAGS: 00010a87 May 12 00:15:50 lara kernel: eax: 417563c0 ebx: ecx: c11956bc edx: May 12 00:15:50 lara kernel: esi: 417563c0 edi: c17563c0 ebp: c11956a0 esp: c356fda0 May 12 00:15:50 lara kernel: ds: 0018 es: 0018 ss:
Re: OOPS on 2.4.4-ac4
computer during this time.=20 So I don't know if this has to do with the new networkcard, the new NVIDIA Driver 0.9-769 I installed yesterday with XFree 4.3 or something else. The = --- Module Size Used by via82cxxx_audio16800 2 (autoclean) soundcore 3600 2 (autoclean) [via82cxxx_audio] ac97_codec 8560 0 (autoclean) [via82cxxx_audio] NVdriver 626480 12 (autoclean) vmnet 16224 3 vmmon 18224 0 dmfe9408 1 (autoclean) You are using binary only drivers. We can't debug them (least of all a 625K module thats almost the size of the kernel). Duplicate the problems on a boot that never loaded vmware or nvdriver and its interesting, otherwise take it up with vmware and nvidia - they have our source we dont have theirs - 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: OOPS on 2.4.4-ac4
On 12-May-01 Alan Cox wrote: computer during this time.=20 So I don't know if this has to do with the new networkcard, the new NVIDIA Driver 0.9-769 I installed yesterday with XFree 4.3 or something else. The = --- Module Size Used by via82cxxx_audio16800 2 (autoclean) soundcore 3600 2 (autoclean) [via82cxxx_audio] ac97_codec 8560 0 (autoclean) [via82cxxx_audio] NVdriver 626480 12 (autoclean) vmnet 16224 3 vmmon 18224 0 dmfe9408 1 (autoclean) You are using binary only drivers. We can't debug them (least of all a 625K module thats almost the size of the kernel). Duplicate the problems on a boot that never loaded vmware or nvdriver and its interesting, otherwise take it up with vmware and nvidia - they have our source we dont have theirs Ok, I will remove vmware and switch from the nvidia driver the nv driver from XFree 4.3. Maybe I get the oops again. Ciao, Ingo The war has already begun, Captain. All that remains now is honor and death. -- Deeron, Points of Departure - 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: OOPS on 2.4.4-ac4
Ok, I will remove vmware and switch from the nvidia driver the nv driver from XFree 4.3. Maybe I get the oops again. Let me know if you do. I've got some other dmfe reports I'm looking at so its quite possible that is the trigger, but this time I'll be able to know its not giant binary stuff 8) - 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/
