Re: FreeBSD-6.2, 7.0-BETA1 on X60
Hello All,
After I follow below instruction it boot kernel, but then give me error says
/etc/fstab not found etc.,
I will attach it next email.
Balgaa
- Original Message -
From: "Alexandre "Sunny" Kovalenko" <[EMAIL PROTECTED]>
To: "Balgansuren Batsukh" <[EMAIL PROTECTED]>
Cc:
Sent: Tuesday, December 04, 2007 12:19 PM
Subject: Re: FreeBSD-6.2, 7.0-BETA1 on X60
On Mon, 2007-12-03 at 21:31 +0800, Balgansuren Batsukh wrote:
Hello All,
I tried to install FreeBSD on X60 using PXE boot, but unsuccessfully
finish
my attempt.
When it start PXE boot it get IP address from DHCP, download PXE boot
file
from TFTP server,
then trying to load kernel image from TFTP server.
After 10-20 minutes it give me error message "can't load kernel", I tried
many times load boot/kernel/kernel, but same result.
I guess PXE boot read much longer time to load kernel file and suddenly
give
me error message.
I followed instruction on http://www.hack.org/mc/freebsd-x60.html
I made X60>LAN switch>TFTP/DHCP/NFS server and even tried
X60---cross-over cable>TFTP/DHCP/NFS server.
Is there any suggestion?
I have built my X60 from such a setup and then used it as the "FixIt"
environment more then a few times. Here are relevant bits from the
server (watch out for the line wrapping):
=== /usr/local/etc/dhcpd.conf (I am using isc-dhcp3-server-3.0.5_2)
option domain-name "rabbitslawn.verizon.net";
option domain-name-servers rabbitslawn.verizon.net;
default-lease-time 600;
max-lease-time 7200;
authoritative;
ddns-update-style none;
log-facility local7;
server-name "twinhead";
server-identifier 10.0.3.236;
next-server 10.0.3.236;
subnet 10.0.3.0 netmask 255.255.255.0 {
range 10.0.3.33 10.0.3.64;
option routers 10.0.3.242;
option domain-name-servers 10.0.3.242;
option root-path "/SHARED/tftpboot";
filename "boot/pxeboot";
}
=== /etc/exports (excerpt)
/SHARED -alldirs
=== /etc/inetd.conf (excerpt)
tftpdgram udp waitroot/usr/libexec/tftpd tftpd -u
sunny -l -s /SHARED/tftpboot
=== /etc/rc.conf (excerpt)
nfs_server_enable="YES"
rpcbind_enable="YES"
=== /SHARED/tftpboot
Contains fairly old (February 2007) snapshot of then 7-CURRENT with two
modifications
=== /SHARED/tftpboot/boot/loader.rc
echo Loading Kernel...
load /boot/kernel/kernel
echo Loading mfsroot...
load -t mfs_root /mfsroot
echo booting...
echo \007\007
echo initializing h0h0magic...
set vfs.root.mountfrom="ufs:/dev/md0c"
boot
=== /SHARED/tftpboot/mfsroot
Is the decompressed version of /SHARED/tftpboot/boot/mfsroot.gz.
I can confirm that stopping NFS on the server will give the symptoms
roughly corresponding to the ones you are describing, so the first thing
I would recommend checking is the ability to mount your equivalent of
the "/SHARED/tftpboot" above.
Hopefully this is all I have done to get this to work -- I have picked
most of it from someone's web page, but I could not find original URL
ATM.
Regards,
Balgaa
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
--
Alexandre "Sunny" Kovalenko <[EMAIL PROTECTED]>
--
No virus found in this incoming message.
Checked by AVG Free Edition.
Version: 7.5.503 / Virus Database: 269.16.13/1165 - Release Date:
12/2/2007 8:34 PM
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: FreeBSD-6.2, 7.0-BETA1 on X60
On Mon, 2007-12-03 at 21:31 +0800, Balgansuren Batsukh wrote:
> Hello All,
>
> I tried to install FreeBSD on X60 using PXE boot, but unsuccessfully finish
> my attempt.
>
> When it start PXE boot it get IP address from DHCP, download PXE boot file
> from TFTP server,
> then trying to load kernel image from TFTP server.
>
> After 10-20 minutes it give me error message "can't load kernel", I tried
> many times load boot/kernel/kernel, but same result.
>
> I guess PXE boot read much longer time to load kernel file and suddenly give
> me error message.
>
> I followed instruction on http://www.hack.org/mc/freebsd-x60.html
>
> I made X60>LAN switch>TFTP/DHCP/NFS server and even tried
> X60---cross-over cable>TFTP/DHCP/NFS server.
>
> Is there any suggestion?
I have built my X60 from such a setup and then used it as the "FixIt"
environment more then a few times. Here are relevant bits from the
server (watch out for the line wrapping):
=== /usr/local/etc/dhcpd.conf (I am using isc-dhcp3-server-3.0.5_2)
option domain-name "rabbitslawn.verizon.net";
option domain-name-servers rabbitslawn.verizon.net;
default-lease-time 600;
max-lease-time 7200;
authoritative;
ddns-update-style none;
log-facility local7;
server-name "twinhead";
server-identifier 10.0.3.236;
next-server 10.0.3.236;
subnet 10.0.3.0 netmask 255.255.255.0 {
range 10.0.3.33 10.0.3.64;
option routers 10.0.3.242;
option domain-name-servers 10.0.3.242;
option root-path "/SHARED/tftpboot";
filename "boot/pxeboot";
}
=== /etc/exports (excerpt)
/SHARED -alldirs
=== /etc/inetd.conf (excerpt)
tftpdgram udp waitroot/usr/libexec/tftpd tftpd -u
sunny -l -s /SHARED/tftpboot
=== /etc/rc.conf (excerpt)
nfs_server_enable="YES"
rpcbind_enable="YES"
=== /SHARED/tftpboot
Contains fairly old (February 2007) snapshot of then 7-CURRENT with two
modifications
=== /SHARED/tftpboot/boot/loader.rc
echo Loading Kernel...
load /boot/kernel/kernel
echo Loading mfsroot...
load -t mfs_root /mfsroot
echo booting...
echo \007\007
echo initializing h0h0magic...
set vfs.root.mountfrom="ufs:/dev/md0c"
boot
=== /SHARED/tftpboot/mfsroot
Is the decompressed version of /SHARED/tftpboot/boot/mfsroot.gz.
I can confirm that stopping NFS on the server will give the symptoms
roughly corresponding to the ones you are describing, so the first thing
I would recommend checking is the ability to mount your equivalent of
the "/SHARED/tftpboot" above.
Hopefully this is all I have done to get this to work -- I have picked
most of it from someone's web page, but I could not find original URL
ATM.
>
> Regards,
> Balgaa
>
> ___
> freebsd-stable@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "[EMAIL PROTECTED]"
--
Alexandre "Sunny" Kovalenko <[EMAIL PROTECTED]>
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: FreeBSD-6.2, 7.0-BETA1 on X60
On Mon, 3 Dec 2007 21:31:55 +0800 Balgansuren Batsukh wrote: > I tried to install FreeBSD on X60 using PXE boot, but unsuccessfully > finish my attempt. > When it start PXE boot it get IP address from DHCP, download PXE boot > file from TFTP server, > then trying to load kernel image from TFTP server. Did you look at /var/log/xferlog? Is there something interesting? > After 10-20 minutes it give me error message "can't load kernel", I > tried many times load boot/kernel/kernel, but same result. You may try tcpdump/wireshark at the server side (as someone has already suggested). > I guess PXE boot read much longer time to load kernel file and > suddenly give me error message. > I followed instruction on http://www.hack.org/mc/freebsd-x60.html There are many ways to run diskless. I found FreeBSD docs very useful: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/network-diskless.html diskless(8), /usr/share/examples/diskless/clone_root > I made X60>LAN switch>TFTP/DHCP/NFS server and even tried > X60---cross-over cable>TFTP/DHCP/NFS server. WBR -- Boris Samorodov (bsam) Research Engineer, http://www.ipt.ru Telephone & Internet SP FreeBSD committer, http://www.FreeBSD.org The Power To Serve ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: FreeBSD-6.2, 7.0-BETA1 on X60
On Mon, 3 Dec 2007 07:41:49 -0800 Jeremy Chadwick wrote: > I've tried this before myself (on all sorts of different hardware), and > I've never gotten it to work on RELENG_6 or RELENG_7 -- I reach the same > point and receive the same error you do. We use diskless setup in production. It works just fine. Even with pxelinux to select an OS and it's version to boot (the default is to load memtest86). I found very useful /var/log/xferlog to debug errors while booting a diskless station. > It appears to me that that an NFS server is *absolutely* necessary for > all of this to work; TFTP by itself doesn't suffice, it appears. Yes. > I've tried setting LOADER_TFTP_SUPPORT=yes in make.conf (forcing the > entire process to avoid using NFS), but believe it or not, a part of the > booting process still continues to use NFS-related code (or at least the > debugging messages state it's trying to do NFS). I was able to get some > pxeboot-related debugging output (to see the aforementioned) by setting > PXE_DEBUG=true in make.conf (see src/sys/boot/i386/libi386/pxe.c for > details on that). Seems that you slightly misunderstood the meaning of the LOADER_TFTP_SUPPORT option. It is used only to boot a custom kernel (when at stage 2, diskless(8)). Without this option your diskless station should load your servers' kernel. The stage 3 always uses NFS to mount the root directory. WBR -- Boris Samorodov (bsam) Research Engineer, http://www.ipt.ru Telephone & Internet SP FreeBSD committer, http://www.FreeBSD.org The Power To Serve ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: FreeBSD-6.2, 7.0-BETA1 on X60
On Mon, Dec 03, 2007 at 09:31:55PM +0800, Balgansuren Batsukh wrote: > Hello All, > > I tried to install FreeBSD on X60 using PXE boot, but unsuccessfully finish > my attempt. > > When it start PXE boot it get IP address from DHCP, download PXE boot file > from TFTP server, > then trying to load kernel image from TFTP server. > > After 10-20 minutes it give me error message "can't load kernel", I tried > many times load boot/kernel/kernel, but same result. > > I guess PXE boot read much longer time to load kernel file and suddenly > give me error message. > > I followed instruction on http://www.hack.org/mc/freebsd-x60.html > > I made X60>LAN switch>TFTP/DHCP/NFS server and even tried > X60---cross-over cable>TFTP/DHCP/NFS server. > > Is there any suggestion? First, there's a manpage for all this: diskless(8). I've tried this before myself (on all sorts of different hardware), and I've never gotten it to work on RELENG_6 or RELENG_7 -- I reach the same point and receive the same error you do. It appears to me that that an NFS server is *absolutely* necessary for all of this to work; TFTP by itself doesn't suffice, it appears. I've tried setting LOADER_TFTP_SUPPORT=yes in make.conf (forcing the entire process to avoid using NFS), but believe it or not, a part of the booting process still continues to use NFS-related code (or at least the debugging messages state it's trying to do NFS). I was able to get some pxeboot-related debugging output (to see the aforementioned) by setting PXE_DEBUG=true in make.conf (see src/sys/boot/i386/libi386/pxe.c for details on that). -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: FreeBSD-6.2, 7.0-BETA1 on X60
try monitoring the traffic (tcpdump/wireshark), this should give you a good starting point. danny ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
FreeBSD-6.2, 7.0-BETA1 on X60
Hello All, I tried to install FreeBSD on X60 using PXE boot, but unsuccessfully finish my attempt. When it start PXE boot it get IP address from DHCP, download PXE boot file from TFTP server, then trying to load kernel image from TFTP server. After 10-20 minutes it give me error message "can't load kernel", I tried many times load boot/kernel/kernel, but same result. I guess PXE boot read much longer time to load kernel file and suddenly give me error message. I followed instruction on http://www.hack.org/mc/freebsd-x60.html I made X60>LAN switch>TFTP/DHCP/NFS server and even tried X60---cross-over cable>TFTP/DHCP/NFS server. Is there any suggestion? Regards, Balgaa ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
panic when burncd attempt to eject disk (after upgrade 7.0-BETA1 -> 7.0-BETA2)
I have cd/dwd writer on my laptop: acd0: DVDR at ata0-master PIO4 Writer work properly on 7.0-BETA1 #15: Tue Oct 30 13:21:42 EET 2007 , but after today upgrade to 7.0-BETA2 #16: Wed Nov 14 15:41:44 EET 2007 kernel panics during run burncd -es 8 data file.iso fixate (i think when burncd attempt to eject disk after fixate): panic: Geom provider ACD::acd0 failed closing ->access() cpuid = 1 KDB: enter: panic [thread pid 1652 tid 100059 ] Stopped atkdb_enter+0x32: leave As there was a change in behaviour "atacontrol mode acd0" command when no disk in writer: on BETA1 command show current mode, but on BETA2 return error "atacontrol: device not found: Input/output error" -- Mykola Dzham, LEFT-(UANIC|RIPE) JID: [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: [FreeBSD 7.0-BETA1 and beyound] Rescue environment is non-functional on AMD64/Intel64
on 09/11/2007 01:23 Wayne Chapeskie said the following: > > We are still in the beta stage of the release cycle, where the mailing > list is actually a good place to find out what is going on. Web site > documentation usually doesn't catch up until release time. The purposes of > the various release ISO images are documented in the release > announcements -- see the 6.2 release announcement at > http://www.freebsd.org/releases/6.2R/announce.html > which did indeed mention the "live CD" functionality in disc1. > > In 6.2, only ia64 had a livefs ISO, amd64 did not, nor did i386. The > configuration of the release ISO's does change over the years, and has > in the past been documented in a README in the ftp directories, and is > now documented in the release announcements. The ia64 livefs ISO was a > slight oversight in the 6.2 release notes, but since we are going to be > seeing more cases of livefs not fitting on the disc1 install, I imagine > future release announcements will reflect that. > > I understand. Maybe a short addition to the Handbook would be nice, maybe somewhere near "2.3.6 Obtain the FreeBSD Installation Files". I think ISO image functions/layouts change rarely enough to be documented in the Handbook. Just my 2c. -- Andriy Gapon ___ 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.0-BETA1 and beyound] Rescue environment is non-functional on AMD64/Intel64
On Thu, Nov 08, 2007 at 03:18:03PM +0200, Andriy Gapon wrote: > > on 08/11/2007 00:25 Wayne Chapeskie said the following: > > For BETA2, there is a separate livefs iso image available for amd64 and > > ia64. The i386 disc1 ISO's still include "Fixit" functionality, in the > > usual place in the first sysinstall menu. If the required packages take > > up too much space for the i386 release, we will probably see a separate > > livefs ISO for this as well. Earlier releases or snapshots for the > > amd64 and ia64 may not have had the same space constraints, and > > perhaps included fixit/livefs functionality on the disc1 ISO. > > BTW, maybe this should be documented somewhere ? > Explanations like this one should not be left to mailing list archives > and search engine indexes alone. > > It seems that livefs ISOs are produced for some time now, but I never > saw any description of them. This might not be a good example, but if I > google for "FreeBSD livefs" I don't get any meaningful results, mostly > links to the ISOs. So until now I was puzzled about the purpose of those > ISOs and their difference to disk1 live fs functionality. Yes, I am a > newcomer from i386 to amd64. We are still in the beta stage of the release cycle, where the mailing list is actually a good place to find out what is going on. Web site documentation usually doesn't catch up until release time. The purposes of the various release ISO images are documented in the release announcements -- see the 6.2 release announcement at http://www.freebsd.org/releases/6.2R/announce.html which did indeed mention the "live CD" functionality in disc1. In 6.2, only ia64 had a livefs ISO, amd64 did not, nor did i386. The configuration of the release ISO's does change over the years, and has in the past been documented in a README in the ftp directories, and is now documented in the release announcements. The ia64 livefs ISO was a slight oversight in the 6.2 release notes, but since we are going to be seeing more cases of livefs not fitting on the disc1 install, I imagine future release announcements will reflect that. -- Wayne Chapeskie ___ 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.0-BETA1 and beyound] Rescue environment is non-functional on AMD64/Intel64
on 08/11/2007 00:25 Wayne Chapeskie said the following: > For BETA2, there is a separate livefs iso image available for amd64 and > ia64. The i386 disc1 ISO's still include "Fixit" functionality, in the > usual place in the first sysinstall menu. If the required packages take > up too much space for the i386 release, we will probably see a separate > livefs ISO for this as well. Earlier releases or snapshots for the > amd64 and ia64 may not have had the same space constraints, and > perhaps included fixit/livefs functionality on the disc1 ISO. BTW, maybe this should be documented somewhere ? Explanations like this one should not be left to mailing list archives and search engine indexes alone. It seems that livefs ISOs are produced for some time now, but I never saw any description of them. This might not be a good example, but if I google for "FreeBSD livefs" I don't get any meaningful results, mostly links to the ISOs. So until now I was puzzled about the purpose of those ISOs and their difference to disk1 live fs functionality. Yes, I am a newcomer from i386 to amd64. -- Andriy Gapon ___ 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.0-BETA1 and beyound] Rescue environment is non-functional on AMD64/Intel64
On Mon, Nov 05, 2007 at 10:39:38PM +0200, Andrei Kolu wrote: > To: freebsd-stable@freebsd.org > ... > Monday 05 November 2007 11:22:30 kirjutas Stefan Lambrev: > > Hi, > > > > Andrei Kolu wrote: > > > After some experimenting with BETA1/1.5 or whatever it is I encountered > > > serious problems: > > > > > > 1. Emergency shell on tty3 is useless- not a single command is available. > > > > This is install CD not fixit CD. On istall CD emergency shell becomes > > useful once you actually install those commands. For BETA2, there is a separate livefs iso image available for amd64 and ia64. The i386 disc1 ISO's still include "Fixit" functionality, in the usual place in the first sysinstall menu. If the required packages take up too much space for the i386 release, we will probably see a separate livefs ISO for this as well. Earlier releases or snapshots for the amd64 and ia64 may not have had the same space constraints, and perhaps included fixit/livefs functionality on the disc1 ISO. > I don't want to start install process, I want to restore bootloader. > > # boot0cfg -B ad0 You will probably need the livefs ISO. -- Wayne Chapeskie ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 7.0-BETA1 & 2 occasionally freezing, how to diagnose?
On Tue, 6 Nov 2007 12:48:35 +1100 Norberto Meijome <[EMAIL PROTECTED]> wrote: > Pretty much everytime I'm getting a lockup, i'm either streaming music > from my music box or on a skype call. Not much to go by, but there > isn't any logs left at all of the crash. It is not a panic (no writing > dump to disk when I press enter, Caps-lock is dead, even the Fn key > which is bound to the bios is dead). What I have noticed in these > cases is that there seems to be a lock upthen, about a minute or > so after it, the mouse seems to come back to life...but then there's > nothing more I can do - i've waited for over 5 minutes after this with > no more results > > Not sure how I can diagnose / test this, but i'm willing to give them > a try, time permitting :) Hmm. Any chances any of you upgraded Xorg/glib2 this weekend? I did on Sunday, and got some soft-locks similar to these ones. In my case, only part of the applications would freeze. Interestingly, only xmms and gkrellm kept running, and I could ssh to the machine---nothing unusual on top(1). In the X console, the mouse would move, but don't do anything useful. The keyboard sometimes didn't worked, but whenever NumLock worked, then I'd be able to vtswitch to some vt and ^C the whole X server. The only worth message was from nvidia module (sometimes more than once), some random time before soft-locking up. If it helps, I heard a slightly different pc-speaker beep (short), which eventually led me to vt-switch and discover this message: kernel: NVRM: API mismatch: the client has the version 100.14.19, but kernel: NVRM: this kernel module has the version 100.14.11. Please kernel: NVRM: make sure that this kernel module and all NVIDIA driver kernel: NVRM: components have the same version. I'm on 6.1-RELEASE, most ports are up-to-date, and now using the nv driver because nvidia module is getting a _sleep unresolved symbol. No locks so far, BTW. -- Ricardo Nabinger Sanchez [EMAIL PROTECTED] Powered by FreeBSD "Left to themselves, things tend to go from bad to worse." ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 7.0-BETA1 & 2 occasionally freezing, how to diagnose?
Kris Kennaway wrote: Doug Poland wrote: On Mon, Nov 05, 2007 at 11:14:13PM +0100, Ivan Voras wrote: Doug Poland wrote: I've been having frequent problems with BETA1 and now BETA2 "freezing". There is no diagnostic information, nothing in /var/log/messages, nothing, just a hung interface. I cannot ssh into the machine and it appears the box ceases to communicate on SSH. A couple of times I've had screen corruption on the laptop's LCD display. are you running powerd? yes: I recently started running powerd, within the last couple of weeks Try disabling it; it (actually acpi_throttle, which powerd uses) is known to cause hangs on dual core systems at least. OK, I'll start there... thanks -- Regards, Doug ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 7.0-BETA1 & 2 occasionally freezing, how to diagnose?
On Mon, Nov 05, 2007 at 07:47:29PM -0600, Doug Poland wrote: > I've done serial console redirection before but this laptop has no > serial port. Can I get console redirection via firewire? Can you point > me at some docs? Check out http://wiki.freebsd.org/DebugWithDcons Brix -- Henrik Brix Andersen <[EMAIL PROTECTED]> pgpyECaGoBq3C.pgp Description: PGP signature
Re: 7.0-BETA1 & 2 occasionally freezing, how to diagnose?
Doug Poland wrote: On Mon, Nov 05, 2007 at 11:14:13PM +0100, Ivan Voras wrote: Doug Poland wrote: Hello, I've been having frequent problems with BETA1 and now BETA2 "freezing". There is no diagnostic information, nothing in /var/log/messages, nothing, just a hung interface. I cannot ssh into the machine and it appears the box ceases to communicate on SSH. A couple of times I've had screen corruption on the laptop's LCD display. Every time it hands I'm running Xorg 7.3, Thunderbird, Firefox, pidgin, and a bunch of xterms. Is there something I can do to diagnose this issue? Only random generic troubleshooting items: - how's your heating? the fan on the laptop runs continuously, sometimes on high speed. I typically see temps between 140 (mostly idle) -> 165 (make -j4 buildworld) Fahrenheit. screen corruption looks like memory or bus errors. In my situation, it usually manifests itself as the external LCD monitor goes blank (says "no signal") and the bottom half of the internal LCD gets weird, multi-colored square patterns. are you running powerd? yes: I recently started running powerd, within the last couple of weeks Try disabling it; it (actually acpi_throttle, which powerd uses) is known to cause hangs on dual core systems at least. Kris ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 7.0-BETA1 & 2 occasionally freezing, how to diagnose?
On Tue, Nov 06, 2007 at 12:48:35PM +1100, Norberto Meijome wrote: > On Mon, 05 Nov 2007 14:24:09 -0600 > Doug Poland <[EMAIL PROTECTED]> wrote: > > > Hello, > > > > I've been having frequent problems with BETA1 and now BETA2 > > "freezing". There is no diagnostic information, nothing in > > /var/log/messages, nothing, just a hung interface. I cannot ssh > > into the machine and it appears the box ceases to communicate on > > SSH. A couple of times I've had screen corruption on the laptop's > > LCD display. > > > > Every time it hands I'm running Xorg 7.3, Thunderbird, Firefox, > > pidgin, and a bunch of xterms. > > > > Is there something I can do to diagnose this issue? > > > > hi Doug, > My laptops is freezing like this too - no corruption on display though > (this is the 2nd time i write this email, as it just happened ). I > am still not sure what the cause is...some things I've used / tried: > > I was using gjournal on my 80 GB /usr partition, with a 1.5 journal > to ad01sh . I was getting quite often lockups where it seemed the disk > subsystem would stall - anything in memory would work, but as soon as > disk access was needed, it'd stall too. Rebooting was not an option, > as the shutdown watchdog would timeout and stop it. > > furthermore, I'd have to go into single user and run fsck > /dev/ad0s1f.journal every time the laptop would crash. I seemed to > have much fewer bad information in the inodes (thanks to the journal), > but I was getting 4 or 6 crashes a day. Since I switched away from > gjournal, these crashes have completely gone away. since this is my > main machine, i cant experiment too much with it. > > I also had skype-1.4 running . One of its processes was spinning > completely out of control , when i wasn't using skype at all (other > than receiving text msgs). I sent an email about it to Multimedia.I've > since switched back to skype.1.2 and that problem is also gone. > > But i still get the occasional lockup. I have a feeling it is related > to using the sound card : > > $ cat /dev/sndstat > FreeBSD Audio Driver (newpcm: 32bit 2007061600/i386) > Installed devices: > pcm0: at memory 0xb000 > irq 11 kld snd_hda [20071020_0048] [MPSAFE] (1p:10v/1r:6v channels duplex > default) > > Pretty much everytime I'm getting a lockup, i'm either streaming music > from my music box or on a skype call. Not much to go by, but there > isn't any logs left at all of the crash. It is not a panic (no writing > dump to disk when I press enter, Caps-lock is dead, even the Fn key > which is bound to the bios is dead). What I have noticed in these > cases is that there seems to be a lock upthen, about a minute or > so after it, the mouse seems to come back to life...but then there's > nothing more I can do - i've waited for over 5 minutes after this with > no more results > It's quite likely that I have streaming audio/video going on but am using mplayer exclusively. Am also using new HDA controller. -- Regards, Doug ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 7.0-BETA1 & 2 occasionally freezing, how to diagnose?
On Tue, 6 Nov 2007 12:48:35 +1100
Norberto Meijome <[EMAIL PROTECTED]> wrote:
> But i still get the occasional lockup. I have a feeling it is related to
> using the sound card :
>
> $ cat /dev/sndstat
> FreeBSD Audio Driver (newpcm: 32bit 2007061600/i386)
> Installed devices:
> pcm0: at memory 0xb000
> irq 11 kld snd_hda [20071020_0048] [MPSAFE] (1p:10v/1r:6v channels duplex
> default)
>
> Pretty much everytime I'm getting a lockup, i'm either streaming music from
> my music box or on a skype call. Not much to go by, but there isn't any logs
> left at all of the crash. It is not a panic (no writing dump to disk when I
> press enter, Caps-lock is dead, even the Fn key which is bound to the bios is
> dead). What I have noticed in these cases is that there seems to be a lock
> upthen, about a minute or so after it, the mouse seems to come back to
> life...but then there's nothing more I can do - i've waited for over 5
> minutes after this with no more results
btw, I've resorted to NOT using XMMS - the issues were happening a LOT more
often when i use it instead of, say, vlc or beep.
I remember having this same issue on 6.2 with the drivers in the kernel. The
latest binary drivers from Ariff would work fine, though i had given up on xmms
by then and using vlc for a while.
cheers,
b
_
{Beto|Norberto|Numard} Meijome
If you find a solution and become attached to it, the solution may become your
next problem.
I speak for myself, not my employer. Contents may be hot. Slippery when wet.
Reading disclaimers makes you go blind. Writing them is worse. You have been
Warned.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 7.0-BETA1 & 2 occasionally freezing, how to diagnose?
On Mon, 05 Nov 2007 14:24:09 -0600
Doug Poland <[EMAIL PROTECTED]> wrote:
> Hello,
>
> I've been having frequent problems with BETA1 and now BETA2 "freezing".
> There is no diagnostic information, nothing in /var/log/messages,
> nothing, just a hung interface. I cannot ssh into the machine and it
> appears the box ceases to communicate on SSH. A couple of times I've had
> screen corruption on the laptop's LCD display.
>
> Every time it hands I'm running Xorg 7.3, Thunderbird, Firefox, pidgin,
> and a bunch of xterms.
>
> Is there something I can do to diagnose this issue?
>
hi Doug,
My laptops is freezing like this too - no corruption on display though (this is
the 2nd time i write this email, as it just happened ). I am still not sure
what the cause is...some things I've used / tried:
I was using gjournal on my 80 GB /usr partition, with a 1.5 journal to ad01sh
. I was getting quite often lockups where it seemed the disk subsystem would
stall - anything in memory would work, but as soon as disk access was needed,
it'd stall too. Rebooting was not an option, as the shutdown watchdog would
timeout and stop it.
furthermore, I'd have to go into single user and run fsck /dev/ad0s1f.journal
every time the laptop would crash. I seemed to have much fewer bad information
in the inodes (thanks to the journal), but I was getting 4 or 6 crashes a day.
Since I switched away from gjournal, these crashes have completely gone away.
since this is my main machine, i cant experiment too much with it.
I also had skype-1.4 running . One of its processes was spinning completely out
of control , when i wasn't using skype at all (other than receiving text msgs).
I sent an email about it to Multimedia.I've since switched back to skype.1.2
and that problem is also gone.
But i still get the occasional lockup. I have a feeling it is related to using
the sound card :
$ cat /dev/sndstat
FreeBSD Audio Driver (newpcm: 32bit 2007061600/i386)
Installed devices:
pcm0: at memory 0xb000 irq
11 kld snd_hda [20071020_0048] [MPSAFE] (1p:10v/1r:6v channels duplex default)
Pretty much everytime I'm getting a lockup, i'm either streaming music from my
music box or on a skype call. Not much to go by, but there isn't any logs left
at all of the crash. It is not a panic (no writing dump to disk when I press
enter, Caps-lock is dead, even the Fn key which is bound to the bios is dead).
What I have noticed in these cases is that there seems to be a lock upthen,
about a minute or so after it, the mouse seems to come back to life...but then
there's nothing more I can do - i've waited for over 5 minutes after this with
no more results
Not sure how I can diagnose / test this, but i'm willing to give them a try,
time permitting :)
thanks!
Beto
_
{Beto|Norberto|Numard} Meijome
Mary had a crypto key
she kept it in escrow
and everything that Mary said
the Feds were sure to know.
I speak for myself, not my employer. Contents may be hot. Slippery when wet.
Reading disclaimers makes you go blind. Writing them is worse. You have been
Warned.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 7.0-BETA1 & 2 occasionally freezing, how to diagnose?
On Mon, Nov 05, 2007 at 11:14:13PM +0100, Ivan Voras wrote:
> Doug Poland wrote:
> > Hello,
> >
> > I've been having frequent problems with BETA1 and now BETA2
> > "freezing". There is no diagnostic information, nothing in
> > /var/log/messages, nothing, just a hung interface. I cannot ssh
> > into the machine and it appears the box ceases to communicate on
> > SSH. A couple of times I've had screen corruption on the laptop's
> > LCD display.
> >
> > Every time it hands I'm running Xorg 7.3, Thunderbird, Firefox,
> > pidgin, and a bunch of xterms.
> >
> > Is there something I can do to diagnose this issue?
>
> Only random generic troubleshooting items:
>
> - how's your heating?
>
the fan on the laptop runs continuously, sometimes on high speed. I
typically see temps between 140 (mostly idle) -> 165 (make -j4
buildworld) Fahrenheit.
> screen corruption looks like memory or bus errors.
>
In my situation, it usually manifests itself as the external LCD monitor
goes blank (says "no signal") and the bottom half of the internal LCD
gets weird, multi-colored square patterns.
> are you running powerd?
>
yes: I recently started running powerd, within the last couple of weeks
> - can you set up a serial or firewire connection to it and monitor the
> machine from there ("screen corruption" may also mean a kernel message
> being printed in text mode, in the part of memory now mapped for
> graphics - if this is the case you'll see the message over the serial
> console).
>
I've done serial console redirection before but this laptop has no
serial port. Can I get console redirection via firewire? Can you point
me at some docs?
--
Regards,
Doug
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 7.0-BETA1 & 2 occasionally freezing, how to diagnose?
On Mon, Nov 05, 2007 at 02:07:46PM -0800, Karol Mroz wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Doug Poland wrote: > > Hello, > > > > I've been having frequent problems with BETA1 and now BETA2 > > "freezing". There is no diagnostic information, nothing in > > /var/log/messages, nothing, just a hung interface. I cannot ssh > > into the machine and it appears the box ceases to communicate on > > SSH. A couple of times I've had screen corruption on the laptop's > > LCD display. > > > > Every time it hands I'm running Xorg 7.3, Thunderbird, Firefox, > > pidgin, and a bunch of xterms. > > > > Is there something I can do to diagnose this issue? > > > > Have you just migrated to CURRENT? Was this machine running fine under > STABLE? > I moved from 6.2-STABLE to 7.0-BETA using cvsup. I may had an infrequent problem in the 6.2-STABLE days, but I can't recall with certainty. > I had similar problems with a desktop of mine that was running 6.2. > Every now and then (sometimes days in between) it would freeze in X, > corrupt the screen, or at times would just reboot. There was no warning > and nothing of worth in any log files. > pretty much my experience here, except I have a laptop. > I had a feeling it might have been my video card, so after taxing it > really hard with gl apps and noticing artifacts on the screen, I > replaced the card. The system ran well for a few weeks, but the > problems persisted. Thought at this point it could be faulty ram, so > ran each half-gig stick on it's own until the next failure. Both > sticks showed failures. So then I moved the sticks out of slots 1,2 > and into 3,4... that was 4 months ago and all is well. > I suppose I could run memtest, although the RAM in this laptop was replaced in July (now running 4GB). > I guess what I'm aiming at here is that this could be a hardware issue > which can be a pain to diagnose. > Thanks for the suggestion. -- Regards, Doug ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 7.0-BETA1 & 2 occasionally freezing, how to diagnose?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Doug Poland wrote: > Hello, > > I've been having frequent problems with BETA1 and now BETA2 "freezing". > There is no diagnostic information, nothing in /var/log/messages, > nothing, just a hung interface. I cannot ssh into the machine and it > appears the box ceases to communicate on SSH. A couple of times I've had > screen corruption on the laptop's LCD display. > > Every time it hands I'm running Xorg 7.3, Thunderbird, Firefox, pidgin, > and a bunch of xterms. > > Is there something I can do to diagnose this issue? > I'm curious if these problems arose with 7.0? Did you run 6.2 on this machine prior to 7.0? I had similar problems with a desktop of mine that was running 6.2. Every now and then (sometimes days in between) it would freeze in X, corrupt the screen, or at times would just reboot. There was no warning and nothing of worth in any log files. I had a feeling it might have been my video card, so after taxing it really hard with gl apps and noticing artifacts on the screen, I replaced the card. The system ran well for a few weeks, but the problems persisted. Thought at this point it could be faulty ram, so ran each half-gig stick on it's own until the next failure. Both sticks showed failures. So then I moved the sticks out of slots 1,2 and into 3,4... that was 4 months ago and all is well. I guess what I'm aiming at here is that this could be a hardware issue which can be a pain to diagnose. - -- Karol Mroz [EMAIL PROTECTED] -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFHL5Qyuoug78g/Mz8RAkEzAJ9yzGU1in5lrS3fUO0mfHfzCuYiqQCfRSn3 EkJrTLktOyfNddasgJPA4V8= =tbgK -END PGP SIGNATURE- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 7.0-BETA1 & 2 occasionally freezing, how to diagnose?
Doug Poland wrote:
> Hello,
>
> I've been having frequent problems with BETA1 and now BETA2 "freezing".
> There is no diagnostic information, nothing in /var/log/messages,
> nothing, just a hung interface. I cannot ssh into the machine and it
> appears the box ceases to communicate on SSH. A couple of times I've had
> screen corruption on the laptop's LCD display.
>
> Every time it hands I'm running Xorg 7.3, Thunderbird, Firefox, pidgin,
> and a bunch of xterms.
>
> Is there something I can do to diagnose this issue?
Only random generic troubleshooting items:
- how's your heating? screen corruption looks like memory or bus errors.
are you running powerd?
- can you set up a serial or firewire connection to it and monitor the
machine from there ("screen corruption" may also mean a kernel message
being printed in text mode, in the part of memory now mapped for
graphics - if this is the case you'll see the message over the serial
console).
signature.asc
Description: OpenPGP digital signature
Re: [FreeBSD 7.0-BETA1 and beyound] Rescue environment is non-functional on AMD64/Intel64
Monday 05 November 2007 11:22:30 kirjutas Stefan Lambrev: > Hi, > > Andrei Kolu wrote: > > After some experimenting with BETA1/1.5 or whatever it is I encountered > > serious problems: > > > > 1. Emergency shell on tty3 is useless- not a single command is available. > > This is install CD not fixit CD. On istall CD emergency shell becomes > useful once you actually install those commands. > Install what? How, where? Why emergency shell works on snapshot release and not on beta? To me this is a BIG * BUG not a feature. > > 2. When tried to use installcd as livecd is asked me to insert livecd > > (there is plenty of free space available on installcd- why not use that > > usefully?). > > BETA ISOs are smaller only because packages are not included, and they > will be included for FreeBSD 7.0-RELEASE. > > > I am positive I was able to use emergency shell and livecd function on > > CURRENT september snapsot just fine (i386 version though). > > Yes you can use it and now after the install process is started. > I don't want to start install process, I want to restore bootloader. # boot0cfg -B ad0 And now I have to download 500+MB to do things I did without any problem for years?! Sry, I am pissed off... ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
7.0-BETA1 & 2 occasionally freezing, how to diagnose?
Hello, I've been having frequent problems with BETA1 and now BETA2 "freezing". There is no diagnostic information, nothing in /var/log/messages, nothing, just a hung interface. I cannot ssh into the machine and it appears the box ceases to communicate on SSH. A couple of times I've had screen corruption on the laptop's LCD display. Every time it hands I'm running Xorg 7.3, Thunderbird, Firefox, pidgin, and a bunch of xterms. Is there something I can do to diagnose this issue? -- Regards, Doug ___ 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.0-BETA1 and beyound] Rescue environment is non-functional on AMD64/Intel64
Hi, Andrei Kolu wrote: After some experimenting with BETA1/1.5 or whatever it is I encountered serious problems: 1. Emergency shell on tty3 is useless- not a single command is available. This is install CD not fixit CD. On istall CD emergency shell becomes useful once you actually install those commands. 2. When tried to use installcd as livecd is asked me to insert livecd (there is plenty of free space available on installcd- why not use that usefully?). BETA ISOs are smaller only because packages are not included, and they will be included for FreeBSD 7.0-RELEASE. I am positive I was able to use emergency shell and livecd function on CURRENT september snapsot just fine (i386 version though). Yes you can use it and now after the install process is started. Andrei ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]" -- Best Wishes, Stefan Lambrev ICQ# 24134177 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
[FreeBSD 7.0-BETA1 and beyound] Rescue environment is non-functional on AMD64/Intel64
After some experimenting with BETA1/1.5 or whatever it is I encountered serious problems: 1. Emergency shell on tty3 is useless- not a single command is available. 2. When tried to use installcd as livecd is asked me to insert livecd (there is plenty of free space available on installcd- why not use that usefully?). I am positive I was able to use emergency shell and livecd function on CURRENT september snapsot just fine (i386 version though). Andrei ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: FreeBSD-6.2, 7.0-BETA1 boot on Lenovo X60
Dimitry Andric wrote: Andreas Rudisch wrote: [...] There's no floppy drive in the X series ThinkPads, so you'll end up using an USB floppy drive. This will probably lead to the same BTX loader problem as with USB CD-ROM drives. The same is probably applicable to booting from USB sticks, and I'm not even sure FreeBSD supports booting off those. About a year ago I created USB stick with GRUB instead of BTX loader for booting on CD-ROM less Sun Fire servers. It works well. So this is the possible way to go. You can create just bootable USB stick from miniboot ISO (30MB) and then install from internal CD-ROM or from network (FTP, NFS...). Or you can create completely working instalation media with packeges etc on USB stick bigger than 512MB. Miroslav Lachman ___ 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.0-BETA1] strange behavior in hostname resolving order
At Sat, 03 Nov 2007 00:05:07 +0900,
Byung-Hee HWANG <[EMAIL PROTECTED]> wrote:
> Usually i prefer 6to4(stf(4)) to 6over4(gif(4)) because some
> tunnel providers like to limit bandwidth too musch. So until my
> upstream ISP give me native ipv6 addresses (it's take long time maybe),
> i'm going to use 6to4 instead of 6over4 continuous.
(snip)
> And from now on, i would give you one question. Why is 7.0-BETA1
> different from another -RELEASE in hostname resolving order? AFAIK, at
> least on 6.2-RELEASE, the order is first IPv6 and then IPv4. However,
> 7.0-BETA1 try to lookup in first IPv4 than IPv6. Here is the evidence:
This is most likely because 7.0 now installs the address selection
policy table at boot time by default:
http://www.freebsd.org/cgi/cvsweb.cgi/src/etc/defaults/rc.conf.diff?r1=1.304&r2=1.305
Now if you have (which I guess is your network configuration)
A. a global IPv4 address and
B. a 6to4 IPv6 address,
and have a candidate destination addresses
C. a global IPv4 address (like 210.226.20.15)
D. a native global IPv6 address (like 2001:218:422:1::15)
then getaddrinfo() will prefer the combination of {A and C} because
these addresses have a matching scope while B and D don't. If you
make sure the 6to4 source address always wins, you should modify the
policy table to:
PrefixPrecedence Label
::1/128 50 0
::/0 40 1
2002::/16 30 1
::/96 20 3
:::0:0/96100 4
(i.e., change the label of 2002::/16).
JINMEI, Tatuya
Communication Platform Lab.
Corporate R&D Center, Toshiba Corp.
[EMAIL PROTECTED]
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: FreeBSD-6.2, 7.0-BETA1 boot on Lenovo X60
On Sun, 2007-11-04 at 23:49 +0800, Balgansuren Batsukh wrote:
> Hello All,
>
> Last few days I try to boot FreeBSD-6.2, 7.0-BETA1 boot CD using USB CDROM
> drive on Lenovo X60.
>
> It give kind of assembler code non-stop flow over screen.
>
> Can't boot system and some times give BTX halted message after CPU register
> code ES=,
>
> Is there any way to boot/install FreeBSD-6.2/7.0-BETA on X60?
If you have another box on the network, PXE is the way to go. I have
used it to troubleshoot my X60, when I have rendered it unbootable,
enough times to justify time spent. I have acquired UltraBase since
then, but it is still *much more convenient* to boot with PXE in need.
Below are relevant pieces of the information from the server (its name
is 'twinhead', its IP is 10.0.3.236 and install CD is copied into
'/SHARED/tftpboot', tftp user with access to the setup is named 'sunny'
-- you will have to adjust it accordingly):
=== excerpt from /usr/local/etc/dhcpd.conf (I am
using isc-dhcp3-server-3.0.5_2):
server-name "twinhead";
server-identifier 10.0.3.236;
next-server 10.0.3.236;
# This is a very basic subnet declaration.
subnet 10.0.3.0 netmask 255.255.255.0 {
range 10.0.3.33 10.0.3.64;
option routers 10.0.3.242;
option domain-name-servers 10.0.3.242;
option root-path "/SHARED/tftpboot";
filename "boot/pxeboot";
}
/SHARED/tftpboot/boot/loader.rc
echo Loading Kernel...
load /boot/kernel/kernel
echo Loading mfsroot...
load -t mfs_root /mfsroot
echo booting...
echo \007\007
echo initializing h0h0magic...
set vfs.root.mountfrom="ufs:/dev/md0c"
boot
excerpt from /etc/inetd.conf
tftpdgram udp waitroot/usr/libexec/tftpd tftpd -u
sunny -l -s /SHARED/tftpboot
I have also gunzip'ed /SHARED/tftpboot/boot/mfsroot.gz and placed it
into /SHARED/tftpboot/.
I don't think there was much else needed doing before you can attempt
booting your X60. Once you boot, you can switch to FTP install, so
version, you are booting from, does not need exactly match whatever you
want installed.
Note: you need to make sure there are no other active DHCP servers on
your network -- I have spend few hours hunting down that one ;)
>
> Regards,
> Balgaa
>
> ___
> [EMAIL PROTECTED] mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "[EMAIL PROTECTED]"
--
Alexandre "Sunny" Kovalenko
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: FreeBSD-6.2, 7.0-BETA1 boot on Lenovo X60
Andreas Rudisch wrote: > or try the boot floopies: > ftp://ftp7.freebsd.org/pub/FreeBSD/releases/i386/6.2-RELEASE/floppies/ > ftp://ftp7.freebsd.org/pub/FreeBSD/releases/i386/7.0-BETA2/floppies/ There's no floppy drive in the X series ThinkPads, so you'll end up using an USB floppy drive. This will probably lead to the same BTX loader problem as with USB CD-ROM drives. The same is probably applicable to booting from USB sticks, and I'm not even sure FreeBSD supports booting off those. AFAIK the only non-PXE alternative is using the UltraBase docking station, which has an optical drive bay connected via ATAPI. But it's rather expensive; here in .nl, it's about EUR 175 for the dock, and EUR 130 for the CD-RW/DVD drive (not even a DVD writer!!). ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: FreeBSD-6.2, 7.0-BETA1 boot on Lenovo X60
On Sun, 4 Nov 2007 23:49:13 +0800 "Balgansuren Batsukh" <[EMAIL PROTECTED]> wrote: > Last few days I try to boot FreeBSD-6.2, 7.0-BETA1 boot CD using USB CDROM > drive on Lenovo X60. > Can't boot system and some times give BTX halted message after CPU register > code ES=, Take a look at this: http://hack.org/mc/freebsd-x60.html or try the boot floopies: ftp://ftp7.freebsd.org/pub/FreeBSD/releases/i386/6.2-RELEASE/floppies/ ftp://ftp7.freebsd.org/pub/FreeBSD/releases/i386/7.0-BETA2/floppies/ Andreas -- GnuPG key : 0x2A573565 | http://cyb.websimplex.de/pubkey.asc Fingerprint: 925D 2089 0BF9 8DE5 9166 33BB F0FD CD37 2A57 3565 pgpVXrYvfCmLI.pgp Description: PGP signature
Re: FreeBSD-6.2, 7.0-BETA1 boot on Lenovo X60
Balgansuren Batsukh wrote: > Last few days I try to boot FreeBSD-6.2, 7.0-BETA1 boot CD using USB > CDROM drive on Lenovo X60. > > It give kind of assembler code non-stop flow over screen. This is a well-known issue with the USB support of some BIOSes (these days, actually most of them). The BIOS uses protected mode, while BTX also does, and this clashes. You'll need to wire up an IDE or SATA optical drive, or fiddle with PXE to get FreeBSD installed. On my X41, which is the predecessor to your X60, I installed OpenBSD instead... :) ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
FreeBSD-6.2, 7.0-BETA1 boot on Lenovo X60
Hello All, Last few days I try to boot FreeBSD-6.2, 7.0-BETA1 boot CD using USB CDROM drive on Lenovo X60. It give kind of assembler code non-stop flow over screen. Can't boot system and some times give BTX halted message after CPU register code ES=, Is there any way to boot/install FreeBSD-6.2/7.0-BETA on X60? Regards, Balgaa ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
[SOLVED] (Was: Re: [FreeBSD 7.0-BETA1] strange behavior in hostname resolving order)
Dear Mr. UMEMOTO, On Sat, 2007-11-03 at 00:58 +0900, Hajimu UMEMOTO wrote: > Hi, > > >>>>> On Sat, 03 Nov 2007 00:05:07 +0900 > >>>>> Byung-Hee HWANG <[EMAIL PROTECTED]> said: > > bh> To Whom It May Concern: (Cc'ed [EMAIL PROTECTED]) > > bh> Usually i prefer 6to4(stf(4)) to 6over4(gif(4)) because some > bh> tunnel providers like to limit bandwidth too musch. So until my > bh> upstream ISP give me native ipv6 addresses (it's take long time maybe), > bh> i'm going to use 6to4 instead of 6over4 continuous. > > bh> Here is my shot using 6to4: > > bh> [EMAIL PROTECTED]:~> uname -a > bh> FreeBSD viola.izb.knu.ac.kr 7.0-BETA1 FreeBSD 7.0-BETA1 #0: > bh> Fri Nov 2 12:13:10 KST 2007 > bh> [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC i386 > > bh> [EMAIL PROTECTED]:~> ifconfig rl0 | grep 2002 > bh> inet6 2002:9be6:9d5d:2:20b:6aff:fe56:969f prefixlen 64 autoconf > > bh> [EMAIL PROTECTED]:~> ping6 -c 5 mx.jp.freebsd.org. > bh> PING6(56=40+8+8 bytes) > bh> 2002:9be6:9d5d:2:20b:6aff:fe56:969f --> 2001:218:422:1::15 > bh> 16 bytes from 2001:218:422:1::15, icmp_seq=0 hlim=49 time=225.297 ms > bh> 16 bytes from 2001:218:422:1::15, icmp_seq=1 hlim=49 time=224.591 ms > bh> 16 bytes from 2001:218:422:1::15, icmp_seq=2 hlim=49 time=237.175 ms > bh> 16 bytes from 2001:218:422:1::15, icmp_seq=3 hlim=49 time=230.540 ms > bh> 16 bytes from 2001:218:422:1::15, icmp_seq=4 hlim=49 time=224.681 ms > > bh> --- mx.jp.freebsd.org ping6 statistics --- > bh> 5 packets transmitted, 5 packets received, 0.0% packet loss > bh> round-trip min/avg/max/std-dev = 224.591/228.457/237.175/4.889 ms > > bh> [EMAIL PROTECTED]:~> traceroute6 mx.jp.freebsd.org. > bh> traceroute6 to mx.jp.freebsd.org (2001:218:422:1::15) from > bh> 2002:9be6:9d5d:2:20b:6aff:fe56:969f, 64 hops max, 12 byte packets > bh> 1 2002:9be6:9d5d:2:250:4dff:fe00:5df3 1.541 ms 0.949 ms 1.154 ms > bh> [..] > bh> 23 v6.imgsrc.co.jp 264.635 ms 226.812 ms 232.207 ms > bh> 24 castle.jp.FreeBSD.org 427.683 ms 219.659 ms 222.862 ms > bh> [EMAIL PROTECTED]:~> > > bh> And from now on, i would give you one question. Why is 7.0-BETA1 > bh> different from another -RELEASE in hostname resolving order? AFAIK, at > bh> least on 6.2-RELEASE, the order is first IPv6 and then IPv4. However, > bh> 7.0-BETA1 try to lookup in first IPv4 than IPv6. Here is the evidence: > > bh> [EMAIL PROTECTED]:~> uname -srm > bh> FreeBSD 6.2-RELEASE-p8 i386 > bh> [EMAIL PROTECTED]:~> telnet mx.jp.freebsd.org 25 > bh> Trying 2001:218:422:1::15... > bh> Connected to mx.jp.freebsd.org. > bh> Escape character is '^]'. > bh> [..] > bh> [EMAIL PROTECTED]:~> ssh -v mx.jp.freebsd.org. > bh> debug1: Connecting to mx.jp.freebsd.org. [2001:218:422:1::15] > bh> ^C > bh> > bh> And > > bh> [EMAIL PROTECTED]:~> uname -srm > bh> FreeBSD 7.0-BETA1 i386 > bh> [EMAIL PROTECTED]:~> telnet mx.jp.freebsd.org 25 > bh> Trying 210.226.20.15... > bh> Connected to mx.jp.freebsd.org. > bh> Escape character is '^]'. > bh> [..] > bh> [EMAIL PROTECTED]:~> ssh -v mx.jp.freebsd.org. > bh> debug1: Connecting to mx.jp.freebsd.org. [210.226.20.15] > bh> ^C > > bh> What happended? Is there anyone to dislike IPv6 in src committers? > bh> Please let me know the correct answer to this puzzle ;; > > The Default Address Selection is turned on by default after > 6.2-RELEASE was out. According to RFC 3484, the default policy is as > follows: > > Prefix Prec Label > ::1/128 50 0 > ::/0 40 1 > 2002::/16 30 2 > ::/96 20 3 > :::0.0.0.0/96 10 4 > > It means that communicating with native IP address is preferred over > 6to4 address when source address and destination adddress are not 6to4 > address. > > If you want not to treat 6to4 address as special, you can omit the > line of 2002::/16 by putting the following lines into your > /etc/ip6addrctl.conf: > > ::1/128 50 0 > ::/040 1 > ::/96 20 3 > :::0.0.0.0/96 10 4 > > Then, run `/etc/rc.d/ip6addrctl restart'. > > Please refer the ip6addrctl(8) manpage and RFC 3484 for detail. Now i can understand the puzzle, thanks for the guidance. Your answer has been useful and is greatly appreciated. Byung-Hee -- "He's a responsible man in his own way." -- Michael Corleone, "Chapter 25", page 363 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
[FreeBSD 7.0-BETA1] strange behavior in hostname resolving order
To Whom It May Concern: (Cc'ed [EMAIL PROTECTED])
Usually i prefer 6to4(stf(4)) to 6over4(gif(4)) because some
tunnel providers like to limit bandwidth too musch. So until my
upstream ISP give me native ipv6 addresses (it's take long time maybe),
i'm going to use 6to4 instead of 6over4 continuous.
Here is my shot using 6to4:
[EMAIL PROTECTED]:~> uname -a
FreeBSD viola.izb.knu.ac.kr 7.0-BETA1 FreeBSD 7.0-BETA1 #0:
Fri Nov 2 12:13:10 KST 2007
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC i386
[EMAIL PROTECTED]:~> ifconfig rl0 | grep 2002
inet6 2002:9be6:9d5d:2:20b:6aff:fe56:969f prefixlen 64 autoconf
[EMAIL PROTECTED]:~> ping6 -c 5 mx.jp.freebsd.org.
PING6(56=40+8+8 bytes)
2002:9be6:9d5d:2:20b:6aff:fe56:969f --> 2001:218:422:1::15
16 bytes from 2001:218:422:1::15, icmp_seq=0 hlim=49 time=225.297 ms
16 bytes from 2001:218:422:1::15, icmp_seq=1 hlim=49 time=224.591 ms
16 bytes from 2001:218:422:1::15, icmp_seq=2 hlim=49 time=237.175 ms
16 bytes from 2001:218:422:1::15, icmp_seq=3 hlim=49 time=230.540 ms
16 bytes from 2001:218:422:1::15, icmp_seq=4 hlim=49 time=224.681 ms
--- mx.jp.freebsd.org ping6 statistics ---
5 packets transmitted, 5 packets received, 0.0% packet loss
round-trip min/avg/max/std-dev = 224.591/228.457/237.175/4.889 ms
[EMAIL PROTECTED]:~> traceroute6 mx.jp.freebsd.org.
traceroute6 to mx.jp.freebsd.org (2001:218:422:1::15) from
2002:9be6:9d5d:2:20b:6aff:fe56:969f, 64 hops max, 12 byte packets
1 2002:9be6:9d5d:2:250:4dff:fe00:5df3 1.541 ms 0.949 ms 1.154 ms
[..]
23 v6.imgsrc.co.jp 264.635 ms 226.812 ms 232.207 ms
24 castle.jp.FreeBSD.org 427.683 ms 219.659 ms 222.862 ms
[EMAIL PROTECTED]:~>
And from now on, i would give you one question. Why is 7.0-BETA1
different from another -RELEASE in hostname resolving order? AFAIK, at
least on 6.2-RELEASE, the order is first IPv6 and then IPv4. However,
7.0-BETA1 try to lookup in first IPv4 than IPv6. Here is the evidence:
[EMAIL PROTECTED]:~> uname -srm
FreeBSD 6.2-RELEASE-p8 i386
[EMAIL PROTECTED]:~> telnet mx.jp.freebsd.org 25
Trying 2001:218:422:1::15...
Connected to mx.jp.freebsd.org.
Escape character is '^]'.
[..]
[EMAIL PROTECTED]:~> ssh -v mx.jp.freebsd.org.
debug1: Connecting to mx.jp.freebsd.org. [2001:218:422:1::15]
^C
And
[EMAIL PROTECTED]:~> uname -srm
FreeBSD 7.0-BETA1 i386
[EMAIL PROTECTED]:~> telnet mx.jp.freebsd.org 25
Trying 210.226.20.15...
Connected to mx.jp.freebsd.org.
Escape character is '^]'.
[..]
[EMAIL PROTECTED]:~> ssh -v mx.jp.freebsd.org.
debug1: Connecting to mx.jp.freebsd.org. [210.226.20.15]
^C
What happended? Is there anyone to dislike IPv6 in src committers?
Please let me know the correct answer to this puzzle ;;
Byung-Hee
--
"After super, can you drive me and the kids to New York in your car?"
"That's what I came for."
-- Kay Adams and Tom Hagen, "Chapter 32", page 443
___
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.0-BETA1] strange behavior in hostname resolving order
Hi, >>>>> On Sat, 03 Nov 2007 00:05:07 +0900 >>>>> Byung-Hee HWANG <[EMAIL PROTECTED]> said: bh> To Whom It May Concern: (Cc'ed [EMAIL PROTECTED]) bh> Usually i prefer 6to4(stf(4)) to 6over4(gif(4)) because some bh> tunnel providers like to limit bandwidth too musch. So until my bh> upstream ISP give me native ipv6 addresses (it's take long time maybe), bh> i'm going to use 6to4 instead of 6over4 continuous. bh> Here is my shot using 6to4: bh> [EMAIL PROTECTED]:~> uname -a bh> FreeBSD viola.izb.knu.ac.kr 7.0-BETA1 FreeBSD 7.0-BETA1 #0: bh> Fri Nov 2 12:13:10 KST 2007 bh> [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC i386 bh> [EMAIL PROTECTED]:~> ifconfig rl0 | grep 2002 bh> inet6 2002:9be6:9d5d:2:20b:6aff:fe56:969f prefixlen 64 autoconf bh> [EMAIL PROTECTED]:~> ping6 -c 5 mx.jp.freebsd.org. bh> PING6(56=40+8+8 bytes) bh> 2002:9be6:9d5d:2:20b:6aff:fe56:969f --> 2001:218:422:1::15 bh> 16 bytes from 2001:218:422:1::15, icmp_seq=0 hlim=49 time=225.297 ms bh> 16 bytes from 2001:218:422:1::15, icmp_seq=1 hlim=49 time=224.591 ms bh> 16 bytes from 2001:218:422:1::15, icmp_seq=2 hlim=49 time=237.175 ms bh> 16 bytes from 2001:218:422:1::15, icmp_seq=3 hlim=49 time=230.540 ms bh> 16 bytes from 2001:218:422:1::15, icmp_seq=4 hlim=49 time=224.681 ms bh> --- mx.jp.freebsd.org ping6 statistics --- bh> 5 packets transmitted, 5 packets received, 0.0% packet loss bh> round-trip min/avg/max/std-dev = 224.591/228.457/237.175/4.889 ms bh> [EMAIL PROTECTED]:~> traceroute6 mx.jp.freebsd.org. bh> traceroute6 to mx.jp.freebsd.org (2001:218:422:1::15) from bh> 2002:9be6:9d5d:2:20b:6aff:fe56:969f, 64 hops max, 12 byte packets bh> 1 2002:9be6:9d5d:2:250:4dff:fe00:5df3 1.541 ms 0.949 ms 1.154 ms bh> [..] bh> 23 v6.imgsrc.co.jp 264.635 ms 226.812 ms 232.207 ms bh> 24 castle.jp.FreeBSD.org 427.683 ms 219.659 ms 222.862 ms bh> [EMAIL PROTECTED]:~> bh> And from now on, i would give you one question. Why is 7.0-BETA1 bh> different from another -RELEASE in hostname resolving order? AFAIK, at bh> least on 6.2-RELEASE, the order is first IPv6 and then IPv4. However, bh> 7.0-BETA1 try to lookup in first IPv4 than IPv6. Here is the evidence: bh> [EMAIL PROTECTED]:~> uname -srm bh> FreeBSD 6.2-RELEASE-p8 i386 bh> [EMAIL PROTECTED]:~> telnet mx.jp.freebsd.org 25 bh> Trying 2001:218:422:1::15... bh> Connected to mx.jp.freebsd.org. bh> Escape character is '^]'. bh> [..] bh> [EMAIL PROTECTED]:~> ssh -v mx.jp.freebsd.org. bh> debug1: Connecting to mx.jp.freebsd.org. [2001:218:422:1::15] bh> ^C bh> bh> And bh> [EMAIL PROTECTED]:~> uname -srm bh> FreeBSD 7.0-BETA1 i386 bh> [EMAIL PROTECTED]:~> telnet mx.jp.freebsd.org 25 bh> Trying 210.226.20.15... bh> Connected to mx.jp.freebsd.org. bh> Escape character is '^]'. bh> [..] bh> [EMAIL PROTECTED]:~> ssh -v mx.jp.freebsd.org. bh> debug1: Connecting to mx.jp.freebsd.org. [210.226.20.15] bh> ^C bh> What happended? Is there anyone to dislike IPv6 in src committers? bh> Please let me know the correct answer to this puzzle ;; The Default Address Selection is turned on by default after 6.2-RELEASE was out. According to RFC 3484, the default policy is as follows: Prefix Prec Label ::1/128 50 0 ::/0 40 1 2002::/16 30 2 ::/96 20 3 :::0.0.0.0/96 10 4 It means that communicating with native IP address is preferred over 6to4 address when source address and destination adddress are not 6to4 address. If you want not to treat 6to4 address as special, you can omit the line of 2002::/16 by putting the following lines into your /etc/ip6addrctl.conf: ::1/128 50 0 ::/0 40 1 ::/96 20 3 :::0.0.0.0/96 10 4 Then, run `/etc/rc.d/ip6addrctl restart'. Please refer the ip6addrctl(8) manpage and RFC 3484 for detail. Sincerely, -- Hajimu UMEMOTO @ Internet Mutual Aid Society Yokohama, Japan [EMAIL PROTECTED] [EMAIL PROTECTED],jp.}FreeBSD.org http://www.imasy.org/~ume/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: usb keyboard FreeBSD 7.0-BETA1
На Friday 02 November 2007 01:13:06 Paul Fraser написа: > For the sake of the record, I also have this problem. Have you tried this one http://selasky.org/hans_petter/usb4bsd/index.html ? ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: usb keyboard FreeBSD 7.0-BETA1
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Juraj Lutter Sent: Friday, 2 November 2007 9:24 AM To: Rainer Hurling Cc: Eric Millbrandt; freebsd-stable@freebsd.org Subject: Re: usb keyboard FreeBSD 7.0-BETA1 >>> Thanks, but my problem does not seems to be with X. The LEDs do not >>> work when using and not using X, single user mode, console, etc >>> Was your problem only in X? >> >> Yes, only in X for a few weeks. This was described in several threads >> before. >> > > FWIW, I am experiencing the same behaviour also with X.org on Linux -> > Keyboard LEDs just does not work. > The OP's problem is with the keyboard while at the console. The Xorg issue is well known and now fixed; it has no bearing on this issue which exists in FreeBSD's USB stack. Check -usb archives for a discussion, if you're interested. For the sake of the record, I also have this problem. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: usb keyboard FreeBSD 7.0-BETA1
Rainer Hurling wrote: Eric Millbrandt schrieb: Rainer Hurling wrote: Hi Eric, I reported yesterday on ports@, that with portupgrade of 30th October, rebuilding some xorg ports and restarting X now all LEDs of my USB-keyboards (3 systems) are working again. (FreeBSD 8.0-CURRENT i386) Hope this helps, Rainer Thanks, but my problem does not seems to be with X. The LEDs do not work when using and not using X, single user mode, console, etc Was your problem only in X? Yes, only in X for a few weeks. This was described in several threads before. FWIW, I am experiencing the same behaviour also with X.org on Linux -> Keyboard LEDs just does not work. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: usb keyboard FreeBSD 7.0-BETA1
Eric Millbrandt schrieb: Rainer Hurling wrote: Hi Eric, I reported yesterday on ports@, that with portupgrade of 30th October, rebuilding some xorg ports and restarting X now all LEDs of my USB-keyboards (3 systems) are working again. (FreeBSD 8.0-CURRENT i386) Hope this helps, Rainer Thanks, but my problem does not seems to be with X. The LEDs do not work when using and not using X, single user mode, console, etc Was your problem only in X? Yes, only in X for a few weeks. This was described in several threads before. Rainer Eric Millbrandt schrieb: Hello all, I has been a while since a FreeBSD release so I decided to help by running 7.0-BETA1 to speed things along. One small thing that I noticed off the bat is that the 'Num Lock', 'CAPS Lock', and 'Scroll Lock' leds on my usb keyboard do not function. The actual keys still do their job, but the Number and CAPS leds are always lit. I do remember them working under RELENG_6_2. I only have the one usb keyboard so I can't tell if it is vendor specific or not. My tablet pc also does not have a built in keyboard or a connection for a ps2 keyboard, so I cannot comment on those either. I will happily run any debug code needed or supply any information needed but do not have the time to find the issue myself. Below is output from usbdevs and messages./dev/usb3 and /dev/usb4 are a zoom pcmcia bluetooth card which did not fully function in RELENG_6_2. They now output some strange error messages, but bluetooth now works! output from usbdevs -d -v Controller /dev/usb0: addr 1: full speed, self powered, config 1, UHCI root hub(0x), Intel(0x), rev 1.00 uhub0 port 1 powered port 2 powered Controller /dev/usb1: addr 1: full speed, self powered, config 1, UHCI root hub(0x), Intel(0x), rev 1.00 uhub1 port 1 addr 2: low speed, power 100 mA, config 1, USB K/B+Mouse(0x0808), Jing-Mold(0x05af), rev 2.20 ukbd0 ums0 port 2 addr 3: full speed, power 100 mA, config 1, Fingerprint Sensor(0x2580), vendor 0x08ff(0x08ff), rev 6.21 ugen0 Controller /dev/usb2: addr 1: high speed, self powered, config 1, EHCI root hub(0x), Intel(0x), rev 1.00 uhub2 port 1 powered port 2 powered port 3 powered port 4 powered Controller /dev/usb3: addr 1: full speed, self powered, config 1, UHCI root hub(0x), VIA(0x), rev 1.00 uhub3 port 1 addr 2: full speed, self powered, config 1, product 0x0001(0x0001), vendor 0x0a12(0x0a12), rev 19.58 ubt0 port 2 powered Controller /dev/usb4: addr 1: full speed, self powered, config 1, product 0x(0x), vendor 0x(0x), rev 1.00 uhub4 port 1 powered port 2 powered /var/log/messages Oct 31 10:40:08 slate kernel: Copyright (c) 1992-2007 The FreeBSD Project. Oct 31 10:40:08 slate kernel: Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 Oct 31 10:40:08 slate kernel: The Regents of the University of California. All rights reserved. Oct 31 10:40:08 slate kernel: FreeBSD is a registered trademark of The FreeBSD Foundation. Oct 31 10:40:08 slate kernel: FreeBSD 7.0-BETA1 #0: Mon Oct 29 23:40:03 EDT 2007 Oct 31 10:40:08 slate kernel: [EMAIL PROTECTED]:/usr/obj/usr/src/sys/SLATE Oct 31 10:40:08 slate kernel: Timecounter "i8254" frequency 1193182 Hz quality 0 Oct 31 10:40:08 slate kernel: CPU: Intel(R) Pentium(R) M processor 1.20GHz (1197.37-MHz 686-class CPU) Oct 31 10:40:08 slate kernel: Origin = "GenuineIntel" Id = 0x6d8 Stepping = 8 Oct 31 10:40:08 slate kernel: Features=0xafe9fbff Oct 31 10:40:08 slate kernel: Features2=0x180 Oct 31 10:40:08 slate kernel: AMD Features=0x10 Oct 31 10:40:08 slate kernel: real memory = 1332150272 (1270 MB) Oct 31 10:40:08 slate kernel: avail memory = 1290915840 (1231 MB) Oct 31 10:40:08 slate kernel: ACPI APIC Table: Oct 31 10:40:08 slate kernel: ioapic0: Changing APIC ID to 1 Oct 31 10:40:08 slate kernel: ioapic0 irqs 0-23 on motherboard Oct 31 10:40:08 slate kernel: kbd1 at kbdmux0 Oct 31 10:40:08 slate kernel: ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413) Oct 31 10:40:08 slate kernel: acpi0: on motherboard Oct 31 10:40:08 slate kernel: acpi0: [ITHREAD] Oct 31 10:40:08 slate kernel: acpi0: Power Button (fixed) Oct 31 10:40:08 slate kernel: Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 Oct 31 10:40:08 slate kernel: acpi_timer0: <24-bit timer at 3.579545MHz> port 0x1008-0x100b on acpi0 Oct 31 10:40:08 slate kernel: cpu0: on acpi0 Oct 31 10:40:08 slate kernel: est0: Control> on cpu0 Oct 31 10:40:08 slate kernel: p4tcc0: on cpu0 Oct 31 10:40:08 slate kernel: pcib0: port 0xcf8-0xcff on acpi0 Oct 31 10:40:08 slate kernel: pci0: on pcib0 Oct 31 10:40:08 slate kernel: vgapci0: port 0x1400-0x1407 mem 0xb008-0xb00f,0xc000-0xcfff,0xb000-0xb003 irq 16 at device 2.0 on pci0 Oct 31 10:40:08 slate kernel: agp0: controller>
Re: usb keyboard FreeBSD 7.0-BETA1
Rainer Hurling wrote: Hi Eric, I reported yesterday on ports@, that with portupgrade of 30th October, rebuilding some xorg ports and restarting X now all LEDs of my USB-keyboards (3 systems) are working again. (FreeBSD 8.0-CURRENT i386) Hope this helps, Rainer Thanks, but my problem does not seems to be with X. The LEDs do not work when using and not using X, single user mode, console, etc Was your problem only in X? Eric Millbrandt schrieb: Hello all, I has been a while since a FreeBSD release so I decided to help by running 7.0-BETA1 to speed things along. One small thing that I noticed off the bat is that the 'Num Lock', 'CAPS Lock', and 'Scroll Lock' leds on my usb keyboard do not function. The actual keys still do their job, but the Number and CAPS leds are always lit. I do remember them working under RELENG_6_2. I only have the one usb keyboard so I can't tell if it is vendor specific or not. My tablet pc also does not have a built in keyboard or a connection for a ps2 keyboard, so I cannot comment on those either. I will happily run any debug code needed or supply any information needed but do not have the time to find the issue myself. Below is output from usbdevs and messages./dev/usb3 and /dev/usb4 are a zoom pcmcia bluetooth card which did not fully function in RELENG_6_2. They now output some strange error messages, but bluetooth now works! output from usbdevs -d -v Controller /dev/usb0: addr 1: full speed, self powered, config 1, UHCI root hub(0x), Intel(0x), rev 1.00 uhub0 port 1 powered port 2 powered Controller /dev/usb1: addr 1: full speed, self powered, config 1, UHCI root hub(0x), Intel(0x), rev 1.00 uhub1 port 1 addr 2: low speed, power 100 mA, config 1, USB K/B+Mouse(0x0808), Jing-Mold(0x05af), rev 2.20 ukbd0 ums0 port 2 addr 3: full speed, power 100 mA, config 1, Fingerprint Sensor(0x2580), vendor 0x08ff(0x08ff), rev 6.21 ugen0 Controller /dev/usb2: addr 1: high speed, self powered, config 1, EHCI root hub(0x), Intel(0x), rev 1.00 uhub2 port 1 powered port 2 powered port 3 powered port 4 powered Controller /dev/usb3: addr 1: full speed, self powered, config 1, UHCI root hub(0x), VIA(0x), rev 1.00 uhub3 port 1 addr 2: full speed, self powered, config 1, product 0x0001(0x0001), vendor 0x0a12(0x0a12), rev 19.58 ubt0 port 2 powered Controller /dev/usb4: addr 1: full speed, self powered, config 1, product 0x(0x), vendor 0x(0x), rev 1.00 uhub4 port 1 powered port 2 powered /var/log/messages Oct 31 10:40:08 slate kernel: Copyright (c) 1992-2007 The FreeBSD Project. Oct 31 10:40:08 slate kernel: Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 Oct 31 10:40:08 slate kernel: The Regents of the University of California. All rights reserved. Oct 31 10:40:08 slate kernel: FreeBSD is a registered trademark of The FreeBSD Foundation. Oct 31 10:40:08 slate kernel: FreeBSD 7.0-BETA1 #0: Mon Oct 29 23:40:03 EDT 2007 Oct 31 10:40:08 slate kernel: [EMAIL PROTECTED]:/usr/obj/usr/src/sys/SLATE Oct 31 10:40:08 slate kernel: Timecounter "i8254" frequency 1193182 Hz quality 0 Oct 31 10:40:08 slate kernel: CPU: Intel(R) Pentium(R) M processor 1.20GHz (1197.37-MHz 686-class CPU) Oct 31 10:40:08 slate kernel: Origin = "GenuineIntel" Id = 0x6d8 Stepping = 8 Oct 31 10:40:08 slate kernel: Features=0xafe9fbff Oct 31 10:40:08 slate kernel: Features2=0x180 Oct 31 10:40:08 slate kernel: AMD Features=0x10 Oct 31 10:40:08 slate kernel: real memory = 1332150272 (1270 MB) Oct 31 10:40:08 slate kernel: avail memory = 1290915840 (1231 MB) Oct 31 10:40:08 slate kernel: ACPI APIC Table: Oct 31 10:40:08 slate kernel: ioapic0: Changing APIC ID to 1 Oct 31 10:40:08 slate kernel: ioapic0 irqs 0-23 on motherboard Oct 31 10:40:08 slate kernel: kbd1 at kbdmux0 Oct 31 10:40:08 slate kernel: ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413) Oct 31 10:40:08 slate kernel: acpi0: on motherboard Oct 31 10:40:08 slate kernel: acpi0: [ITHREAD] Oct 31 10:40:08 slate kernel: acpi0: Power Button (fixed) Oct 31 10:40:08 slate kernel: Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 Oct 31 10:40:08 slate kernel: acpi_timer0: <24-bit timer at 3.579545MHz> port 0x1008-0x100b on acpi0 Oct 31 10:40:08 slate kernel: cpu0: on acpi0 Oct 31 10:40:08 slate kernel: est0: Control> on cpu0 Oct 31 10:40:08 slate kernel: p4tcc0: on cpu0 Oct 31 10:40:08 slate kernel: pcib0: port 0xcf8-0xcff on acpi0 Oct 31 10:40:08 slate kernel: pci0: on pcib0 Oct 31 10:40:08 slate kernel: vgapci0: port 0x1400-0x1407 mem 0xb008-0xb00f,0xc000-0xcfff,0xb000-0xb003 irq 16 at device 2.0 on pci0 Oct 31 10:40:08 slate kernel: agp0: controller> on vgapci0 Oct 31 10:40:08 slate kernel: agp0: detected 7932k stolen memory Oct 31 10:40:08 slate kernel: agp0: ap
Re: usb keyboard FreeBSD 7.0-BETA1
Hi Eric, I reported yesterday on ports@, that with portupgrade of 30th October, rebuilding some xorg ports and restarting X now all LEDs of my USB-keyboards (3 systems) are working again. (FreeBSD 8.0-CURRENT i386) Hope this helps, Rainer Eric Millbrandt schrieb: Hello all, I has been a while since a FreeBSD release so I decided to help by running 7.0-BETA1 to speed things along. One small thing that I noticed off the bat is that the 'Num Lock', 'CAPS Lock', and 'Scroll Lock' leds on my usb keyboard do not function. The actual keys still do their job, but the Number and CAPS leds are always lit. I do remember them working under RELENG_6_2. I only have the one usb keyboard so I can't tell if it is vendor specific or not. My tablet pc also does not have a built in keyboard or a connection for a ps2 keyboard, so I cannot comment on those either. I will happily run any debug code needed or supply any information needed but do not have the time to find the issue myself. Below is output from usbdevs and messages./dev/usb3 and /dev/usb4 are a zoom pcmcia bluetooth card which did not fully function in RELENG_6_2. They now output some strange error messages, but bluetooth now works! output from usbdevs -d -v Controller /dev/usb0: addr 1: full speed, self powered, config 1, UHCI root hub(0x), Intel(0x), rev 1.00 uhub0 port 1 powered port 2 powered Controller /dev/usb1: addr 1: full speed, self powered, config 1, UHCI root hub(0x), Intel(0x), rev 1.00 uhub1 port 1 addr 2: low speed, power 100 mA, config 1, USB K/B+Mouse(0x0808), Jing-Mold(0x05af), rev 2.20 ukbd0 ums0 port 2 addr 3: full speed, power 100 mA, config 1, Fingerprint Sensor(0x2580), vendor 0x08ff(0x08ff), rev 6.21 ugen0 Controller /dev/usb2: addr 1: high speed, self powered, config 1, EHCI root hub(0x), Intel(0x), rev 1.00 uhub2 port 1 powered port 2 powered port 3 powered port 4 powered Controller /dev/usb3: addr 1: full speed, self powered, config 1, UHCI root hub(0x), VIA(0x), rev 1.00 uhub3 port 1 addr 2: full speed, self powered, config 1, product 0x0001(0x0001), vendor 0x0a12(0x0a12), rev 19.58 ubt0 port 2 powered Controller /dev/usb4: addr 1: full speed, self powered, config 1, product 0x(0x), vendor 0x(0x), rev 1.00 uhub4 port 1 powered port 2 powered /var/log/messages Oct 31 10:40:08 slate kernel: Copyright (c) 1992-2007 The FreeBSD Project. Oct 31 10:40:08 slate kernel: Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 Oct 31 10:40:08 slate kernel: The Regents of the University of California. All rights reserved. Oct 31 10:40:08 slate kernel: FreeBSD is a registered trademark of The FreeBSD Foundation. Oct 31 10:40:08 slate kernel: FreeBSD 7.0-BETA1 #0: Mon Oct 29 23:40:03 EDT 2007 Oct 31 10:40:08 slate kernel: [EMAIL PROTECTED]:/usr/obj/usr/src/sys/SLATE Oct 31 10:40:08 slate kernel: Timecounter "i8254" frequency 1193182 Hz quality 0 Oct 31 10:40:08 slate kernel: CPU: Intel(R) Pentium(R) M processor 1.20GHz (1197.37-MHz 686-class CPU) Oct 31 10:40:08 slate kernel: Origin = "GenuineIntel" Id = 0x6d8 Stepping = 8 Oct 31 10:40:08 slate kernel: Features=0xafe9fbff Oct 31 10:40:08 slate kernel: Features2=0x180 Oct 31 10:40:08 slate kernel: AMD Features=0x10 Oct 31 10:40:08 slate kernel: real memory = 1332150272 (1270 MB) Oct 31 10:40:08 slate kernel: avail memory = 1290915840 (1231 MB) Oct 31 10:40:08 slate kernel: ACPI APIC Table: Oct 31 10:40:08 slate kernel: ioapic0: Changing APIC ID to 1 Oct 31 10:40:08 slate kernel: ioapic0 irqs 0-23 on motherboard Oct 31 10:40:08 slate kernel: kbd1 at kbdmux0 Oct 31 10:40:08 slate kernel: ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413) Oct 31 10:40:08 slate kernel: acpi0: on motherboard Oct 31 10:40:08 slate kernel: acpi0: [ITHREAD] Oct 31 10:40:08 slate kernel: acpi0: Power Button (fixed) Oct 31 10:40:08 slate kernel: Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 Oct 31 10:40:08 slate kernel: acpi_timer0: <24-bit timer at 3.579545MHz> port 0x1008-0x100b on acpi0 Oct 31 10:40:08 slate kernel: cpu0: on acpi0 Oct 31 10:40:08 slate kernel: est0: Control> on cpu0 Oct 31 10:40:08 slate kernel: p4tcc0: on cpu0 Oct 31 10:40:08 slate kernel: pcib0: port 0xcf8-0xcff on acpi0 Oct 31 10:40:08 slate kernel: pci0: on pcib0 Oct 31 10:40:08 slate kernel: vgapci0: port 0x1400-0x1407 mem 0xb008-0xb00f,0xc000-0xcfff,0xb000-0xb003 irq 16 at device 2.0 on pci0 Oct 31 10:40:08 slate kernel: agp0: controller> on vgapci0 Oct 31 10:40:08 slate kernel: agp0: detected 7932k stolen memory Oct 31 10:40:08 slate kernel: agp0: aperture size is 256M Oct 31 10:40:08 slate kernel: vgapci1: at device 2.1 on pci0 Oct 31 10:40:08 slate kernel: pcib1: irq 17 at device 28.0 on pci0 Oct 31 10:40:08 slate kernel: pci2: on pc
Re: Memory issues (was 7.0-BETA1 freeze using portmaster)
On Wed, Oct 31, 2007 at 08:50:44AM -1000, Robert Marella wrote: > > Robert Marella wrote: > > > > > It is looking like a hardware problem. I update portmaster to 1.24 > > > and it didn't help. When I tried with the -B option it froze in a > > > different place. I then csup the latest source rm'd /usr/obj and > > > attempted a buildworld. > > > > > > Lo and behold it froze up. It has been very hot the last few days > > > here in Kona but all the fans seem to pulling good air. I am now > > > running memtest and will let you know what I find. > > > > This is for the archives and to see if any hardware guru out there has > some helpful knowledge. > > This computer has a ASUS P4P800 mobo with 2Gig of ram (4x500M). Memtest > failed within minutes. I then ran each memory module one at a time and > each ran without failures no matter which socket it was in. > > Further tests showed that memory tests failed only when I had 2 or 4 > modules configured as dual channel *. The system is now running flawless > with 3 modules (1.5G) installed which forces single channel operation. > Again, the 3 modules can be in any sockets. I could be wrong but IIRC, some MBs of that era require very specific DIMM timing parameters and/or require "registered" (buffered) DIMMs when populating all slots for dual-channel operation. Usually they are more tolerant when running only a single bank or not running in dual-channel. If you can find the manual, you might want to check that possibility. -- Clifton -- Clifton Royston -- [EMAIL PROTECTED] / [EMAIL PROTECTED] President - I and I Computing * http://www.iandicomputing.com/ Custom programming, network design, systems and network consulting services ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Memory issues (was 7.0-BETA1 freeze using portmaster)
Robert Marella wrote: Robert Marella wrote: It is looking like a hardware problem. I update portmaster to 1.24 and it didn't help. When I tried with the -B option it froze in a different place. I then csup the latest source rm'd /usr/obj and attempted a buildworld. Lo and behold it froze up. It has been very hot the last few days here in Kona but all the fans seem to pulling good air. I am now running memtest and will let you know what I find. This is for the archives and to see if any hardware guru out there has some helpful knowledge. This computer has a ASUS P4P800 mobo with 2Gig of ram (4x500M). Memtest failed within minutes. I then ran each memory module one at a time and each ran without failures no matter which socket it was in. Further tests showed that memory tests failed only when I had 2 or 4 modules configured as dual channel *. The system is now running flawless with 3 modules (1.5G) installed which forces single channel operation. Again, the 3 modules can be in any sockets. Since the computer is about 4 years old I am not sure if I want to invest any additional $$ into it but I would suspect either the mother board or CPU as the culprit. I will be willing to test any ideas anyone has but I guess we can close this out as another strange effect of memory. Robert * From the User Guide: Mode DIMM_A1 DIMM_A2 DIMM_B1 DIMM_B2 Dual-channel X X X X X X X X Thanks for following up, and I'm glad you resolved it. It's good to remind people from time to time that hardware can and does fail so not every bug is in software :) Kris ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
usb keyboard FreeBSD 7.0-BETA1
Hello all, I has been a while since a FreeBSD release so I decided to help by running 7.0-BETA1 to speed things along. One small thing that I noticed off the bat is that the 'Num Lock', 'CAPS Lock', and 'Scroll Lock' leds on my usb keyboard do not function. The actual keys still do their job, but the Number and CAPS leds are always lit. I do remember them working under RELENG_6_2. I only have the one usb keyboard so I can't tell if it is vendor specific or not. My tablet pc also does not have a built in keyboard or a connection for a ps2 keyboard, so I cannot comment on those either. I will happily run any debug code needed or supply any information needed but do not have the time to find the issue myself. Below is output from usbdevs and messages. /dev/usb3 and /dev/usb4 are a zoom pcmcia bluetooth card which did not fully function in RELENG_6_2. They now output some strange error messages, but bluetooth now works! output from usbdevs -d -v Controller /dev/usb0: addr 1: full speed, self powered, config 1, UHCI root hub(0x), Intel(0x), rev 1.00 uhub0 port 1 powered port 2 powered Controller /dev/usb1: addr 1: full speed, self powered, config 1, UHCI root hub(0x), Intel(0x), rev 1.00 uhub1 port 1 addr 2: low speed, power 100 mA, config 1, USB K/B+Mouse(0x0808), Jing-Mold(0x05af), rev 2.20 ukbd0 ums0 port 2 addr 3: full speed, power 100 mA, config 1, Fingerprint Sensor(0x2580), vendor 0x08ff(0x08ff), rev 6.21 ugen0 Controller /dev/usb2: addr 1: high speed, self powered, config 1, EHCI root hub(0x), Intel(0x), rev 1.00 uhub2 port 1 powered port 2 powered port 3 powered port 4 powered Controller /dev/usb3: addr 1: full speed, self powered, config 1, UHCI root hub(0x), VIA(0x), rev 1.00 uhub3 port 1 addr 2: full speed, self powered, config 1, product 0x0001(0x0001), vendor 0x0a12(0x0a12), rev 19.58 ubt0 port 2 powered Controller /dev/usb4: addr 1: full speed, self powered, config 1, product 0x(0x), vendor 0x(0x), rev 1.00 uhub4 port 1 powered port 2 powered /var/log/messages Oct 31 10:40:08 slate kernel: Copyright (c) 1992-2007 The FreeBSD Project. Oct 31 10:40:08 slate kernel: Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 Oct 31 10:40:08 slate kernel: The Regents of the University of California. All rights reserved. Oct 31 10:40:08 slate kernel: FreeBSD is a registered trademark of The FreeBSD Foundation. Oct 31 10:40:08 slate kernel: FreeBSD 7.0-BETA1 #0: Mon Oct 29 23:40:03 EDT 2007 Oct 31 10:40:08 slate kernel: [EMAIL PROTECTED]:/usr/obj/usr/src/sys/SLATE Oct 31 10:40:08 slate kernel: Timecounter "i8254" frequency 1193182 Hz quality 0 Oct 31 10:40:08 slate kernel: CPU: Intel(R) Pentium(R) M processor 1.20GHz (1197.37-MHz 686-class CPU) Oct 31 10:40:08 slate kernel: Origin = "GenuineIntel" Id = 0x6d8 Stepping = 8 Oct 31 10:40:08 slate kernel: Features=0xafe9fbff Oct 31 10:40:08 slate kernel: Features2=0x180 Oct 31 10:40:08 slate kernel: AMD Features=0x10 Oct 31 10:40:08 slate kernel: real memory = 1332150272 (1270 MB) Oct 31 10:40:08 slate kernel: avail memory = 1290915840 (1231 MB) Oct 31 10:40:08 slate kernel: ACPI APIC Table: Oct 31 10:40:08 slate kernel: ioapic0: Changing APIC ID to 1 Oct 31 10:40:08 slate kernel: ioapic0 irqs 0-23 on motherboard Oct 31 10:40:08 slate kernel: kbd1 at kbdmux0 Oct 31 10:40:08 slate kernel: ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413) Oct 31 10:40:08 slate kernel: acpi0: on motherboard Oct 31 10:40:08 slate kernel: acpi0: [ITHREAD] Oct 31 10:40:08 slate kernel: acpi0: Power Button (fixed) Oct 31 10:40:08 slate kernel: Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 Oct 31 10:40:08 slate kernel: acpi_timer0: <24-bit timer at 3.579545MHz> port 0x1008-0x100b on acpi0 Oct 31 10:40:08 slate kernel: cpu0: on acpi0 Oct 31 10:40:08 slate kernel: est0: Control> on cpu0 Oct 31 10:40:08 slate kernel: p4tcc0: on cpu0 Oct 31 10:40:08 slate kernel: pcib0: port 0xcf8-0xcff on acpi0 Oct 31 10:40:08 slate kernel: pci0: on pcib0 Oct 31 10:40:08 slate kernel: vgapci0: port 0x1400-0x1407 mem 0xb008-0xb00f,0xc000-0xcfff,0xb000-0xb003 irq 16 at device 2.0 on pci0 Oct 31 10:40:08 slate kernel: agp0: controller> on vgapci0 Oct 31 10:40:08 slate kernel: agp0: detected 7932k stolen memory Oct 31 10:40:08 slate kernel: agp0: aperture size is 256M Oct 31 10:40:08 slate kernel: vgapci1: at device 2.1 on pci0 Oct 31 10:40:08 slate kernel: pcib1: irq 17 at device 28.0 on pci0 Oct 31 10:40:08 slate kernel: pci2: on pcib1 Oct 31 10:40:08 slate kernel: pci0:2:0:0: bad VPD cksum, remain 14 Oct 31 10:40:08 slate kernel: bge0: Controller, ASIC rev. 0x4101> mem 0xb010-0xb010 irq 16 at device 0.0 on pci2 Oct 31 10:40:08 slate kernel: miibus0: on bge0 Oct 31 10:40:08 slate ker
Memory issues (was 7.0-BETA1 freeze using portmaster)
> Robert Marella wrote: > > > It is looking like a hardware problem. I update portmaster to 1.24 > > and it didn't help. When I tried with the -B option it froze in a > > different place. I then csup the latest source rm'd /usr/obj and > > attempted a buildworld. > > > > Lo and behold it froze up. It has been very hot the last few days > > here in Kona but all the fans seem to pulling good air. I am now > > running memtest and will let you know what I find. > This is for the archives and to see if any hardware guru out there has some helpful knowledge. This computer has a ASUS P4P800 mobo with 2Gig of ram (4x500M). Memtest failed within minutes. I then ran each memory module one at a time and each ran without failures no matter which socket it was in. Further tests showed that memory tests failed only when I had 2 or 4 modules configured as dual channel *. The system is now running flawless with 3 modules (1.5G) installed which forces single channel operation. Again, the 3 modules can be in any sockets. Since the computer is about 4 years old I am not sure if I want to invest any additional $$ into it but I would suspect either the mother board or CPU as the culprit. I will be willing to test any ideas anyone has but I guess we can close this out as another strange effect of memory. Robert * From the User Guide: Mode DIMM_A1 DIMM_A2 DIMM_B1 DIMM_B2 Dual-channel X X X X X X X X ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 7.0 BETA1 and Thinkpad T61p : Wireless misadventure
- Original Message From: Scot Hetzel <[EMAIL PROTECTED]> To: Mike Pumford <[EMAIL PROTECTED]> Cc: [EMAIL PROTECTED]; freebsd-stable@freebsd.org; Abdullah Ibn Hamad Al-Marri <[EMAIL PROTECTED]> Sent: Wednesday, October 31, 2007 6:56:58 AM Subject: Re: 7.0 BETA1 and Thinkpad T61p : Wireless misadventure On 10/30/07, Mike Pumford <[EMAIL PROTECTED]> wrote: > Abdullah Ibn Hamad Al-Marri wrote: > > > > > Previously I didn't mention that there are some functions missing from > > > > the FreeBSD's NDIS api. These are: > > > > With the help of NDIS reference and Linux ndiswrapper I have been able > > > > to implement all but KeBugCheckEx (they are all rather simple but I > > > Can help you with this one. This is the Windows equivalent of panic(). > So just call panic with an appropriate string. If the string includes > the bugcheck code and parameters so much the better. > Thanks for your hint to use panic() in the KeBugCheckEx function. I have KeBugCheckEx partially implemented. It currently prints the bugcheck code and the 4 paramators that are sent to KeBugCheckEx. The KeBugCheckEx function still needs to be changed to display the right information depending on the bugcheck code. Abdullah, I made a minor change to your patch, strncat should be prefixed with ntoskrnl_strncat. changed IMPORT_CFUNC(strncat..) to IMPORT_CFUNC_MAP(ntoskrnl_strncat..). Scot -Inline Attachment Follows- Index: ndis_var.h === RCS file: /home/ncvs/src/sys/compat/ndis/ndis_var.h,v retrieving revision 1.47 diff -u -r1.47 ndis_var.h --- ndis_var.h6 Apr 2007 11:18:57 -1.47 +++ ndis_var.h31 Oct 2007 03:31:24 - @@ -49,6 +49,10 @@ typedef register_t ndis_kspin_lock; typedef uint8_t ndis_kirql; +/* Version of NDIS supported by FreeBSD */ +#defineNDIS_VERSION_510x00050001 +#defineNDIS_VERSIONNDIS_VERSION_51 + /* * NDIS status codes (there are lots of them). The ones that * don't seem to fit the pattern are actually mapped to generic Index: ntoskrnl_var.h === RCS file: /home/ncvs/src/sys/compat/ndis/ntoskrnl_var.h,v retrieving revision 1.43 diff -u -r1.43 ntoskrnl_var.h --- ntoskrnl_var.h17 Aug 2006 22:50:32 -1.43 +++ ntoskrnl_var.h31 Oct 2007 03:31:24 - @@ -1202,14 +1202,22 @@ /* Memory pool types, for ExAllocatePoolWithTag() */ -#define NonPagedPool0x -#define PagedPool0x0001 -#define NonPagedPoolMustSucceed0x0002 -#define DontUseThisType0x0003 -#define NonPagedPoolCacheAligned0x0004 -#define PagedPoolCacheAligned0x0005 -#define NonPagedPoolCacheAlignedMustS0x0006 -#define MaxPoolType0x0007 +#defineNonPagedPool0x +#definePagedPool0x0001 +#defineNonPagedPoolMustSucceed0x0002 +#defineDontUseThisType0x0003 +#defineNonPagedPoolCacheAligned0x0004 +#definePagedPoolCacheAligned0x0005 +#defineNonPagedPoolCacheAlignedMustS0x0006 +#defineMaxPoolType0x0007 + +#defineNonPagedPoolSession0x0020 +#definePagedPoolSession0x0021 +#defineNonPagedPoolMustSucceedSession0x0022 +#defineDontUseThisTypeSession0x0023 +#defineNonPagedPoolCacheAlignedSession0x0024 +#definePagedPoolCacheAlignedSession0x0025 +#defineNonPagedPoolCacheAlignedMustSSession0x0026 /* * IO_WORKITEM is an opaque structures that must be allocated @@ -1357,8 +1365,12 @@ extern uint8_t KeSynchronizeExecution(kinterrupt *, void *, void *); extern uintptr_t InterlockedExchange(volatile uint32_t *, uintptr_t); +extern void *ExAllocatePool(uint32_t, size_t); +extern void *ExAllocatePoolWithQuota(uint32_t, size_t); +extern void *ExAllocatePoolWithQuotaTag(uint32_t, size_t, uint32_t); extern void *ExAllocatePoolWithTag(uint32_t, size_t, uint32_t); extern void ExFreePool(void *); +extern void ExFreePoolWithTag(void *, uint32_t); extern uint32_t IoConnectInterrupt(kinterrupt **, void *, void *, kspin_lock *, uint32_t, uint8_t, uint8_t, uint8_t, uint8_t, uint32_t, uint8_t); Index: subr_ndis.c === RCS file: /home/ncvs/src/sys/compat/ndis/subr_ndis.c,v retrieving revision 1.108 diff -u -r1.108 subr_ndis.c --- subr_ndis.c31 May 2007 11:51:49 -1.108 +++ subr_ndis.c31 Oct 2007 03:31:24 - @@ -272,6 +272,7 @@ static void NdisUnmapFile(ndis_ha
Re: 7.0 BETA1 and Thinkpad T61p : Wireless misadventure
On 10/30/07, Mike Pumford <[EMAIL PROTECTED]> wrote: > Abdullah Ibn Hamad Al-Marri wrote: > > > > > Previously I didn't mention that there are some functions missing from > > > > the FreeBSD's NDIS api. These are: > > > > With the help of NDIS reference and Linux ndiswrapper I have been able > > > > to implement all but KeBugCheckEx (they are all rather simple but I > > > Can help you with this one. This is the Windows equivalent of panic(). > So just call panic with an appropriate string. If the string includes > the bugcheck code and parameters so much the better. > Thanks for your hint to use panic() in the KeBugCheckEx function. I have KeBugCheckEx partially implemented. It currently prints the bugcheck code and the 4 paramators that are sent to KeBugCheckEx. The KeBugCheckEx function still needs to be changed to display the right information depending on the bugcheck code. Abdullah, I made a minor change to your patch, strncat should be prefixed with ntoskrnl_strncat. changed IMPORT_CFUNC(strncat..) to IMPORT_CFUNC_MAP(ntoskrnl_strncat..). Scot Index: ndis_var.h === RCS file: /home/ncvs/src/sys/compat/ndis/ndis_var.h,v retrieving revision 1.47 diff -u -r1.47 ndis_var.h --- ndis_var.h 6 Apr 2007 11:18:57 - 1.47 +++ ndis_var.h 31 Oct 2007 03:31:24 - @@ -49,6 +49,10 @@ typedef register_t ndis_kspin_lock; typedef uint8_t ndis_kirql; +/* Version of NDIS supported by FreeBSD */ +#defineNDIS_VERSION_51 0x00050001 +#defineNDIS_VERSIONNDIS_VERSION_51 + /* * NDIS status codes (there are lots of them). The ones that * don't seem to fit the pattern are actually mapped to generic Index: ntoskrnl_var.h === RCS file: /home/ncvs/src/sys/compat/ndis/ntoskrnl_var.h,v retrieving revision 1.43 diff -u -r1.43 ntoskrnl_var.h --- ntoskrnl_var.h 17 Aug 2006 22:50:32 - 1.43 +++ ntoskrnl_var.h 31 Oct 2007 03:31:24 - @@ -1202,14 +1202,22 @@ /* Memory pool types, for ExAllocatePoolWithTag() */ -#define NonPagedPool 0x -#define PagedPool 0x0001 -#define NonPagedPoolMustSucceed0x0002 -#define DontUseThisType0x0003 -#define NonPagedPoolCacheAligned 0x0004 -#define PagedPoolCacheAligned 0x0005 -#define NonPagedPoolCacheAlignedMustS 0x0006 -#define MaxPoolType0x0007 +#defineNonPagedPool0x +#definePagedPool 0x0001 +#defineNonPagedPoolMustSucceed 0x0002 +#defineDontUseThisType 0x0003 +#defineNonPagedPoolCacheAligned0x0004 +#definePagedPoolCacheAligned 0x0005 +#defineNonPagedPoolCacheAlignedMustS 0x0006 +#defineMaxPoolType 0x0007 + +#defineNonPagedPoolSession 0x0020 +#definePagedPoolSession0x0021 +#defineNonPagedPoolMustSucceedSession 0x0022 +#defineDontUseThisTypeSession 0x0023 +#defineNonPagedPoolCacheAlignedSession 0x0024 +#definePagedPoolCacheAlignedSession0x0025 +#defineNonPagedPoolCacheAlignedMustSSession0x0026 /* * IO_WORKITEM is an opaque structures that must be allocated @@ -1357,8 +1365,12 @@ extern uint8_t KeSynchronizeExecution(kinterrupt *, void *, void *); extern uintptr_t InterlockedExchange(volatile uint32_t *, uintptr_t); +extern void *ExAllocatePool(uint32_t, size_t); +extern void *ExAllocatePoolWithQuota(uint32_t, size_t); +extern void *ExAllocatePoolWithQuotaTag(uint32_t, size_t, uint32_t); extern void *ExAllocatePoolWithTag(uint32_t, size_t, uint32_t); extern void ExFreePool(void *); +extern void ExFreePoolWithTag(void *, uint32_t); extern uint32_t IoConnectInterrupt(kinterrupt **, void *, void *, kspin_lock *, uint32_t, uint8_t, uint8_t, uint8_t, uint8_t, uint32_t, uint8_t); Index: subr_ndis.c === RCS file: /home/ncvs/src/sys/compat/ndis/subr_ndis.c,v retrieving revision 1.108 diff -u -r1.108 subr_ndis.c --- subr_ndis.c 31 May 2007 11:51:49 - 1.108 +++ subr_ndis.c 31 Oct 2007 03:31:24 - @@ -272,6 +272,7 @@ static void NdisUnmapFile(ndis_handle); static void NdisCloseFile(ndis_handle); static uint8_t NdisSystemProcessorCount(void); +static void NdisGetCurrentProcessorCounts(uint32_t *, uint32_t *, uint32_t*); static void NdisMIndicateStatusComplete(ndis_handle); static void NdisMIndicateStatus(ndis_handle, ndis_status, void *, uint32_t); @@ -282,6 +283,7 @@ uint32
Re: 7.0-BETA1 freeze using portmaster
Robert Marella wrote: > It is looking like a hardware problem. I update portmaster to 1.24 and > it didn't help. When I tried with the -B option it froze in a different > place. I then csup the latest source rm'd /usr/obj and attempted a > buildworld. > > Lo and behold it froze up. It has been very hot the last few days here > in Kona but all the fans seem to pulling good air. I am now running > memtest and will let you know what I find. Ok, thanks for the update. FYI, if you're using portmaster version 1.24 you need the following patch: http://dougbarton.us/portmaster-install-fix.patch good luck, Doug -- This .signature sanitized for your protection ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 7.0-BETA1 freeze using portmaster
On Tue, 30 Oct 2007 11:16:09 -0700 (PDT) Doug Barton <[EMAIL PROTECTED]> wrote: > On Tue, 30 Oct 2007, Robert Marella wrote: > > > On Mon, 29 Oct 2007 23:05:06 -0700 (PDT) > > Doug Barton <[EMAIL PROTECTED]> wrote: > > > >> On Mon, 29 Oct 2007, Robert Marella wrote: > >> > >>> Aloha > >>> > >>> [EMAIL PROTECTED] ~> uname -a > >>> FreeBSD p4.konav201.local 7.0-BETA1 FreeBSD 7.0-BETA1 #2: Mon Oct > >>> 29 07:58:19 HST 2007 root@:/usr/obj/usr/src/sys/GENERIC i386 > >>> > >>> This was a fresh install of 7 from a couple of months ago when it > >>> was -current. I have been updating > >> > >> src, ports, or both? > > Well, that's good news I suppose. Please install the latest (1.24) > version of portmaster, and try again, with and without the -B flag > and let me know how it goes. > > > Thank you for responding. Does this mean that I alone am > > experiencing this problem? > > Yes. > It is looking like a hardware problem. I update portmaster to 1.24 and it didn't help. When I tried with the -B option it froze in a different place. I then csup the latest source rm'd /usr/obj and attempted a buildworld. Lo and behold it froze up. It has been very hot the last few days here in Kona but all the fans seem to pulling good air. I am now running memtest and will let you know what I find. Thanks for your help Robert ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 7.0-BETA1 freeze using portmaster
Robert Marella wrote: Aloha [EMAIL PROTECTED] ~> uname -a FreeBSD p4.konav201.local 7.0-BETA1 FreeBSD 7.0-BETA1 #2: Mon Oct 29 07:58:19 HST 2007 root@:/usr/obj/usr/src/sys/GENERIC i386 This was a fresh install of 7 from a couple of months ago when it was -current. I have been updating at least weekly since then. I csup'd and did the buildworld/kernel thing this past Friday. At that time I change from the generic kernel to a generic using -ULE. When updating the ports over the weekend using "portmaster -a -u" the system would freeze at "Creating a backup package for old version pkg-glob". Where pkg-glob is whatever was being updated at the time of course. The keyboard would not respond and I was unable to ssh into it from other computers on my network. It would not even respond to a ping request. The only recovery is a power off reboot. I was able to update my ports by doing a make deinstall, make clean, make install clean from the ports directory. This morning I tried to update python25 and had the same results. I reverted back to the generic kernel and had the same results. I have tried it as root, using sudo from my user login and also from su. All fail the same way. I have no trouble with portmaster from my 6.2-Stable computer. FreeBSD 7.0-BETA1 #2: Mon Oct 29 07:58:19 HST 2007 root@:/usr/obj/usr/src/sys/GENERIC Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel(R) Pentium(R) 4 CPU 2.60GHz (2598.76-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0xf29 Stepping = 9 Features=0xbfebfbff Features2=0x4400 Logical CPUs per core: 2 real memory = 2146631680 (2047 MB) avail memory = 2086854656 (1990 MB) I was testing hyperthreading but have disabled it also with the same failure. Thanks Robert ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]" http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kerneldebug.html Kris ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 7.0-BETA1 freeze using portmaster
On Tue, 30 Oct 2007, Robert Marella wrote: On Mon, 29 Oct 2007 23:05:06 -0700 (PDT) Doug Barton <[EMAIL PROTECTED]> wrote: On Mon, 29 Oct 2007, Robert Marella wrote: Aloha [EMAIL PROTECTED] ~> uname -a FreeBSD p4.konav201.local 7.0-BETA1 FreeBSD 7.0-BETA1 #2: Mon Oct 29 07:58:19 HST 2007 root@:/usr/obj/usr/src/sys/GENERIC i386 This was a fresh install of 7 from a couple of months ago when it was -current. I have been updating src, ports, or both? It was a clean install. I backed up my data and did a new install from a snapshot iso. I reinstalled all 3rd party software from ports. Ok. What happens if you just run 'pkg_create -b '? I strongly suspect that this is a problem with your pkg_create binary, since that's all portmaster is doing in that spot. If the pkg_create command failed then you would see an error message and portmaster would exit. Okay, I just did that from my /root directory and it worked. Well, that's good news I suppose. Please install the latest (1.24) version of portmaster, and try again, with and without the -B flag and let me know how it goes. Thank you for responding. Does this mean that I alone am experiencing this problem? Yes. One other thing, I replaced my video card last week with an NVIDIA card. I installed the nvidia port which brought in linux ports and compat5x. Could this have messed up my libraries? Highly unlikely, but thanks for mentioning it. Doug -- This .signature sanitized for your protection ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 7.0-BETA1 freeze using portmaster
On Mon, 29 Oct 2007 23:05:06 -0700 (PDT) Doug Barton <[EMAIL PROTECTED]> wrote: > On Mon, 29 Oct 2007, Robert Marella wrote: > > > Aloha > > > > [EMAIL PROTECTED] ~> uname -a > > FreeBSD p4.konav201.local 7.0-BETA1 FreeBSD 7.0-BETA1 #2: Mon Oct 29 > > 07:58:19 HST 2007 root@:/usr/obj/usr/src/sys/GENERIC i386 > > > > This was a fresh install of 7 from a couple of months ago when it > > was -current. I have been updating > > src, ports, or both? It was a clean install. I backed up my data and did a new install from a snapshot iso. I reinstalled all 3rd party software from ports. > > > at least weekly since then. I csup'd and did the buildworld/kernel > > thing this past Friday. At that time I change from the generic > > kernel to a generic using -ULE. > > Assuming that you're now tracking RELENG_7, and assuming that you > installed the new kernel and world, did you clean out all the old > libraries and includes from before the branch? See above > > > When updating the ports over the weekend using "portmaster -a -u" > > the > > This isn't really relevant to your question, but I'd like to point > out that I think people are using the -u flag a lot more than they > really need to. Under normal circumstances once you're past the 'make > config' stage and the ports start actually compiling there won't be > any interaction required. In fact, now that the OPTIONS framework is > fixed if you already have options files for the ports you have > installed, and those options haven't changed, you won't even get > those screens to deal with. Noted > > > system would freeze at "Creating a backup package for old version > > pkg-glob". Where pkg-glob is whatever was being updated at the time > > of course. > > What happens if you just run 'pkg_create -b from /var/db/pkg>'? I strongly suspect that this is a problem with > your pkg_create binary, since that's all portmaster is doing in that > spot. If the pkg_create command failed then you would see an error > message and portmaster would exit. Okay, I just did that from my /root directory and it worked. p4# ls -l total 8528 drwx-- 2 root wheel 512 Oct 9 11:46 Desktop drwxr-xr-x 2 root wheel 512 Oct 8 19:31 bin -rw-r--r-- 1 root wheel 8668867 Oct 30 07:07 python25-2.5.1.tbz -rwxr-xr-x 1 root wheel 184 Oct 12 08:18 supfile.os > > hth, > > Doug Thank you for responding. Does this mean that I alone am experiencing this problem? One other thing, I replaced my video card last week with an NVIDIA card. I installed the nvidia port which brought in linux ports and compat5x. Could this have messed up my libraries? Robert > ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 7.0 BETA1 and Thinkpad T61p : Wireless misadventure
Abdullah Ibn Hamad Al-Marri wrote: Previously I didn't mention that there are some functions missing from the FreeBSD's NDIS api. These are: With the help of NDIS reference and Linux ndiswrapper I have been able to implement all but KeBugCheckEx (they are all rather simple but I Can help you with this one. This is the Windows equivalent of panic(). So just call panic with an appropriate string. If the string includes the bugcheck code and parameters so much the better. Mike ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 7.0-BETA1 freeze using portmaster
On Mon, 29 Oct 2007, Robert Marella wrote: Aloha [EMAIL PROTECTED] ~> uname -a FreeBSD p4.konav201.local 7.0-BETA1 FreeBSD 7.0-BETA1 #2: Mon Oct 29 07:58:19 HST 2007 root@:/usr/obj/usr/src/sys/GENERIC i386 This was a fresh install of 7 from a couple of months ago when it was -current. I have been updating src, ports, or both? at least weekly since then. I csup'd and did the buildworld/kernel thing this past Friday. At that time I change from the generic kernel to a generic using -ULE. Assuming that you're now tracking RELENG_7, and assuming that you installed the new kernel and world, did you clean out all the old libraries and includes from before the branch? When updating the ports over the weekend using "portmaster -a -u" the This isn't really relevant to your question, but I'd like to point out that I think people are using the -u flag a lot more than they really need to. Under normal circumstances once you're past the 'make config' stage and the ports start actually compiling there won't be any interaction required. In fact, now that the OPTIONS framework is fixed if you already have options files for the ports you have installed, and those options haven't changed, you won't even get those screens to deal with. system would freeze at "Creating a backup package for old version pkg-glob". Where pkg-glob is whatever was being updated at the time of course. What happens if you just run 'pkg_create -b '? I strongly suspect that this is a problem with your pkg_create binary, since that's all portmaster is doing in that spot. If the pkg_create command failed then you would see an error message and portmaster would exit. hth, Doug -- This .signature sanitized for your protection ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: portupgrade error with 7.0-BETA1
Diane Bruce wrote: On Mon, Oct 29, 2007 at 09:04:12PM +0100, Kris Kennaway wrote: Diane Bruce wrote: On Sun, Oct 28, 2007 at 11:38:26PM +0100, Kris Kennaway wrote: ... What do you mean by obsolete libs? The portupgrade -fa should have fixed precisely that ;) Yes, I was going to suggest that one myself, I had forgotten to mention it. It's not one I wanted to take right now, for various reasons. But it is a good suggestion, I'm sure others will find it useful. It's not just a good suggestion, it's mandatory ;-) Kris ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: portupgrade error with 7.0-BETA1
On Mon, Oct 29, 2007 at 09:04:12PM +0100, Kris Kennaway wrote: > Diane Bruce wrote: > >On Sun, Oct 28, 2007 at 11:38:26PM +0100, Kris Kennaway wrote: ... > What do you mean by obsolete libs? The portupgrade -fa should have > fixed precisely that ;) Yes, I was going to suggest that one myself, I had forgotten to mention it. It's not one I wanted to take right now, for various reasons. But it is a good suggestion, I'm sure others will find it useful. - Diane -- - [EMAIL PROTECTED] [EMAIL PROTECTED] http://www.db.net/~db ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: portupgrade error with 7.0-BETA1
Diane Bruce wrote: On Sun, Oct 28, 2007 at 11:38:26PM +0100, Kris Kennaway wrote: Marc UBM Bocklet wrote: On Sun, 28 Oct 2007 18:45:59 +0100 Marc "UBM" Bocklet <[EMAIL PROTECTED]> wrote: ... A tip from Diane Bruce ([EMAIL PROTECTED]) did the trick: This one bit me as well. It's an obsolete library (libthr) in the binary, Recompile ruby18 and problem will go away. You'll find other programs will do this too, but a lot of them disapear after doing a portupgrade. ...which is a necessary part of any upgrade to a new branch. Just to keep it clear. ;-) I always upgrade my portupgrade manually after a branch, but his problems sounded like he had not. What I am getting bit with are things like: -rw--- 1 db wheel 1056768 Oct 28 23:12 xfce4-mixer-plugin.core -rw--- 1 db wheel 1159168 Oct 28 23:12 xfdesktop.core -rw--- 1 db wheel 1024000 Oct 28 23:12 xfce-mcs-manager.core -rw--- 1 db wheel 978944 Oct 28 23:12 xscreensaver-gl-hel.core -rw--- 1 db wheel 1032192 Oct 28 23:03 xfce4-session.core All due to obsolete libs. Since there was a gnome import lately, updating now seemed a good idea. What do you mean by obsolete libs? The portupgrade -fa should have fixed precisely that ;) Kris ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
7.0-BETA1 freeze using portmaster
Aloha [EMAIL PROTECTED] ~> uname -a FreeBSD p4.konav201.local 7.0-BETA1 FreeBSD 7.0-BETA1 #2: Mon Oct 29 07:58:19 HST 2007 root@:/usr/obj/usr/src/sys/GENERIC i386 This was a fresh install of 7 from a couple of months ago when it was -current. I have been updating at least weekly since then. I csup'd and did the buildworld/kernel thing this past Friday. At that time I change from the generic kernel to a generic using -ULE. When updating the ports over the weekend using "portmaster -a -u" the system would freeze at "Creating a backup package for old version pkg-glob". Where pkg-glob is whatever was being updated at the time of course. The keyboard would not respond and I was unable to ssh into it from other computers on my network. It would not even respond to a ping request. The only recovery is a power off reboot. I was able to update my ports by doing a make deinstall, make clean, make install clean from the ports directory. This morning I tried to update python25 and had the same results. I reverted back to the generic kernel and had the same results. I have tried it as root, using sudo from my user login and also from su. All fail the same way. I have no trouble with portmaster from my 6.2-Stable computer. FreeBSD 7.0-BETA1 #2: Mon Oct 29 07:58:19 HST 2007 root@:/usr/obj/usr/src/sys/GENERIC Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel(R) Pentium(R) 4 CPU 2.60GHz (2598.76-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0xf29 Stepping = 9 Features=0xbfebfbff Features2=0x4400 Logical CPUs per core: 2 real memory = 2146631680 (2047 MB) avail memory = 2086854656 (1990 MB) I was testing hyperthreading but have disabled it also with the same failure. Thanks Robert ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: portupgrade error with 7.0-BETA1
On Sun, Oct 28, 2007 at 11:38:26PM +0100, Kris Kennaway wrote: > Marc UBM Bocklet wrote: > >On Sun, 28 Oct 2007 18:45:59 +0100 > >Marc "UBM" Bocklet <[EMAIL PROTECTED]> wrote: > > ... > > > >A tip from Diane Bruce ([EMAIL PROTECTED]) did the trick: > > > > > > > >This one bit me as well. It's an obsolete library (libthr) in the > >binary, Recompile ruby18 and problem will go away. You'll find other > >programs will do this too, but a lot of them disapear after doing a > >portupgrade. > > > > > > ...which is a necessary part of any upgrade to a new branch. > Just to keep it clear. ;-) I always upgrade my portupgrade manually after a branch, but his problems sounded like he had not. What I am getting bit with are things like: -rw--- 1 db wheel 1056768 Oct 28 23:12 xfce4-mixer-plugin.core -rw--- 1 db wheel 1159168 Oct 28 23:12 xfdesktop.core -rw--- 1 db wheel 1024000 Oct 28 23:12 xfce-mcs-manager.core -rw--- 1 db wheel 978944 Oct 28 23:12 xscreensaver-gl-hel.core -rw--- 1 db wheel 1032192 Oct 28 23:03 xfce4-session.core All due to obsolete libs. Since there was a gnome import lately, updating now seemed a good idea. > Kris > - Diane -- - [EMAIL PROTECTED] [EMAIL PROTECTED] http://www.db.net/~db ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: portupgrade error with 7.0-BETA1
Roland Smith wrote: > On Sun, Oct 28, 2007 at 11:31:49PM +0100, Marc UBM Bocklet wrote: >>> and then tried using portupgrade, which promptly fails with: >>> >>> Fatal error 'Cannot allocate red zone for initial thread' at line 382 >>> in file /usr/src/lib/libthr/thread/thr_init.c (errno = 12) >>> Illegal instruction: 4 (core dumped) >>> >>> (the red zone error ist repeated about 20 times). > [snip] >> This one bit me as well. It's an obsolete library (libthr) in the >> binary, Recompile ruby18 and problem will go away. You'll find other >> programs will do this too, but a lot of them disapear after doing a >> portupgrade. > > After updated to a new major version of FreeBSD (6->7, not 6.2->6.3) is > to make a list of all ports, remove them all with pkg_delete and install > them from scratch. > > That is the only sure way to prevent programs linking to older libraries. > > And while your at it, it would be a good idea to clean out the old cruft > from (/usr)/lib as well. > > Roland The new sysutils/bsdadminscripts release has a script called pkg_libchk that tells you all the packages which need to be rebuild/relinked. http://www.freebsd.org/cgi/query-pr.cgi?pr=117533 I wrote it just for the occasion to update from RELENG_6 to RELENG_7. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: pf broken in 7.0-BETA1 ?
Abdullah Ibn Hamad Al-Marri wrote:
- Original Message
From: Andrew Birukov <[EMAIL PROTECTED]>
To: Ermal Luçi <[EMAIL PROTECTED]>
Cc: freebsd-stable@freebsd.org; [EMAIL PROTECTED]
Sent: Sunday, October 28, 2007 10:34:56 PM
Subject: Re: pf broken in 7.0-BETA1 ?
Ermal Luçi wrote:
Try using
pass out on $ext_if proto tcp from any to any tos 0x10 no keep
state
queue ssh
and it should work as you expect!
pf.conf
---
ext_if="xl0"
altq on $ext_if priq bandwidth 520Kb queue { ssh, traf }
queue ssh priority 1
queue traf priority 15 priq(default)
pass in all
pass out all
pass out on $ext_if proto tcp from any to any tos 0x10 no keep state
queue ssh
---
# /etc/rc.d/pf restart
Disabling pf.
pf disabled
Enabling pf.
/etc/pf.conf:10: syntax error
pfctl: Syntax error in config file: pf rules not loaded
pf enabled
Unfortunately syntax error...
--
Andrew Biriukov
[EMAIL PROTECTED]
Is this related to your problem?
http://www.nabble.com/Suggestion-with-patch%2C-change-PF-TOS-matching-to-bitmask-tf4697797.html
It is not related, but interesting for me.
I am going to try this patch.
Thank you!
--
Andrew Biriukov
[EMAIL PROTECTED]
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: pf broken in 7.0-BETA1 ?
Paul Schenkeveld wrote:
On Sun, Oct 28, 2007 at 04:34:56PM -0300, Andrew Birukov wrote:
Ermal Luçi wrote:
Try using
pass out on $ext_if proto tcp from any to any tos 0x10 no keep state queue
ssh
and it should work as you expect!
pf.conf
---
ext_if="xl0"
altq on $ext_if priq bandwidth 520Kb queue { ssh, traf }
queue ssh priority 1
queue traf priority 15 priq(default)
pass in all
pass out all
pass out on $ext_if proto tcp from any to any tos 0x10 no keep state
queue ssh
---
# /etc/rc.d/pf restart
Disabling pf.
pf disabled
Enabling pf.
/etc/pf.conf:10: syntax error
pfctl: Syntax error in config file: pf rules not loaded
pf enabled
Unfortunately syntax error...
Should be "no state" according to pf.conf(5)
Thank's a lot !
That was it!
--
Andrew Biriukov
[EMAIL PROTECTED]
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: portupgrade error with 7.0-BETA1
On Sun, Oct 28, 2007 at 11:31:49PM +0100, Marc UBM Bocklet wrote: > > and then tried using portupgrade, which promptly fails with: > > > > Fatal error 'Cannot allocate red zone for initial thread' at line 382 > > in file /usr/src/lib/libthr/thread/thr_init.c (errno = 12) > > Illegal instruction: 4 (core dumped) > > > > (the red zone error ist repeated about 20 times). [snip] > This one bit me as well. It's an obsolete library (libthr) in the > binary, Recompile ruby18 and problem will go away. You'll find other > programs will do this too, but a lot of them disapear after doing a > portupgrade. After updated to a new major version of FreeBSD (6->7, not 6.2->6.3) is to make a list of all ports, remove them all with pkg_delete and install them from scratch. That is the only sure way to prevent programs linking to older libraries. And while your at it, it would be a good idea to clean out the old cruft from (/usr)/lib as well. Roland -- R.F.Smith http://www.xs4all.nl/~rsmith/ [plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated] pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: C321A725) pgpxlteOj41v5.pgp Description: PGP signature
Re: portupgrade error with 7.0-BETA1
Marc UBM Bocklet wrote: On Sun, 28 Oct 2007 18:45:59 +0100 Marc "UBM" Bocklet <[EMAIL PROTECTED]> wrote: Hiho! ;-) I just upgraded my machine to: FreeBSD blah.blah 7.0-BETA1 FreeBSD 7.0-BETA1 #6: Thu Oct 25 19:43:35 CEST 2007 and then tried using portupgrade, which promptly fails with: Fatal error 'Cannot allocate red zone for initial thread' at line 382 in file /usr/src/lib/libthr/thread/thr_init.c (errno = 12) Illegal instruction: 4 (core dumped) (the red zone error ist repeated about 20 times). I'm not sure if it has anything to do with the upgrade. I tried deinstalling / reinstalling portupgrade and I also tried portupgrade-devel, but they both keep failing with the above error. Googling didn't yield any results. I've also installed the compat6x port and included COMPAT_FREEBSD6 in my kernel, but that didn't help either. Has anybody encountered this error before? Thanks in advance! A tip from Diane Bruce ([EMAIL PROTECTED]) did the trick: This one bit me as well. It's an obsolete library (libthr) in the binary, Recompile ruby18 and problem will go away. You'll find other programs will do this too, but a lot of them disapear after doing a portupgrade. ...which is a necessary part of any upgrade to a new branch. Kris ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: portupgrade error with 7.0-BETA1
On Sun, 28 Oct 2007 18:45:59 +0100 Marc "UBM" Bocklet <[EMAIL PROTECTED]> wrote: > > Hiho! ;-) > > I just upgraded my machine to: > > FreeBSD blah.blah 7.0-BETA1 FreeBSD 7.0-BETA1 #6: Thu Oct 25 19:43:35 > CEST 2007 > > and then tried using portupgrade, which promptly fails with: > > Fatal error 'Cannot allocate red zone for initial thread' at line 382 > in file /usr/src/lib/libthr/thread/thr_init.c (errno = 12) > Illegal instruction: 4 (core dumped) > > (the red zone error ist repeated about 20 times). > > I'm not sure if it has anything to do with the upgrade. I tried > deinstalling / reinstalling portupgrade and I also tried > portupgrade-devel, but they both keep failing with the above error. > Googling didn't yield any results. > I've also installed the compat6x port and included COMPAT_FREEBSD6 in > my kernel, but that didn't help either. > > Has anybody encountered this error before? > > Thanks in advance! A tip from Diane Bruce ([EMAIL PROTECTED]) did the trick: This one bit me as well. It's an obsolete library (libthr) in the binary, Recompile ruby18 and problem will go away. You'll find other programs will do this too, but a lot of them disapear after doing a portupgrade. I recompiled ruby18, ruby-bdb and portupgrade and now everything works like a charm again! Bye Marc -- "And what rough beast, its hour come round at last, Slouches towards Bethlehem to be born?" W.B. Yeats, The Second Coming ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: pf broken in 7.0-BETA1 ?
On Sun, Oct 28, 2007 at 04:34:56PM -0300, Andrew Birukov wrote:
> Ermal Luçi wrote:
> >Try using
> >
> >pass out on $ext_if proto tcp from any to any tos 0x10 no keep state queue
> >ssh
> >
> >and it should work as you expect!
>
> pf.conf
> ---
> ext_if="xl0"
>
> altq on $ext_if priq bandwidth 520Kb queue { ssh, traf }
> queue ssh priority 1
> queue traf priority 15 priq(default)
>
> pass in all
> pass out all
>
> pass out on $ext_if proto tcp from any to any tos 0x10 no keep state
> queue ssh
> ---
>
> # /etc/rc.d/pf restart
> Disabling pf.
> pf disabled
> Enabling pf.
> /etc/pf.conf:10: syntax error
> pfctl: Syntax error in config file: pf rules not loaded
> pf enabled
>
> Unfortunately syntax error...
Should be "no state" according to pf.conf(5)
> --
> Andrew Biriukov
> [EMAIL PROTECTED]
Paul Schenkeveld
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: pf broken in 7.0-BETA1 ?
- Original Message
> From: Andrew Birukov <[EMAIL PROTECTED]>
> To: Ermal Luçi <[EMAIL PROTECTED]>
> Cc: freebsd-stable@freebsd.org; [EMAIL PROTECTED]
> Sent: Sunday, October 28, 2007 10:34:56 PM
> Subject: Re: pf broken in 7.0-BETA1 ?
>
> Ermal Luçi wrote:
> > Try using
> >
> > pass out on $ext_if proto tcp from any to any tos 0x10 no keep
> state
>
queue ssh
> >
> > and it should work as you expect!
>
> pf.conf
> ---
> ext_if="xl0"
>
> altq on $ext_if priq bandwidth 520Kb queue { ssh, traf }
> queue ssh priority 1
> queue traf priority 15 priq(default)
>
> pass in all
> pass out all
>
> pass out on $ext_if proto tcp from any to any tos 0x10 no keep state
> queue ssh
> ---
>
> # /etc/rc.d/pf restart
> Disabling pf.
> pf disabled
> Enabling pf.
> /etc/pf.conf:10: syntax error
> pfctl: Syntax error in config file: pf rules not loaded
> pf enabled
>
> Unfortunately syntax error...
>
>
> --
> Andrew Biriukov
> [EMAIL PROTECTED]
Is this related to your problem?
http://www.nabble.com/Suggestion-with-patch%2C-change-PF-TOS-matching-to-bitmask-tf4697797.html
--
Regards,
-Abdullah Ibn Hamad Al-Marri
Arab Portal
http://www.WeArab.Net/
__
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: pf broken in 7.0-BETA1 ?
Try using
pass out on $ext_if proto tcp from any to any tos 0x10 no keep state queue ssh
and it should work as you expect!
On 10/28/07, Andrew Birukov <[EMAIL PROTECTED]> wrote:
>
> pf.conf:
> ---
> ext_if="xl0"
>
> altq on $ext_if priq bandwidth 520Kb queue { ssh, traf }
> queue ssh priority 1
> queue traf priority 15 priq(default)
>
> pass in all
> pass out all
>
> pass out on $ext_if proto tcp from any to any tos 0x10 queue ssh
> -
>
> I connected to remote host by ssh.
> In tcpdump i see many packets witch tos 0x10.
>
> 12:54:46.732928 IP (tos 0x10, ttl 64, id 12486, offset 0, flags [DF],
> proto TCP (6), length 52) 10.15.25.2.56587 > 194.0.91.110.22: ., cksum
> 0x35d5 (correct), 1919:1919(0) ack 2832 win 8181 8630585 535444648>
> 12:54:46.746958 IP (tos 0x10, ttl 64, id 12487, offset 0, flags [DF],
> proto TCP (6), length 100) 10.15.25.2.56587 > 194.0.91.110.22: P
> 1919:1967(48) ack 2832 win 8195
> 12:54:46.900186 IP (tos 0x10, ttl 64, id 12488, offset 0, flags [DF],
> proto TCP (6), length 52) 10.15.25.2.56587 > 194.0.91.110.22: ., cksum
> 0x33ec (correct), 1967:1967(0) ack 2944 win 8181 8630746 535444816>
> 12:54:46.915079 IP (tos 0x10, ttl 64, id 12489, offset 0, flags [DF],
> proto TCP (6), length 100) 10.15.25.2.56587 > 194.0.91.110.22: P
> 1967:2015(48) ack 2944 win 8195
>
> tcpdump confirms that the outgoing ssh data packets have tos 0x10, but
> the majority of the packets are still going to the default "traf" queue.
>
> queue ssh on xl0
> [ pkts: 0 bytes: 0 dropped pkts: 0 bytes:
> 0 ]
> [ qlength: 0/ 50 ]
> [ measured: 0.0 packets/s, 0 b/s ]
> queue traf on xl0 priority 15 priq( default )
> [ pkts: 5059 bytes:1130390 dropped pkts: 69 bytes:
> 80689 ]
> [ qlength: 0/ 50 ]
> [ measured: 3.9 packets/s, 2.15Kb/s ]
>
>
> This problem is affected 7.0 only.
> pf rools witch tos in FreeBSD-6.2 (previous pf version) work properly.
>
> My configuration:
> # uname -a
> FreeBSD amb.kiev.ua 7.0-BETA1 FreeBSD 7.0-BETA1 #1: Sun Oct 28 10:08:13
> ADT 2007 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/AMB.7.0 i386
>
> dmesg output and kernel config file are attached to this letter.
>
> Last time I cvsupped RELENG_7 and reinstall world in this morning.
>
> --
> Andrew Biriukov
> [EMAIL PROTECTED]
>
>
> #
> # GENERIC -- Generic kernel configuration file for FreeBSD/i386
> #
> # For more information on this file, please read the handbook section on
> # Kernel Configuration Files:
> #
> #
> http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/kernelconfig-config.html
> #
> # The handbook is also available locally in /usr/share/doc/handbook
> # if you've installed the doc distribution, otherwise always see the
> # FreeBSD World Wide Web server (http://www.FreeBSD.org/) for the
> # latest information.
> #
> # An exhaustive list of options and more detailed explanations of the
> # device lines is also present in the ../../conf/NOTES and NOTES files.
> # If you are in doubt as to the purpose or necessity of a line, check first
> # in NOTES.
> #
> # $FreeBSD: src/sys/i386/conf/GENERIC,v 1.474.2.1 2007/10/11 06:20:26
> kensmith Exp $
>
> #cpuI486_CPU
> #cpuI586_CPU
> cpu I686_CPU
> ident AMB
>
> # To statically compile in device wiring instead of /boot/device.hints
> #hints "GENERIC.hints" # Default places to look for devices.
>
> makeoptions DEBUG=-g# Build kernel with gdb(1) debug
> symbols
>
> options SCHED_4BSD # 4BSD scheduler
> #options SCHED_ULE
> options PREEMPTION # Enable kernel thread preemption
> options INET# InterNETworking
> #optionsINET6 # IPv6 communications protocols
> #optionsSCTP# Stream Control Transmission Protocol
> options FFS # Berkeley Fast Filesystem
> options SOFTUPDATES # Enable FFS soft updates support
> options UFS_ACL # Support for access control lists
> options UFS_DIRHASH # Improve performance on big
> directories
> options UFS_GJOURNAL# Enable gjournal-based UFS journaling
> options MD_ROOT # MD is a potential root device
> #optionsNFSCLIENT # Network Filesystem Client
> #optionsNFSSERVER
Re: pf broken in 7.0-BETA1 ?
Ermal Luçi wrote:
Try using
pass out on $ext_if proto tcp from any to any tos 0x10 no keep state queue ssh
and it should work as you expect!
pf.conf
---
ext_if="xl0"
altq on $ext_if priq bandwidth 520Kb queue { ssh, traf }
queue ssh priority 1
queue traf priority 15 priq(default)
pass in all
pass out all
pass out on $ext_if proto tcp from any to any tos 0x10 no keep state
queue ssh
---
# /etc/rc.d/pf restart
Disabling pf.
pf disabled
Enabling pf.
/etc/pf.conf:10: syntax error
pfctl: Syntax error in config file: pf rules not loaded
pf enabled
Unfortunately syntax error...
--
Andrew Biriukov
[EMAIL PROTECTED]
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
pf broken in 7.0-BETA1 ?
pf.conf:
---
ext_if="xl0"
altq on $ext_if priq bandwidth 520Kb queue { ssh, traf }
queue ssh priority 1
queue traf priority 15 priq(default)
pass in all
pass out all
pass out on $ext_if proto tcp from any to any tos 0x10 queue ssh
-
I connected to remote host by ssh.
In tcpdump i see many packets witch tos 0x10.
12:54:46.732928 IP (tos 0x10, ttl 64, id 12486, offset 0, flags [DF],
proto TCP (6), length 52) 10.15.25.2.56587 > 194.0.91.110.22: ., cksum
0x35d5 (correct), 1919:1919(0) ack 2832 win 8181
12:54:46.746958 IP (tos 0x10, ttl 64, id 12487, offset 0, flags [DF],
proto TCP (6), length 100) 10.15.25.2.56587 > 194.0.91.110.22: P
1919:1967(48) ack 2832 win 8195
12:54:46.900186 IP (tos 0x10, ttl 64, id 12488, offset 0, flags [DF],
proto TCP (6), length 52) 10.15.25.2.56587 > 194.0.91.110.22: ., cksum
0x33ec (correct), 1967:1967(0) ack 2944 win 8181
12:54:46.915079 IP (tos 0x10, ttl 64, id 12489, offset 0, flags [DF],
proto TCP (6), length 100) 10.15.25.2.56587 > 194.0.91.110.22: P
1967:2015(48) ack 2944 win 8195
tcpdump confirms that the outgoing ssh data packets have tos 0x10, but
the majority of the packets are still going to the default "traf" queue.
queue ssh on xl0
[ pkts: 0 bytes: 0 dropped pkts: 0 bytes:
0 ]
[ qlength: 0/ 50 ]
[ measured: 0.0 packets/s, 0 b/s ]
queue traf on xl0 priority 15 priq( default )
[ pkts: 5059 bytes:1130390 dropped pkts: 69 bytes:
80689 ]
[ qlength: 0/ 50 ]
[ measured: 3.9 packets/s, 2.15Kb/s ]
This problem is affected 7.0 only.
pf rools witch tos in FreeBSD-6.2 (previous pf version) work properly.
My configuration:
# uname -a
FreeBSD amb.kiev.ua 7.0-BETA1 FreeBSD 7.0-BETA1 #1: Sun Oct 28 10:08:13
ADT 2007 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/AMB.7.0 i386
dmesg output and kernel config file are attached to this letter.
Last time I cvsupped RELENG_7 and reinstall world in this morning.
--
Andrew Biriukov
[EMAIL PROTECTED]
#
# GENERIC -- Generic kernel configuration file for FreeBSD/i386
#
# For more information on this file, please read the handbook section on
# Kernel Configuration Files:
#
#
http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/kernelconfig-config.html
#
# The handbook is also available locally in /usr/share/doc/handbook
# if you've installed the doc distribution, otherwise always see the
# FreeBSD World Wide Web server (http://www.FreeBSD.org/) for the
# latest information.
#
# An exhaustive list of options and more detailed explanations of the
# device lines is also present in the ../../conf/NOTES and NOTES files.
# If you are in doubt as to the purpose or necessity of a line, check first
# in NOTES.
#
# $FreeBSD: src/sys/i386/conf/GENERIC,v 1.474.2.1 2007/10/11 06:20:26 kensmith
Exp $
#cpuI486_CPU
#cpuI586_CPU
cpu I686_CPU
ident AMB
# To statically compile in device wiring instead of /boot/device.hints
#hints "GENERIC.hints" # Default places to look for devices.
makeoptions DEBUG=-g# Build kernel with gdb(1) debug symbols
options SCHED_4BSD # 4BSD scheduler
#options SCHED_ULE
options PREEMPTION # Enable kernel thread preemption
options INET# InterNETworking
#optionsINET6 # IPv6 communications protocols
#optionsSCTP# Stream Control Transmission Protocol
options FFS # Berkeley Fast Filesystem
options SOFTUPDATES # Enable FFS soft updates support
options UFS_ACL # Support for access control lists
options UFS_DIRHASH # Improve performance on big directories
options UFS_GJOURNAL# Enable gjournal-based UFS journaling
options MD_ROOT # MD is a potential root device
#optionsNFSCLIENT # Network Filesystem Client
#optionsNFSSERVER # Network Filesystem Server
#optionsNFS_ROOT# NFS usable as /, requires NFSCLIENT
#optionsMSDOSFS # MSDOS Filesystem
#optionsCD9660 # ISO 9660 Filesystem
options PROCFS # Process filesystem (requires PSEUDOFS)
options PSEUDOFS# Pseudo-filesystem framework
options GEOM_PART_GPT # GUID Partition Tables.
options GEOM_LABEL # Provides labelization
options COMPAT_43TTY# BSD 4.3 TTY compat [KEEP THIS!]
options COMPAT_FREEBSD4 # Compatible with FreeBSD4
options COMPAT_FREEBSD5 # Compatible with FreeBSD5
options COMPAT_FREEBSD6 # Compatibl
portupgrade error with 7.0-BETA1
Hiho! ;-) I just upgraded my machine to: FreeBSD blah.blah 7.0-BETA1 FreeBSD 7.0-BETA1 #6: Thu Oct 25 19:43:35 CEST 2007 and then tried using portupgrade, which promptly fails with: Fatal error 'Cannot allocate red zone for initial thread' at line 382 in file /usr/src/lib/libthr/thread/thr_init.c (errno = 12) Illegal instruction: 4 (core dumped) (the red zone error ist repeated about 20 times). I'm not sure if it has anything to do with the upgrade. I tried deinstalling / reinstalling portupgrade and I also tried portupgrade-devel, but they both keep failing with the above error. Googling didn't yield any results. I've also installed the compat6x port and included COMPAT_FREEBSD6 in my kernel, but that didn't help either. Has anybody encountered this error before? Thanks in advance! Bye Marc -- "And what rough beast, its hour come round at last, Slouches towards Bethlehem to be born?" W.B. Yeats, The Second Coming ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: pf broken in 7.0-BETA1 ?
- Original Message > From: Per olof Ljungmark <[EMAIL PROTECTED]> > To: Andrew Birukov <[EMAIL PROTECTED]> > Cc: [EMAIL PROTECTED] > Sent: Sunday, October 28, 2007 8:47:11 PM > Subject: Re: pf broken in 7.0-BETA1 ? > > Andrew Birukov wrote: > > > > This problem is affected 7.0 only. > > pf rools witch tos in FreeBSD-6.2 work properly. > > Just a guess, could this be the problem? > "Warning: When browsing the pf user's guide, please keep in mind that > different versions of FreeBSD contain different versions of pf." > > I believe pf in 7 is based on OpenBSD 4.1. > > --per I think this should be sent to [EMAIL PROTECTED] and stable, since RELENG_7 is branched. Also the man isn't updated to reflect the changes in 7.0 yet :( Regards, -Abdullah Ibn Hamad Al-Marri Arab Portal http://www.WeArab.Net/ __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
FreeBSD 7.0-BETA1/OpenLDAP/PAM: passwd: Sorry, `passwd' can only change passwords for local or NIS users.
Users can not change their passwords on a machine which performs authentication via OpenLDAP/pam_ldap/nss_ldap facilities. I read about a patch, bu t is there another way to make this possible as a standard facility in sources? Ragards, Oliver ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Debugging off in 7.0-BETA1 kernel?
Doug Poland wrote: > Hello, > > A couple of days ago I csup'd RELENG_7 and I noticed the GENERIC kernel > was missing the following options... > > options KDB > options DDB > options GDB > options INVARIANTS > options INVARIANT_SUPPORT > options WITNESS > options WITNESS_SKIPSPIN > > The GENERIC kernel from BETA1.5 ISO did, however, include these options. > > Question, is this a feature? What are the preferred settings for > testing in the BETA/RC stages of the release cycle? I think for BETA stage we will prefer to have these options (disclaimer: this is only my own $0.02), but for RC stages it will be preferred to use kernel without these stuff. Cheers, -- Xin LI <[EMAIL PROTECTED]> http://www.delphij.net/ FreeBSD - The Power to Serve! signature.asc Description: OpenPGP digital signature
Debugging off in 7.0-BETA1 kernel?
Hello, A couple of days ago I csup'd RELENG_7 and I noticed the GENERIC kernel was missing the following options... options KDB options DDB options GDB options INVARIANTS options INVARIANT_SUPPORT options WITNESS options WITNESS_SKIPSPIN The GENERIC kernel from BETA1.5 ISO did, however, include these options. Question, is this a feature? What are the preferred settings for testing in the BETA/RC stages of the release cycle? -- Regards, Doug ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 7.0 BETA1 and Thinkpad T61p : Wireless misadventure
On Fri, 26 Oct 2007 16:34:12 +0100, Luis Neves wrote > > "ath" card > [EMAIL PROTECTED]:22:0:0: class=0x02 card=0xcb2114b9 > chip=0x0013168c rev=0x01 hdr=0x00 vendor = 'Atheros > Communications Inc.' device = 'AR5212, AR5213 802.11a/b/g > Wireless Adapter' class = network subclass = ethernet > Your output is exactly the same as mine so the driver seemingly attaches and the part appears to be recognized. At which point do you see those messages? Can you build src/tools/tools/ath/athstats, run it and post the output here? -Yuri ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 7.0 BETA1 and Thinkpad T61p : Wireless misadventure
> There are no FreeBSD drivers for the included intel 4965AG card. > I've tried to use the ndiswrapper framework without success. The ndisgen > wizard > runs without issues, but kldloading the driver freezes and reboots the > machine. This occurs if the Windows driver contains function calls that have not been implemented in the ndiswrapper framework. Often, an older version of the Windows driver solves the issue. For Broadcom cards that use bcmwl5.sys, kernel crash is a frequent problem if the newer drivers are used, but the old drivers solve the issue. I don't know if the card you mention would even work with ndis, but it's a good first step that ndisgen wizard works. Trying an older version of the Windows driver *might* help, but only if this card is compatible with ndis framework in the first place. Good luck. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 7.0 BETA1 and Thinkpad T61p : Wireless misadventure
- Original Message > From: Luis Neves <[EMAIL PROTECTED]> > To: [EMAIL PROTECTED]; freebsd-stable@freebsd.org > Sent: Friday, October 26, 2007 5:24:40 PM > Subject: 7.0 BETA1 and Thinkpad T61p : Wireless misadventure > > > Hi all. > So far I've failed to have a working wireless connection with > this > combination. > > There are no FreeBSD drivers for the included intel 4965AG card. > I've tried to use the ndiswrapper framework without success. > The > ndisgen wizard > runs without issues, but kldloading the driver freezes and reboots > the > machine. > > I've also tried two cardbus devices. > > The Cisco Aironet - AIR CB21AG (ath driver): > > Oct 26 13:30:27 t61p kernel: cardbus0: Expecting link target, got 0x0 > Oct 26 13:30:27 t61p kernel: ath0: > mem > 0xbfeb-0xbfeb irq > 16 at device 0.0 on cardbus0 > Oct 26 13:30:27 t61p kernel: ath0: [ITHREAD] > Oct 26 13:30:27 t61p kernel: ath0: unable to attach hardware; > HAL > status 13 > Oct 26 13:30:27 t61p kernel: device_attach: ath0 attach returned 6 > > and the Conceptronic C54RC (ral driver): > > Oct 26 13:40:59 t61p kernel: cardbus0: Expecting link target, got 0x0 > Oct 26 13:40:59 t61p kernel: ral0: mem > 0xbfeb-0xbfeb1fff irq 16 at device 0.0 on cardbus0 > Oct 26 13:40:59 t61p kernel: ral0: MAC/BBP RT2560 (rev 0x00), RF RT2522 > Oct 26 13:40:59 t61p kernel: ral0: [ITHREAD] > Oct 26 13:41:40 t61p kernel: ral0: could not read from BBP > Oct 26 13:41:40 t61p kernel: ral0: could not write to BBP > Oct 26 13:41:40 t61p kernel: ral0: could not read from BBP > Oct 26 13:41:40 t61p kernel: ral0: could not write to BBP > Oct 26 13:41:40 t61p kernel: ral0: could not read from BBP > Oct 26 13:41:40 t61p last message repeated 99 times > Oct 26 13:41:40 t61p kernel: ral0: timeout waiting for BBP > > I'm running: > uname -a > FreeBSD t61p 7.0-BETA1 FreeBSD 7.0-BETA1 #0: Fri Oct 26 13:10:37 > WEST > 2007 > [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC i386 > > GENERIC kernel with ULE and without debugging. > > Is there anything I can do to diagnose these issues? > > Thanks! > > -- > Luis Neves -- Forwarded message -- From: Marcin Simonides <[EMAIL PROTECTED]> Date: Oct 18, 2007 7:32 PM Subject: Re: NDIS: intel 4965 panic To: [EMAIL PROTECTED] Marcin Simonides wrote: > I've tried using an XP ndis wrapper for my intel 4965 wifi adapter. > After loading the driver the device is recognized and then kernel panics > during driver attachement. [...] Previously I didn't mention that there are some functions missing from the FreeBSD's NDIS api. These are: NdisIMCopySendPerPacketInfo strncat KeQuerySystemTime KeBugCheckEx KeTickCount With the help of NDIS reference and Linux ndiswrapper I have been able to implement all but KeBugCheckEx (they are all rather simple but I can't be 100% sure they're correct and exported appropriately). Now I'm able to load the driver and don't get any of the "ntoskrnl dummy called..." messages which probably means that there are no missing functions the driver tries to call. Unfortunately I'm still left with the: ndis0: NDIS ERROR: 40001b7c (unknown error) error message and the device doesn't work. ifconfig ndis0 shows: ndis0: flags=8806 mtu 1500 ether 00:13:e8:64:aa:f7 media: IEEE 802.11 Wireless Ethernet autoselect status: no carrier ssid "" channel 1 authmode OPEN privacy OFF txpowmax 100 bmiss 7 protmode CTS The LED indicating whether WLAN is on doesn't light up. Calling ifconfig ndis0 up results with the following kernel messages: ndis0: NDIS ERROR: 40001b7c (unknown error) ndis0: NDIS NUMERRORS: 2 ndis0: argptr: 0x56524457 ndis0: argptr: 0xdd And that's all I have been able to achieve so far :) I'll try to read some more of NDIS specification, locate the source of the aforementioned error message and generally try to blindly find something. Maybe someone has some suggestions? Maybe I should also try to post my questions to some other list? The diff of my changes: http://marcin.studio4plus.com/ndis/ndis.diff All changes are confined to the /usr/src/sys/compat/ndis directory. The functions I have added are implemented in a quick and dirty way :) -- Marcin Simonides --- Check it, it may work for you with ndis. Regards, -Abdullah Ibn Hamad Al-Marri Arab Portal http://www.WeArab.Net/ __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 7.0 BETA1 and Thinkpad T61p : Wireless misadventure
On Fri, 26 Oct 2007 15:24:40 +0100, Luis Neves wrote > Hi all. > So far I've failed to have a working wireless connection with this > combination. > > There are no FreeBSD drivers for the included intel 4965AG card. > I've tried to use the ndiswrapper framework without success. The > ndisgen wizard runs without issues, but kldloading the driver > freezes and reboots the machine. I dont think there's any support for this card in FreeBSD just yet. > > I've also tried two cardbus devices. > > The Cisco Aironet - AIR CB21AG (ath driver): > > Oct 26 13:30:27 t61p kernel: cardbus0: Expecting link target, got 0x0 > > Oct 26 13:30:27 t61p kernel: ath0: mem 0xbfeb- > 0xbfeb irq 16 at device 0.0 on cardbus0 > Oct 26 13:30:27 t61p kernel: ath0: [ITHREAD] > Oct 26 13:30:27 t61p kernel: ath0: unable to attach hardware; HAL > status 13 > Oct 26 13:30:27 t61p kernel: device_attach: ath0 attach returned 6 > FWIW, I have a T61 (not the "p" version) with 7.0-PRERELEASE from Oct 15th and have an integrated IBM miniPCI card that uses the ath driver without any problems: ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413) ath0: mem 0xdf2f-0xdf2f irq 17 at device 0.0 on pci3 ath0: [ITHREAD] ath0: using obsoleted if_watchdog interface ath0: mac 10.3 phy 6.1 radio 10.2 You should have no issues using the CB21AG adapter under FreeBSD. I have several of these and have used them as far back as 6.0-RELEASE on multiple laptops without any issues. In fact, I just dug one up and inserted it into my T61 and it attached to ath1: ath1: mem 0x8800-0x8800 irq 16 at device 0.0 on cardbus0 ath1: [ITHREAD] ath1: using obsoleted if_watchdog interface ath1: mac 5.6 phy 4.1 radio 3.6 > and the Conceptronic C54RC (ral driver): > I have no experience with these. > I'm running: > uname -a > > FreeBSD t61p 7.0-BETA1 FreeBSD 7.0-BETA1 #0: Fri Oct 26 13:10:37 > WEST 2007 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC i386 > > GENERIC kernel with ULE and without debugging. > > Is there anything I can do to diagnose these issues? > What does dmesg show for "ath" when you boot? Or can you post "pciconf -l -v"? -Yuri ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 7.0 BETA1 and Thinkpad T61p : Wireless misadventure
Yuri Lukin wrote: On Fri, 26 Oct 2007 15:24:40 +0100, Luis Neves wrote FWIW, I have a T61 (not the "p" version) with 7.0-PRERELEASE from Oct 15th and have an integrated IBM miniPCI card that uses the ath driver without any problems: ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413) ath0: mem 0xdf2f-0xdf2f irq 17 at device 0.0 on pci3 ath0: [ITHREAD] ath0: using obsoleted if_watchdog interface ath0: mac 10.3 phy 6.1 radio 10.2 You should have no issues using the CB21AG adapter under FreeBSD. I have several of these and have used them as far back as 6.0-RELEASE on multiple laptops without any issues. In fact, I just dug one up and inserted it into my T61 and it attached to ath1: ath1: mem 0x8800-0x8800 irq 16 at device 0.0 on cardbus0 ath1: [ITHREAD] ath1: using obsoleted if_watchdog interface ath1: mac 5.6 phy 4.1 radio 3.6 Huumm... this is similar output to what i had last week, since then I've updated RAM to 4GB (a delicate process, I might have screwed up something) and updated FreeBSD a couple of times to the latest RELENG_7. I'm running: uname -a FreeBSD t61p 7.0-BETA1 FreeBSD 7.0-BETA1 #0: Fri Oct 26 13:10:37 WEST 2007 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC i386 GENERIC kernel with ULE and without debugging. Is there anything I can do to diagnose these issues? What does dmesg show for "ath" when you boot? Or can you post "pciconf -l -v"? cardbus: [EMAIL PROTECTED]:21:0:0: class=0x060700 card=0x20c617aa chip=0x04761180 rev=0xba hdr=0x02 vendor = 'Ricoh Company, Ltd.' device = 'unknown Ricoh R/RL/5C476(II)' class = bridge subclass = PCI-CardBus "ral" card: [EMAIL PROTECTED]:22:0:0: class=0x028000 card=0x3c001948 chip=0x02011814 rev=0x01 hdr=0x00 vendor = 'Ralink Technology, Corp' device = '0x03011814 Zonet ZEW1601 (Ralink Chipset) 802.11b/g WLAN Card' class = network "ath" card [EMAIL PROTECTED]:22:0:0: class=0x02 card=0xcb2114b9 chip=0x0013168c rev=0x01 hdr=0x00 vendor = 'Atheros Communications Inc.' device = 'AR5212, AR5213 802.11a/b/g Wireless Adapter' class = network subclass = ethernet Thanks for your help! -- Luis Neves ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
7.0 BETA1 and Thinkpad T61p : Wireless misadventure
Hi all. So far I've failed to have a working wireless connection with this combination. There are no FreeBSD drivers for the included intel 4965AG card. I've tried to use the ndiswrapper framework without success. The ndisgen wizard runs without issues, but kldloading the driver freezes and reboots the machine. I've also tried two cardbus devices. The Cisco Aironet - AIR CB21AG (ath driver): Oct 26 13:30:27 t61p kernel: cardbus0: Expecting link target, got 0x0 Oct 26 13:30:27 t61p kernel: ath0: mem 0xbfeb-0xbfeb irq 16 at device 0.0 on cardbus0 Oct 26 13:30:27 t61p kernel: ath0: [ITHREAD] Oct 26 13:30:27 t61p kernel: ath0: unable to attach hardware; HAL status 13 Oct 26 13:30:27 t61p kernel: device_attach: ath0 attach returned 6 and the Conceptronic C54RC (ral driver): Oct 26 13:40:59 t61p kernel: cardbus0: Expecting link target, got 0x0 Oct 26 13:40:59 t61p kernel: ral0: mem 0xbfeb-0xbfeb1fff irq 16 at device 0.0 on cardbus0 Oct 26 13:40:59 t61p kernel: ral0: MAC/BBP RT2560 (rev 0x00), RF RT2522 Oct 26 13:40:59 t61p kernel: ral0: [ITHREAD] Oct 26 13:41:40 t61p kernel: ral0: could not read from BBP Oct 26 13:41:40 t61p kernel: ral0: could not write to BBP Oct 26 13:41:40 t61p kernel: ral0: could not read from BBP Oct 26 13:41:40 t61p kernel: ral0: could not write to BBP Oct 26 13:41:40 t61p kernel: ral0: could not read from BBP Oct 26 13:41:40 t61p last message repeated 99 times Oct 26 13:41:40 t61p kernel: ral0: timeout waiting for BBP I'm running: uname -a FreeBSD t61p 7.0-BETA1 FreeBSD 7.0-BETA1 #0: Fri Oct 26 13:10:37 WEST 2007 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC i386 GENERIC kernel with ULE and without debugging. Is there anything I can do to diagnose these issues? Thanks! -- Luis Neves ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Fatal trap 12 on 7.0-BETA1 i386
On Thu, Oct 25, 2007 at 08:11:56PM +0200, Kris Kennaway wrote: > Doug Poland wrote: > >On Thu, Oct 25, 2007 at 01:17:38AM +0200, Kris Kennaway wrote: > >>Doug Poland wrote: > >>> > >>>I just had a kernel panic using BETA1. According to the Developer > >>>Handbook Kernel Debugging, I'm supplying the following information > >>>in hopes that it is useful. Please note: I'm not familiar with > >>>this process so you need more data, just ask: > >>> > >>>snip > >>> > > > >>Almost :) > >> > >>What does 'bt' show in kgdb? > >> > > > >Here's the whole thing with a backtrace. Thanks for your patience... > > > >snip > > > > > > I asked Sam about this and he says he has seen it reported before but > not with enough details to track it down further. Can you file a PR > and describe your system network configuration in more detail, > including kernel config, dmesg, rc.conf and other settings, and any > firewall rules that are applied? > Will do, thanks for pointing me in the right direction -- Regards, Doug ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Fatal trap 12 on 7.0-BETA1 i386
Doug Poland wrote:
On Thu, Oct 25, 2007 at 01:17:38AM +0200, Kris Kennaway wrote:
Doug Poland wrote:
Hello,
I just had a kernel panic using BETA1. According to the Developer
Handbook Kernel Debugging, I'm supplying the following information in
hopes that it is useful. Please note: I'm not familiar with this
process so you need more data, just ask:
snip
Almost :)
What does 'bt' show in kgdb?
kgdb kernel.debug /var/crash/vmcore.0
[GDB will not be able to debug user-mode threads: /usr/lib/libthread_db.so: Undefined
symbol "ps_pglobal_lookup"]
GNU gdb 6.1.1 [FreeBSD]
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "i386-marcel-freebsd".
Unread portion of the kernel message buffer:
Fatal trap 12: page fault while in kernel mode
cpuid = 1; apic id = 01
fault virtual address = 0x9006004
fault code = supervisor read, page not present
instruction pointer = 0x20:0xc079c961
stack pointer = 0x28:0xe74a7bcc
frame pointer = 0x28:0xe74a7be0
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 = 46 (ath0 taskq)
trap number = 12
panic: page fault
cpuid = 1
Uptime: 4h9m30s
Physical memory: 3435 MB
Dumping 214 MB: 199 183 167 151 135 119 103 87 71 55 39 23 7
#0 doadump () at pcpu.h:195
195 __asm __volatile("movl %%fs:0,%0" : "=r" (td));
(kgdb) list *0xc079c961
0xc079c961 is in mb_free_ext (/usr/src/sys/kern/uipc_mbuf.c:226).
221 * check if the header is embedded in the cluster
222 */
223 skipmbuf = (m->m_flags & M_NOFREE);
224
225 /* Free attached storage if this mbuf is the only reference to
it. */
226 if (*(m->m_ext.ref_cnt) == 1 ||
227 atomic_fetchadd_int(m->m_ext.ref_cnt, -1) == 1) {
228 switch (m->m_ext.ext_type) {
229 case EXT_PACKET:/* The packet zone is special.
*/
230 if (*(m->m_ext.ref_cnt) == 0)
(kgdb) backtrace
#0 doadump () at pcpu.h:195
#1 0xc074fed7 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:409
#2 0xc0750199 in panic (fmt=Variable "fmt" is not available.
) at /usr/src/sys/kern/kern_shutdown.c:563
#3 0xc0a1485c in trap_fatal (frame=0xe74a7b8c, eva=151019524) at
/usr/src/sys/i386/i386/trap.c:872
#4 0xc0a14ae0 in trap_pfault (frame=0xe74a7b8c, usermode=0, eva=151019524) at
/usr/src/sys/i386/i386/trap.c:785
#5 0xc0a15455 in trap (frame=0xe74a7b8c) at /usr/src/sys/i386/i386/trap.c:463
#6 0xc09fb46b in calltrap () at /usr/src/sys/i386/i386/exception.s:139
#7 0xc079c961 in mb_free_ext (m=0xc7151e00) at
/usr/src/sys/kern/uipc_mbuf.c:226
#8 0xc079cfc1 in m_freem (mb=0x0) at mbuf.h:510
#9 0xc051e39e in ath_rxbuf_init (sc=0xc6e95000, bf=0xc6e9cc94) at
/usr/src/sys/dev/ath/if_ath.c:3257
#10 0xc052595d in ath_rx_proc (arg=0xc6e95000, npending=1) at
/usr/src/sys/dev/ath/if_ath.c:3711
#11 0xc07809c5 in taskqueue_run (queue=0xc6dd8300) at
/usr/src/sys/kern/subr_taskqueue.c:255
#12 0xc0780bcb in taskqueue_thread_loop (arg=0xc6e96664) at
/usr/src/sys/kern/subr_taskqueue.c:374
#13 0xc07304b9 in fork_exit (callout=0xc0780b10 ,
arg=0xc6e96664, frame=0xe74a7d38) at /usr/src/sys/kern/kern_fork.c:796
#14 0xc09fb4e0 in fork_trampoline () at /usr/src/sys/i386/i386/exception.s:205
(kgdb)
Here's the whole thing with a backtrace. Thanks for your patience...
I asked Sam about this and he says he has seen it reported before but
not with enough details to track it down further. Can you file a PR and
describe your system network configuration in more detail, including
kernel config, dmesg, rc.conf and other settings, and any firewall rules
that are applied?
Kris
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 7.0-BETA1 Available, 6.3-BETA1 coming soon...
Wayne Chapeskie wrote: > On Mon, 2007-10-22 at 22:21 -0400, Ken Smith wrote: > > > The 7.0-BETA1 builds have completed and are on many of the FreeBSD > > mirror sites. If you want to update an existing machine using cvsup use > > I've been doing some install testing of the 7.0-BETA1 i386 ISO's, and > have found a small glitch or two. Where should bug reports for > the BETA or RC installs be sent? Suggestion: Use send-pr & add cc: "Release Engineers" <[EMAIL PROTECTED]> -- Julian Stacey. Munich Computer Consultant, BSD Unix C Linux. http://berklix.com Ihr Rauch=mein allergischer Kopfschmerz. Dump cigs 4 snuff. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
7.0-BETA1 AMD64 buildworld error
I have updated sources as of Oct 25 and I tried building world (7.0-BETA1 AMD64), but I keep receiving the same error (see below) and I'm not sure how to fix it. I tried removing my sources completely and getting a fresh copy as well as running make clean in /usr/src, but to no avail. Anyone have any ideas? echo libc.so.7: /usr/obj/usr/src/lib32/usr/lib32/libgcc.a >> .depend /usr/local/libexec/ccache/world-cc -O2 -fno-strict-aliasing -pipe -O2 -fno-strict-aliasing -pipe -s -mtune=nocona -I/usr/src/lib/libc/include -I/usr/src/lib/libc/../../include -I/usr/src/lib/libc/i386 -D__DBINTERFACE_PRIVATE -I/usr/src/lib/libc/../../contrib/gdtoa -DINET6 -I/usr/obj/lib32/usr/src/lib/libc -I/usr/src/lib/libc/resolv -DPOSIX_MISTAKE -I/usr/src/lib/libc/locale -DBROKEN_DES -DPORTMAP -DDES_BUILTIN -I/usr/src/lib/libc/rpc -DYP -DNS_CACHING -DSYMBOL_VERSIONING -Wsystem-headers -Wall -Wno-format-y2k -Wno-uninitialized -Wno-pointer-sign -c fork.S /usr/local/libexec/ccache/world-cc -fpic -DPIC -O2 -fno-strict-aliasing -pipe -O2 -fno-strict-aliasing -pipe -s -mtune=nocona -I/usr/src/lib/libc/include -I/usr/src/lib/libc/../../include -I/usr/src/lib/libc/i386 -D__DBINTERFACE_PRIVATE -I/usr/src/lib/libc/../../contrib/gdtoa -DINET6 -I/usr/obj/lib32/usr/src/lib/libc -I/usr/src/lib/libc/resolv -DPOSIX_MISTAKE -I/usr/src/lib/libc/locale -DBROKEN_DES -DPORTMAP -DDES_BUILTIN -I/usr/src/lib/libc/rpc -DYP -DNS_CACHING -DSYMBOL_VERSIONING -Wsystem-headers -Wall -Wno-format-y2k -Wno-uninitialized -Wno-pointer-sign -c fork.S -o fork.So /usr/local/libexec/ccache/world-cc -O2 -fno-strict-aliasing -pipe -O2 -fno-strict-aliasing -pipe -s -mtune=nocona -I/usr/src/lib/libc/include -I/usr/src/lib/libc/../../include -I/usr/src/lib/libc/i386 -D__DBINTERFACE_PRIVATE -I/usr/src/lib/libc/../../contrib/gdtoa -DINET6 -I/usr/obj/lib32/usr/src/lib/libc -I/usr/src/lib/libc/resolv -DPOSIX_MISTAKE -I/usr/src/lib/libc/locale -DBROKEN_DES -DPORTMAP -DDES_BUILTIN -I/usr/src/lib/libc/rpc -DYP -DNS_CACHING -DSYMBOL_VERSIONING -Wsystem-headers -Wall -Wno-format-y2k -Wno-uninitialized -Wno-pointer-sign -c read.S fork.S: Assembler messages: fork.S:2: Error: invalid character '_' in mnemonic *** Error code 1 fork.S: Assembler messages: fork.S:2: Error: invalid character '_' in mnemonic *** Error code 1 read.S: Assembler messages: read.S:2: Error: invalid character '_' in mnemonic *** Error code 1 3 errors *** Error code 2 2 errors *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error Thanks. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 7.0-BETA1 Available, 6.3-BETA1 coming soon...
On Mon, 2007-10-22 at 22:21 -0400, Ken Smith wrote: > The 7.0-BETA1 builds have completed and are on many of the FreeBSD > mirror sites. If you want to update an existing machine using cvsup use I've been doing some install testing of the 7.0-BETA1 i386 ISO's, and have found a small glitch or two. Where should bug reports for the BETA or RC installs be sent? Thanks, -- Wayne Chapeskie ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Fatal trap 12 on 7.0-BETA1 i386
On Thu, Oct 25, 2007 at 01:17:38AM +0200, Kris Kennaway wrote:
> Doug Poland wrote:
> >Hello,
> >
> >I just had a kernel panic using BETA1. According to the Developer
> >Handbook Kernel Debugging, I'm supplying the following information in
> >hopes that it is useful. Please note: I'm not familiar with this
> >process so you need more data, just ask:
> >
> >
> > snip
> >
>
> Almost :)
>
> What does 'bt' show in kgdb?
>
kgdb kernel.debug /var/crash/vmcore.0
[GDB will not be able to debug user-mode threads: /usr/lib/libthread_db.so:
Undefined symbol "ps_pglobal_lookup"]
GNU gdb 6.1.1 [FreeBSD]
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "i386-marcel-freebsd".
Unread portion of the kernel message buffer:
Fatal trap 12: page fault while in kernel mode
cpuid = 1; apic id = 01
fault virtual address = 0x9006004
fault code = supervisor read, page not present
instruction pointer = 0x20:0xc079c961
stack pointer = 0x28:0xe74a7bcc
frame pointer = 0x28:0xe74a7be0
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 = 46 (ath0 taskq)
trap number = 12
panic: page fault
cpuid = 1
Uptime: 4h9m30s
Physical memory: 3435 MB
Dumping 214 MB: 199 183 167 151 135 119 103 87 71 55 39 23 7
#0 doadump () at pcpu.h:195
195 __asm __volatile("movl %%fs:0,%0" : "=r" (td));
(kgdb) list *0xc079c961
0xc079c961 is in mb_free_ext (/usr/src/sys/kern/uipc_mbuf.c:226).
221 * check if the header is embedded in the cluster
222 */
223 skipmbuf = (m->m_flags & M_NOFREE);
224
225 /* Free attached storage if this mbuf is the only reference to
it. */
226 if (*(m->m_ext.ref_cnt) == 1 ||
227 atomic_fetchadd_int(m->m_ext.ref_cnt, -1) == 1) {
228 switch (m->m_ext.ext_type) {
229 case EXT_PACKET:/* The packet zone is special.
*/
230 if (*(m->m_ext.ref_cnt) == 0)
(kgdb) backtrace
#0 doadump () at pcpu.h:195
#1 0xc074fed7 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:409
#2 0xc0750199 in panic (fmt=Variable "fmt" is not available.
) at /usr/src/sys/kern/kern_shutdown.c:563
#3 0xc0a1485c in trap_fatal (frame=0xe74a7b8c, eva=151019524) at
/usr/src/sys/i386/i386/trap.c:872
#4 0xc0a14ae0 in trap_pfault (frame=0xe74a7b8c, usermode=0, eva=151019524) at
/usr/src/sys/i386/i386/trap.c:785
#5 0xc0a15455 in trap (frame=0xe74a7b8c) at /usr/src/sys/i386/i386/trap.c:463
#6 0xc09fb46b in calltrap () at /usr/src/sys/i386/i386/exception.s:139
#7 0xc079c961 in mb_free_ext (m=0xc7151e00) at
/usr/src/sys/kern/uipc_mbuf.c:226
#8 0xc079cfc1 in m_freem (mb=0x0) at mbuf.h:510
#9 0xc051e39e in ath_rxbuf_init (sc=0xc6e95000, bf=0xc6e9cc94) at
/usr/src/sys/dev/ath/if_ath.c:3257
#10 0xc052595d in ath_rx_proc (arg=0xc6e95000, npending=1) at
/usr/src/sys/dev/ath/if_ath.c:3711
#11 0xc07809c5 in taskqueue_run (queue=0xc6dd8300) at
/usr/src/sys/kern/subr_taskqueue.c:255
#12 0xc0780bcb in taskqueue_thread_loop (arg=0xc6e96664) at
/usr/src/sys/kern/subr_taskqueue.c:374
#13 0xc07304b9 in fork_exit (callout=0xc0780b10 ,
arg=0xc6e96664, frame=0xe74a7d38) at /usr/src/sys/kern/kern_fork.c:796
#14 0xc09fb4e0 in fork_trampoline () at /usr/src/sys/i386/i386/exception.s:205
(kgdb)
Here's the whole thing with a backtrace. Thanks for your patience...
--
Regards,
Doug
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Fatal trap 12 on 7.0-BETA1 i386
Doug Poland wrote:
Hello,
I just had a kernel panic using BETA1. According to the Developer
Handbook Kernel Debugging, I'm supplying the following information in
hopes that it is useful. Please note: I'm not familiar with this
process so you need more data, just ask:
kgdb kernel.debug /var/crash/vmcore.0
[GDB will not be able to debug user-mode threads:
/usr/lib/libthread_db.so: Undefined symbol "ps_pglobal_lookup"]
GNU gdb 6.1.1 [FreeBSD]
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you
are
welcome to change it and/or distribute copies of it under certain
conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "i386-marcel-freebsd".
Unread portion of the kernel message buffer:
Fatal trap 12: page fault while in kernel mode
cpuid = 1; apic id = 01
fault virtual address = 0x9006004
fault code = supervisor read, page not present
instruction pointer = 0x20:0xc079c961
stack pointer = 0x28:0xe74a7bcc
frame pointer = 0x28:0xe74a7be0
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 = 46 (ath0 taskq)
trap number = 12
panic: page fault
cpuid = 1
Uptime: 4h9m30s
Physical memory: 3435 MB
Dumping 214 MB: ...
#0 doadump () at pcpu.h:195
195 __asm __volatile("movl %%fs:0,%0" : "=r" (td));
(kgdb) list *0xc079c961
0xc079c961 is in mb_free_ext (/usr/src/sys/kern/uipc_mbuf.c:226).
221 * check if the header is embedded in the cluster
222 */
223 skipmbuf = (m->m_flags & M_NOFREE);
224
225 /* Free attached storage if this mbuf is the only
reference to it. */
226 if (*(m->m_ext.ref_cnt) == 1 ||
227 atomic_fetchadd_int(m->m_ext.ref_cnt, -1) == 1) {
228 switch (m->m_ext.ext_type) {
229 case EXT_PACKET:/* The packet zone is
special. */
230 if (*(m->m_ext.ref_cnt) == 0)
Almost :)
What does 'bt' show in kgdb?
Kris
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Fatal trap 12 on 7.0-BETA1 i386
Hello,
I just had a kernel panic using BETA1. According to the Developer
Handbook Kernel Debugging, I'm supplying the following information in
hopes that it is useful. Please note: I'm not familiar with this
process so you need more data, just ask:
kgdb kernel.debug /var/crash/vmcore.0
[GDB will not be able to debug user-mode threads:
/usr/lib/libthread_db.so: Undefined symbol "ps_pglobal_lookup"]
GNU gdb 6.1.1 [FreeBSD]
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain
conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "i386-marcel-freebsd".
Unread portion of the kernel message buffer:
Fatal trap 12: page fault while in kernel mode
cpuid = 1; apic id = 01
fault virtual address = 0x9006004
fault code = supervisor read, page not present
instruction pointer = 0x20:0xc079c961
stack pointer = 0x28:0xe74a7bcc
frame pointer = 0x28:0xe74a7be0
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 = 46 (ath0 taskq)
trap number = 12
panic: page fault
cpuid = 1
Uptime: 4h9m30s
Physical memory: 3435 MB
Dumping 214 MB: ...
#0 doadump () at pcpu.h:195
195 __asm __volatile("movl %%fs:0,%0" : "=r" (td));
(kgdb) list *0xc079c961
0xc079c961 is in mb_free_ext (/usr/src/sys/kern/uipc_mbuf.c:226).
221 * check if the header is embedded in the cluster
222 */
223 skipmbuf = (m->m_flags & M_NOFREE);
224
225 /* Free attached storage if this mbuf is the only
reference to it. */
226 if (*(m->m_ext.ref_cnt) == 1 ||
227 atomic_fetchadd_int(m->m_ext.ref_cnt, -1) == 1) {
228 switch (m->m_ext.ext_type) {
229 case EXT_PACKET:/* The packet zone is
special. */
230 if (*(m->m_ext.ref_cnt) == 0)
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 7.0-BETA1 Available, 6.3-BETA1 coming soon...
On Mon, 2007-10-22 at 22:21 -0400, Ken Smith wrote: > We have entered the final phases of the FreeBSD-7.0 Release cycle which > also means the beginning of the FreeBSD-6.3 Release cycle. Because the > people who support the ports for FreeBSD also need to go through a > freeze cycle as part of releases we had decided to combine the two > releases to try and minimize the impact on the ports maintainers. [...snip...] I upgraded with CVSup. It works fine. I'll wait for -RELEASE. [EMAIL PROTECTED]:~> uname -v FreeBSD 7.0-BETA1 #3: Wed Oct 24 00:58:37 KST 2007 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC [EMAIL PROTECTED]:~> Thanks! -- Byung-Hee HWANG * InZealBomb "You know who I am?" -- Vito Corleone, "Chapter 1", page 52 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 7.0-BETA1
rihad <[EMAIL PROTECTED]> wrote: > My question was more a theoretical one: it's called BETA for some > reason, otherwise it'd still be in HEAD. To me BETA means that no major > architectural changes are expected in it any more, no? That's correct. In theory, if BETA had no bugs (and no new ones are discovered during the beta/rc phase), the exact same code would probably become the RELEASE. Of course, in practice there are always bugs. > > > But: TEST FIRST! > > > > I concur with Per. Me too. > > I've been running 7-CURRENT on a couple of "production" > > machines for some months, without any serious problems -- but these are not > > mission-critical machines. I've updated a production machine from 6-stable to 7-stable last week, without any issues. It was even a remote update without console access, which presented a certain risk. But all went well (and I had backups, of course). > Our machine-to-be is quite mission-critical... But if I start with the > latest 6.x release, it would be more difficult to migrate to 7.0 when it > comes out than if I start with 7.0-BETA?. Not necessarily. The update from 6-stable to 7-stable was just as easy as an update within the 6-stable branch. It was just the usual buildworld, kernel, mergemaster dance. Nothing special at all, except that mergemaster took a little longer because there were more differences, and I had to do a few edits to the kernel config (enable the new scheduler). But you have to do that anyway, whether you go for 7.x now or later. > Again it's named BETA for a reason, so it could be less intrusive than > STABLE?.. BETA means it is on its way to the RELEASE (with some RCs in between, i.e. release candidates). It means that no architectural changes are made (those usually only happen in -current anyway), and no major new features, only fixes. Best regards Oliver -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing b. M. Handelsregister: Registergericht Muenchen, HRA 74606, Geschäftsfuehrung: secnetix Verwaltungsgesellsch. mbH, Handelsregister: Registergericht Mün- chen, HRB 125758, Geschäftsführer: Maik Bachmann, Olaf Erb, Ralf Gebhart FreeBSD-Dienstleistungen, -Produkte und mehr: http://www.secnetix.de/bsd I suggested holding a "Python Object Oriented Programming Seminar", but the acronym was unpopular. -- Joseph Strout ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 7.0-BETA1
On Wed, Oct 24, 2007 at 02:00:42PM +0500, rihad wrote: > >>rihad wrote: > >>>How risky is it to start using 7.0-BETA1 in production, with the > >>>intention of upgrading to release as soon as possible? Thanks. > My question was more a theoretical one: it's called BETA for some > reason, otherwise it'd still be in HEAD. To me BETA means that no major > architectural changes are expected in it any more, no? Yes, but it doesn't mean that there can't be undiscovered bugs that could cause problems. > Our machine-to-be is quite mission-critical... But if I start with the > latest 6.x release, it would be more difficult to migrate to 7.0 when it > comes out than if I start with 7.0-BETA?. I've known people running > 4-STABLE or 5-STABLE branches on mission-critical machines, without even > bothering to upgrade, but I think they're stress-testing their luck ;-) > So I don't want to join their camp, that's why I asked for advice ;-) > Again it's named BETA for a reason, so it could be less intrusive than > STABLE?.. > I will definitely start with beta if it reaches BETA2 in a week or two - > the time I got ;-) Thanks for advice. Well, if it is a "machine-to-be", then I suspect that you should be safe in starting with 7.0-BETA. First, there don't appear to be any serious problems with it, and second, if it is a new build "machine-to-be", then you will have the opportunity to do the testing required to ensure that there are no problems (in your situation) prior to rollout. -- 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: 7.0-BETA1
Greg Byshenk wrote: On Tue, Oct 23, 2007 at 11:08:27PM +0200, Per olof Ljungmark wrote: rihad wrote: How risky is it to start using 7.0-BETA1 in production, with the intention of upgrading to release as soon as possible? Thanks. We've used 7-CURRENT since January on a couple of production boxes and had very few disasters, well, none, but a couple of issues. "Risky" is a relative term really, but if you ask me I'd say the "risk" is rather low. My question was more a theoretical one: it's called BETA for some reason, otherwise it'd still be in HEAD. To me BETA means that no major architectural changes are expected in it any more, no? But: TEST FIRST! I concur with Per. I've been running 7-CURRENT on a couple of "production" machines for some months, without any serious problems -- but these are not mission-critical machines. Our machine-to-be is quite mission-critical... But if I start with the latest 6.x release, it would be more difficult to migrate to 7.0 when it comes out than if I start with 7.0-BETA?. I've known people running 4-STABLE or 5-STABLE branches on mission-critical machines, without even bothering to upgrade, but I think they're stress-testing their luck ;-) So I don't want to join their camp, that's why I asked for advice ;-) Again it's named BETA for a reason, so it could be less intrusive than STABLE?.. I will definitely start with beta if it reaches BETA2 in a week or two - the time I got ;-) Thanks for advice. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 7.0-BETA1
On Tue, Oct 23, 2007 at 11:08:27PM +0200, Per olof Ljungmark wrote: > rihad wrote: > >How risky is it to start using 7.0-BETA1 in production, with the > >intention of upgrading to release as soon as possible? Thanks. > We've used 7-CURRENT since January on a couple of production boxes and > had very few disasters, well, none, but a couple of issues. > "Risky" is a relative term really, but if you ask me I'd say the "risk" > is rather low. > But: TEST FIRST! I concur with Per. I've been running 7-CURRENT on a couple of "production" machines for some months, without any serious problems -- but these are not mission-critical machines. Risk is a relative thing, and it is relative to both the risk of failure and the cost of that failure should it occur. I have 7- running on one fileserver that is used only by our IT group (for online copies of distfiles and other installable software), meaning that if something should go horribly wrong, it would be an annoyance, but not a disaster. The same could _not_ be said about our central user fileservers, and so they do not run 7-. I could also note that I've been running 7-CURRENT on my own workstation (including X, but only fvwm2 and nothing too fancy) for about 6 months, and have experienced no serious problems (though I have swapped out SCHED_4BSD for SCHED_ULE due to poor interactivity with 4BSD). And I also emphasise: TEST FIRST! My situation is not the same as yours, and something that works fine in my environment may break horribly in yours. -- 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: 7.0-BETA1
rihad wrote: How risky is it to start using 7.0-BETA1 in production, with the intention of upgrading to release as soon as possible? Thanks. We've used 7-CURRENT since January on a couple of production boxes and had very few disasters, well, none, but a couple of issues. "Risky" is a relative term really, but if you ask me I'd say the "risk" is rather low. But: TEST FIRST! --per ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 7.0-BETA1
On Tue, 23 Oct 2007 19:57:52 +0200, rihad <[EMAIL PROTECTED]> wrote: How risky is it to start using 7.0-BETA1 in production, with the intention of upgrading to release as soon as possible? Thanks. BTW, where can I find 7-STABLE release notes? It's not here: http://www.freebsd.org/relnotes.html Here are snapshots of the release notes. http://people.freebsd.org/~bmah/relnotes/ -- Ronald Klop Amsterdam, The Netherlands ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
7.0-BETA1
How risky is it to start using 7.0-BETA1 in production, with the intention of upgrading to release as soon as possible? Thanks. BTW, where can I find 7-STABLE release notes? It's not here: http://www.freebsd.org/relnotes.html ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 7.0-BETA1 Available, 6.3-BETA1 coming soon...
- Original Message > From: Ken Smith <[EMAIL PROTECTED]> > To: freebsd-stable@freebsd.org; [EMAIL PROTECTED] > Sent: Tuesday, October 23, 2007 5:21:00 AM > Subject: 7.0-BETA1 Available, 6.3-BETA1 coming soon... > > > We have entered the final phases of the FreeBSD-7.0 Release cycle which > also means the beginning of the FreeBSD-6.3 Release cycle. Because the > people who support the ports for FreeBSD also need to go through a > freeze cycle as part of releases we had decided to combine the two > releases to try and minimize the impact on the ports maintainers. > > The current plan is to interleave the BETAs/RCs of the 7.0 and 6.3 > releases, trying to follow this for the dates when the builds will get > started (with them becoming available on the FTP mirrors a day or two > after the builds start): > > 7.0 6.3 > BETA1 10/17 10/24 > BETA2 10/31 11/7 > RC1 11/14 11/21 > RC2 11/28 12/5 > REL 12/12 12/19 > > Tomorrow (10/23) the RELENG_6 branch will be marked "6.3-PRERELEASE" to > note that we have entered the 6.3 release cycle. > > The schedule dates are, as usual, tentative. At this point RELENG_6 is > pretty mature so that schedule should be fairly accurate. Being a new > branch it is at least somewhat likely the dates for 7.0 will wind up > slipping. > > The 7.0-BETA1 builds have completed and are on many of the FreeBSD > mirror sites. If you want to update an existing machine using > cvsup > use > RELENG_7 as the branch tag. Instructions on using FreeBSD Update to > perform a binary upgrade from FreeBSD 6.x to 7.0-BETA1 will be provided > via the freebsd-stable list when available. > > Ken Smith > - From there to here, from here to | > [EMAIL PROTECTED] > there, funny things are everywhere. | > - Theodore Geisel | Thank you Ken! Could you please have someone to put these interesting news in the main page of FreeBSD? I wish FreeBSD main page is more attractive for new users, with links to PC-BSD, and DesktopBSD ..etc ;) --- Regards, -Abdullah Ibn Hamad Al-Marri Arab Portal http://www.WeArab.Net/ __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
