ZFS root on MB Intel S3420GP
Hi! I have this hardware: smbios.system.maker="Intel Corporation" smbios.system.product="S3420GP" with 4G ram and 4x WD 500G drives. I try both raids in the bios, in both cases i try raid 10. I.e. I have 1Tb ar0 device. After reading http://wiki.freebsd.org/RootOnZFS/GPTZFSBoot/RAIDZ1 I try to install FreeBSD on this box, but I change ad0..ad1.. to my ar0 device. I try to have zfs on intel raid10. All commands run successfully, but after reboot I have: gptzfsboot no zfs pools located: can't boot What mistake I made? What best solution with my hardware exist? -- Lystopad Olexandr ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: ZFS root on MB Intel S3420GP
Hello, George Kontostanos! On Sun, Apr 17, 2011 at 04:54:34PM +0300 gkontos.m...@gmail.com wrote about "Re: ZFS root on MB Intel S3420GP": > There is a nice guide in the WIKI regarding how to install your system with > ZFS on root. > > http://wiki.freebsd.org/RootOnZFS/GPTZFSBoot/RAIDZ2 > > In any case don't configure the raid in your controller and let ZFS take > care of this. Thanks for answer! Is it possible to hot change disks with zfs raid on my motherboard? > Regards, > > 2011/4/17 Lystopad Olexandr > > > Hi! > > > > I have this hardware: > > > > smbios.system.maker="Intel Corporation" > > smbios.system.product="S3420GP" > > > > with 4G ram and 4x WD 500G drives. > > > > I try both raids in the bios, in both cases i try raid 10. > > I.e. I have 1Tb ar0 device. > > > > After reading http://wiki.freebsd.org/RootOnZFS/GPTZFSBoot/RAIDZ1 I > > try to install FreeBSD on this box, but I change ad0..ad1.. to my > > ar0 device. I try to have zfs on intel raid10. > > > > All commands run successfully, but after reboot I have: > > > > gptzfsboot no zfs pools located: can't boot > > > > What mistake I made? > > > > What best solution with my hardware exist? > > > > -- > > Lystopad Olexandr > > ___ > > freebsd-stable@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > > To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org" > > > > > > -- > George Kontostanos > aisecure.net <http://www.aisecure.net> -- Lystopad Olexandr ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: ZFS root on MB Intel S3420GP
Hello, Jeremy Chadwick! On Sun, Apr 17, 2011 at 07:21:35AM -0700 free...@jdc.parodius.com wrote about "Re: ZFS root on MB Intel S3420GP": > On Sun, Apr 17, 2011 at 04:32:32PM +0400, Lystopad Olexandr wrote: > > I have this hardware: > > > > smbios.system.maker="Intel Corporation" > > smbios.system.product="S3420GP" > > > > with 4G ram and 4x WD 500G drives. > > > > I try both raids in the bios, in both cases i try raid 10. > > I.e. I have 1Tb ar0 device. > > I strongly urge you to remove use of Intel RST[1]. It's been confirmed > many times over[2] that FreeBSD's support for it is broken in many > regards. You are putting your data at extreme/great risk using it. > Something as simple as a single-disk failure could result in the > *entire* loss of your array. You will need to read the PRs listed at > Wikipedia slowly, and in full to understand the nature of the problem. > Do not skim them. > > I cannot stress the importance of this enough. This is not a joke nor > is it overblown. I recommend you rely on ZFS entirely, and run your > SATA controller in AHCI mode instead. My personal recommendation would > be to use UFS for your root filesystem (or even gmirror) and use ZFS for > the rest. Jeremy, thank you very much! I remove intel raids and move to ahci already. I install freebsd 8.2-amd64 on that box and about to make gmirror with 4 disks. :-) Is it possible to remote migrate to zfs? I have access to this server remotely, and do not have local access. This server with 4 disks, and I can do anything with 3 of disks. Now there installed 8.2-amd64 on ad4. > With regards to AHCI mode: Most of us strongly advocate use of ahci.ko > (not ataahci.ko; they differ), which does SATA<->CAM translation. You > also gain NCQ capability using this. Be aware your disks will appear as > "adaX" (not a typo), and you will use "camcontrol" (rather than > "atacontrol") to maintain them. Utilities like smartmontools do work > with this. Many of us (users and developers) have been using ahci.ko > reliably for 1-2 years now. Simply add ahci_load="YES" in loader.conf? Or something else? > > After reading http://wiki.freebsd.org/RootOnZFS/GPTZFSBoot/RAIDZ1 I > > try to install FreeBSD on this box, but I change ad0..ad1.. to my > > ar0 device. I try to have zfs on intel raid10. > > > > All commands run successfully, but after reboot I have: > > > > gptzfsboot no zfs pools located: can't boot > > > > What mistake I made? > > > > What best solution with my hardware exist? > > I imagine what you're trying to accomplish won't work given that the > disk geometry and other mechanics are completely lost given use of > Intel RST, and *especially* with regards to the boot sequence. > > Furthermore, the bootstraps you're using imply use of GPT; did you > configure your setup using GPT? I'm guessing not. I make all steps in url in first my mail. Am I wrong? > [1]: Known as "Intel Rapid Storage Technology", "Intel MatrixRAID", > "Intel HostRAID", "Intel Embedded Server RAID Technology", "Intel Matrix > Storage RAID Technology", and many other terms. Intel keeps changing > the term/labelling of this BIOS-level RAID, almost certainly for > marketing purposes. :-((( I dont know... > [2]: http://en.wikipedia.org/wiki/Intel_Rapid_Storage_Technology > Note that FreeBSD PRs are provided in the article. -- Lystopad Olexandr ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: ZFS root on MB Intel S3420GP
Hello, Jeremy Chadwick! > > > With regards to AHCI mode: Most of us strongly advocate use of ahci.ko > > > (not ataahci.ko; they differ), which does SATA<->CAM translation. You > > > also gain NCQ capability using this. Be aware your disks will appear as > > > "adaX" (not a typo), and you will use "camcontrol" (rather than > > > "atacontrol") to maintain them. Utilities like smartmontools do work > > > with this. Many of us (users and developers) have been using ahci.ko > > > reliably for 1-2 years now. > > > > Simply add ahci_load="YES" in loader.conf? Or something else? > > Correct. > > I tend to do the following from the very beginning of a new FreeBSD box > installation, however: > > - Boot FreeBSD installation medium (PXE, CD, USB, whatever) > - At beastie menu, escape to loader prompt and do "load ahci" then > "boot" > - Install FreeBSD like usual, creating slices/partitions on adaX disks > like normal, etc... > - When the system reboots, at the beastie prompt, make sure to escape to > loader and do "load ahci" then "boot" again. > - Once the system is finally up, edit /boot/loader.conf to add > ahci_load="yes". What about ahci_load="YES" after freebsd install? Is it too late? Thank you for your quick answers! -- Lystopad Olexandr ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: ZFS root on MB Intel S3420GP
Hello, Jeremy Chadwick!
> > What about ahci_load="YES" after freebsd install? Is it too late?
>
> I don't recommend enabling ahci.ko after the OS has already been
> installed on an adX disk, simply because I believe the combination of
> GEOM+CAM+ahci may show different geometry details than GEOM+ata would.
>
> Note: I said "I believe", not "I can confirm/validate". I could be
> completely wrong. Rather than find out ( :-) ) I tend to try and do
> things consistently from the very beginning.
>
> So you can try it if you want, be my guest, report back.
Jeremy, I ask remote boy to reinstall freebsd ot that box with load
ahci in loader prompt and successfully get adaX deveices! Thanks.
I'll try to make zfs on ada{6,8,10} devices remotely with raidz1.
thanks!
--
Lystopad Olexandr
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: ZFS root on MB Intel S3420GP
Hello, Jeremy Chadwick! > > What about ahci_load="YES" after freebsd install? Is it too late? > > I don't recommend enabling ahci.ko after the OS has already been > installed on an adX disk, simply because I believe the combination of > GEOM+CAM+ahci may show different geometry details than GEOM+ata would. > > Note: I said "I believe", not "I can confirm/validate". I could be > completely wrong. Rather than find out ( :-) ) I tend to try and do > things consistently from the very beginning. > > So you can try it if you want, be my guest, report back. Wow! Remote boy install freebsd onto another hdd, but boot server from old hdd with gmirror! In the loader prompt he write load ahci and server boots ok!!! :-) I see adaX devices! Thanks! -- Lystopad Olexandr ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: ZFS root on MB Intel S3420GP
Hello, Jeremy Chadwick!
On Sun, Apr 17, 2011 at 11:49:12AM -0700
free...@jdc.parodius.com wrote about "Re: ZFS root on MB Intel S3420GP":
> On Sun, Apr 17, 2011 at 08:14:40PM +0400, Lystopad Olexandr wrote:
> > On Sun, Apr 17, 2011 at 04:54:34PM +0300
> > gkontos.m...@gmail.com wrote about "Re: ZFS root on MB Intel S3420GP":
> > > There is a nice guide in the WIKI regarding how to install your system
> > > with
> > > ZFS on root.
> > >
> > > http://wiki.freebsd.org/RootOnZFS/GPTZFSBoot/RAIDZ2
> > >
> > > In any case don't configure the raid in your controller and let ZFS take
> > > care of this.
> >
> > Thanks for answer!
> >
> > Is it possible to hot change disks with zfs raid on my motherboard?
>
> This has little to do with ZFS and more to do with SATA. You will need
> a hot-swap backplane for this to be possible. Decent server chassis
> usually provide this. We use Supermicro systems with hot-swap backplanes
> and they work fantastic with FreeBSD + ahci.ko.
>
> If you do not have a hot-swap backplane, there is a very good chance
> "strange things" will happen when you yank power or the signal cable.
> I've personally tried it on a test system without a hot-swap bay. When
> I pulled the SATA power connector from the hard disk, I saw a blue spark
> near the power connector and the entire system lost power.
>
> I've blogged about hot-swapping SATA disks on FreeBSD with ZFS in use
> and with ahci.ko, with full kernel output and all necessary details:
>
> http://koitsu.wordpress.com/2010/07/22/freebsd-and-zfs-hot-swapping-sata-disks-with-ahci/
>
> Please note the blog post demonstrated how I went about upgrading disks
> without needing to power the system off. Readers have commented how I
> could have done it all by using the spare bay I had, but I explicitly
> chose *not* to use that bay for the benefit of the readers who might not
> have a spare bay.
>
> Furthermore, the "zpool offline" steps probably aren't needed (ZFS
> should note the disk as UNAVAIL immediately and the array should become
> degraded), same with "zpool online". I should really refine those
> procedures, or re-do the post for present-day 8.2-RELEASE.
>
> When doing administrative/maintenance tasks, I tend to do as much
> possible to ensure the kernel/system knows what I'm about to do. :-)
>
> If you want me to perform an actual disk failure (literally yanking a
> disk out of a bay while the disk is in use + part of a ZFS pool), I can
> do that without any worry and provide the results here. Just ask.
Needed one reboot and change boot sequnce. Remote boy helps me.
I successfully migrate remotely from gmirror (ada0) to gpt+zfs(raidz1):
[root@ ~]# df -h
Filesystem SizeUsed Avail Capacity Mounted on
zroot905G569M904G 0%/
devfs1.0K1.0K 0B 100%/dev
zroot/tmp904G 35K904G 0%/tmp
zroot/usr906G2.0G904G 0%/usr
zroot/usr/local 904G142M904G 0%/usr/local
zroot/usr/local/pgsql904G 33K904G 0%/usr/local/pgsql
zroot/usr/ports 904G 31K904G 0%/usr/ports
zroot/usr/ports/distfiles904G 28K904G 0%/usr/ports/distfiles
zroot/usr/src905G242M904G 0%/usr/src
zroot/var904G111M904G 0%/var
# zpool status
pool: zroot
state: ONLINE
status: One or more devices has experienced an unrecoverable error. An
attempt was made to correct the error. Applications are unaffected.
action: Determine if the device needs to be replaced, and clear the errors
using 'zpool clear' or replace the device with 'zpool replace'.
see: http://www.sun.com/msg/ZFS-8000-9P
scrub: resilver completed after 0h0m with 0 errors on Sun Apr 17 20:56:30 2011
config:
NAME STATE READ WRITE CKSUM
zroot ONLINE 0 0 0
raidz1 ONLINE 0 0 0
gpt/disk1 ONLINE 0 0 5 12K resilvered
gpt/disk2 ONLINE 0 0 0
gpt/disk3 ONLINE 0 0 0
errors: No known data errors
[root@ ~]#
--
Lystopad Olexandr
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: ZFS root on MB Intel S3420GP
Hello, Jeremy Chadwick! On Sun, Apr 17, 2011 at 11:49:12AM -0700 free...@jdc.parodius.com wrote about "Re: ZFS root on MB Intel S3420GP": > On Sun, Apr 17, 2011 at 08:14:40PM +0400, Lystopad Olexandr wrote: > > On Sun, Apr 17, 2011 at 04:54:34PM +0300 > > gkontos.m...@gmail.com wrote about "Re: ZFS root on MB Intel S3420GP": > > > There is a nice guide in the WIKI regarding how to install your system > > > with > > > ZFS on root. > > > > > > http://wiki.freebsd.org/RootOnZFS/GPTZFSBoot/RAIDZ2 > > > > > > In any case don't configure the raid in your controller and let ZFS take > > > care of this. > > > > Thanks for answer! > > > > Is it possible to hot change disks with zfs raid on my motherboard? > > This has little to do with ZFS and more to do with SATA. You will need > a hot-swap backplane for this to be possible. Decent server chassis > usually provide this. We use Supermicro systems with hot-swap backplanes > and they work fantastic with FreeBSD + ahci.ko. Opps, forgot to add in my prev mail about hot swap: Apr 17 20:50:32 kernel: (ada1:ahcich1:0:0:0): lost device Apr 17 20:50:32 kernel: (ada1:ahcich1:0:0:0): Synchronize cache failed Apr 17 20:50:32 kernel: (ada1:ahcich1:0:0:0): removing device entry Apr 17 20:50:49 kernel: ada1 at ahcich1 bus 0 scbus1 target 0 lun 0 Apr 17 20:50:49 kernel: ada1: ATA-8 SATA 2.x device Apr 17 20:50:49 kernel: ada1: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes) Apr 17 20:50:49 kernel: ada1: Command Queueing enabled Apr 17 20:50:49 kernel: ada1: 476940MB (976773168 512 byte sectors: 16H 63S/T 16383C) worked fine. Thanks you, guys! -- Lystopad Olexandr ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Large number of SATA commits (MFCs) to RELENG_8
Hello, Jeremy Chadwick! On Tue, Apr 19, 2011 at 04:50:38PM -0700 free...@jdc.parodius.com wrote about "Large number of SATA commits (MFCs) to RELENG_8": > Folks who use SATA (speaking generally here because there's too much > that got touched) should be aware: > > Within the past ~7 hours there have been a *very* large number of > commits by mav@ that pertain to SATA-related storage controllers and > subsystems. > > I would advocate that folks rebuild world/kernel and make sure there > aren't any issues seen, or any quirks which were previously needed are > no longer. > > I haven't gone through *all* of the commits yet, but I do see some > controller-centric things that got MFC'd, such as disabling of NCQ > support on multiport Marvell 88SX61XX to relieve I/O timeouts when > doing lots of I/O (common with ZFS). > > Below are the commits. Users should absolutely use cvsweb or similar > tools to examine the commit message and see if anything relevant to > their storage subsystems was modified. I have no problems with yesturday build world+kernel. All compiled ok and system boots ok. But I have 1 question, why needed src/UPDATING? There are a lot of changes in the tree since release date and there are no one in that file. May be we need another one file, like src/ChangeLog ? ;-) -- Lystopad Olexandr ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
wi0 and adhoc
Hi! I have two freebsd boxes with 4.11 (yes, really!). They both serve wifi adhoc link (wi0 + pcic0: ) during many years with no problems. One box has died, and I change it to new one with 8.0-rel. New box have cbb0 and same wi0 card. So, now I have two boxes 4.11 and 8.0. Both with wi0 devices detected. Configs: 4.11 freebsd: wi0: flags=8843 mtu 1500 inet 192.168.197.1 netmask 0xfffc broadcast 192.168.197.3 ether 00:02:2d:05:77:1e media: IEEE 802.11 Wireless Ethernet autoselect (DS/11Mbps ) status: associated ssid IBSS 1:NT stationname sta1 channel 12 authmode OPEN powersavemode OFF powersavesleep 100 wepmode OFF weptxkey 1 8.0 freebsd: wi0: flags=8843 metric 0 mtu 2290 ether 00:60:1d:f6:bf:a4 media: IEEE 802.11 Wireless Ethernet autoselect mode 11b status: running wlan0: flags=8843 metric 0 mtu 1500 ether 00:60:1d:f6:bf:a4 inet 192.168.197.2 netmask 0xfffc broadcast 192.168.197.3 media: IEEE 802.11 Wireless Ethernet autoselect mode 11b status: running ssid IBSS channel 12 (2467 Mhz 11b) bssid 5e:b2:ec:5c:c1:8c country US authmode OPEN privacy OFF txpower 0 scanvalid 60 # ifconfig wlan0 list caps drivercaps=10301 cryptocaps=1 pciconf -lvc: ... cbb0@pci0:2:9:0:class=0x060700 card=0x14101524 chip=0x14101524 rev=0x01 hdr=0x02 vendor = 'ENE Technology Inc' device = 'CardBus Controller (CB-1420)' class = bridge subclass = PCI-CardBus cap 01[a0] = powerspec 1 supports D0 D1 D2 D3 current D0 ... dmesg: wi0: at port 0x100-0x13f irq 17 function 0 config 1 on pccard0 wi0: [ITHREAD] wi0: device timeout wi0: device timeout wi0: record read mismatch, rid=fd44, got=fc80 wi0: device timeout my questions are: 1. why txpower 0 in 8.0 box? 2. why too many ``device timeout'' messages in dmesg on 8.0 box? 3. why all pings lost in that link? thanks. -- Lystopad Olexandr ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: 8-STABLE won't boot with ZFSv28
Hello, Holger Kipp! On Wed, Jun 01, 2011 at 08:23:19AM + holger.k...@alogis.com wrote about "8-STABLE won't boot with ZFSv28": > Hi all, > I have a very irritating problem with 8-STABLE and ZFSv28 > > I upgraded to 8-STABLE as of yesterday (31.05.2011), > downloaded stable-8-zfsv28-20110521.patch.xz > and applied the patch using > > cd /usr/src > patch -E -p0 < /path/to/patchfile > make buildworld > make buildkernel KERNCONF=foo > make installkernel KERNCONF=foo > make installworld > mergemaster Looks like you forgot to update your bootcode. gpart bootcode > which all went smoothly. > > After reboot, I only got > unknown: WARNING - ATAPI_IDENTITFY requeued due to channel reset LBA=0 > all the time, and then after an hour or so (wasn't on site), > system gave > Fatal trap 12: page fault while in kernel mode > cupid - 0; apic id = 00 > fault virtual address = 0x8 > fault code = supervisor read data, page not present > instruction pointer= 0x20:0x80252301 > stack poiner = 0x28:0xff8a7ac0 > frame pointer= 0x28:0xff8a7b00 > code segment= base 0x0, limit 0xf, type 0x1b >= DPL 0, pres1, long 1, def32 > 0, gran 1 > processor eflags = interrupt enabled, resume, IOPL = 0 > current process = 0 (thread taskq)trap number = 12 > panic: page fault > cpuid = 0 > Uptime: 1h0m13s > Cannot dump. Device not defined or unavailable. > Automatic reboot in 15 seconds - press a key on the console to abort > > > Needless to say the system did not reboot. Had to powercycle. > > Then always got the > unknown: WARNING - ATAPI_IDENTITFY requeued due to channel reset LBA=0 > error about once per second. > > Have now used a fixit-disk to change back to the old kernel: > FreeBSD 8.2-STABLE #12: Mon Apr 18 12:48:56 CEST 2011 > and rebootet. > Now zfs claims to be v28, current storage pool is at 15.I'd love to > try ZFSv28, but with the old kernel I don't think > this is a good idea - but with the new kernel it seems I can't > even boot properly. > Any suggestions as to how to proceed? -- Lystopad Olexandr ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: HEADS UP: ZFS v28 merged to 8-STABLE
Hello, Martin Matuska! On Mon, Jun 06, 2011 at 12:53:11PM +0200 m...@freebsd.org wrote about "HEADS UP: ZFS v28 merged to 8-STABLE": > Hi, > > I have merged ZFS version 28 to 8-STABLE (revision 222741) finally! Thanks! My home server works ok with this update. -- Lystopad Olexandr ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
nfe troubles on -stable
hi! I csup 8.2-rel to 8.2-stable from 2011.06.09.00.00.00, add ifconfig_nfe0="up DHCP" to rc.conf and have error. But if I put static ip in rc.conf system boots ok. error: Jun 24 11:10:58 hosted-by2 kernel: nfe0: discard frame w/o leading ethernet header (len 0 pkt len 0) Jun 24 11:10:58 hosted-by2 last message repeated 28 times Jun 24 11:11:00 hosted-by2 /usr/sbin/cron[1553]: (operator) CMD (/usr/libexec/save-entropy) Jun 24 11:11:05 hosted-by2 dhclient[1359]: DHCPREQUEST on nfe0 to 255.255.255.255 port 67 Jun 24 11:11:05 hosted-by2 kernel: nfe0: discard frame w/o leading ethernet header (len 0 pkt len 0) Jun 24 11:11:20 hosted-by2 last message repeated 35 times Jun 24 11:11:21 hosted-by2 dhclient[1359]: DHCPDISCOVER on nfe0 to 255.255.255.255 port 67 interval 8 Jun 24 11:11:21 hosted-by2 kernel: nfe0: discard frame w/o leading ethernet header (len 0 pkt len 0) Jun 24 11:11:21 hosted-by2 last message repeated 28 times Jun 24 11:11:29 hosted-by2 dhclient[1359]: DHCPDISCOVER on nfe0 to 255.255.255.255 port 67 interval 10 Jun 24 11:11:29 hosted-by2 kernel: nfe0: discard frame w/o leading ethernet header (len 0 pkt len 0) Jun 24 11:11:36 hosted-by2 last message repeated 29 times Jun 24 11:11:39 hosted-by2 dhclient[1359]: DHCPDISCOVER on nfe0 to 255.255.255.255 port 67 interval 15 Jun 24 11:11:39 hosted-by2 kernel: nfe0: discard frame w/o leading ethernet header (len 0 pkt len 0) Jun 24 11:11:39 hosted-by2 last message repeated 28 times Jun 24 11:11:42 hosted-by2 kernel: nfe0: discard frame w/o leading ethernet header (len 4294967295 pkt len 4294967295) Jun 24 11:11:52 hosted-by2 last message repeated 3 times Jun 24 11:11:54 hosted-by2 dhclient[1359]: DHCPDISCOVER on nfe0 to 255.255.255.255 port 67 interval 9 Jun 24 11:11:54 hosted-by2 kernel: nfe0: discard frame w/o leading ethernet header (len 0 pkt len 0) Jun 24 11:12:01 hosted-by2 last message repeated 30 times Jun 24 11:12:03 hosted-by2 dhclient[1359]: DHCPDISCOVER on nfe0 to 255.255.255.255 port 67 interval 9 Jun 24 11:12:03 hosted-by2 kernel: nfe0: discard frame w/o leading ethernet header (len 0 pkt len 0) Jun 24 11:12:09 hosted-by2 last message repeated 29 times Jun 24 11:12:12 hosted-by2 dhclient[1359]: DHCPDISCOVER on nfe0 to 255.255.255.255 port 67 interval 10 Jun 24 11:12:12 hosted-by2 kernel: nfe0: discard frame w/o leading ethernet header (len 0 pkt len 0) pciconf -lvbc: nfe0@pci0:0:20:0: class=0x068000 card=0x2a54103c chip=0x026910de rev=0xa3 hdr=0x00 vendor = 'NVIDIA Corporation' device = 'MCP51 Network Bus Enumerator' class = bridge bar [10] = type Memory, range 32, base 0xfe02b000, size 4096, enabled bar [14] = type I/O Port, range 32, base 0xcc00, size 8, enabled cap 01[44] = powerspec 2 supports D0 D1 D2 D3 current D0 kenv: smbios.bios.reldate="04/17/2007" smbios.bios.vendor="Phoenix Technologies, LTD" smbios.bios.version=" 5.04" smbios.chassis.maker="Hewlett-Packard" smbios.chassis.serial="DM0001" smbios.chassis.tag=" " smbios.chassis.version="" smbios.memory.enabled="1048576" smbios.planar.maker="ASUSTek Computer INC." smbios.planar.product="Hematite-XL" smbios.planar.serial="MS1C75S00802301" smbios.planar.version="1.00" smbios.socket.enabled="1" smbios.socket.populated="1" smbios.system.maker="HP-Pavilion" smbios.system.product="GJ474AA-ABA s3100n" -- Lystopad Olexandr ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: 9.0 B1 Panic
Hello, Martin Wilke! On Tue, Aug 02, 2011 at 12:41:29PM +0800 m...@freebsd.org wrote about "9.0 B1 Panic": > 9.0 Beta1 Panic > > Hi guys, > > I just downloaded and install 9.0 BETA1 but it panics on ACPI. Please view > attached screenshot for the error. If you need more information, do let us > know. There no attachments in your mail. -- Lystopad Olexandr ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: how to update source tree
Hello, Man Chan! On Sat, Dec 10, 2011 at 12:20:33PM +0800 freebsd...@yahoo.com.hk wrote about "how to update source tree": > Hi, > > I am new to freebsd and just installed a 8.2 release on a laptop. I just > tried to update my source tree with the example describe in the A.4 > Anonymous CVS without any luck. The error is no route to host. Can anyone > help. You need to configure your network card, default gateway and dns. Read ch. 12.8.2 from http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/config-network-setup.html Good luck. -- Lystopad Olexandr ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
7.3-STABLE acpi and mpt problems?
Hi! I have FreeBSD 7.3-STABLE on Biostar 945GC-M4 motherboard. When I boot with custom kernel it fail to boot on ACPI. FreeBSD box do not respond to any key. But it successfully boots with button 2 from boot menu (without acpi). Then I try to boot with GENERIC. Success! Ok, I try comment out one-by-one devices in GENERIC, rebuild and install kernel, and try to boot. My custom kernel boot fine until I comment out mpt device in kernel, but it successfully boots without acpi (button 2 on boot menu). I have no mpt devices in this box. When I insert "device mpt" back to the kernel it boots successfully. Why acpi depends on device mpt? Why this server do not boot without this device? # uname -a: FreeBSD milk 7.3-STABLE FreeBSD 7.3-STABLE #15: Wed Jun 16 13:47:37 EEST 2010 r...@milk:/usr/obj/usr/src/sys/milk i386 # dmesg without acpi and with mpt device: Copyright (c) 1992-2010 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 is a registered trademark of The FreeBSD Foundation. FreeBSD 7.3-STABLE #14: Wed Jun 16 12:01:41 EEST 2010 r...@milk:/usr/obj/usr/src/sys/milk i386 Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel(R) Pentium(R) 4 CPU 2.40GHz (2394.29-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0xf33 Family = f Model = 3 Stepping = 3 Features=0xbfebfbff Features2=0x41d real memory = 528220160 (503 MB) avail memory = 507195392 (483 MB) MPTable: ioapic0: Assuming intbase of 0 ioapic0 irqs 0-23 on motherboard kbd1 at kbdmux0 pcib0: pcibus 0 on motherboard pci0: on pcib0 vgapci0: port 0xcc00-0xcc07 mem 0xfe98-0xfe9f,0xe000-0xefff,0xfe94-0xfe97 irq 16 at device 2.0 on pci0 agp0: on vgapci0 agp0: detected 7932k stolen memory agp0: aperture size is 256M pci0: at device 27.0 (no driver attached) pcib1: irq 16 at device 28.0 on pci0 pci1: on pcib1 pcib2: irq 17 at device 28.1 on pci0 pci2: on pcib2 re0: port 0xd800-0xd8ff mem 0xfdfff000-0xfdff,0xfdfe-0xfdfe irq 17 at device 0.0 on pci2 re0: Using 1 MSI messages re0: Chip rev. 0x2480 re0: MAC rev. 0x miibus0: on re0 rlphy0: PHY 1 on miibus0 rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto re0: Ethernet address: 00:30:67:41:c8:ee re0: [FILTER] uhci0: port 0xc880-0xc89f irq 23 at device 29.0 on pci0 uhci0: [GIANT-LOCKED] uhci0: [ITHREAD] usb0: on uhci0 usb0: USB revision 1.0 uhub0: on usb0 uhub0: 2 ports with 2 removable, self powered uhci1: port 0xc800-0xc81f irq 19 at device 29.1 on pci0 uhci1: [GIANT-LOCKED] uhci1: [ITHREAD] usb1: on uhci1 usb1: USB revision 1.0 uhub1: on usb1 uhub1: 2 ports with 2 removable, self powered uhci2: port 0xc480-0xc49f irq 18 at device 29.2 on pci0 uhci2: [GIANT-LOCKED] uhci2: [ITHREAD] usb2: on uhci2 usb2: USB revision 1.0 uhub2: on usb2 uhub2: 2 ports with 2 removable, self powered uhci3: port 0xc400-0xc41f irq 16 at device 29.3 on pci0 uhci3: [GIANT-LOCKED] uhci3: [ITHREAD] usb3: on uhci3 usb3: USB revision 1.0 uhub3: on usb3 uhub3: 2 ports with 2 removable, self powered ehci0: mem 0xfe937c00-0xfe937fff irq 23 at device 29.7 on pci0 ehci0: [GIANT-LOCKED] ehci0: [ITHREAD] usb4: EHCI version 1.0 usb4: companion controllers, 2 ports each: usb0 usb1 usb2 usb3 usb4: on ehci0 usb4: USB revision 2.0 uhub4: on usb4 uhub4: 8 ports with 8 removable, self powered pcib3: at device 30.0 on pci0 pci3: on pcib3 rl0: port 0xe800-0xe8ff mem 0xfebffc00-0xfebffcff irq 16 at device 2.0 on pci3 miibus1: on rl0 rlphy1: PHY 0 on miibus1 rlphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto rl0: Ethernet address: 00:e0:4c:1a:c7:92 rl0: [ITHREAD] isab0: at device 31.0 on pci0 isa0: on isab0 atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xffa0-0xffaf at device 31.1 on pci0 ata0: on atapci0 ata0: [ITHREAD] atapci1: port 0xc080-0xc087,0xc000-0xc003,0xbc00-0xbc07,0xb880-0xb883,0xb800-0xb80f irq 19 at device 31.2 on pci0 atapci1: [ITHREAD] ata2: on atapci1 ata2: [ITHREAD] ata3: on atapci1 ata3: [ITHREAD] pci0: at device 31.3 (no driver attached) cpu0 on motherboard p4tcc0: on cpu0 pmtimer0 on isa0 atkbdc0: at port 0x60,0x64 on isa0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] atkbd0: [ITHREAD] sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> vga0: at port 0x3c0-0x3df iomem 0xa-0xb on isa0 unknown: can't assign resources (memory) unknown: can't assign resources (memory) unknown: can't assign resources (port) Timecounter "TSC" frequency 2394285804 Hz quality 800 Timecounters tick every 1.000 msec ipfw2 initialized, divert loadable, nat enabled, rule-based forwarding enabled, default to accept, logging limited to 100 packets/entry by default ad0: DMA limited to UDMA33, controller found non-ATA66 cable ad0: 38166MB at ata0-master UDMA33 Trying to mount root from ufs:/dev/ad0s1a WARNING: attempt to net_add_domain(netg
Re: 7.3-STABLE acpi and mpt problems?
Hello, John Baldwin! On Wed, Jun 16, 2010 at 07:55:27AM -0400 j...@freebsd.org wrote about "Re: 7.3-STABLE acpi and mpt problems?": > On Wednesday 16 June 2010 7:14:09 am Lystopad Olexandr wrote: > > > > Hi! > > > > I have FreeBSD 7.3-STABLE on Biostar 945GC-M4 motherboard. > > When I boot with custom kernel it fail to boot on ACPI. FreeBSD box > > do not respond to any key. But it successfully boots with button 2 > > from boot menu (without acpi). > > > > Then I try to boot with GENERIC. Success! Ok, I try comment > > out one-by-one devices in GENERIC, rebuild and install kernel, > > and try to boot. My custom kernel boot fine until I comment > > out mpt device in kernel, but it successfully boots without > > acpi (button 2 on boot menu). I have no mpt devices in > > this box. When I insert "device mpt" back to the kernel it boots > > successfully. > > > > Why acpi depends on device mpt? Why this server do not boot without > > this device? > > How does it fail to boot in the non-mpt case? Does it hang, does it panic? > If it hangs, can you break into DDB and capture the output of 'ps' and a > stack > trace? (A serial console is probably useful for this.) John, thank you very much for your answer. Sorry for delay. My freebsd box fails to boot after detecting CPU and memory. It simply hang. I think this is too early to run ddb or somethig else. Also, similar problem with this device I detect on two remote bsd servers in production. After insert mpt device into kernel, that servers begin boots fine. -- Olexandr Lystopad ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
ath0: kernel panic when adhoc mode.
Hi! I install 8.0 FreeBSD, upgrade it to yesturday stable. I need to create wireless link in adhoc mode. Help me to do this. I put a wireless card into this box: a...@pci0:3:3:0:class=0x02 card=0xcc2114b9 chip=0x0013168c rev=0x01 hdr=0x00 vendor = 'Atheros Communications Inc.' device = '802.11a/b/g Wireless Adapter (AR5212)' class = network subclass = ethernet cap 01[44] = powerspec 2 supports D0 D3 current D0 when I do: # ifconfig wlan0 create wlandev ath0 wlanmode adhoc server reboot with kernel panic: Fatal trap 12: page fault while in kernel mode cpuid = 1; apic id = 01 fault virtual address = 0x fault code = supervisor read, page not present instruction pointer = 0x20:0xc0791612 stack pointer = 0x28:0xd2f42ba4 frame pointer = 0x28:0xd2f42bac 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 (ath0 taskq) trap number = 12 panic: page fault cpuid = 1 Uptime: 3m35s Physical memory: 439 MB Dumping 80 MB: 65 49 33panic: bufwrite: buffer is not busy??? cpuid = 1 17 1 #0 doadump () at pcpu.h:246 246 pcpu.h: No such file or directory. in pcpu.h (kgdb) #0 doadump () at pcpu.h:246 #1 0xc06b3497 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:416 #2 0xc06b3789 in panic (fmt=Variable "fmt" is not available. ) at /usr/src/sys/kern/kern_shutdown.c:579 #3 0xc08b63bc in trap_fatal (frame=0xd2f42b64, eva=65535) at /usr/src/sys/i386/i386/trap.c:938 #4 0xc08b6620 in trap_pfault (frame=0xd2f42b64, usermode=0, eva=65535) at /usr/src/sys/i386/i386/trap.c:851 #5 0xc08b6f39 in trap (frame=0xd2f42b64) at /usr/src/sys/i386/i386/trap.c:533 #6 0xc0899b3b in calltrap () at /usr/src/sys/i386/i386/exception.s:165 #7 0xc0791612 in ieee80211_getcapinfo (vap=0xc2d5f000, chan=0x) at /usr/src/sys/net80211/ieee80211_output.c:1836 #8 0xc0793d17 in ieee80211_beacon_construct (m=0xc2edca00, frm=0xc2f0516e "", bo=0xc2d5f884, ni=0xc2ceb000) at /usr/src/sys/net80211/ieee80211_output.c:2559 #9 0xc07946db in ieee80211_beacon_alloc (ni=0xc2ceb000, bo=0xc2d5f884) at /usr/src/sys/net80211/ieee80211_output.c:2756 #10 0xc050eaea in ath_newstate (vap=0xc2d5f000, nstate=IEEE80211_S_RUN, arg=-1) at /usr/src/sys/dev/ath/if_ath.c:2641 #11 0xc0798db1 in ieee80211_newstate_cb (xvap=0xc2d5f000, npending=3) at /usr/src/sys/net80211/ieee80211_proto.c:1654 #12 0xc06ebf92 in taskqueue_run (queue=0xc2a84c80) at /usr/src/sys/kern/subr_taskqueue.c:239 #13 0xc06ec19d in taskqueue_thread_loop (arg=0xc2ada074) at /usr/src/sys/kern/subr_taskqueue.c:360 #14 0xc068a331 in fork_exit (callout=0xc06ec0e0 , arg=0xc2ada074, frame=0xd2f42d38) at /usr/src/sys/kern/kern_fork.c:843 #15 0xc0899bb0 in fork_trampoline () at /usr/src/sys/i386/i386/exception.s:270 (kgdb) dmesg is: Copyright (c) 1992-2010 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 is a registered trademark of The FreeBSD Foundation. FreeBSD 8.0-STABLE #0: Wed Apr 14 07:45:45 MSD 2010 r...@serv01:/usr/obj/usr/src/sys/serv01 i386 Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: AMD Athlon(tm) 64 X2 Dual Core Processor 4200+ (2194.76-MHz 686-class CPU) Origin = "AuthenticAMD" Id = 0x40fb2 Family = f Model = 4b Stepping = 2 Features=0x178bfbff Features2=0x2001 AMD Features=0xea500800 AMD Features2=0x1f real memory = 536870912 (512 MB) avail memory = 449187840 (428 MB) ACPI APIC Table: <050407 APIC1334> FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs FreeBSD/SMP: 1 package(s) x 2 core(s) cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 ioapic0 irqs 0-23 on motherboard kbd1 at kbdmux0 acpi0: <050407 RSDT1334> on motherboard acpi0: [ITHREAD] acpi0: Power Button (fixed) acpi0: reservation of fee0, 1000 (3) failed acpi0: reservation of ffb8, 8 (3) failed acpi0: reservation of fff8, 8 (3) failed acpi0: reservation of 0, a (3) failed acpi0: reservation of 10, 1bf0 (3) failed ACPI HPET table warning: Sequence is non-zero (2) Timecounter "ACPI-safe" frequency 3579545 Hz quality 850 acpi_timer0: <32-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0 cpu0: on acpi0 cpu1: on acpi0 acpi_hpet0: iomem 0xfed0-0xfed003ff on acpi0 Timecounter "HPET" frequency 14318180 Hz quality 900 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pcib1: at device 1.0 on pci0 pci1: on pcib1 vgapci0: port 0xc000-0xc0ff mem 0xf800-0xfbff,0xfe7f-0xfe7f,0xfe60-0xfe6f irq 18 at device 5.0 on pci1 pcib2: at device 7.0 on pci0 pci2: on pcib2 re0: port 0xd800-0xd8ff mem 0xfe8ff000-0xfe8f irq 19 at device 0.0 on pci2 re0: Using 1 MSI messages re0: Chip rev. 0x3400 re0: MAC
Re: ath0: kernel panic when adhoc mode.
Hello, Johann Hugo! > > when I do: > > # ifconfig wlan0 create wlandev ath0 wlanmode adhoc > > > > I remember a colleague of mine having a similar problem. I think he > eventually > tried a workaround by doing it in two commands. Try to split it up to see if > it works. > > #ifconfig wlan0 create wlandev ath0 > #ifconfig wlan0 wlanmode adhoc Thanks for your reply! But no luck: # ifconfig wlan0 wlanmode adhoc ifconfig: wlanmode: bad value and: # ifconfig -m ath0|grep -c adhoc 80 -- Olexandr Lystopad ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: ath0: kernel panic when adhoc mode.
Hello, Johann Hugo! On Wed, Apr 14, 2010 at 04:19:01PM +0200 jh...@meraka.csir.co.za wrote about "Re: ath0: kernel panic when adhoc mode.": > On Wednesday 14 April 2010 02:57:35 pm Lystopad Olexandr wrote: > > But no luck: > > # ifconfig wlan0 wlanmode adhoc > > ifconfig: wlanmode: bad value > > > > Oops, should be: > # ifconfig wlan0 mediaopt adhoc # ifconfig wlan0 mediaopt adhoc ifconfig: SIOCSIFMEDIA (media): Device not configured :-( -- Olexandr Lystopad ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: ath0: kernel panic when adhoc mode.
Hello, Paul B Mahol! On Sun, Apr 18, 2010 at 10:20:26AM + one...@gmail.com wrote about "Re: ath0: kernel panic when adhoc mode.": > On 4/14/10, Lystopad Olexandr wrote: > > Hi! > > > > I install 8.0 FreeBSD, upgrade it to yesturday stable. > > I need to create wireless link in adhoc mode. > > Help me to do this. > > > > > > I put a wireless card into this box: > > > > a...@pci0:3:3:0:class=0x02 card=0xcc2114b9 chip=0x0013168c > > rev=0x01 hdr=0x00 > > vendor = 'Atheros Communications Inc.' > > device = '802.11a/b/g Wireless Adapter (AR5212)' > > class = network > > subclass = ethernet > > cap 01[44] = powerspec 2 supports D0 D3 current D0 > > > > > > > > when I do: > > # ifconfig wlan0 create wlandev ath0 wlanmode adhoc > > > > server reboot with kernel panic: > > > > Fatal trap 12: page fault while in kernel mode > > cpuid = 1; apic id = 01 > > fault virtual address = 0x > > fault code = supervisor read, page not present > > instruction pointer = 0x20:0xc0791612 > > stack pointer = 0x28:0xd2f42ba4 > > frame pointer = 0x28:0xd2f42bac > > 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 (ath0 taskq) > > trap number = 12 > > panic: page fault > > cpuid = 1 > > Uptime: 3m35s > > Physical memory: 439 MB > > Dumping 80 MB: 65 49 33panic: bufwrite: buffer is not busy??? > > cpuid = 1 > > 17 1 > > > > #0 doadump () at pcpu.h:246 > > 246 pcpu.h: No such file or directory. > > in pcpu.h > > (kgdb) #0 doadump () at pcpu.h:246 > > #1 0xc06b3497 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:416 > > #2 0xc06b3789 in panic (fmt=Variable "fmt" is not available. > > ) at /usr/src/sys/kern/kern_shutdown.c:579 > > #3 0xc08b63bc in trap_fatal (frame=0xd2f42b64, eva=65535) > > at /usr/src/sys/i386/i386/trap.c:938 > > #4 0xc08b6620 in trap_pfault (frame=0xd2f42b64, usermode=0, eva=65535) > > at /usr/src/sys/i386/i386/trap.c:851 > > #5 0xc08b6f39 in trap (frame=0xd2f42b64) at > > /usr/src/sys/i386/i386/trap.c:533 > > #6 0xc0899b3b in calltrap () at /usr/src/sys/i386/i386/exception.s:165 > > #7 0xc0791612 in ieee80211_getcapinfo (vap=0xc2d5f000, chan=0x) > > at /usr/src/sys/net80211/ieee80211_output.c:1836 > > #8 0xc0793d17 in ieee80211_beacon_construct (m=0xc2edca00, > > frm=0xc2f0516e "", bo=0xc2d5f884, ni=0xc2ceb000) > > at /usr/src/sys/net80211/ieee80211_output.c:2559 > > #9 0xc07946db in ieee80211_beacon_alloc (ni=0xc2ceb000, bo=0xc2d5f884) > > at /usr/src/sys/net80211/ieee80211_output.c:2756 > > #10 0xc050eaea in ath_newstate (vap=0xc2d5f000, nstate=IEEE80211_S_RUN, > > arg=-1) at /usr/src/sys/dev/ath/if_ath.c:2641 > > #11 0xc0798db1 in ieee80211_newstate_cb (xvap=0xc2d5f000, npending=3) > > at /usr/src/sys/net80211/ieee80211_proto.c:1654 > > #12 0xc06ebf92 in taskqueue_run (queue=0xc2a84c80) > > at /usr/src/sys/kern/subr_taskqueue.c:239 > > #13 0xc06ec19d in taskqueue_thread_loop (arg=0xc2ada074) > > at /usr/src/sys/kern/subr_taskqueue.c:360 > > #14 0xc068a331 in fork_exit (callout=0xc06ec0e0 , > > arg=0xc2ada074, frame=0xd2f42d38) at /usr/src/sys/kern/kern_fork.c:843 > > #15 0xc0899bb0 in fork_trampoline () at > > /usr/src/sys/i386/i386/exception.s:270 > > (kgdb) > > > > This is bug, please report it ASAP. Thanks. Done. http://www.freebsd.org/cgi/query-pr.cgi?pr=145826 -- Olexandr Lystopad ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
