loader can't load kernel on FreeBSD 6.1-p6.
Hi, folks. While booting 6.1-RELEASE-p6 i have this error on /boot/loader stage: can't load kernel ls shows nothing... lsdev shows me: disk devices: disk0: BIOS drive C: disk0s1: FFS bad disklabel But when i am booting from LiveCD i see all my labels, i can mount them, i can produce read/write operations. Other thing that confused me is that when i am using second stage bootstrap file i see my root partition: FreeBSD/i386 BOOT Default: 0:ad(0,a)/boot/loader boot: ?. .. .snap bin boot dev etc lib libexec mnt proc and so on... But when i am trying to boot kernel (GENERIC) directly from bootstrap i have BTX halted error, don't know if this actually supported. World was builded on other box and installed to this drive using tar. Here is additional information that i can get from LiveCD: [EMAIL PROTECTED]:~# fdisk /dev/ad0 *** Working on device /dev/ad0 *** parameters extracted from in-core disklabel are: cylinders=19679 heads=16 sectors/track=255 (4080 blks/cyl) Figures below won't work with BIOS for partitions not in cyl 1 parameters to be used for BIOS calculations are: cylinders=19679 heads=16 sectors/track=255 (4080 blks/cyl) Media sector size is 512 Warning: BIOS sector numbering starts with sector 1 Information from DOS bootblock is: The data for partition 1 is: sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD) start 63, size 80293185 (39205 Meg), flag 80 (active) beg: cyl 0/ head 1/ sector 1; end: cyl 807/ head 15/ sector 63 The data for partition 2 is: UNUSED The data for partition 3 is: UNUSED The data for partition 4 is: UNUSED [EMAIL PROTECTED]:~# disklabel /dev/ad0s1 # /dev/ad0s1: 8 partitions: #size offsetfstype [fsize bsize bps/cpg] a: 52428804.2BSD 2048 16384 32776 b: 4161280 524288 swap c: 802931850unused0 0 # raw part, don't edit d: 2097152 46855684.2BSD 2048 16384 28552 e: 20971520 67827204.2BSD 2048 16384 28552 f: 10485760 277542404.2BSD 2048 16384 28552 g: 42053185 38244.2BSD 2048 16384 28552 [EMAIL PROTECTED]:~# atacontrol list ATA channel 0: Master: ad0 Maxtor 6E040L0/NAR61590 ATA/ATAPI revision 7 Slave: no device present ATA channel 1: Master: no device present Slave: no device present [EMAIL PROTECTED]:~# mount /dev/iso9660/FreeSBIE on / (cd9660, local, read-only) devfs on /dev (devfs, local) /dev/md0.uzip on /usr (ufs, local, read-only) /dev/md1 on /etc (ufs, local) /dev/md2 on /usr/local/etc (ufs, local) /dev/md3 on /root (ufs, local) /dev/md4 on /var (ufs, local) /dev/md5 on /tmp (ufs, local) /dev/ad0s1a on /mnt/ufs.1 (ufs, local, read-only) /dev/ad0s1d on /mnt/ufs.2 (ufs, local, read-only) /dev/ad0s1e on /mnt/ufs.3 (ufs, local, read-only) /dev/ad0s1f on /mnt/ufs.4 (ufs, local, read-only) /dev/ad0s1g on /mnt/ufs.5 (ufs, local, read-only) [EMAIL PROTECTED]:~# ls -al /mnt/ufs.1/boot/ total 588 drwxr-xr-x 5 root wheel 512 Sep 16 00:52 . drwxr-xr-x 20 root wheel 512 Sep 15 10:05 .. -r--r--r-- 1 root wheel7638 Sep 6 18:43 beastie.4th -r--r--r-- 1 root wheel8192 Sep 6 18:43 boot -r--r--r-- 1 root wheel 512 Sep 6 18:43 boot0 -r--r--r-- 1 root wheel 512 Sep 6 18:43 boot0sio -r--r--r-- 1 root wheel 512 Sep 6 18:43 boot1 -r--r--r-- 1 root wheel7680 Sep 6 18:43 boot2 -r--r--r-- 1 root wheel1200 Sep 6 18:43 cdboot drwxr-xr-x 2 root wheel 512 Sep 6 18:43 defaults -r--r--r-- 1 root wheel1741 Sep 6 18:43 device.hints -r--r--r-- 1 root wheel2249 Sep 6 18:43 frames.4th drwxr-xr-x 2 root wheel9216 Sep 6 18:44 kernel -r-xr-xr-x 1 root wheel 212992 Sep 6 18:43 loader -r--r--r-- 1 root wheel7772 Sep 6 18:43 loader.4th -rw-r--r-- 1 root wheel 463 Sep 6 18:44 loader.conf -r--r--r-- 1 root wheel 15058 Sep 6 18:43 loader.help -r--r--r-- 1 root wheel 389 Sep 6 18:43 loader.rc -r--r--r-- 1 root wheel 512 Sep 6 18:43 mbr drwxr-xr-x 2 root wheel 512 Sep 6 18:41 modules -r--r--r-- 1 root wheel 215040 Sep 6 18:43 pxeboot -r--r--r-- 1 root wheel 692 Sep 6 18:43 screen.4th -r--r--r-- 1 root wheel 36440 Sep 6 18:43 support.4th [EMAIL PROTECTED]:~# ls -al /mnt/ufs.1/boot/kernel/kernel -r-xr-xr-x 1 root wheel 6640118 Sep 6 18:21 /mnt/ufs.1/boot/kernel/kernel [EMAIL PROTECTED]:~# file /mnt/ufs.1/boot/kernel/kernel /mnt/ufs.1/boot/kernel/kernel: ELF 32-bit LSB executable, Intel 80386, version 1 (FreeBSD), dynamically linked (uses shared libs), not stripped -- = = Best regards, Nikolay Pavlov. = = ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To
Re: ARRRRGH! Guys, who's breaking -STABLE's GMIRROR code?!
Hans Lambermont wrote: Julian H. Stacey wrote: Stable is a misnomer that harms FreeBSD somewhat. Why not rename 'stable' into 'stable-api' ? Nice, an improvement on what we have :-) If enough agree, the name of this mail list could be changed for a start. -- Julian Stacey. BSD Unix C Net Consultancy, Munich/Muenchen http://berklix.com Mail Ascii, not HTML. Ihr Rauch = mein allergischer Kopfschmerz. Don't buy it ! Get it free ! http://berklix.org/free-software ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: em0: watchdog timeout -- resetting (6.1-STABLE)
Hello, Just wanted to send a me too on this issue. Whenever it happends I can see our Cisco switch reporting the interface going down and up as well (Line Protocol). FreeBSD localhost.localdomain 6.2-PRERELEASE FreeBSD 6.2-PRERELEASE #1: Wed Sep 13 00:10:04 CEST 2006 [EMAIL PROTECTED]:/ usr/obj/usr/src/sys/PT i386 em0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 options=bRXCSUM,TXCSUM,VLAN_MTU media: Ethernet autoselect (1000baseTX full-duplex) status: active [EMAIL PROTECTED]:11:0: class=0x02 card=0x10048086 chip=0x10048086 rev=0x02 hdr=0x00 vendor = 'Intel Corporation' device = '82543GC Gigabit Ethernet Controller (Copper)' class= network subclass = ethernet (This is a add-in 64bit PCI card.) I am stress-testing -STABLE on a spare server to aid in making 6.2 as bugfree as possible. It is set up as a NFS server with two Linux NFS clients connected that is concurrently extracting 5 copies of /usr/src to it, and running a program that creates millions of files with random UID's to test for QUOTA issues. On the server I repeatedly dump the exported filesystem with snapshot and cache enabled. (dump -L -C 32 -af /dev/null ...) I'm building todays -STABLE on a different server with SMP and two em NIC's onboard, and will start similar tests on it to see if I can reproduce the watchdog timeouts there as well. -- Frode Nordahl ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: amd64/101873: Freebsd amd64 hangs on booting sata drive?
David wrote: I attempted to do a test install of FreeBSD 6.1 ISO on a new machine I was building, the specs were: *AMD AM2 5000+ dual core *Asus M2N32-SLI Deluxe Motherboard *1GBx4 Mushkin ddr2 800Mhz *750GBx4 S-ATA Seagate Barracuda Hard Drive (Tested with and without motherboard NV RAID in 0+1 mode with the same results) *ATI Radeon 1800 video card *standard dvd-rom When attempting to boot in verbose and non verbose mode the machine would hang (to the best of what I recall) on the hard drives. Audit-Trail: From: Frank Reppin [EMAIL PROTECTED] I've had the same experience with my brand new and shiny amd64 equipmnent...: Mainboard - ASUS M2N-E (nforce 570 - *no* SLI) Both 7.0-CURRENT-200607 and 6.1-STABLE-200607 (july) snapshots failed. The 7.0-CURRENT-200608 passed the disk probes, and indeed finished the install, but was subject to a massive interrupt storm. As of today (2006-sep-16) the problem is solved in both 7-CURRENT and 6-STABLE (soon to be 6.2-RELEASE), I verified personally with 2 home-built snapshot CDROMs. I think this PR can be closed (FIXED). http://www.freebsd.org/cgi/query-pr.cgi?pr=101873 Angelo Turetta ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: final message in buildworld as there is in buildkernel
Oliver Fromme wrote: martinko [EMAIL PROTECTED] wrote: i've been wondering why there is no footer in buildworld Because it's not necessary. When you see your shell prompt again, you know that it's finished. And if there's no error message or exit code != 0, ithas finished successfully. Also, historically the sendmail build is always the last part of buildworld (and installworld), so it's easy to recognize. Best regards Oliver well, i still think it's not clear enough. and you don't really want users to investigate what the exit status was, do you. (also not many know about sendmail i believe.) anyway, we've got it with buildkernel and i can't see any reason why not to have it with buildworld. well, i'm not a hacker and this is not something i can decide. i just thought it'd be a good idea and that it'd help freebsd users. cheers, martin ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ARRRRGH! Guys, who's breaking -STABLE's GMIRROR code?!
On Fri, Sep 15, 2006 at 03:41:04PM -0300, Marc G. Fournier wrote: But, I'm just curious here ... for all of the talk going around about this whole issue, how many ppl have truly ever been bitten by an unstable -STABLE? And for those that have, how long did it take to get help from a developer to get it fixed? I run -STABLE on a number of production machines. I have twice been bitten by an unstable -STABLE -- but bitten in a very small way. When we build a new -STABLE (on average perhaps once per month), we build it on a test machine, so that we can be sure that it actually works. Once it is tested and we know it works, then we can roll it out to the production machines without undue concern. I note that we follow the same process with out Linux machines, our Irix machines, and our Windows machines. Blindly rolling out updates or patches to critical production machines is unwise and dangerous (at least IMO). I will add that I have never even needed to contact a maintainer. When there has been a problem, I checked the lists. In one case the fix was already committed, in the other there was already an I'm working on it message and a fix was commited in less than 24 hours. In the interim, my test machine had a problem -- but that's what a test machine is for. In the case that started this thread, it seems to be that the developer fixed his mistake fairly quickly, which is what one would expect ... it shouldn't be so much that he *broke* -STABLE (shit happens, do you want your money back?), but it should be 'was he around to reverse his mistake in a reasonable amount of time?' ... ? Exactly. -- greg byshenk - [EMAIL PROTECTED] - Leiden, NL ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: iSCSI HBAs
Matthew Jacob wrote: Why do you think an iSCSI HBA would be of any benefit to anything other than the target mode side as a server? Mostly for deploying servers that are diskless, quickly. No need to depend on another server (other than the iSCSI target) to get servers up without a lot of fusing around. Diskless + the software initiator seems like a lot of fusing around to get one server up. I mean I could be wrong, I'm not really sure how the FreeBSD software initiator works or if it's actual optimized and stable. If it's as easy as setting up a DHCP and TFTP server just to boot the kernel, then mount the iSCSI volume, that might be an option. But right now, if an iSCSI HBA driver was available it might be the more reliable way to go. Again, I could be way off base. We use FreeBSD in all of our server clusters now, most via RAID1 mirrors on every server, I'd like to stay with FreeBSD, but sometimes it's lack of support for new server beneficial drivers make that choice hard to make. -- Robert Blayzor, BOFH INOC, LLC rblayzor\@(inoc.net|gmail.com) PGP: 0x66F90BFC @ http://pgp.mit.edu Key fingerprint = 6296 F715 038B 44C1 2720 292A 8580 500E 66F9 0BFC One picture is worth 128K words. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: iSCSI HBAs
Matthew Jacob wrote: Why do you think an iSCSI HBA would be of any benefit to anything other than the target mode side as a server? Mostly for deploying servers that are diskless, quickly. No need to depend on another server (other than the iSCSI target) to get servers up without a lot of fusing around. Diskless + the software initiator seems like a lot of fusing around to get one server up. I mean I could be wrong, I'm not really sure how the FreeBSD software initiator works or if it's actual optimized and stable. If it's as easy as setting up a DHCP and TFTP server just to boot the kernel, then mount the iSCSI volume, that might be an option. But right now, if an iSCSI HBA driver was available it might be the more reliable way to go. Again, I could be way off base. We use FreeBSD in all of our server clusters now, most via RAID1 mirrors on every server, I'd like to stay with FreeBSD, but sometimes it's lack of support for new server beneficial drivers make that choice hard to make. we have been running diskless clients for a few hundred work stations, so i think i have some experience :-) 1- setting a diskless freebsd is far easier than linux 2- it's by far much easier to manage. btw, the majority of ws are running linux. being involved with the iSCSI initiator for FreeBSD, I can't see where this can help for a diskless host, or in other words, what's wrong with NFS? also, the TOE cards are not that cheep either :-) my 2c, danny ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
ERROR: StepTime does not match Avc 900. Please Report this.
FreeBSD 6.2-PRERELEASE #10: Sat Sep 16 04:13:37 MSD 2006 16-09-2006 16:50:01, ERROR: StepTime does not match Avc 900. Please Report this. 16-09-2006 16:50:01, ERROR: StepTime does not match Avc -600. Please Report this. 16-09-2006 16:50:01, ERROR: StepTime does not match Avc-2100. Please Report this. 16-09-2006 16:50:01, ERROR: StepTime does not match Avc-3600. Please Report this. 16-09-2006 16:50:01, ERROR: StepTime does not match Avc-5100. Please Report this. 16-09-2006 16:50:01, ERROR: StepTime does not match Avc-6600. Please Report this. 16-09-2006 16:50:01, ERROR: StepTime does not match Avc-8100. Please Report this. 16-09-2006 16:50:01, ERROR: StepTime does not match Avc-9600. Please Report this. 16-09-2006 16:50:01, ERROR: StepTime does not match Avc -11100. Please Report this. 16-09-2006 16:50:01, ERROR: StepTime does not match Avc -12600. Please Report this. 16-09-2006 16:50:01, ERROR: StepTime does not match Avc -14100. Please Report this. 16-09-2006 16:50:01, ERROR: StepTime does not match Avc -15600. Please Report this. 16-09-2006 16:50:01, ERROR: StepTime does not match Avc -17100. Please Report this. 16-09-2006 16:50:01, ERROR: StepTime does not match Avc -18600. Please Report this. 16-09-2006 16:50:01, ERROR: StepTime does not match Avc -20100. Please Report this. 16-09-2006 16:50:01, ERROR: StepTime does not match Avc -21600. Please Report this. 16-09-2006 16:50:01, ERROR: StepTime does not match Avc -23100. Please Report this. 16-09-2006 16:50:01, ERROR: StepTime does not match Avc -24600. Please Report this. 16-09-2006 16:50:01, ERROR: StepTime does not match Avc -26100. Please Report this. 16-09-2006 16:50:01, ERROR: StepTime does not match Avc -27600. Please Report this. 16-09-2006 16:50:01, ERROR: StepTime does not match Avc -29100. Please Report this. 16-09-2006 16:50:01, ERROR: StepTime does not match Avc -30600. Please Report this. 16-09-2006 16:50:01, ERROR: StepTime does not match Avc -32100. Please Report this. 16-09-2006 16:50:01, ERROR: StepTime does not match Avc -33600. Please Report this. 16-09-2006 16:50:01, ERROR: StepTime does not match Avc -35100. Please Report this. 16-09-2006 16:50:01, ERROR: StepTime does not match Avc -36600. Please Report this. . 16-09-2006 16:50:01, ERROR: StepTime does not match Avc -493200. Please Report this. 16-09-2006 16:50:01, ERROR: StepTime does not match Avc -493200. Please Report this. 16-09-2006 16:50:01, ERROR: StepTime does not match Avc -493200. Please Report this. 16-09-2006 16:50:01, ERROR: StepTime does not match Avc -493200. Please Report this. 16-09-2006 16:50:01, ERROR: StepTime does not match Avc -493200. Please Report this. 16-09-2006 16:50:01, ERROR: StepTime does not match Avc -493200. Please Report this. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: iSCSI HBAs
Danny Braniss wrote: we have been running diskless clients for a few hundred work stations, so i think i have some experience :-) 1- setting a diskless freebsd is far easier than linux 2- it's by far much easier to manage. btw, the majority of ws are running linux. being involved with the iSCSI initiator for FreeBSD, I can't see where this can help for a diskless host, or in other words, what's wrong with NFS? also, the TOE cards are not that cheep either :-) TOE cards are no more expensive than putting a RAID card and two drives in a box. Is it more expensive than native FreeBSD diskless? Sure. I'm not saying that NFS is bad, we use it all over the place. What's nice about iSCSI is you can setup servers for anything and not care what runs on the box. Thus making almost any server diskless so long as it supports the HBA. This works great when you deploy things like Plesk, etc, which don't support NFS or diskless environements. Does it run? Sure, but not without a lot of messing around. Also, if you have the one or two Windows servers you may be forced to have, you can run them diskless as well using the same iSCSI system. I agree that diskless is a nice system to consider, and it's one of our alternate choices, but we do have some applications, virtual servers, etc, which do not support running in native FreeBSD diskless fashion. -- Robert Blayzor, BOFH INOC, LLC rblayzor\@(inoc.net|gmail.com) PGP: 0x66F90BFC @ http://pgp.mit.edu Key fingerprint = 6296 F715 038B 44C1 2720 292A 8580 500E 66F9 0BFC Esc key to reboot Universe, or any other key to continue... ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ARRRRGH! Guys, who's breaking -STABLE's GMIRROR code?!
On Sat, 16 Sep 2006, Julian H. Stacey wrote: Hans Lambermont wrote: Julian H. Stacey wrote: Stable is a misnomer that harms FreeBSD somewhat. Why not rename 'stable' into 'stable-api' ? Nice, an improvement on what we have :-) If enough agree, the name of this mail list could be changed for a start. Sure, but what colour the new bikeshed? Cheers, Ian ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
panic: integer divide fault on 6.1
Hi all,
I was contacted by Chris who had the same problem.
Since I didn't follow up on my problem he asked me if it was solved
and indeed it was solved by Søren and the fix has been committed to
CURRENT:
http://lists.freebsd.org/pipermail/cvs-all/2006-September/188353.html
I'm hoping this gets MFC'ed in time for 6.2
My conversation with Søren is bellow:
-- Forwarded message --
From: Joao Barros [EMAIL PROTECTED]
Date: Sep 14, 2006 8:04 PM
Subject: Re: Fwd: panic: integer divide fault on 6.1
To: Søren Schmidt [EMAIL PROTECTED]
On 9/13/06, Joao Barros [EMAIL PROTECTED] wrote:
On 9/13/06, Søren Schmidt [EMAIL PROTECTED] wrote:
Joao Barros wrote:
-- Forwarded message --
From: Sam Leffler [EMAIL PROTECTED]
Date: Sep 10, 2006 5:16 PM
Subject: Re: panic: integer divide fault on 6.1
To: Joao Barros [EMAIL PROTECTED]
Cc: freebsd-current@freebsd.org, freebsd-stable@freebsd.org, Kris
Kennaway [EMAIL PROTECTED]
Joao Barros wrote:
On 9/9/06, Kris Kennaway [EMAIL PROTECTED] wrote:
On Sat, Sep 09, 2006 at 09:02:35PM +0100, Joao Barros wrote:
On 9/9/06, Max Laier [EMAIL PROTECTED] wrote:
Can you try to get a dump, trace, or at least figure out which
function
the IP is refering to?
Well, the problem only occurs when I boot from the disk and the
installed kernel doesn't have debug support.
Does 'set dumpdev=' work from the boot loader? I tried some
combinations with no success.
No.
I can try and install a 6-STABLE snapshot if there's no way of
getting
the info needed.
You can either try to install a new kernel with DDB support, or follow
the instruction pointer method in the developers handbook chapter on
kernel debugging.
I copied a CURRENT kernel from a 200608 snapshot and the problem also
occurs thus I'm adding [EMAIL PROTECTED]
My current laptop doesn't have a serial port so I'm copying this by
hand:
Fatal trap 18: integer divide fault while in kernel mode
cpuid = 0; apic id = 00
instruction pointer = 0x20:0xc08a1fb7
stack pointer = 0x28:0xc0c20b14
frame pointer = 0x28:0xc0c20b9c
code segment= base 0x0, limit 0xf, type 0x1b
= DPL 0, pres 1, def32 1, gran 1
processor eflags= interrupt enabled, resume, IOPL = 0
current process = 0 (swapper)
[thread pid 0 tid 0 ]
Stopped at__qdivrem+0x3b: divl%ecx,%eax
db bt
Tracing pid 0 tid0 td 0xc0a0c818
__qdivrem(37fdfa0,0,0,0,0,...) at __qdivrem+0x3b
__udivdi3(37fdfa0,0,0,0) at __udivdi3+0x16
ata_raid_promise_read_meta(c37a5000,c09f4a80,1,8086,c37a5000,...) at
ata_raid_promise_read_meta+0x9b
ata_raid_read_metadata(c37a5000,c37a5000,c0c20c70,c06b58a4,c37a5000,...)
at ata_raid_metadata+0x2be
ata_raid_subdisk_attach(c37a5000) at ata_raid_subdisk_attach+0x33
device_attach(c37a5000,c37a5180,c37a5000,c36885c0,0,...) at
device_attach+0x58
device_probe_and_attach(c37a5200,c37a5200,c08ec9a9,0,c37a5180,...) at
bus_generic_attach+0x16
ad_attach(c37a5200) at ad_attach+0x2c8
device_attach(c37a5200,c095f2d0,c37a5200,0,c368d800,...) at
device_attach+0x58
device_probe_and_attach(c37a5200) at device_probe_and_atach+0xe0
bus_generic_attach(c3659080,c3659080,,0,c37a5200,...) at
bus_generic_attach+0x16
ata_identify(c3659080) at ata_identify+0x1c8
ata_boot_attach(0xc0a11d80,0,c09212e7,47,...) at ata_boot_attach+0x3e
run_interrupt_drive_config_hooks(0,c1ec00,c1e000,0,c0451065,...) at
run_interrupt_drive_config_hooks+0x43
mi_startup() at mi_startup+0x96
begin() at begin+0x2c
This board has a Promise SATA raid controller and it is disabled in
the BIOS. I even tried disabling it through a jumper but it still
stops.
In sys/dev/ata/ata-raid.h the PROMISE_LBA macro does an unchecked
calculation that apparently can divide by zero. Soren would likely
understand the root cause of this problem but until then you can patch
the driver to workaround the problem.
Sam
Hi Søren,
I don't know if you bumped into this thread but this should definitely
be fixed.
Do you want me to open a PR?
Hmm, the problem seems to be that the geometry thats gotten from the
disk has (all) zero's in it, which we cannot handle.
Its most likely because your BIOS put invalid or no current geometry
info in the disks parameters page.
If you are up to a little debugging, you could try this patch:
diff -u -r1.189.2.4 ata-disk.c
--- ata-disk.c 4 Apr 2006 16:07:42 - 1.189.2.4
+++ ata-disk.c 13 Sep 2006 06:18:59 -
@@ -97,7 +97,8 @@
}
device_set_ivars(dev, adp);
-if (atadev-param.atavalid ATA_FLAG_54_58) {
+if ((atadev-param.atavalid ATA_FLAG_54_58)
+ atadev-param.current_heads atadev-param.current_sectors) {
adp-heads = atadev-param.current_heads;
adp-sectors = atadev-param.current_sectors;
adp-total_secs =
Re: ARRRRGH! Guys, who's breaking -STABLE's GMIRROR code?!
Ian Smith wrote: On Sat, 16 Sep 2006, Julian H. Stacey wrote: Hans Lambermont wrote: Julian H. Stacey wrote: Stable is a misnomer that harms FreeBSD somewhat. Why not rename 'stable' into 'stable-api' ? Nice, an improvement on what we have :-) If enough agree, the name of this mail list could be changed for a start. Sure, but what colour the new bikeshed? Trite.Stable != stable. Let Core choose any non misnomer. -- Julian Stacey. BSD Unix C Net Consultancy, Munich/Muenchen http://berklix.com Mail Ascii, not HTML. Ihr Rauch = mein allergischer Kopfschmerz. Don't buy it ! Get it free ! http://berklix.org/free-software ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: panic: integer divide fault on 6.1
Joao Barros wrote: Hi all, I was contacted by Chris who had the same problem. Since I didn't follow up on my problem he asked me if it was solved and indeed it was solved by Søren and the fix has been committed to CURRENT: http://lists.freebsd.org/pipermail/cvs-all/2006-September/188353.html I'm hoping this gets MFC'ed in time for 6.2 It will be, I'm collecting fixes in -current that I'll get MFC'd soon... -Søren ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: iSCSI HBAs
On Sat, Sep 16, 2006 at 03:35:52PM +0300, Danny Braniss wrote: being involved with the iSCSI initiator for FreeBSD, I can't see where this can help for a diskless host, or in other words, what's wrong with NFS? Well, for one thing since iSCSI is designed for SAN use, the filesystem can safely assume that nothing else is accessing it concurrently and do a lot more aggressive caching. NFS has to play it safe and check with the server every time a file is accessed to make sure it hasn't changed. It sounds to me like the OP is thinking about servers in a large data center booting off an iSCSI SAN. Makes migrating off of dead hardware to a new machine (or even a VM) a snap. also, the TOE cards are not that cheep either :-) my 2c, danny They're usually cheaper than fibre channel HBAs though ;-) Craig ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Polling and em0
polling(4) says that supported devices include em(4) and that polling support is turned on and off with ifconfig's 'polling' option. But ifconfig doesn't seem to recognize that option either as a standalone request or with the initial em0 setup at boot. This is after a source cvsup (releng=6 for the frozen for 6.2 sources) yesterday and buildworld + buildkernel. em support is compiled in the kernel rather than loaded. Mobo is a Supermicro P4SCT-0 with Intel 875 chipset. Is this a known issue that I haven't found references to, or perhaps something related to my specific configuration? FreeBSD v2.netoldies.com 6.2-PRERELEASE FreeBSD 6.2-PRERELEASE #0: Fri Sep 15 15:14:07 PDT 2006 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/V2KERNEL i386 Thanks --Bill ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
sshd failed to update ( /libexec/ld-elf.so.1: Shared object libbsm.so.1 not found, required by sshd )
I have RELENG_6 ( just updated and installed kernel , 6_2 prerelease ) and by mistake ( or my stupid hands ) I did : cd /usr/src/secure make install now sshd does not work. it tells: /libexec/ld-elf.so.1: Shared object libbsm.so.1 not found, required by sshd I tried to build the system again but the result is same. I did make cleandir ( twice ) in /usr/src and tried this solution: # cd /usr/src/secure/lib/libssh # make obj make depend make make install # cd /usr/src/secure/usr.sbin/sshd # make obj make depend make make install but build fails at: /usr/src/secure/usr.sbin/sshd/../../../crypto/openssh/audit-bsm.c:50:31: bsm/audit_uevents.h: No such file or directory /usr/src/secure/usr.sbin/sshd/../../../crypto/openssh/audit-bsm.c:51:30: bsm/audit_record.h: No such file or directory mkdep: compile failed *** Error code 1 But make buildworld did the job without error ( at the end of compilation ) If I try to copy libbsm.so/a/1 ( or install libbsm ) to the /usr/lib - sshd can be launched, , but does not allow to login ( abort connection ) without any messages in the log. -- Pavel Sokolov ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Attention Julian Stacey
You are refusing personal email. This is a bit antisocial since it leaves me no way to reply privately to your email. Kris ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: RELENG_6 Livelock
On Saturday 16 September 2006 07:02, Frode Nordahl wrote: Hello, FreeBSD localhost.localdomain 6.2-PRERELEASE FreeBSD 6.2-PRERELEASE #1: Wed Sep 13 00:10:04 CEST 2006 [EMAIL PROTECTED]:/ usr/obj/usr/src/sys/PT i386 After running some stress tests for 3 days, I wanted to remove some large directories. Do you have a coredump? I assume you do from your debug output. Can you download http://www.FreeBSD.org/~jhb/gdb/gdb6, fire up kgdb, and once in kgdb, do 'source /path/to/gdb6' and then run 'ps' and reply with the output from that? -- John Baldwin ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: sshd failed to update ( /libexec/ld-elf.so.1: Shared object libbsm.so.1 not found, required by sshd )
On Saturday 16 September 2006 15:12, Pavel Sokolov wrote: I have RELENG_6 ( just updated and installed kernel , 6_2 prerelease ) and by mistake ( or my stupid hands ) I did : cd /usr/src/secure make install now sshd does not work. it tells: /libexec/ld-elf.so.1: Shared object libbsm.so.1 not found, required by sshd I tried to build the system again but the result is same. I did make cleandir ( twice ) in /usr/src and tried this solution: # cd /usr/src/secure/lib/libssh # make obj make depend make make install # cd /usr/src/secure/usr.sbin/sshd # make obj make depend make make install but build fails at: Use NO_AUDIT=yes in your build and see if that gives you a working sshd. (i.e. make NO_AUDIT=yes depend make NO_AUDIT=yes make NO_AUDIT=yes install) -- John Baldwin ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Attention Julian Stacey
Kris Kennaway wrote: You are refusing personal email. This is a bit antisocial since it leaves me no way to reply privately to your email. Hi Kris, Huh ? Some mistake. No intent to block, except the usual list of spam domains phrases get filtered. Maybe something got wrongly listed there though. But I have had problems a while back, been reconfiging lots of things, inc named etc last few days. Wasn't aware anyone inconvenienced, sorry if so. Please private mail max info on nature of the block you see I'll try to solve it. I'll private mail you (don't want 'em in list archive :-) some addresses you can use to send the debug of the blockage you see I'm unaware of. Cheers. -- Julian Stacey. BSD Unix C Net Consultancy, Munich/Muenchen http://berklix.com Mail Ascii, not HTML. Ihr Rauch = mein allergischer Kopfschmerz. Don't buy it ! Get it free ! http://berklix.org/free-software ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: RELENG_6 Livelock
On 16. sep. 2006, at 22.09, John Baldwin wrote: On Saturday 16 September 2006 07:02, Frode Nordahl wrote: Hello, FreeBSD localhost.localdomain 6.2-PRERELEASE FreeBSD 6.2-PRERELEASE #1: Wed Sep 13 00:10:04 CEST 2006 [EMAIL PROTECTED]:/ usr/obj/usr/src/sys/PT i386 After running some stress tests for 3 days, I wanted to remove some large directories. Do you have a coredump? I assume you do from your debug output. Can you download http://www.FreeBSD.org/~jhb/gdb/gdb6, fire up kgdb, and once in kgdb, do 'source /path/to/gdb6' and then run 'ps' and reply with the output from that? I am sorry, I have not. I tried to call doadump, but there was no dumpdevice configured :-( Somehow I have convinced myself that this was turned on by default now, so I have not enabled it explicitly in rc.conf. Is there any way to tell DDB what dumpdevice to use directly? I will configure a dumpdevice and try really hard to make it happen again. -- Frode Nordahl ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: RELENG_6 Livelock
On 16. sep. 2006, at 22.22, Frode Nordahl wrote: On 16. sep. 2006, at 22.09, John Baldwin wrote: On Saturday 16 September 2006 07:02, Frode Nordahl wrote: Hello, FreeBSD localhost.localdomain 6.2-PRERELEASE FreeBSD 6.2-PRERELEASE #1: Wed Sep 13 00:10:04 CEST 2006 [EMAIL PROTECTED]:/ usr/obj/usr/src/sys/PT i386 After running some stress tests for 3 days, I wanted to remove some large directories. Do you have a coredump? I assume you do from your debug output. Can you download http://www.FreeBSD.org/~jhb/gdb/gdb6, fire up kgdb, and once in kgdb, do 'source /path/to/gdb6' and then run 'ps' and reply with the output from that? I am sorry, I have not. I tried to call doadump, but there was no dumpdevice configured :-( Somehow I have convinced myself that this was turned on by default now, so I have not enabled it explicitly in rc.conf. Is there any way to tell DDB what dumpdevice to use directly? I will configure a dumpdevice and try really hard to make it happen again. I was able to reproduce the livelock again, and this time I had the system armed with dumpon :-) Here is the output you requested: (kgdb) ps pid ppid pgrp uid state wmesg wchancmd 2535 2499 2535 0 R+ CPU 0 rm 2534 2499 2534 0 L+ *Giant0xc6704580 rm 2533 2499 2533 0 L+ *Giant0xc6704580 rm 2532 2499 2532 0 R+ rm 2531 2499 2531 0 L+ *Giant0xc6704580 rm 2499 2496 2499 0 Ss+ ttyin0xc655d810 bash 2496 784 2496 0 Rs sshd 852 1 852 0 Rs+ getty 851 1 851 0 Ss+ ttyin0xc6569010 getty 850 1 850 0 Ss+ ttyin0xc6568c10 getty 849 1 849 0 Ss+ ttyin0xc6569c10 getty 848 1 848 0 Ss+ ttyin0xc6569810 getty 847 1 847 0 Ss+ ttyin0xc6568410 getty 846 1 846 0 Ss+ ttyin0xc6568010 getty 845 1 845 0 Ss+ ttyin0xc6567810 getty 844 1 844 0 Ss+ ttyin0xc6567c10 getty 802 1 802 0 Rs cron 796 1 79625 Ss pause0xc673524c sendmail 790 1 790 0 Rs sendmail 784 1 784 0 Ss select 0xc09ebb64 sshd 763 1 763 0 Rs ntpd 731 725 725 0 S nfslockd 0xc09f4128 rpc.lockd ---Type return to continue, or q return to quit--- 725 1 725 0 Rs rpc.lockd 720 1 720 0 Rs rpc.statd 715 710 710 0 S -0xc6715800 nfsd 714 710 710 0 S -0xc671f000 nfsd 713 710 710 0 S -0xc651b600 nfsd 712 710 710 0 S -0xc6715e00 nfsd 710 1 710 0 Ss select 0xc09ebb64 nfsd 708 1 708 0 Ss select 0xc09ebb64 mountd 639 1 639 0 Rs rpcbind 604 1 604 0 Rs syslogd 530 1 530 0 Ss select 0xc09ebb64 devd 43 0 0 0 RL [schedcpu] 42 0 0 0 DL sdflush 0xc09f9554 [softdepflush] 41 0 0 0 RL [syncer] 40 0 0 0 RL [vnlru] 39 0 0 0 DL psleep 0xc09ec0cc [bufdaemon] 38 0 0 0 RL [pagezero] 37 0 0 0 DL psleep 0xc09fa014 [vmdaemon] 36 0 0 0 DL psleep 0xc09f9fd0 [pagedaemon] 35 0 0 0 WL [irq1: atkbd0] 34 0 0 0 DL -0xc6560a3c [fdc0] 33 0 0 0 WL [irq7: ppc0] 32 0 0 0 WL [swi0: sio] ---Type return to continue, or q return to quit--- 31 0 0 0 RL [acpi_thermal] 30 0 0 0 DL -0xc651dd00 [em0 taskq] 29 0 0 0 WL [irq20: amr0] 28 0 0 0 DL idle 0xc651b000 [aic_recovery1] 27 0 0 0 WL [irq17: ahc1] 26 0 0 0 DL idle 0xc651b000 [aic_recovery1] 25 0 0 0 DL idle 0xc648a600 [aic_recovery0] 24 0 0 0 WL [irq16: ahc0] 23 0 0 0 DL idle 0xc648a600 [aic_recovery0] 22 0 0 0 WL [irq15: ata2] 21 0 0 0 WL [irq14: ata0] 20 0 0 0 WL [irq18: fxp0] 19 0 0 0 WL [irq31: acpi0] 18 0 0 0 WL [swi6: Giant taskq] 17 0
Re: sshd failed to update ( /libexec/ld-elf.so.1: Shared object libbsm.so.1 not found, required by sshd )
Pavel Sokolov wrote: I have RELENG_6 ( just updated and installed kernel , 6_2 prerelease ) and by mistake ( or my stupid hands ) I did : cd /usr/src/secure make install now sshd does not work. it tells: /libexec/ld-elf.so.1: Shared object libbsm.so.1 not found, required by sshd I tried to build the system again but the result is same. I did make cleandir ( twice ) in /usr/src and tried this solution: # cd /usr/src/secure/lib/libssh # make obj make depend make make install # cd /usr/src/secure/usr.sbin/sshd # make obj make depend make make install but build fails at: /usr/src/secure/usr.sbin/sshd/../../../crypto/openssh/audit-bsm.c:50:31: bsm/audit_uevents.h: No such file or directory /usr/src/secure/usr.sbin/sshd/../../../crypto/openssh/audit-bsm.c:51:30: bsm/audit_record.h: No such file or directory mkdep: compile failed *** Error code 1 But make buildworld did the job without error ( at the end of compilation ) If I try to copy libbsm.so/a/1 ( or install libbsm ) to the /usr/lib - sshd can be launched, , but does not allow to login ( abort connection ) without any messages in the log. -- Pavel Sokolov man ldconfig Try to `ldconfig -m /PATH/TO/LIB` - here PATH_TO_LIB not meaning point to lib as it s but only on dir where it placed. if it works fine insert into /etc/defaults/rc.conf in ``ldconfig'' section. Hope it works. And use portupgrade for the future, because it places copy to /usr/local/lib/compat of previous versions of needed libs... -- Oleg D. -- don't believe every word people use to say, they might be wrong. an undefined problem has infinitive number of solutions. smime.p7s Description: S/MIME Cryptographic Signature
Re: sshd failed to update ( /libexec/ld-elf.so.1: Shared objectlibbsm.so.1 not found, required by sshd )
# cd /usr/src/secure/lib/libssh # make obj make depend make make install # cd /usr/src/secure/usr.sbin/sshd # make obj make depend make make install but build fails at: Use NO_AUDIT=yes in your build and see if that gives you a working sshd. (i.e. make NO_AUDIT=yes depend make NO_AUDIT=yes make NO_AUDIT=yes install) John Baldwin It works ! Thanks! -- Pavel Sokolov ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Attention Julian Stacey
Julian H. Stacey wrote: Kris Kennaway wrote: You are refusing personal email. This is a bit antisocial since it leaves me no way to reply privately to your email. Hi Kris, Huh ? Some mistake. No intent to block, except the usual list of spam domains phrases get filtered. Maybe something got wrongly listed there though. But I have had problems a while back, been reconfiging lots of things, inc named etc last few days. Wasn't aware anyone inconvenienced, sorry if so. Please private mail max info on nature of the block you see I'll try to solve it. I'll private mail you (don't want 'em in list archive :-) some addresses you can use to send the debug of the blockage you see I'm unaware of. Cheers. That mail routed through mu.org which is listed as a spam domain here, so my SMTP issuedAccess denied http://berklix.com/~jhs/phone/; (To rescue the occasional non spammer that might inadvertently get caught). I dont keep records of each spam that causes each domain to be added to the spam list. Looking at mu.org To see what it is: http://www.mu.org/ features a female nude. Tableware, Hosting for christians hodge podge of strange domain names - I wouldn't be suprised if spammers had lurked @ mu.org. Not a tight unified ship. nslookup doesn't show an MX for obsecurity.org @ mu.org, but mu.org was an uplink on Dyn-DNS from [EMAIL PROTECTED] Whois lists Paul Saab, not a name I know. I don't use external RBL services, so don't know if public RBLs block mu.org ? -- Julian Stacey. BSD Unix C Net Consultancy, Munich/Muenchen http://berklix.com Mail Ascii, not HTML. Ihr Rauch = mein allergischer Kopfschmerz. Don't buy it ! Get it free ! http://berklix.org/free-software ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Attention Julian Stacey
On Sat, Sep 16, 2006 at 11:35:46PM +0200, Julian H. Stacey wrote: Julian H. Stacey wrote: Kris Kennaway wrote: You are refusing personal email. This is a bit antisocial since it leaves me no way to reply privately to your email. Hi Kris, Huh ? Some mistake. No intent to block, except the usual list of spam domains phrases get filtered. Maybe something got wrongly listed there though. But I have had problems a while back, been reconfiging lots of things, inc named etc last few days. Wasn't aware anyone inconvenienced, sorry if so. Please private mail max info on nature of the block you see I'll try to solve it. I'll private mail you (don't want 'em in list archive :-) some addresses you can use to send the debug of the blockage you see I'm unaware of. Cheers. That mail routed through mu.org which is listed as a spam domain here, so my SMTP issued Access denied http://berklix.com/~jhs/phone/; (To rescue the occasional non spammer that might inadvertently get caught). I dont keep records of each spam that causes each domain to be added to the spam list. Looking at mu.org To see what it is: http://www.mu.org/ features a female nude. Tableware, Hosting for christians hodge podge of strange domain names - I wouldn't be suprised if spammers had lurked @ mu.org. Not a tight unified ship. nslookup doesn't show an MX for obsecurity.org @ mu.org, but mu.org was an uplink on Dyn-DNS from [EMAIL PROTECTED] Whois lists Paul Saab, not a name I know. I don't use external RBL services, so don't know if public RBLs block mu.org ? lol, that's the stupidest thing I've heard all week. finger [EMAIL PROTECTED] Kris pgp8WBahB5z5c.pgp Description: PGP signature
Re: Attention Julian Stacey
[EMAIL PROTECTED] Message-id: [EMAIL PROTECTED] From: Kris Kennaway [EMAIL PROTECTED] lol, that's the stupidest thing I've heard all week. Inflamatory. Refered to postmaster. -- Julian Stacey. BSD Unix C Net Consultancy, Munich/Muenchen http://berklix.com Mail Ascii, not HTML. Ihr Rauch = mein allergischer Kopfschmerz. Don't buy it ! Get it free ! http://berklix.org/free-software ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
RELENG_6 power button ignored after halt if ACPI enabled
I've just upgraded 2 machines to 6.2-PRERELEASE #1: Sat Sep 16 18:31:43 NZST 2006: - Supermicro P3TDER (Serverworks HE-SL Chipset, AMIBOIS) - Supermicro P3TDDE (VIA Apolla 266 chipset, AWARD) They both exhibit the same problem: If ACPI is enabled, shutting down via 'shutdown -h' appears to work properly (judging by the console output) - however to actually power off the machine the power button must be held until the power supply detects that the button has been down for 20s and turns us off. Poweroff via 'shutdown -p' and reboot via 'shutdown -r' all work ok. If I boot with ACPI disabled, then after 'shutdown -h', pressing the power button works in the usual way (i.e powers off after about 1-2 seconds). Given that the two machines are reasonably different, this looks like it might be common - anyone else seeing this? In terms of getting more information to help debug this, what is the best way to proceed? Cheers Mark ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Attention Julian Stacey
On Sun, Sep 17, 2006 at 02:19:35AM +0200, Julian H. Stacey wrote: [EMAIL PROTECTED] Message-id: [EMAIL PROTECTED] From: Kris Kennaway [EMAIL PROTECTED] lol, that's the stupidest thing I've heard all week. Inflamatory. Refered to postmaster. Let's hope your filtering doesn't accuse him of being a spammer too! Kris pgpj6XW4ZPZXc.pgp Description: PGP signature
Re: gmirror RAID-1: rebuilding freezes machine
On Thu, Sep 14, 2006 at 07:42:25AM -0400, Michael Butler wrote: I've been bitten by this - make sure that the first slice on the mirrored partition does not start at offset 0. For example, this disk is mirrored on slice 2 .. [EMAIL PROTECTED]:/home/imb sudo bsdlabel mirror/gm0s2 # /dev/mirror/gm0s2: 8 partitions: #size offsetfstype [fsize bsize bps/cpg] ~ a: 524272 164.2BSD 2048 16384 32768 ~^^^ ~ c: 2846557340unused0 0# raw part .. ~ d: 1048576 5242884.2BSD0 0 0 ~ e: 1048576 15728644.2BSD0 0 0 ~ f: 282034294 26214404.2BSD0 0 0 What is the problem with this? And how would one avoid it? I've got quite a few production systems with this: # bsdlabel mirror/gm0s1 # /dev/mirror/gm0s1: 8 partitions: #size offsetfstype [fsize bsize bps/cpg] a: 419430404.2BSD 2048 16384 28552 b: 4194304 4194304 swap c: 5860672020unused0 0 # raw part, don't edit d: 67108864 83886084.2BSD 2048 16384 28552 e: 188743680 754974724.2BSD 2048 16384 28552 f: 321826050 2642411524.2BSD 2048 16384 28552 -- Jo Rhett senior geek SVcolo : Silicon Valley Colocation ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Attention Julian Stacey
On Sun, 17 Sep 2006, Julian H. Stacey wrote: lol, that's the stupidest thing I've heard all week. Inflamatory. Refered to postmaster. That's even funnier. -- Dave ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: RELENG_6 Livelock
On Saturday 16 September 2006 16:55, Frode Nordahl wrote: On 16. sep. 2006, at 22.22, Frode Nordahl wrote: On 16. sep. 2006, at 22.09, John Baldwin wrote: On Saturday 16 September 2006 07:02, Frode Nordahl wrote: Hello, FreeBSD localhost.localdomain 6.2-PRERELEASE FreeBSD 6.2-PRERELEASE #1: Wed Sep 13 00:10:04 CEST 2006 [EMAIL PROTECTED]:/ usr/obj/usr/src/sys/PT i386 After running some stress tests for 3 days, I wanted to remove some large directories. Do you have a coredump? I assume you do from your debug output. Can you download http://www.FreeBSD.org/~jhb/gdb/gdb6, fire up kgdb, and once in kgdb, do 'source /path/to/gdb6' and then run 'ps' and reply with the output from that? I am sorry, I have not. I tried to call doadump, but there was no dumpdevice configured :-( Somehow I have convinced myself that this was turned on by default now, so I have not enabled it explicitly in rc.conf. Is there any way to tell DDB what dumpdevice to use directly? I will configure a dumpdevice and try really hard to make it happen again. I was able to reproduce the livelock again, and this time I had the system armed with dumpon :-) Here is the output you requested: (kgdb) ps pid ppid pgrp uid state wmesg wchancmd 2535 2499 2535 0 R+ CPU 0 rm 2534 2499 2534 0 L+ *Giant0xc6704580 rm 2533 2499 2533 0 L+ *Giant0xc6704580 rm 2532 2499 2532 0 R+ rm 2531 2499 2531 0 L+ *Giant0xc6704580 rm 2499 2496 2499 0 Ss+ ttyin0xc655d810 bash 2496 784 2496 0 Rs sshd Ok, do 'lockchain 2534' in kgdb (with gdb6 sourced) and let me see the output from that. -- John Baldwin ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Polling and em0
On 9/17/06, Bill Blue [EMAIL PROTECTED] wrote: polling(4) says that supported devices include em(4) and that polling support is turned on and off with ifconfig's 'polling' option. But ifconfig doesn't seem to recognize that option either as a standalone request or with the initial em0 setup at boot. This is after a source cvsup (releng=6 for the frozen for 6.2 sources) yesterday and buildworld + buildkernel. em support is compiled in the kernel rather than loaded. Mobo is a Supermicro P4SCT-0 with Intel 875 chipset. Is this a known issue that I haven't found references to, or perhaps something related to my specific configuration? You need polling support in the kernel, you can look at NOTES for POLLING option. Cheers, Jiawei Ye -- If it looks like a duck, walks like a duck, and quacks like a duck, then to the end user it's a duck, and end users have made it pretty clear they want a duck; whether the duck drinks hot chocolate or coffee is irrelevant. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ARRRRGH! Guys, who's breaking -STABLE's GMIRROR code?!
On Fri, 2006-09-15 at 02:09 +0200, Karol Kwiatkowski wrote: On 15/09/2006 01:37, Benjamin Lutz wrote: On Friday 15 September 2006 01:15, Kris Kennaway wrote: Anyone who is confused but doesn't attempt to enlighten themselves by reading the provided documentation deserves to stay confused :) What if they're unaware of their own confusion? I guess they get what they deserves ;) Is there a be better source of enlightenment than a handbook? To quote[1]: --% 21.2.2.1 What Is FreeBSD-STABLE? FreeBSD-STABLE is our development branch from which major releases are made. Changes go into this branch at a different pace, and with the general assumption that they have first gone into FreeBSD-CURRENT for testing. This is still a development branch, however, and this means that at any given time, the sources for FreeBSD-STABLE may or may not be suitable for any particular purpose. It is simply another engineering development track, not a resource for end-users. --% Perhaps the flow of FAQs and confusion resulting from the misnomer might be stemmed somewhat if something like the following were appended to that: Note that -STABLE refers to the stability of the FreeBSD API, not to the run-time stability of the branch. The FreeBSD API (normally?) only changes across major version releases. Someone with a more intimate understanding of how it all works could probably write a better version of that. I suspect that the confusion for new users isn't helped by the following statement from the 'version-guide' article: 1.3 STABLE versus CURRENT During the lifetime of each major release, an individual branch may also be termed STABLE. This indicates that the FreeBSD Project believes that the branch is of sufficiently proven quality to be used by a wide range of users. Branches that need further testing before being widely adopted are named CURRENT. The crux of the confusion is exemplified here by the terms wide range of users and widely adopted used in reference to the suggested target audiences for STABLE and CURRENT, respectively. While the explanations themselves are not specifically inaccurate, they are easily misinterpreted or, rather, difficult to interpret correctly, for a new user trying to understand it all. It simply reflects the confusion caused by the use of the STABLE tag. All-in-all, I think Marc G. Fournier had the best suggestion: Or rename it what it is: 6.x-BETA Where x == the next -RELEASE ... Which has at least the following benefits: 1. highlights that the software is BETA (and thus in need of testing - in both senses) 2. shows that the software is version n+1 (n == existing -RELEASE) 3. avoids the confusion of the -STABLE tag (both for new, and - dare I say - existing, users) Wayne ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Polling and em0
Bill Blue wrote: polling(4) says that supported devices include em(4) and that polling support is turned on and off with ifconfig's 'polling' option. But ifconfig doesn't seem to recognize that option either as a standalone request or with the initial em0 setup at boot. This is after a source cvsup (releng=6 for the frozen for 6.2 sources) yesterday and buildworld + buildkernel. em support is compiled in the kernel rather than loaded. Mobo is a Supermicro P4SCT-0 with Intel 875 chipset. Is this a known issue that I haven't found references to, or perhaps something related to my specific configuration? FreeBSD v2.netoldies.com 6.2-PRERELEASE FreeBSD 6.2-PRERELEASE #0: Fri Sep 15 15:14:07 PDT 2006 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/V2KERNEL i386 Thanks --Bill Since 6.1 I have stopped using polling as a regular kernel seems to give good performance as compared to polling mode. In fact I used to get anything between 55-75megs/sec on 6.1 with regular cables but since upgraded to cat6 quality Ethernet cable I get practically full gigabit speed with no polling. Close to 97megs/sec is the performance I get out of my Dells with the em driver, and apparently the new em driver in 6-stable 6.2 is even faster. em(4) Dell to em(4) Dell dell1# cat /dev/zero | dd bs=1m | nc dell2 3000 ^C0+18456 records in 0+18455 records out 1209466880 bytes transferred in 12.459299 secs (97,073,429 bytes/sec) Mike ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
