Re: Oops on booting 2.4.4
Pete Zaitcev wrote: > > May 23 02:46:24 localhost kernel: Process kudzu (pid: 219, > > stackpage=c7845000) > > May 23 02:46:24 localhost kernel: Stack: c12607e0 0400 0400 > > c73aa000 c122a060 c122a05c c122a058 c88fbb20 > > May 23 02:46:24 localhost kernel:03f1 03f1 c014ab80 > > c73aa3f1 c7845f9c 0400 ffea > > May 23 02:46:24 localhost kernel:c7f43f60 0400 b4b8 > > c7f2e220 c12607e0 c73aa000 > > May 23 02:46:24 localhost kernel: Call Trace: [] > > [proc_file_read+184/464] [sys_read+142/196] [system_call+51/56] > > May 23 02:46:24 localhost kernel: Call Trace: [] [] > > [] [] > > A module deregistered incorrectly, or has a race between > post-load activities and unload. One way or another it left > a dangling proc entry. > > The oops does not provide off-stack information, so it's impossible > to tell what particular modules is the culprit. > > > May 23 02:46:24 localhost kernel: hub.c: USB new device connect on > > bus1/2, assigned device number 2 > > May 23 02:46:24 localhost kernel: usb.c: USB device 2 (vend/prod > > 0x4a9/0x2204) is not claimed by any active driver. > > What is this thing you have on USB? Try to run without it. > > -- Pete It's a canon usb scanner. running with or without it does not make any difference. kind regards, Harm - 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 booting 2.4.4
Pete Zaitcev wrote: May 23 02:46:24 localhost kernel: Process kudzu (pid: 219, stackpage=c7845000) May 23 02:46:24 localhost kernel: Stack: c12607e0 0400 0400 c73aa000 c122a060 c122a05c c122a058 c88fbb20 May 23 02:46:24 localhost kernel:03f1 03f1 c014ab80 c73aa3f1 c7845f9c 0400 ffea May 23 02:46:24 localhost kernel:c7f43f60 0400 b4b8 c7f2e220 c12607e0 c73aa000 May 23 02:46:24 localhost kernel: Call Trace: [c88fbb20] [proc_file_read+184/464] [sys_read+142/196] [system_call+51/56] May 23 02:46:24 localhost kernel: Call Trace: [c88fbb20] [c014ab80] [c012e83e] [c0106aeb] A module deregistered incorrectly, or has a race between post-load activities and unload. One way or another it left a dangling proc entry. The oops does not provide off-stack information, so it's impossible to tell what particular modules is the culprit. May 23 02:46:24 localhost kernel: hub.c: USB new device connect on bus1/2, assigned device number 2 May 23 02:46:24 localhost kernel: usb.c: USB device 2 (vend/prod 0x4a9/0x2204) is not claimed by any active driver. What is this thing you have on USB? Try to run without it. -- Pete It's a canon usb scanner. running with or without it does not make any difference. kind regards, Harm - 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 booting 2.4.4
Hi folks,(cc me, as i'm not on the list) [1.] One line summary of the problem: Kernel 2.4.4 oopses during boot [2.] Full description of the problem/report: Kernel 2.4.4 oopses during boot on RH 7.1 system, seems when it's running kudzu or something (maybe I saw it wrong) After first oops, some more appears and system hangs. on RH 6.2 2.4.4 with same .config worked fine. I tried both: CC = $(CROSS_COMPILE)kgcc and CC = $(CROSS_COMPILE)gcc [3.] Keywords (i.e., modules, networking, kernel): kernel, oops, boot [4.] Kernel version: Linux version 2.4.4 [5.] Output of Oops.. message (if applicable) with symbolic information resolved (see Documentation/oops-tracing.txt) ksymoops 2.4.0 on i686 2.4.2-2. Options used -V (default) -K (specified) -l /proc/modules (default) -o /lib/modules/2.4.4 (specified) -m /boot/System.map-2.4.4 (specified) No modules in ksyms, skipping objects No ksyms, skipping lsmod May 23 02:46:24 localhost kernel: Unable to handle kernel paging request at virtual address c88fbb28 May 23 02:46:24 localhost kernel: c02071ad May 23 02:46:24 localhost kernel: *pde = 01240067 May 23 02:46:24 localhost kernel: Oops: May 23 02:46:24 localhost kernel: CPU:0 May 23 02:46:24 localhost kernel: EIP: 0010:[get_pci_dev_info+269/432] May 23 02:46:24 localhost kernel: EIP:0010:[] Using defaults from ksymoops -t elf32-i386 -a i386 May 23 02:46:24 localhost kernel: EFLAGS: 00010282 May 23 02:46:24 localhost kernel: eax: 0009 ebx: 008e ecx: c88fbb20 edx: c02b27e1 May 23 02:46:24 localhost kernel: esi: 00c4 edi: 0007 ebp: c122a000 esp: c7845f40 May 23 02:46:24 localhost kernel: ds: 0018 es: 0018 ss: 0018 May 23 02:46:24 localhost kernel: Process kudzu (pid: 219, stackpage=c7845000) May 23 02:46:24 localhost kernel: Stack: c12607e0 0400 0400 c73aa000 c122a060 c122a05c c122a058 c88fbb20 May 23 02:46:24 localhost kernel:03f1 03f1 c014ab80 c73aa3f1 c7845f9c 0400 ffea May 23 02:46:24 localhost kernel:c7f43f60 0400 b4b8 c7f2e220 c12607e0 c73aa000 May 23 02:46:24 localhost kernel: Call Trace: [] [proc_file_read+184/464] [sys_read+142/196] [system_call+51/56] May 23 02:46:24 localhost kernel: Call Trace: [] [] [] [] May 23 02:46:24 localhost kernel: Code: 8b 41 08 50 68 e3 27 2b c0 8b 44 24 34 01 d8 50 e8 02 d3 05 >>EIP; c02071ad<= Trace; c88fbb20 Trace; c88fbb20 Trace; c014ab80 Trace; c012e83e Trace; c0106aeb Code; c02071ad <_EIP>: Code; c02071ad<= 0: 8b 41 08 mov0x8(%ecx),%eax <= Code; c02071b0 3: 50push %eax Code; c02071b1 4: 68 e3 27 2b c0push $0xc02b27e3 Code; c02071b6 9: 8b 44 24 34 mov0x34(%esp,1),%eax Code; c02071ba d: 01 d8 add%ebx,%eax Code; c02071bc f: 50push %eax Code; c02071bd 10: e8 02 d3 05 00call 5d317 <_EIP+0x5d317> c02644c4 [6.] A small shell script or example program which triggers the problem (if possible) [7.] Environment [7.1.] Software (add the output of the ver_linux script here) Linux c122070.upc-c.chello.nl 2.4.2-2 #1 Sun Apr 8 20:41:30 EDT 2001 i686 unknow n Gnu C 2.96(kgcc egcs-2.91.66) Gnu make 3.79.1 binutils 2.10.91.0.2 util-linux 2.10s mount 2.11b modutils 2.4.5 e2fsprogs 1.19 reiserfsprogs 3.x.0f PPP2.4.0 Linux C Library2.2.2 Dynamic linker (ldd) 2.2.2 Procps 2.0.7 Net-tools 1.57 Console-tools 0.3.3 Sh-utils 2.0 Modules Loaded ppa parport_pc parport autofs 3c59x nls_iso8859-1 nls_cp4 37 vfat fat reiserfs usb-uhci usbcore aic7xxx sd_mod scsi_mod [7.2.] Processor information (from /proc/cpuinfo): processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 7 model name : Pentium III (Katmai) stepping : 3 cpu MHz : 451.031 cache size : 512 KB fdiv_bug : no hlt_bug : no f00f_bug : no coma_bug : no fpu : yes fpu_exception : yes cpuid level : 2 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 sep mtrr pge mca cmov pat pse36 mmx fxsr sse bogomips : 897.84 [8] Bootmessages May 23 02:46:23 localhost syslogd 1.4-0: restart. May 23 02:46:23 localhost syslog: syslogd startup succeeded May 23 02:46:23 localhost kernel: klogd 1.4-0, log source = /proc/kmsg started. May 23 02:46:23 localhost kernel: Inspecting /boot/System.map-2.4.4 May 23 02:46:23 localhost syslog: klogd startup succeeded May 23 02:46:23 localhost modprobe: modprobe: Can't locate module autofs May 23 02:46:23 localhost identd: identd startup succeeded May 23 02:46:23 localhost kernel: Loaded 16874 symbols from /boot/System.map-2.4.4. May 23 02:46:23 localhost kernel: Symbols match
Oops on booting 2.4.4
Hi folks,(cc me, as i'm not on the list) [1.] One line summary of the problem: Kernel 2.4.4 oopses during boot [2.] Full description of the problem/report: Kernel 2.4.4 oopses during boot on RH 7.1 system, seems when it's running kudzu or something (maybe I saw it wrong) After first oops, some more appears and system hangs. on RH 6.2 2.4.4 with same .config worked fine. I tried both: CC = $(CROSS_COMPILE)kgcc and CC = $(CROSS_COMPILE)gcc [3.] Keywords (i.e., modules, networking, kernel): kernel, oops, boot [4.] Kernel version: Linux version 2.4.4 [5.] Output of Oops.. message (if applicable) with symbolic information resolved (see Documentation/oops-tracing.txt) ksymoops 2.4.0 on i686 2.4.2-2. Options used -V (default) -K (specified) -l /proc/modules (default) -o /lib/modules/2.4.4 (specified) -m /boot/System.map-2.4.4 (specified) No modules in ksyms, skipping objects No ksyms, skipping lsmod May 23 02:46:24 localhost kernel: Unable to handle kernel paging request at virtual address c88fbb28 May 23 02:46:24 localhost kernel: c02071ad May 23 02:46:24 localhost kernel: *pde = 01240067 May 23 02:46:24 localhost kernel: Oops: May 23 02:46:24 localhost kernel: CPU:0 May 23 02:46:24 localhost kernel: EIP: 0010:[get_pci_dev_info+269/432] May 23 02:46:24 localhost kernel: EIP:0010:[c02071ad] Using defaults from ksymoops -t elf32-i386 -a i386 May 23 02:46:24 localhost kernel: EFLAGS: 00010282 May 23 02:46:24 localhost kernel: eax: 0009 ebx: 008e ecx: c88fbb20 edx: c02b27e1 May 23 02:46:24 localhost kernel: esi: 00c4 edi: 0007 ebp: c122a000 esp: c7845f40 May 23 02:46:24 localhost kernel: ds: 0018 es: 0018 ss: 0018 May 23 02:46:24 localhost kernel: Process kudzu (pid: 219, stackpage=c7845000) May 23 02:46:24 localhost kernel: Stack: c12607e0 0400 0400 c73aa000 c122a060 c122a05c c122a058 c88fbb20 May 23 02:46:24 localhost kernel:03f1 03f1 c014ab80 c73aa3f1 c7845f9c 0400 ffea May 23 02:46:24 localhost kernel:c7f43f60 0400 b4b8 c7f2e220 c12607e0 c73aa000 May 23 02:46:24 localhost kernel: Call Trace: [c88fbb20] [proc_file_read+184/464] [sys_read+142/196] [system_call+51/56] May 23 02:46:24 localhost kernel: Call Trace: [c88fbb20] [c014ab80] [c012e83e] [c0106aeb] May 23 02:46:24 localhost kernel: Code: 8b 41 08 50 68 e3 27 2b c0 8b 44 24 34 01 d8 50 e8 02 d3 05 EIP; c02071ad get_pci_dev_info+10d/1b0 = Trace; c88fbb20 END_OF_CODE+8598cc8/ Trace; c88fbb20 END_OF_CODE+8598cc8/ Trace; c014ab80 proc_file_read+b8/1d0 Trace; c012e83e sys_read+8e/c4 Trace; c0106aeb system_call+33/38 Code; c02071ad get_pci_dev_info+10d/1b0 _EIP: Code; c02071ad get_pci_dev_info+10d/1b0 = 0: 8b 41 08 mov0x8(%ecx),%eax = Code; c02071b0 get_pci_dev_info+110/1b0 3: 50push %eax Code; c02071b1 get_pci_dev_info+111/1b0 4: 68 e3 27 2b c0push $0xc02b27e3 Code; c02071b6 get_pci_dev_info+116/1b0 9: 8b 44 24 34 mov0x34(%esp,1),%eax Code; c02071ba get_pci_dev_info+11a/1b0 d: 01 d8 add%ebx,%eax Code; c02071bc get_pci_dev_info+11c/1b0 f: 50push %eax Code; c02071bd get_pci_dev_info+11d/1b0 10: e8 02 d3 05 00call 5d317 _EIP+0x5d317 c02644c4 sprintf+0/1c [6.] A small shell script or example program which triggers the problem (if possible) [7.] Environment [7.1.] Software (add the output of the ver_linux script here) Linux c122070.upc-c.chello.nl 2.4.2-2 #1 Sun Apr 8 20:41:30 EDT 2001 i686 unknow n Gnu C 2.96(kgcc egcs-2.91.66) Gnu make 3.79.1 binutils 2.10.91.0.2 util-linux 2.10s mount 2.11b modutils 2.4.5 e2fsprogs 1.19 reiserfsprogs 3.x.0f PPP2.4.0 Linux C Library2.2.2 Dynamic linker (ldd) 2.2.2 Procps 2.0.7 Net-tools 1.57 Console-tools 0.3.3 Sh-utils 2.0 Modules Loaded ppa parport_pc parport autofs 3c59x nls_iso8859-1 nls_cp4 37 vfat fat reiserfs usb-uhci usbcore aic7xxx sd_mod scsi_mod [7.2.] Processor information (from /proc/cpuinfo): processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 7 model name : Pentium III (Katmai) stepping : 3 cpu MHz : 451.031 cache size : 512 KB fdiv_bug : no hlt_bug : no f00f_bug : no coma_bug : no fpu : yes fpu_exception : yes cpuid level : 2 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 sep mtrr pge mca cmov pat pse36 mmx fxsr sse bogomips : 897.84 [8] Bootmessages May 23 02:46:23 localhost syslogd 1.4-0: restart. May 23 02:46:23 localhost syslog: syslogd startup succeeded May 23 02:46:23 localhost kernel: klogd 1.4-0, log source = /proc/kmsg started. May 23 02:46:23 localhost
Re: 2.2 / 2.4 ethernet detection order
I had the same problem on a RedHat 6.2 distro. on 2.4 Ifup for dhcp card fails if done after ifup for static ip. The problem comes from the pump package. Using dhcpcd instead of pump fixed the problem completely. kind regards, Harm >I got the same problem. >The consequence was that if my eth0 card (static ip) was "ifupped" before my >eth1 card (dhcp), it became impossible to ifup my eth1 card (I could no more .obtain an ip from the dhcp server). - Message d'origine - De : James Lewis Nance <[EMAIL PROTECTED]> À : <[EMAIL PROTECTED]> Envoyé : mardi 5 septembre 2000 15:55 Objet : 2.2 / 2.4 ethernet detection order > Hello All, > I have a box with 2 ethernet cards. One is a ne2k-pci and one is a > tulip. Under 2.2.X the ne card is eth0 and the tulip is eth1. Unfortunatly > if I boot a 2.4.X kernel, the tulip card is assigned eth0 and the ne card > eth1, which of course breaks all my networking setup scripts. I can get > the 2.4.X kernels to assign 2.2.X identities by using command line args > like (from memory): > > ethers=eth1 > > but unfortunatly at least one of the cards does not work if I try this. > I "solved" the problem by using kernel modules and an /etc/modules.conf > file that looks like this: > > alias eth0 ne2k-pci > alias eth1 tulip > > but I would really rather not use a modular kernel. I have no idea what I > would do if I had two identical network cards in the computer. Is there > a better way to solve this problem? > > Thanks, > > Jim > - > 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/ - 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/ - 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: 2.2 / 2.4 ethernet detection order
I had the same problem on a RedHat 6.2 distro. on 2.4 Ifup for dhcp card fails if done after ifup for static ip. The problem comes from the pump package. Using dhcpcd instead of pump fixed the problem completely. kind regards, Harm I got the same problem. The consequence was that if my eth0 card (static ip) was "ifupped" before my eth1 card (dhcp), it became impossible to ifup my eth1 card (I could no more .obtain an ip from the dhcp server). - Message d'origine - De : James Lewis Nance [EMAIL PROTECTED] À : [EMAIL PROTECTED] Envoyé : mardi 5 septembre 2000 15:55 Objet : 2.2 / 2.4 ethernet detection order Hello All, I have a box with 2 ethernet cards. One is a ne2k-pci and one is a tulip. Under 2.2.X the ne card is eth0 and the tulip is eth1. Unfortunatly if I boot a 2.4.X kernel, the tulip card is assigned eth0 and the ne card eth1, which of course breaks all my networking setup scripts. I can get the 2.4.X kernels to assign 2.2.X identities by using command line args like (from memory): ethers=eth1 but unfortunatly at least one of the cards does not work if I try this. I "solved" the problem by using kernel modules and an /etc/modules.conf file that looks like this: alias eth0 ne2k-pci alias eth1 tulip but I would really rather not use a modular kernel. I have no idea what I would do if I had two identical network cards in the computer. Is there a better way to solve this problem? Thanks, Jim - 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/ - 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/ - 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/
