Re: BTX halted
this is a few days old. i got a reply saying to try floppies but from the INSTALL.txt under the amd64/5.3-REL it says: 1.3 Floppy Disk Image Instructions Floppy disk based install is not supported on FreeBSD/amd64. like i said i played with bios settings and nothing really worked. can somebody help? thanks.. > hi all... > > i'm trying to install 5.3 on an amd machine... > i got the discs and they are ok but when i start the off the disk the boot > stops with BTX halted no matter which boot mode i chose. > i looked on google and i found a few posts about bios issues but non of > that helped - i couldn't find how to disable DMA. the only location i saw > the DMA mentioned was under PnP/PCI configurations => Resources Controlled > by in the bios but there the setting is Auto(ESCD). i tried al the options > there and it still stops at the same place... > > anybody can help?! > > thanks > > > -- > > > > > ___ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "[EMAIL PROTECTED]" > -- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: burncd freeze system
On Tue, 2005-Jan-04 00:20:59 +0100, Norbert Augenstein wrote: >i have tried to burn an iso of 26MB of size, and my system locks >up so i have to reboot. /var/log/messages is unlikely to include the last 30 seconds or so of logging following a crash. Try running burncd from the console and see if there are any messages. Also, you might like to expand on "locks up". Can you ping the system from another host? Switch VTYs? If you have DDB enabled, can you enter it? >As i can burn it in Win, i am out of ideas. I presume this is Winbloze on the same host (dual-boot). -- Peter Jeremy ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: mysql crashes on 5.3-stable, SMP, linuxthreads
--On 1-1-2005 20:17 -0600 Billy Newsom <[EMAIL PROTECTED]> wrote: I have just built a FreeBSD 5.3 box with SMP enabled on a dual processor machine. I kept having a lot of crashes at some point in the install, and I believe I now have the cuprit: mysql-server-4.1.7 is doing it. Lately, when mysql-server is running under no load, it caused lockups of the system, with no core dumps. I had a similar issue: within one hour after upgrading mysql from 4.0.20 to 4.0.22 on a 4.10 box, my machine crashed. This happened when I asked for a webpage that querys a mysql database. It had been running stable for two years continuously and now it unexpectedly crashed without any available log entry or core dump. On startup the automatig file system check failed because of some unexpected softupdate errors. This could very well be completely unrelated to your problem as my setup is completely different, and all signs suggest a hardware problem. However as the only thing changed was mysql and the thing triggering it was accessing the database, I have my suspicions. As it is a colocated box and someone had to manually run an fsck I've decided not to try to reproduce it, but to disable mysql (all but one application was using postgresql anyway) and the server has been running stable since then. -- Edwin ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
burncd freeze system
Hallo list, i have tried to burn an iso of 26MB of size, and my system locks up so i have to reboot. The image was created with: mkisofs -l -J -r -o output.iso burndir/ and the burncommand was: burncd -f /dev/acd1 -s 4 data output.iso fixate After reboot i can find in /var/log/messages: Jan 3 23:40:07 seth kernel: acd1: unknown transfer phase Jan 3 23:40:17 seth kernel: acd1: FAILURE - ATAPI_IDENTIFY timed out Jan 3 23:40:17 seth kernel: acd1: timeout sending command=a1 Jan 3 23:40:17 seth kernel: acd1: error issueing ATAPI_IDENTIFY command Jan 3 23:41:27 seth syslogd: kernel boot file is /boot/kernel/kernel The system freezes while fixating the disc, so burncd -t shows no error. As i can burn it in Win, i am out of ideas. --> auge dmesg: Copyright (c) 1992-2004 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.3-RELEASE-p2 #0: Fri Dec 24 02:42:28 CET 2004 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/AUGE Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: AMD Athlon(TM) XP 2600+ (2083.11-MHz 686-class CPU) Origin = "AuthenticAMD" Id = 0x681 Stepping = 1 Features=0x383fbff AMD Features=0xc040 real memory = 536854528 (511 MB) avail memory = 511483904 (487 MB) npx0: [FAST] npx0: on motherboard npx0: INT 16 interface acpi0: on motherboard acpi0: Power Button (fixed) Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <32-bit timer at 3.579545MHz> port 0xe408-0xe40b on acpi0 cpu0: on acpi0 acpi_button0: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 ACPI link \\_SB_.LNKE has invalid initial irq 15, ignoring ACPI link \\_SB_.LNKF has invalid initial irq 9, ignoring pci0: on pcib0 pcib1: at device 1.0 on pci0 pci1: on pcib1 nvidia0: mem 0xe780-0xe787,0xe800-0xefff,0xe600-0xe6ff irq 11 at device 0.0 on pci1 nvidia0: [GIANT-LOCKED] bfe0: mem 0xe580-0xe5801fff irq 10 at device 9.0 on pci0 miibus0: on bfe0 bmtphy0: on miibus0 bmtphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto bfe0: Ethernet address: 00:e0:18:c0:c7:28 bfe0: [GIANT-LOCKED] isab0: at device 17.0 on pci0 isa0: on isab0 atapci0: port 0xb800-0xb80f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 17.1 on pci0 ata0: channel #0 on atapci0 ata1: channel #1 on atapci0 pcm0: port 0xe000-0xe0ff at device 17.5 on pci0 pcm0: [GIANT-LOCKED] pcm0: fdc0: port 0x3f7,0x3f2-0x3f5 irq 6 drq 2 on acpi0 fdc0: [FAST] fd0: <1440-KB 3.5" drive> on fdc0 drive 0 ppc0: port 0x778-0x77b,0x378-0x37f irq 7 drq 3 on acpi0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/9 bytes threshold ppbus0: on ppc0 plip0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A sio1: <16550A-compatible COM port> port 0x2f8-0x2ff irq 3 on acpi0 sio1: type 16550A atkbdc0: port 0x64,0x60 irq 1 on acpi0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] psm0: irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: model MouseMan+, device ID 0 pmtimer0 on isa0 orm0: at iomem 0xc-0xcefff on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> vga0: at port 0x3c0-0x3df iomem 0xa-0xb on isa0 Timecounter "TSC" frequency 2083105636 Hz quality 800 Timecounters tick every 10.000 msec ad0: 57241MB [116301/16/63] at ata0-master UDMA100 acd0: DVDROM at ata1-master UDMA33 acd1: CDRW at ata1-slave UDMA33 Mounting root from ufs:/dev/ad0s2a WARNING: / was not properly dismounted WARNING: /tmp was not properly dismounted WARNING: /var was not properly dismounted WARNING: /usr was not properly dismounted WARNING: /home was not properly dismounted -- 11:50PM up 2 days, 2:55, 0 users, load averages: 0.00, 0.00, 0.00 Does the name Pavlov ring a bell? ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
dump dumping core
With RELENG_5 from yesterday, as well from a week or so ago I'm finding that dump is failing. Must admit, this is the first time I've tried to run a backup since migrating from RELENG_4 to RELENG_5. fsck -f / marks the file system as clean. Any ideas? [EMAIL PROTECTED] dump -0a -b 512 -f - / > /dev/null DUMP: WARNING: should use -L when dumping live read-write filesystems! DUMP: Date of this level 0 dump: Mon Jan 3 21:38:32 2005 DUMP: Date of last level 0 dump: the epoch DUMP: Dumping /dev/ad0s1a (/) to standard output DUMP: mapping (Pass I) [regular files] DUMP: mapping (Pass II) [directories] DUMP: estimated 21084554 tape blocks. DUMP: 0.00% done, finished in 0:00 at Mon Jan 3 21:38:44 2005 DUMP: dumping (Pass III) [directories] DUMP: SIGSEGV: ABORTING! DUMP: SIGSEGV: ABORTING! DUMP: SIGSEGV: ABORTING! DUMP: SIGSEGV: ABORTING! DUMP: SIGSEGV: ABORTING! Segmentation fault (core dumped) [EMAIL PROTECTED] gdb /sbin/dump -c dump.core GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-marcel-freebsd"... Core was generated by `dump'. Program terminated with signal 11, Segmentation fault. Reading symbols from /lib/libc.so.5...done. Loaded symbols for /lib/libc.so.5 Reading symbols from /libexec/ld-elf.so.1...done. Loaded symbols for /libexec/ld-elf.so.1 #0 0x2814a687 in memcpy () from /lib/libc.so.5 (gdb) bt #0 0x2814a687 in memcpy () from /lib/libc.so.5 #1 0x080506a7 in bread (blkno=1001, buf=0x82b4000 "", size=0) at /usr/src/sbin/dump/traverse.c:785 #2 0x0804e406 in doslave (cmd=4, slave_number=0) at /usr/src/sbin/dump/tape.c:787 #3 0x0804e235 in enslave () at /usr/src/sbin/dump/tape.c:725 #4 0x0804df6f in startnewtape (top=1) at /usr/src/sbin/dump/tape.c:630 #5 0x0804b309 in main (argc=0, argv=0xbfbfec48) at /usr/src/sbin/dump/main.c:503 (gdb) up #1 0x080506a7 in bread (blkno=1001, buf=0x82b4000 "", size=0) at /usr/src/sbin/dump/traverse.c:785 785 memcpy(&buf[xfer], tmpbuf, resid); (gdb) print resid $1 = -512 Cheers, -- Mark A. R. Knight finger: [EMAIL PROTECTED] Tel: +44 7973 410732http://www.knigma.org/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: unkillable processes after debugging on 5.3R
The scheduler is plain SCHED_4BSD btw. lsof (ports/sysutils) doesn't display anything for pid 20328, but does for 20326. The output fstat -vp 20328 generates changes over time; when I try it now, I get: turtle:/#fstat -vp 20328 USER CMD PID FD MOUNT INUM MODE SZ|DV R/W peters zsh20328 root / 2 drwxr-xr-x1024 r peters zsh20328 wd /toad.mnt/capitalism 892355 drwxr-xr-x 512 r peters zsh20328 text /usr 921879 -r-xr-xr-x3156 r unknown file type 5 for file 10 of pid 20328 peters zsh20328 12* local stream c7bdb690 <-> c3d8b08c can't read pipe at 0x0 peters zsh20328 13* error turtle:/#netstat -an | grep '\(c7bdb690\)\|\(c3d8b08c\)' c7bdb690 stream 0 00 c3d8b08c00 /tmp/.ICE-unix/dcop40846-1104760155 c3d8b08c stream 0 00 c7bdb69000 turtle:/#lsof /tmp/.ICE-unix/dcop40846-1104760155 COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME kdeinit 40846 wynke4u unix 0xc218b144 0t0 /tmp/.ICE-unix/dcop40846-1104760155 kdeinit 40846 wynke8u unix 0xc4752144 0t0 /tmp/.ICE-unix/dcop40846-1104760155 kdeinit 40846 wynke9u unix 0xc3dabdec 0t0 /tmp/.ICE-unix/dcop40846-1104760155 kdeinit 40846 wynke 10u unix 0xc7bde144 0t0 /tmp/.ICE-unix/dcop40846-1104760155 kdeinit 40846 wynke 11u unix 0xc3c01ca8 0t0 /tmp/.ICE-unix/dcop40846-1104760155 kdeinit 40846 wynke 12u unix 0xc25b7798 0t0 /tmp/.ICE-unix/dcop40846-1104760155 kdeinit 40846 wynke 13u unix 0xc3e07dec 0t0 /tmp/.ICE-unix/dcop40846-1104760155 kdeinit 40846 wynke 14u unix 0xc3b4c000 0t0 /tmp/.ICE-unix/dcop40846-1104760155 kdeinit 40846 wynke 15u unix 0xc3c00654 0t0 /tmp/.ICE-unix/dcop40846-1104760155 kdeinit 40846 wynke 16u unix 0xc3a95144 0t0 /tmp/.ICE-unix/dcop40846-1104760155 kdeinit 40846 wynke 17u unix 0xc238fb64 0t0 /tmp/.ICE-unix/dcop40846-1104760155 kdeinit 40846 wynke 18u unix 0xc7be2510 0t0 /tmp/.ICE-unix/dcop40846-1104760155 kdeinit 40846 wynke 19u unix 0xc1e4fa20 0t0 /tmp/.ICE-unix/dcop40846-1104760155 kdeinit 40846 wynke 21u unix 0xc3d99144 0t0 /tmp/.ICE-unix/dcop40846-1104760155 kdeinit 40846 wynke 22u unix 0xc4c14510 0t0 /tmp/.ICE-unix/dcop40846-1104760155 kdeinit 40846 wynke 23u unix 0xc3e523cc 0t0 /tmp/.ICE-unix/dcop40846-1104760155 kdeinit 40846 wynke 24u unix 0xc3c00a20 0t0 /tmp/.ICE-unix/dcop40846-1104760155 kdeinit 40846 wynke 25u unix 0xc22bd8dc 0t0 /tmp/.ICE-unix/dcop40846-1104760155 kdeinit 40846 wynke 26u unix 0xc21db654 0t0 /tmp/.ICE-unix/dcop40846-1104760155 kdeinit 40846 wynke 27u unix 0xc3e533cc 0t0 /tmp/.ICE-unix/dcop40846-1104760155 kdeinit 40846 wynke 28u unix 0xc3e53a20 0t0 /tmp/.ICE-unix/dcop40846-1104760155 kdeinit 40846 wynke 29u unix 0xc3c01144 0t0 /tmp/.ICE-unix/dcop40846-1104760155 kdeinit 40846 wynke 30u unix 0xc3b8a000 0t0 /tmp/.ICE-unix/dcop40846-1104760155 kdeinit 40846 wynke 31u unix 0xc3be9b64 0t0 /tmp/.ICE-unix/dcop40846-1104760155 kdeinit 40846 wynke 36u unix 0xc3c00288 0t0 /tmp/.ICE-unix/dcop40846-1104760155 kdeinit 40846 wynke 37u unix 0xc25b7dec 0t0 /tmp/.ICE-unix/dcop40846-1104760155 kdeinit 40846 wynke 38u unix 0xc7bdf3cc 0t0 /tmp/.ICE-unix/dcop40846-1104760155 kdeinit 40846 wynke 39u unix 0xc3c018dc 0t0 /tmp/.ICE-unix/dcop40846-1104760155 kdeinit 40846 wynke 41u unix 0xc3a95b64 0t0 /tmp/.ICE-unix/dcop40846-1104760155 kdeinit 40846 wynke 42u unix 0xc2968dec 0t0 /tmp/.ICE-unix/dcop40846-1104760155 turtle:/# So it seems like some memory is reused but still accessible via the 'hanging' process... Marc pgpcyXVrTvBCM.pgp Description: PGP signature
Re: USB scanner not attached when connected after system startup]
On Mon, Jan 03, 2005 at 08:23:33PM +0100, Harald Weis wrote: > On Sun, Jan 02, 2005 at 02:22:27PM +0100, Roland Smith wrote: > > On Sun, Jan 02, 2005 at 01:17:37PM +0100, Harald Weis wrote: > > > Sometimes the device that gets noticed by usbd is not the device that > > you eventually want. For instance, I have a usb pendrive. When I plug it > > in, usbd sees a device called umass0. But what I'm interested in is the > > adXsY device that represents the partition on the drive. So in this case > > usbd isn't very helpful. > > and you would see it in dmesg ? Yes. For instance when I plug in my digital camera to offload pictures, I get the following in dmesg: umass0: NIKON NIKON DSC D70, rev 1.10/1.00, addr 2 da0 at umass-sim0 bus 0 target 0 lun 0 da0: Removable Direct Access SCSI-2 device da0: 1.000MB/s transfers da0: 244MB (500401 512 byte sectors: 64H 32S/T 244C) In usbd I'd only see the events related to umass0. > > I've asked this before, but you never answered; If you plug in the > > scanner in a running system, do you see it in the 'dmesg' output? > > No. That's not good. AFAICT, the code that reports a new scanner to dmesg is also present in 4.x, so if you don't see a message, it looks like the scanner is not found for one reason or another. Do you see anything in dmesg if it is available at boot? If so, it would look like a definite bug to me. But since it works on 5.3, I don't know what the value would be of sending a Problem Report on 4.9, since 5.3 is now STABLE. Have you considered upgrading to 5.3? > [Very sorry for not having replied to that question before. I have > simply repressed it (verdrängt in German) :-) > because sane, scanimage and > last not least usbd clearly proved - to my troubled mind - that the > scanner was not attached and I was subconsciously convinced that dmesg > signals only events during system startup. This is how I used it up to > now. I still don't know what `core file' and `name list' or `kernel > image' exactly means.] See 'man core' for more info about coredumps. Core is an old term for memory (dating from the time of ferrite core memory). See the jargon file. > > If you do _not_ get a message like: > > > > uscanner0: EPSON EPSON Scanner, rev 1.10/3.02, addr 2 > > > > in your dmesg after you plug in the scanner, I'd say that your kernel > > doesn't recognize the scanner for some reason. This would be a bug in 4.x. > > So I've got a long-standing bug (on two different boxes and several > releases starting in 2001) Very strange that I'd be the only case in > this world. I couldn't find anything in the mailing list archives. It might be the combination of the type of motherboard, chipset and scanner that causes the problem. So you could get only a small number of people affected. During a recent discussion of a bug in the direct rendering code for Radeon graphics cards on amd64, only three users of those particular cards on amd64 participated IIRC. > > If it does appear, the scanner is found by the kernel. If the scanner > > does not work in this case, what exactly is the reported error? If > > you've not running devfs, and the scanner wasn't available at boot time, > > devfs does not exist on 4.x According to the manual page for devfs(5), it has existed since 2.0. AFAIK, it has only become mandatory in 5.x. > > maybe the the device node was never created? Can you confirm that the > > device node for the scanner exists if you boot up without the scanner > > present? > > Yes, I confirm definitely. Ok, so at least that's not the problem. :-) Roland -- R.F. Smith /"\ASCII Ribbon Campaign r s m i t h @ x s 4 a l l . n l \ /No HTML/RTF in e-mail http://www.xs4all.nl/~rsmith/ X No Word docs in e-mail public key: http://www.keyserver.net / \Respect for open standards pgpAScTUWQgu9.pgp Description: PGP signature
Re: everything concerning SLIP seems to be out of date
On Mon, Jan 03, 2005 at 12:52:57AM +0100, Björn König wrote: > Hello, > > thanks a lot for your hints. The null-modem cable connection is working now. > Anyway, it was surprisingly easy, but I'm totally inexperienced and the > neglected manpages and handbook discouraged me, because I didn't touch > serial ports since a decade ;-) Finally someone points me at [1]. > > Regards Björn > > [1] > http://www.netbsd.org/guide/en/chap-net-practice.html#chap-net-practice-p2p-via-serial > Well, now that you have figured it out, don't hesitate to submit an update for the respective handbook chapter :-) (BTW, please break your lines at 75 characters or something. Makes your mails much easier to read for people with console-based clients). - Christian -- Christian Brueffer [EMAIL PROTECTED] [EMAIL PROTECTED] GPG Key: http://people.freebsd.org/~brueffer/brueffer.key.asc GPG Fingerprint: A5C8 2099 19FF AACA F41B B29B 6C76 178C A0ED 982D pgpnyCznkoAeO.pgp Description: PGP signature
Re: setting net.inet.tcp.inflight_* on 5.3-STABLE
On Sun, Jan 02, 2005 at 04:52:08PM -0800, darren david wrote: > hi all- > > so i'm attempting to tweak my kernel to eke out a bit more oomph from my > Gigabit interface, but i can't seem to set any of the > "net.inet.tcp.inflight_*" params with sysctl. i get: > > sysctl: unknown oid 'net.inet.tcp.inflight_enable' > > et al. all of the docs i've found seem to assume that it's enabled by > default in the kernel. what do i need to enable in the kernel config to > get it working? > Does 'all of the docs' include documentation of the FreeBSD website or in the FreeBSD source tree? If yes, that needs to get fixed. - Christian -- Christian Brueffer [EMAIL PROTECTED] [EMAIL PROTECTED] GPG Key: http://people.freebsd.org/~brueffer/brueffer.key.asc GPG Fingerprint: A5C8 2099 19FF AACA F41B B29B 6C76 178C A0ED 982D pgpTKOwbL4NAw.pgp Description: PGP signature
unkillable processes after debugging on 5.3R
I have two unkillable processes. System: FreeBSD turtle.stack.nl 5.3-RELEASE-p2 FreeBSD 5.3-RELEASE-p2 #5: Thu Dec 2 17:25:55 CET 2004 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/SNAIL i386 The system is SMP with two CPUs. Quoting the user: > I was debugging with the system gdb some c++-code (with a strange > segmentation fault). I was logged in via ssh and the connection seemed to > freeze (no response from keyboard input) so I disconnected (~.-sequence in > ssh). > Logging in again on the machine, I killed the debugger and shell (I don't > remember in which order) and tried to kill the program skilllist (pid > 20326). The skilllist program then appeared to be using 100% CPU time and > did not respond to any of the signals I sent. About 24 hours later, I > discovered that a zsh-process (pid 20328) was also running at lots of > cpu-time. The program was initially not run in the background, the nicing > and placing into the idle queue has been done later. > My code is c++-code, using both fd 1 and 2 for output. It is not threaded. > It does not use fork, exec etc. It's basically a simple prog, generating > only output, not listening for input. The working directory is mounted over > nfs (but my code does not open files). After the nicing and placing into the idle queue the system is properly responsive. Output of some commands about the processes: UID PID PPID CPU PRI NI VSZ RSS MWCHAN STAT TT TIME COMMAND 1711 20326 1 475 171 20 2280 1416 - RNph- 2421:35.76 ./skilllist 1711 20328 1 106 -8 20 2696 2328 - RNE ph- 729:34.15 -zsh (zsh) RTPRIO idle:25 idle:76 db> trace 20328 sched_switch(c29cd320,0,1) at sched_switch+0x143 mi_switch(1,0,c29cd320,1,c29cd320) at mi_switch+0x1ba sleepq_switch(c2302a80) at sleepq_switch+0x133 sleepq_wait(c2302a80,0,0,0,0) at sleepq_wait+0xb msleep(c2302a80,c2302bd8,4c,c06d14b3,0) at msleep+0x322 pipeclose(c2302a80,c2302b14,c3eba484,e9e9eb94,c050736c) at pipeclose+0x88 pipe_close(c3eba484,c29cd320) at pipe_close+0x2a fdrop_locked(c3eba484,c29cd320,c25b0c8c,e9e9ec04,c050616f) at fdrop_locked+0xa8 fdrop(c3eba484,c29cd320,0,2,c388a000) at fdrop+0x41 closef(c3eba484,c29cd320) at closef+0x23f fdfree(c29cd320,c3c22d70) at fdfree+0x383 exit1(c29cd320,2,1,c29cd320,c388a000) at exit1+0x4d4 sigexit(c29cd320,2,0,c3c22c5c,c29cd320) at sigexit+0xd3 postsig(2) at postsig+0x13f ast(e9e9ed48) at ast+0x4ba doreti_ast() at doreti_ast+0x17 db> trace 20326 sched_switch(,c22e3000,400,8067000,df42c340) at sched_switch+0x143 db> c [EMAIL PROTECTED] /home/jilles% fstat -vp20326 USER CMD PID FD MOUNT INUM MODE SZ|DV R/W peters skilllist 20326 root / 2 drwxr-xr-x1024 r peters skilllist 20326 wd /toad.mnt/capitalism 892355 drwxr-xr-x 512 r peters skilllist 20326 text /toad.mnt/capitalism 892490 -rwxr-xr-x 235868 r peters skilllist 203260 - - bad- peters skilllist 203261* pipe c2302b2c <-> c2302a80 0 rw peters skilllist 203262* pipe c2302b2c <-> c2302a80 0 rw [EMAIL PROTECTED] /home/jilles% fstat -vp20328 USER CMD PID FD MOUNT INUM MODE SZ|DV R/W peters zsh20328 root / 2 drwxr-xr-x1024 r peters zsh20328 wd /toad.mnt/capitalism 892355 drwxr-xr-x 512 r peters zsh20328 text /usr 921879 -r-xr-xr-x3156 r can't read sock at 0x0 peters zsh20328 10* error peters zsh20328 12 - - bad- can't read pipe at 0x0 peters zsh20328 13* error [EMAIL PROTECTED] /home/jilles% The address c2302a80 occurs in the 20328 backtrace as well. The fstat output of 20328 is unreliable: a later query returned this: [EMAIL PROTECTED] /home/jilles% fstat -vp20328 USER CMD PID FD MOUNT INUM MODE SZ|DV R/W peters zsh20328 root / 2 drwxr-xr-x1024 r peters zsh20328 wd /toad.mnt/capitalism 892355 drwxr-xr-x 512 r peters zsh20328 text /usr 921879 -r-xr-xr-x3156 r unknown file type 5 for file 10 of pid 20328 unknown file type 5 for file 12 of pid 20328 can't read pipe at 0x0 peters zsh20328 13* error [EMAIL PROTECTED] /home/jilles% -- Jilles Tjoelker ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Strange networking problems after update 5.2.1->5.3
On Mon, 2005-Jan-03 15:58:26 +0100, Gerrit Kühn wrote: >ed0: flags=108843 mtu 1500 > inet 130.75.117.37 netmask 0x broadcast 130.75.255.255 > ether 01:d4:ff:03:00:20 That's a multicast MAC address (the LSB of the first byte is 1). More intelligent NICs will have an internal list of multicast MAC addresses that they have been programmed to respond to and will ignore all other multicast addresses (for dumber NICs, this checking should be in the driver). This would explain the peculiar behaviour you are seeing. Firstly, I presume you're not attempting to change the MAC address. Secondly, the MAC address should be reported as part of the ed0 probe message - can you have a look back through your messages file and report the ed0 probe messages for both 5.2.1 and 5.3. -- Peter Jeremy ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: USB scanner not attached when connected after system startup]
On Sun, Jan 02, 2005 at 02:22:27PM +0100, Roland Smith wrote: > On Sun, Jan 02, 2005 at 01:17:37PM +0100, Harald Weis wrote: > Sometimes the device that gets noticed by usbd is not the device that > you eventually want. For instance, I have a usb pendrive. When I plug it > in, usbd sees a device called umass0. But what I'm interested in is the > adXsY device that represents the partition on the drive. So in this case > usbd isn't very helpful. and you would see it in dmesg ? > I've asked this before, but you never answered; If you plug in the > scanner in a running system, do you see it in the 'dmesg' output? No. [Very sorry for not having replied to that question before. I have simply repressed it (verdrängt in German) because sane, scanimage and last not least usbd clearly proved - to my troubled mind - that the scanner was not attached and I was subconsciously convinced that dmesg signals only events during system startup. This is how I used it up to now. I still don't know what `core file' and `name list' or `kernel image' exactly means.] > If you do _not_ get a message like: > > uscanner0: EPSON EPSON Scanner, rev 1.10/3.02, addr 2 > > in your dmesg after you plug in the scanner, I'd say that your kernel > doesn't recognize the scanner for some reason. This would be a bug in 4.x. So I've got a long-standing bug (on two different boxes and several releases starting in 2001) Very strange that I'd be the only case in this world. I couldn't find anything in the mailing list archives. > If it does appear, the scanner is found by the kernel. If the scanner > does not work in this case, what exactly is the reported error? If > you've not running devfs, and the scanner wasn't available at boot time, devfs does not exist on 4.x > maybe the the device node was never created? Can you confirm that the > device node for the scanner exists if you boot up without the scanner > present? Yes, I confirm definitely. Harald -- FreeBSD 4.9-RELEASE #0: Mon Oct 27 17:51:09 GMT 2003 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: /etc/rc: WARNING: /dev/apmctl not found
> Date: Mon, 3 Jan 2005 11:19:33 -0500 (EST) > From: "Mike Jakubik" <[EMAIL PROTECTED]> > Sender: [EMAIL PROTECTED] > > Godwin Stewart said: > > > Do you also have this in /boot/device.hints: > > > > hint.apm.0.disabled="0" > > hint.acpi.0.disabled="1" > > I have whatever the default values are for 5.3. Do these need to be set > manally? Any reason for this? What you have leaves ACPI as the power management system on you r computer. This is probably a good thing as ACPI will certainly receive better support as time goes on. ACPI is not a new APM. It covers far more things than just power management, but, since it does deal with power management, it can't co-exist with APM. It's one or the other if your BIOS supports both. Old BIOS may not support ACPI and new BIOS may not support APM. Old BIOS that does support ACPI and APM may not have very good ACPI capability, making APM a better choice. If you run ACPI, an APM emulator is also available that provides a limited APM API for utilities that used APM for things like battery life and such. For that reason, you will probably see /dev/apm if either ACPI or APM is running. You will see an apmd process and /dev/apmctl only when actual APM is used. If you have APMD_ENABLE="YES" in /etc/rc.conf, apmd will error when started with ACPI. Simply remove the like from /etc/rc/conf if you run ACPI. When you have a little time, issue the command "sysctl hw.acpi" for a list of things you can read and/or modify. Also, if you are using a laptop, try "acpiconf -i 0". (This will probably do nothing on a desktop.) -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: [EMAIL PROTECTED] Phone: +1 510 486-8634 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: /etc/rc: WARNING: /dev/apmctl not found
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Mon, 3 Jan 2005 11:19:33 -0500 (EST), "Mike Jakubik" <[EMAIL PROTECTED]> wrote: > I have whatever the default values are for 5.3. Do these need to be set > manally? Yes, they do. > Any reason for this? ACPI and APM are mutually exclusive. If one's running the other will refuse to start. The default kernel tries to load ACPI by default first thing unless either of the 2 following conditions are met: 1) The laptop is on a "blacklist" of machines known to have a fscked up ACPI subsystem. 2) You tell it explicitly *not* to do so. This is done by adding the `hint.acpi.0.disabled="1"' hint. - -- G. Stewart - [EMAIL PROTECTED] Why do people pay to go up tall buildings and then put money in binoculars to look down at things on the ground? -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQFB2XV8K5oiGLo9AcYRAo+JAKCE8J4tSPvvwu9EenRPzONboYTj2QCfd4k0 hqwFUdbLHyWgtv3G/UD8m3A= =tw4C -END PGP SIGNATURE- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Radeon DRM error
Torfinn Ingolfsen said: > On Mon, 03 Jan 2005 10:31:20 -0500 (EST) > Mike Jakubik <[EMAIL PROTECTED]> wrote: > >> Updated world recently and all my ports, and now i get the following >> when loading X on my laptop. It use to work before OK. > > And have you also updated to the correct dri version? > See /usr/ports/UPDATING, entry 20041224 (the last (topmost) one). > It suggests that there are now two dri ports graphics/dri (for Xorg) and > graphics/xfree86-dri (for Xfree86). I ran portupgrade -a, so it would have updated what was there before. I checked, and it is indeed dri 6.2_1 from ports/graphics/dri. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Samba, NTFS & FreeBSD 5-STABLE.
Igor Robul wrote: Hello, when I export NTFS volume mounted on FreeBSD-STABLE (FreeBSD sysadm.stc 5.3-STABLE FreeBSD 5.3-STABLE #0: Fri Dec 17 18:49:45 MSK 2004) via Samba, then I get strange effect: When accessing share (from Windows or from localhost via smbclient) all directories appear as files with 0 size, when I try access it, then Windows asks how to open this file. After first access, file reappears as directory. Maybe this is Samba bug, but does anyone have same problem? I only have a UFS2-share and no problems with that. Why don't you switch to UFS2, too, since you mounted it on FreeBSD and not Windows? Kay ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: setting net.inet.tcp.inflight_* on 5.3-STABLE
Joel Dahl wrote: On Sun, 2005-01-02 at 16:52 -0800, darren david wrote: hi all- so i'm attempting to tweak my kernel to eke out a bit more oomph from my Gigabit interface, but i can't seem to set any of the "net.inet.tcp.inflight_*" params with sysctl. i get: sysctl: unknown oid 'net.inet.tcp.inflight_enable' It's "net.inet.tcp.inflight.enable" :-) What a difference a "." makes. so much for cut'n'paste off the web. :p thanks! d. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: /etc/rc: WARNING: /dev/apmctl not found
Kevin Oberman said: > OK. A couple of basics: > 1. What version are you running? I'm guessing 5.3-Stable. > 2. Does /boot/loader.conf disable ACPI? How about /boot/device.hints? >(hw.acpi.0.disabled="1") It is 5.3-STABLE (from Jan 1). The values in /boot are all default. > It looks like you are starting ACPI which will block apm even if it is > in the kernel. Since APM never really starts, no /dev/apmctl is created > and ampd can't start without /dev/apmctl. (Note: You will nave /dev/apm > with either APM or ACPI.) > > Do you want/need to run with APM? On older hardware it is often much > more stable than ACPI, but on newer hardware it is often getting pretty > limited and may be vanishing completely in some cases. ACPI is the way > of the future and, for new hardware may be the only way the system will > run, but, if your system does OK on APM, it may be a safer way to go for > laptops in particular. (I run ACPI on my laptop, but I may just be a bit > crazy.) Ok, i think i may be confsed here. This is a recent (~1 year old) laptop, but basically i want the os to support all the power managment functions, be able to see the battery status, supsend/resume, etc. Is apmd not required for this? Thanks. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: /etc/rc: WARNING: /dev/apmctl not found
Godwin Stewart said: > Do you also have this in /boot/device.hints: > > hint.apm.0.disabled="0" > hint.acpi.0.disabled="1" I have whatever the default values are for 5.3. Do these need to be set manally? Any reason for this? Thanks. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Radeon DRM error
On Mon, 03 Jan 2005 10:31:20 -0500 (EST) Mike Jakubik <[EMAIL PROTECTED]> wrote: > Updated world recently and all my ports, and now i get the following > when loading X on my laptop. It use to work before OK. And have you also updated to the correct dri version? See /usr/ports/UPDATING, entry 20041224 (the last (topmost) one). It suggests that there are now two dri ports graphics/dri (for Xorg) and graphics/xfree86-dri (for Xfree86). HTH, HAND -- Regards, Torfinn Ingolfsen, Norway ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: /etc/rc: WARNING: /dev/apmctl not found
> Date: Mon, 3 Jan 2005 10:14:27 -0500 (EST) > From: "Mike Jakubik" <[EMAIL PROTECTED]> > Sender: [EMAIL PROTECTED] > > Since a recent buildworld, i have noticed the following on my laptop. > > dmesg output: > -- > > Starting usbd. > /etc/rc: WARNING: /dev/apmctl not found; kernel is missing apm(4) > Starting apmd. > > -- > > My kernel: > -- > # Power management support (see NOTES for more options) > device apm > # Add suspend/resume support for the i8254. > device pmtimer OK. A couple of basics: 1. What version are you running? I'm guessing 5.3-Stable. 2. Does /boot/loader.conf disable ACPI? How about /boot/device.hints? (hw.acpi.0.disabled="1") It looks like you are starting ACPI which will block apm even if it is in the kernel. Since APM never really starts, no /dev/apmctl is created and ampd can't start without /dev/apmctl. (Note: You will nave /dev/apm with either APM or ACPI.) Do you want/need to run with APM? On older hardware it is often much more stable than ACPI, but on newer hardware it is often getting pretty limited and may be vanishing completely in some cases. ACPI is the way of the future and, for new hardware may be the only way the system will run, but, if your system does OK on APM, it may be a safer way to go for laptops in particular. (I run ACPI on my laptop, but I may just be a bit crazy.) -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: [EMAIL PROTECTED] Phone: +1 510 486-8634 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: /etc/rc: WARNING: /dev/apmctl not found
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Mon, 3 Jan 2005 10:14:27 -0500 (EST), "Mike Jakubik" <[EMAIL PROTECTED]> wrote: > Starting usbd. > /etc/rc: WARNING: /dev/apmctl not found; kernel is missing apm(4) > Starting apmd. > > -- > > My kernel: > -- > # Power management support (see NOTES for more options) > device apm > # Add suspend/resume support for the i8254. > device pmtimer Do you also have this in /boot/device.hints: hint.apm.0.disabled="0" hint.acpi.0.disabled="1" - -- G. Stewart - [EMAIL PROTECTED] "The day Microsoft makes something that doesn't suck is probably the day they start making vacuum cleaners." --- Ernst Jan Plugge -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQFB2WWhK5oiGLo9AcYRAhYUAJoCuQK3hrzibVZxQciHLwB8ntk/kgCfVjdu lfozQR6kzf1PZB1rQkWRXm4= =9m00 -END PGP SIGNATURE- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Radeon DRM error
Updated world recently and all my ports, and now i get the following when loading X on my laptop. It use to work before OK. --- X Window System Version 6.8.1 Release Date: 17 September 2004 X Protocol Version 11, Revision 0, Release 6.8.1 Build Operating System: FreeBSD 5.3 i386 [ELF] Current Operating System: FreeBSD laptop.local 5.3-STABLE FreeBSD 5.3-STABLE #0: Sat Jan 1 17:47:12 EST 2005 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/LAPTOP i386 Build Date: 01 January 2005 Before reporting problems, check http://wiki.X.Org to make sure that you have the latest version. Module Loader present Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: "/var/log/Xorg.0.log", Time: Mon Jan 3 10:07:50 2005 (++) Using config file: "xorg.conf.new" drm0: port 0x9000-0x90ff mem 0xd010-0xd010fff f,0xe000-0xefff irq 10 at device 5.0 on pci1 info: [drm] Initialized radeon 1.11.0 20020828 on minor 0 (EE) RADEON(0): [agp] AGP failed to initialize. Disabling the DRI. error: [drm:pid491:radeon_cp_init] *ERROR* radeon_cp_init called without lock he ld error: [drm:pid491:radeon_unlock] *ERROR* Process 491 using kernel context 0 --- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
/etc/rc: WARNING: /dev/apmctl not found
Since a recent buildworld, i have noticed the following on my laptop. dmesg output: -- Starting usbd. /etc/rc: WARNING: /dev/apmctl not found; kernel is missing apm(4) Starting apmd. -- My kernel: -- # Power management support (see NOTES for more options) device apm # Add suspend/resume support for the i8254. device pmtimer -- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: setting net.inet.tcp.inflight_* on 5.3-STABLE
On Sun, 2005-01-02 at 16:52 -0800, darren david wrote: > hi all- > > so i'm attempting to tweak my kernel to eke out a bit more oomph from my >Gigabit interface, but i can't seem to set any of the > "net.inet.tcp.inflight_*" params with sysctl. i get: > > sysctl: unknown oid 'net.inet.tcp.inflight_enable' > It's "net.inet.tcp.inflight.enable" :-) -- Joel ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Strange networking problems after update 5.2.1->5.3
On Mon, 3 Jan 2005 13:19:13 + (GMT) Robert Watson <[EMAIL PROTECTED]> wrote about Re: Strange networking problems after update 5.2.1->5.3: RW> > arp things look ok, but I cannot ping the router, though I can ping RW> > any other host (the same thing I already noticed here at work). But RW> > my router at home complains about this: RW> > arp: ether address is multicast for IP address 192.168.1.4! RW> Ah, now this is very interesting -- could you send me the output of RW> "ifconfig" on the interface? ed0: flags=108843 mtu 1500 inet 130.75.117.37 netmask 0x broadcast 130.75.255.255 ether 01:d4:ff:03:00:20 RW> Could you tell me if a tcpdump on another RW> host shows the same hardware address as the source of packets from this RW> host as ifconfig shows? tcpdump -e shows the same address on the foreign host, so does arp -a. RW> Likewise, dmesg? The same, too RW> A multicast source address RW> might cause other systems to treat your system like it had the plague, RW> with some OS's ignoring it, others not, etc. So if the router refuses RW> to talk to your system because of its ethernet address, that might RW> explain many of the symptoms you are seeing. Right. Meanwhile I tried two further pcmcia cards which are 32bit (cardbus). Both (Xircom CBE2-100 and D-Link DFE-690-TXD) result in cbb0: CardBus card activation failed It seems it's rather the pcmcia bridge that's broken than the driver for the card itself. The notebook has a TI 1225 chip. RW> > I'm anything but a network guru and will see if I have some time to RW> > dig further into the packets. Perhaps I can find the broken bit then. RW> I'm guessing it's a driver problem of some sort based on the above, but RW> a few more details as described above would be helpful in confirming RW> that. Just tell me what you would like to know. RW> I've CC'd Warner Losh on the general principle that if it's a problem RW> with a PCCARD ethernet adapter, he might be able to help (perhaps RW> especially if it's possible to ship him one of the cards). I will do so if it's the support for the cards that is broken. However, I have tried 4 different cards now, and only one of them worked. So I'm tending to put the blame on the pcmcia bridge and it's driver. cu Gerrit ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Patch for PNP BIOS hang
A colleague of mine reported on a hang during boot on a SuperMicro board
(with ACPI off):
http://lists.freebsd.org/pipermail/freebsd-current/2004-March/023045.html
with some more analysis:
http://lists.freebsd.org/pipermail/freebsd-current/2004-July/030827.html
as it turns out it doesn't actually always hang, it usually takes 30-45
minutes to boot. The problem comes from the PNP0c01 entry in the PNP
BIOS, and specifically the entry:
PNP0c01: adding fixed memory32 range 0xfff8-0x, size=0x8
In isa/isa_common.c:isa_find_memory() there's a for loop that looks for
space for the memory block:
for (start = config->ic_mem[i].ir_start,
end = config->ic_mem[i].ir_end,
align = config->ic_mem[i].ir_align;
start + size - 1 <= end;
start += align) {
For some reason the attempt to use the given memory region fails. After
adding align to start, start + size - 1 wraps and the <= end test remains
true.
The following patch gets this board booting for me:
--- isa_common.c@@/main/sandvine_bsd_5_main/0 2005-01-02 15:39:24.0
-0500
+++ isa_common.c2005-01-02 23:59:06.0 -0500
@@ -149,7 +149,7 @@
for (start = config->ic_mem[i].ir_start,
end = config->ic_mem[i].ir_end,
align = config->ic_mem[i].ir_align;
-start + size - 1 <= end;
+start + size - 1 <= end && start + size > start;
start += align) {
bus_set_resource(child, SYS_RES_MEMORY, i,
start, size);
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Strange networking problems after update 5.2.1->5.3
On Mon, 3 Jan 2005, Gerrit Kühn wrote: > arp things look ok, but I cannot ping the router, though I can ping any > other host (the same thing I already noticed here at work). But my > router at home complains about this: > > arp: ether address is multicast for IP address 192.168.1.4! Ah, now this is very interesting -- could you send me the output of "ifconfig" on the interface? Could you tell me if a tcpdump on another host shows the same hardware address as the source of packets from this host as ifconfig shows? Likewise, dmesg? A multicast source address might cause other systems to treat your system like it had the plague, with some OS's ignoring it, others not, etc. So if the router refuses to talk to your system because of its ethernet address, that might explain many of the symptoms you are seeing. > >Somewhere during all of this, you will probably find the broken bit -- > >packets missing at some step, the wrong address, or the like. If you find > >anything that isn't fixed via a configuration change (i.e., failed > >checksums, no way to explain the address being put in the packet, etc), > >let us know. > > The best thing I can guess here is that 5.3 in contrast to 5.2.1 (all > three cards worked flawlessly with 5.2.1) has some problems dealing with > my hardware. :-) > > I'm anything but a network guru and will see if I have some time to dig > further into the packets. Perhaps I can find the broken bit then. I'm guessing it's a driver problem of some sort based on the above, but a few more details as described above would be helpful in confirming that. I've CC'd Warner Losh on the general principle that if it's a problem with a PCCARD ethernet adapter, he might be able to help (perhaps especially if it's possible to ship him one of the cards). Robert N M Watson ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RELENG_5: Giant not owned in ufs/ffs/ffs_vnops.c:371
Backtrace points to device md (accesses to md were during a make release on that machine). Sorry I don't have anything more detailed, panic didn't provide a dump. Excerpt from kernel stack trace: ffs_read() mdstart_vnode() md_ktrhead() Kernel from 2004-12-28. -- A: Yes. Pierre Beyssac [EMAIL PROTECTED] >Q: Are you sure? >>A: Because it reverses the logical flow of conversation. >>>Q: Why is top posting annoying in email? ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Strange networking problems after update 5.2.1->5.3
>> I recently updated my old Compaq Armada 1500c from 5.2.1 to 5-stable. 5.2
>> worked fine, the update went without any noticable problem according to the
>> docs. 5.3 behaves well apart from a strange networking problem.
>> The notebook lives in a /16 subnet with a /16 netmask and has a 16bit
>> NE2000 PCMCIA-card (Longshine).
>> Things that do work:
>> - ping to hosts in /24
>> - ssh to hosts in /24
>> - nis with a server in /24
>> Things that don't work:
>> - ping from any host
>> - ping to hosts outside /24
>> - nfs
>> - query dns in /16
>> - connecting ntp server in /16
> The summary appears to be "known local things work, less local things
> don't", although for the NFS instance it's unclear if that's local or not.
Well, what surprised me most was the fact that nothing gets to this notebook
from the outside. I cannot ping it even from a host connected to the same
switch being in the same /24 subnet.
The nfs server was in /24, too.
>This suggests a routing or ARP problem.
I think if there are such problems, they're the result of something else
that is broken with the pcmcia card itself (wrong initialization or
whatever).
I took the notebook home via New Year's and tried to hunt the problem down.
My network at home is somewhat simpler (192.168.1.0/24 is local,
192.168.1.253 is another notebook that is acting as NAT and default router).
> route -n get default
> route -n get {host in /24}
> route -n get {host in /16}
Looks ok for me. netstat doesn't show any problems either.
>Check "arp -a" and make sure that the default gateway is what you expect,
>and check to make sure it's hardware address is right. You may want to
>compare against what you see on another machine on the segment. Make sure
>you can ping the default gateway.
arp things look ok, but I cannot ping the router, though I can ping any
other host (the same thing I already noticed here at work). But my router at
home complains about this:
arp: ether address is multicast for IP address 192.168.1.4!
.4 is the IP of my notebook. Obviously the ping packets reach the router,
but I don't know what should be wrong with the MAC. The output of ifconfig
looks ok.
I tried diagnosing via tcpdump and noticed a rather strange behaviour on the
notebook (the host with the problem, not the router): Quite often tcpdumps
sees nothing at all, not even the obviously outgoing ping packets. In this
state I cannot interrupt it with CTRL-C. Waiting some time (minutes) lets it
suddenly see the packets, but they still don't get through to ping as
desired.
At home I was able to use nfs with .5 as server. However, I noticed that the
packets are broad-(or multi-?)casted to each and every host in my subnet. I
guess this is closely related to the arp-message above from my router.
I have two further pcmcia-cards in the router (dlink de-660 and dlink
dfe-650) which I took out to try them in the Compaq. The dfe-650 was
recognized as 8 bit ne1000 card and didn't work at all. The de-660 was
recognized correctly and worked fine.
I built an OLDCARD kernel, which was complaining about an interrupt storm on
irq 11 (this is the one all the network cards attached to). It found the
pcmcia-bridge, but didn't find any cards, so there was no network device.
>Somewhere during all of this, you will probably find the broken bit --
>packets missing at some step, the wrong address, or the like. If you find
>anything that isn't fixed via a configuration change (i.e., failed
>checksums, no way to explain the address being put in the packet, etc),
>let us know.
The best thing I can guess here is that 5.3 in contrast to 5.2.1 (all three
cards worked flawlessly with 5.2.1) has some problems dealing with my
hardware. :-)
I'm anything but a network guru and will see if I have some time to dig
further into the packets. Perhaps I can find the broken bit then.
cu
Gerrit
--
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: IPNAT & IPv6
but i want to do the data redirection transparently :( On Mon, 3 Jan 2005 09:25:11 +0100 (CET), Patrick M. Hausen <[EMAIL PROTECTED]> wrote: > Hello! > > > my original ipnat rule is > > rdr rl0 0.0.0.0/0 port 80 -> 127.0.0.1 port 8000 tcp > > which redirect a priv port to a non-priv port > > > > but when i setup dual stack, i find it's unable to handle ipv6 connections. > > when i change 0.0.0.0 to ::0, ipnat complains it can't resolve it. > > even when i use domains instead of numeric format, still no help. > > > > so it seems that ipnat doesn't work with ipv6? any solution? > > Don't know if ipnat works with IPv6 or if ipfw/natd would do better, > but you can always use netcat (/usr/ports/net/netcat) and inetd > for incoming connections on a NAT gateway. > > HTH, > Patrick > -- > punkt.de GmbH Internet - Dienstleistungen - Beratung > Vorholzstr. 25Tel. 0721 9109 -0 Fax: -100 > 76137 Karlsruhe http://punkt.de > -- freewizard (at) gmail.com http://blog.tsing.org/freewizard/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: IPNAT & IPv6
Hello! > my original ipnat rule is > rdr rl0 0.0.0.0/0 port 80 -> 127.0.0.1 port 8000 tcp > which redirect a priv port to a non-priv port > > but when i setup dual stack, i find it's unable to handle ipv6 connections. > when i change 0.0.0.0 to ::0, ipnat complains it can't resolve it. > even when i use domains instead of numeric format, still no help. > > so it seems that ipnat doesn't work with ipv6? any solution? Don't know if ipnat works with IPv6 or if ipfw/natd would do better, but you can always use netcat (/usr/ports/net/netcat) and inetd for incoming connections on a NAT gateway. HTH, Patrick -- punkt.de GmbH Internet - Dienstleistungen - Beratung Vorholzstr. 25Tel. 0721 9109 -0 Fax: -100 76137 Karlsruhe http://punkt.de ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
