<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-text-html" lang="x-unicode"> Hi Arnaud,<br>
<br>
Great to hear this is an isolated case; hopefully it means we've
found a bug we can help solve.<br>
<br>
On 27/11/12 22:50, Arnaud Quette wrote:<br>
<blockquote
cite="mid:CAFm_bUj1O6CFt=pyUJbNnH0cyo05Pz8hfFm0fgud8JZvL=x7zQ@mail.gmail.com"
type="cite">please send the log here, in compressed form.<br>
<div class="gmail_quote">
<div>are the photos taken with a still cam?<br>
please put these on your website (or any other public
storage) and point the link<br>
</div>
</div>
</blockquote>
For each of the four crashes I've got syslog excerpts (which
include some messages from just before and just after the crash)
and photos of the screen. I couldn't take the whole screen at
once clearly, so I took several photos that overlap. The photos
were pretty bad (low end smartphone - sorry) but they should be
legible; I've treated them to improve clarity and image size.<br>
<br>
Crashes 1 and 2 used the same (fairly basic) setup. After crash 2
I added the 'pollonly' driver flag, and after crash 3 I removed
that and was running the driver with -D instead.<br>
<br>
Crash 1 - <a href="http://ubuntuone.com/0J9nFa80fvGSou2eytvm92">A.png</a>
<a href="http://ubuntuone.com/5xJS7R2NuKR7jlDsyHa60B">B.png</a>
(syslog.1.gz attached)<br>
Crash 2 - <a href="http://ubuntuone.com/3oDzexDvymLlEZp9n08yi5">A.png</a>
<a href="http://ubuntuone.com/4E75bm8hP1Dn26ZALc38P2">B.png</a> <a
href="http://ubuntuone.com/5R9lx8sxILvfTSLElZwB75">C.png</a> <a
href="http://ubuntuone.com/2Z9f2KhxgsuoQUZKCgyWUr">D.png</a>
(syslog.2.gz attached)<br>
Crash 3 - <a href="http://ubuntuone.com/3dLbezmhjk94EH1NWebId8">A.png</a>
<a href="http://ubuntuone.com/74ZOCo4ymmm4ONUsRgdeSL">B.png</a>
(syslog.3.gz attached)<br>
Crash 4 - <a href="http://ubuntuone.com/0BSntOkyOuB935R6oxie7v">A.png</a>
<a href="http://ubuntuone.com/735zksHQYCzeidhTjJM28P">B.png</a> <a
href="http://ubuntuone.com/1Bs3sn2rIRU5vkqXe8Pc2x">C.png</a>
(syslog.4.gz attached)<br>
<br>
There should be most kernel details you need in the screenshots.
This is running the latest nut-server package from Ubuntu Precise
64-bit (version 2.6.3-1ubuntu1.1 at present) on a Dell PowerEdge
R210 II.<br>
<br>
<blockquote
cite="mid:CAFm_bUj1O6CFt=pyUJbNnH0cyo05Pz8hfFm0fgud8JZvL=x7zQ@mail.gmail.com"
type="cite">
<div class="gmail_quote">
<div>a dump file would be preferable:<br>
<a moz-do-not-send="true"
href="https://help.ubuntu.com/12.04/serverguide/kernel-crash-dump.html">https://help.ubuntu.com/12.04/serverguide/kernel-crash-dump.html</a><br>
</div>
</div>
</blockquote>
I'll see what I can do; this is our main development server, so
I'll probably be limited to weekends.<br>
<br>
I'm not very familiar with what data crash dumps record, but do
know
that I can only post one if I'm sure it doesn't contain company
file data, encryption keys, VM state, etc. (for obvious reasons).
Since I know in advance I'll be taking a crash dump, are there any
steps I can take steps to
avoid such data? If not, I can still run tools on the dump
locally (out of hours) and send backtraces or other output you
might need.<br>
<br>
Let me know if any other details, config files, etc., would help.<br>
<br>
Cheers,
<div class="moz-text-html" lang="x-unicode"><br>
Paul.<br>
</div>
<br>
PS I've replied only to the list; do you prefer that I reply to
you and CC: the list instead?<br>
<br>
</div>
</body>
</html>