Re: ghosthunting: machine freeze 6.2R
Roger Miranda wrote: Volker wrote: [...] I've attached the latest dmesg, can you see any similarities (as it still might be a hardware issue)? [...] Our current version is: FreeBSD 6.2-RELEASE FreeBSD 6.2-RELEASE #0 Looks like you are also using the EM network adapter driver. We are suspecting the driver or Network adapters them self. Our other boxes are using xl0 (3com) and are working fine. The em(4) driver has received quite a few updates lately, and I think some of them have been MFCed to RELENG_6 since 6.2-RELEASE. I don't use any em(4) interfaces myself (I prefer bge(4) and others), so I'm not sure if there's any relationship with your trouble, but I suggest you try updating to the latest 6-stable (RELENG_6) code. (Or even give 7-current a try if you have a spare disk for installation so you can quickly swap it back with 6.x if any show-stoppers arise. In general I don't recommend installing 7-current on production machines, though.) 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 'Instead of asking why a piece of software is using 1970s technology, start asking why software is ignoring 30 years of accumulated wisdom.' ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: xorg 7.2 start problem
On Wednesday 23 May 2007, Andriy Babiy wrote: You need at least the following ports: x11-drivers/xf86-video-mga x11-drivers/xf86-input-mouse x11-drivers/xf86-input-keyboard I wanted to thank everybody who helped me. I added those ports, and that fixed the problem I had before. So, I was able to issue: X -configure and obtain xorg.conf.new file. I checked the configuration and found that the hardware was recognized without errors. The pathes were changed to /usr/local accordingly. But when I issue: X -config /root/xorg.conf.new the X server doesn't start; it fails with the message: Fatal server error: could not open default font 'fixed' I checked xorg.conf.new and found that the pathes to appropriate fonts are listed there, namely: xorg-fonts-100dpi-7.2 xorg-fonts-75dpi-7.2 xorg-fonts-cyrillic-7.2 xorg-fonts-miscbitmaps-7.2 xorg-fonts-truetype-7.2 xorg-fonts-type1-7.2 I checked all the directories; they exist, and their contents exist. I tried mkfontdir in each of them, but it changed nothing. Maybe, you could advise me what I need to do in order to resolve it, apart from rebuilding the whole thing. Thank you very much in advance! joke Yep... you have to rebuild everything. Not to fix the error but just because you don't read other threads on the ML /joke On another thread the conclusion was that installing x11-fonts/font-alias solved the fixed font problem. -- Best Regards, Iulian Margarintescu http://www.erata.net [EMAIL PROTECTED] (spamassassin pf spamd all said it's OK to make it public ;-) ) Key ID: 0x03176E5CEDEFF7AB I prefer plain text email pgpm5emVwPNRB.pgp Description: PGP signature
Re: ghosthunting: machine freeze 6.2R
On 05/23/07 09:17, Oliver Fromme wrote: Roger Miranda wrote: Volker wrote: [...] I've attached the latest dmesg, can you see any similarities (as it still might be a hardware issue)? [...] Our current version is: FreeBSD 6.2-RELEASE FreeBSD 6.2-RELEASE #0 Looks like you are also using the EM network adapter driver. We are suspecting the driver or Network adapters them self. Our other boxes are using xl0 (3com) and are working fine. The em(4) driver has received quite a few updates lately, and I think some of them have been MFCed to RELENG_6 since 6.2-RELEASE. I don't use any em(4) interfaces myself (I prefer bge(4) and others), so I'm not sure if there's any relationship with your trouble, but I suggest you try updating to the latest 6-stable (RELENG_6) code. (Or even give 7-current a try if you have a spare disk for installation so you can quickly swap it back with 6.x if any show-stoppers arise. In general I don't recommend installing 7-current on production machines, though.) Oliver, thanks for your hints. I haven't monitored RELENG_6 for em changes. If the problem remains (today no freeze occurred) I'll go -STABLE on that machine and see if it solves the issues. Currently I'm watching this machine over the distance and waiting for the freeze... I'm unable to check -CURRENT on it (it's 24x7 production and remote and both is a 'don't do it'). Volker ___ 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 Interrupted system call (4) when exit from mc
Hi ALL When I start mc, and do Ctrl+o,and then write exit - I got... Sometime this heppend when I close some shell-aplication with Ctrl+C/D I setup FreeBSD 6.2RC1 and FreeBSD 6.2-stable... When I have 6.1 - I dont catch this 6.2-RELEASE-p4:server/exit read (subshell_pty...): Interrupted system call (4) ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Update on goal-setting resource
As you may know, the Legacy Project at www.legacyproject.org is an education initiative with the nonprofit Parenting Coalition and Generations United in Washington, DC. We have a new free online goal-setting resource that many homeschoolers, parents, and teachers are finding useful. 1) ACTIVITY SET: Teaching children to set goals and the skills to achieve them is important to academic and personal success. Research shows it's critical to get kids thinking early -- in elementary and middle school grades -- about what's important to them and why. Dreams and goals give life purpose, direction, and meaning. They help young people build toward the future, and offer a sense of control and hope. The new Begin and End With a Dream activity set offers over two dozen meaningful, literacy-based activities. A Star Highlights sheet gets children to make a Top 10 List of the best memories and things they've learned over the school year, while a Dream Reading List encourages them to set summer reading goals. There are ideas for making a Life List, inspiration for creating The Next Page in your life story, a My Dream sheet for sharing personal goals, and a Ladder to the Stars sheet for identifying the steps to reaching a goal. For the free online Begin and End With a Dream activity set: www.legacyproject.org/guides/beginend.html 2) DREAM BOOK: To start a discussion about a child's dreams and goals, we have our award-winning book Dream: A Tale of Wonder, Wisdom Wishes by author and educator Susan V. Bosak. Dream is illustrated by 15 top children's illustrators, like two-time Caldecott Medal winners Leo and Diane Dillon. The book has won 11 national awards, including an International Reading Association Children's Choice (10,000 children read and vote on the books they like best), a Teachers' Choice, an iParenting Award, and the Pinnacle Award for Best Gift Book. Says The Bloomsbury Review, This elegant book depicts the journey of life -- from infancy to older adulthood -- highlighting all the hopes and dreams found along the way... Inspirational quotes from people such as Martin Luther King Jr, Sir Edmund Hillary, and Emily Dickinson are set alongside gorgeous illustrations by internationally acclaimed artists. Richly crafted and thoughtfully written, 'Dream' is a dazzling project that challenges us to find a dream and follow it. In addition to being a rich cross-curricular literacy resource, Dream is a great gift book for life milestones like a graduation, birth, birthday, even retirement. So, check out Dream by Susan V. Bosak on the graduation gift display in the children's section of bookstores like Barnes Noble, Borders, Chapters/Indigo, and Books-A-Million. You can also get a bonus with your book purchase... 3) GET A BONUS: If you don't already have Dream, it's worth looking at. And if you do, you know it's worth giving to friends and family. When you go to your local bookstore to get Dream (Susan Bosak, $17.95) between May 20 and June 17, 2007 and send us your receipt, you get a special bonus -- Legacy Dollars you can redeem for books, CDs, and posters. For example, one copy of Dream would earn six Legacy Dollars, enough for a softcover copy of the heartwarming bestseller Something to Remember Me By, a story about love across generations that many compare to Love You Forever. For all the details, www.legacyproject.org/books/specialdr.html If you have any questions, feel free to contact me. Also, please pass along this e-mail to friends you think might be interested. As a small educational group, we depend on word-of-mouth. Best, Brian Puppa Program Director Legacy Project [EMAIL PROTECTED] (800) 772-7765 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Opening /dev/ad0 for writing render the system unusable until reboot
Hi! Would anybody be so kind to look at http://www.FreeBSD.org/cgi/query-pr.cgi?pr=kern/112707 ? In short: the command true /dev/ad0 makes all access to filesystem fail for GENERIC and produces panic for INVARIANTS-enabled kernel. This make it impossible to do boot0cfg -s 2 ad0 for remote upgrade of NanoBSD running from IDE Flash. Thank you. Eugene Grosbein ___ 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 Interrupted system call (4) when exit from mc
When I start mc, and do Ctrl+o,and then write exit - I got... Sometime this heppend when I close some shell-aplication with Ctrl+C/D I setup FreeBSD 6.2RC1 and FreeBSD 6.2-stable... When I have 6.1 - I dont catch this If I get it right, it should be midnight commander? Exits fine with F10. On my nokia 770 I go out with just escape 0. Yes, I see some issue with xchm from mc, but ctrl l resolves it. Zoran ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
atapicam cd error
Hi, some knows how to solve this problema or what it is? acd0: CDRW HL-DT-ST GCE-8527B/1.02 at ata0-master UDMA33 acd0: FAILURE - INQUIRY ILLEGAL REQUEST asc=0x24 ascq=0x00 acd0: FAILURE - INQUIRY ILLEGAL REQUEST asc=0x24 ascq=0x00 cd0 at ata0 bus 0 target 0 lun 0 cd0: HL-DT-ST CD-RW GCE-8527B 1.02 Removable CD-ROM SCSI-0 device cd0: 33.000MB/s transfers cd0: cd present [1 x 2048 byte records] acd0: FAILURE - READ_TOC ILLEGAL REQUEST asc=0x24 ascq=0x00 acd0: FAILURE - READ_TOC ILLEGAL REQUEST asc=0x24 ascq=0x00 I can still mount and read bot not write anymore k3b crashes whith CD inserted or when I put one in telling about in pthread_testcancel () from lib/libpthread.so.2 in pthread_mutexattr_init () from lib/libpthread.so.2 in pthread_setconcurrency () from lib/libpthread.so.2 -- João A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: atapicam cd error
On Wed, 2007-05-23 at 12:44 -0300, JoaoBR wrote: Hi, some knows how to solve this problema or what it is? acd0: CDRW HL-DT-ST GCE-8527B/1.02 at ata0-master UDMA33 acd0: FAILURE - INQUIRY ILLEGAL REQUEST asc=0x24 ascq=0x00 acd0: FAILURE - INQUIRY ILLEGAL REQUEST asc=0x24 ascq=0x00 cd0 at ata0 bus 0 target 0 lun 0 cd0: HL-DT-ST CD-RW GCE-8527B 1.02 Removable CD-ROM SCSI-0 device cd0: 33.000MB/s transfers cd0: cd present [1 x 2048 byte records] acd0: FAILURE - READ_TOC ILLEGAL REQUEST asc=0x24 ascq=0x00 acd0: FAILURE - READ_TOC ILLEGAL REQUEST asc=0x24 ascq=0x00 I can still mount and read bot not write anymore k3b crashes whith CD inserted or when I put one in telling about in pthread_testcancel () from lib/libpthread.so.2 in pthread_mutexattr_init () from lib/libpthread.so.2 in pthread_setconcurrency () from lib/libpthread.so.2 Running what version, updated when? Search the archive for k3b, there were extensive discussions on this problem. signature.asc Description: This is a digitally signed message part
Re: atapicam cd error
On Wednesday 23 May 2007 13:05:40 you wrote: JoaoBR wrote: Hi, some knows how to solve this problema or what it is? acd0: CDRW HL-DT-ST GCE-8527B/1.02 at ata0-master UDMA33 acd0: FAILURE - INQUIRY ILLEGAL REQUEST asc=0x24 ascq=0x00 acd0: FAILURE - INQUIRY ILLEGAL REQUEST asc=0x24 ascq=0x00 cd0 at ata0 bus 0 target 0 lun 0 cd0: HL-DT-ST CD-RW GCE-8527B 1.02 Removable CD-ROM SCSI-0 device cd0: 33.000MB/s transfers cd0: cd present [1 x 2048 byte records] acd0: FAILURE - READ_TOC ILLEGAL REQUEST asc=0x24 ascq=0x00 acd0: FAILURE - READ_TOC ILLEGAL REQUEST asc=0x24 ascq=0x00 I can still mount and read bot not write anymore k3b crashes whith CD inserted or when I put one in telling about in pthread_testcancel () from lib/libpthread.so.2 in pthread_mutexattr_init () from lib/libpthread.so.2 in pthread_setconcurrency () from lib/libpthread.so.2 It's fixed in latest 6-STABLE. hum, dont think so, I cvsupped yesterday and portstree also and it is still here -- João A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: atapicam cd error
JoaoBR wrote: Hi, some knows how to solve this problema or what it is? acd0: CDRW HL-DT-ST GCE-8527B/1.02 at ata0-master UDMA33 acd0: FAILURE - INQUIRY ILLEGAL REQUEST asc=0x24 ascq=0x00 acd0: FAILURE - INQUIRY ILLEGAL REQUEST asc=0x24 ascq=0x00 cd0 at ata0 bus 0 target 0 lun 0 cd0: HL-DT-ST CD-RW GCE-8527B 1.02 Removable CD-ROM SCSI-0 device cd0: 33.000MB/s transfers cd0: cd present [1 x 2048 byte records] acd0: FAILURE - READ_TOC ILLEGAL REQUEST asc=0x24 ascq=0x00 acd0: FAILURE - READ_TOC ILLEGAL REQUEST asc=0x24 ascq=0x00 I can still mount and read bot not write anymore k3b crashes whith CD inserted or when I put one in telling about in pthread_testcancel () from lib/libpthread.so.2 in pthread_mutexattr_init () from lib/libpthread.so.2 in pthread_setconcurrency () from lib/libpthread.so.2 It's fixed in latest 6-STABLE. /cjg ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
AcerLabs/ULi SATA woes (was: Re: Gigabyte GA-VM900M caveats)
The affected Gigabyte motherboard boots fine with a JMicron card -- the hard workaround was to disable the VIA onboard SATA and IDE controllers completely and swap in the spare PCI-e card. However, the machine I swapped this card out of does not boot now: atapci1: AcerLabs M5287 SATA150 controller port 0xec00-0xec0f,0xe880-0xe887,0xe800-0xe80f,0xe480-0xe487,0xe400-0xe41f mem 0xfebff800-0xfebffbff irq 21 at device 31.1 on pci0 atapci1: Reserved 0x20 bytes for rid 0x20 type 4 at 0xe400 ioapic0: routing intpin 21 (PCI IRQ 21) to vector 51 atapci1: [MPSAFE] atapci1: Reserved 0x400 bytes for rid 0x24 type 3 at 0xfebff800 atapci1: AHCI controller reset failure device_attach: atapci1 attach returned 6 This is with -CURRENT p4'd with an IFC from around 2-3 weeks ago on branch bms_netdev, which suggests the regression is still present in -CURRENT. 6.2-STABLE from around 1 month ago had the same AHCI controller reset problem. I'm not really sure how best to deal with this -- the machine needs to be working, that's for sure, as it is the machine where I do most of my FreeBSD development. There were no problems with 6.1-RELEASE, it has 4 SATA ports on the motherboard which makes it useful (although, ironically, there are probably not enough drive bays as it is a small ASUS barebones system), and it strikes one as odd that it might be necessary to maintain patches for consumer off-the-shelf hardware. Suggestions? Regards, BMS ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: atapicam cd error
On Wed, May 23, 2007 at 01:28:50PM -0300, JoaoBR wrote: On Wednesday 23 May 2007 13:05:40 you wrote: JoaoBR wrote: Hi, some knows how to solve this problema or what it is? acd0: CDRW HL-DT-ST GCE-8527B/1.02 at ata0-master UDMA33 acd0: FAILURE - INQUIRY ILLEGAL REQUEST asc=0x24 ascq=0x00 acd0: FAILURE - INQUIRY ILLEGAL REQUEST asc=0x24 ascq=0x00 cd0 at ata0 bus 0 target 0 lun 0 cd0: HL-DT-ST CD-RW GCE-8527B 1.02 Removable CD-ROM SCSI-0 device cd0: 33.000MB/s transfers cd0: cd present [1 x 2048 byte records] acd0: FAILURE - READ_TOC ILLEGAL REQUEST asc=0x24 ascq=0x00 acd0: FAILURE - READ_TOC ILLEGAL REQUEST asc=0x24 ascq=0x00 It's fixed in latest 6-STABLE. hum, dont think so, I cvsupped yesterday and portstree also and it is still here Did you buildkernel + installkernel + reboot after cvsup'ing? -- | 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: atapicam cd error
On Wednesday 23 May 2007 13:46:55 Jeremy Chadwick wrote: On Wed, May 23, 2007 at 01:28:50PM -0300, JoaoBR wrote: On Wednesday 23 May 2007 13:05:40 you wrote: JoaoBR wrote: Hi, some knows how to solve this problema or what it is? acd0: CDRW HL-DT-ST GCE-8527B/1.02 at ata0-master UDMA33 acd0: FAILURE - INQUIRY ILLEGAL REQUEST asc=0x24 ascq=0x00 acd0: FAILURE - INQUIRY ILLEGAL REQUEST asc=0x24 ascq=0x00 cd0 at ata0 bus 0 target 0 lun 0 cd0: HL-DT-ST CD-RW GCE-8527B 1.02 Removable CD-ROM SCSI-0 device cd0: 33.000MB/s transfers cd0: cd present [1 x 2048 byte records] acd0: FAILURE - READ_TOC ILLEGAL REQUEST asc=0x24 ascq=0x00 acd0: FAILURE - READ_TOC ILLEGAL REQUEST asc=0x24 ascq=0x00 It's fixed in latest 6-STABLE. hum, dont think so, I cvsupped yesterday and portstree also and it is still here Did you buildkernel + installkernel + reboot after cvsup'ing? sure, but as make kernel KERNCONF=blabla after building world may be that I am running amd64 is the problem? -- João A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: atapicam cd error
On Wed, May 23, 2007 at 01:49:33PM -0300, JoaoBR wrote: sure, but as make kernel KERNCONF=blabla after building world may be that I am running amd64 is the problem? I only run i386, so I can't confirm/deny. Sorry. :-( -- | 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: atapicam cd error
On Wednesday 23 May 2007 14:03:18 Jeremy Chadwick wrote: On Wed, May 23, 2007 at 01:49:33PM -0300, JoaoBR wrote: sure, but as make kernel KERNCONF=blabla after building world may be that I am running amd64 is the problem? I only run i386, so I can't confirm/deny. Sorry. :-( I am now compiling on my nb which is i386 to confirm this or compare thank's so far! -- João A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: AcerLabs/ULi SATA woes
A workaround for this issue posted here works for me with 6.2-STABLE: http://www.mail-archive.com/freebsd-stable@freebsd.org/msg87083.html I plan to commit it on HEAD and RELENG_6 as soon as possible, as it fixes the regression introduced last year. It seems acceptable that the AHCI controller be degraded to legacy mode until such time as AHCI mode may be reliably enabled on this hardware. I don't have time to implement a better fix. It seems there has been some Linux activity from the vendor. The controller on my system is the one described in the patch set for Linux: http://www.ussg.iu.edu/hypermail/linux/kernel/0412.2/0825.html Regards, BMS ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: xorg 7.2 start problem
On Wed, May 23, 2007 at 11:06:46AM +0300, Iulian M wrote: joke Yep... you have to rebuild everything. Not to fix the error but just because you don't read other threads on the ML /joke On another thread the conclusion was that installing x11-fonts/font-alias solved the fixed font problem. Speaking of not reading other threads, you might also look closer to home ;) Adding font-alias would just be treating the next symptom, and then you'll probably find that something else still doesn't work because it is also missing. As I've said a *number* of times already (and as is mentioned in the UPDATING instructions), install the x11/xorg port to obtain a complete installation. Kris pgp1OjLCXYvnp.pgp Description: PGP signature
Re: AcerLabs/ULi SATA woes
Just for reference:
Soren has gotten back to me about this and has a patch pending. In the
meantime here is the style(9)-ified patch from Sven which I am currently
using (in 6.2-STABLE, CURRENT , and p4 branches).
Regards,
BMS
--- ata-chipset.c.orig Wed May 23 17:59:28 2007
+++ ata-chipset.c Wed May 23 18:00:44 2007
@@ -952,7 +952,7 @@
struct ata_chip_id *idx;
static struct ata_chip_id ids[] =
{{ ATA_ALI_5289, 0x00, 2, ALISATA, ATA_SA150, M5289 },
- { ATA_ALI_5288, 0x00, 4, ALISATA, ATA_SA300, M5288 },
+ { ATA_ALI_5288, 0x00, 4, ALIAHCI, ATA_SA300, M5288 },
{ ATA_ALI_5287, 0x00, 4, ALISATA, ATA_SA150, M5287 },
{ ATA_ALI_5281, 0x00, 2, ALISATA, ATA_SA150, M5281 },
{ ATA_ALI_5229, 0xc5, 0, ALINEW, ATA_UDMA6, M5229 },
@@ -984,16 +984,19 @@
switch (ctlr-chip-cfg2) {
case ALISATA:
+case ALIAHCI:
ctlr-channels = ctlr-chip-cfg1;
ctlr-allocate = ata_ali_sata_allocate;
ctlr-setmode = ata_sata_setmode;
/* if we have a memory resource we can likely do AHCI */
- ctlr-r_type2 = SYS_RES_MEMORY;
- ctlr-r_rid2 = PCIR_BAR(5);
- if ((ctlr-r_res2 = bus_alloc_resource_any(dev, ctlr-r_type2,
- ctlr-r_rid2, RF_ACTIVE)))
- return ata_ahci_chipinit(dev);
+ if (ctlr-chip-cfg2 == ALIAHCI) {
+ ctlr-r_type2 = SYS_RES_MEMORY;
+ ctlr-r_rid2 = PCIR_BAR(5);
+ if ((ctlr-r_res2 = bus_alloc_resource_any(dev,
+ ctlr-r_type2, ctlr-r_rid2, RF_ACTIVE)))
+ return ata_ahci_chipinit(dev);
+ }
/* enable PCI interrupt */
pci_write_config(dev, PCIR_COMMAND,
--- ata-pci.h.orig Wed May 23 18:00:53 2007
+++ ata-pci.h Wed May 23 18:01:02 2007
@@ -360,6 +360,7 @@
#define ALIOLD 0x01
#define ALINEW 0x02
#define ALISATA 0x04
+#define ALIAHCI 0x08
#define HPT366 0
#define HPT370 1
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ghosthunting: machine freeze 6.2R
On Tuesday 22 May 2007 14:03, Kris Kennaway wrote: What happens if you enable INVARIANTS and/or WITNESS? I have enabled WITNESS, I have no experienced a freeze yet. But i did notice on boot an WITNESS message for if_bridge. See attached. Could this be causing the freeze? softdep_waitidle: Failed to flush worklist for 0xc44ffcf8 em1: link state changed to DOWN bridge0: Ethernet address: 66:9e:c9:a6:f5:27 em0: promiscuous mode enabled em1: promiscuous mode enabled em1: link state changed to UP lock order reversal: 1st 0xc06e0820 polling (polling) @ /usr/src/sys/kern/kern_poll.c:422 2nd 0xc473070c if_bridge (if_bridge) @ /usr/src/sys/net/if_bridge.c:1976 KDB: stack backtrace: witness_checkorder(c473070c,9,c068bfbc,7b8) at witness_checkorder+0x55c _mtx_lock_flags(c473070c,0,c068bfbc,7b8,c473070c,...) at _mtx_lock_flags+0x41 bridge_input(c43d9000,c474,c43a828c,c43a8000,c474,...) at bridge_input+0x80 ether_input(c43d9000,c474,c43a828c,0,c0675f3c,...) at ether_input+0x122 e1000_rxeof(d43f2cbc,c0524e5d,d43f2ca8,1,5,...) at e1000_rxeof+0x19b e1000_poll(c43d9000,0,5) at e1000_poll+0x46 netisr_poll(0) at netisr_poll+0x70 swi_net(0,c4315438,c4323a80,c050a484,c4322648,...) at swi_net+0xb0 ithread_loop(c430f700,d43f2d38,c430f700,c050a484,0,...) at ithread_loop+0x1de fork_exit(c050a484,c430f700,d43f2d38) at fork_exit+0x7d fork_trampoline() at fork_trampoline+0x8 --- trap 0x1, eip = 0, esp = 0xd43f2d6c, ebp = 0 --- softdep_waitidle: Failed to flush worklist for 0xc44ffcf8 em0: link state changed to UP ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: xorg 7.2 start problem
On Wednesday 23 May 2007 16:26:25 Kris Kennaway wrote: On Wed, May 23, 2007 at 11:06:46AM +0300, Iulian M wrote: joke Yep... you have to rebuild everything. Not to fix the error but just because you don't read other threads on the ML /joke On another thread the conclusion was that installing x11-fonts/font-alias solved the fixed font problem. Speaking of not reading other threads, you might also look closer to home ;) Adding font-alias would just be treating the next symptom, and then you'll probably find that something else still doesn't work because it is also missing. As I've said a *number* of times already (and as is mentioned in the UPDATING instructions), install the x11/xorg port to obtain a complete installation. I also haven't read anything and got terrible caught by this 7.2 xorg thing I guess that the most shit comes from the path change and that portupgrade deos not tell anything about the old default /usr/X11R6/lib/X11/fonts change to /usr/local/lib/X11/fonts. Kind of sed operation would have solved this easily without bothering anyone Seems it is necessary to delete manually the old font dirs because portupgrade does not. so then most people may find out that editing the font paths in xorg.conf will solve the problem at the end and not to forget the new X path in kdmrc which also is a good one when saying a msg as cannot execute instead of is not there ... :) font-alias also does wierd things and creates font.alias even for fonts which are not installed, let's say cyrillic for instance, not sure if this is right, anyway, font-alias is not necessary I think and kind of lame that portupgrade xorg does not install the modules, that is a funny strike uninstalling xorg and installing the meta port also does not solve the issue ... but installs some zillions of font crap which I can not believe that somebody still use them but it was a funny day and useful to learn finally something about xorg which before 7.2 was a really too easy going install :) -- João A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: atapicam cd error
On Wednesday 23 May 2007 14:03:18 Jeremy Chadwick wrote: On Wed, May 23, 2007 at 01:49:33PM -0300, JoaoBR wrote: acd0: CDRW HL-DT-ST GCE-8527B/1.02 at ata0-master UDMA33 acd0: FAILURE - INQUIRY ILLEGAL REQUEST asc=0x24 ascq=0x00 acd0: FAILURE - INQUIRY ILLEGAL REQUEST asc=0x24 ascq=0x00 cd0 at ata0 bus 0 target 0 lun 0 cd0: HL-DT-ST CD-RW GCE-8527B 1.02 Removable CD-ROM SCSI-0 device cd0: 33.000MB/s transfers cd0: cd present [1 x 2048 byte records] acd0: FAILURE - READ_TOC ILLEGAL REQUEST asc=0x24 ascq=0x00 acd0: FAILURE - READ_TOC ILLEGAL REQUEST asc=0x24 ascq=0x00 sure, but as make kernel KERNCONF=blabla after building world may be that I am running amd64 is the problem? I only run i386, so I can't confirm/deny. Sorry. :-( ok I compiled on i386 it's ok, also k3b works fine I recompiled amd64 world and kernel to be sure and the problem persists -- João A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: xorg 7.2 start problem
On Wed, May 23, 2007 at 05:29:54PM -0300, JoaoBR wrote: I also haven't read anything and got terrible caught by this 7.2 xorg thing Says it all, really. :-) and kind of lame that portupgrade xorg does not install the modules, And how is portupgrade to know which specific drivers you need? There will always be big ports changes that exceed the capabilities of the automated ports management tools and need manual intervention. 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) pgprQfHaYPRve.pgp Description: PGP signature
Re: xorg 7.2 start problem
On Wednesday 23 May 2007 17:51:34 Roland Smith wrote: On Wed, May 23, 2007 at 05:29:54PM -0300, JoaoBR wrote: I also haven't read anything and got terrible caught by this 7.2 xorg thing Says it all, really. :-) you're not laughing at me aren't you? and kind of lame that portupgrade xorg does not install the modules, And how is portupgrade to know which specific drivers you need? good question deserve good answers: how the heck portupgrade did it before? There will always be big ports changes that exceed the capabilities of the automated ports management tools and need manual intervention. absolutely, but only partial correct because the tools are perfectly capable, the thing is that the process is not really thought through enough when publishing it -- João A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Broken locale after upgrade to 6-STABEL from 5-STABLE
Recently i figured out that all locales stopped working
properly on some of my 6-STABLE servers and in all jails
on them.
These server diffeer from others (on which locale work)
in that they were upgraded to 6-STABLE directly from
5.3-STABLE.
Test was easy:
#!/usr/bin/perl
use POSIX qw(locale_h);
use locale;
setlocale(LC_ALL, 'ru_RU.CP1251') || warn LOCALE: $!\n;
print lc(РУЧКАручкаABCabc\n).\n;
(the string is partially in RUssia, so you might not
be able to see correctly, but that is not the point).
After an hour of figuring out why it does not work
i figureed that it was because of
/lib/libc.so.5
I chflaged it, deleted it and made a link to
libc.so.6
After that setlocale in perl worked fine.
However, on another server, where setlocale worked
and works fine this libc.so.5 also present and causes
no problems.
What i don't understand, is how the appropriate 'so'
is selected? How freebsd known which so to load
this
libc.so.5
or this
libc.so.6
?
where it is specified?
Another question, is why setlocale in C
says that locale is set fine.
A simple proggie:
#include locale.h
#include errno.h
#include ctype.h
main(){
char *b=setlocale(LC_ALL, ru_RU.CP1251);
if (!b){
printf(FAILED! %d\n,errno);
}
else {
printf(OK: %s %d\n,b,errno);
printf(LOCALE %s\n,setlocale(LC_CTYPE,NULL));
printf(1: TO UPPER %c TO LOWER %c\n,toupper('я'),tolower('Я'));
printf(1-0: TO UPPER %c TO LOWER %c\n,toupper('Я'),tolower('я'));
printf(2: TO UPPER %c TO LOWER %c\n,toupper('r'),tolower('R'));
}
}
Does not work even when locales work on perl (toupper does not
return an upper letter for russia, but works with latin r, same
with tolower).
Am i missing something?
--
Regards,
Artem
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ghosthunting: machine freeze 6.2R
talking to myself... ;) On 2007-05-23 10:27, Volker wrote: Currently I'm watching this machine over the distance and waiting for the freeze... ...and the machine freeze came this afternoon. I've had a good dump of the network traffic and haven't seen any strange network traffic. Unfortunately three hours later, the machine died completely. It has been a hardware failure which came quietly. Sorry for the noise I've put on this list but when experiencing things like that, one has to think in all possible directions (I first thought about a DoS attack). Thx! Volker ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: xorg 7.2 start problem
On Wed, May 23, 2007 at 06:18:12PM -0300, JoaoBR wrote:
On Wednesday 23 May 2007 17:51:34 Roland Smith wrote:
On Wed, May 23, 2007 at 05:29:54PM -0300, JoaoBR wrote:
I also haven't read anything and got terrible caught by this 7.2 xorg
thing
Says it all, really. :-)
you're not laughing at me aren't you?
A little. Ignoring /usr/{ports|src}/UPDATING usually has predictable results.
Been there, done that. :-)
and kind of lame that portupgrade xorg does not install the modules,
And how is portupgrade to know which specific drivers you need?
good question deserve good answers: how the heck portupgrade did it before?
It didn't. All the drivers were in one huge package, the X server. Now
they are in seperate ports. But the xorg or xorgs-drivers meta-ports
should install all of them.
There will always be big ports changes that exceed the capabilities of
the automated ports management tools and need manual intervention.
absolutely, but only partial correct because the tools are perfectly capable,
the thing is that the process is not really thought through enough when
publishing it
That's funny. :-) If you can't be bothered to read UPDATING, you are not
the person to tell the maintainers that they haven't thought it
through.
Tools like portupgrade and portmaster and even the ports system are
great but they have their limitations. I think they are kept relatively
simple for a reason. It's much better to have a simple (maintainable)
tool that does 95% of the jobs well than to build an extremely
complicated ACME contraption that can cover all the corner cases and
oddball situations. It's just not worth the effort.
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)
pgpoEkCp7cPMT.pgp
Description: PGP signature
Strange ACPI messages on Core 2 Duo system
Hi, I noticed the following in dmesg output should I be concerned? this is with 6.2-RELEASE SMP kernel. This is a Gigabyte GA-VM900M with Intel Core 2 Duo E4300 CPU. Copyright (c) 1992-2007 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 6.2-RELEASE #0: Fri Jan 12 11:05:30 UTC 2007 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/SMP Timecounter i8254 frequency 1193182 Hz quality 0 CPU: Intel(R) Core(TM)2 CPU 4300 @ 1.80GHz (1808.71-MHz 686-class CPU) Origin = GenuineIntel Id = 0x6f2 Stepping = 2 Features=0xbfebfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,C MOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE Features2=0xe39dSSE3,RSVD2,MON,DS_CPL,EST,TM2,b9,CX16,b14,b15 AMD Features=0x2010NX,LM AMD Features2=0x1LAHF Cores per package: 2 real memory = 1006567424 (959 MB) avail memory = 975724544 (930 MB) ACPI APIC Table: GBTGBTUACPI FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 ioapic0: Changing APIC ID to 2 ioapic0 Version 0.3 irqs 0-23 on motherboard ioapic1 Version 0.3 irqs 24-47 on motherboard kbd1 at kbdmux0 ath_hal: 0.9.17.2 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413) acpi0: GBT GBTUACPI on motherboard ACPI-0438: *** Error: Looking up [\\_SB_.PCI0.LNK9] in namespace, AE_NOT_FOU ND SearchNode 0xc49c2480 StartNode 0xc49c2480 ReturnNode 0 ACPI-0438: *** Error: Looking up [\\_SB_.PCI0.LNK9] in namespace, AE_NOT_FOU ND SearchNode 0xc49c22c0 StartNode 0xc49c22c0 ReturnNode 0 ACPI-0438: *** Error: Looking up [\\_SB_.PCI0.LNK9] in namespace, AE_NOT_FOU ND SearchNode 0xc49c1ca0 StartNode 0xc49c1ca0 ReturnNode 0 ACPI-0438: *** Error: Looking up [\\_SB_.PCI0.LNK9] in namespace, AE_NOT_FOU ND SearchNode 0xc49c3cc0 StartNode 0xc49c3cc0 ReturnNode 0 ACPI-0438: *** Error: Looking up [\\_SB_.PCI0.LNK9] in namespace, AE_NOT_FOU ND SearchNode 0xc49c3ac0 StartNode 0xc49c3ac0 ReturnNode 0 ACPI-0438: *** Error: Looking up [\\_SB_.PCI0.LNK9] in namespace, AE_NOT_FOU ND SearchNode 0xc49c79a0 StartNode 0xc49c79a0 ReturnNode 0 acpi_bus_number: can't get _ADR (repeated ~30 times) The rest is pretty normal. Regards, BMS ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ghosthunting: machine freeze 6.2R
On Wed, May 23, 2007 at 11:31:32PM +0100, Volker wrote: talking to myself... ;) On 2007-05-23 10:27, Volker wrote: Currently I'm watching this machine over the distance and waiting for the freeze... ...and the machine freeze came this afternoon. I've had a good dump of the network traffic and haven't seen any strange network traffic. Unfortunately three hours later, the machine died completely. It has been a hardware failure which came quietly. Sorry for the noise I've put on this list but when experiencing things like that, one has to think in all possible directions (I first thought about a DoS attack). Even though it turned out to be a hardware failure, it was helpful to publicize this fact. It is often difficult to convince users to accept the possibility that hardware failure may be the cause of weird system behaviour, because it has always been fine. It is worth remembering that if your hardware is going to fail, then there is going to be a first time. Kris ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ghosthunting: machine freeze 6.2R
On Wed, May 23, 2007 at 02:57:59PM -0500, Roger Miranda wrote: On Tuesday 22 May 2007 14:03, Kris Kennaway wrote: What happens if you enable INVARIANTS and/or WITNESS? I have enabled WITNESS, I have no experienced a freeze yet. But i did notice on boot an WITNESS message for if_bridge. See attached. Could this be causing the freeze? Possibly, the point of WITNESS is to detect possible deadlock conditions that can cause hangs at runtime so it may well have succeeded to do its job here. Kris ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: xorg 7.2 start problem
On Wednesday 23 May 2007 18:46:41 Roland Smith wrote:
On Wed, May 23, 2007 at 06:18:12PM -0300, JoaoBR wrote:
On Wednesday 23 May 2007 17:51:34 Roland Smith wrote:
On Wed, May 23, 2007 at 05:29:54PM -0300, JoaoBR wrote:
I also haven't read anything and got terrible caught by this 7.2 xorg
thing
Says it all, really. :-)
you're not laughing at me aren't you?
A little. Ignoring /usr/{ports|src}/UPDATING usually has predictable
results. Been there, done that. :-)
good to know, so at the end nobody is alone and some beast will bite me again
sooner or later at the same place :)
and kind of lame that portupgrade xorg does not install the modules,
And how is portupgrade to know which specific drivers you need?
good question deserve good answers: how the heck portupgrade did it
before?
It didn't. All the drivers were in one huge package, the X server. Now
they are in seperate ports. But the xorg or xorgs-drivers meta-ports
should install all of them.
ok, that is what I ment, the better way would be that portupgrade installs
them all as before (when they were in the package)
I believe that is unusual that some de-installs xorg and installs the meta
port then and also I am not sure but I believe that xorg needs some drivers
in any case so it should be a necessary step or dependency here
That's funny. :-) If you can't be bothered to read UPDATING, you are not
the person to tell the maintainers that they haven't thought it
through.
yup, that is right but life is hard either way and it is never fair to all of
us, but then, thinking well, we might discover that the critics are ever a
valid input even if appear to one or another as offense they might not been
thought to be so
Tools like portupgrade and portmaster and even the ports system are
great but they have their limitations. I think they are kept relatively
simple for a reason. It's much better to have a simple (maintainable)
tool that does 95% of the jobs well than to build an extremely
complicated ACME contraption that can cover all the corner cases and
oddball situations. It's just not worth the effort.
I agree and totally understandable but when there is a big change involved
then it would be wise to advise more clearly what is happening from within
the upgrade process because almost nobody reads the files especially when he
portupgraded flawless something like xorg for years, even from x86 to xorg
was a no-issue at all but there was a scary name-change.
other ports do it for less and a message like local base has changed you need
to edit your xorg.conf or something would do good here
--
João
A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura.
Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]
6.2-STABLE Hard Freeze while using RAID1 on Adaptec 1210SA
Hi, I am trying to use two SATA II disks over an Adaptec 1210SA PCI SATA Controller (based on SiI 3112 SATA150 chip). While trying to use the disks I get shortly the following message and the system is hard freezing soon after that. May 14 15:47:32 noname kernel: ad6: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=238231007 If I move the HDD's in a computer with VIA SATA150 on board or nVIDIA SATA150 the RAID system is working without problems with the same version of FreeBSD. Are there any known problems with this Adaptec controller or is the combination controller SATA150 and HDD SATA300 not well supported? Is there a way to fix this? The system is installed on a 3rd disk (IDE). Regrads, Johny. Here is the dmesg taken on the system with Adaptec controller: Copyright (c) 1992-2007 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 6.2-STABLE-200704 #0: Sun Apr 1 11:05:41 UTC 2007 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC Timecounter i8254 frequency 1193182 Hz quality 0 CPU: Intel Pentium III (999.72-MHz 686-class CPU) Origin = GenuineIntel Id = 0x686 Stepping = 6 Features=0x383f9ffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE real memory = 1073659904 (1023 MB) avail memory = 1041649664 (993 MB) kbd1 at kbdmux0 ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413) acpi0: ASUS CUV4X_EA on motherboard acpi0: Power Button (fixed) Timecounter ACPI-fast frequency 3579545 Hz quality 1000 acpi_timer0: 24-bit timer at 3.579545MHz port 0xe408-0xe40b on acpi0 cpu0: ACPI CPU on acpi0 acpi_throttle0: ACPI CPU Throttling on cpu0 acpi_button0: Power Button on acpi0 pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0 pci0: ACPI PCI bus on pcib0 agp0: VIA 82C691 (Apollo Pro) host to PCI bridge mem 0xfc00-0xfdff at device 0.0 on pci0 pcib1: ACPI PCI-PCI bridge at device 1.0 on pci0 pci1: ACPI PCI bus on pcib1 pci1: display, VGA at device 0.0 (no driver attached) isab0: PCI-ISA bridge at device 4.0 on pci0 isa0: ISA bus on isab0 atapci0: VIA 82C686B UDMA100 controller port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xd800-0xd80f at device 4.1 on pci0 ata0: ATA channel 0 on atapci0 ata1: ATA channel 1 on atapci0 uhci0: VIA 83C572 USB controller port 0xd400-0xd41f irq 11 at device 4.2 on pci0 uhci0: [GIANT-LOCKED] usb0: VIA 83C572 USB controller on uhci0 usb0: USB revision 1.0 uhub0: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered uhci1: VIA 83C572 USB controller port 0xd000-0xd01f irq 11 at device 4.3 on pci0 uhci1: [GIANT-LOCKED] usb1: VIA 83C572 USB controller on uhci1 usb1: USB revision 1.0 uhub1: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered atapci1: SiI 3112 SATA150 controller port 0xb800-0xb807,0xb400-0xb403,0xb000-0xb007,0xa800-0xa803,0xa400-0xa40f mem 0xf800-0xf80001ff irq 10 at device 7.0 on pci0 ata2: ATA channel 0 on atapci1 ata3: ATA channel 1 on atapci1 xl0: 3Com 3c905C-TX Fast Etherlink XL port 0xa000-0xa07f mem 0xf780-0xf780007f irq 11 at device 10.0 on pci0 miibus0: MII bus on xl0 xlphy0: 3c905C 10/100 internal PHY on miibus0 xlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto xl0: Ethernet address: 00:01:02:fa:01:a1 fdc0: floppy drive controller port 0x3f2-0x3f5,0x3f7 irq 6 drq 2 on acpi0 fdc0: [FAST] fd0: 1440-KB 3.5 drive on fdc0 drive 0 ppc0: ECP parallel printer port port 0x378-0x37f,0x778-0x77b irq 7 drq 3 on acpi0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/8 bytes threshold ppbus0: Parallel port bus on ppc0 plip0: PLIP network interface on ppbus0 lpt0: Printer on ppbus0 lpt0: Interrupt-driven port ppi0: Parallel I/O on ppbus0 sio0: 16550A-compatible COM port port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A sio1: 16550A-compatible COM port port 0x2f8-0x2ff irq 3 on acpi0 sio1: type 16550A atkbdc0: Keyboard controller (i8042) port 0x60,0x64 irq 1 on acpi0 atkbd0: AT Keyboard irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] psm0: PS/2 Mouse irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: model IntelliMouse Explorer, device ID 4 pmtimer0 on isa0 orm0: ISA Option ROMs at iomem 0xc-0xc7fff,0xc8000-0xcbfff,0xcc000-0xcc7ff on isa0 sc0: System console at flags 0x100 on isa0 sc0: VGA 16 virtual consoles, flags=0x300 vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on isa0 Timecounter TSC frequency 999720598 Hz quality 800 Timecounters tick every 1.000 msec ad0: 19623MB IBM DTLA-305020 TW2OA60A at ata0-master UDMA100 acd0: CDROM TOSHIBA CD-ROM XM-6702B/1007 at ata1-master UDMA33 ad4: 157066MB Hitachi HDS721616PLA380 P22OA70A at ata2-master SATA150 ad6: 157066MB Hitachi HDS721616PLA380 P22OA70A at ata3-master SATA150 ar0: 157066MB Adaptec
Re: Broken locale after upgrade to 6-STABEL from 5-STABLE
On Thu, May 24, 2007, Artem Kuchin wrote: What i don't understand, is how the appropriate 'so' is selected? How freebsd known which so to load this libc.so.5 or this libc.so.6 ? Did you recompile Perl after the last installworld? If not, do so. -- Whenever you find that you are on the side of the majority, it is time to reform. -- Mark Twain ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: xorg 7.2 start problem
On Wed, 23 May 2007, JoaoBR wrote: On Wednesday 23 May 2007 17:51:34 Roland Smith wrote: On Wed, May 23, 2007 at 05:29:54PM -0300, JoaoBR wrote: I also haven't read anything and got terrible caught by this 7.2 xorg thing Says it all, really. :-) you're not laughing at me aren't you? i'm afraid he might be. however, don't fret. i am surely much werse than u. u made me happy that i am not the only one. this also motivates me to change my ways. -- João A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] *--* Kayven Riese, BSCS, MS (Physiology and Biophysics) (415) 902 5513 cellular http://kayve.net Webmaster http://ChessYoga.org *--*___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Broken locale after upgrade to 6-STABEL from 5-STABLE
On Thu, 24 May 2007, Artem Kuchin wrote:
/lib/libc.so.5
I chflaged it, deleted it and made a link to
libc.so.6
this guy sounds familiar. i am really hosed right now, i can't
run a browser simultaneously, maybe i am being really stupid,
but what do you mean when you say you chflaged it? an explicit
unix command line dingy is the sort of thing that makes me happy.
After that setlocale in perl worked fine.
However, on another server, where setlocale worked
and works fine this libc.so.5 also present and causes
no problems.
What i don't understand, is how the appropriate 'so'
is selected? How freebsd known which so to load
this
libc.so.5
or this
libc.so.6
?
where it is specified?
Another question, is why setlocale in C
says that locale is set fine.
A simple proggie:
#include locale.h
#include errno.h
#include ctype.h
main(){
char *b=setlocale(LC_ALL, ru_RU.CP1251);
if (!b){
printf(FAILED! %d\n,errno);
}
else {
printf(OK: %s %d\n,b,errno);
printf(LOCALE %s\n,setlocale(LC_CTYPE,NULL));
printf(1: TO UPPER %c TO LOWER %c\n,toupper('я'),tolower('Я'));
printf(1-0: TO UPPER %c TO LOWER %c\n,toupper('Я'),tolower('я'));
printf(2: TO UPPER %c TO LOWER %c\n,toupper('r'),tolower('R'));
}
}
Does not work even when locales work on perl (toupper does not
return an upper letter for russia, but works with latin r, same
with tolower).
Am i missing something?
--
Regards,
Artem
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]
*--*
Kayven Riese, BSCS, MS (Physiology and Biophysics)
(415) 902 5513 cellular
http://kayve.net
Webmaster http://ChessYoga.org
*--*___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: xorg 7.2 start problem
On Wed, 23 May 2007, Roland Smith wrote:
On Wed, May 23, 2007 at 06:18:12PM -0300, JoaoBR wrote:
On Wednesday 23 May 2007 17:51:34 Roland Smith wrote:
On Wed, May 23, 2007 at 05:29:54PM -0300, JoaoBR wrote:
I also haven't read anything and got terrible caught by this 7.2 xorg
thing
Says it all, really. :-)
you're not laughing at me aren't you?
A little. Ignoring /usr/{ports|src}/UPDATING usually has predictable results.
Been there, done that. :-)
WOW. now i'm even HAPPIER!
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)
*--*
Kayven Riese, BSCS, MS (Physiology and Biophysics)
(415) 902 5513 cellular
http://kayve.net
Webmaster http://ChessYoga.org
*--*
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: xorg 7.2 start problem
On Wed, May 23, 2007 at 03:26:25PM -0400, Kris Kennaway wrote: As I've said a *number* of times already (and as is mentioned in the UPDATING instructions), install the x11/xorg port to obtain a complete installation. Hmm, I have the x11/xorg port, same problem could not open default font 'fixed' Oh, well. So now I have an X-less system, Don't mind so much myself, but my other family members freaked out :( They thought the shell prompt was an error message! --John -- SDF Public Access UNIX System - http://sdf.lonestar.org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
kernel panic on 6-STABLE with ipv6?
Hello,
With curiosity, today I tried to enable ipv6 in avahi-daemon.conf (I
don't really understand what avahi-daemon does, though) and start the
daemon using rc.d script, then I hit a kernel panic. I updated the
tree and build world yesterday before the trial (because I wanted
Intel HDA support, but it was another story).
# uname -a
FreeBSD elvenbow.cc.kyushu-u.ac.jp 6.2-STABLE FreeBSD 6.2-STABLE #0: Wed May 23
20:27:20 JST 2007 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/ELVENBOW amd64
The output of kgdb with stack backtrace follows:
--
# kgdb /usr/obj/usr/src/sys/ELVENBOW/kernel.debug vmcore.3
kgdb: kvm_nlist(_stopped_cpus):
kgdb: kvm_nlist(_stoppcbs):
[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 amd64-marcel-freebsd.
Unread portion of the kernel message buffer:
Fatal trap 12: page fault while in kernel mode
fault virtual address = 0xff015057d198
fault code = supervisor read data, page not present
instruction pointer = 0x8:0x80508175
stack pointer = 0x10:0xb75af7c0
frame pointer = 0x10:0xff007857d100
code segment= base 0x0, limit 0xf, type 0x1b
= DPL 0, pres 1, long 1, def32 0, gran 1
processor eflags= interrupt enabled, resume, IOPL = 0
current process = 2670 (avahi-daemon)
trap number = 12
panic: page fault
Uptime: 14m43s
Dumping 2045 MB (2 chunks)
chunk 0: 1MB (159 pages) ... ok
chunk 1: 2046MB (523567 pages) 2030 2014 1998 1982 1966 1950 1934 1918 1902
1886 1870 1854 1838 1822 1806 1790 1774 1758 1742 1726 1710 1694 1678 1662 1646
1630 1614 1598 1582 1566 1550 1534 1518 1502 1486 1470 1454 1438 1422 1406 1390
1374 1358 1342 1326 1310 1294 1278 1262 1246 1230 1214 1198 1182 1166 1150 1134
1118 1102 1086 1070 1054 1038 1022 1006 990 974 958 942 926 910 894 878 862 846
830 814 798 782 766 750 734 718 702 686 670 654 638 622 606 590 574 558 542 526
510 494 478 462 446 430 414 398 382 366 350 334 318 302 286 270 254 238 222 206
190 174 158 142 126 110 94 78 62 46 30 14
#0 doadump () at pcpu.h:172
172 pcpu.h: No such file or directory.
in pcpu.h
(kgdb) where
#0 doadump () at pcpu.h:172
#1 0x0004 in ?? ()
#2 0x8041da53 in boot (howto=260)
at /usr/src/sys/kern/kern_shutdown.c:409
#3 0x8041e056 in panic (fmt=0xff0059884980 \bJ )
at /usr/src/sys/kern/kern_shutdown.c:565
#4 0x8063ecd1 in trap_fatal (frame=0xff0059884980,
eva=18446742975690328584) at /usr/src/sys/amd64/amd64/trap.c:668
#5 0x8063f042 in trap_pfault (frame=0xb75af710, usermode=0)
at /usr/src/sys/amd64/amd64/trap.c:580
#6 0x8063f2f3 in trap (frame=
{tf_rdi = -1093868727912, tf_rsi = 3623878728, tf_rdx = -1097492606640,
tf_rcx = 671088564, tf_r8 = 3623878728, tf_r9 = 0, tf_rax = 3623878725, tf_rbx
= -1093868727912, tf_rbp = -1097492606720, tf_r10 = 0, tf_r11 = 1, tf_r12 =
-1218774912, tf_r13 = 17, tf_r14 = 0, tf_r15 = -1097492606720, tf_trapno = 12,
tf_addr = -1093868727912, tf_flags = -2142209856, tf_err = 0, tf_rip =
-2142207627, tf_cs = 8, tf_rflags = 66070, tf_rsp = -1218775088, tf_ss = 16})
at /usr/src/sys/amd64/amd64/trap.c:353
#7 0x806297bb in calltrap ()
at /usr/src/sys/amd64/amd64/exception.S:168
#8 0x80508175 in ip6_setpktopts (control=0xff007857d100,
opt=0xb75af880, stickyopt=0xff015057d198, priv=0, uproto=17)
at /usr/src/sys/netinet6/ip6_output.c:2992
#9 0x80517911 in udp6_output (in6p=0xff005bb03980,
m=0xff007853c800, addr6=0xb75af880,
control=0xff007857d100, td=0xff0059884980)
at /usr/src/sys/netinet6/udp6_output.c:170
#10 0x80519607 in udp6_send (so=0xff00529df000, flags=0,
m=0xff007853c800, addr=0xff0001031c20, control=0xff007857d100,
td=0xff0059884980) at /usr/src/sys/netinet6/udp6_usrreq.c:794
#11 0x80461f0c in sosend (so=0xff00529df000,
addr=0xff0001031c20, uio=0xb75afa70, top=0xff007853c800,
control=0xff007857d100, flags=0, td=0xff0059884980)
at /usr/src/sys/kern/uipc_socket.c:836
#12 0x80469968 in kern_sendit (td=0xff0059884980, s=16,
mp=0xb75afb30, flags=0, control=0xff007857d100, segflg=52)
at /usr/src/sys/kern/uipc_syscalls.c:772
#13 0x8046ad57 in sendit (td=0xff0059884980, s=16,
mp=0xb75afb30, flags=0) at /usr/src/sys/kern/uipc_syscalls.c:712
#14 0x8046af56 in sendmsg
