On Fri, Jan 18, 2013 at 12:05 PM, Udo Grabowski (IMK)
wrote:
> 3. OI should concentrate on importing working new drivers for
>new hardware, a lot of stuff is already out there in the
>illumos cloud and elsewhere and just needs to be packaged.
>Otherwise, we will quickly loose users sin
Hello,
Since Windows 8 and Server 2012 there is a new Version of the SMB protocol.
SMB 3.0 has one special feature which I'm interested in, called
multipathing.
Though SMB is very nice implemented in OpenIndiana i couldnt find which SMB
Version it supports, and are there plans to support S
One time when I happened to look, I saw that the Ultra 60 I used at work had
been up for over 18 months.
If a sys admin told me he wanted to reboot a system once a week, "just in case"
he'd be looking for a new job very soon or else sent back to the PC support
pool.
BTW The reason that 11/78
Hi,
I have a home NAS that I'm running on an Asus E35M1-I (AMD E-350)
motherboard. When I do a shutdown using "init 5", and then physically
walk over to power it on (without ever unplugging the power),
sometimes the system powers up with the date set to December 27th
1986. I have ntp installed, so
On 01/19/2013 05:37 PM, Jan Owoc wrote:
> Hi,
>
> I have a home NAS that I'm running on an Asus E35M1-I (AMD E-350)
> motherboard. When I do a shutdown using "init 5", and then physically
> walk over to power it on (without ever unplugging the power),
> sometimes the system powers up with the date
You may have better luck getting an answer using the dev mailing list.
mailto:oi-...@openindiana.org
On 2013-01-19 7:31 AM, "Johannes Grieb" wrote:
> Hello,
>
>
>
> Since Windows 8 and Server 2012 there is a new Version of the SMB protocol.
>
> SMB 3.0 has one special feature which I'm intereste
Hi,
Has someone mentioned using 'fmdump' ?
With this tool I discovered that I had issues with an unreliable disk
controller on my workstation with the consequence of OI freezing approx.
every 2months.
In my case ZFS is getting the fault and standby until resolution of the
issue, thus yielding an i
Having a console window open and checking it periodically can be very helpful.
Such events will get logged to the console. I recently had a correctable event
show up in mine. There's probably a way to have the events trigger an email if
desired.
Have Fun!
Reg
--- On Sat, 1/19/13, Aurélien La
On 2013-01-19 20:04, Reginald Beardsley wrote:
Having a console window open and checking it periodically can be very helpful.
Such events will get logged to the console. I recently had a correctable event
show up in mine. There's probably a way to have the events trigger an email if
desired.
http://os-solaris.ru/en/bluetooth-dlya-illumos-versiya-0-1/
___
OpenIndiana-discuss mailing list
OpenIndiana-discuss@openindiana.org
http://openindiana.org/mailman/listinfo/openindiana-discuss
$ fmdump
TIME UUID SUNW-MSG-ID EVENT
Jan 17 20:08:28.9193 809adc23-290c-c3bb-bcde-c3d4c5c1ebe6 SUNOS-8000-KL
Diagnosed
$ uptime
16:12pm up 1 day 20:04, 2 users, load average: 0.08, 0.14, 0.21
Given today is the 19th and such, I think that timest
If you use the -m flags to get the details what does it say ?
On Sat, Jan 19, 2013 at 11:15 PM, David Scharbach
wrote:
> $ fmdump
> TIME UUID SUNW-MSG-ID EVENT
> Jan 17 20:08:28.9193 809adc23-290c-c3bb-bcde-c3d4c5c1ebe6 SUNOS-8000-KL
> Diagnosed
> $
English is good.
$ fmdump -m
SUNW-MSG-ID: SUNOS-8000-KL, TYPE: Defect, VER: 1, SEVERITY: Major
EVENT-TIME: Thu Jan 17 20:08:28 CST 2013
PLATFORM: System-Product-Name, CSN: System-Serial-Number, HOSTNAME: openindiana
SOURCE: software-diagnosis, REV: 0.1
EVENT-ID: 809adc23-290c-c3bb-bcde-c3d4c5c1ebe
to this end, redirect your console to a serial port and put a serial recorder
on it. they cost maybe 60$ but can be handy to catch output from panics.
j.
Sent from Jasons' hand held
On Jan 19, 2013, at 11:04 AM, Reginald Beardsley wrote:
> Having a console window open and checking it perio
Your dump device contains a crash dump from a kernel panic that your
machine previously encountered. See
http://wiki.illumos.org/display/illumos/How+To+Report+Problems for a
guide on how to extract useful information from the crash dump and post
it here. In particular, you'll want to do "savecore"
I cannot tell what would be the next step to diagnose the problem but:
panicstr = BAD TRAP: type=e (#pf Page fault) rp=ff003c913840 addr=77
occurred in module "smbsrv" due to a NULL pointer dereference
panicstack = unix:die+dd () | unix:trap+17db () | unix:cmntrap+e6 () |
smbsrv:smb_mbc_vdecod
On 2013-01-19 23:50, Aurélien Larcher wrote:
I cannot tell what would be the next step to diagnose the problem but:
panicstr = BAD TRAP: type=e (#pf Page fault) rp=ff003c913840 addr=77
occurred in module "smbsrv" due to a NULL pointer dereference
panicstack = unix:die+dd () | unix:trap+17db
17 matches
Mail list logo
