Hi All,
Sorry for late reply, i was out of work for a week.
I made wrong comment in Getpid():
Getpid() {
/* ..
/* ... */
*/
return()
}
I removed it and now it is working fine.
Thanks
--- On Mon, 1/19/09, Dag-Erling Smørgrav wrote:
From: Dag-Erling Smørgrav
Subject: Re: panic: G
On Fri, Jan 16, 2009 at 02:36:06PM -0800, Jason Evans wrote:
> Brian Fundakowski Feldman wrote:
> > Could you, and anyone else who would care to, check this out? It's a
> regression
>> fix but it also makes the code a little bit clearer. Thanks!
>>
>> Index: lib/libc/stdlib/malloc.c
>
> Why d
Ed Schouten writes:
> I guess if you break getpid() to not return 1 in the case of init(8), it
> will just say "init: already running" and quit. This causes this panic
> to occur.
Who knows? We have no idea what the OP actually did, because he didn't
bother to tell us.
DES
--
Dag-Erling Smørgr
igor krasnoselski wrote:
I'm up to build a little Wi-Fi network at my home. So I need to know, what
Wi-Fi NIC is working better under FreeBSD 7.1, from the next little list:
ZyXEL G-302 EE
D-link DWA-510
ASUS WL-138g V2
TRENDnet TEW-423PI
P.S. Digging the "7.1 Hardware Notes" on the Web gave me
igor krasnoselski writes:
> Hi world,
> I'm up to build a little Wi-Fi network at my home. So I need to know, what
> Wi-Fi NIC is working better under FreeBSD 7.1, from the next little list:
> ZyXEL G-302 EE
> D-link DWA-510
> ASUS WL-138g V2
> TRENDnet TEW-423PI
> P.S. Digging the "7.1 Hardware
Hi world,
I'm up to build a little Wi-Fi network at my home. So I need to know, what
Wi-Fi NIC is working better under FreeBSD 7.1, from the next little list:
ZyXEL G-302 EE
D-link DWA-510
ASUS WL-138g V2
TRENDnet TEW-423PI
P.S. Digging the "7.1 Hardware Notes" on the Web gave me no information a
* Garrett Cooper wrote:
> I still don't understand why adding a [C, etc] `comment' would cause
> these problems.
I guess if you break getpid() to not return 1 in the case of init(8), it
will just say "init: already running" and quit. This causes this panic
to occur.
--
Ed Schouten
WWW: http:
on 19/01/2009 14:27 Pegasus Mc Cleaft said the following:
>
> - Original Message - From: "Andriy Gapon"
[snip]
>> So, if we globally disable SMI, then the watchdog in ICH9 does indeed
>> cause a reboot. Evidently this happens after the timer expires twice
>> in row.
[snip]
>Mentioned
- Original Message -
From: "Andriy Gapon"
To: ;
Sent: Monday, January 19, 2009 12:11 PM
Subject: ich watchdog vs intel smm code
Some time earlier I reported that ichwd driver doesn't produce any
effect on my system with Intel DG33TL motherboard when watchdog timer is
allowed to ex
Some time earlier I reported that ichwd driver doesn't produce any
effect on my system with Intel DG33TL motherboard when watchdog timer is
allowed to expire.
I did some investigation and also discussed the issue with a maintainer
of Linux iTCO_wdt driver, Wim Van Sebroeck. He told me that the iss
10 matches
Mail list logo
