reproducible panic on 8.2-RELEASE, but no core file
Hi, I'm experiencing a reproducible kernel panic that would be really nice to debug, but unfortunately no core file is getting generated. I don't have console access either. All I can get so far is this, from syslog: Aug 23 19:51:38 estranged kernel: Aug 23 19:51:38 estranged kernel: Fatal double fault: Aug 23 19:51:38 estranged kernel: eip = 0xc0593b2e Aug 23 19:51:38 estranged kernel: esp = 0xe5583fe4 Aug 23 19:51:38 estranged kernel: ebp = 0xe5584010 Aug 23 19:51:38 estranged kernel: cpuid = 0; apic id = 00 Aug 23 19:51:38 estranged kernel: panic: double fault Aug 23 19:51:38 estranged kernel: cpuid = 0 Aug 23 19:51:38 estranged kernel: panic: 0xc4263b40 must be migratable Aug 23 19:51:38 estranged kernel: cpuid = 0 Aug 23 19:51:38 estranged kernel: panic: 0xc4263b40 must be migratable Aug 23 19:51:38 estranged kernel: cpuid = 0 [SNIP - above two lines repeated alot] Aug 23 19:51:38 estranged kernel: cpuid = 0kernel trap 12 with interrupts disabled Aug 23 19:51:38 estranged kernel: panic: Aug 23 19:51:38 estranged kernel: 0xc4263b40 must be migratablekernel trap 12 with interrupts disabled Aug 23 19:51:38 estranged kernel: kernel trap 12 with interrupts disabled Aug 23 19:51:38 estranged kernel: cpuid = 0 Aug 23 19:51:38 estranged kernel: kernel trap 12 with interrupts disabled Aug 23 19:51:38 estranged kernel: panic: My dumpdev is set: $ ls -l /dev/dumpdev lrwxr-xr-x 1 root wheel 11 Aug 23 19:56 /dev/dumpdev@ -> /dev/ad4s1b But savecore reports: Aug 23 19:56:34 estranged kernel: No core dumps found. Any advice for getting a core file? :) Thanks, Aragon ___ 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"
please review my openssl build patch
http://www.freebsd.org/cgi/query-pr.cgi?pr=168396 ___ 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"
FreeBSD on Intel DH55TC?
Hi, Please could anyone share their experiences with 8-STABLE on an Intel DH55TC motherboard? Looking to use one soon. :) Thanks, Aragon ___ 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: Intel G33 & FreeBSD 7.x
| By Daniel O'Connor <[EMAIL PROTECTED]> | [ 2008-08-18 09:47 +0200 ] > Does anyone have a G33 chipset system working in 7.x? > > I have a 6.3 install here and it isn't working with that so I have been > merging things from HEAD but it still doesn't work. > > It would be worth switching to 7.x if it worked there though :) I'm using an Intel branded G33 board with 7.0-STABLE. Works better than the MSI G33 board I tried first... Copyright (c) 1992-2008 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.0-STABLE #5: Thu May 15 21:13:01 SAST 2008 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/IGOR Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel(R) Core(TM)2 Duo CPU E8500 @ 3.16GHz (3185.32-MHz K8-class CPU) Origin = "GenuineIntel" Id = 0x10676 Stepping = 6 Features=0xbfebfbff Features2=0x8e3fd> AMD Features=0x20100800 AMD Features2=0x1 Cores per package: 2 usable memory = 8509808640 (8115 MB) avail memory = 8225095680 (7844 MB) ACPI APIC Table: Regards, Aragon ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: FreeBSD 7.1 Content
| By Dan Allen <[EMAIL PROTECTED]> | [ 2008-09-03 23:06 +0200 ] > FreeBSD from the machine and installed Ubuntu 8.04. I therefore > cannot run "pciconf -l" at this moment in time, but I may get back > around to it. lspci ? Regards, Aragon ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Keyspan USB serial adapter
Hi, I'm on the market for a USB serial adapter. The Keyspan USA-19HS gets a lot of good reviews for its performance, but I've noticed previous Keyspan models have a history of not supporting FreeBSD due to firmware issues. The 19HS is listed in /usr/src/sys/dev/usb/usbdevs with nothing noted about firmware (as opposed to the older 19WQ). Can I assume that the firmware problems of the past aren't relevant to the current 19HS? Can anyone confirm if a USA-19HS works on FreeBSD 7-STABLE right now? Thanks, Aragon ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Keyspan USB serial adapter
| By Richard Arends <[EMAIL PROTECTED]> | [ 2008-09-17 07:05 +0200 ] > On Tue, Sep 16, 2008 at 09:24:26PM -0700, Jeremy Chadwick wrote: > > > Since you're still in the market: I've heard wonderful things about any > > of the USB serial adapters that use the Prolific chip; see uplcom(4). > > I can second that. I use a Sitecom CN-104 (also Prolific) with several > devices like Sun hardware and Soekris/Wrap systems boards and it al works > perfectly (FreeBSD/Linux and Windows). Thanks. I decided to not take a chance and ordered a Prolific based Iogear adapter. :) Thanks, Aragon (who wishes laptops still had com ports) ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Upcoming Releases Schedule...
>From what I've gathered so far... | By Jo Rhett <[EMAIL PROTECTED]> | [ 2008-09-20 02:46 +0200 ] > To get a business to commit resources to a project there must be an > actual goal. [1] The FreeBSD project would have to commit resources too. Its community that provides those resources need to see tangible work that is useful to the project before committing any resources to it. > And to reach that actual goal there must be both (a) a > plan to get there, (b) a reasoned assessment of the effort involved, > etc etc and (z) the effort taking place to reach that goal. For (a), (b), and (z), this is where you come in. Define the goal. Make a plan to get there. Assess the effort involved. Convince your employer that (a), (b) and (z) is worth it to him/her and that the result of (z) will convince the FreeBSD project to commit the resources needed to integrate it. If they're happy, start working on (z) and bring it to the FreeBSD project when you think it's ready. If the FreeBSD project has to be involved in (a), (b), or (z), it will have to commit its own resources to the effort. See [1]. Just my humble observation as a fellow FreeBSD user... Regards, Aragon ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: "mount -u -o ro" problems with 7-stable
| By Oliver Fromme <[EMAIL PROTECTED]> | [ 2008-10-17 15:29 +0200 ] > > This is believed to be fixed for HEAD. I do not want to do MFC > > before 7.1. > > OK, that's good news. Thanks for the information. > So I'll watch the commit messages for the MFC after 7.1. I hit my head against this a while ago too, and it has been PR'd: http://www.freebsd.org/cgi/query-pr.cgi?pr=121809 I'll be watching out for the fix too. Thanks to all those involved in fixing it! Regards, Aragon ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 6.4 RC1 locks up solid on first reboot
| By Jo Rhett <[EMAIL PROTECTED]> | [ 2008-10-24 21:13 +0200 ] > On Oct 22, 2008, at 9:27 PM, Milan Obuch wrote: > >I did not investigate on this issue too much, but there is an > >workaround - > >copy older /boot/loader over newer one. In my case, I am rebuilding > >whole > >world often, and now /boot/loader seems to not build correctly for > >me. Older > >one is ~ 250 kB, rebuilt will be ~ 185 kB, and freezes. > > 6.4's boot loader is 221k > 6.3's boot loader is 217k > > Copying 6.3 boot loader to the 6.4 solved the keyboard lockup problem, > but it still panics during the boot. At last now I get the entire > panic to the serial console so I can cut/paste. FWIW, I've had problems with 7.0's boot loader locking up too. I'm running a -stable compile from march and during bootup, if I make too many keypresses the bootup sequence freezes. Once loader has handed off to the kernel then everything's fine, but I can't make any use of loader's or bootX's command lines without the system freezing. I'm careful not to touch my keyboard during bootup! Keyboard and mouse are both USB. Regards, Aragon ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 6.4 RC1 locks up solid on first reboot
| By Jeremy Chadwick <[EMAIL PROTECTED]> | [ 2008-10-25 03:22 +0200 ] > > FWIW, I've had problems with 7.0's boot loader locking up too. I'm running > > a -stable compile from march and during bootup, if I make too many > > keypresses the bootup sequence freezes. Once loader has handed off to the > > kernel then everything's fine, but I can't make any use of loader's or > > bootX's command lines without the system freezing. I'm careful not to touch > > my keyboard during bootup! > > > > Keyboard and mouse are both USB. > > There are known problems with some BIOSes and "USB Legacy" support. > Said BIOS option allows a USB keyboard and mouse to be emulated as PS/2 > for operating systems which lack a USB stack, such as MS-DOS -- and more > importantly, bootloaders! The FreeBSD bootloader only understands > AT/PS2 keyboards, which is why that BIOS option is needed. > > Can you confirm this problem happens when using a PS/2 keyboard? Unfortunately, no luck. I've just tried: * USB and PS/2 keyboards both plugged in, enough key input on the PS/2 keyboard causes a freeze * Just the PS/2 keyboard plugged in, no different. * Just the PS/2 keyboard plugged in, and USB legacy disabled in the BIOS. Same. Is it possible that excessive build optimisations could lead to this? Last time I rebuilt I did so with '-O2 -fno-strict-aliasing' and -march in make.conf. I've been meaning to try with a rebuilt loader with no optimisations... > P.S. -- Why are you slamming keys during the bootup sequence? :-) It's my workstation and I'm usually impatient to get through the bootup sequence quickly. :) Regards, Aragon ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 6.4 RC1 locks up solid on first reboot
| By Jeremy Chadwick <[EMAIL PROTECTED]> | [ 2008-10-25 10:09 +0200 ] > Okay, so then the issue is probably with the bootloader in some bizarre > way. John might have some ideas, but I have none (outside of my skill > set). > > Also, it might help if you could explain "enough key input" and "too > many keypresses". These are a little too vague. Did a bit of experimenting now. My system uses the boot0 boot manager. I can't reproduce the keypress freeze issue in any part of boot0, 1, or 2 stages. It only becomes a problem when loader takes over. Once loader takes over the system can freeze at any point if too many keypresses are made at any point while loader is in control - at the prompt, while it's busy pulling the kernel/modules off the disk, any time. The actual amount of too many keypresses is seemingly random. It can freeze with just one keypress, or after the upteenth keypress - my record is about 25 keypresses without freezing. :) Not a fun game if you're trying to use the loader prompt. At one point while I was testing now the display output went translucent red when the system froze after some keypresses. Strange huh? I didn't know transparency was supported in text mode. :) > Anything is possible. Can you please rebuild your system, and the > bootstraps (and don't forget to install them; bsdlabel -B ), > without messing with optimisation flags? Will do. > I'm still having trouble understanding what you're talking about or > why you're doing this. > > I *think* what you're trying to say is something like: "when my machine > boots up, I don't like waiting 10 seconds at the Beastie/loader menu, so > I hit Enter to skip the counterdown". Please clarify. :-) You are correct. I usually whack enter 3 times or so straight after BIOS post to eliminate boot0's, boot2's, and loader's timeouts. Regards, Aragon ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
compliments to the chef(s)!
Hi, I just updated a 7.0-RELEASE system to 7.1-PRERELEASE. Everything went smoothly. This is on an HP Pavilion dv2600 notebook. In particular I am beyond happy with the new linux emulation updates! I saw all the relevant patches have been committed to RELENG_7 now so I didn't have to do any manual patching. I take it this means 7.1-RELEASE will launch with them? In any case, for the first time in my history of using BSD as a workstation OS have I finally been able to have a fully working flash setup. BIG thanks to everyone that made it happen - this is going to make 7.1 rock. Regards, Aragon ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Script-friendly (parseble) ps(1) output?
| By Eduardo Meyer <[EMAIL PROTECTED]> | [ 2008-10-30 00:04 +0200 ] > Hello, > > I need to write a cgi script which will print the output from ps(1) in > a table (html), so the average-operator can click on a KILL link and > the cgi will send the selected signal. > > I need to add one ps information per column in a table (html), > however, I found ps(1) output to be too hard to parse. There is no > separator. I believed \t was the separator but its not. Another option might be to mount /proc and use that instead. See procfs(5). Regards, Aragon ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 6.4 RC1 locks up solid on first reboot
Hi, | By Jeremy Chadwick <[EMAIL PROTECTED]> | [ 2008-10-25 10:09 +0200 ] > Anything is possible. Can you please rebuild your system, and the > bootstraps (and don't forget to install them; bsdlabel -B ), > without messing with optimisation flags? I just upgraded to 7.1 today. No luck, even with loader compiled without optimisations, it is still unstable on my system for some reason. No biggie for me, but possibly worthy of investigation if others have similar problems. (my hardware is quite new still) I'm more than open to help troubleshoot this further if you (or anyone) has any ideas on what to try next. Regards, Aragon ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 6.4 RC1 locks up solid on first reboot
| By Aragon Gouveia <[EMAIL PROTECTED]> | [ 2008-11-01 08:43 +0200 ] > > Anything is possible. Can you please rebuild your system, and the > > bootstraps (and don't forget to install them; bsdlabel -B ), > > without messing with optimisation flags? > > I just upgraded to 7.1 today. No luck, even with loader compiled without > optimisations, it is still unstable on my system for some reason. No > biggie for me, but possibly worthy of investigation if others have similar > problems. (my hardware is quite new still) > > I'm more than open to help troubleshoot this further if you (or anyone) has > any ideas on what to try next. Quick (progressive) update! I thought I'd see how loader behaves on my various boot CDs. My 7.0-RELEASE discs both work fine - loader doesn't freeze. My 7.1-BETA2 disc's loader behaves the same as the loader I compile. I've copied the loader binary from one of the 7.0-RELEASE discs onto my system and it works great just like that, and no more freezing. Perhaps a change that happened in RELENG_7 after 7.0-RELEASE is causing this? I've been experiencing it since my RELENG_7 checkout in May this year. Regards, Aragon ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: FreeBSD 7.1-RC1 Available...
Hi, | By Ken Smith | [ 2008-12-10 04:40 +0200 ] > In addition to general testing we're looking for information about > potential problems with the boot loader. There has been traffic here > about problems but the reports haven't helped narrow down the causes > yet. So far it seems to be related to USB keyboards and at least so far > systems with more than one processor in them. More data points like > cases where a USB keyboard was not involved as well as if possible > things like which motherboard it is might help us narrow down the cause. > Testing on a variety of motherboards, of varying ages and manufacturers > would help. I have been experiencing problems with loader(8) on my system. Essentially it freezes the system if "too much" keyboard input is given. Please see these posts for more background: http://lists.freebsd.org/pipermail/freebsd-stable/2008-October/046176.html http://lists.freebsd.org/pipermail/freebsd-stable/2008-October/046189.html http://lists.freebsd.org/pipermail/freebsd-stable/2008-November/046337.html I've just tested booting up with an i386 RC1 disc and the problem is still there. My motherboard is an Intel DG33BU. Regards, Aragon ___ 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: immense delayed write to file system (ZFS and UFS2), performance issues
On 01/18/10 22:13, O. Hartmann wrote: Symptome: All boxes have ZFS and UFS2 filesystems. Since two weeks or so, sometimes the I/O performance drops massively when doing 'svn update', 'make world' or even 'make kernel'. It doesn't matter what memory and how many cpu the box has, it get stuck for several seconds and freezing. On the UP box, this is sometimes for 10 - 20 seconds. A very interesting phenomenon is the massively delayed file writing on ZFS filesystems I realise. Editing a file in 'vi' running on one XTerm and having in another Xterminal my shell for compiling this file, it takes sometimes up to 20 seconds to get the file updated after it has been written. It's like having an old, slow NFS connection with long cache delays. These massively delayed file transactions are not necessarely under heavy load, sometimes they occur in a relaxed situation. They seem to occur much more often on the UP box than on the SMP boxes, but this strange phenomenon also occur on the Dell Poweredge II, which has 16GB RAM and summa summarum 16 cores. This phenomenon does occur on ZFS- and UFS2 filesystems as well. It is hardly reproducable. I'm experiencing the same thing, except in my case it's most noticeable when writing to a USB flash drive with a FAT32 filesystem. It slows the entire system down, even if the data being written is coming from cache or a memory file system. I don't know if it's related. I'm running 8-STABLE from about 4 December. Regards, Aragon ___ 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: Expresscard Wireless
Hi, I just purchased the Ubiquiti SRX and can confirm that it works under FreeBSD 7. It doesn't seem to handle ejections or hotplugging though. Regards, Aragon | By Michael Lankton <[EMAIL PROTECTED]> | [ 2008-02-12 17:57 +0200 ] > I bought a laptop with no PCMCIA slot, just expresscard. Instead of > using a usb dongle for wireless, I would like to use an expresscard if > possible. Ubiquiti makes one that uses atheros chip. > > Has anyone successfully used an expresscard wifi card in FreeBSD? Any > info? > > Thanks ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
sound hosed on 7.0-STABLE/amd64 ?
Hi, I'm running an amd64 install of 7.0-STABLE. Sound is behaving strangely. I'm trying to get either uaudio or snd_hda working, but am not having joy with either. The kernel detects the devices, but /dev/dsp* entries aren't created or take a long time to appear. And, of course, sound playback doesn't work either. Kernel output attached. Anyone know what could be up? Thanks, Aragon May 11 15:31:49 igor kernel: uaudio0: on uhub4 May 11 15:31:49 igor kernel: uaudio0: audio rev 1.00 May 11 15:31:49 igor kernel: pcm0: on uaudio0 May 11 15:49:09 igor kernel: pcm1: mem 0xe032-0xe0323fff irq 22 at device 27.0 on pci0 May 11 15:49:09 igor kernel: pcm1: [ITHREAD] May 11 15:49:09 igor kernel: pcm1: May 11 15:49:09 igor kernel: pcm1: May 11 15:49:09 igor kernel: pcm2: mem 0xe021-0xe0213fff irq 17 at device 0.1 on pci1 May 11 15:49:09 igor kernel: pcm2: [ITHREAD] May 11 15:49:09 igor kernel: pcm2: May 11 15:49:09 igor kernel: pcm2: ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: sound hosed on 7.0-STABLE/amd64 ?
Hi again, I guess I should have spent more time troubleshooting. Sound is working now. I spent the last 30 minutes testing it with 6.3-RELEASE and 7.0-RELEASE livecds on two different machines. Ended up tracing my uaudio dysfunctionality to a dodgy USB hub! Onboard HDA was just a matter of setting the right options in the BIOS. All's good on both fronts. Sorry for the false alarm. Regards, Aragon | By Aragon Gouveia <[EMAIL PROTECTED]> | [ 2008-05-11 16:29 +0200 ] > Hi, > > I'm running an amd64 install of 7.0-STABLE. Sound is behaving strangely. > I'm trying to get either uaudio or snd_hda working, but am not having joy > with either. The kernel detects the devices, but /dev/dsp* entries aren't > created or take a long time to appear. And, of course, sound playback > doesn't work either. > > Kernel output attached. Anyone know what could be up? > > > Thanks, > Aragon > > > May 11 15:31:49 igor kernel: uaudio0: Audio CODEC, class 0/0, rev 1.10/1.00, addr 5> on uhub4 > May 11 15:31:49 igor kernel: uaudio0: audio rev 1.00 > May 11 15:31:49 igor kernel: pcm0: on uaudio0 > May 11 15:49:09 igor kernel: pcm1: Audio Controller> mem 0xe032-0xe0323fff irq 22 at device 27.0 on pci0 > May 11 15:49:09 igor kernel: pcm1: [ITHREAD] > May 11 15:49:09 igor kernel: pcm1: > May 11 15:49:09 igor kernel: pcm1: 20071129_0050> > May 11 15:49:09 igor kernel: pcm2: Audio Controller> mem 0xe021-0xe0213fff irq 17 at device 0.1 on pci1 > May 11 15:49:09 igor kernel: pcm2: [ITHREAD] > May 11 15:49:09 igor kernel: pcm2: > May 11 15:49:09 igor kernel: pcm2: 20071129_0050> > ___ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
instability with gmirror and atacontrol spindown
Hi, I eagerly started using atacontrol's new spindown command the other day. There's a gmirror volume running on top of the two disks that get spundown. I find that often when the drives are spun back up to serve a disk request, one of the ata devices times out and my system goes into a never ending loop of retrying. At that point I'm lucky if I'm able to shutdown gracefully. This is what is logged on the console after the disk spin up message: ad8: WARNING - SETFEATURES SET TRANSFER MODE taskqueue timeout - completing request directly ad8: WARNING - SETFEATURES SET TRANSFER MODE taskqueue timeout - completing request directly ad8: WARNING - SETFEATURES ENABLE RCACHE taskqueue timeout - completing request directly ad8: WARNING - SETFEATURES ENABLE RCACHE taskqueue timeout - completing request directly ad8: WARNING - SET_MULTI taskqueue timeout - completing request directly ad8: TIMEOUT - READ_DMA retrying (1 retry left) LBA=20047817 ad8: WARNING - SETFEATURES SET TRANSFER MODE taskqueue timeout - completing request directly ad8: WARNING - SETFEATURES SET TRANSFER MODE taskqueue timeout - completing request directly ad8: WARNING - SETFEATURES ENABLE RCACHE taskqueue timeout - completing request directly ad8: WARNING - SETFEATURES ENABLE RCACHE taskqueue timeout - completing request directly ad8: WARNING - SET_MULTI taskqueue timeout - completing request directly ad8: TIMEOUT - READ_DMA retrying (0 retries left) LBA=20047817 I can only reproduce it when my gmirror volume is running. Any ideas? Thanks, Aragon ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: UMASS problem on 7.0 STABLE
Hi, | By Ronald Klop <[EMAIL PROTECTED]> | [ 2008-07-09 11:51 +0200 ] > It might be something else, but I had usb problems in 6-STABLE until I > disabled usb support in the bios. FreeBSD still detects the usb hardware. > In my case there was some sort of conflict between the usb detection of > the bios and the detection FreeBSD. > The symptoms where very weird, because it also depended on the connected > usb devices on time of boot. Connecting theme after booting did work. I have a similar problem. If I boot up with a umass device connected, my 7.0-STABLE system core dumps when hald starts. http://www.freebsd.org/cgi/query-pr.cgi?pr=123714 I guess don't boot up with a umass device plugged in. :) Regards, Aragon ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: reecommendations for an 'appliance" platform ?
Hi, Pete French wrote: I'm not 100% sure, but fairly sure that you'll have a hard time finding something that combines the low-power standalone type spec with a 64-bit capable processor. Once you get the higher-end processor, That was my experiense when shopping around yes - annoying as I don't need anything particularly low power (it ain't going to be my leccy bill :-). The Atom 230 and 330 are supposed to be 64-bit capable: http://ark.intel.com/Compare.aspx?ids=36331,35635,35641, but I have not personally tested either with an AMD64 FreeBSD install. It needs to be: 1) Complete as purchased - I dont want to build a machine 2) Capable of having a simple boot device (e.g. CF card) dropped in 3) At least one ether port. 100 meg will do. 4) Small enough to be posted to the end user 5) Cheap - under 400 euros, preferably 300 You might consider something like this: http://www.tranquilpc-shop.co.uk/acatalog/T7-330_Barebones.html Or this which is rack mountable: http://www.tranquilpc-shop.co.uk/acatalog/T2e_300atom_nocd.html Both Atom 330 based and prebuilt. No affiliation with them, but I almost ordered one and found their support to be responsive and helpful. :) Regards, Aragon ___ 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: reecommendations for an 'appliance" platform ?
Pete French wrote: http://www.tranquilpc-shop.co.uk/acatalog/T7-330_Barebones.html Now *that* is very much what I am thinking of - OK, I will need to drop in a CF->SATA along with the card, but thats not much hassle. 64 bit and I can add in more RAM than on the other. Thanks, I hadn't realised the new ATonms did 64 bit. No, I don't think you will need a CF->SATA adapter. A simple CF->ATA adapter should do. Those systems just have an Intel GCLF2 board in them, which has both SATA and ATA: http://www.intel.com/products/desktop/motherboards/D945GCLF2-D945GCLF2D/D945GCLF2-D945GCLF2D-overview.htm Best you mail them to confirm though... They're also fanless. :) Regards, Aragon ___ 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: reecommendations for an 'appliance" platform ?
TJ Varghese wrote: They're also fanless. :) Chipset has a fan, however the processor itself is fanless. I've read You are correct about the Intel GCLF2, however I was talking specifically about the tranquil system. They build their systems to be fanless, so I assume they remove the stock heatsinks/fans. The systems are quite heavy if you look at the specs, so the casing is probably a big heatsink. Regards, Aragon ___ 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"
out of place syslog entries
Hi, Jun 5 00:22:47 root postfix/smtpd[57574] Jun 5 00:22:47 root postfix/qmgr[55069] Jun 5 00:22:47 root postfix/local[57577] Jun 5 00:22:48 root imapd[57576] Jun 5 00:22:48 root imapd[57576] Jun 5 00:22:49 root imapd[57576] Jun 5 00:22:55 root imapd[56177] Jun 5 00:22:58 root imapd[57629] Jun 5 00:23:00 root postfix/smtp[57515] Jun 5 00:23:00 root postfix/smtp[57515] Jun 4 22:25:25 root postfix/smtpd[57772] Jun 4 22:25:25 root postfix/smtpd[57772] Jun 4 22:25:25 root postfix/smtpd[57772] Jun 4 22:25:45 root postfix/smtpd[57772] Jun 4 22:25:46 root postfix/smtpd[57772] Jun 4 22:25:52 root postfix/smtpd[57772] Jun 4 22:30:19 root postfix/smtpd[58118] Jun 4 22:30:20 root postfix/smtpd[58118] Jun 4 22:30:20 root postfix/smtpd[58118] Jun 4 22:30:23 root postfix/smtpd[58118] Jun 4 22:30:23 root postfix/smtpd[58118] Jun 4 22:30:29 root postfix/smtpd[58118] Jun 5 00:42:03 root postfix/smtpd[58916] Jun 5 00:42:03 root postfix/smtpd[58916] Jun 5 00:42:03 root postfix/smtpd[58916] Jun 5 00:42:03 root postfix/smtpd[58916] Jun 5 00:42:03 root postfix/cleanup[58917] Jun 5 00:42:03 root postfix/qmgr[55069] Jun 5 00:42:03 root postfix/smtpd[58916] Jun 5 00:42:46 root postfix/smtp[58919] I've removed the actual message to protect the innocent. What I'm getting at is the log entry for 2 hours in the past being added in the middle of the present. Is this a bug or a feature? Thanks, Aragon To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Compiling a New Kernel
| By Jamie Heckford <[EMAIL PROTECTED]> | [ 2002-10-11 11:13 +0200 ] > Bizarre how could it be different/not work if you have cvsup'd all of your >sources including sys/ tree at exactly the same time, > and compile your kernel just after the installworld? Ideally you should build, install, and boot your new kernel before installing your new world. If your new kernel fails to boot for whatever reason, you can easily boot the old kernel and have a fully functional system again. If you installworld before verifying your new kernel, you could run into worse problems if your new kernel doesn't load and you have to boot the old kernel with your new world. Regards, Aragon To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
