-drm?
> > >
> > > С уважением,
> > > Александр Пыхалов,
> > > программист отдела телекоммуникационной инфраструктуры
> > > управления информационно-коммуникационной инфраструктуры ЮФУ
> > >
> > >
> > > __
cussion list for OpenIndiana
> Тема: Re: [OpenIndiana-discuss] Kernel panic after pkg update
>
> The only outstanding things since May were switching gfx-drm to gcc-
> 7
> and
> cherry-picking gcc-10 patches from upstream.
>
>
> On Tue, Aug 18, 2020 at 9:43 AM Tony Brian Alb
>> программист отдела телекоммуникационной инфраструктуры
>> управления информационно-коммуникационной инфраструктуры ЮФУ
>>
>>
>>
>> От: Aurélien Larcher
>> Отправлено: 18 августа 2020 г. 11:29
>> Кому: Discus
cussion list for OpenIndiana
> Тема: Re: [OpenIndiana-discuss] Kernel panic after pkg update
>
> The only outstanding things since May were switching gfx-drm to gcc-
> 7
> and
> cherry-picking gcc-10 patches from upstream.
>
>
> On Tue, Aug 18, 2020 at 9:43 AM Tony Brian Alb
От: Aurélien Larcher
> Отправлено: 18 августа 2020 г. 11:29
> Кому: Discussion list for OpenIndiana
> Тема: Re: [OpenIndiana-discuss] Kernel panic after pkg update
>
> The only outstanding things since May were switching gfx-drm to gcc-7 and
> cherry-picking gcc-10 patches from u
От: Aurélien Larcher
Отправлено: 18 августа 2020 г. 11:29
Кому: Discussion list for OpenIndiana
Тема: Re: [OpenIndiana-discuss] Kernel panic after pkg update
The only outstanding things since May were switching gfx-drm to gcc-7 and
cherry-picking gcc-10 patches from upstream.
On Tue, Aug 18
t; управления информационно-коммуникационной инфраструктуры ЮФУ
> >
> >
> >
> > От: Tony Brian Albers
> > Отправлено: 18 августа 2020 г. 10:14
> > Кому: openindiana-discuss@openindiana.org
> > Тема: Re: [OpenIndiana-discuss] Kernel p
оммуникационной инфраструктуры
> управления информационно-коммуникационной инфраструктуры ЮФУ
>
>
>
> От: Tony Brian Albers
> Отправлено: 18 августа 2020 г. 10:14
> Кому: openindiana-discuss@openindiana.org
> Тема: Re: [OpenIndiana-discuss]
инфраструктуры
> управления информационно-коммуникационной инфраструктуры ЮФУ
>
>
>
> От: Tony Brian Albers
> Отправлено: 18 августа 2020 г. 10:14
> Кому: openindiana-discuss@openindiana.org
> Тема: Re: [OpenIndiana-discuss] Kernel
Кому: openindiana-discuss@openindiana.org
Тема: Re: [OpenIndiana-discuss] Kernel panic after pkg update
FYI
I removed and reinstalled all xorg-related pkgs. I also ran pkg update
again.
Now Xorg loads more driver modules and there are no errors in Xorg.log,
but the system still panics.
Kernel
FYI
I removed and reinstalled all xorg-related pkgs. I also ran pkg update
again.
Now Xorg loads more driver modules and there are no errors in Xorg.log,
but the system still panics.
Kernel illumos-0d54f452f4
The panic message in /var/adm/messages seems to be exactly the same.
/tony
On
Hi guys,
I'm trying to get my workstation to run the latest OI. Installation of
the desktop-image went fine, and after reboot everything is still ok.
Then I did a pkg update. Now running kernel illumos-06260e34c2
Now, everytime I try to start X, it panics and reboots. I've disabled
the
Can you post the core dump somewhere?
Cheers,
Adam
> On 4 Oct 2016, at 14:33, Apostolos Syropoulos via openindiana-discuss
> wrote:
>
> Today I saw the following:
>
>
>
> Oct 4 15:26:18 adalind savecore: [ID 570001 auth.error] reboot after panic:
>
>
Today I saw the following:
Oct 4 15:26:18 adalind savecore: [ID 570001 auth.error] reboot after panic:
assertion failed: (vp->v_count > 0) && (vp->v_count_dnlc > 0), file:
../../common/fs/vnode.c, line: 852
Does anybody have any idea what this is about?
A.S.
--
Sent from my iPhone
> On Sep 16, 2015, at 11:49 AM, Watson, Dan wrote:
>
> I've noticed that drives with a labeled WWN tend to be less error prone, and
> only when a driv
This a distinction that only exists in your head. :)
I have only 768 HGST 600gb sas drives
On 09/16/15 10:42 PM, Andrew Gabriel wrote:
Also what OI/illumos is that, because I was reading long ago there
were some bugs solved in illumos for mpt_sas.
Somewhere around 18 months ago IIRC, Nexenta pushed a load of fixes
for this into their git repo. I don't think I've seen these picked
riginal Message-
> From: Nikola M [mailto:minik...@gmail.com]
> Sent: September 16, 2015 11:25 AM
> To: Discussion list for OpenIndiana
> Subject: Re: [OpenIndiana-discuss] Kernel panic on hung zpool accessed via
> lofi
>
> On 09/11/15 08:57 PM, Watson, Dan wrote:
RAM available to do dedupe.
Thanks!
Dan
-Original Message-
From: Nikola M [mailto:minik...@gmail.com]
Sent: September 16, 2015 11:25 AM
To: Discussion list for OpenIndiana
Subject: Re: [OpenIndiana-discuss] Kernel panic on hung zpool accessed via lofi
On 09/11/15 08:57 PM, Watson, Da
>-Original Message-
>From: Jim Klimov [mailto:jimkli...@cos.ru]
>Sent: September 12, 2015 10:31 AM
>To: Discussion list for OpenIndiana; Watson, Dan;
>openindiana-discuss@openindiana.org
>Subject: Re: [OpenIndiana-discuss] Kernel panic on hung zpool accessed via lofi
&
diana-discuss@openindiana.org
>>Subject: Re: [OpenIndiana-discuss] Kernel panic on hung zpool accessed
>via lofi
>>
>>11 сентября 2015 г. 20:57:46 CEST, "Watson, Dan"
><dan.wat...@bcferries.com> пишет:
>>>Hi all,
>>>
>>>I've been e
11 сентября 2015 г. 20:57:46 CEST, "Watson, Dan"
пишет:
>Hi all,
>
>I've been enjoying OI for quite a while butI'm running into a problem
>with accessing zpool on disk image files sitting on zfs accessed via
>lofi that I hope someone can give me a hint on.
>
>To recover
Hi all,
I've been enjoying OI for quite a while butI'm running into a problem with
accessing zpool on disk image files sitting on zfs accessed via lofi that I
hope someone can give me a hint on.
To recover data from a zpool I've copied slice 0 off of all the disks to a
different host under
You need this fix:
https://github.com/Nexenta/illumos-nexenta/commit/9a60a9d168313d9c350f813abccc6320879ad9b5
On Thu, Apr 17, 2014 at 5:05 PM, Geoff Nordli geo...@gnaa.net wrote:
On 14-04-17 01:20 PM, Geoff Nordli wrote:
I am running OI 151a8.
I had a kernel panic today. I have the dump
Thanks Gordon.
Any idea if that has been merged into illumos gate yet?
On 14-04-21 06:04 PM, Gordon Ross wrote:
You need this fix:
https://github.com/Nexenta/illumos-nexenta/commit/9a60a9d168313d9c350f813abccc6320879ad9b5
On Thu, Apr 17, 2014 at 5:05 PM, Geoff Nordli geo...@gnaa.net
On 14-04-17 01:20 PM, Geoff Nordli wrote:
I am running OI 151a8.
I had a kernel panic today. I have the dump file so I can provide
more detail if needed.
Should I send this over to the illumos list or can someone help me here?
thanks,
Geoff
TIME UUID
On Thu, Dec 12, 2013 at 02:48:21PM -0800, Reginald Beardsley wrote:
I didn't find anything in the wiki about reporting kernel panics. Is there a
documented procedure? The dump is ~285 MB.
http://wiki.illumos.org/display/illumos/How+To+Report+Problems
--
FWIW My system just went down w/ a kernel panic caused by a null reference in
genunix. I'm running oi_151a8. I had just unmounted an SDHC card w/ a FAT
filesystem used in my Canon camera and when I came back from putting the
camera away found the system at the grub menu.
I didn't find
From: Geoff Simmons ge...@uplex.de
A colleague attempted to boot oi_151a from CD on an HP EliteBook 8560w
laptop:
http://h10010.www1.hp.com/wwpc/us/en/sm/WF06a/321957-321957-64295-3740645-4307559-5071171.html
... the variant with Intel i7-2670QM. He got an immediate kernel panic
Maybe you could try disabling ACPI in BIOS if possible, or otherwise use
the acpi-user-options=0x2 at boot.
Read here for more info on disabling ACPI on boot:
https://blogs.oracle.com/danasblog/entry/configuring_solaris_acpi_at_boot
BTW and OT, I hadn't even thought that attaching an image to
i would start even more conservatively and disable speed step in the bios first
and then more on to the other suggestions. i am not a fan of speedstep in
general.
j.
Sent from Jasons' hand held
On Feb 13, 2012, at 9:44 AM, Bryan N Iotti ironsides.med...@gmail.com wrote:
Maybe you could
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 02/13/12 06:51 PM, Jason Matthews wrote:
i would start even more conservatively and disable speed step in the
bios first and then more on to the other suggestions. i am not a fan of
speedstep in general.
On Feb 13, 2012, at 9:44 AM, Bryan N
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 02/13/12 06:44 PM, Bryan N Iotti wrote:
Maybe you could try disabling ACPI in BIOS if possible, or otherwise use
the acpi-user-options=0x2 at boot.
Read here for more info on disabling ACPI on boot:
Hi Geoff,
Geoff Simmons píše v po 13. 02. 2012 v 19:39 +0100:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 02/13/12 06:44 PM, Bryan N Iotti wrote:
Maybe you could try disabling ACPI in BIOS if possible, or otherwise use
the acpi-user-options=0x2 at boot.
Read here for more
.
More to follow...
Lou Picciano
- Original Message -
From: Geoff Simmons ge...@uplex.de
To: openindiana-discuss@openindiana.org
Cc: Nils Goroll nils.gor...@uplex.de
Sent: Tuesday, February 7, 2012 7:55:22 AM
Subject: [OpenIndiana-discuss] Kernel panic with Intel i7
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hello all,
A colleague attempted to boot oi_151a from CD on an HP EliteBook 8560w
laptop:
http://h10010.www1.hp.com/wwpc/us/en/sm/WF06a/321957-321957-64295-3740645-4307559-5071171.html
... the variant with Intel i7-2670QM. He got an immediate
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 02/ 7/12 05:15 PM, Jerry Kemp wrote:
I have the same issue/problem with my MacBook Pro 17 i7 and also with a 2010
Mac Mini server.
Solaris runs fine though from my 2007 Mac Mini.
Jerry
On 02/ 7/12 07:37 AM, Bryan N Iotti wrote:
I
On 06/28/2011 09:32 PM, Gordon Ross wrote:
Here is the ::stack
http://img220.imageshack.us/i/oi148stack.jpg/
If you look at what the other threads are doing
::walk thread | ::findstack -v
I suspect you'll see that ZFS is still trying to import.
I would suggest you dd if=/dev/zero
On Thu, Jun 30, 2011 at 08:01, Johan Guldmyr johan.guld...@csc.fi wrote:
On 06/28/2011 09:32 PM, Gordon Ross wrote:
Here is the ::stack
http://img220.imageshack.us/i/oi148stack.jpg/
If you look at what the other threads are doing
::walk thread | ::findstack -v
I suspect you'll see that
On 06/30/2011 09:22 AM, Michael Schuster wrote:
with dd, use bs=bignumber to increase the block size dd reads and
writes in one go - as you quote it, dd wrote 512 bytes at a time. A
good value to start with would be 1048576 (1MB).
Also, you may have stopped the command in an unintended way -
On 06/27/2011 04:42 PM, Steve Gonczi wrote:
Hello,
This should be analyzed and root caused.
A ::stack woudl be useful to see the call parameters.
Without disassembling zio_buf_alloc() I can only guess that
the mutex_enter you see crashing is really in kmem_cache_alloc()
If that proves to be
On Tue, Jun 28, 2011 at 2:51 AM, Johan Guldmyr johan.guld...@csc.fi wrote:
On 06/27/2011 04:42 PM, Steve Gonczi wrote:
[...]
- Original Message -
Now with the pictures, hope this works:
http://imageshack.us/photo/my-images/402/oi151paniccdollarstatus.jpg/
Hello! A bit of a long e-mail and large attachment but I want to be as
thorough as possible.
It says that the blade is pending HP-support for Solaris 10 Update 9 -
has anybody got it working?
We have several bl460c g1 running SunOS 5.11 snv_134.
When I try to install it, it kernel panics at
On 06/27/2011 10:01 AM, Johan Guldmyr wrote:
When I try to install it, it kernel panics at 0%. By adding -k to the
grub line I got the the :msgbuf (attached in .zip file - several .jpg
files), but I don't understand most of it. If anybody could help me shed
some light in this I would appreciate
On 27/06/2011 7:11 p.m., Johan Guldmyr wrote:
On 06/27/2011 10:01 AM, Johan Guldmyr wrote:
When I try to install it, it kernel panics at 0%. By adding -k to the
grub line I got the the :msgbuf (attached in .zip file - several .jpg
files), but I don't understand most of it. If anybody could help
On 06/27/2011 10:52 AM, Mark wrote:
Have you tried deleting the solaris partition from the hard disk (via
format) ?
It can help prevent detection of an existing, broken filesystem.
Mark.
Hello Mark,
I deleted the partition via format, created a new one of 50% and then in
install I chose to
Hello,
This should be analyzed and root caused.
A ::stack woudl be useful to see the call parameters.
Without disassembling zio_buf_alloc() I can only guess that
the mutex_enter you see crashing is really in kmem_cache_alloc()
If that proves to be the case, I would verify the offset of
Hi Thorsten,
I found that I experienced a similar kernel panic when attempting to
perform a clean install of OpenIndiana which would occur at around 2% of
the installation on a consistent basis.
I eventually worked out that I had to use GParted to delete any
partitions on the boot disc
On Fri, Oct 22, 2010 at 3:28 AM, russell str...@willows7.myzen.co.uk wrote:
Hi Thorsten,
I found that I experienced a similar kernel panic when attempting to perform
a clean install of OpenIndiana which would occur at around 2% of the
installation on a consistent basis.
I eventually worked
Michael michaelspriv...@gmail.com schrieb am 04.10.2010 12:12:13:
On Mon, Oct 4, 2010 at 12:05 PM, Thorsten Heit thorsten.h...@vkb.de
wrote:
Hi,
It seems very easy to overlook, but it is my understanding that you
always need to run these steps in a specific order:
first just run
Hi,
It seems very easy to overlook, but it is my understanding that you
always need to run these steps in a specific order:
first just run import by itself
pfexec zpool import
output will list pools available for import
Great, didn't know about that. Thanks :-)
Just run import by
On Mon, Oct 4, 2010 at 12:05 PM, Thorsten Heit thorsten.h...@vkb.de wrote:
Hi,
It seems very easy to overlook, but it is my understanding that you
always need to run these steps in a specific order:
first just run import by itself
pfexec zpool import
output will list pools available
Hi,
This appears very similar to another issue with the bootfs
specification which is normally transparent:
http://opensolaris.org/jive/thread.jspa?messageID=315743
Also make sure you have the current version of GRUB installed on
*both* disks in your mirror, as it's responsible for
Sorry you are having trouble. Just a couple probing questions to open up
everyones mind. Before I forget, make sure you have burned a OS b134 live
cd and a OI b147 live dvd before you do anything.
The first thing I would try is booting into your b134 BE. Then export all
the pools besides
Hi,
Sorry you are having trouble. Just a couple probing questions to open
up
everyones mind. Before I forget, make sure you have burned a OS b134
live
cd and a OI b147 live dvd before you do anything.
The first thing I would try is booting into your b134 BE. Then export
all
the pools
I actually even reinstalled OI, but that didn't change anything.
There's only a slight difference in the message after the NOTICE: line:
Cannot mount root on rpool/95 fstype zfs
can you show the output of zfs list -tall as run from a different BE
(at least the relevant parts)? Maybe you can
This appears very similar to another issue with the bootfs
specification which is normally transparent:
http://opensolaris.org/jive/thread.jspa?messageID=315743
Also make sure you have the current version of GRUB installed on
*both* disks in your mirror, as it's responsible for specifying the
56 matches
Mail list logo