xl0: reset didn't complete
I am using -CURRENT cvsup'd August 29 and having some problems with a 3com 3c575B PC Card. I am running on a Dell Latitude C600 and -CURRENT has, for the most part, worked perfectly for me. The problem is that the 3Com card is no longer getting activated. The system sees when the card is plugged in and attempts to initialize it, but the initialization always fail with an "xl0 reset didn't complete". I did a quick couple of google searches and grep'd my email folders and didn't turn up anything helpful to me. I will also point out that, unlike Soeren's problems on August 13, wi0 is working just fine for me. Attached are the results of a boot -v, as well as the results from me setting hw.cardbus.debug and hw.pccard.debug to 1. For grins, I have also included my kernel configuration. Sorry for the long email. Any help would be greatly appreciated. Mik boot -v: Copyright (c) 1992-2003 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.1-CURRENT #0: Fri Aug 29 23:35:14 EDT 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/BULLET Preloaded elf kernel "/boot/kernel/kernel" at 0xc04af000. Preloaded elf module "/boot/kernel/snd_ess.ko" at 0xc04af1cc. Preloaded elf module "/boot/kernel/snd_pcm.ko" at 0xc04af278. Preloaded elf module "/boot/kernel/snd_sbc.ko" at 0xc04af324. Preloaded acpi_dsdt "/boot/acpi_dsdt.aml" at 0xc04af3d0. Preloaded elf module "/boot/kernel/acpi.ko" at 0xc04af418. Calibrating clock(s) ... i8254 clock: 1193123 Hz CLK_USE_I8254_CALIBRATION not specified - using default frequency Timecounter "i8254" frequency 1193182 Hz quality 0 Calibrating TSC clock ... TSC clock: 751706469 Hz CPU: Intel Pentium III (751.71-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x68a Stepping = 10 Features=0x383f9ff real memory = 268283904 (255 MB) Physical memory chunk(s): 0x1000 - 0x0009efff, 647168 bytes (158 pages) 0x004d6000 - 0x0fb34fff, 258338816 bytes (63071 pages) avail memory = 255438848 (243 MB) bios32: Found BIOS32 Service Directory header at 0xc00ffe80 bios32: Entry = 0xffe90 (c00ffe90) Rev = 0 Len = 1 pcibios: PCI BIOS entry at 0xf+0xc12e pnpbios: Found PnP BIOS data at 0xc00fe2d0 pnpbios: Entry = f:e2f4 Rev = 1.0 pnpbios: Event flag at 4b4 Other BIOS signatures found: wlan: <802.11 Link Layer> null: mem: Pentium Pro MTRR support enabled random: ACPI: DSDT was overridden. ACPI-0375: *** Info: Table [DSDT] replaced by host OS npx0: on motherboard npx0: INT 16 interface acpi0: on motherboard pci_open(1):mode 1 addr port (0x0cf8) is 0x8060 pci_open(1a): mode1res=0x8000 (0x8000) pci_cfgcheck: device 0 [class=06] [hdr=00] is there (id=71908086) pcibios: BIOS version 2.10 Using $PIR table, 9 entries at 0xc00fbd70 PCI-Only Interrupts: none Location Bus Device Pin Link IRQs embedded07D 0x63 3 4 5 6 7 9 10 11 12 14 15 embedded10A 0x60 3 4 5 6 7 9 10 11 12 14 15 embedded10B 0x61 3 4 5 6 7 9 10 11 12 14 15 embedded03A 0x63 3 4 5 6 7 9 10 11 12 14 15 embedded03B 0x63 3 4 5 6 7 9 10 11 12 14 15 embedded08A 0x61 3 4 5 6 7 9 10 11 12 14 15 embedded0 16A 0x63 3 4 5 6 7 9 10 11 12 14 15 embedded0 16B 0x62 3 4 5 6 7 9 10 11 12 14 15 embedded80A 0x63 3 4 5 6 7 9 10 11 12 14 15 embedded81A 0x63 3 4 5 6 7 9 10 11 12 14 15 embedded0 13A 0x62 11 embedded0 17A 0x62 11 embedded0 17B 0x62 11 embedded0 17C 0x62 11 embedded0 17D 0x62 11 acpi_bus_number: root bus has no _BBN, assuming 0 AcpiOsDerivePciId: bus 0 dev 7 func 0 ACPI timer looks BAD min = 2, max = 6, width = 4 ACPI timer looks BAD min = 2, max = 6, width = 4 ACPI timer looks BAD min = 2, max = 6, width = 4 ACPI timer looks BAD min = 2, max = 6, width = 4 ACPI timer looks BAD min = 2, max = 6, width = 4 ACPI timer looks BAD min = 2, max = 6, width = 4 ACPI timer looks BAD min = 2, max = 6, width = 4 ACPI timer looks BAD min = 2, max = 6, width = 4 ACPI timer looks BAD min = 2, max = 6, width = 4 ACPI timer looks BAD min = 2, max = 6, width = 4 Timecounter "ACPI-safe" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0 acpi_cpu0: on acpi0 acpi_tz0: on acpi0 acpi_acad0: on acpi0 acpi_cmbat0: on acpi0 acpi_cmbat1: on acpi0 acpi_lid0: on acpi0 acpi_button0: on acpi0 acpi_button1: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 initial configuration \\_SB_.PCI0.LNKA irq 11: [ 3 4 5 6 7 9 10 11 12 14 15] low,level,sharable 0.7.0 \\_SB_.PCI0.LNKB irq 5: [ 3 4 5 6 7 9 10 11 12 14 15] low,level,sharable 0.7.1 \\_SB_.PCI0.LNKC irq 0: [ 3 4 5 6 7 9 10 11 12 14 15] low,level,sharable 0.7.2 \\_SB_.PCI0.LNKD irq 11: [ 3 4 5 6 7 9 10 1
Re: FreeBSD 5.1-R kernel panic
On Tue, Jul 22, 2003 at 12:18:31AM +0100, Bruce Cran wrote: > On Mon, Jul 21, 2003 at 06:43:11PM +, Bosko Milekic wrote: > > > > > > On Mon, Jul 21, 2003 at 06:24:07PM -0400, Mik Firestone wrote: > > > For what it is worth, I am having the exact same problem. I cvsup'd and > > > builtworld on Sunday, July 20, and my machine has been crashing about every > > > half-hour since. It starts slowing down, the load average begins to > > > climb until it eventually grinds to a halt. If I wait long enough, I > > > will see the same panic Stephane saw. > > > > > > Doing a ps -auxw shows that usb0 is using the vast majority of the CPU > > > time before the grinding halt. I have tried leaving the machine in > > > multi-user and sigle-user mode with the same results. I have attempted > > > to compile a new kernel that does not have the USB stuff compiled in, > > > but my machine won't stay running long enough. > > > > > > I do have the debugger compiled in, but I do not know enough of what I > > > am doing to provide reasonable information to the list. If somebody > > > can tell me the commands to run in the debugger, I will let my machine > > > panic again and grab that data. > > > > > > Mik > > > > Does reverting to pre-July 20 get rid of your problem? Note that the > > originator of the first Email mentionned that he is running what > > appeared to be stock 5.1-RELEASE, which may or may not be related to > > what you're seeing. > > > > If reverting to pre-July 20 gets rid of your problem, perhaps we can > > figure out what commit triggered this behavior for you. Also, do you > > have PAE enabled? > > > > It sounds like the same or similar problem reported in the 'USB crappiness' > thread - the system slows down, and then any command crashes the system with > the error about kmem. I posted a backtrace to the problem in usb_mem.c, and > the developer has posted a temporary fix - it was a problem with bus_dma, > it was allocating too much memory and running out of kernel memory. > > If the kernel debugger is compiled in, the system should drop to the db> > prompt when it panics. Type 'tr' and post the results it gives. This > panic appears to stop memory dumps working, otherwise you could set the > dumpdev variable in rc.conf also get > the source listing of where the problem occurs: the FreeBSD Developers Handbook > has more information. > > -- > Bruce Cran > ___ > [EMAIL PROTECTED] mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "[EMAIL PROTECTED]" Thanks! I found the thread in the archives and applied the patch. My machine is now up and seems to be much happier. Mik ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: FreeBSD 5.1-R kernel panic
For what it is worth, I am having the exact same problem. I cvsup'd and builtworld on Sunday, July 20, and my machine has been crashing about every half-hour since. It starts slowing down, the load average begins to climb until it eventually grinds to a halt. If I wait long enough, I will see the same panic Stephane saw. Doing a ps -auxw shows that usb0 is using the vast majority of the CPU time before the grinding halt. I have tried leaving the machine in multi-user and sigle-user mode with the same results. I have attempted to compile a new kernel that does not have the USB stuff compiled in, but my machine won't stay running long enough. I do have the debugger compiled in, but I do not know enough of what I am doing to provide reasonable information to the list. If somebody can tell me the commands to run in the debugger, I will let my machine panic again and grab that data. Mik On Mon, Jul 21, 2003 at 03:01:24PM -0600, Stephane Raimbault wrote: > I'm running FreeBSD 5.1-RELEASE with the SMP kernel and ran across the > following kernel panic. > > panic: kmem_malloc(4096): kmem_map too small: 275251200 total allocated > > I'm trying to figure out what could be causing this, what kind of > information that I could provide to this group (or other group?) to see if > this is a bug in FreeBSD that needs to be looked into? > > The box is basically a busy apache server... the kernel panic seemed to > occur during the periodic daily was running. It seems to complete the > 440.status-mailq part of periodic daily , but doesn't do > 450.status-security. > > This isn't the first time the box has crashed at aprox. 3:01 am (when daily > runs)... however this is the first time I've seend the kernel panic message > quoted above in the /var/run/dmesg.boot file. > > I have attached the entire /var/run/dmesg.boot file to this message. > > What can I do to assist in identifiying and resolving this problem? > > Thanks, > Stephane Raimbault. > %cat /var/run/dmesg.boot > 76.232.138 in via em0 > panic: kmem_malloc(4096): kmem_map too small: 275251200 total allocated > cpuid = 0; lapic.id = > boot() called on cpu#0 > > syncing disks, buffers remaining... 7154 7154 7153 7153 7153 7153 7154 7152 7152 > 7152 7152 7152 7152 7152 7152 7152 7152 7152 7152 7152 7152 7152 7152 7152 7152 7152 > 7152 > Copyright (c) 1992-2003 The FreeBSD Project. > Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 > The Regents of the University of California. All rights reserved. > FreeBSD 5.1-RELEASE #0: Fri Jun 20 18:36:54 MDT 2003 > [EMAIL PROTECTED]:/usr/obj/usr/src/sys/SRV2 > Preloaded elf kernel "/boot/kernel/kernel" at 0xc06ef000. > Preloaded elf module "/boot/kernel/ipfw.ko" at 0xc06ef2e4. > Preloaded elf module "/boot/kernel/acpi.ko" at 0xc06ef390. > Timecounter "i8254" frequency 1193182 Hz > Timecounter "TSC" frequency 2399328676 Hz > CPU: Intel(R) Xeon(TM) CPU 2.40GHz (2399.33-MHz 686-class CPU) > Origin = "GenuineIntel" Id = 0xf27 Stepping = 7 > > Features=0xbfebfbff > Hyperthreading: 2 logical CPUs > real memory = 4160225280 (3967 MB) > avail memory = 4045828096 (3858 MB) > Programming 24 pins in IOAPIC #0 > IOAPIC #0 intpin 2 -> irq 0 > Programming 24 pins in IOAPIC #1 > Programming 24 pins in IOAPIC #2 > FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs > cpu0 (BSP): apic id: 0, version: 0x00050014, at 0xfee0 > cpu1 (AP): apic id: 6, version: 0x00050014, at 0xfee0 > cpu2 (AP): apic id: 1, version: 0x00050014, at 0xfee0 > cpu3 (AP): apic id: 7, version: 0x00050014, at 0xfee0 > io0 (APIC): apic id: 2, version: 0x00178020, at 0xfec0 > io1 (APIC): apic id: 3, version: 0x00178020, at 0xfec8 > io2 (APIC): apic id: 4, version: 0x00178020, at 0xfec80400 > Pentium Pro MTRR support enabled > npx0: on motherboard > npx0: INT 16 interface > acpi0: on motherboard > pcibios: BIOS version 2.10 > Using $PIR table, 24 entries at 0xc00fde40 > acpi0: power button is handled as a fixed feature programming model. > Timecounter "ACPI-fast" frequency 3579545 Hz > acpi_timer0: <24-bit timer at 3.579545MHz> port 0x1008-0x100b on acpi0 > acpi_cpu0: on acpi0 > acpi_cpu1: on acpi0 > pcib0: port 0xcf8-0xcff on acpi0 > pci0: on pcib0 > IOAPIC #0 intpin 16 -> irq 2 > IOAPIC #0 intpin 19 -> irq 10 > IOAPIC #0 intpin 18 -> irq 11 > pcib1: at device 2.0 on pci0 > pcib1: could not get PCI interrupt routing table for \\_SB_.PCI0.HLB_ - AE_NOT_FOUND > pci1: on pcib1 > pci1: at device 28.0 (no driver attached) > pcib2: at device 29.0 on pci1 > pci2: on pcib2 > IOAPIC #2 intpin 6 -> irq 16 > IOAPIC #2 intpin 7 -> irq 17 > em0: port 0x3000-0x303f mem > 0xf820-0xf821 irq 16 at device 3.0 on pci2 > em0: Speed:100 Mbps Duplex:Half > em1: port 0x3040-0x307f mem > 0xf822-0xf823 irq 17 at device 3.1 on pci2 > em1: Speed:1000 Mbps Duplex:Full > pci1: at device 30.0 (no driver attached) > pcib3: at device 31.0 on pci1 > pci3: o
