Hi,
after rebooting my Opensolaris System (b130) after I/O was hung it came up with
the
following messages:
WARNING: dmar0,0 generated a fault event when translating DMA write
on address 0x25a000 for PCI(9, 0, 0), the reason is:
The Write field in a page-table entry is Clear when DMA write
129: Xen manager did not even start
130: could not even see the screen as it was all dark white
I hope that build 131 will come soon and run smoothly like 128a.
Thanks.
--
This message posted from opensolaris.org
___
opensolaris-discuss mailing list
On 01/13/10 07:40 AM, Mauro Mozzarelli wrote:
130: could not even see the screen as it was all dark white
Which graphics? If NVIDIA and you had previously manually
enabled compiz, try the workaround in:
http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=6912450
Experiencing very strange behaviour with upgraded OpenSolaris machine ( from
snv_124 to snv_130 )
Machine gets panic, with the following error:
trap: Unknown trap type 8 in user mode.
panic[cpu0]/thread = fbc2e3a0: mutex_enter: bad mutex, lp=20
owner=f000e987f000fea0
Experiencing very strange behaviour with upgraded OpenSolaris machine ( from
snv_124 to snv_130 )
Machine gets panic, with the following error:
trap: Unknown trap type 8 in user mode.
panic[cpu0]/thread = fbc2e3a0: mutex_enter: bad mutex, lp=20
owner=f000e987f000fea0 thread
This is not about some specific process.
All this happens when I try to boot newly created boot environment (after pkg
image-update from snv_124 to snv_130 build)
So when I boot kernel with kmdb enabled (using -kd flags in grub and manually
run kernel) I get this.
Unfortunately users using this
I had this EXACT SAME THING happen to me!
I started a thread in zfs discuss about it:
http://opensolaris.org/jive/thread.jspa?threadID=121451tstart=15
I actually had iscsi turned off when I did the destroy. Didn't matter.
I still have not been able to get my pool back.
This is the 2nd time in
Are your AMD processors actually of a type that is
supported in
OpenSolaris for frequency scaling? If they are
family type 15 or lower,
then they aren't and likely will never be because of
lacking invariant
TSC support.
Of course, family 15 exactly. Do you think that if I had a business
* Mauro Mozzarelli (opensolari...@ezplanet.net) wrote:
Are your AMD processors actually of a type that is
supported in
OpenSolaris for frequency scaling? If they are
family type 15 or lower,
then they aren't and likely will never be because of
lacking invariant
TSC support.
Of
Hi all,
I just switch (or tested, if you will) using fvmw instead fo Gnome.
Now my external usb (with UFS) does not automount anymore. Is the
automount feature tied to Gnome? Is there a way to get it without
Gnome?
Johann
___
opensolaris-discuss
On 01/13/10 11:07 AM, Johann Myrkraverk Oskarsson wrote:
Hi all,
I just switch (or tested, if you will) using fvmw instead fo Gnome.
Now my external usb (with UFS) does not automount anymore. Is the
automount feature tied to Gnome? Is there a way to get it without
Gnome?
rmvolmgr should do
On 01/13/10 12:17 PM, Johann Myrkraverk Oskarsson wrote:
rmvolmgr should do the automounting when Nautilus is not present. Make sure
this service is online:
Thank you. Both hal and rmvolmgr were offline. Something had caused
hal to maintenance. Just clearing it removed the issue and now
Mauro Mozzarelli wrote:
129: Xen manager did not even start
Odd, my xVM server is running b129.
130: could not even see the screen as it was all dark white
Odd, my desktop is running b130!
--
Ian.
___
opensolaris-discuss mailing list
Experiencing very strange behaviour with upgraded
OpenSolaris machine ( from snv_124 to snv_130 )
Machine gets panic, with the following error:
Just a wild guess...
An opensolaris upgrade currently has a nasty bug that
results in old kernel modules ending in the boot_archive:
Bug ID:
Hi All,
I'd like to announce the immediate availability of NexentaStor
Developer Edition v2.2.1.
Changes since v2.2 include many bug fixes. More information:
* This is a major stable release.
* Storage limit increased to 4TB.
* Built-in antivirus capability.
* Consistent snapshots Oracle and
It already *has* market share. Think of all the Solaris 10 deployments
(from which OpenSolaris was initially started from). Not to mention the
people
(like Joyent) who are running OpenSolaris *today* in *production*.
No, this is very much incorrect. Joyent does not run OpenSolaris Indiana
Now, just to keep the record straight. I'm not in 100% agreement with Ben
Rockwood (maybe only 96% agreement).
I actually love Indiana and run it as my main day-to-day desktop OS. The
problem is that you can't use Indiana as a minimal server OS in production
because the Caiman installer does
* Anon Y Mous (music_anal...@yahoo.com) wrote:
It already *has* market share. Think of all the Solaris 10 deployments
(from which OpenSolaris was initially started from). Not to mention the
people
(like Joyent) who are running OpenSolaris *today* in *production*.
No, this is very
* Anon Y Mous (music_anal...@yahoo.com) wrote:
Now, just to keep the record straight. I'm not in 100% agreement with
Ben Rockwood (maybe only 96% agreement).
I actually love Indiana and run it as my main day-to-day desktop OS.
The problem is that you can't use Indiana as a minimal server OS
129: Xen manager did not even start
130: could not even see the screen as it was all dark white
I hope that build 131 will come soon and run smoothly like 128a.
Although I believe both of these issues have been resolved, did you
examine http://defect.opensolaris.org and/or
20 matches
Mail list logo
