RE: 4 -> 5 Problem
I've just completed my 3rd 5.0 -> 5-current upgrade over nfs, and it always
sig 12's on me. however, if I cd /usr/obj/usr/src/sys/ and 'make
install' from there it works fine. Good workaround for this particular
problem.
I have also gotten an error regarding this line in Makefile.inc1 for early
versions of 5.x
743 .if (!defined(NO_RESCUE) || \
744 defined(RELEASEDIR)) && \
745 (${TARGET_ARCH} != ${MACHINE_ARCH} || ${BOOTSTRAPPING} < 501101)
746 _crunchide= usr.sbin/crunch/crunchide
747 .endif
where make complains that ${BOOTSTRAPPING} < 501101 is invalid, because it
thinks it's a string comparison..
Changing it to != for a quick hack works for upgrading 5.0.
Lawrence Farr wrote:
> Does this need a note in UPDATING then? 4-> 5 over NFS, and Older
> 5-> Newer 5 over NFS no longer work as previous?
>
> Lawrence Farr
> EPC Direct Limited
>> > > -Original Message-
>> > > From: M. Warner Losh [mailto:[EMAIL PROTECTED]
>> > > Sent: 02 December 2003 17:16
>> > > :
>> > > : > install -p -m 555 -o root -g wheel kernel /boot/kernel
>> > > : > *** Signal 12
>> > > :
>> > > : This usually means you've tried to update something out of
>> > > the correct
>> > > : order.
>> > >
>> > > Signal 12 means thaqt you didn't upgrade your kernel first.
this cracked me up.
--
othermark
atkin901 at nospam dot yahoo dot com
(!wired)?(coffee++):(wired);
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: BTX halts installing 5.x
Hi, I have this same machine setup, and although I haven't tried running/ booting 5.x lately, I had the same symptoms -- cold boot works, warm boots, BTX halted. I suspect that this may be the critical fix: http://article.gmane.org/gmane.os.freebsd.devel.cvs.src/15784/match=btx Josh Paetzel wrote: > I'm trying to install FreeBSD on a Dual Pentium Pro 200mhz 512K cache > system and I am getting the following error: > > CD Loader 1.01 > > Building the boot loader arguements > Looking up /BOOT/LOADER... Found > Relocating the loader and the BTX > Starting the BTX loader > > BTX loader 1.00 BTX version is 1.01 > > int=0005 err= efl=00019286 eip=0001c8a4 > eax=00a3 ebx= ecx= edx= > esi=cce65d00 edi= ebp= esp=0009407c > cs=002b ds=0033 es=0033fs=0033 gs=0033 ss=0033 > cs:eip=62 6f 6f 74 2e 6e 65 74-69 66 2e 69 70 00 62 6f >6f 74 2e 6e 65 74 69 66-2e 6e 65 74 6d 61 73 6b > ss:esp=00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 >00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 > BTX halted > > I've tried warm booting after this and I get the same results. I've tried > 5.0-RELEASE, 5.0-DP1, 5.1-RELEASE, and three different snapshots, all of > which work fine on my other machines, including one > other SMP box. It's also worth noting that 4.8-RELEASE and 4.9-RELEASE > install fine on this box. > > I can boot 4.9 and post a dmesg if that would help, but to briefly > describe the hardware: > > Intel PR440FX Mainboard > Dual Pentium Pro 200mhz 512K Cache CPUs > Adaptec 7880 SCSI controller > 4.3 gig IBM Wide SCSI-2 Disks > Intel EtherExpress Pro LAN adapter > I've tried a couple different video cards, Cirrus Logis and SIS PCI > 320 Megs of Registered ECC SDRAM > > > I've tried googling for a solution for this as well as perused the > -CURRENT archives and haven't seen anything relevent to this issue. > > Thanks in Advance, > > Josh Paetzel > > ___ > [EMAIL PROTECTED] mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "[EMAIL PROTECTED]" -- othermark atkin901 at nospam dot yahoo dot com (!wired)?(coffee++):(wired); ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Unfortunate dynamic linking for everything
I got bit by this just two days ago. I have one machine that tracks -current. It upgraded to DYNAMICROOT just fine. I nfs mounted /usr/src and /usr/obj on another 5.0-release machine made the necessary adjustments, installed the kernel, rebooted, remounted and began make installworld. It failed. The only thing that saved me was being able to nfs mount /rescue from the -current machine. I then selectively copied stuff from /usr/obj into the respective places to get various 'make install' stuff to work, in order to get to a point where I could re-run make installworld. THANKFULLY mount was statically linked (and make installworld had not yet overwritten it). Yes I still could have recovered this using a cd/floppy (neither of which this headless machine has), but it would have been a serious PITA. -- othermark atkin901 at nospam dot yahoo dot com (!wired)?(coffee++):(wired); ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Nov 4 kernel broke my 115200 console.. and fix.
My machine was hard-locking with a kernel built from yesterday. With boot -s, it freezes before you can hit return for the shell. This is a fairly generic PIII machine with ATA hdd. Booting with a keyboard and video attached works wonderfully, but is a pain in the ass with a machine that's supposed to be headless. This was working fine on the serial console before the interrupt and APIC_IO commits. It guess (*) I needed these in the kernel config, by adding options SMP deviceapic deviceacpi into my config it now boots up via serial console. *NOTE: I didn't think I had to bother with the note in UPDATING before since IO_APIC was commented out in my previous kernel config and acpi had been disabled. just a FYI for anyone else who might be lurking/searching the current list with the same problem. -- othermark atkin901 at nospam dot yahoo dot com (!wired)?(coffee++):(wired); ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: LOR route.c:182
I'll me too this one.. Another backtrace with a different call sequence (via ipv6), exact same LOR lock order reversal 1st 0xc2177c90 rtentry (rtentry) @ /usr/src/sys/net/route.c:182 2nd 0xc206537c radix node head (radix node head) @ /usr/src/sys/net route.c:544 Stack backtrace: backtrace(c0841847,c206537c,c08472ff,c08472ff,c0847355) at backtrace+0x17 witness_lock(c206537c,8,c0847355,220,c0926300) at witness_lock+0x672 _mtx_lock_flags(c206537c,0,c0847355,220,c8f45868) at _mtx_lock_flags+0xba rtrequest1(1,c8f45874,c8f458c8,0,c24376b0) at rtrequest1+0x59 rtrequest(1,c24376b0,c24376b0,c8f458cc,405) at rtrequest+0x4a in6_ifloop_request(1,c2437600,0,c2437600,40) at in6_ifloop_request+0x76 in6_ifaddloop(c2437600,0,c2437600,0,c8f45a84) at in6_ifaddloop+0x50 in6_ifinit(c200,c2437600,c8f45a2c,1,1be) at in6_ifinit+0x147 in6_update_ifa(c200,c8f45a1c,0,0,20080fe) at in6_update_ifa+0x500 in6_ifadd(c8f45b34,0,40,0,0) at in6_ifadd+0x22a prelist_update(c8f45b34,c2425740,c1390700,246,c0894d8c) at prelist_updat +0x3f7 nd6_ra_input(c1390700,28,38,4,1) at nd6_ra_input+0x4ec icmp6_input(c8f45cac,c8f45c8c,3a,c0629780,38) at icmp6_input+0x9b5 ip6_input(c139f400,0,c084706a,89,0) at ip6_input+0xb97 netisr_processqueue(c0927378,0,c084706a,e5,c1f4d040) at netisr_processqueu +0x8e swi_net(0,0,c083c53a,21b,c137e5ac) at swi_net+0x98 ithread_loop(c137cb80,c8f45d48,c083c3ac,311,0) at ithread_loop+0x192 fork_exit(c061f2f0,c137cb80,c8f45d48) at fork_exit+0xb4 fork_trampoline() at fork_trampoline+0x8 --- trap 0x1, eip = 0, esp = 0xc8f45d7c, ebp = 0 --- Jiri Mikulas wrote: > lock order reversal > 1st 0xc220b690 rtentry (rtentry) @ /usr/src/sys/net/route.c:182 > 2nd 0xc204807c radix node head (radix node head) @ > /usr/src/sys/net/route.c:133 > Stack backtrace: > backtrace(c087588d,c204807c,c087b88a,c087b88a,c087b8e0) at backtrace+0x17 > witness_lock(c204807c,8,c087b8e0,85,c087b8e0) at witness_lock+0x672 > _mtx_lock_flags(c204807c,0,c087b8e0,85,0) at _mtx_lock_flags+0xba > rtalloc1(c08d657c,1,1,3d8,c8f44b30) at rtalloc1+0x79 > rt_setgate(c220b600,c2255a40,c08d657c,1,0) at rt_setgate+0x268 > rtredirect(c08d656c,c08d657c,0,6,c08d658c) at rtredirect+0x1bf > icmp_input(c1397c00,14,c0666d13,c093af88,c093b280) at icmp_input+0x4ff > ip_input(c1397c00,0,c087b5f5,89,0) at ip_input+0xae8 > netisr_processqueue(c0961b10,0,c087b5f5,e5,c1f491c0) at > netisr_processqueue+0x8e > swi_net(0,0,c0870582,21b,c137e974) at swi_net+0x98 > ithread_loop(c137cd00,c8f44d48,c08703f4,311,0) at ithread_loop+0x192 > fork_exit(c062bbe0,c137cd00,c8f44d48) at fork_exit+0xb4 > fork_trampoline() at fork_trampoline+0x8 > --- trap 0x1, eip = 0, esp = 0xc8f44d7c, ebp = 0 --- > > > ___ > [EMAIL PROTECTED] mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "[EMAIL PROTECTED]" -- othermark atkin901 at nospam dot yahoo dot com (!wired)?(coffee++):(wired); ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: panic: Memory modified after free
Thanks again for looking at this problem Doug White wrote: > On Thu, 23 Oct 2003, othermark wrote: > Onboard fiber? What kind of system is this? They're wired to the board. I'd probably break the connector if I remove it. This box has custom hardware attached, I don't expect any of the drivers to attach (with exception of the std onboard ethernet) because of this. I do want -current to come up so I can begin driver twiddling. >> > That or perhaps you have bad memory. Do you have ECC RAM in the >> > system? I found some and turned on bios ecc logging. Same panic, no ECC errors corrections. > I suspect the actual last user is irrelevant; its a leaking pointer > reference somewhere and the memory allocator is handing the memory block > it points to back out to some innocent bystander who triggers the panic. > > Have you emailed the em driver maintainer yet? Based on my later replies - October 16th boots fine, and October 17th snapshot b0rks on this panic, I'm not convinced the em driver is at fault. I will recompile w/o em in the kernel to test this theory. -- othermark atkin901 at nospam dot yahoo dot com (!wired)?(coffee++):(wired); ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: panic: Memory modified after free
Hi, thanks for taking a gander at my problem. The original panic can be reviewed here: http://article.gmane.org/gmane.os.freebsd.current/31913 now to answer your query... Doug Rabson wrote: > On Thu, 2003-10-23 at 22:45, othermark wrote: >> I wrote: >> > I will try seeing how far I can go up the list of snapshots until I >> > encounter the first boot -s panic. >> >> Well I walked up the available snapshots and the first panic occurs with >> the snapshot from the 17th of October. Reviewing the commit logs between >> the 16th and the 17th I note the following commits are the most >> 'interesting.' as related to this panic.. This is just a cursory look >> at the logs, I haven't gotten into compiling and fingering an exact >> commit yet (which takes loads of time). >> >> dfr 2003/10/16 02:16:28 PDT >> >> FreeBSD src repository >> >> Modified files: >> sys/sys bus.h kobj.h param.h >> sys/kern subr_bus.c subr_kobj.c >> Log: >> * Add multiple inheritance to kobj. > > I haven't had any other reports of breakage related to this. Is it > possible that you are using a kernel module which you have not re-built > after this date (e.g. nvidia.ko)? I'm not loading any modules with the single user boot 'boot -s'. (kldstat shows no modules, just 'kernel'). In fact I only downloaded the 'kernel' file for each snapshot off current.freebsd.org, placed it in it's own directory under /boot and referenced it explicitly at the boot prompt. Beginning at the oct 17th snapshot, I got the same panic as referenced in my original post to the list. Does anyone else have a box with several legacy isa pnp cards or embedded devices that can try to boot up -current from after the 17th? -- othermark atkin901 at nospam dot yahoo dot com (!wired)?(coffee++):(wired); ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: panic: Memory modified after free
I wrote: > I will try seeing how far I can go up the list of snapshots until I > encounter the first boot -s panic. Well I walked up the available snapshots and the first panic occurs with the snapshot from the 17th of October. Reviewing the commit logs between the 16th and the 17th I note the following commits are the most 'interesting.' as related to this panic.. This is just a cursory look at the logs, I haven't gotten into compiling and fingering an exact commit yet (which takes loads of time). dfr 2003/10/16 02:16:28 PDT FreeBSD src repository Modified files: sys/sys bus.h kobj.h param.h sys/kern subr_bus.c subr_kobj.c Log: * Add multiple inheritance to kobj. ... dfr 2003/10/16 02:18:36 PDT FreeBSD src repository Modified files: sys/i386/isa isa_compat.c Log: Add a workaround for the fact that the priv field was removed ... bde 2003/10/16 03:44:24 PDT FreeBSD src repository Modified files: sys/i386/isa apic_vector.s Log: Don't forget to load %es with the kernel data segment selector in Xcpustop(). ... -- othermark atkin901 at nospam dot yahoo dot com (!wired)?(coffee++):(wired); ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: panic: Memory modified after free
apologies for repling to my own post, but it seemed the best way to continue
the thread.
othermark wrote:
> I think the next step is to move up to a 5.1-release kernel and see if
> it boots as well as the 5.0-release does, or provides a more interesting
> panic.
I tried a 5.1-RELEASE kernel and booted successfully. To take it a step
further, I tried an ftp'd kernel from current.freebsd.org
5.1-CURRENT-20031009-JPSNAP
and I was able to bootstrap the box into single user mode.
If I bootstrap the box into multiuser (snapshot kernel + 5.0 userland) I get
the following panic:
Memory modified after free 0xc4987800(2044) val=c4986800 @ 0xc4987950
panic: Most recently used by bus
Debugger("panic")
Stopped at Debugger+0x54: xchgl %ebx,in_Debugger.0
db> where
Debugger(c083db04,c08ffbc0,c0855049,d782662c,100) at Debugger+0x54
panic(c0855049,c081f6e0,7fc,c4986800,c4987950) at panic+0xd5
mtrash_ctor(c4987800,800,0,583,c4987800) at mtrash_ctor+0x67
uma_zalloc_arg(c103ae40,0,2,c08feb04,0) at uma_zalloc_arg+0x1ce
malloc(800,c0899c40,2,a7c,c0843763) at malloc+0xd3
allocbuf(cec0ef88,800,c0843763,a31,4000) at allocbuf+0x202
getblk(c49d136c,0,0,800,0) at getblk+0x4d6
breadn(c49d136c,0,0,800,0) at breadn+0x52
bread(c49d136c,0,0,800,0) at bread+0x4c
ffs_blkatoff(c49d136c,0,0,0,d7826888) at ffs_blkatoff+0xcf
ufs_lookup(d7826948,d7826984,c0685211,d7826948,d7826bec) at ufs_lookup+0x393
ufs_vnoperate(d7826948,d7826bec,d7826c00,c0844f5d,c1d05390) at ufs_vnoperat
+0x18
vfs_cache_lookup(d78269c8,d78269e4,c068a2b2,d78269c8,20002) at
vfs_cache_lookup+0x301
ufs_vnoperate(d78269c8,20002,c1d05390,c062d9a0,c1d05390) at ufs_vnoperat
+0x18
lookup(d7826bd8,0,c0844896,a6,c1d05390) at lookup+0x302
namei(d7826bd8,0,c09091e0,3,c1d05390) at namei+0x24e
vn_open_cred(d7826bd8,d7826cd8,0,c1cfbe00,9) at vn_open_cred+0x251
vn_open(d7826bd8,d7826cd8,0,9,c083b124) at vn_open+0x30
kern_open(c1d05390,bfbfefb0,0,a,0) at kern_open+0x140
open(c1d05390,d7826d10,c08590bb,3ec,3) at open+0x30
syscall(2f,2f,2f,bfbfefaf,bfbfdde4) at syscall+0x273
Xint0x80_syscall() at Xint0x80_syscall+0x1d
--- syscall (5, FreeBSD ELF32, open), eip = 0x280b6973, esp = 0xbfbfdd3c,
ebp = 0xbfbfe218 ---
db>
I will try seeing how far I can go up the list of snapshots until I
encounter the first boot -s panic.
--
othermark
atkin901 at nospam dot yahoo dot com
(!wired)?(coffee++):(wired);
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: panic: Memory modified after free
Thanks for looking at this. I'm still scratching my head on it. Doug White wrote: > On Mon, 20 Oct 2003, othermark wrote: >> I have a strange panic during the isa pnp code that does not occur with a >> 5.0-release kernel. ... > Can you pull out or disable the gig-e card? Its having trouble > initializing, and I'm wondering if its doing something bad in the process. these are fibre 1000 base sx connections. They don't attach correctly in the 5.0-release kernel as well (with the exact same error), but it does continue to boot correctly. These are hardwired into the bus, and I'm unable to disable them. :( > That or perhaps you have bad memory. Do you have ECC RAM in the system? I'm not positive, so I'm going to say no, but I'm also fairly sure that the memory is good. I ran make buildworld on 5.0 successfully w/o any problems. Slow bios memcheck at startup is good. > Here is the panic again: > >> Memory modified after free 0xc4758800(2044) val=c4756800 @ 0xc47589dc >> panic: Most recently used by bus-sc this seems similar to: http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/53566 except the last user is of memory is different. Speaking of memory 5.0 - release: real memory = 536870912 (512 MB) Physical memory chunk(s): ! 0x1000 - 0x0009efff, 647168 bytes (158 pages) ! 0x0064f000 - 0x1fff7fff, 530223104 bytes (129449 pages) ! avail memory = 515031040 (491 MB) -current: real memory = 536870912 (512 MB) Physical memory chunk(s): ! 0x1000 - 0x0009efff, 647168 bytes (158 pages) ! 0x0010 - 0x003f, 3145728 bytes (768 pages) ! 0x00c26000 - 0x1f6d9fff, 514539520 bytes (125620 pages) ! avail memory = 511942656 (488 MB) I think the next step is to move up to a 5.1-release kernel and see if it boots as well as the 5.0-release does, or provides a more interesting panic. -- othermark atkin901 at nospam dot yahoo dot com (!wired)?(coffee++):(wired); ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
panic: Memory modified after free
baseTX-FDX, auto
fxp0: bpf attached
pci0: at device 11.0 (no driver attached)
isab0: port 0x580-0x58f at device 15.0 on pci0
isa0: on isab0
atapci0: port 0xffa0-0xffaf at device
15.1
on pci0
ata0: reset tp1 mask=03 ostat0=50 ostat1=50
ata0-master: stat=0x50 err=0x01 lsb=0x00 msb=0x00
ata0-slave: stat=0x50 err=0x01 lsb=0x00 msb=0x00
ata0: reset tp2 mask=03 stat0=50 stat1=50 devices=0x3
ata0: at 0x1f0 irq 14 on atapci0
ata0: [MPSAFE]
ata1: reset tp1 mask=03 ostat0=20 ostat1=30
ata1-master: stat=0x20 err=0x20 lsb=0x20 msb=0x20
ata1-slave: stat=0x30 err=0x30 lsb=0x30 msb=0x30
ata1: reset tp2 mask=03 stat0=20 stat1=30 devices=0x0
ata1: at 0x170 irq 15 on atapci0
ata1: [MPSAFE]
ohci0: mem 0xfe9ee000-0xfe9eefff irq 10 at
devic
e 15.2 on pci0
ohci0: (New OHCI DeviceId=0x02201166)
usb0: OHCI version 1.0, legacy support
usb0: on ohci0
usb0: USB revision 1.0
uhub0: (0x1166) OHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub0: 4 ports with 4 removable, self powered
pcib2: at pcibus 2 on motherboard
pci2: on pcib2
pci2: physical bus=2
map[10]: type 1, range 32, base febe, size 17, enabled
pci_cfgintr_valid: BIOS irq 9 is valid
pci_cfgintr: 2:1 INTA BIOS irq 9
found-> vendor=0x8086, dev=0x1001, revid=0x02
bus=2, slot=1, func=0
class=02-00-00, hdrtype=0x00, mfdev=0
cmdreg=0x0116, statreg=0x0220, cachelnsz=8 (dwords)
lattimer=0x40 (1920 ns), mingnt=0xff (63750 ns), maxlat=0x00 (0 ns)
intpin=a, irq=9
em0: mem
0xfebe-0xf
ebf irq 9 at device 1.0 on pci2
em0: [MPSAFE]
em0: Hardware Initialization Failedem0: Unable to initialize the hardware
device_probe_and_attach: em0 attach returned 5
ata: ata0 already exists; skipping it
ata: ata1 already exists; skipping it
Trying Read_Port at 203
Trying Read_Port at 243
Trying Read_Port at 283
Trying Read_Port at 2c3
Trying Read_Port at 303
Trying Read_Port at 343
Trying Read_Port at 383
Trying Read_Port at 3c3
ex_isa_identify()
pnpbios: 15 devices, largest 234 bytes
pnpbios: handle 0 device ID PNP0c01 (010cd041)
PNP: adding io range 0x20-0x21, size=0x2, align=0x1
PNP: adding io range 0xa0-0xa1, size=0x2, align=0x1
PNP: adding irq mask 0x4
Memory modified after free 0xc4758800(2044) val=c4756800 @ 0xc47589dc
panic: Most recently used by bus-sc
Debugger("panic")
Stopped at Debugger+0x54: xchgl %ebx,in_Debugger.0
db> where
Debugger(c083c6e1,c08fe300,c0853cc0,c0c21b4c,100) at Debugger+0x54
panic(c0853cc0,c083dd01,7fc,c4756800,c47589dc) at panic+0xd5
mtrash_ctor(c4758800,800,0,583,c4758800) at mtrash_ctor+0x67
uma_zalloc_arg(c103ae40,0,1,2c21bbc,c0891040) at uma_zalloc_arg+0x1ce
malloc(7ec,c0891040,1,c473dc80,c478f000) at malloc+0xd3
isa_add_config(c4765b00,c478d280,0,c478f000,c478f000) at isa_add_config+0x33
pnp_parse_resources(c478d280,c478e30e,19,0,c478e302) at pnp_parse_resource
+0x3b8
pnpbios_identify(c08d0db4,c4765b00,c0863280,c085d008,c08caab0) at
pnpbios_identify+0x43f
bus_generic_probe(c4765b00,c0c21d5c,c064f78e,c1cfd180,c474904c) at
bus_generic_probe+0x62
isa_probe_children(c4765b00,c08570dd,0,c0c21d98,c0610455) at
isa_probe_children+0x14
configure(0,c1e000,c1ec00,c1e000,0) at configure+0x4b
mi_startup() at mi_startup+0xb5
begin() at begin+0x2c
db>
--
othermark
atkin901 at nospam dot yahoo dot com
(!wired)?(coffee++):(wired);
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
ipv6: Strange packet leaked locally to bpf with fxp.
Hi, I'm seeing a strange packet in tcpdump when sending ICMP6 echo-requests to the all nodes multicast address (ff02::1) in both -stable and -current. This packet does not appear to get out over the wire, since a 3rd party host will not observe this packet when attached to a real hub. However when capturing locally, this packet appears before and after the ICMP6 echo request. These packets seem to contain the ipv6 packet to be sent but offset incorrectly and with the wrong data. The destination MAC address seems to be the start of the ipv6 packet. What are these null I packets? Are they particular to fxp? [EMAIL PROTECTED] root]$ tcpdump -i fxp3 tcpdump: listening on fxp3 08:05:20.213988 3a:40:fe:80:0:0 > 60:0:0:0:0:10 null I (s=1,r=112,C) len=38 81ff fe00 f6bf ff02 0001 8000 e7c9 3904 b03e 7c3f b843 0300 08:05:20.214004 fe80::2e0:81ff:fe00:f6bf > ff02::1: icmp6: echo request (len 16, hlim 64) 08:05:20.214044 3a:40:fe:80:0:0 > 60:0:0:0:0:10 null I (s=1,r=112,C) len=38 81ff fe00 f6bf fe80 02e0 81ff fe00 f6bf 8100 6dac 3904 b03e 7c3f b843 0300 08:05:21.218031 3a:40:fe:80:0:0 > 60:0:0:0:0:10 null I (s=1,r=112,C) len=38 81ff fe00 f6bf ff02 0001 8000 1eb9 3904 0001 b13e 7c3f 8053 0300 08:05:21.218047 fe80::2e0:81ff:fe00:f6bf > ff02::1: icmp6: echo request (len 16, hlim 64) 08:05:21.218086 3a:40:fe:80:0:0 > 60:0:0:0:0:10 null I (s=1,r=112,C) len=38 81ff fe00 f6bf fe80 02e0 81ff fe00 f6bf 8100 a49b 3904 0001 b13e 7c3f 8053 0300 08:05:22.208128 3a:40:fe:80:0:0 > 60:0:0:0:0:10 null I (s=1,r=112,C) len=38 81ff fe00 f6bf ff02 0001 8000 cade 3904 0002 b23e 7c3f d32c 0300 08:05:22.208143 fe80::2e0:81ff:fe00:f6bf > ff02::1: icmp6: echo request (len 16, hlim 64) 08:05:22.208183 3a:40:fe:80:0:0 > 60:0:0:0:0:10 null I (s=1,r=112,C) len=38 81ff fe00 f6bf fe80 02e0 81ff fe00 f6bf 8100 50c1 3904 0002 b23e 7c3f d32c 0300 ^C 9 packets received by filter 0 packets dropped by kernel Note that ipv6 works fine, it's just that these packets prevent me from verifying that my other hardware isn't leaking or misformatting packets. All the best, Mark atkin901 at nospam dot yahoo dot com (!wired)?(coffee++):(wired); ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: PATCH: Disable 6 byte commands for USB, firewire, ATAPICAM
In article <[EMAIL PROTECTED]>, Nate Lawson wrote: > Content-Type: TEXT/PLAIN; charset=US-ASCII > > Attached is a patch that disables ever sending 6 byte commands to buses > that do not support them. Got this trap, it's sitting there at the prompt, let me know how I can help. The clie should be acting as a USB mass storage device with no entries in scsi_da.c for quirks. I simply plugged in the device in 'export mode' (which should be like plugging in a cf reader with media inserted), and then observed these errors, then disconnected the device. The device was 'hung' during these reset/bulk messages. [EMAIL PROTECTED] root]$ sysctl hw.usb.umass.debug=5 hw.usb.umass.debug: 0 -> 5 umass0: Sony Sony PEG Mass Storage, rev 1.10/1.00, addr 2 umass0: 8070i (ATAPI) over CBI with CCI (using CBI); quirks = 0x umass0:0:0:-1: Attached to scbus0 (probe0:umass-sim0:0:0:0): INQUIRY. CDB: 12 0 0 0 24 0 (probe0:umass-sim0:0:0:0): CAM Status: SCSI Status Error (probe0:umass-sim0:0:0:0): SCSI Status: Check Condition (probe0:umass-sim0:0:0:0): UNIT ATTENTION asc:28,0 (probe0:umass-sim0:0:0:0): Not ready to ready change, medium may have changed (probe0:umass-sim0:0:0:0): Retrying Command (per Sense Data) umass0: CBI reset failed, TIMEOUT umass0: CBI bulk-in stall clear failed, TIMEOUT umass0: CBI bulk-out stall clear failed, TIMEOUT daregister: setting no 6 byte umass0: CBI reset failed, TIMEOUT umass0: CBI bulk-in stall clear failed, TIMEOUT umass0: CBI bulk-out stall clear failed, TIMEOUT umass0: CBI reset failed, TIMEOUT umass0: CBI bulk-in stall clear failed, TIMEOUT umass0: CBI bulk-out stall clear failed, TIMEOUT umass0: CBI reset failed, TIMEOUT umass0: CBI bulk-in stall clear failed, TIMEOUT umass0: CBI bulk-out stall clear failed, TIMEOUT umass0: CBI reset failed, TIMEOUT umass0: CBI bulk-in stall clear failed, TIMEOUT umass0: CBI bulk-out stall clear failed, TIMEOUT umass0: CBI reset failed, IOERROR umass0: CBI bulk-in stall clear failed, IOERROR umass0: CBI bulk-out stall clear failed, IOERROR (da0:umass-sim0:0:0:0): got CAM status 0x4 (da0:umass-sim0:0:0:0): fatal error, failed to attach to device (da0:umass-sim0:0:0:0): lost device umass0: CBI reset failed, IOERROR umass0: CBI bulk-in stall clear failed, IOERROR umass0: CBI bulk-out stall clear failed, IOERROR umass0: CBI reset failed, IOERROR umass0: CBI bulk-in stall clear failed, IOERROR umass0: CBI bulk-out stall clear failed, IOERROR umass0: CBI reset failed, IOERROR umass0: CBI bulk-in stall clear failed, IOERROR umass0: CBI bulk-out stall clear failed, IOERROR umass0: CBI reset failed, IOERROR umass0: CBI bulk-in stall clear failed, IOERROR umass0: CBI bulk-out stall clear failed, IOERROR umass0: CBI reset failed, IOERROR umass0: at uhub0 port 2 (addr 2) disconnected umass0: detached Fatal trap 12: page fault while in kernel mode fault virtual address = 0xdeadc10a fault code = supervisor read, page not present instruction pointer = 0x8:0xc034a346 stack pointer = 0x10:0xc8625b88 frame pointer = 0x10:0xc8625b88 code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags= interrupt enabled, resume, IOPL = 0 current process = 26 (usb0) kernel: type 12 trap, code=0 Stopped at device_get_nameunit+0x6:movl0x2c(%eax),%eax db> trace device_get_nameunit(deadc0de,23,0,0,6) at device_get_nameunit+0x6 umass_cbi_state(c1c12300,c1c12500,6,c18b5000,6) at umass_cbi_state+0x659 usb_transfer_complete(c1c12300,2,c053635d,c18b5000,c19f5800,c05900c4) at usb_tra nsfer_complete+0x1ba uhci_abort_xfer(c1c12300,6,c8625c40,c02d7349,c1c12300) at uhci_abort_xfer+0x118 uhci_device_ctrl_abort(c1c12300,0,c053635d,14a,c19f5800) at uhci_device_ctrl_abo rt+0x33 usbd_ar_pipe(c19f5800,c8625c60,c02d5594,c19f5800,c19f5d80) at usbd_ar_pipe+0x99 usbd_abort_pipe(c19f5800,c19f5d80,c19f5e00,c8625c7c,c02d62bd) at usbd_abort_pipe +0x11 usbd_kill_pipe(c19f5800,c0349f4c,c19f5e00,1,c18d55c0) at usbd_kill_pipe+0x14 usb_free_device(c19f5e00,c19f5d80,c18d15a0,c18d5400,c18d15a0) at usb_free_device +0x1d usb_disconnect_port(c18d55c0,c18d5500,11,0,0) at usb_disconnect_port+0x12d uhub_explore(c18d5400,c18aa120,c8625d0c,c02d2d01,c18aa120) at uhub_explore+0x2a1 usb_discover(c18aa120,0,5c,c052c40e,1770) at usb_discover+0x65 usb_event_thread(c18aa120,c8625d48,c053571a,312,423f0) at usb_event_thread+0x91 fork_exit(c02d2c70,c18aa120,c8625d48) at fork_exit+0xcf fork_trampoline() at fork_trampoline+0x1a --- trap 0x1, eip = 0, esp = 0xc8625d7c, ebp = 0 --- db> --- Mark atkin901 at NOSPAM yahoo dot com (!wired)?(coffee++):(wired); ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
