Re: Missing Man-Pages in RELENG_4
On Fri, Jan 07, 2005 at 01:57:20PM +0900, Hideyuki KURASHINA wrote: Darren, could you please commit following patch? Guido, also please merge those changes? As Darren seems to be afk untill the 10th, I took the liberty to commit the changes. -Guido ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: VIA C3 CPU not recognized
On Fri, 7 Jan 2005 12:40:57 +1100, Peter Jeremy [EMAIL PROTECTED] wrote: On Fri, 2005-Jan-07 00:20:12 +0100, Lukas Ertl wrote: Nevermind. It seems I now explicitely need cpu I686_CPU in my kernel. You should have always needed that. Interestingly, I didn't have it in the old kernel, and it worked. cheers, le ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
5.3 and re driver problem?
Hello, on a box with 3 re interfaces i get a lot of watchdog timeouts and stopping/clow connections. only found 1 or 2 postings with the same problem, but not much replys. the box worked great with 4.x. any suggestions would be very appreziated. many thanks, karl ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Instant reboots with CPUTYPE=pentium-m
Bartosz Fabianowski wrote: I use the athlon-xp switch on 3 boxes with no problems all of them running 5.3 What CFLAGS are you using? I have CFLAGS=-O -pipe in my make.conf. Maybe you have optimization turned off and that's making a difference? I reported the problem with the athlon-xp. My /etc/make.conf looks like the following (when I wish to kill the loader and experience instant reboots, that is ;-): CPUTYPE?= athlon-xp CFLAGS= -O -pipe COPTFLAGS= -O -pipe Note that I only see the problem when building the loader as part of a buildworld. Compiling just the boot stuff in /usr/src/sys/boot/ (i.e., without a bootstrapped gcc) results in a loader that works fine. Thus, I think defining CPUTYPE results in a gcc that produces a bad loader. Jon ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Instant reboots with CPUTYPE=pentium-m
- Original Message - From: Jon Noack [EMAIL PROTECTED] To: Bartosz Fabianowski [EMAIL PROTECTED] Cc: Chris [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] Sent: Thursday, January 06, 2005 7:35 PM Subject: Re: Instant reboots with CPUTYPE=pentium-m Bartosz Fabianowski wrote: I use the athlon-xp switch on 3 boxes with no problems all of them running 5.3 What CFLAGS are you using? I have CFLAGS=-O -pipe in my make.conf. Maybe you have optimization turned off and that's making a difference? I reported the problem with the athlon-xp. My /etc/make.conf looks like the following (when I wish to kill the loader and experience instant reboots, that is ;-): CPUTYPE?= athlon-xp CFLAGS= -O -pipe COPTFLAGS= -O -pipe Note that I only see the problem when building the loader as part of a buildworld. Compiling just the boot stuff in /usr/src/sys/boot/ (i.e., without a bootstrapped gcc) results in a loader that works fine. Thus, I think defining CPUTYPE results in a gcc that produces a bad loader. Mentioning athlon-xp sparked my interest... One of my systems is unstable under load when compiled with CPUTYPE?= athlon-xp, but not with i686. This typically manifests itself as segmentation faults or ICE errors at random places during compile jobs. The bootloader seems always fine however. regards, Derkjan ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 5.3 and re driver problem?
Karl M. Joch wrote: Hello, on a box with 3 re interfaces i get a lot of watchdog timeouts and stopping/clow connections. only found 1 or 2 postings with the same problem, but not much replys. the box worked great with 4.x. any suggestions would be very appreziated. I changed re nic to Intel gigE (em) and had no network problems since. Disabling ACPI might help. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Promise FastTrak Tx4200 FreeBSD 5.3
Hey. I'm having some trouble getting my promise fasttrak tx4200 (PDC20619) to work on FreeBSD 5.3. It wont show up on dmesg or when i use atacontrol list. when i use pciconf -lv it give me this. [EMAIL PROTECTED]:8:0: class=0x010400 card=0x3519105a chip=0x3519105a rev=0x02 hdr=0x00 vendor = 'Promise Technology Inc' class = mass storage subclass = RAID I have asked around and tried to get info from freebsd.org and google.com, but i cant seem to find any good info. the people i have talked to said to add device ataraid to the kernel so i did but it didn't help. So any tips and hints would be grateful. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
AW: 5.3 and re driver problem?
forgot to mention, this 3 cards are onboard because this i a mini-pc. so no chance to replace them :-(. thx. -Ursprüngliche Nachricht- Von: Pertti Kosunen [mailto:[EMAIL PROTECTED] Gesendet: Freitag, 07. Jänner 2005 17:21 An: [EMAIL PROTECTED] Cc: Karl M. Joch Betreff: Re: 5.3 and re driver problem? Karl M. Joch wrote: Hello, on a box with 3 re interfaces i get a lot of watchdog timeouts and stopping/clow connections. only found 1 or 2 postings with the same problem, but not much replys. the box worked great with 4.x. any suggestions would be very appreziated. I changed re nic to Intel gigE (em) and had no network problems since. Disabling ACPI might help. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: Promise FastTrak Tx4200 FreeBSD 5.3
Hello Fredrik, I think you are out of luck at the moment. The Linux driver is a binary/source hybrid which isn't usually a good sign. Good luck, Dominic -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of fredrik engberg Sent: 07 January 2005 21:34 To: freebsd-stable@freebsd.org Subject: Promise FastTrak Tx4200 FreeBSD 5.3 Hey. I'm having some trouble getting my promise fasttrak tx4200 (PDC20619) to work on FreeBSD 5.3. It wont show up on dmesg or when i use atacontrol list. when i use pciconf -lv it give me this. [EMAIL PROTECTED]:8:0: class=0x010400 card=0x3519105a chip=0x3519105a rev=0x02 hdr=0x00 vendor = 'Promise Technology Inc' class = mass storage subclass = RAID I have asked around and tried to get info from freebsd.org and google.com, but i cant seem to find any good info. the people i have talked to said to add device ataraid to the kernel so i did but it didn't help. So any tips and hints would be grateful. ___ 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: Instant reboots with CPUTYPE=pentium-m
Note that I only see the problem when building the loader as part of a buildworld. Compiling just the boot stuff in /usr/src/sys/boot/ (i.e., without a bootstrapped gcc) results in a loader that works fine. Curious. Either what you are seeing is a different problem then or it somehow shows in a different way than on my system. I would be very interested in investigating this further. To find the root of the cause, I guess it would be best to compare the .s files generated for the loader when a) compiling it as part of the world and b) compiling it on its own. In both cases, CPUTYPE=athlon-xp should be set, of course. Also, you should be using the exact same GCC to eliminate the possibility that different GCC binaries behave in different ways. I am not sure how much space this would take, but if you have the space, it would be great if you could do a full buildworld with -save-temps and then a separate build of the loader, with -save-temps again. For me, one of the offending files is: /usr/obj/usr/src/sys/boot/i386/loader/bcache.s You could try diffing that file and if it shows no differences, all the other .s files in that directory. Some file must change when the loader breaks / unbreaks after all. If you can send me the diffs, I will be glad to look into it. - Bartosz ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Promise FastTrak Tx4200 FreeBSD 5.3
fredrik engberg wrote: Hey. I'm having some trouble getting my promise fasttrak tx4200 (PDC20619) to work on FreeBSD 5.3. It wont show up on dmesg or when i use atacontrol list. when i use pciconf -lv it give me this. [EMAIL PROTECTED]:8:0: class=0x010400 card=0x3519105a chip=0x3519105a rev=0x02 hdr=0x00 vendor = 'Promise Technology Inc' class = mass storage subclass = RAID Interesting - PDC20619 is listed in ata(4) manual page for 5.3 Release, so one would expect it to show up. Not sure if this is very useful, but here is what I see for a TX2000: $ pciconv -lv [EMAIL PROTECTED]:20:0: class=0x010485 card=0x4d68105a chip=0x6269105a rev=0x02 hdr=0x00 vendor = 'Promise Technology Inc' device = 'PDC20271 FastTrak TX2000 EIDE controller' class= mass storage subclass = RAID $ dmesg atapci1: Promise PDC20271 UDMA133 controller port 0xec00-0xec0f,0xe800-0xe803,0xe400-0xe407,0xe000-0xe003,0xdc00-0xdc07 mem 0xd900-0xd900 irq 11 at device 20.0 on pci0 ata2: channel #0 on atapci1 ata3: channel #1 on atapci1 regards Mark ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: AW: 5.3 and re driver problem?
On Fri, 7 Jan 2005, Karl M. Joch wrote: forgot to mention, this 3 cards are onboard because this i a mini-pc. so no chance to replace them :-(. I had to turn off checksum offloading (add -rxcsum -txcsum to ifconfig_re0 in /etc/rc.conf) in order to make my on-board interface work. $.02, /Mikko thx. -Ursprüngliche Nachricht- Von: Pertti Kosunen [mailto:[EMAIL PROTECTED] Gesendet: Freitag, 07. Jänner 2005 17:21 An: [EMAIL PROTECTED] Cc: Karl M. Joch Betreff: Re: 5.3 and re driver problem? Karl M. Joch wrote: Hello, on a box with 3 re interfaces i get a lot of watchdog timeouts and stopping/clow connections. only found 1 or 2 postings with the same problem, but not much replys. the box worked great with 4.x. any suggestions would be very appreziated. I changed re nic to Intel gigE (em) and had no network problems since. Disabling ACPI might help. ___ 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]
