Oops in stock 2.2.18
Can anybody shed some light on this? Thanks, --- cut here --- Unable to handle kernel paging request at virtual address e6d94ba1 current->tss.cr3 = 07211000, %cr3 = 07211000 *pde = Oops: CPU:0 EIP:0010:[] Using defaults from ksymoops -t elf32-i386 -a i386 EFLAGS: 00010206 eax: c72e1b0a ebx: c72e1b80 ecx: c15d edx: esi: c731e000 edi: 0024 ebp: esp: c731ff2c ds: 0018 es: 0018 ss: 0018 Process master (pid: 465, process nr: 32, stackpage=c731f000) Stack: c70c6d80 c72060a0 c15d 0001 c012d31f c70c6d80 c15d 0002 c163af30 0010 0145 c731e000 1770 c15d c15d c012d785 003b c731ffa8 c731ffa4 c731e000 bb54 bb4c Call Trace: [] [] [] Code: 8b 43 6c 2b 43 50 3d ff 07 00 00 7e 06 81 ca 04 03 00 00 89 >>EIP; c016faa5<= Trace; c012d31f Trace; c012d785 Trace; c0107b68 Code; c016faa5 <_EIP>: Code; c016faa5<= 0: 8b 43 6c movl 0x6c(%ebx),%eax <= Code; c016faa8 3: 2b 43 50 subl 0x50(%ebx),%eax Code; c016faab 6: 3d ff 07 00 00cmpl $0x7ff,%eax Code; c016fab0 b: 7e 06 jle13 <_EIP+0x13> c016fab8 Code; c016fab2 d: 81 ca 04 03 00orl$0x304,%edx Code; c016fab7 12: 00 Code; c016fab8 13: 89 00 movl %eax,(%eax) 6 warnings issued. Results may not be reliable. - 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/
[2.2.18] Oops in schedule/reschedule
[1.] One line summary of the problem: Oops in schedule [2.] Full description of the problem/report: I am unsure of the actual cause. My machine is running Postfix and INN and both were killed when the oops occurred. These are the only two tasks that appear to have died. [3.] Keywords (i.e., modules, networking, kernel): kernel, oops, schedule, reschedule [4.] Kernel version (from /proc/version): Linux version 2.2.18 (root@gateway) (gcc version 2.7.2.3) #1 Mon Jan 8 01:42:03 EST 2001 [5.] Output of Oops ksymoops 2.3.7 on i586 2.2.18. Options used -V (default) -k /proc/ksyms (default) -l /proc/modules (default) -o /lib/modules/2.2.18/ (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. Warning (compare_maps): ksyms_base symbol module_list_R__ver_module_list not found in System.map. Ignoring ksyms_base entry Unable to handle kernel NULL pointer dereference at virtual address 0001 current->tss.cr3 = 023ef000, %cr3 = 023ef000 *pde = Oops: 0002 CPU:0 EIP:0010:[] Using defaults from ksymoops -t elf32-i386 -a i386 EFLAGS: 00010006 eax: 0001 ebx: c6c4a000 ecx: 0003 edx: 0001 esi: c6c4a000 edi: 0003 ebp: 0003 esp: c6c4bfb0 ds: 0018 es: 0018 ss: 0018 Process dnetc (pid: 7716, process nr: 93, stackpage=c6c4b000) Stack: ea26425b c01f4c00 73bf4b97 c0107c3d 3e39d86e c681e5c8 238b04b1 f754b3f4 ea26425b 73bf4b97 a2f6e117 002b 002a ff00 08071cfe 0023 0203 bf9ffb00 002b Call Trace: [] Code: 00 00 c7 05 00 00 00 00 00 00 00 00 8d 65 ec 5b 5e 5f 89 ec >>EIP; c010f440<= Trace; c0107c3d Code; c010f440 <_EIP>: Code; c010f440<= 0: 00 00 addb %al,(%eax) <= Code; c010f442 2: c7 05 00 00 00movl $0x0,0x0 Code; c010f447 7: 00 00 00 00 00 Code; c010f44c c: 8d 65 ec leal 0xffec(%ebp),%esp Code; c010f44f f: 5bpopl %ebx Code; c010f450 10: 5epopl %esi Code; c010f451 11: 5fpopl %edi Code; c010f452 12: 89 ec movl %ebp,%esp 2 warnings issued. Results may not be reliable. [6.] A small shell script or example program which triggers the problem (if possible) (not applicable) [7.] Environment [7.1.] Software (add the output of the ver_linux script here) -- Versions installed: (if some fields are empty or looks -- unusual then possibly you have very old versions) Linux gateway 2.2.18 #1 Mon Jan 8 01:42:03 EST 2001 i586 unknown Kernel modules 2.4.1 Gnu C 2.7.2.3 Binutils 2.9.1.0.15 Linux C Library2.0.7 Dynamic linker ldd (GNU libc) 2.0.7 Linux C++ Library 2.8.0 Procps 1.2.9 Mount 2.10m Net-tools 1.50 Kbd0.96 Sh-utils 1.16 Modules Loaded nfs ppp slhc ip_masq_irc ip_masq_ftp nfsd lockd sunrpc 3c509 ne 8390 ncr53c8xx [7.2.] Processor information (from /proc/cpuinfo): processor : 0 vendor_id : AuthenticAMD cpu family : 5 model : 6 model name : AMD-K6tm w/ multimedia extensions stepping: 2 cpu MHz : 233.867 cache size : 64 KB fdiv_bug: no hlt_bug : no sep_bug : no f00f_bug: no coma_bug: no fpu : yes fpu_exception : yes cpuid level : 1 wp : yes flags : fpu vme de pse tsc msr mce cx8 sep mmx bogomips: 466.94 [7.3.] Module information (from /proc/modules): nfs71488 1 (autoclean) ppp19728 0 (unused) slhc4384 0 [ppp] ip_masq_irc 1968 0 (unused) ip_masq_ftp 2528 0 nfsd 180432 8 (autoclean) lockd 42288 1 (autoclean) [nfs nfsd] sunrpc 55488 1 (autoclean) [nfs nfsd lockd] 3c509 5584 1 (autoclean) ne 6208 1 (autoclean) 83906144 0 (autoclean) [ne] ncr53c8xx 49732 4 [7.4.] SCSI information (from /proc/scsi/scsi) Attached devices: Host: scsi0 Channel: 00 Id: 00 Lun: 00 Vendor: SEAGATE Model: ST32430N Rev: 0510 Type: Direct-AccessANSI SCSI revision: 02 Host: scsi0 Channel: 00 Id: 01 Lun: 00 Vendor: QUANTUM Model: FIREBALL_TM2110S Rev: 300N Type: Direct-AccessANSI SCSI revision: 02 Host: scsi0 Channel: 00 Id: 02 Lun: 00 Vendor: SEAGATE Model
Oops in 2.2.19pre7
Unable to handle kernel paging request at virtual address 813de1c0 current->tss.cr3 = 015fa000, %cr3 = 015fa000 *pde = Oops: 0002 CPU:0 EIP:0010:[] Using defaults from ksymoops -t elf32-i386 -a i386 EFLAGS: 00010283 eax: c09ef0e0 ebx: c7fff740 ecx: 000f edx: c09ef0e0 esi: 0800 edi: 0005 ebp: 0400 esp: c4153cbc ds: 0018 es: 0018 ss: 0018 Process dump (pid: 4001, process nr: 83, stackpage=c4153000) Stack: 0400 0400 c5752000 0801 c4153cdc c4153cdc c4152000 c4152000 c0125dc1 c5752000 0400 0400 0004 0801 c0124ff6 0400 c01251aa 0400 0034 Call Trace: [] [] [] [] [] [] [] [] [] Code: 00 04 00 00 ff ff 00 00 00 00 00 00 00 00 00 00 00 00 00 00 >>EIP; c09ef0e8 <_end+7d8f00/85fae18> <= Trace; c0125dc1 Trace; c0124ff6 Trace; c01251aa Trace; c0128265 Trace; c0147bfd Trace; c010f0b7 Trace; c0123559 Trace; c0123712 Trace; c01079cc Code; c09ef0e8 <_end+7d8f00/85fae18> <_EIP>: Code; c09ef0e8 <_end+7d8f00/85fae18> <= 0: 00 04 00 add%al,(%eax,%eax,1) <= Code; c09ef0eb <_end+7d8f03/85fae18> 3: 00 ff add%bh,%bh Code; c09ef0ed <_end+7d8f05/85fae18> 5: ff 00 incl (%eax) - 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: Status of ALi MAGiK 1 support in 2.4.?
On Mon, May 28, 2001 at 05:57:12PM +0200, Axel Thimm wrote: > What is the status of the support for this chipset, found for example in an > ASUS A7A266? Judging from > http://www.acerlabs.com/eng/support/faqlnx.htm > one gets the impression that ALi is respectfully treating the Linux community. I cannot answer your question about the level of support this chipset has, but suffice it to say that my new (as of last week) A7A266 based system (1.2Ghz T-Bird w/256MB Crucial DDR RAM) is running 2.4.5 (and previous to that 2.2.18) quite nicely. Perhaps Linux is not optimized for performance with this chipset, but it feels fast to me. According to 'hdparm -t /dev/hda', I am getting 25MB/s transfer rates with my Quantum Fireball Plus LM. Seems a little high, but drive performance 'feels' good. Based on my weekend experience with this board and Linux, I think I have made the right choice. - 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: Status of ALi MAGiK 1 support in 2.4.?
On Tue, May 29, 2001 at 05:18:39AM +0600, Bobby D. Bryant wrote: > sailing ever since. The only problems that I'm are ware of are a > (maybe) DMA problem and a (maybe) SMBus problem, per below. Right now I noticed the Win32 benchmark/test application Sandra mentioned an SMBus problem with the A7A266 as well. I have yet to try lm_sensors myself, but it looks like I won't get far. > May 22 21:45:07 pollux kernel: ALI15X3: IDE controller on PCI bus 00 dev > 20 > May 22 21:45:07 pollux kernel: PCI: No IRQ known for interrupt pin A of > device 00:04.0. Please try using pci=biosirq. I get the same message, but it does not appear to dramatically affect my performance. As I mentioned, I am getting 25MB/s (through hdparm; I have yet to try anything more) with my Quantum Fireball. My DMA is enabled in the BIOS and detected by the kernel. > The routing to IQR 0 sounds funny to me, but this is already way beyond > what I understand. Do you have the PnP operating system setting in the BIOS turned off? (ie. telling the BIOS you have non-PnP aware O/S) I noticed that prior to doing this, all of my PCI cards were listed as IRo 0. Mike. - 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/
IRQ problems w/VIA Apollo VP2/97 & NCR 53c875
Summary: IRQ conflict on VIA Apollo VP2/97-based motherboard between dual controllers on NCR 53c875 (Diamond Fireport 40). Kernel version is 2.4.5-ac9. --- cut here --- 00:00.0 Host bridge: VIA Technologies, Inc. VT82C595/97 [Apollo VP2/97] (rev 04) Flags: bus master, 66Mhz, medium devsel, latency 64 00:07.0 ISA bridge: VIA Technologies, Inc. VT82C586/A/B PCI-to-ISA [Apollo VP] (rev 25) Flags: bus master, medium devsel, latency 0 00:07.1 IDE interface: VIA Technologies, Inc. Bus Master IDE (rev 06) (prog-if 8a [Master SecP PriP]) Flags: bus master, medium devsel, latency 64 I/O ports at 6000 [size=16] --- cut here --- When I attempt to mobprobe the ncr53c8xx module, I get the following output: SCSI subsystem driver Revision: 1.00 PCI: Found IRQ 11 for device 00:0b.0 IRQ routing conflict in pirq table for device 00:0b.0 IRQ routing conflict in pirq table for device 00:0b.1 It appears that something is getting confused and doesn't want to allow the two controllers of this card to share the same IRQ. Here is the relevent output from 'lspci -v': --- cut here --- 00:0b.0 SCSI storage controller: Symbios Logic Inc. (formerly NCR) 53c875 (rev 14) Subsystem: Diamond Multimedia Systems FirePort 40 Dual SCSI Controller Flags: bus master, medium devsel, latency 144, IRQ 10 I/O ports at 6c00 [size=256] Memory at e2001000 (32-bit, non-prefetchable) [size=256] Memory at e2002000 (32-bit, non-prefetchable) [size=4K] Expansion ROM at [disabled] [size=64K] 00:0b.1 SCSI storage controller: Symbios Logic Inc. (formerly NCR) 53c875 (rev 14) Subsystem: Diamond Multimedia Systems FirePort 40 Dual SCSI Controller Flags: bus master, medium devsel, latency 144, IRQ 10 I/O ports at 7000 [size=256] Memory at e2003000 (32-bit, non-prefetchable) [size=256] Memory at e2004000 (32-bit, non-prefetchable) [size=4K] Expansion ROM at [disabled] [size=64K] --- cut here -- There are no other devices using IRQ10. Is this a lost cause? This controller and drives in their current configuration can be moved to an Intel based machine and works flawlessly. I have yet to see this controller work on this VIA motherboard. Any assistance is appreciated. Thanks, Mike. - 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/
