Re: Dhclient fix for systems with media settings
Hi, Is this going to cure the cases where using DHCP results in my network link going dead about ~30 minutes after getting a lease? At that point it starts spitting out timeout errors and stuff, and i have to unplug/replug the card and re-start dhclient to get connectivity again.. Unless the lease time was ~30 minutes and you've changed networks, I doubt it. This sounds like a if_wi driver problem. Warner should be able to tell you more. Martin ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: vinum problems with todays current
In message [EMAIL PROTECTED], Rob writes:
Hi all,
After cvs'upping (about 12 hours ago) and building world/kernel vinum
stopped working. It does show my two disks but nothing more. I also
get an error message right after the bootloader:
Can you try this patch:
Index: spec_vnops.c
===
RCS file: /home/ncvs/src/sys/fs/specfs/spec_vnops.c,v
retrieving revision 1.206
diff -u -r1.206 spec_vnops.c
--- spec_vnops.c5 Aug 2003 06:43:56 - 1.206
+++ spec_vnops.c5 Aug 2003 19:33:06 -
@@ -505,9 +505,9 @@
devtoname(bp-b_dev), bp));
if ((dsw-d_flags D_NOGIANT) !(bp-b_flags B_KEEPGIANT)) {
- DROP_GIANT();
+ /* DROP_GIANT(); */
DEV_STRATEGY(bp);
- PICKUP_GIANT();
+ /* PICKUP_GIANT(); */
} else
DEV_STRATEGY(bp);
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]
[current tinderbox] failure on alpha/alpha
TB --- mkdir /home/des/tinderbox/CURRENT/alpha TB --- mkdir /home/des/tinderbox/CURRENT/alpha/alpha TB --- 2003-08-06 04:00:07 - starting CURRENT tinderbox run for alpha/alpha TB --- 2003-08-06 04:00:07 - checking out the source tree TB --- cd /home/des/tinderbox/CURRENT/alpha/alpha TB --- /usr/bin/cvs -f -R -q -d/home/ncvs checkout -P -A src TB --- 2003-08-06 04:03:50 - building world TB --- cd /home/des/tinderbox/CURRENT/alpha/alpha/src TB --- /usr/bin/make -B buildworld Rebuilding the temporary build tree stage 1: legacy release compatibility shims stage 1: bootstrap tools stage 2: cleaning up the object tree stage 2: rebuilding the object tree stage 2: build tools stage 3: cross tools stage 4: populating /home/des/tinderbox/CURRENT/alpha/alpha/obj/alpha/vol/vol0/users/des/tinderbox/CURRENT/alpha/alpha/src/i386/usr/include stage 4: building libraries stage 4: make dependencies stage 4: building everything.. TB --- 2003-08-06 05:07:24 - building generic kernel TB --- cd /home/des/tinderbox/CURRENT/alpha/alpha/src TB --- /usr/bin/make buildkernel KERNCONF=GENERIC Kernel build for GENERIC started on Wed Aug 6 05:07:25 GMT 2003 Kernel build for GENERIC completed on Wed Aug 6 05:18:56 GMT 2003 TB --- 2003-08-06 05:18:56 - generating LINT kernel config TB --- cd /home/des/tinderbox/CURRENT/alpha/alpha/src/sys/alpha/conf TB --- /usr/bin/make -B LINT TB --- 2003-08-06 05:18:56 - building LINT kernel TB --- cd /home/des/tinderbox/CURRENT/alpha/alpha/src TB --- /usr/bin/make buildkernel KERNCONF=LINT Kernel build for LINT started on Wed Aug 6 05:18:56 GMT 2003 [...] cc -c -O -pipe -mcpu=ev4 -mtune=ev5 -mieee -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/vol/vol0/users/des/tinderbox/CURRENT/alpha/alpha/src/sys -I/vol/vol0/users/des/tinderbox/CURRENT/alpha/alpha/src/sys/dev -I/vol/vol0/users/des/tinderbox/CURRENT/alpha/alpha/src/sys/contrib/dev/acpica -I/vol/vol0/users/des/tinderbox/CURRENT/alpha/alpha/src/sys/contrib/ipfilter -I/vol/vol0/users/des/tinderbox/CURRENT/alpha/alpha/src/sys/contrib/dev/ath -I/vol/vol0/users/des/tinderbox/CURRENT/alpha/alpha/src/sys/contrib/dev/ath/freebsd -D_KERNEL -include opt_global.h -fno-common -finline-limit=15000 -fno-strict-aliasing -fno-builtin -mno-fp-regs -ffixed-8 -Wa,-mev6 -ffreestanding -Werror /vol/vol0/users/des/tinderbox/CURRENT/alpha/alpha/src/sys/dev/cs/if_cs_pccard.c cc -c -O -pipe -mcpu=ev4 -mtune=ev5 -mieee -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/vol/vol0/users/des/tinderbox/CURRENT/alpha/alpha/src/sys -I/vol/vol0/users/des/tinderbox/CURRENT/alpha/alpha/src/sys/dev -I/vol/vol0/users/des/tinderbox/CURRENT/alpha/alpha/src/sys/contrib/dev/acpica -I/vol/vol0/users/des/tinderbox/CURRENT/alpha/alpha/src/sys/contrib/ipfilter -I/vol/vol0/users/des/tinderbox/CURRENT/alpha/alpha/src/sys/contrib/dev/ath -I/vol/vol0/users/des/tinderbox/CURRENT/alpha/alpha/src/sys/contrib/dev/ath/freebsd -D_KERNEL -include opt_global.h -fno-common -finline-limit=15000 -fno-strict-aliasing -fno-builtin -mno-fp-regs -ffixed-8 -Wa,-mev6 -ffreestanding -Werror /vol/vol0/users/des/tinderbox/CURRENT/alpha/alpha/src/sys/dev/dpt/dpt_eisa.c cc -c -O -pipe -mcpu=ev4 -mtune=ev5 -mieee -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/vol/vol0/users/des/tinderbox/CURRENT/alpha/alpha/src/sys -I/vol/vol0/users/des/tinderbox/CURRENT/alpha/alpha/src/sys/dev -I/vol/vol0/users/des/tinderbox/CURRENT/alpha/alpha/src/sys/contrib/dev/acpica -I/vol/vol0/users/des/tinderbox/CURRENT/alpha/alpha/src/sys/contrib/ipfilter -I/vol/vol0/users/des/tinderbox/CURRENT/alpha/alpha/src/sys/contrib/dev/ath -I/vol/vol0/users/des/tinderbox/CURRENT/alpha/alpha/src/sys/contrib/dev/ath/freebsd -D_KERNEL -include opt_global.h -fno-common -finline-limit=15000 -fno-strict-aliasing -fno-builtin -mno-fp-regs -ffixed-8 -Wa,-mev6 -ffreestanding -Werror /vol/vol0/users/des/tinderbox/CURRENT/alpha/alpha/src/sys/dev/dpt/dpt_pci.c cc -c -O -pipe -mcpu=ev4 -mtune=ev5 -mieee -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/vol/vol0/users/des/tinderbox/CURRENT/alpha/alpha/src/sys -I/vol/vol0/users/des/tinderbox/CURRENT/alpha/alpha/src/sys/dev -I/vol/vol0/users/des/tinderbox/CURRENT/alpha/alpha/src/sys/contrib/dev/acpica -I/vol/vol0/users/des/tinderbox/CURRENT/alpha/alpha/src/sys/contrib/ipfilter -I/vol/vol0/users/des/tinderbox/CURRENT/alpha/alpha/src/sys/contrib/dev/ath -I/vol/vol0/users/des/tinderbox/CURRENT/alpha/alpha/src/sys/contrib/dev/ath/freebsd -D_KERNEL -include opt_global.h
Re: MSDOSFS woes
On Wed, Aug 06, 2003 at 08:05:52PM +1000, Tim Robbins wrote: On Sat, Aug 02, 2003 at 06:08:50PM +0300, Ruslan Ermilov wrote: Gang, :-) While working with Marcel on a bootable CD-ROM for IA64 issue, I've stumbled upon the following problem. I needed to increase the size of the EFI partition (which is an MS-DOS file system) to 64M, and that made two of my machines stuck solidly -- a lot of process are waiting on the wdrain event. Interesting. Were you running with INVARIANTS on? I got a completely reproducible kernel panic when running your script, regardless of whether I used -F 12 or -F 16; it was trying to write file data past the end of the disk, and causing kernel memory pool to become corrupted. I was seeing Memory modified after free errors, with blocks most recently used by GEOM and file desc. Were you running the script with INVARIANTS on? My kernel config includes the GENERIC config which has INVARIANTS on. Further analysis of the problem shows that there are actually two problems. First problem is with newfs_msdos(8) (and kernel part of MSDOSFS). newfs_msdos(8) sometimes results in a bad file system lying about the number of available sectors (recorded in sector 0) than is actually available, as was demonstrated by Bruce Evans (and I've been able to reproduce this). Sometimes, this results in warnings from MSDOSFS on a console, immediately followed by a panic. Sometimes, I also saw the Memory modified after free. IIRC, I ended up with a conclusion that -s arguments 32M are unsafe with newfs_msdos(8). Second problem is with vnode-backed md(4) devices, and it is not MSDOSFS-specific. I've been able to reproduce the wdrain lockup after attempting to newfs(8) and fill (with cpio(1)) an 11MB-only vnode-backed UFS file system yesterday. Sometimes it just works, and sometimes it causes a lock-up. I asked Poul-Henning to look into this issue in a private message to him with more details and a test case. Cheers, -- Ruslan Ermilov Sysadmin and DBA, [EMAIL PROTECTED] Sunbay Software Ltd, [EMAIL PROTECTED] FreeBSD committer pgp0.pgp Description: PGP signature
ath0 driver
Ive got a Dlink DWL-G520 that Ive installed into a Freebsd system. Ive set up the card with the following ifconfig_ath0=inet 10.0.0.1 netmask 255.255.255.0 ssid daves channel 10 media DS11 mediaopt hostap This system was cvsuped and buildworld about 3 days ago. The card appears to be working because when I try to connect with my PDA it shows full Link and quality, and when I ifconfig ath0 down , the link and quality go down to nothing. However it doesnt give out dhcp addresses over this interface. Im sure my dhcpd.conf is fine because I've used a similar one on a laptop = aka wireless access point that worked very well. So I tried to use dstumbler to see if it could detect the PDA, however it gives me the following error error: unable to ioctl device socket: Operation now in progress and it stays that way. Has anyone had this issue as well or now what it means? Thanks David ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: dump/restore locale supports
On Wed, Aug 06, 2003 at 12:03:20 +0400, Alex Deiter wrote: restore ls .: ???_/ ???_.txt restore What to do ? I just commit fix for this into -current restore, try it. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Weird reboots from bootmgr or loader
On Tue, 5 Aug 2003, Florian Smeets wrote: Lukas Ertl wrote: I managed to fix it by booting from floppies and running the Fixit floppy, writing a new disklabel, which seems to have become corrupted somehow. Yes this really did the trick! :-) May I ask if you boot from a vinum volume? regards, le -- Lukas Ertl eMail: [EMAIL PROTECTED] UNIX Systemadministrator Tel.: (+43 1) 4277-14073 Vienna University Computer Center Fax.: (+43 1) 4277-9140 University of Vienna http://mailbox.univie.ac.at/~le/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ath0 driver
Verify you have the latest HAL using sysctl hw.ath The version should be 0.9.5.3 or better (can't remember if I committed .4 or .3). Shouldn't that be 0.9.5.2? I run the latest current, and hw.ath.hal.version is 0.9.5.2. You're right; I committed a slightly older version to FreeBSD than to Linux. Sam ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
dump/restore locale supports
dump and restore support locale? i want to restore files with russian filenames and see instead names of files: # locale LANG=ru_RU.KOI8-R LC_CTYPE=ru_RU.KOI8-R LC_COLLATE=ru_RU.KOI8-R LC_TIME=ru_RU.KOI8-R LC_NUMERIC=ru_RU.KOI8-R LC_MONETARY=ru_RU.KOI8-R LC_MESSAGES=ru_RU.KOI8-R LC_ALL=ru_RU.KOI8-R # mkdir /home/_ # touch /home/_.txt # ls -ld /home/_* drwxr-xr-x 2 root wheel 512 6 11:33 /home/_ -rw-r--r-- 1 root wheel0 6 11:52 /home/_.txt # dump -0af home.dmp /home . DUMP: DUMP IS DONE # restore -i -f home.dmp restore ls .: ???_/ ???_.txt restore What to do ? Thanks! ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: [HEADSDOWN] swap_pager.c calming down...
From: Poul-Henning Kamp [EMAIL PROTECTED] Date: Wed, 06 Aug 2003 15:54:58 +0200 ::In message [EMAIL PROTECTED], [EMAIL PROTECTED] writes: ::Hello Poul, :: ::Can you please look into problems reported on current@ list, ::the thread with subject Weird reboots from bootmgr or loader, ::as it seems to related with your recent changes for the swap code. :: ::There is no way my work could cause reboots from the bootmgr or loader. No. Actually, as John-Mark Gurney has pointed out, your change seems to let disk label part of the disk get overwritten, and you get BTX Halted or similer kind of error while tring to boot. Please see the following post (url) and its related thead. http://docs.freebsd.org/cgi/getmsg.cgi?fetch=623604+0+current/freebsd-current For my case, I had to somehow boot system up, and do 'bsdlabel -B' to get system into working condition, again. Thank you, Haro =--- _ _Munehiro (haro) Matsuda -|- /_\ |_|_| Kubota Graphics Technology Inc. /|\ |_| |_|_| 2-8-8 Shinjuku, Shinjuku-ku Tokyo 160-0022, Japan Tel: +81-3-3225-0767 Fax: +81-3-3225-0740 Email: [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: INET6 in world
On Mon, 4 Aug 2003, Terry Lambert wrote: Bernd Walter wrote: On Mon, Aug 04, 2003 at 03:32:47PM +0200, Harti Brandt wrote: What's the sense of enabling and using IPv6, if your infrastucture in the company doesn't support it (because of the overhead with routing (hardware vs. software routing)) and you don't have an IPv6 connection to the outside world. Well, you could ping localhost per IPv6... That's chicken/egg - IPv6 never will be widely used if everyone thinks that way. The sense is to break this dependency loop by ecouraging everyone to use it and not to make it easier to completely disable the support. As I said: you -always- have an IPv6 connection to the outside world as long as you have a single official IPv4 address. Not using it because it doesn't fit in your current network is one point, but disabling it in a way to make a future step to IPv6 harder is another. The number of IPv4 only systems is already big enough - we don't need to build new ones. This has been so over-argued, I don't think there's anything else to say on the matter except: Use the right tool for the right job. If you don't see yourself keeping your installation for a few years, then go ahead with your IPv4-only installation. More environments are starting to become mixed and this is a trend that will only accelerate as more sites embrace IPv6. The problem, as I see it, is that it doesn't come enabled by default on Windows systems. Until it does, it's never going to get any traction. This is really OT, but Windows XP Professional does ship with an IPv6 stack. At the cmd prompt, type 'ipv6 install' and it'll load the Microsoft IPv6 Developer Edition protocol suite. Enjoy. I wouldn't be surprised if the government has asked Microsoft to not deploy it, or to deploy it without encryption support, given world events. Well, given that they've included IPSEC in their latest operating system releases, I can't really say that I agree with that statement. To get back to the original question, NO_IPV4 and NO_IPV6 world knobs would be nice and would keep everyone happy for years to come! :-) Regards, Andre Guibert de Bruet | Enterprise Software Consultant Silicon Landmark, LLC. | http://siliconlandmark.com/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Bootstrap: Machine keeps booting ? (boot0/mbr) ?
Mensaje citado por Stephan van Beerschoten [EMAIL PROTECTED]: | I just finished installing this brand new -CURRENT box. I haven't been | on -CURRENt for a while, and thought about having a peek at 5.x. | | After installing the machine, it boots up fine for a while, but then | something strange happends. | I have not yet been able to determine WHY it happends, much less do I | know WHAT exactly happends. I hope you can help. | The only thing I did was to update my 5.1 install to the latest | -CURRENT. I assume the make world somehow also does something to update | the bootloader, or is this where I went wrong ? | Please read on: | | I installed the Bootloader for my dualboot machine, and when it comes up | during boot: | | F1 ?? | F2 FreeBSD | | and I press F2, it autmatically reboots again. Please note it DID work | yesterday, but somehow my laptops keeps booting on my now. (-CURRENT ? | why?) | | I am dualbooting with WinXP, and I initially grabbed the first 512bytes | from /dev/ad0s2c and dumped them on the XP disk, using the NTLoader to | boot FreeBSD for me. This too worked untill _something_ happened and | selecting FreeBSD caused the machine to spontaniously reboot too. | | Since this happends even before any real kernels are loaded, I cannot | produce any debug output, so any hints on resolving this issue would be | greatly appreciated. | | Please copy me in on any replies, as I am not yet on -current. I will | once this problem is fixed :) | Stephan, I have exactly the same problem. I'm assuming that this was caused by the changes committed by PHK. See the [HEADSDOWN] swap_pager.c calming down and the Weird reboots from bootmgr or loader threads. He is looking at it now and will probably be committing a fix. ed - ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Weird reboots from bootmgr or loader
quote who=Lukas Ertl On Tue, 5 Aug 2003, John-Mark Gurney wrote: Are you running -current w/ a kernel from the last 24 hrs? (After phk's mass swap check in?) If so, make sure your swap isn't at the start of your disk. If it is, phk was nice enough to only blow away your boot blocks instead of your disk label too. :) Swap currently uses all but the first page (4k on i386). Argl, YES, swap _is_ the first partition: Yes same here! Does that mean I have to rearranged or never build world again? Yeah good question, what can we do ? regards, flo ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: RAID controller problem on Digital Server 5305
On Friday 01 August 2003 17:55, you wrote: Hi, I have tried what you suggest and it asks to insert a disk for addition modules BUT when I press enter it says it cant find any floppy drives, but I just boot the setup from the floppy drive. Any ideas? Thanks Anthony I remember having problems with this, but I can't remember what I did to fix them. It's probably easiest just to boot off a cdrom, if that's possible for you. Download the 'cdboot.iso' image via ftp from current.freebsd.org/pub/FreeBSD/snapshots/alpha/ISO-IMAGES/, burn it to a cd, and then 'boot dka500' (or similar, see the 'show dev' output from the SRM prompt), should boot off the cd with no problems. CD installs are *far* easier on on Alpha, to the point that floppy-boot installs have been deprectated in 5.1-CURRENT as of a few weeks ago. You could also boot off a floppy and load the mlx module from a cd, I suppose, but I've not tried that. -Adam ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: bootstrapping network (bcm) on Dell D800
On Wed, 6 Aug 2003, David Gilbert wrote: Andre == Andre Guibert de Bruet [EMAIL PROTECTED] writes: Andre On Tue, 5 Aug 2003, Dr. Richard E. Hawkins wrote: If I'm reading the recent messages correctly, the bcm driver won't work unless updated to approximately July 17. I burned 5.1 iso's, and installed most of it successfully. How do I bootstrap the network. I saw Bill Paul's references to testing a patch prior to committing it. Is this something I can apply singly to the source that comes on the ISO (and if so, just where do I grab it?), and then build a kernel, reboot, and update the rest of the source? Andre Does this new toy have a 32-bit pci slot available? If so, pop Andre in a nic (temporarily), cvsup and/or grab the needed patches Andre and rebuild away! It has a mini-pci slot. You'd have a hard time getting an ethernet card in there. Having just had a look at the patch, it's a little large to be typing in by hand. Actually, you can get mini-pci wireless and wired nics. When I first posted, I didn't realize that the machine in question was a Latitude D800. Popping in a nic would require dismantling the unit, which you probably don't want to do... :-) Here's the options I see for you: 1) the D800 has a serial port (rare on today's laptops). Hook up a modem or a null serial cable and network thusly to cvsup. I'm under the impression that pretty much all of the 8xx-series Latitudes have DB9 ports (Including C800, C820 and friends). 2) the D800 has a pccard slot. Find someone with a wireless or ethernet card. 3) the D800 has usb2 and firewire... both of which can have ethernet 4) if you remove your hard drive, you can cheaply get a dodad that will convert the mini ide connector to a regular one. 5) burn a CD or a DVD on another machine with the new src tree. Regards, Andre Guibert de Bruet | Enterprise Software Consultant Silicon Landmark, LLC. | http://siliconlandmark.com/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Memory modified after free / most recently used by GEOM
H. Can you look at the contents of memory starting at
0xc13f7600 and going to 0xc13f7600 + 252 bytes? If GEOM is the offender
then maybe phk can more easily recognize what could possibly be trashing
a freed malloc()'d buffer 252-bytes in size.
Sorry for the top-post.
-Bosko
On Wed, Aug 06, 2003 at 12:27:22PM +1000, Tim Robbins wrote:
While trying to reproduce the wdrain problems ru@ reported in the MSDOSFS
woes thread, I kept running into this panic. I've also seen a similar one
but didn't keep the vmcore for it where a LOR is detected between Giant and
filedesc, then a page fault occurs. The backtrace for that one shows that the
fault occurred in the file desc code, and traces down to an ioctl() syscall
issued by the shell (ksh).
Kernel is trimmed down -current as of ~13:30 GMT on Aug 5 w/ obsolete drivers
(pcvt, gsc, etc.) deleted, but with no other significant changes.
Memory modified after free 0xc13f7600(252)
panic: Most recently used by GEOM
panic: from debugger
Uptime: 5m33s
Dumping 64 MB
ata0: resetting devices ..
done
16 32 48
---
#0 doadump () at /home/tim/p4/freebsd/sys/kern/kern_shutdown.c:240
240 dumping++;
(kgdb) bt
#0 doadump () at /home/tim/p4/freebsd/sys/kern/kern_shutdown.c:240
#1 0xc01a19ac in boot (howto=260) at
/home/tim/p4/freebsd/sys/kern/kern_shutdown.c:372
#2 0xc01a1d37 in panic () at
/home/tim/p4/freebsd/sys/kern/kern_shutdown.c:550
#3 0xc0127042 in db_panic () at /home/tim/p4/freebsd/sys/ddb/db_command.c:450
#4 0xc0126fa2 in db_command (last_cmdp=0xc031f780, cmd_table=0x0,
aux_cmd_tablep=0xc02fadc0, aux_cmd_tablep_end=0xc02fadc4)
at /home/tim/p4/freebsd/sys/ddb/db_command.c:346
#5 0xc01270e5 in db_command_loop () at
/home/tim/p4/freebsd/sys/ddb/db_command.c:472
#6 0xc012a0e5 in db_trap (type=3, code=0) at
/home/tim/p4/freebsd/sys/ddb/db_trap.c:73
#7 0xc02b23ec in kdb_trap (type=3, code=0, regs=0xc5f69b68) at
/home/tim/p4/freebsd/sys/i386/i386/db_interface.c:172
#8 0xc02c2eda in trap (frame=
{tf_fs = 24, tf_es = 16, tf_ds = 16, tf_edi = 1, tf_esi = -1070640529,
tf_ebp = -973694028, tf_isp = -973694060, tf_ebx = 0, tf_edx = 0, tf_ecx = 32,
tf_eax = 18, tf_trapno = 3, tf_err = 0, tf_eip = -1070913874, tf_cs = 8,
tf_eflags = 646, tf_esp = -1070632808, tf_ss = -1070709550}) at
/home/tim/p4/freebsd/sys/i386/i386/trap.c:580
#9 0xc02b3de8 in calltrap () at {standard input}:102
#10 0xc01a1cc5 in panic (fmt=0xc02f526f Most recently used by %s\n) at
/home/tim/p4/freebsd/sys/kern/kern_shutdown.c:534
#11 0xc0292c5d in mtrash_ctor (mem=0xc13f7600, size=0, arg=0x0) at
/home/tim/p4/freebsd/sys/vm/uma_dbg.c:137
#12 0xc0291434 in uma_zalloc_arg (zone=0xc083ab60, udata=0x0, flags=2) at
/home/tim/p4/freebsd/sys/vm/uma_core.c:1385
#13 0xc0196463 in malloc (size=3229854560, type=0xc0305560, flags=2) at
/home/tim/p4/freebsd/sys/vm/uma.h:229
#14 0xc0184cea in fdcopy (fdp=0xc1218200) at
/home/tim/p4/freebsd/sys/kern/kern_descrip.c:1309
#15 0xc018de0e in fork1 (td=0xc0a0d390, flags=20, pages=0, procp=0xc5f69cd8)
at /home/tim/p4/freebsd/sys/kern/kern_fork.c:424
#16 0xc018d61b in fork (td=0xc0a0d390, uap=0xc5f69d10) at
/home/tim/p4/freebsd/sys/kern/kern_fork.c:102
#17 0xc02c37c3 in syscall (frame=
{tf_fs = 47, tf_es = 47, tf_ds = 47, tf_edi = 0, tf_esi = 135299072,
tf_ebp = -1077937224, tf_isp = -973693580, tf_ebx = 0, tf_edx = 135295016,
tf_ecx = -1, tf_eax = 2, tf_trapno = 12, tf_err = 2, tf_eip = 134725423, tf_cs
= 31, tf_eflags = 582, tf_esp = -1077937268, tf_ss = 47}) at
/home/tim/p4/freebsd/sys/i386/i386/trap.c:1008
#18 0xc02b3e3d in Xint0x80_syscall () at {standard input}:144
---Can't read userspace from dump, or kernel process---
--
Bosko Milekic * [EMAIL PROTECTED] * [EMAIL PROTECTED]
TECHNOkRATIS Consulting Services * http://www.technokratis.com/
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Specifying default alternate sound device?
On 2003-08-05 13:17 -0400, Mathew Kanner wrote: On Aug 05, Adam wrote: Is there any easy way to specify a default alternate sound device (eg, /dev/dsp1). I have both onboard sound (/dev/dsp) and a SB Live card (/dev/dsp1), but I don't use the onboard sound. It's really frustrating to try to configure every single application (that uses sound) to use /dev/dsp1 instead. Is there some safe/easy trick to set a general rule that all/most apps will follow, so that they use /dev/dsp1 instead? With devfs, the default sound unit is tunable by a sysctl. tube# sysctl hw.snd.unit=0 ; ls -l dsp dsp0.0 dsp1.0 ; sysctl hw.snd.unit=1 ; ls -l dsp dsp0.0 dsp1.0 hw.snd.unit: 1 - 0 crw-rw-rw- 1 root wheel 30, 3 Aug 5 11:24 dsp crw-rw-rw- 1 root wheel 30, 3 Aug 5 11:24 dsp0.0 crw-rw-rw- 1 root wheel 30, 19 Aug 5 11:24 dsp1.0 hw.snd.unit: 0 - 1 crw-rw-rw- 1 root wheel 30, 19 Aug 5 11:24 dsp crw-rw-rw- 1 root wheel 30, 3 Aug 5 11:24 dsp0.0 crw-rw-rw- 1 root wheel 30, 19 Aug 5 11:24 dsp1.0 --Mat -- sig machine broken. Besides this solution, you could just turn off onboard sound in the BIOS. -- Munish Chopra ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
ML370 crash
Hi All, I have a Compaq ML370 that freezes during 5.1-RELEASE boot, I tryed the default boot, single user boot and disable ACPI boot. I installed 4.8-RELEASE and then upgraded to CURRENT, make buildworld and buildkernel was perfect, after make installkernel, I made a copy of /sys/i386/conf/GENERIC.hints to /boot/device.hints and the command ran ok too, but when booting with new kernel (/boot/kernel/kernel), the server freeze's at same point, after kernel display vga0 device, but now with an error message and a prompt to an debugger. Follow in attached an dmesg from 4.8-RELEASE that is working and a picture off machine's display at crash moment. Some Idea ?! Best Regards, Alexandre Biancalana Copyright (c) 1992-2003 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 4.8-RELEASE #0: Thu Apr 3 10:53:38 GMT 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC Timecounter i8254 frequency 1193182 Hz CPU: Intel Pentium III (731.02-MHz 686-class CPU) Origin = GenuineIntel Id = 0x683 Stepping = 3 Features=0x383fbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE real memory = 1073725440 (1048560K bytes) avail memory = 1039876096 (1015504K bytes) Preloaded elf kernel kernel at 0xc051d000. Pentium Pro MTRR support enabled md0: Malloc disk npx0: math processor on motherboard npx0: INT 16 interface pcib0: ServerWorks NB6635 3.0LE host to PCI bridge on motherboard pci0: PCI bus on pcib0 sym0: 1510d port 0x2000-0x20ff mem 0xc6efe000-0xc6efefff,0xc6effc00-0xc6ef irq 11 at device 1.0 on pci0 sym0: No NVRAM, ID 7, Fast-40, LVD, parity checking sym1: 1510d port 0x2400-0x24ff mem 0xc6efc000-0xc6efcfff,0xc6efdc00-0xc6efdfff irq 15 at device 1.1 on pci0 sym1: No NVRAM, ID 7, Fast-40, LVD, parity checking fxp0: Intel Pro 10/100B/100+ Ethernet port 0x2800-0x283f mem 0xc6d0-0xc6df,0xc6efb000-0xc6efbfff irq 5 at device 2.0 on pci0 fxp0: Ethernet address 00:50:8b:de:72:26 inphy0: i82555 10/100 media interface on miibus0 inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto pci0: ATI Mach64-GV graphics accelerator at 3.0 pci0: unknown card (vendor=0x0e11, dev=0xa0f0) at 4.0 xl0: 3Com 3c905B-TX Fast Etherlink XL port 0x3000-0x307f mem 0xc6cfee80-0xc6cfeeff irq 5 at device 5.0 on pci0 xl0: Ethernet address: 00:10:4b:c6:38:24 miibus1: MII bus on xl0 xlphy0: 3Com internal media interface on miibus1 xlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto isab0: ServerWorks IB6566 PCI to ISA bridge at device 15.0 on pci0 isa0: ISA bus on isab0 atapci0: ServerWorks ROSB4 ATA33 controller port 0x3080-0x308f at device 15.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 pcib3: ServerWorks NB6635 3.0LE host to PCI bridge on motherboard pci3: PCI bus on pcib3 ida0: Compaq Smart Array 431 controller port 0x4000-0x40ff mem 0xc6fff000-0xc6ff irq 10 at device 3.0 on pci3 ida0: drives=2 firm_rev=1.02 idad0: Compaq Logical Drive on ida0 idad0: 17359MB (35553120 sectors), blocksize=512 idad1: Compaq Logical Drive on ida0 idad1: 17359MB (35553120 sectors), blocksize=512 eisa0: EISA bus on motherboard mainboard0: CPQ0690 (System Board) on eisa0 slot 0 orm0: Option ROMs at iomem 0xc-0xc7fff,0xc8000-0xcbfff,0xe8000-0xedfff,0xee000-0xe on isa0 fdc0: NEC 72065B or clone at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: 1440-KB 3.5 drive on fdc0 drive 0 atkbdc0: Keyboard controller (i8042) at port 0x60,0x64 on isa0 atkbd0: AT Keyboard flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on isa0 sc0: System console at flags 0x100 on isa0 sc0: VGA 16 virtual consoles, flags=0x300 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A ppc0: Parallel port at port 0x378-0x37f irq 7 on isa0 ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode plip0: PLIP network interface on ppbus0 lpt0: Printer on ppbus0 lpt0: Interrupt-driven port ppi0: Parallel I/O on ppbus0 ata0-slave: ATAPI identify retries exceeded acd0: CDROM COMPAQ CDR-8435 at ata0-master PIO4 Waiting 15 seconds for SCSI devices to settle Mounting root from ufs:/dev/idad0s2a ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
[Fwd: cvs commit: src/sys/i386/i386 pmap.c]
If your i386 system has panic()ed in pmap_remove_all() recently, I would encourage you to update your pmap.c. Regards, Alan---BeginMessage--- alc 2003/08/06 11:46:48 PDT FreeBSD src repository Modified files: sys/i386/i386pmap.c Log: Acquire the page queues lock in pmap_insert_entry(). (I used to believe that the page's busy flag could be relied upon to synchronize access to the pv list. I don't any longer. See, for example, the call to pmap_insert_entry() from pmap_copy().) Revision ChangesPath 1.422 +2 -0 src/sys/i386/i386/pmap.c ---End Message--- ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Troubles while mounting ext2 from 5.1-RELEASE
Hello, after digging the various mailing-lists, release notes, errata and Google, I thought I might get some help here. I have just installed a FreeBSD 5.1-RELEASE on my x86 laptop. Everything works like a charm, including DRI, except mounting ext2 : # mount -t ext2fs /dev/ad0s2 /mnt/linux ext2fs: /dev/ad0s2: No such file or directory # ll /dev/ad0s2 crw-r- 1 root operator4, 12 Aug 6 17:14 /dev/ad0s2 # ll -d /mnt/linux drwxr-xr-x 2 root wheel 512 Aug 5 17:16 /mnt/linux # fdisk /dev/ad0 [...] The data for partition 2 is: sysid 131 (0x83),(Linux native) start 996030, size 46877670 (22889 Meg), flag 0 beg: cyl 988/ head 2/ sector 1; end: cyl 1023/ head 11/ sector 63 dmesg and /var/log/messages are mute. I've found this kind of report in the recent archives but it was never answered. How could I interpret this error message ? Other information : the ext2 partition was formated with mke2fs by a Debian 3.0 (Woody) installer running Linux 2.2.20. Here is some output from dumpe2fs under Linux : $ dumpe2fs /dev/hda2 Filesystem volume name: none Last mounted on: not available Filesystem UUID: none Filesystem magic number: 0xEF53 Filesystem revision #:1 (dynamic) Filesystem features: filetype sparse_super Default mount options:(none) Filesystem state: not clean Errors behavior: Continue Filesystem OS type: Linux Inode count: 2932736 Block count: 5859708 Reserved block count: 292985 Free blocks: 5364944 Free inodes: 2847765 First block: 0 Block size: 4096 Fragment size:4096 Blocks per group: 32768 Fragments per group: 32768 Inodes per group: 16384 Inode blocks per group: 512 Last mount time: Wed Aug 6 16:53:27 2003 Last write time: Wed Aug 6 17:01:48 2003 Mount count: 13 Maximum mount count: 25 Last checked: Sun Aug 3 20:24:37 2003 Check interval: 15552000 (6 months) Next check after: Fri Jan 30 19:24:37 2004 Reserved blocks uid: 0 (user root) Reserved blocks gid: 0 (group root) First inode: 11 Inode size: 128 [...] Thanks for any hint, Vincent. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
ACPI battery state and resume not working on Inspiron 5150
I've read a lot of the recent Dell Inspiron posts on current@, and even tried the Dell AML patch (doesn't apply on the 5150, Stijn). Most things seems to be working for ACPI except for battery status and suspend/resume (the laptop suspends, but never comes back). Here is what dmesg reports for ACPI: FreeBSD 5.1-CURRENT #14: Mon Aug 4 18:11:11 EDT 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GYROS acpi0: DELL MwoodNwd on motherboard pcibios: BIOS version 2.10 Using $PIR table, 9 entries at 0xc00fdf30 ACPI-1287: *** Error: Method execution failed [\\_SB_.PCI0.LPCB.BAT1._STA] (Node 0xc6137640), AE_NOT_EXIST acpi0: power button is handled as a fixed feature programming model. Timecounter ACPI-fast frequency 3579545 Hz ACPI-1287: *** Error: Method execution failed [\\_SB_.PCI0.LPCB.BAT1._STA] (Node 0xc6137640), AE_NOT_EXIST acpi_timer0: 24-bit timer at 3.579545MHz port 0x1008-0x100b on acpi0 acpi_cpu0: CPU on acpi0 acpi_cpu1: CPU on acpi0 acpi_tz0: thermal zone on acpi0 acpi_button0: Power Button on acpi0 acpi_button1: Sleep Button on acpi0 acpi_lid0: Control Method Lid Switch on acpi0 If anyone has some suggestions, I'd be happy to hear them. I realize more info may be required, so if you're interested, I'll gladly send you what you need. Thanks. Joe -- PGP Key : http://www.marcuscom.com/pgp.asc signature.asc Description: This is a digitally signed message part
Re: ACPI battery state and resume not working on Inspiron 5150
On Wed, 2003-08-06 at 15:56, Barney Wolff wrote: On Wed, Aug 06, 2003 at 03:31:01PM -0400, Joe Marcus Clarke wrote: ACPI-1287: *** Error: Method execution failed [\\_SB_.PCI0.LPCB.BAT1._STA] (Node 0xc6137640), AE_NOT_EXIST I would not expect BAT1 to exist unless you have 2 batteries installed. Ah, good point. However, I don't see any battery sysctls, and I do have at least one battery installed. As to resume, on my I5000 it takes almost a minute to come back from S3, but does eventually come back on a -current from 7/30. Thanks for the suggestion. I'll wait a bit longer. Joe -- PGP Key : http://www.marcuscom.com/pgp.asc signature.asc Description: This is a digitally signed message part
Re: ACPI battery state and resume not working on Inspiron 5150
On Wed, Aug 06, 2003 at 03:31:01PM -0400, Joe Marcus Clarke wrote: ACPI-1287: *** Error: Method execution failed [\\_SB_.PCI0.LPCB.BAT1._STA] (Node 0xc6137640), AE_NOT_EXIST I would not expect BAT1 to exist unless you have 2 batteries installed. As to resume, on my I5000 it takes almost a minute to come back from S3, but does eventually come back on a -current from 7/30. -- Barney Wolff http://www.databus.com/bwresume.pdf I'm available by contract or FT, in the NYC metro area or via the 'Net. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: gcc ABI compliance (was: Re: Memory Mangement Problem in5.1-RELEASE)
On Sat, 26 Jul 2003, Alexander Leidinger wrote: On Fri, 25 Jul 2003 23:22:00 -0700 Terry Lambert [EMAIL PROTECTED] wrote: Didn't the GNU people say they had to change it to be more ABI compliant with the 'standard'? I will believe that when they upgrade their FORTRAN compiler to be more compliant with 'the standard'. Some standards are not worth complying with; I still have yet to see anyone tell me exactly what the practical benefit of doing this is. When X (X 1) compilers comply to the same ABI standard, I can mix the results of those compilers (if I see a benefit to do so). As we have icc in the ports collection and the base system is compiled with gcc and I want to be able to link to gcc compiled libs with icc, I appreciate the effort of the involved parties to try to comply to a common ABI standard. That might be so over in your reality, but over in this really there is tonns of paisn due to the changes and changing libstdc++.so major. Lets not get into promises about ABI stability Bye, Alexander. -- I believe the technical term is Oops! http://www.Leidinger.net Alexander @ Leidinger.net GPG fingerprint = C518 BC70 E67F 143F BE91 3365 79E2 9C60 B006 3FE7 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ath0 driver
On Wed, 6 Aug 2003, Sam Leffler wrote: Verify you have the latest HAL using sysctl hw.ath The version should be 0.9.5.3 or better (can't remember if I committed .4 or .3). Shouldn't that be 0.9.5.2? I run the latest current, and hw.ath.hal.version is 0.9.5.2. regards, le -- Lukas Ertl eMail: [EMAIL PROTECTED] UNIX Systemadministrator Tel.: (+43 1) 4277-14073 Vienna University Computer Center Fax.: (+43 1) 4277-9140 University of Vienna http://mailbox.univie.ac.at/~le/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: td-td_kstack spam
On Wed, Aug 06, 2003 at 04:00:14PM -0700, Kris Kennaway wrote: Booting a new kernel I get: FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): apic id: 1, version: 0x00040011, at 0xfee0 cpu1 (AP): apic id: 0, version: 0x00040011, at 0xfee0 io0 (APIC): apic id: 2, version: 0x000f0011, at 0xfec0 io1 (APIC): apic id: 3, version: 0x000f0011, at 0xfec01000 td-td_kstack = 0xdf111000 Oops, it turns out this was the result of a debugging patch someone had given me to try and track down the panic problems I was having on bento (turned out to be due to broken KSTACK_PAGES support). kris pgp0.pgp Description: PGP signature
Re: Bootstrap: Machine keeps booting ? (boot0/mbr) ?
On Wed, 6 Aug 2003, Stephan van Beerschoten wrote: I installed the Bootloader for my dualboot machine, and when it comes up during boot: F1 ?? F2 FreeBSD and I press F2, it autmatically reboots again. Please note it DID work yesterday, but somehow my laptops keeps booting on my now. (-CURRENT ? why?) You probably have your swap partition as the first partition on your drive. Boot up to a fixit floppy and rewrite your boot blocks. Then re-cvsup to the very latest current, phk@ has already fixed this problem. regards, le -- Lukas Ertl eMail: [EMAIL PROTECTED] UNIX Systemadministrator Tel.: (+43 1) 4277-14073 Vienna University Computer Center Fax.: (+43 1) 4277-9140 University of Vienna http://mailbox.univie.ac.at/~le/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
ipfw - default to accept + bootp = confusion.
Does someone have any idea what approach to take for the following scenario? I'm leaning towards a compile time failure, or an informative panic at the beginning of bootp... You have IPFIREWALL, but not the default to accept option, and you have BOOTP. The BOOTP stuff will fail in sosend with EACCESS (informatively printed as 13), because of IPFW, and this may be slightly non-obvious to people who haven't dealt with early ipfw interference before. If not compile time failure / panic, I'd say probably we want some way to notify a user in general of ipfw stopping pre-init operation, but I don't want to add the concept of runlevels, and don't know if there's anything there currently to do detection of if we've hit that point yet. Thanx, juli. -- juli mallett [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
help! 5.1 doesn't do the rc thing?
OMG. I did it (the 5.1 update), and it went flawlessly until the reboot. I read /usr/src/UPDATING! It said that the old rc system was going away, but it would keep all your old files. So anyways, does anyone have a link to info about how the heck I start stuff in 5.1? Most important: -my lo0 interface doesn't have the 127.0.0.1 address.. it just comes up with no addy. -rc.conf didn't get run :( no named, no nothing :( -my firewall rules (rc.firewall) and sysctl.conf didn't seem to be read. Links, hints appreciated. --Charlie ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
