On 01/24/2013 06:38 PM, Dimitri Alexandris wrote:
> I will agree with the driver problem.
>
> My OI has 2 1G Intel ethernet bonded, and crashes at random times.
>
> There are also 2 10G ports connected and working fine.
>
> Symptom: OI crashes when a lot of traffic at the bond (5 - 40 minutes
>
I will agree with the driver problem.
My OI has 2 1G Intel ethernet bonded, and crashes at random times.
There are also 2 10G ports connected and working fine.
Symptom: OI crashes when a lot of traffic at the bond (5 - 40 minutes
after heavy traffic starts):
- Night rsync backups from other ser
I have a topic posted at illumos.org. Lame title for bug #3489.
Cheers,
Dave
On 2013-01-20, at 4:31 AM, Albert Lee wrote:
> Hi Dave,
>
> Please try to copy this and any other information you can obtain, as
> explained by others, into a bug report on illumos.org. Some of us are
> very interes
Hi Dave,
Please try to copy this and any other information you can obtain, as
explained by others, into a bug report on illumos.org. Some of us are
very interested in any problems with the CIFS service (which has
crashed here).
Thanks,
-Albert
On Sat, Jan 19, 2013 at 5:28 PM, David Scharbach
wr
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
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
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"
Larcher wrote:
>
>> From: Aurélien Larcher
>> Subject: Re: [OpenIndiana-discuss] OI Crash
>> To: "Discussion list for OpenIndiana"
>> Date: Saturday, January 19, 2013, 12:30 PM
>> Hi,
>> Has someone mentioned using 'fmdump' ?
>
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
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
> $
$ 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
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.
élien Larcher wrote:
> From: Aurélien Larcher
> Subject: Re: [OpenIndiana-discuss] OI Crash
> To: "Discussion list for OpenIndiana"
> Date: Saturday, January 19, 2013, 12:30 PM
> Hi,
> Has someone mentioned using 'fmdump' ?
>
> With this tool I disco
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
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
Well, I don't think it's stressing the hardware all that much, when you
consider our oldest server is 11 1/2 years old, with all its original hardware.
Our newest server is somewhere around 7 years old, without a hardware failure
for at least five years.
I admit I'm not much of a system admin.
On 1/18/2013 7:53 PM, dormitionsk...@hotmail.com wrote:
On Jan 17, 2013, at 8:47 PM, Reginald Beardsley wrote:
As far as I'm concerned, problems like this are a bottomless abyss. Which is
why I'm still putting up w/ my OI box hanging. It's annoying, but not
critical. It's also why critical
On 01/19/2013 01:53 AM, dormitionsk...@hotmail.com wrote:
> From 1992 to I used to 1998, I used to work at the Denver Museum of Natural
> History -- now the Denver Museum of Nature and Science. We had two or three
> DEC Vax's and an AIX machine there. It was their policy that once a week we
>
On Jan 17, 2013, at 8:47 PM, Reginald Beardsley wrote:
> As far as I'm concerned, problems like this are a bottomless abyss. Which is
> why I'm still putting up w/ my OI box hanging. It's annoying, but not
> critical. It's also why critical stuff still runs on Solaris 10.
>
> Intermittent fa
> BTW Back in the 80's there was a VAX operator in Texas who went out to his
> truck, got a .357 and shot the computer. His employer was not happy. But I
> can certainly understand how the operator felt.
Ah. That's too bad! I used to love VAX!
A shotgun would have done a much better job, t
On 01/18/2013 03:20 AM, David Scharbach wrote:
> I ran memtest86 for 3 passes, everything was ok there.
>
> Computer froze again today after only 1 day of uptime. I now have a dump
> file but I am confused as to what to do with it. Sorry to be a n00b but
> could you point me in the right direc
s there was a VAX operator in Texas who went out to his
truck, got a .357 and shot the computer. His employer was not happy. But I
can certainly understand how the operator felt.
--- On Thu, 1/17/13, David Scharbach wrote:
> From: David Scharbach
> Subject: Re: [OpenIndiana-dis
lol, you make it seem so easy :)
I just disabled the on board NIC. We will see. Next I will try the storage
controller. Then a hammer.
Cheers,
On 2013-01-16, at 9:01 AM, "Edward Ned Harvey (openindiana)"
wrote:
>> From: David Scharbach [mailto:david.scharb...@mac.com]
>>
>> I have an OI
I checked and the P8V77-v that I am using seems to be listed, unless the LK
suffix makes a big difference.
I just disabled my on-board NIC and installed an Intel NIC. Shall see…
Thanks again,
On 2013-01-15, at 10:44 PM, Mehmet Erol Sanliturk
wrote:
> On Tue, Jan 15, 2013 at 6:50 PM, David S
I ran memtest86 for 3 passes, everything was ok there.
Computer froze again today after only 1 day of uptime. I now have a dump file
but I am confused as to what to do with it. Sorry to be a n00b but could you
point me in the right direction?
Cheers,
On 2013-01-15, at 9:10 PM, Ian Collins w
I have had this issue and it turned out to be a power supply with too
little power for the 6 hard drives stuffed into my ultra 20. Removed 2
drives and everything was fine. The drives were perfectly fine. The
other time I have run into this is when I would lose a required nfs
mount (like a ho
> From: David Scharbach [mailto:david.scharb...@mac.com]
>
> I have an OI installation that seems to crash about every 20 days. Locks up
> completely and needs a hard reset. Not very much fun.
Whenever I've seen this type of behavior before, it was hardware/driver
related, but we never were ab
On 01/15/13 23:02, Rich wrote:
> mkdir -p /var/crash/$(hostname)
> pfexec dumpadm -y
>
> And ideally, put "set dump_plat_mincpu=0" in /etc/system, lest the
> core dump code try to thread and fail miserably.
>
> Next time you die, you should get a core dump in
> /var/crash/[hostname]/, presuming y
On 2013-01-16 05:04, Reginald Beardsley wrote:
This is apparently an outstanding bug and as far as I can see not easily fixed.
I did not have this problem w/ 148 and I would revert to that except I can't
remember the root password :-(
Can't you "beadm mount oi_148" (insert proper BE name) an
On Tue, Jan 15, 2013 at 6:50 PM, David Scharbach wrote:
> I have an OI installation that seems to crash about every 20 days. Locks
> up completely and needs a hard reset. Not very much fun.
>
> Question I have is where would I start to look to see why? I first
> thought it may be due to scrubbi
o resolve the cause and fix
it. There's nothing to get a hold of.
Good luck and please keep us posted.
Reg
--- On Tue, 1/15/13, David Scharbach wrote:
> From: David Scharbach
> Subject: Re: [OpenIndiana-discuss] OI Crash
> To: "Discussion list for OpenIndiana"
&g
mkdir -p /var/crash/$(hostname)
pfexec dumpadm -y
And ideally, put "set dump_plat_mincpu=0" in /etc/system, lest the
core dump code try to thread and fail miserably.
Next time you die, you should get a core dump in
/var/crash/[hostname]/, presuming your dump device has enough space.
- Rich
On T
On Jan 15, 2013, at 7:10 PM, Ian Collins wrote:
>
> If there isn't any evidence of a crash, there's a fair chance you have a
> hardware problem.
i have decent number of identical production boxes.
about once per quarter one of them spontaneously reboots leaving no trace as to
why. it is ne
I will make a memtest ISO ASAP. /var/adm/messages shows nothing. /var/crash
does not exist on my system.
Will see what memtest says.
Cheers,
Dave
On 2013-01-15, at 9:10 PM, Ian Collins wrote:
> David Scharbach wrote:
>> I have an OI installation that seems to crash about every 20 days. Lo
David Scharbach wrote:
I have an OI installation that seems to crash about every 20 days. Locks up
completely and needs a hard reset. Not very much fun.
Question I have is where would I start to look to see why? I first thought it
may be due to scrubbing load on the LSI controller but that
35 matches
Mail list logo
