-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 2010/08/27 06:34, John Baldwin wrote:
> On Thursday, August 26, 2010 8:50:01 pm Xin LI wrote:
>> Hi,
>>
>> The attached patch changes FreeBSD/x86 back to FreeBSD/i386 on i386 and
>> FreeBSD/amd64 on amd64.
>>
>> Comments welcome! I'll commit it i
on 30/08/2010 20:18 Mike Tancsa said the following:
> At 12:51 PM 8/30/2010, Olivier Smedts wrote:
>
>> By any chance, is it disabled in BIOS ?
>
> Hi,
> There are a couple of options in the BIOS. There is a "reboot the box if the
> bios does not post within 6min" as well as "Fire the watchdog if
On Mon, 30 Aug 2010 13:36:03 -0400
Boris Kochergin wrote:
> Steve Kargl wrote:
> > I know that several libraries in FreeBSD
> > uses symbol versioning. In looking through
> > src/ I was unable to determine whether
> > symbol versioning is used on libgcc. Any
> > guidance would be appreciated.
At 02:47 PM 8/30/2010, Xin LI wrote:
My guess is that your motherboard provided another watchdog (like
Winbond based super I/O chips) which requires a driver, you can try this
one if you wish:
http://people.freebsd.org/~delphij/for_review/winbondwd/
I've no idea about your ichwd issue
On Mon, Aug 30, 2010 at 02:51:16PM -0400, Alexander Kabaev wrote:
> On Mon, 30 Aug 2010 13:36:03 -0400
> Boris Kochergin wrote:
>
> > Steve Kargl wrote:
> > > I know that several libraries in FreeBSD
> > > uses symbol versioning. In looking through
> > > src/ I was unable to determine whether
>
Alexander Kabaev wrote:
On Mon, 30 Aug 2010 13:36:03 -0400
Boris Kochergin wrote:
Steve Kargl wrote:
I know that several libraries in FreeBSD
uses symbol versioning. In looking through
src/ I was unable to determine whether
symbol versioning is used on libgcc. Any
guidance would b
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi, Mike,
On 2010/08/30 10:18, Mike Tancsa wrote:
> At 12:51 PM 8/30/2010, Olivier Smedts wrote:
>
>> By any chance, is it disabled in BIOS ?
>
> Hi,
> There are a couple of options in the BIOS. There is a "reboot the box if
> the bios does not po
Steve Kargl wrote:
I know that several libraries in FreeBSD
uses symbol versioning. In looking through
src/ I was unable to determine whether
symbol versioning is used on libgcc. Any
guidance would be appreciated.
I don't think it is. I haven't poked at any sources, but there are no
FB
On Mon, Aug 30, 2010 at 08:43:40PM +0300, Andriy Gapon wrote:
> on 30/08/2010 20:32 Steve Kargl said the following:
> > I know that several libraries in FreeBSD
> > uses symbol versioning. In looking through
> > src/ I was unable to determine whether
> > symbol versioning is used on libgcc. Any
on 30/08/2010 20:32 Steve Kargl said the following:
> I know that several libraries in FreeBSD
> uses symbol versioning. In looking through
> src/ I was unable to determine whether
> symbol versioning is used on libgcc. Any
> guidance would be appreciated.
Check out output of e.g. objdump -T /u
I know that several libraries in FreeBSD
uses symbol versioning. In looking through
src/ I was unable to determine whether
symbol versioning is used on libgcc. Any
guidance would be appreciated.
--
Steve
___
freebsd-current@freebsd.org mailing list
h
At 12:51 PM 8/30/2010, Olivier Smedts wrote:
By any chance, is it disabled in BIOS ?
Hi,
There are a couple of options in the BIOS. There is a "reboot the box
if the bios does not post within 6min" as well as "Fire the watchdog
if the dog has not been patted after 5,10 or 15min after the BIO
2010/8/30 Mike Tancsa :
> Hi Jack,
> I was trying to see if your recent commits for the ichwd IDs now work
> with the integrated watchdog for my i5 boards, but no luck.
>
> ichsmb0: port 0x3000-0x301f mem
> 0xb1b23000-0xb1b230ff irq 18 at device 31.3 on pci0
> ichsmb0: [ITHREAD]
> smbus0:
on 29/08/2010 12:25 Andriy Gapon said the following:
> The patch is substantially based on the Junk-uk's patch, but with some changes
I several times mistyped Jung-uk's name, my sincere apologies.
Probably should have used jkim instead :)
Thanks to rdivacky for pointing this out to me.
--
Andriy
Hi Jack,
I was trying to see if your recent commits for the ichwd IDs
now work with the integrated watchdog for my i5 boards, but no luck.
ichsmb0: port 0x3000-0x301f mem
0xb1b23000-0xb1b230ff irq 18 at device 31.3 on pci0
ichsmb0: [ITHREAD]
smbus0: on ichsmb0
ichwd0: on isa0
ichwd
Hi All,
i`ve big problems on my sparc64 FIRE 240 with bge BCM5704 interfeces
i upgrade my system from 8.0 to 8.1 and the problems have to begin
on 8.0 work all fine.
if i create some traffic about 10Mbits i see in dmesg this message:
bge0: watchdog timeout -- resetting
bge0: link state chang
on 30/08/2010 12:15 pluknet said the following:
> On 29 August 2010 13:25, Andriy Gapon wrote:
>>
>> [Reposted from stable@; edited]
>>
>> The below patch is against sources in FreeBSD tree, it should be applied
>> either to sys/amd64/amd64/mp_machdep.c or sys/i386/i386/mp_machdep.c
>> depending
YAMAMOTO, Taku wrote:
> On Mon, 30 Aug 2010 13:07:38 +0300
> Alexander Motin wrote:
>> Gary Jennejohn wrote:
> (snip)
>>> So, what else did you do to reduce interrupts so much?
>>>
>>> Ah, I think I see it now. My desktop has only C1 enabled. Is that it?
>>> Unfortunately, it appears that only C
On Mon, 30 Aug 2010 13:07:38 +0300
Alexander Motin wrote:
> Gary Jennejohn wrote:
(snip)
> > So, what else did you do to reduce interrupts so much?
> >
> > Ah, I think I see it now. My desktop has only C1 enabled. Is that it?
> > Unfortunately, it appears that only C1 is supported :(
>
> Yes,
Gary Jennejohn wrote:
> On Mon, 30 Aug 2010 13:07:38 +0300
> Alexander Motin wrote:
>> Gary Jennejohn wrote:
>>> Ah, I think I see it now. My desktop has only C1 enabled. Is that it?
>>> Unfortunately, it appears that only C1 is supported :(
>> Yes, as I have said, at this moment empty ticks ski
On Mon, 30 Aug 2010 13:07:38 +0300
Alexander Motin wrote:
> Gary Jennejohn wrote:
> > Hmm. I applied your patches and am now running the new kernel. But I
> > only installed the new kernel and didn't do make buildworld installworld.
> >
> > Mu systat -vm 1 doesn't look anything like yours. I'
Gary Jennejohn wrote:
> Hmm. I applied your patches and am now running the new kernel. But I
> only installed the new kernel and didn't do make buildworld installworld.
>
> Mu systat -vm 1 doesn't look anything like yours. I'm seeing about 2300
> interrupts per second and most of those are comi
On 29 August 2010 13:25, Andriy Gapon wrote:
>
> [Reposted from stable@; edited]
>
> The below patch is against sources in FreeBSD tree, it should be applied
> either to sys/amd64/amd64/mp_machdep.c or sys/i386/i386/mp_machdep.c depending
> on the desired architecture:
> http://people.freebsd.org/
On Sun, 29 Aug 2010 16:10:00 +0300
Alexander Motin wrote:
> I have actively tested this code for a few days on my amd64 Core2Duo
> laptop and i386 Core-i5 desktop system. With C2/C3 states enabled
> systems experience only about 100-150 interrupts per second, having HZ
> set to 1000. These events
Brandon Gooch wrote:
> One thing I see:
>
> Where is *frame pointing to? It isn't initialized in the function, so...
Thanks! Fixed. Patch updated.
> Also, for those of us testing, should we "reset" our timer settings
> back to defaults and work from there[1] (meaning, should we be futzing
> arou
25 matches
Mail list logo
