Hi!
> Am 05.04.2019 um 16:36 schrieb Warner Losh :
> What normally comes after the nvme6 line in boot? Often times it's the next
> thing after the last message that's the issue, not the last thing.
nvme7 ;-)
And I had hangs at nvme1, nvme3, … as well.
Patrick
--
punkt.de GmbH
On Fri, Apr 5, 2019 at 6:41 AM Patrick M. Hausen wrote:
> Hi all,
>
> in addition to the aborted commands every dozen of system boots or so
> (this order of magnitude) the kernel simply hangs during initialisation of
> one of the NVME devices:
>
> https://cloud.hausen.com/s/TxPTDFJwMe6sJr2
>
> Th
Hi all,
in addition to the aborted commands every dozen of system boots or so
(this order of magnitude) the kernel simply hangs during initialisation of
one of the NVME devices:
https://cloud.hausen.com/s/TxPTDFJwMe6sJr2
The particular device affected is not constant.
A power cycle fixes it, th
led: 1
The process will require 2 MiB more space.
Proceed with this action? [y/N]: y
[1/1] Installing xf86-video-intel-2.99.917.20180512...
[1/1] Extracting xf86-video-intel-2.99.917.20180512: 100%
If I do anything much different than the following, I get a black-screen
freeze, no network, no
-g -o kernel.full ...
>> > > >
>> > >
>> > > How reproducible is the crash? What previous kernel was known to work?
>> > > Can you narrow it down to a particular revision, preferably with
>> kernel
>> > > debugging enabled? (see t
usr/bin:/
> > > > sbin:/bin:/usr/sbin:/usr/bin
> > > > > make -m /usr/src/share/mk KERNEL=kernel all -DNO_MODULES_OBJ
> > > > > linking kernel.full
> > > > > ctfmerge -L VERSION -g -o kernel.full ...
> > > > >
> > > >
>
..
> > > >
> > >
> > > How reproducible is the crash? What previous kernel was known to work?
> > > Can you narrow it down to a particular revision, preferably with kernel
> > > debugging enabled? (see the end of the mail)
> > >
> >
> &g
ernel.full
> > > ctfmerge -L VERSION -g -o kernel.full ...
> > >
> >
> > How reproducible is the crash? What previous kernel was known to work?
> > Can you narrow it down to a particular revision, preferably with kernel
> > debugging enabled? (see the end of
erably with kernel
> debugging enabled? (see the end of the mail)
>
It first appeared a few days ago (forget what revision) then disappeared
the day after and reappeared yesterday. It is 100% reproducible (i.e.
clearing out /usr/obj and doing a make kernel in either single or multiuser
mode both
r revision, preferably with kernel
> debugging enabled? (see the end of the mail)
FWIW, I did not see anything approaching such a freeze, either on my
build machine or my laptop, during the just-comopleted upgrade from:
FreeBSD g1-252.catwhisker.org 11.0-STABLE FreeBSD 11.0-STABLE #209
r31
On Mon, Jan 02, 2017 at 06:57:48AM -0500, Aryeh Friedman wrote:
> FreeBSD lilith 11.0-STABLE FreeBSD 11.0-STABLE #7 r311003: Sun Jan 1
> 02:45:34 EST 2017 root@lilith:/usr/obj/usr/src/sys/GENERIC amd64
>
>
> --
> >>> stage 3.1: bui
FreeBSD lilith 11.0-STABLE FreeBSD 11.0-STABLE #7 r311003: Sun Jan 1
02:45:34 EST 2017 root@lilith:/usr/obj/usr/src/sys/GENERIC amd64
--
>>> stage 3.1: building everything
---
On Thu, Aug 27, 2015 at 11:29:28AM +0200, Johann Hugo wrote:
> It's working for me so far and I haven't seen any watchdog timeouts.
> With 10.2-RELEASE I got timeouts and lost connectivity in less that a
> minute.
>
Ok, great. Committed in r287238.
Thanks again.
> Johann
>
> On Wed, Aug 26, 20
It's working for me so far and I haven't seen any watchdog timeouts.
With 10.2-RELEASE I got timeouts and lost connectivity in less that a
minute.
Johann
On Wed, Aug 26, 2015 at 10:28 AM, Yonghyeon PYUN wrote:
> On Wed, Aug 26, 2015 at 10:06:29AM +0200, Johann Hugo wrote:
>> 10.2-RELEASE does no
On Wed, Aug 26, 2015 at 10:06:29AM +0200, Johann Hugo wrote:
> 10.2-RELEASE does not work for me. It works for a very short while and
> then it stops with "msk0 watchdog timeout" errors
>
Thanks a lot for your report. This is the first report for
msk(4) watchdog timeouts on 10.2-RELEASE.
> I'm
10.2-RELEASE does not work for me. It works for a very short while and
then it stops with "msk0 watchdog timeout" errors
I'm not sure what patch Roosevelt was talking about, but the patch in
this thread works for me:
https://lists.freebsd.org/pipermail/freebsd-stable/2015-April/082226.html
I've c
On Wed, Aug 12, 2015 at 09:44:06AM -0400, Roosevelt Littleton wrote:
> Hi,
> So, I can confirm with the attached patch. I have a working msk0 that
> hasn't failed for the past month. I considered this problem fix for me.
> Since, I have went a long time without any problems. Thanks!
I'm not sure w
On 08/12/2015 04:44 PM, Roosevelt Littleton wrote:
Hi,
So, I can confirm with the attached patch. I have a working msk0 that
hasn't failed for the past month. I considered this problem fix for me.
Since, I have went a long time without any problems. Thanks!
Roosevelt
Hi,
So, I can confirm with the attached patch. I have a working msk0 that
hasn't failed for the past month. I considered this problem fix for me.
Since, I have went a long time without any problems. Thanks!
Roosevelt
___
freebsd-stable@freebsd.org mailin
On 07/26/2015 01:40 PM, Yonghyeon PYUN wrote:
On Sat, Jul 25, 2015 at 02:08:10PM +0300, Alnis Morics wrote:
Just tried 10.2-RC1 amd64 GENERIC, and the problem seems to be gone. I
was even able to scp a 500 MB file. Could it be related to this fix in
BETA2, as mentioned in the announcement, "The
On Sat, Jul 25, 2015 at 02:08:10PM +0300, Alnis Morics wrote:
> Just tried 10.2-RC1 amd64 GENERIC, and the problem seems to be gone. I
> was even able to scp a 500 MB file. Could it be related to this fix in
> BETA2, as mentioned in the announcement, "The watchdog(4) device has
> been fixed to
n
behalf of Yonghyeon PYUN [pyu...@gmail.com]
Sent: 13 April 2015 09:13
To: Gareth Wyn Roberts
Cc: freebsd-stable@freebsd.org
Subject: Re: msk msk0 watchdog timeout freeze hang lock stop problem
On Sun, Apr 12, 2015 at 05:57:34PM +, Gareth Wyn Roberts wrote:
I've run in to problems usi
For those not subscribed to svn commit email, the code freeze for the
upcoming 10.2-RELEASE is now in effect.
The full schedule as it stands now is available here:
https://www.FreeBSD.org/releases/10.2R/schedule.html
If you are aware of an issue that affects stable/10 that does not have
a
On Wed, Apr 15, 2015 at 09:52:09PM +, Gareth Wyn Roberts wrote:
> I've inserted code to print some values which show the differences between
> specifying 4096 or 8192 for MSK_STAT_ALIGN. In both cases the status buffer
> has length 0x4000 (8x2048=16K) but the alignments are different as expe
=0
mskc0: msk_handle_events: Break #1 cons=512 csrread=519
mskc0: msk_handle_events: sd=0xfe011e23c000 sd->msk_control=0 control=0
...etc
From: owner-freebsd-sta...@freebsd.org [owner-freebsd-sta...@freebsd.org] on
behalf of Yonghyeon PYUN [pyu...@gmail.com]
Sent: 13
Hm... I patched if_msk.c with if_msk.c.rev262524.dma.diff
(attachment-001.bin) and if_mskreg.h with if_mskreg.h.rev264442.dma.diff
(attachment-002.bin), and nothing changed: scp'ing 50 MB soon got
"stalled" and ended up with "broken pipe", as it was before.
I have 10.1-RELEASE-p9 amd64
pcicon
On Sun, Apr 12, 2015 at 05:57:34PM +, Gareth Wyn Roberts wrote:
> I've run in to problems using the msk device where initially it works well
> enough to set DHCP etc. but stops/freezes as soon as any appreciable network
> traffic occurs . There are several threads describing similar symptoms
Hi!
> I've run in to problems using the msk device [...]
> I'm working on 10.1-RELEASE source, i.e. if_msk.c revision 262524 and
> if_mskreg.h revision 264442.
>
> Here's the patch to if_mskreg.h
[...]
Thanks for the suggested fix.
There are five PRs, all describe similar things:
https://bug
I've run in to problems using the msk device where initially it works well
enough to set DHCP etc. but stops/freezes as soon as any appreciable network
traffic occurs . There are several threads describing similar symptoms over the
past two years or more. I've been following several false leads
Gary Palmer [gpal...@freebsd.org] wrote:
> It used to be that ports had MAKE_JOBS_SAFE in the Makefile to mark that
> the port could be built using parallel compiles with the '-j' argument
> to make. It appears that the logic has been switched and now you have
> to mark them as MAKE_JOBS_UNSAFE to
Gary Palmer [gpal...@freebsd.org] wrote:
> It's not a compiler flag, it's a make flag. make -j n will fork off up to
> n compilers to do the build. If you just do "make buildworld" then there
> is no parallel compilation.
>
> It used to be that ports had MAKE_JOBS_SAFE in the Makefile to mark th
On 20 September 2013 11:52, Gary Palmer wrote:
> On Fri, Sep 20, 2013 at 10:49:28AM -0400, Thomas Laus wrote:
>> Gary Palmer [gpal...@freebsd.org] wrote:
>> >
>> > When building kernel & world do you use the '-j' argument to do parallel
>> > builds? AFAIK thats not done by default, but it is for
On Fri, Sep 20, 2013 at 10:49:28AM -0400, Thomas Laus wrote:
> Gary Palmer [gpal...@freebsd.org] wrote:
> >
> > When building kernel & world do you use the '-j' argument to do parallel
> > builds? AFAIK thats not done by default, but it is for some ports.
> >
> Gary:
>
> I just use the system de
Gary Palmer [gpal...@freebsd.org] wrote:
>
> When building kernel & world do you use the '-j' argument to do parallel
> builds? AFAIK thats not done by default, but it is for some ports.
>
Gary:
I just use the system defaults when building anything. If there is a
'-j' argument passed to the com
On Fri, Sep 20, 2013 at 09:12:09AM -0400, Thomas Laus wrote:
> > Tom,
> > I have had multiple D510's and now D525's that are part of my test
> > systems, all are 4GB machines and all run the latest (ie 2 days old) 9.X
> > Stable. They're faultless. I have a D510 in production serving 30
> > users
> Tom,
> I have had multiple D510's and now D525's that are part of my test
> systems, all are 4GB machines and all run the latest (ie 2 days old) 9.X
> Stable. They're faultless. I have a D510 in production serving 30
> users - yes its a 1G system running, sendmail, squid, samba as PDC.
> It's
tried both schedulers in
FreeBSD 8-Stable. I have also replaced memory, power supply and disk drives
to attempt to isolate hardware from the equation. Last evening I had a
complete
freeze when rebuilding tshark. The keyboard was dead, screen display was
frozen
and no network access. I recovered by
sutils/automounter, which is a scripting solution
>>>>>>> that generates an amd.map file based on encountered devices and devd
>>>>>>> events. The SIGHUP it sends to amd to tell it the map file was updated
>>>>>>> does not cause problems, only a -SIGK
;>>> ...
>>>>>>>>>
>>>>>>>>> I run amd through sysutils/automounter, which is a scripting solution
>>>>>>>>> that generates an amd.map file based on encountered devices and devd
>>>>>>>>
>>>> I run amd through sysutils/automounter, which is a scripting solution
> >>>>>>> that generates an amd.map file based on encountered devices and devd
> >>>>>>> events. The SIGHUP it sends to
sutils/automounter, which is a scripting solution
>>>>>>> that generates an amd.map file based on encountered devices and devd
>>>>>>> events. The SIGHUP it sends to amd to tell it the map file was updated
>>>>>>> does not cause problems, only a -SIGK
s an amd.map file based on encountered devices and devd
> >>>>> events. The SIGHUP it sends to amd to tell it the map file was updated
> >>>>> does not cause problems, only a -SIGKILL- SIGTERM may cause the freeze.
> >>>>>
> &g
to tell it the map file was updated
>>>>> does not cause problems, only a -SIGKILL- SIGTERM may cause the freeze.
>>>>>
>>>>> Nothing was mounted (by amd) during the last freeze.
>>>>>
>>>>> ...
>>>>
>>&g
On 26/07/2013 20:37, Artem Belevich wrote:
> On Fri, Jul 26, 2013 at 10:10 AM, Dominic Fandrey wrote:
>
>> Amd exhibits several very strange behaviours.
>>
>> a)
>> During the first start it writes the wrong PID into the pidfile,
>> it however still reacts to SIGTERM.
>>
>> b)
>> After starting it
On Fri, Jul 26, 2013 at 10:10 AM, Dominic Fandrey wrote:
> Amd exhibits several very strange behaviours.
>
> a)
> During the first start it writes the wrong PID into the pidfile,
> it however still reacts to SIGTERM.
>
> b)
> After starting it again, it no longer reacts to SIGTERM.
>
amd does blo
gt;>>> I run amd through sysutils/automounter, which is a scripting solution
>>>> that generates an amd.map file based on encountered devices and devd
>>>> events. The SIGHUP it sends to amd to tell it the map file was updated
>>>> does not cause problems, on
ting solution
> >> that generates an amd.map file based on encountered devices and devd
> >> events. The SIGHUP it sends to amd to tell it the map file was updated
> >> does not cause problems, only a -SIGKILL- SIGTERM may cause the freeze.
> >>
> >> Nothing
vd
>> events. The SIGHUP it sends to amd to tell it the map file was updated
>> does not cause problems, only a -SIGKILL- SIGTERM may cause the freeze.
>>
>> Nothing was mounted (by amd) during the last freeze.
>>
>> ...
>
> Are you sure that the machine
On Tue, Jul 23, 2013 at 10:43 AM, Dominic Fandrey wrote:
> > Don't use KILL or make sure that nobody tries to use amd mountpoints
> until
> > new instance starts. Manually unmounting them before killing amd may
> help.
> > Why not let amd do it itself with "/etc/rc.d/amd stop" ?
>
> That was a typ
On 22/07/2013 20:05, Artem Belevich wrote:
> On Mon, Jul 22, 2013 at 2:50 AM, Dominic Fandrey wrote:
>
>> Occasionally stopping amd freezes my system. It's a rare occurrence,
>> and I haven't found a reliable way to reproduce it.
>>
>> It's also a r
On Mon, Jul 22, 2013 at 2:50 AM, Dominic Fandrey wrote:
> Occasionally stopping amd freezes my system. It's a rare occurrence,
> and I haven't found a reliable way to reproduce it.
>
> It's also a real freeze, so there's no way to get into the debugger
> or g
g amd freezes my system. It's a rare occurrence,
>>>> and I haven't found a reliable way to reproduce it.
>>>>
>>>> It's also a real freeze, so there's no way to get into the debugger
>>>> or grab a core dump. I only can perform the 4 secon
reproduce it.
It's also a real freeze, so there's no way to get into the debugger
or grab a core dump. I only can perform the 4 seconds hard shutdown to
revive the system.
I run amd through sysutils/automounter, which is a scripting solution
that generates an amd.map file based on enc
On 22/07/2013 12:07, Konstantin Belousov wrote:
> On Mon, Jul 22, 2013 at 11:50:24AM +0200, Dominic Fandrey wrote:
>> Occasionally stopping amd freezes my system. It's a rare occurrence,
>> and I haven't found a reliable way to reproduce it.
>>
>> It's al
On Mon, Jul 22, 2013 at 11:50:24AM +0200, Dominic Fandrey wrote:
> Occasionally stopping amd freezes my system. It's a rare occurrence,
> and I haven't found a reliable way to reproduce it.
>
> It's also a real freeze, so there's no way to get into the debugger
&
Occasionally stopping amd freezes my system. It's a rare occurrence,
and I haven't found a reliable way to reproduce it.
It's also a real freeze, so there's no way to get into the debugger
or grab a core dump. I only can perform the 4 seconds hard shutdown to
revive the system
This is a really old thread i thought i would bring back to life. I have heard
that the flash card vendor has fessed up to a problem and said there is a
software fix they can create. So far i have no ETA on when that is going to
happen and for the record i don't think i will.
Oh well... here c
thing in /var/log/messages to indicate a problem. Output of
pciconf -lv and uname -a are at:
http://www.eskimo.com/~joji/wisdom/
Anybody else experiencing similar freeze ups with 8.3 or 9.0 while using
firefox?
Since Firefox uses all kinds of GPU stuff nowadays. Is it possible it
locks up
ate a problem. Output of
pciconf -lv and uname -a are at:
http://www.eskimo.com/~joji/wisdom/
Anybody else experiencing similar freeze ups with 8.3 or 9.0 while using
firefox?
Since Firefox uses all kinds of GPU stuff nowadays. Is it possible it
locks up your graphics card?
I suggest trying to tu
ack is by pressing and holding down the power
> > button.
> >
> > The problem seems similar to: kern/163145
> >
> >
> > There is nothing in /var/log/messages to indicate a problem. Output of
> > pciconf -lv and uname -a are at:
> >
> > http://
gt;
>
> There is nothing in /var/log/messages to indicate a problem. Output of
> pciconf -lv and uname -a are at:
>
> http://www.eskimo.com/~joji/wisdom/
>
> Anybody else experiencing similar freeze ups with 8.3 or 9.0 while using
> firefox?
>
I use 8.3 and Firefox without
http://www.eskimo.com/~joji/wisdom/
Anybody else experiencing similar freeze ups with 8.3 or 9.0 while using
firefox?
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to &qu
2012 7:57 PM
Subject: Re: 6.2-Release ..ish.. CF + ata == freeze?
2 of the 3 cf cards are very new, like less then 6 months old.
I think around 65-70 percent is in use. This number doesn't change unless the
user dumps data in a home dir, which isn't the case so far.
You are correct that
rry from T-Mobile
-Original Message-
From: Jeremy Chadwick
Date: Mon, 13 Feb 2012 21:18:28
To: john fleming
Cc: freebsd-stable@freebsd.org
Subject: Re: 6.2-Release ..ish.. CF + ata == freeze?
On Mon, Feb 13, 2012 at 08:43:08PM -0800, john fleming wrote:
> Just thought i would post over he
On Tue, 2012-02-14 at 00:12 -0500, Jason Hellenthal wrote:
>
> On Mon, Feb 13, 2012 at 08:43:08PM -0800, john fleming wrote:
> > Just thought i would post over here as i'm not getting a warm fuzzy from
> > checkpoint about being able to find the root cause of an issue. I have a
> > large install
On Mon, Feb 13, 2012 at 11:38:06PM -0600, Adam Vande More wrote:
> On Mon, Feb 13, 2012 at 10:43 PM, john fleming wrote:
>
> > Just thought i would post over here as i'm not getting a warm fuzzy from
> > checkpoint about being able to find the root cause of an issue. I have a
> > large install b
On Mon, Feb 13, 2012 at 10:43 PM, john fleming wrote:
> Just thought i would post over here as i'm not getting a warm fuzzy from
> checkpoint about being able to find the root cause of an issue. I have a
> large install base of IPSO checkpoint firewalls, which are based on FreeBSD
> 6.2. I've had
I can't seem to replicate it at all. I've seen it happen on 3 different IPSO
boxes so far. The last machine it happened on is maybe 4 months old. Basically
on all 3 machines once rebooted the problem doesn't come back. Checkpoint so
far is telling me its a known issue and they don't know what th
On Mon, Feb 13, 2012 at 08:43:08PM -0800, john fleming wrote:
> Just thought i would post over here as i'm not getting a warm fuzzy from
> checkpoint about being able to find the root cause of an issue. I have a
> large install base of IPSO checkpoint firewalls, which are based on FreeBSD
> 6.2.
On Mon, Feb 13, 2012 at 08:43:08PM -0800, john fleming wrote:
> Just thought i would post over here as i'm not getting a warm fuzzy from
> checkpoint about being able to find the root cause of an issue. I have a
> large install base of IPSO checkpoint firewalls, which are based on FreeBSD
> 6.
Just thought i would post over here as i'm not getting a warm fuzzy from
checkpoint about being able to find the root cause of an issue. I have a large
install base of IPSO checkpoint firewalls, which are based on FreeBSD 6.2. I've
had 3 firewalls hang basically the same way, with something that
On 26 October 2011 23:31, Subbsd wrote:
> Hi
>
> I get easy reproducible a hang-up servers that use the file-based
> swap file after swapoff / swapon procedure (in this case, some of the
> data must be swapped). For example:
>
> 1) dd if=/dev/zero of=/usr/swp1 bs=1m count=100
> 2) mdconfig -a -t
Hi
I get easy reproducible a hang-up servers that use the file-based
swap file after swapoff / swapon procedure (in this case, some of the
data must be swapped). For example:
1) dd if=/dev/zero of=/usr/swp1 bs=1m count=100
2) mdconfig -a -t vnode -f /usr/swp1
3) swapon /dev/md0
4) begin to alloc
On Fri, Oct 07, 2011 at 11:20:28AM +0200, Erwin Lansing wrote:
> In preparation for 9.0 the ports tree will be in feature freeze
> after release candidate 2 (RC2)is released, currently planned for
> October 17.
>
Depending on your timezone, October 17 has come and gone and the ports
Just on case anyone's not on ports@:
-- Forwarded message --
From: "Chris Rees"
Date: 8 Oct 2011 10:30
Subject: Re: [HEADSUP]: ports feature freeze starts soon
To: "Thomas Mueller"
Cc: , "Erwin Lansing"
On 8 October 2011 10:22, Thomas M
In preparation for 9.0 the ports tree will be in feature freeze
after release candidate 1 (RC2)is released, currently planned for
October 17.
If you have any commits with high impact planned, get them in the tree
before then and if they require an experimental build, have a request
for one in
On Thu, Sep 15, 2011 at 12:13 AM, Dennis Koegel wrote:
> I'm not aware how licensing issues play in here, but apart from that, it
> should be easy to patch this into base. (I was already half-way there
> yesterday and I think I could work up a patch against HEAD and 8.x).
I won't worry about fili
On Wed, Sep 14, 2011 at 07:26:20PM -0700, Jeremy Chadwick wrote:
> I'm actually very surprised to hear there's an official FreeBSD driver
> on Adaptec's site that's actually intended for FreeBSD 8.x.
As far as I can tell from the source, it's the very same driver (same
source code and copyright no
ped. ?I haven't had a single freeze since using the new
> > code. ?The newest driver from the website has source code with it, so
> > it shouldn't be that big of a deal to incorporate it into the base
> > system. ? ?I emailed the authors of the aac driver (Mike Smith and
On 15 September 2011 00:38, Elliot Finley wrote:
> I was having the exact same problem using an Adaptec 52445. After
> downloading and using the latest driver from the adaptec website, the
> problems stopped. I haven't had a single freeze since using the new
> code. The newes
I was having the exact same problem using an Adaptec 52445. After
downloading and using the latest driver from the adaptec website, the
problems stopped. I haven't had a single freeze since using the new
code. The newest driver from the website has source code with it, so
it shouldn'
Cheers,
we have a reproducible system freeze due to Adaptec driver (aac) timeouts:
Sep 3 05:26:44 foo kernel: aac0: COMMAND 0xff80005ae4c0 (TYPE 502) TIMEOUT
AFTER 129 SECONDS
Sep 3 05:26:44 foo kernel: aac0: COMMAND 0xff80005ac0e0 (TYPE 502) TIMEOUT
AFTER 129 SECONDS
Sep 3 05:26:44
l.
After upgrading the zfsboot just to be able to upgrade the pool to v15,
the server don't boot anymore.
It is a remote server, so I reproduce this config under VirtualBox. The
boot freeze after zfsboot displaying "-".
I grab a old zfsboot from another server running 8.1-STAB
On Sat, Aug 21, 2010 at 11:09:04PM +0200, Stefan Bethke wrote:
> Am 21.08.2010 um 23:02 schrieb Andriy Gapon:
>
> > on 21/08/2010 23:33 Stefan Bethke said the following:
> >> Hi,
> >>
> >> somewhat foolishly, I activated watchdogd and ichwd on a remote box, and
> >> while testing it (by suspendin
gt;
> Dont know about that particular MB implementation, but I have a number of
> various ICH7 based boards where ichwd works as expected. The freeze could
> some something as simple as the box is waiting for keyboard input at the BIOS
> prompt, or the BIOS option after a watchdog
based boards where ichwd works as
expected. The freeze could some something as simple as the box is
waiting for keyboard input at the BIOS prompt, or the BIOS option
after a watchdog reset is to power off However, I have only seen
that option in later boards.
--
Am 21.08.2010 um 23:02 schrieb Andriy Gapon:
> on 21/08/2010 23:33 Stefan Bethke said the following:
>> Hi,
>>
>> somewhat foolishly, I activated watchdogd and ichwd on a remote box, and
>> while testing it (by suspending watchdogd), apparently the watchdog
>> triggered. But instead of resetting
on 21/08/2010 23:33 Stefan Bethke said the following:
> Hi,
>
> somewhat foolishly, I activated watchdogd and ichwd on a remote box, and
> while testing it (by suspending watchdogd), apparently the watchdog
> triggered. But instead of resetting, the machine does not react anymore on
> the serial
Hi,
somewhat foolishly, I activated watchdogd and ichwd on a remote box, and while
testing it (by suspending watchdogd), apparently the watchdog triggered. But
instead of resetting, the machine does not react anymore on the serial console.
I will have to wait until Monday to get physical acce
On Fri, 18 Jun 2010 14:10:28 +0200
Erwin Lansing wrote:
> In preparation for 8.1-RELEASE, the ports tree is now in feature
> freeze.
>
> Normal upgrade, new ports, and changes that only affect other branches
> are allowed without prior approval but with the extra Feature safe:
&
In preparation for 8.1-RELEASE, the ports tree is now in feature freeze.
Normal upgrade, new ports, and changes that only affect other branches
are allowed without prior approval but with the extra Feature safe: yes
tag in the commit message. Any commit that is sweeping, i.e. touches a
large
On Tue, Jun 08, 2010 at 02:20:53PM -0400, FreeBSD portmgr secretary wrote:
> In preparation for 8.1-RELEASE, the ports tree will be in feature freeze
> after release candidate 1 (RC1) is released, currently planned for June 11.
As you may have noticed, RC1 has not been released as yet, b
In preparation for 8.1-RELEASE, the ports tree will be in feature freeze
after release candidate 1 (RC1) is released, currently planned for June 11.
If you have any commits with high impact planned, get them in the tree
before then and if they require an experimental build, have a request for
one
On Mon, May 17, 2010 at 5:29 PM, Thomas Abthorpe wrote:
> The next wave of the challenge, fear, there is one more already
> composed to be released with 8.1!
>
> --
>
> Give Freeze a chance
> with apologies to John Lennon et al
>
> Ev'rybody's talkin
The next wave of the challenge, fear, there is one more already
composed to be released with 8.1!
--
Give Freeze a chance
with apologies to John Lennon et al
Ev'rybody's talkin' 'bout
portism, srcism, docism, cvsism, svnism, tagism
This-ism, that-ism, ism ism ism
All w
On Wed, Apr 14, 2010 at 3:31 AM, Demelier David
wrote:
> Hi,
>
> I'm so sad because FreeBSD is the one which can runs almost perfectly
> on
> my laptop. But it freezes. Sometime I just do anything and I want to
> click on a link in firefox, or open a t
irefox, or open a terminal and then freeze.
>
> Sounds like a problem with the X graphics driver.. when it next
> happens, can you press Alt+F1 or Ctrl+Alt+F1 to get back to a text console?
>
> You might like to try upgrading your version of X to a newer version.
>
> - Andre
Demelier David wrote:
I'm so sad because FreeBSD is the one which can runs almost perfectly on
my laptop. But it freezes. Sometime I just do anything and I want to
click on a link in firefox, or open a terminal and then freeze.
Sounds like a problem with the X gra
Hi,
I'm so sad because FreeBSD is the one which can runs almost perfectly on
my laptop. But it freezes. Sometime I just do anything and I want to
click on a link in firefox, or open a terminal and then freeze.
There is no messages, no reboot nothing. Can&#
On 3/17/10, Mathias Sogorski wrote:
> Hello!
> I am running 8.0-RELEASE on a notebook with the Intel 3945 WiFi. I usually
> start wpa_supplicant [...]& on a terminal when entering gnome followed by
> the dhcpcd call to use the WiFi connection. After having finished work and
> closing the terminal
1 - 100 of 420 matches
Mail list logo
