I have a VAIO with an AC97 soundcard. Here's the pciconf output:
pcm0@pci0:31:5: class=0x040100 card=0x80fa104d chip=0x24858086 rev=0x02
hdr=0x00
vendor = 'Intel Corporation'
device = '82801CA/CAM (ICH3-S/ICH3-M) AC'97 Audio Controller'
class= multimedia
subclass = audio
Here's the /var/
Yeah. I'm in the middle of the Mozilla code base as you probably remember,
trying to fix the problem of these bad DNS servers. I did complain to the
technical administrators for the ones that were giving me problems, but I've
only received form letter replies and they are still broken.
I also saw
>On May 31, Peter Haight wrote:
>>
>> If I link with libc_r can I use gethostbyname2() at the same time in two
>> different threads?
>
>Pardon my ignorance, but how does re-entrancy affect this? It would seem
>that you're interested in a function that doe
>You would do everyone a favour by notifying those sites that don't
>handle IPv6 DNS queries properly. In many (most) cases the sites aren't
>aware that their DNS software is broken. A quick e-mail will often see
>the problem fixed in short order. (bbc.co.uk is a recent example of
>this.)
Of cour
>In mozilla's case, it's not the FreeBSD resolver that's trying ipv6 and
>then ipv4. Mozilla does it explicitly by calling gethostbyname2 first
>with AF_INET6, and if that fails with AF_INET. You could just patch it
>to not make the first gethostbyname2 call. From a quick browse of the
>source fro
>www.vanguard.com has a broken DNS implementation.
>Find out the zone administrator via SOA record or whois and complain.
>RFC requires the behavour you saw with google.
Ok. The thing is that there are a lot of these sites. Watching the log on
the other side of my DNS server it looks like it is s
Recently mozilla has been really slow resolving some DNS queries. I tracked
this down to a call to gethostbyname2. For some addresses (e.g.
'www.vanguard.com'), gethostbyname2 with AF_INET6 will fail and takes more
than a minute. I verified this with my own short program that does nothing
but ca
I rebuilt mozilla after upgrading to 4.2 and was getting an assertion
because pthread_attr_setschedparam() was failing with a ENOTSUP. It turns
out Mozilla was trying to set the thread priority to 42 which is above the
new limit of 31 which changed a little before 4.2-RELEASE.
To patch mozilla I
8 matches
Mail list logo
