to a VM.
>>
>> One of the first things I do is a 'portsnap fetch extract'. As soon as
>> the extract starts it produces a 'lock order reversal' message with a
>> KDB stack backtrace, but then proceeds successfully to verify the
>> integ
on as
> the extract starts it produces a 'lock order reversal' message with a KDB
> stack backtrace, but then proceeds successfully to verify the integrity
> and install the ports tree.
>
> Should I worry?
Yes, you should worry ;-)
Worry you didn't realise:
El 01/06/2013 15:44, "Walter Hurry" escribió:
>
> I'm installing FreeBSD10 (head; snapshot from 30 May 2013) into a VM.
>
> One of the first things I do is a 'portsnap fetch extract'. As soon as
> the extract starts it produces a 'lock order revers
I'm installing FreeBSD10 (head; snapshot from 30 May 2013) into a VM.
One of the first things I do is a 'portsnap fetch extract'. As soon as
the extract starts it produces a 'lock order reversal' message with a KDB
stack backtrace, but then proceeds successfully to
Hello all,
Is there any way for a process in user space to try to trigger
a SCSI LUN reservation in FreeBSD?
This would be a very useful thing to have when using a multi-port
storage device which can be simultaneously connected to multiple
systems.
--jau
www:user, so
apache can't display them.
Is there a way to "lock" a directory such that all files created in that
directory are owned by the directory owner? If not, I'll have to script
something to change perms after uploads.
There is the suiddir option, see mount(8) a
r user (www) to be the owner of all directories and
> files.
>
> Meanwhile, the site owners want to be able to update and add files to the
> site. When they update files everything is fine. When they upload new
> files, the ownership of the file is user:user instead of www:user, so
> apac
ners want to be able to update and add files to the
site. When they update files everything is fine. When they upload new
files, the ownership of the file is user:user instead of www:user, so
apache can't display them.
Is there a way to "lock" a directory such that all files c
On Fri, 2 Dec 2011 01:23:19 +0100, Patrick Lamaiziere wrote:
> I use Xfce 4.8, is there a way to lock the session when the screen goes
> to sleep?
I think you can install the port "xscreensaver" which
integrates well with Xfce. At least it did the last
time I did look at it. :-)
Hello,
I use Xfce 4.8, is there a way to lock the session when the screen goes
to sleep?
Thanks, regards.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to
That looks like LOR #261, known not be a problem.
[ http://ipv4.sources.zabbadoz.net/freebsd/lor.html ]
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-q
Hi all,
I'm seeing weird messages at dmesg saying someting about "lock order
reversal" (see below) on my FreeBSD 9.0 beta 3.
I think this has something to do with the filesystem, so I'm a little
bit worried. Does anybody know if this is a known bug? (If so, how do
you know
6
drm0: on vgapci0
We've been talking about ATI lockups on the forums:
http://forums.freebsd.org/showthread.php?t=25540
It's mystifying to me, since I haven't seen the lockups at all.
Thanks for the heads up, replied to the thread there, and will here too.
Switching to XAA fixe
On Mon, 15 Aug 2011, Jimmie James wrote:
I just noticed this, but I'm pretty sure it's a result of the last ATI driver
update,
FreeBSD 8.2-STABLE #0: Sun Jun 26 08:42:45 EDT 2011
xf86-video-ati-6.14.2 + libreoffice-3.3.3_2 + xorg-7.5.1 = hard lockup,
keyboard LEDs work for a bit, can't chang
I just noticed this, but I'm pretty sure it's a result of the last ATI
driver update,
FreeBSD 8.2-STABLE #0: Sun Jun 26 08:42:45 EDT 2011
xf86-video-ati-6.14.2 + libreoffice-3.3.3_2 + xorg-7.5.1 = hard lockup,
keyboard LEDs work for a bit, can't change
to a console, kill X. ssh'ing in, running
On Apr 18, 2011, at 12:18 PM, Steven Friedrich wrote:
> I tried searching the archives, but didn't get hits.
>
> Goggle hits revealed little info.
>
> Unable to find an appropriate lock to guard the shared cache. This *should*
> be essentially impossible
Does th
I tried searching the archives, but didn't get hits.
Goggle hits revealed little info.
Unable to find an appropriate lock to guard the shared cache. This *should*
be essentially impossible
--
System Name: doris.StevenFriedrich.org
Window Manager(s): kde4-4.6.2
X Window S
x27;
/usr/src/sys/dev/usb/controller/usb_controller.c:434: warning: nested
extern declaration of 'PI_SWI'
I'm feeding "fwcontrol -u 1 -S /dev/stdin" from a pipe. The write()
to the pipe took over a second. Perhaps connected to the lock
contention
of over a second? T
On Thursday 13 January 2011 21:28:15 dieter...@engineer.com wrote:
> I suspect that I have a problem with lock/mutex contention.
> Reading from a USB disk appears to lock out the firewire driver
> for too long, causing data transfer (writing to firewire bus) to fail
> with EAGAIN. O
I suspect that I have a problem with lock/mutex contention.
Reading from a USB disk appears to lock out the firewire driver
for too long, causing data transfer (writing to firewire bus) to fail
with EAGAIN. Once it fails it does not recover.
kernel: fwohci1: IT DMA underrun (0x40308011) (stat
On Fri, 11 Dec 2009 23:58:05 -0800 Yuri wrote:
> I guess that's a side effect of /compat/linux not being owned by root.
Yes, you've found the root of the problem. Chown it to root:wheel and
all should be fine.
--
WBR, bsam
___
freebsd-questions@freebs
Boris Samorodov wrote:
That's possible only if you are root. That's the most essential info.
Please, annouce it everytime you have any error at the very beginning
of an e-mail with capital letters.
Never work as root. Never-never work as root under X.
I don't work as root. /compat/linux di
On Fri, 11 Dec 2009 15:17:19 -0800 Yuri wrote:
> Now I found who creates /compat/linux/home. It's skype. After I delete
> /compat/linux/home and relaunch skype it recreates it.
That's possible only if you are root. That's the most essential info.
Please, annouce it everytime you have any error at
Boris Samorodov wrote:
Please show me how can I repeat that case. Or at least show
# ls -l /compat/linux
The problem is actually a bug (?) in googleearth, that it leaves the
lock file when it finishes ungracefully, and after it is restarted it
complains about this file without
On Fri, 11 Dec 2009 11:34:51 -0800 Yuri wrote:
> Boris Samorodov wrote:
> > ...and remove /compat/linux/home if it exists.
> You should make sure that installer doesn't create /compat/linux/home.
> Because I never created it myself, must have been installer.
Please show me how can I repeat that c
Boris Samorodov wrote:
...and remove /compat/linux/home if it exists.
You should make sure that installer doesn't create /compat/linux/home.
Because I never created it myself, must have been installer.
Yuri
___
freebsd-questions@freebsd.org maili
On Fri, 11 Dec 2009 06:44:26 + Matthew Seaman wrote:
> Yuri wrote:
> > Glen Barber wrote:
> >>
> >> Remove the file? Or rename it?
> >
> > I wouldn't ask this question if it was that easy.
> > There is even no such directory: /home/yuri/.googleearth
> Check /compat/linux/home/yuri/
...and re
Yuri wrote:
Glen Barber wrote:
Remove the file? Or rename it?
I wouldn't ask this question if it was that easy.
There is even no such directory: /home/yuri/.googleearth
Check /compat/linux/home/yuri/
Cheers,
Matthew
--
Dr Matthew J Seaman MA, D.Phil.
Glen Barber wrote:
Have you tried creating the directory?
Creating it doesn't help.
But I solved the problem: when it talks about /home/yuri/~.googleearth
it actually means /compat/linux/home/yuri/.googleearth/
Deleting file there fixes the problem.
I guess it's a good idea to have a lin
On Thu, Dec 10, 2009 at 8:46 PM, Yuri wrote:
> Glen Barber wrote:
>>
>> Remove the file? Or rename it?
>>
>
>
> I wouldn't ask this question if it was that easy.
> There is even no such directory: /home/yuri/.googleearth
Could you provide possibly important information such as this in
future que
Glen Barber wrote:
Remove the file? Or rename it?
I wouldn't ask this question if it was that easy.
There is even no such directory: /home/yuri/.googleearth
Yuri
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/l
On Thu, Dec 10, 2009 at 8:39 PM, Yuri wrote:
> Hi,
>
> I am getting this fatal error:
> Unable to create symlink for lock
> '/home/yuri/.googleearth/instance-running-lock'. File exists.
>
Remove the file? Or rename it?
--
Glen Barber
___
Hi,
I am getting this fatal error:
Unable to create symlink for lock
'/home/yuri/.googleearth/instance-running-lock'. File exists.
google-earth-5.1.3509.4636
8.0-STABLE
Thanks,
Yuri
___
freebsd-questions@freebsd.org mailing
older FreeBSD release.
-Original Message-
From: Hans Petter Selasky [mailto:hsela...@c2i.net]
Sent: Wednesday, November 18, 2009 3:14 AM
To: freebsd-...@freebsd.org
Cc: Guojun Jin; freebsd-sta...@freebsd.org; questi...@freebsd.org
Subject: Re: 8.0-RC3 USB lock up on mounting two
Guojun Jin
> Sent: Tue 11/17/2009 11:05 PM
> To: freebsd-sta...@freebsd.org
> Cc: questi...@freebsd.org; freebsd-...@freebsd.org
> Subject: 8.0-RC3 USB lock up on mounting two partitions from one USB drive
>
> When mounting two partitions from a USB dirve, it can cause the drive
> access l
When mounting two partitions from a USB dirve, it can cause the drive access
lock up for a long time.
Details:
Terminal 1 --
term1# mount /dev/da0s3d /mnt
term1# cd /mnt ; rm -fr *
when rm starts, go to terminal 2 and do:
term2# mount /dev/da0s3e /dist ### this will hanging for a long time
dump -0f - /home | restore -rf -
105 23:27 history 15
-Original Message-
From: Guojun Jin
Sent: Tue 11/17/2009 11:05 PM
To: freebsd-sta...@freebsd.org
Cc: questi...@freebsd.org; freebsd-...@freebsd.org
Subject: 8.0-RC3 USB lock up on mounting two partitions from one USB drive
On Thu, Aug 20, 2009 at 2:08 PM, Peter Cornelius wrote:
> Hi,
>
> Are these lock order reversals reported any reason for preoccupation and/or
> should I report elsewhere?
>
> The kernel I just built does not boot at all, so I don´t know whether these
> are a closed issue a
Hi,
Are these lock order reversals reported any reason for preoccupation and/or
should I report elsewhere?
The kernel I just built does not boot at all, so I don´t know whether these are
a closed issue already. I´m off for a couple of days and will retry then.
Thanks & regards,
P
t; >> On ia64 8.0-beta1 SMP, running bsdstats-5.4_2,
> > >> I get this error:
> > >>
> > >> # /usr/local/etc/periodic/monthly/300.statistics
> > >> /usr/src/lib/bind/isc/../../../contrib/bind9/lib/isc/task.c:1023: fatal
> > >> error: RUNTI
t; >>
> >> # /usr/local/etc/periodic/monthly/300.statistics
> >> /usr/src/lib/bind/isc/../../../contrib/bind9/lib/isc/task.c:1023: fatal
> >> error: RUNTIME_CHECK(((pthread_mutex_destroy(((&manager->lock))) == 0) ?
> >> 0
> >>
> >> :
odic/monthly/300.statistics
>> /usr/src/lib/bind/isc/../../../contrib/bind9/lib/isc/task.c:1023: fatal
>> error: RUNTIME_CHECK(((pthread_mutex_destroy(((&manager->lock))) == 0) ? 0
>> : 34) == 0) failed
>
> That error from bind,
>
>> [:1: unexpected
ror: RUNTIME_CHECK(((pthread_mutex_destroy(((&manager->lock))) == 0) ? 0
> : 34) == 0) failed
That error from bind,
> [:1: unexpected operator
Is not handled gracefully in the bsdstats script.
The annoyance is that ISC Bind finds it not useful to print errno, which is
what you'd need
On ia64 8.0-beta1 SMP, running bsdstats-5.4_2,
I get this error:
# /usr/local/etc/periodic/monthly/300.statistics
/usr/src/lib/bind/isc/../../../contrib/bind9/lib/isc/task.c:1023: fatal error:
RUNTIME_CHECK(((pthread_mutex_destroy(((&manager->lock))) == 0) ? 0 : 34) == 0)
failed
[:
On Wednesday 15 July 2009 01:20:19 Frederique Rijsdijk wrote:
> I guess I'll look into the bluetooth thing. That looks quite doable.
If you can spare the time, I'd appreciate write-up of how you got it working
on FreeBSD as it's the first bluetooth application that seems worthwhile to
me.
I als
Chad Perrin wrote:
Does /usr/ports/x11/xscreensaver.app do this? It almost certainly
requires the GNUStep framework as a dependency, but you may find a number
of old "friends" (applications you liked) are available for that
framework, in varying states of faithfulness to what you remember. If
y
screensaver applications since, as it's pretty simple. They just had a
> > facility where moving the mouse cursor to one corner of the screen and
> > leaving it still for a few seconds would cause the screen saver / screen
> > lock to come on straight away.
> KDE 3.5 p
y just had a facility where
> moving the mouse cursor to one corner of the screen and leaving it still
> for a few seconds would cause the screen saver / screen lock to come on
> straight away.
>
> Conversely you could designate another corner of the screen as "don't tu
d a facility where
> moving the mouse cursor to one corner of the screen and leaving it still
> for a few seconds would cause the screen saver / screen lock to come on
> straight away.
>
> Conversely you could designate another corner of the screen as "don't turn
> o
facility where
> moving the mouse cursor to one corner of the screen and leaving it still
> for a few seconds would cause the screen saver / screen lock to come on
> straight away.
>
> Conversely you could designate another corner of the screen as "don't turn
> on s
Chad Perrin wrote:
On Tue, Jul 14, 2009 at 05:32:01PM +0200, Frederique Rijsdijk wrote:
Hi,
I'm looking for a way to automaticaly lock my X session when I leave my
desk. Probably just using 'xlockmore -mode blank' or such. But how to
detect?
Why does it have to be automatic?
Hi all,
Frederique Rijsdijk wrote:
> I'm looking for a way to automaticaly lock my X session when I leave my
> desk. Probably just using 'xlockmore -mode blank' or such. But how to
> detect?
Thanks all for the replies. To answer some questions:
- I prefer automatic. I
On Tuesday 14 July 2009 17:36:24 Polytropon wrote:
> so in my opinion it's
> always safe to first umount, then remove.
Kids (or aging muscles) force you to revise your view. Not to mention low
quality USB camera cables. AFAIK the panic is resolved in 8.x though. Not sure
about the 7.x series.
-
e device, and unplug it when you leave the keyboard. Then
> your computer would be safe from snooping, because it would kernel panic
> every time you walk away!
I first thought about that, too, but in my opinion it's not needed to mount
whatever you plug in as USB device, maybe a defec
On Wed, Jul 15, 2009 at 12:35:24AM +0200, Polytropon wrote:
>
> To make it more complicated, what about wearing some specific USB device
> on your clothes, attached to a chain, and when you leave the computer,
> it will pop out of the USB socket and therefore cause "xlock" to be
> called? :-)
Doe
> To make it more complicated, what about wearing some specific USB device
> on your clothes, attached to a chain, and when you leave the computer,
> it will pop out of the USB socket and therefore cause "xlock" to be
> called? :-)
Haha... Polytropon's witty responses are enough reason in themselv
On Tue, 14 Jul 2009 14:03:04 -0800, Mel Flynn
wrote:
> And use xev to figure out the keycode of an unused key on your keyboard you
> can easily access (like multimedia keys). Then you can activate it
> when leaving your spot or when that creepy guy from accounting tries to
> look over your should
On Tuesday 14 July 2009 07:52:43 Bill Moran wrote:
> In response to Frederique Rijsdijk :
> > I'm looking for a way to automaticaly lock my X session when I leave my
> > desk. Probably just using 'xlockmore -mode blank' or such. But how to
> > detect?
>
On 14 Jul 2009 21:43, Chad Perrin wrote:
On Tue, Jul 14, 2009 at 05:32:01PM +0200, Frederique Rijsdijk wrote:
> Hi,
>
> I'm looking for a way to automaticaly lock my X session when I leave my
> desk. Probably just using 'xlockmore -mode blank' or s
On Tue, Jul 14, 2009 at 05:32:01PM +0200, Frederique Rijsdijk wrote:
> Hi,
>
> I'm looking for a way to automaticaly lock my X session when I leave my
> desk. Probably just using 'xlockmore -mode blank' or such. But how to
> detect?
Why does it have to be automatic
Hi,
On Tue, Jul 14, 2009 at 11:32 AM, Frederique
Rijsdijk wrote:
> Hi,
>
> I'm looking for a way to automaticaly lock my X session when I leave my
> desk. Probably just using 'xlockmore -mode blank' or such. But how to
> detect?
>
> It could be infrared based (
In response to Frederique Rijsdijk :
>
> I'm looking for a way to automaticaly lock my X session when I leave my
> desk. Probably just using 'xlockmore -mode blank' or such. But how to
> detect?
>
> It could be infrared based (heat signature), video based (webc
Hi,
I'm looking for a way to automaticaly lock my X session when I leave my
desk. Probably just using 'xlockmore -mode blank' or such. But how to
detect?
It could be infrared based (heat signature), video based (webcam w/
motion detection) or even mechanical (switch in seat? m
Antonio L. wrote:
I tried running "lsof -p 77214," which showed a long list of files used by
the process, but I didn't see anything about it trying to get a lock on a
file. Googling suggests that "pfiles" on Solaris might help with this -- is
there an ana
t;lockf" state, so I assume
they're blocking while trying to acquire a lock on some file.
I tried using truss to see where this is occurring and get a lot of the
following:
# truss -p 77214
...
poll({10/POLLIN|POLLERR|POLLHUP},1,1000) = 1 (0x1)
recvfrom(10,"STORED\r\n",81
On 7/5/09, Polytropon wrote:
> Additional information, just recognized:
>
> When Num Lock is on (as described in my first message), some window
> manager functions don't work anymore: When doubleclicking on a title
> bar, the window does not roll up. When pressing Alt and drag
Additional information, just recognized:
When Num Lock is on (as described in my first message), some window
manager functions don't work anymore: When doubleclicking on a title
bar, the window does not roll up. When pressing Alt and dragging a
window with the left mouse button, the window
Dear list,
since I moved to a new keyboard, I have some trouble. Everything except
the Num Lock functionality works fine. Let me explain:
The keyboard is a BOSCOM PS/2 keyboard (with 122 keys, intended for
5250 operations on a PC) that contains a keyboard controller, so the
keyboard can simply
Charles Howse writes:
> >> ** Stale lock file was found. Removed.
> >
> >These are related to a (harmless) twitch in a recent version of
> > ruby. Updating to the latest version fixed it for me.
>
> Running 'portversion -c' after 'p
On Jun 27, 2009, at 10:42 AM, Robert Huff wrote:
Charles Howse writes:
What are stale lock files?
I've been having them for a few weeks now, they need to go away!
r...@curly /root# portupgrade -a
** Stale lock file was found. Removed.
** Stale lock file was found. Removed.
[..
Charles Howse writes:
> What are stale lock files?
> I've been having them for a few weeks now, they need to go away!
>
> r...@curly /root# portupgrade -a
> ** Stale lock file was found. Removed.
> ** Stale lock file was found. Removed.
> [...]
>
>
On Sat, 27 Jun 2009 10:00:24 -0500, Charles Howse wrote:
> What are stale lock files?
> I've been having them for a few weeks now, they need to go away!
Lock files are used by several programs to indicate file-wise that
they are running. The lock file is created when the program
Hi,
What are stale lock files?
I've been having them for a few weeks now, they need to go away!
r...@curly /root# portupgrade -a
** Stale lock file was found. Removed.
** Stale lock file was found. Removed.
[...]
r...@curly /root# portversion -c
** Stale lock file was found. Removed.
#
flushes to disk?
I've also managed to lock up the system, and just trying to pin point
the problem. This is a 7.1R just upgraded to 7.2 with GPT + gmirror +
gjournal with GENERIC kernel.
All SSH no data. Local console is locked as well, but the num lock
light turns on/off.
I had gstat runnin
running out of cache? or
> is that the journal cache that it flushes to disk?
>
>
> I've also managed to lock up the system, and just trying to pin point
> the problem. This is a 7.1R just upgraded to 7.2 with GPT + gmirror +
> gjournal with GENERIC kernel.
> All SSH no dat
And I think the cleanest solution would be to link .login to vtysh , make
sure that your system logs out when it finishes this command or you can't use
this technique.
Steve Bertrand wrote (earlier today):
> I think the cleanest solution would be to create a match block for your
> user, and ap
hi...
have a look here:
http://docs.hp.com/en/5991-7517/ch01s04.html
I think the cleanest solution would be to create a match block for your
user, and apply the forcecommand within that block...
--
Olli
On Fr, 2009-03-13 at 21:50 -0400, Steve Bertrand wrote:
> Jonathan Chen wrote:
> >
Jonathan Chen wrote:
> On Sat, Mar 14, 2009 at 02:18:27AM +0100, Polytropon wrote:
>
> [..]
>> If the user's shell is csh (FreeBSD's standard dialog shell), you
>> could achieve the goal:
>>
>> ~/.login
>> vtysh
>> logout
>>
>> Only problem: I don't know how the shell will act when
On Sat, Mar 14, 2009 at 02:18:27AM +0100, Polytropon wrote:
[..]
> If the user's shell is csh (FreeBSD's standard dialog shell), you
> could achieve the goal:
>
> ~/.login
> vtysh
> logout
>
> Only problem: I don't know how the shell will act when the user
> terminates the vtys
at are
>>> to be blackholed by the edge devices.
>>>
>>> What I want is to set up an environment so that when a specific user
>>> logs in to the box via SSH, a command is run, and they immediately get
>>> dropped into the environment that the command pro
ices.
> >
> > What I want is to set up an environment so that when a specific user
> > logs in to the box via SSH, a command is run, and they immediately get
> > dropped into the environment that the command produces.
> >
> > When they exit this 'command&#x
a command is run, and they immediately get
> dropped into the environment that the command produces.
>
> When they exit this 'command', the login session is dropped.
>
> Essentially, I want to 'lock' a user into a program upon SSH login, and
> drop them from t
.
When they exit this 'command', the login session is dropped.
Essentially, I want to 'lock' a user into a program upon SSH login, and
drop them from the SSH session when the program terminates.
In essence:
- user 'router' connects via SSH
- user is dropped into
Mel пишет:
On Friday 26 December 2008 08:12:49 Artem Kuchin wrote:
I am not even sure that it is related to freebsd, but maybe someone could
point out the problem.
We wanted to upgrade our hosting server from
FreeBSD 6.2, 3ware 8506-4LP SATA RAID, raid 5
to
FreeBSD 7.1 (RC for now), 9550SX
On Friday 26 December 2008 08:12:49 Artem Kuchin wrote:
> I am not even sure that it is related to freebsd, but maybe someone could
> point out the problem.
>
> We wanted to upgrade our hosting server from
> FreeBSD 6.2, 3ware 8506-4LP SATA RAID, raid 5
> to
> FreeBSD 7.1 (RC for now), 9550SXU-4LP,
I am not even sure that it is related to freebsd, but maybe someone could
point out the problem.
We wanted to upgrade our hosting server from
FreeBSD 6.2, 3ware 8506-4LP SATA RAID, raid 5
to
FreeBSD 7.1 (RC for now), 9550SXU-4LP, raid 10
We have tested the new installation on ASUS P5K WS motherb
installed
gnome and all other packages from packages-7-stable/Lastest on the
website, and it gives me the error from the subject line, 'Could not lock
the file "/var/tmp/gconf-test-locking-file-blah"'. It says that it's an
NFS locking error, but I'm not using NFS.
Do y
Aloha,
Loading a FreeBSD 8 Current I get Lock Order Reversals. There used to be
a site for looking into them. What do we do now?
~Al Plant - Honolulu, Hawaii - Phone: 808-284-2740
+ http://hawaiidakine.com + http://freebsdinfo.org +
+ http://aloha50.net - Supporting - FreeBSD 6.* - 7
Per olof Ljungmark wrote:
Al Plant wrote:
Kris Kennaway wrote:
Per olof Ljungmark wrote:
7.0-STABLE #0: Tue Aug 19 20:39:48 CEST 2008
After system update from June 12 sources to Aug 12 I have seen frequent
lockups during network operations. Compiled debugging kernel and got
the
below during
Al Plant wrote:
Kris Kennaway wrote:
Per olof Ljungmark wrote:
7.0-STABLE #0: Tue Aug 19 20:39:48 CEST 2008
After system update from June 12 sources to Aug 12 I have seen frequent
lockups during network operations. Compiled debugging kernel and got the
below during boot.
Should I open a PR? S
Al Plant wrote:
Kris Kennaway wrote:
Per olof Ljungmark wrote:
7.0-STABLE #0: Tue Aug 19 20:39:48 CEST 2008
After system update from June 12 sources to Aug 12 I have seen frequent
lockups during network operations. Compiled debugging kernel and got the
below during boot.
Should I open a PR? S
Kris Kennaway wrote:
Per olof Ljungmark wrote:
7.0-STABLE #0: Tue Aug 19 20:39:48 CEST 2008
After system update from June 12 sources to Aug 12 I have seen frequent
lockups during network operations. Compiled debugging kernel and got the
below during boot.
Should I open a PR? Suggestions welcom
Per olof Ljungmark wrote:
7.0-STABLE #0: Tue Aug 19 20:39:48 CEST 2008
After system update from June 12 sources to Aug 12 I have seen frequent
lockups during network operations. Compiled debugging kernel and got the
below during boot.
Should I open a PR? Suggestions welcome. Thanks.
Yes or tr
: uhid0: on uhub5
Aug 19 22:12:47 kreutzman kernel: lock order reversal:
Aug 19 22:12:47 kreutzman kernel: 1st 0xc7077a14 rtentry (rtentry) @
/usr/src/sys/net/route.c:328
Aug 19 22:12:47 kreutzman kernel: 2nd 0xc6eee07c radix node head (radix
node head) @ /usr/src/sys/net/route.c:879
Aug 19 22:12:47
On Tuesday 15 July 2008, Kris Kennaway wrote:
> Mike Clarke wrote:
> > I'm getting frequent panics due to spin lock held too long when
> > booting my recently built 6.3 system with an Athlon 4850e dual core
> > processor on a Foxconn 6150M2MA motherboard (GeForce 6150 a
Mike Clarke wrote:
On Tuesday 15 July 2008, Kris Kennaway wrote:
Mike Clarke wrote:
I'm getting frequent panics due to spin lock held too long when
booting my recently built 6.3 system with an Athlon 4850e dual core
processor on a Foxconn 6150M2MA motherboard (GeForce 6150 and
nForc
On Tuesday 15 July 2008, Kris Kennaway wrote:
> Mike Clarke wrote:
> > I'm getting frequent panics due to spin lock held too long when
> > booting my recently built 6.3 system with an Athlon 4850e dual core
> > processor on a Foxconn 6150M2MA motherboard (GeForce 6150 a
Mike Clarke wrote:
I'm getting frequent panics due to spin lock held too long when booting
my recently built 6.3 system with an Athlon 4850e dual core processor
on a Foxconn 6150M2MA motherboard (GeForce 6150 and nForce 430
chipsets).
FreeBSD curlew.lan 6.3-STABLE FreeBSD 6.3-STABLE #2
I'm getting frequent panics due to spin lock held too long when booting
my recently built 6.3 system with an Athlon 4850e dual core processor
on a Foxconn 6150M2MA motherboard (GeForce 6150 and nForce 430
chipsets).
FreeBSD curlew.lan 6.3-STABLE FreeBSD 6.3-STABLE #2: Sat Jul 12 09:43:21
On Fri, May 23, 2008 at 05:26:29AM -0700, Tobias Hoellrich wrote:
> Does anybody happen to know where I can submit lock order reversal
> outputs (like the one below)? I don't want to spam freebsd-current and
> http://sources.zabbadoz.net/freebsd/lor.html seems to have not been
>
1 - 100 of 262 matches
Mail list logo
