Note that hitting the close button doesn't cause a crash, just hitting
the Quit button. Other than the crash, both do the same thing.
** Summary changed:
- nvidia-settings-325 crash with pressing exit button
+ nvidia-settings-325 crashes on Quit button press
--
You received this bug
I have the same on my Thinkpad W510 (Nvidia Quadro FX 880M) on Xubuntu
12.10, using the xorg-edgers PPA, which brings in Linux 3.7.0.7-generic.
I installed nvidia-325 via synaptic. I get this in /var/log/syslog after
two crashes:
Sep 3 18:30:57 Escher kernel: [ 990.669702] traps:
Oops, never mind. I get the same crash whether I hit Quit or simply
close the window. Seems apport stopped bothering to report the crashes
after the first few times. Running nvidia-setttings from the command
line gives this on exit:
Illegal instruction (core dumped)Illegal instruction (core
*** This bug is a duplicate of bug 1214508 ***
https://bugs.launchpad.net/bugs/1214508
I just marked this as a duplicate of Bug #1214508. Alberto Milone, could
you assign yourself to that bug?
** This bug has been marked a duplicate of bug 1214508
nvidia-settings =319 segfaults on close
seems to apply to all versions since 319
** Package changed: nvidia-settings-319-updates (Ubuntu) = nvidia-
settings (Ubuntu)
** Also affects: nvidia-drivers-ubuntu
Importance: Undecided
Status: New
** No longer affects: nvidia-drivers-ubuntu
** Also affects: gdk-pixbuf
*** This bug is a duplicate of bug 1214508 ***
https://bugs.launchpad.net/bugs/1214508
Still seeing this in nvidia-settings version 331.20 from the xorg-edgers
PPA on Xubuntu 12.10. I updated the title to make it less version
specific.
** Summary changed:
- nvidia-settings-325 crashes on
** Summary changed:
- htree_dirblock_to_tree:920: inode #53629599: block 214443464: comm rm: bad
entry in directory: rec_len % 4 != 0 - offset=0(0), inode=1667681412,
rec_len=45654, name_len=39
+ fstrim corrpution on some SSDs
** Summary changed:
- fstrim corrpution on some SSDs
+ fstrim
I've installed Xubuntu 14.04 on a brand new Crucial MX100 SSD
(CT512MX100SSD1, original MU01 firmware, no newer firmware available) on
a Thinkpad W510, and saw the note in the cron.weekly/fstrim file. After
running fstrim manually the first two times, I got this:
$ sudo fstrim -v /
/:
@penalvch,
Huh? I'm not currently having this problem. Just reporting that my
Crucial CT512MX100SSD1 currently doesn't seem to exhibit the problem,
and therefore should maybe be added to the whitelist.
If you still want me to file a separate bug report (to get more hardware
details?), please let
Note that there are reports on the Crucial forum that the Crucial M550
has the same problem, and therefore because it uses the same controller
(and firmware?), the MX100 does too:
http://forum.crucial.com/t5/Solid-State-Drives-SSD/M500-M5x0-QUEUED-
@Allard, OK, that's good to know that a message shows up in dmseg saying
the queued trim is disabled. I don't have that message for my MX100, so
it seems trim isn't disabled in the kernel for the MX100:
$ dmesg | grep ata1
[1.995490] ata1: SATA max UDMA/133 abar m2048@0xf2627000 port
@Jeffrey
AFAIK, the Crucial M500 uses the Marvell 88SS9187 controller, while the
M550 and MX100 both use the Marvell 88SS9189 controller, and therefore
probably share the same firmware (or maybe the MX100 firmware was forked
off of the M550 firmware):
These new Crucial MX100 SSD series features
@Jeffrey, I don't know for sure, but I'd say it's likely that two drives
from the same manufacturer using the same controller will at the very
least be both derived from the same firmware code base, and their
firmware will therefore likely have a lot of bugs (and features) in
common. Since your
I'm getting these errors in Xubuntu 14.04 amd64 with nvidia binaries on
a Lenovo Thinkpad W510. I only noticed them because several times over
the past couple of months since installing Xubuntu 14.04, the machine
has suddenly, and quite randomly, remounted the filesystem to read only.
When that
I seem to be having the same problem with a Microsoft Sculpt Mobile
Mouse I just bought.
http://www.microsoft.com/hardware/en-ca/p/sculpt-mobile-mouse
This is in Xubuntu 14.04 amd64 on a Thinkpad W510. In the xfce Mouse
and Touchpad settings I get two entries for Microsoft Microsoft (R)
Nano
Just to clarify, it seems the hard resetting link and SError: {
CommWake DevExch } errors I was seeing had to do with me
connecting/disconnecting an external bus-powered portable eSATA drive
(ata6) that sometimes isn't correctly detected for some reason. The
sudden, random remounting of my main
16 matches
Mail list logo
