7.0-RELEASE panics in ip_output
Since upgrading to 7.0-RELEASE, I seem to get a panic about once a
week or so.
I have 6to4 set up on this machine, and the stack trace I get from
kgdb usually looks something like this:
#0 doadump () at pcpu.h:195
#1 0xc062e2a7 in boot (howto=260) at /usr/src/sys/kern/
kern_shutdown.c:409
#2 0xc062e569 in panic (fmt=Variable "fmt" is not available.
) at /usr/src/sys/kern/kern_shutdown.c:563
#3 0xc084ce2c in trap_fatal (frame=0xe679875c, eva=76)
at /usr/src/sys/i386/i386/trap.c:899
#4 0xc084d0b0 in trap_pfault (frame=0xe679875c, usermode=0, eva=76)
at /usr/src/sys/i386/i386/trap.c:812
#5 0xc084da5c in trap (frame=0xe679875c) at /usr/src/sys/i386/i386/
trap.c:490
#6 0xc0833d3b in calltrap () at /usr/src/sys/i386/i386/exception.s:139
#7 0xc06f23b9 in ip_output (m=0xc4494e00, opt=0x0, ro=0xc3eabbc4,
flags=0,
imo=0x0, inp=0x0) at /usr/src/sys/netinet/ip_output.c:169
#8 0xc06ca751 in stf_output (ifp=0xc3ee1000, m=0xc4494e00,
dst=0xc3ee5bdc,
rt=0xc3fb5780) at /usr/src/sys/net/if_stf.c:533
#9 0xc02d in nd6_output (ifp=0xc3ee1000, origifp=0xc3ee1000,
m0=0xc4494e00, dst=0xc3ee5bdc, rt0=0xc3fb5780)
at /usr/src/sys/netinet6/nd6.c:2123
#10 0xc07749f2 in ip6_output (m0=0xc4494e00, opt=0xc4089c80,
ro=0xe6798a0c,
flags=0, im6o=0x0, ifpp=0x0, inp=0xc3fb2924)
at /usr/src/sys/netinet6/ip6_output.c:927
#11 0xc0785a27 in udp6_send (so=0xc424d630, flags=0, m=0xc4494e00,
addr=0xc3e4d880, control=0x0, td=0xc4246210)
at /usr/src/sys/netinet6/udp6_usrreq.c:675
#12 0xc0681785 in sosend_generic (so=0xc424d630, addr=0xc3e4d880,
uio=0xe6798bd4, top=0xc4494e00, control=0x0, flags=0,
td=0xc4246210)
at /usr/src/sys/kern/uipc_socket.c:1240
#13 0xc067d74f in sosend (so=0xc424d630, addr=0xc3e4d880,
uio=0xe6798bd4,
top=0x0, control=0x0, flags=0, td=0xc4246210)
at /usr/src/sys/kern/uipc_socket.c:1286
#14 0xc0683ed6 in kern_sendit (td=0xc4246210, s=27, mp=0xe6798c58,
flags=0,
control=0x0, segflg=UIO_USERSPACE) at /usr/src/sys/kern/
uipc_syscalls.c:789
#15 0xc0686f91 in sendit (td=0xc4246210, s=27, mp=0xe6798c58, flags=0)
at /usr/src/sys/kern/uipc_syscalls.c:730
#16 0xc0687031 in sendmsg (td=0xc4246210, uap=0xe6798cfc)
at /usr/src/sys/kern/uipc_syscalls.c:922
#17 0xc084d405 in syscall (frame=0xe6798d38)
at /usr/src/sys/i386/i386/trap.c:1035
#18 0xc0833da0 in Xint0x80_syscall () at /usr/src/sys/i386/i386/
exception.s:196
#19 0x0033 in ?? ()
Previous frame inner to this frame (corrupt stack?)
The exact details can vary, but the line where things seem to blow up
is always in this code in ip_output.c:
/*
* If there is a cached route,
* check that it is to the same destination
* and is still up. If not, free it and try again.
* The address family should also be checked in case of
sharing the
* cache with IPv6.
*/
if (ro->ro_rt && ((ro->ro_rt->rt_flags & RTF_UP) == 0 ||
dst->sin_family != AF_INET ||
dst->sin_addr.s_addr != ip->ip_dst.s_addr)) {
RTFREE(ro->ro_rt);
ro->ro_rt = (struct rtentry *)NULL;
}
on the RTFREE line.
Is it just me, or is this something other folks have seen as well?
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: GPT support?
Never mind. I figured it out. option GEOM_GPT got renamed to GEOM_PART_GPT in 7.0. With a new, corrected kernel, it's working. :) On Jan 12, 2008, at 6:13 PM, Nick Sayer wrote: I've got a 7.0-RC1 system and am setting up a 1TB USB drive on it. I'd like to set the drive up with a GUID partition table. I've used the GPT utility to create the GPT label and the partition, but though GPT says that there's now a da0p1 partition, I don't see a / dev node for it. I'd assume that I'd need to load a GEOM module for GPT but I don't see one. It hardly seems possible that GPT support isn't there... What do I have to do? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
GPT support?
I've got a 7.0-RC1 system and am setting up a 1TB USB drive on it. I'd like to set the drive up with a GUID partition table. I've used the GPT utility to create the GPT label and the partition, but though GPT says that there's now a da0p1 partition, I don't see a /dev node for it. I'd assume that I'd need to load a GEOM module for GPT but I don't see one. It hardly seems possible that GPT support isn't there... What do I have to do? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
More on ICH8
I've gotten a little bit further in trying to get the ICH8 (P965) chipset on my new machine recognized. This page is quite helpful: http://pci-ids.ucw.cz/iii/?i=8086 Using it, I added some code to ata-chipset.c to recognize the ICH8 SATA controllers and ehci_pci.c and uhci_pci.c to recognize the USB controllers. The USB stuff appears to work flawlessly. The ATA stuff has one minor glitch: atapci2: port 0xd400-0xd407,0xd080-0xd083,0xd000-0xd007,0xcc00-0xcc03,0xc880-0xc88f, 0xc800-0xc80f irq 19 at device 31.5 on pci0 atapci2: failed to enable memory mapping! ata7: on atapci2 ata8: on atapci2 I'm not sure what's up with the failure to memory-map, but since I only have one drive connected (and it's not connected to this particular instance), it's harmless at the moment. I've moved my SATA drive from the JMicro RAID controller to one of the ICH8 ports, and it appears to work. I tried to add the HD audio chip to /sys/sound/pci/ich.c, but unfortunately, all I get is an error that it cannot map its I/O space: pcm0: mem 0xfebf8000-0xfebfbfff irq 22 at device 27.0 on pci0 pcm0: unable to map IO port space device_attach: pcm0 attach returned 6 The P5B motherboard has a Realtek Ethernet controller. Realtek has a FreeBSD driver for it: http://www.realtek.com.tw/downloads/ downloads1-3.aspx?Keyword=rtl8168 Perhaps their changes could be either rolled into -CURRENT or merged back to RELENG_6? Getting the SMB controller recognized would be next, so I could get mbmon to work. I can't quite figure out which driver (if any) is close enough a match to try adding the PCI ID. Last, but not least, since I have ATA_STATIC_ID turned on, I need to let the kernel know where the disk is every time I move it. The problem is that my AT keyboard doesn't work at the mountroot prompt for some odd reason. A USB keyboard plugged in early enough to be probed does work, however. But for some unknown reason, having a USB keyboard plugged in causes the system to boot in slow motion (this appears to be a BIOS bug - and yes, I did disable legacy USB support. No help). Anybody know what's up with that? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
ICH8 chipset support?
I just upgraded my machine at home to a Conroy-ready motherboard - An Asus P5B. This particular motherboard has the smallest fraction of recognized devices I think I've ever come across. From what I can tell, the blame can be placed squarely on the Intel ICH8 chipset that supplies almost all of the devices in the system. USB is working, though it is recognized only generically. The ICH8 SATA ports do not seem to work properly (thank goodness for the JMicro RAID controller - which can be used without RAID). The audio subsystem, SMB controller and the Realtek on-board Ethernet aren't recognized at all. There's an nVidia PCI Express graphics card in there too, but I probably won't even run X on this machine, much less 3D stuff. I'll attach the output from pciconf -l and the dmesg.boot. At this point, it is up, sort of. Is there any hope of improving support for this system? [EMAIL PROTECTED]:0:0:class=0x06 card=0x81ea1043 chip=0x29a08086 rev=0x02 hdr=0x00 [EMAIL PROTECTED]:1:0: class=0x060400 card=0x0088 chip=0x29a18086 rev=0x02 hdr=0x01 [EMAIL PROTECTED]:26:0:class=0x0c0300 card=0x81ec1043 chip=0x28348086 rev=0x02 hdr=0x00 [EMAIL PROTECTED]:26:1:class=0x0c0300 card=0x81ec1043 chip=0x28358086 rev=0x02 hdr=0x00 [EMAIL PROTECTED]:26:7:class=0x0c0320 card=0x81ec1043 chip=0x283a8086 rev=0x02 hdr=0x00 [EMAIL PROTECTED]:27:0:class=0x040300 card=0x81ec1043 chip=0x284b8086 rev=0x02 hdr=0x00 [EMAIL PROTECTED]:28:0:class=0x060400 card=0x0040 chip=0x283f8086 rev=0x02 hdr=0x01 [EMAIL PROTECTED]:28:3:class=0x060400 card=0x0040 chip=0x28458086 rev=0x02 hdr=0x01 [EMAIL PROTECTED]:28:4:class=0x060400 card=0x0040 chip=0x28478086 rev=0x02 hdr=0x01 [EMAIL PROTECTED]:29:0:class=0x0c0300 card=0x81ec1043 chip=0x28308086 rev=0x02 hdr=0x00 [EMAIL PROTECTED]:29:1:class=0x0c0300 card=0x81ec1043 chip=0x28318086 rev=0x02 hdr=0x00 [EMAIL PROTECTED]:29:2:class=0x0c0300 card=0x81ec1043 chip=0x28328086 rev=0x02 hdr=0x00 [EMAIL PROTECTED]:29:7:class=0x0c0320 card=0x81ec1043 chip=0x28368086 rev=0x02 hdr=0x00 [EMAIL PROTECTED]:30:0:class=0x060401 card=0x0050 chip=0x244e8086 rev=0xf2 hdr=0x01 [EMAIL PROTECTED]:31:0:class=0x060100 card=0x81ec1043 chip=0x28108086 rev=0x02 hdr=0x00 [EMAIL PROTECTED]:31:2: class=0x01018f card=0x81ec1043 chip=0x28208086 rev=0x02 hdr=0x00 [EMAIL PROTECTED]:31:3:class=0x0c0500 card=0x81ec1043 chip=0x283e8086 rev=0x02 hdr=0x00 [EMAIL PROTECTED]:31:5: class=0x010185 card=0x81ec1043 chip=0x28258086 rev=0x02 hdr=0x00 [EMAIL PROTECTED]:0:0: class=0x03 card=0xc2233842 chip=0x016110de rev=0xa1 hdr=0x00 [EMAIL PROTECTED]:0:0: class=0x02 card=0x81681043 chip=0x816810ec rev=0x01 hdr=0x00 [EMAIL PROTECTED]:0:0: class=0x010185 card=0x81e41043 chip=0x2363197b rev=0x02 hdr=0x00 [EMAIL PROTECTED]:0:0: class=0x02 card=0x10128086 chip=0x10108086 rev=0x01 hdr=0x00 [EMAIL PROTECTED]:0:1: class=0x02 card=0x10128086 chip=0x10108086 rev=0x01 hdr=0x00 [EMAIL PROTECTED]:2:0: class=0x01 card=0xe2a09005 chip=0x00809005 rev=0x02 hdr=0x00Copyright (c) 1992-2006 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 6.1-RELEASE-p3 #5: Wed Jul 19 18:54:04 PDT 2006 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/QUACK ACPI APIC Table: Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel(R) Pentium(R) 4 CPU 2.66GHz (2660.49-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0xf49 Stepping = 9 Features=0xbfebfbff Features2=0x651d> AMD Features=0x2010 AMD Features2=0x1 real memory = 1073348608 (1023 MB) avail memory = 1041428480 (993 MB) ioapic0 irqs 0-23 on motherboard kbd1 at kbdmux0 acpi0: on motherboard acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR acpi0: Power Button (fixed) Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0 cpu0: on acpi0 ACPI-1304: *** Error: Method execution failed [\\_PR_.CPU1._PDC] (Node 0xc4a6e780), AE_BAD_HEADER pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pcib1: irq 16 at device 1.0 on pci0 pci1: on pcib1 pci1: at device 0.0 (no driver attached) uhci0: port 0xdc00-0xdc1f irq 16 at device 26.0 on pci0 uhci0: [GIANT-LOCKED] usb0: on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered uhci1: port 0xe000-0xe01f irq 17 at device 26.1 on pci0 uhci1: [GIANT-LOCKED] usb1: on uhci1 usb1: USB revision 1.0 uhub1: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered ehci0: mem 0xfebffc00-0xfebf irq 18 at device 26.7 on pci0 ehci0: [GIANT-LOCKED] usb2:
Re: 5.3 RC2 sendmail problem
On Nov 8, 2004, at 6:25 AM, Lowell Gilbert wrote: Nick Sayer <[EMAIL PROTECTED]> writes: Something is very wrong with sendmail in 5.3RC2. Under 5.2.1, my sendmail config, which is simply the default, plus a SMART_HOST worked fine. Under 5.3RC2, attempts to get to the smart host result in 'host name lookup failure'. In searching the archives, I note I am not the first to bring this up, but I've found no solution. I'm really, really sure nothing changed except upgrading to 5.3RC2. What happened? I'm not seeing anything like this. Can you otherwise resolve the same hostname? Yup. The only thing that even seems like it may be remotely related is that there is no MX record for this host (only an A record). But even that seems like it should make no difference. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
5.3 RC2 sendmail problem
Something is very wrong with sendmail in 5.3RC2. Under 5.2.1, my sendmail config, which is simply the default, plus a SMART_HOST worked fine. Under 5.3RC2, attempts to get to the smart host result in 'host name lookup failure'. In searching the archives, I note I am not the first to bring this up, but I've found no solution. I'm really, really sure nothing changed except upgrading to 5.3RC2. What happened?
FreeBSD + parallel port = virtual "printer"?
Does anyone have any experience trying to get the FreeBSD parallel port driver to emulate a printer? I have a device that outputs postscript print jobs to a printer, and I'd like to capture those jobs with a nearby FreeBSD machine and pass them into lpr. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
Re: (Retry) Bridging a wi-device with a LAN-adapter
Erik Paulsen Skålerud wrote: >Hello. I'm a little confused here. >I want to bridge my wireless card (Orinoco/Lucent Silver 11mbit) with my >LAN-adapter (fxp0). > [...] > >So. Where do I stand? Can it do bridging in FreeBSD or not? I tried to make >it work, both in FreeBSD and Windows XP (yes, I know.) without any results. > You can't do it with Lucent cards, but if you go get a PrismII based 802.11b NIC, you can use host_ap mode and turn it into a "virtual access point". This, in turn, can be bridged with ng_bridge (I find netgraph bridging easier, personally. See /usr/share/examples/netgraph/ether.bridge) to fxp0 without difficulty. I don't know whether or not you can use bridging with adhoc mode. Various manufacturers OEM the PrismII cards... SMC, Lucent, Linksys, USR, ... The only bummer is that I don't know for sure whether or not the new SMC and Linksys integrated PCI cards (both sell PCI cards that simply have a pccard slot for a pccard adapter, but both now also sell all-in-one PCI cards that aren't just pccard adapters), but I don't know whether or not the wi driver supports them. I think it might be time for a "30 day loan" from Fry's. :-) > >While searching on mailinglists, I see several people saying that you need a >binary firmware wich costs money so that the cards can work with bridging.. >the reason would be that the manufactors of these chipsets wants to make >money on selling licenses to companies who want an AP. > That's true, for Lucent cards. > >I've also heard a rumour that ng_bridge(4)/netgraph can do bridging with >wi(4)-devices. Is this true? > That's true, for PrismII cards. :-) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
