Do you know whether this problem was reported as debian bug for
kernel-package?
Regards, Karol
-686-pae first - segmentation faults occurred on 4.8.0-2-686-pae
- the image from 4.1.2017..
Maybe -1 is ok...
Regards, Karol
On 01/20/2017 02:54 PM, iqwue Wabv wrote:
Hello,
I'm using debian-testing and from about 2 weeks ago gnome sessions are
killed several times per day.
In syslog I see the following stacktrace:
snip
Jan 20 23:43:51 debian /usr/lib/gdm3/gdm-x-session[2454]: (EE) 3:
Hello,
I'm using debian-testing and from about 2 weeks ago gnome sessions are
killed several times per day.
In syslog I see the following stacktrace:
Jan 20 23:43:51 debian /usr/lib/gdm3/gdm-x-session[2454]: (EE)
Jan 20 23:43:51 debian /usr/lib/gdm3/gdm-x-session[2454]: (EE) Backtrace:
Jan
I finally got back to this ThinkPad R51 stability problem and was able
to definitively assign blame to a defective (at least in this box)
memory module. Defective memory was suggested on list as a probable
cause, so thank you. I first used the "mem=1G" kernel boot parameter to
limit memory
On Fri, 2015-06-19 at 11:55 -0700, Paul Ausbeck wrote:
for emacs23, or at least I can't find any. I'm not yet ready to install
emacs24 because I have some confidence that the problem won't occur with
emacs24, just as it doesn't occur with my built emacs23. But I'll still
have the problem
I apologize, Sven, for not following up on your suggestion. Or rather
for not mentioning my followup in my last post. I did look at the
available symbols packages. However, there aren't any symbols available
for emacs23, or at least I can't find any. I'm not yet ready to install
emacs24
On Wed, 2015-06-17 at 16:06 -0700, Paul Ausbeck wrote:
anyone have any insight into how one can build the identical Debian
binary to that installed?
My previous reply:
It definitively sounds like a hardware problem, but I just wanted to
address the above. Debian have quite a few -dbg
Thanks to everyone who read and/or responded to my query. I've got some
additional information that may prompt some additional discussion.
It seems there there is some chance that the problem is due to a RAM
fault. I had run memtest86+ before I made the initial posting and hadn't
gotten any
On Sun, 2015-06-14 at 14:49 -0700, Paul Ausbeck wrote:
I've looked at
compiling a debug version of emacs but that isn't trivial, still in
progress.
It definitively sounds like a hardware problem, but I just wanted to
address the above. Debian have quite a few -dbg packages. For emacs
there
On 14/06/15 23:40, Bob Proulx wrote:
In the old days computers would use ECC ram throughout.
ECC (in the strict sense) has never been ubiquitous.
Parity was quite common in certain timeframes, but parity won't stop
your system crashing if you get bitflips - it'll just make it crash
On 15/06/15 07:52 PM, Bob Proulx wrote:
Martin Read wrote:
Bob Proulx wrote:
In the old days computers would use ECC ram throughout.
ECC (in the strict sense) has never been ubiquitous.
At one time every computer I interfaced with had ECC. It was very
popular with me and everyone else I
Martin Read wrote:
Bob Proulx wrote:
In the old days computers would use ECC ram throughout.
ECC (in the strict sense) has never been ubiquitous.
At one time every computer I interfaced with had ECC. It was very
popular with me and everyone else I knew. :-)
Parity was quite common in
not really playable.
I'm reasonably certain that the problem is not configuration related.
I've used 3.2, 3.12 and 3.14 kernels on this box and all behave
similarly to the 3.16 kernel. I've also used Debian Jessie and though
segmentation faults are not reported, in the same creeping fashion
used 3.2, 3.12 and 3.14 kernels on this box and all behave similarly to the
3.16 kernel. I've also used Debian Jessie and though segmentation faults are
not reported, in the same creeping fashion the loader will begin to refuse
to load certain programs, and though right now I can't remember
Paul Ausbeck wrote:
I recently replaced the hard disk in my ThinkPad R51 with a solid
state drive
The ThinkPad R51 is a solid machine. Don't let anyone tell you
otherwise.
The symptom is that as time goes on more and more programs will cause a
segmentation fault while loading. For instance,
On Tue, 18 Sep 2012 02:21:51 +, Albretch Mueller wrote:
I am trying to install an application (huludesktop), but I either get a
Segmentation fault or Hulu Desktop could not locate the Flash plugin
message.
(...)
The error messages you get are similar to these:
GDK Failures - Hulu
I am trying to install an application (huludesktop), but I either get
a Segmentation fault or Hulu Desktop could not locate the Flash
plugin message.
You may easily spot the mistake or have suggestions based on the steps
I followed or you could let me know about either how to troubleshoot
that
On 15.03.09 18:07, Henrik Brautaset Aronsen wrote:
I just did a aptitude upgrade on an early lenny (testing) system to
lenny release, which has resulted in an unusable system. Several
programs (bind, apache, greylist and a couple of others) segfaults on
startup:
lenny is not testing
In 49bd35e3.7000...@henrik.synth.no, Henrik Brautaset Aronsen wrote:
I just did a aptitude upgrade on an early lenny (testing) system to
lenny release, which has resulted in an unusable system.
You made sure to change all occurrences of testing to lenny or stable
in your apt sources, right? I
I just did a aptitude upgrade on an early lenny (testing) system to
lenny release, which has resulted in an unusable system. Several
programs (bind, apache, greylist and a couple of others) segfaults on
startup:
Starting domain name service...: bind9/etc/rc2.d/S15bind9: line 44:
1359
Hi.
I am running Debian stable.
Suddenly when I run mplayer, xine, xmms, glxinfo and other I get
segmentation fault.
I have tried running both with and with Nvidia drivers.
I have run a memtest without any errors.
What can be causing this?
Best regards.
Rico.
--
To UNSUBSCRIBE, email to
On Thu, 13 Dec 2007 23:39:11 +0100
Rico Secada [EMAIL PROTECTED] wrote:
Solution found!
Can someone please explain why doing this:
touch /etc/ld.so.nohwcap
Solves the problem?
Hi.
I am running Debian stable.
Suddenly when I run mplayer, xine, xmms, glxinfo and other I get
segmentation
2007/12/13, Rico Secada [EMAIL PROTECTED]:
On Thu, 13 Dec 2007 23:39:11 +0100
Rico Secada [EMAIL PROTECTED] wrote:
Solution found!
Can someone please explain why doing this:
touch /etc/ld.so.nohwcap
Solves the problem?
Hi.
I am running Debian stable.
Suddenly when I run
Rico Secada [EMAIL PROTECTED] writes:
On Thu, 13 Dec 2007 23:39:11 +0100
Rico Secada [EMAIL PROTECTED] wrote:
Solution found!
Can someone please explain why doing this:
touch /etc/ld.so.nohwcap
Solves the problem?
Well, that causes the dynamic linker to use the non-optimized version
of
On Thu, 13 Dec 2007 16:57:16 -0600
Sergio Cuéllar Valdés [EMAIL PROTECTED] wrote:
2007/12/13, Rico Secada [EMAIL PROTECTED]:
On Thu, 13 Dec 2007 23:39:11 +0100
Rico Secada [EMAIL PROTECTED] wrote:
Solution found!
Can someone please explain why doing this:
touch /etc/ld.so.nohwcap
I am getting segmentation faults with Gnome.
This is a new install of Debian woody on a new but used machine.
I'm new to Debian.
Initially had trouble with X and did apt-get install --reinstall
xserver-xfree86
It now works.
On arriving in Gnome I get the segmentation faults.
I have apt-get remove
downloaded the source and built
kernel-2.6.0-test9. With this kernel I was unable to access my Netgear
MA311 PCI Adapter. To solve this I downloaded and installed
linux-wlan-ng-0.2.1-pre14 from the tarball. At this point I began to
have problems - segmentation faults - so I tried to go back
Hi,
I just installed emacs on a woody system. When I do a little bit of
editing it crashes with:
Fatal error (11).Segmentation fault
How can I get more information to see what the problem is?
Rudy
--
Rudy Gevaert[EMAIL PROTECTED]
Web page
On Wed, 30 Oct 2002 20:40:08 -0800
Paul Mackinney [EMAIL PROTECTED] wrote:
Colin Watson declaimed:
On Tue, Oct 29, 2002 at 04:35:15PM -0800, Paul Mackinney wrote:
I've been running Sid, for some time, lately I've started getting
segmentaion faults when I run apropos, as in the following:
On Thu, Oct 31, 2002 at 02:16:45AM -0600, Gerald Livingston wrote:
On Wed, 30 Oct 2002 20:40:08 -0800
Paul Mackinney [EMAIL PROTECTED] wrote:
Thanks, Colin. I did look in the bug tracker before posting,
the search mechanism came up empty on open bugs with 'apropos'...
The bugs are
Colin Watson declaimed:
On Tue, Oct 29, 2002 at 04:35:15PM -0800, Paul Mackinney wrote:
I've been running Sid, for some time, lately I've started getting
segmentaion faults when I run apropos, as in the following:
$ apropos hyphenation
Segmentation fault
$
This has so far
I've been running Sid, for some time, lately I've started getting
segmentaion faults when I run apropos, as in the following:
$ apropos hyphenation
Segmentation fault
$
When I run with the debug flag, I get a bunch of normal-looking messages
about paths, ending with
adding
Paul Mackinney wrote:
I've been running Sid, for some time, lately I've started getting
segmentaion faults when I run apropos, as in the following:
$ apropos hyphenation
Segmentation fault
$
When I run with the debug flag, I get a bunch of normal-looking messages
about paths, ending
On Tue, Oct 29, 2002 at 04:35:15PM -0800, Paul Mackinney wrote:
I've been running Sid, for some time, lately I've started getting
segmentaion faults when I run apropos, as in the following:
$ apropos hyphenation
Segmentation fault
$
This has so far been reported as a bug six times,
I've been trying to run Kmud and it was working fine for
quite a while. The other night I started getting
segmentation faults. The exact error message is:
QGList::locate: Index -1 out of range
./kmud: line 21: 4573 Segmentation fault
$KDEDIR/gin/kmud $1
What could be causing
I've been trying to run Kmud and it was working fine for
quite a while. The other night I started getting
segmentation faults. The exact error message is:
QGList::locate: Index -1 out of range
./kmud: line 21: 4573 Segmentation fault
$KDEDIR/gin/kmud $1
What could be causing
On my machine, two or three different programs have given me segmentation
faults. The two that I remember are Enlightenment and bwBASIC. The
segmentation fault in Enlightenment only happened once, and Enlightenment
was removed soon thereafter.
In bwBASIC, however, I was able to reproduce
On Tue, Dec 18, 2001 at 09:59:19PM -0500, Seneca Cunningham wrote:
[what causes a segmentation fault]
A segmentation fault (also called a seg fault, or SEGV) occurs when a
program tries to access memory it is not allowed to access. For
example dereferencing a null pointer, or dereferencing a
* Seneca Cunningham ([EMAIL PROTECTED]) [011218 18:59]:
[what causes segmentation faults?]
The short answer is: a bug in the program. A correctly-written program
should never die with a segmentation violation. If you're just a user,
and not a programmer, that's probably all you need to know
, was planning to compile a new kernel. Then someone unplugged
the machine. Eventually I gave up, and started trying to reinstall.
After a few tries, still getting segmentation faults, and these kinds of long
messages, I pulled out one dimm. The system worked better. But eventually I
did get
This machine has been running Debian Woody pretty nicely for a few months.
Recently,
segfaults have been plaguing me. I suspect Hardware, but must ask
for advice.
Sounds like a possbile memory problem, run memtest all as root to
find out.
regards,
Volker
--
People with narrow minds
I have recently upgraded my motherboard and CPU...after doing so I have been
unable to get into Window Maker (I really do not think that there is a tie
between the two, but that is the only thing that I did before this happened).
After I log into the system Window Maker begins to open up, and
on Sun, Nov 05, 2000 at 08:40:59PM -0700, Matheson ([EMAIL PROTECTED]) wrote:
Wow,
I get segmentation faults whenever anything (or me) tries to remove
stuff (rm). When by system boots up, a see up bunch of segmentation
faults, cause certain things try to rm -f, and now when I try to log
Please respond on-list.
Please include replied-to message, quoted (postfix your response).
List included in recpipients.
Reply-to directed to list.
on Mon, Nov 06, 2000 at 02:50:26PM -0700, Matheson ([EMAIL PROTECTED]) wrote:
I don't know what debsums is, but if I run `strace rm`, it just tells
Wow,
I get segmentation faults whenever anything (or me)
tries to remove stuff (rm). When by system boots up, a see up bunch of
segmentation faults,cause certain things try to rm -f, and now when I try
to log in I get:
tux login: root
System bootup in progress - please
wait
Password:
I
On Fri, Mar 17, 2000 at 01:12:01PM -0800, Bart Friederichs generated a stream
of 1s and 0s:
Hi,
Here another one from the guy that can't get Debian installed due to a bad
PC (I think). When I run dselect and it starts installing all goes well
until one of the packages gets a segfault
Hi,
Here another one from the guy that can't get Debian installed due to a bad
PC (I think). When I run dselect and it starts installing all goes well
until one of the packages gets a segfault (dpkg does actually) and then my
whole PC crashes. I tried again and it crashed on the same
Hi,
Here another one from the guy that can't get Debian installed due to a bad
PC (I think). When I run dselect and it starts installing all goes well
until one of the packages gets a segfault (dpkg does actually) and then my
whole PC crashes. I tried again and it crashed on the same package (m4
On Sat, Oct 23, 1999 at 08:39:19PM +, John wrote:
Have been unable to find any definition and write-up on
'segmentation faults'. I have encountered this whilst trying
a package installation as part of the learning process -
the matter is not critical, but nontheless I would like
Have been unable to find any definition and write-up on
'segmentation faults'. I have encountered this whilst trying
a package installation as part of the learning process -
the matter is not critical, but nontheless I would like to
understand what is involved in case I meet this error
when
| Ditto!
|
| It only happens when I telnet in from work. Thanks - I assume I
| don't need to worry about it.
I've had the problem even when running apt-get (0.3.7, compiled for
slink) from the console accessing a (partial) archive on the local
system. I don't think it was caused by faulty
I am getting unexplained segmentation faults with two programs I installed from
source. How can I find out exactly what is causing them?
It has to be a problem with my system, because I was using these programs (kget
is one) with no problems before I had to reinstall Debian.
thanks
--
Andrew
On Mon, 28 Dec 1998, Jim McCloskey wrote:
[ upgraded from bo to hamm ]
There were small problems here and there, but nothing more than I
expected, and all the diagnostics I ran (apt-get check especially)
gave (and give) no indication of trouble.
There is one big problem though---trying to
Hello.
On Sunday, I finally upgraded my home system from bo to hamm (I've
been postponing the upgrade because I had a lot of important work to
finish, and I didn't want to risk breaking the system until that was
done).
I used apt-get and the official Debian CD (it came with the new
edition of
Thank you for the assistance.
I am getting the segmentation faults when executing 1) arena 2)xquake
3)squake There may be others. When squake faults it gives the message
svgalib: Signal 11: segmentatin fault recieved. The vast majority of
programs. both x and non x, run fine. I suspect
Could anyone please answer these questions about segmentation faults?
What is a Segmentation Fault? How do I trace its cause? How are they
normally fixed. Why don't I get a core dump when they happen? Thank you
On Thu, Dec 10, 1998 at 06:22:54PM -0500, Tom wrote:
Could anyone please answer these questions about segmentation faults?
What is a Segmentation Fault? How do I trace its cause? How are they
normally fixed. Why don't I get a core dump when they happen? Thank you
It's a memory access
On Mon, Sep 28, 1998 at 01:53:48AM -0700, George Bonser wrote:
On Mon, 28 Sep 1998, E.L. Meijer (Eric) wrote:
This can indeed be the case. If you have more than one dimm, or more
than two simms, you can test this by removing half of your memory, see
if you get the same errors, then
Hi,
My experience :
Some time ago I bought 2*16 Mo of 60ns memory. I had them to my 2*8 Mo of 60ns
Memory. After reboot, the system send me error messages, especially concerning
the harddisk. I tried a lot of thing as inverting memories, asking for
new ones at my
vendor, installing the setx86
Sorry to bother everyone here, but I have been getting a lot of
segmentation faults lately and I was wondering what causes them. I think I
have heard on this list before that it is causes by bad memory chips and
just wanted to verify this.
This can indeed be the case. If you have
Sorry to bother everyone here, but I have been getting a lot of
segmentation faults lately and I was wondering what causes them. I think I
have heard on this list before that it is causes by bad memory chips and
just wanted to verify this.
Also have been getting general
On Mon, 7 Sep 1998, C.J.LAWSON wrote:
Humm,
This doesn't sound too pretty ... did you watch what was
happening to your memory usage when the program was running?
Yes. No problem. I have 24 meg ram + about 60 meg swap space.
Johann
On Mon, 7 Sep 1998, C.J.LAWSON wrote:
You might want to chech if you have enough memory (if not you may want to
do something about your swap space). Run free when you try and start one
of those 'seggy' programs
After your message I changed taper's memory configuration and at first it
seemed
I never had such a lot of segmentation faults before I have upgraded to
Debian 2.0. I even had te push the reset-button after pine made the
computer hang and there was no response to the keyboard or the mouse. The
past few weeks reminded me of the time I was using Windows 3.1 for a lot
of my
update-menus is giving me segmentation faults (core dumped) ... I recently
upgraded several programs (dselect wanted to/hamm distribution) and now it
doesn't work. Anyone have an idea on what could be wrong?
-Paul
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to
[EMAIL
-BEGIN PGP SIGNED MESSAGE-
On Tue, 7 Oct 1997, Paul Miller wrote:
update-menus is giving me segmentation faults (core dumped) ... I recently
upgraded several programs (dselect wanted to/hamm distribution) and now it
doesn't work. Anyone have an idea on what could be wrong?
Yes
I had written earlier that I've been getting seg faults when trying to
run programs from rxvt since updating hamm last night and that window
manager programs ran fine but that isn't the case.
I have found that Image magik seg faults from the menu.
Since I just got re-subscribed to the list I'll
I was able to install Star Office. I was able to print a WinWord 2
document, and happily it looked much as it would originally. However,
when trying the Thesaurus, and worse, when trying to convert the
Winword file to any other format, a segmentation fault was
experienced.
There has been some
---
Using FTP to check directories...(stop with ^C)
Connecting to ftp.debian.org...
query/setup script was terminated by a signal: Segmentation fault.
(It left a coredump.)
Press RETURN to continue.
---
I'm using the dpkg-ftp_1.4.9.deb and dpkg_1.4.0.19.deb packages from the
hamm distribution.
never mind about this message. I figured it out; what I needed was a
never version of ldso (or something else I installed)...
-Paul
On Thu, 21 Aug 1997, Paul Miller wrote:
---
Using FTP to check directories...(stop with ^C)
Connecting to ftp.debian.org...
query/setup script was
Hi,
Bruce == Bruce Perens [EMAIL PROTECTED] writes:
From William Chow [EMAIL PROTECTED]
Time to RTFM, there, Corey.
Bruce That's RTM on this list, please.
What, You don't think our manuals are Fine? ;-)
manoj
--
...The Universe is thronged with fire and light, And we but
On 26 Feb 1997, Manoj Srivastava wrote:
Hi,
Bruce == Bruce Perens [EMAIL PROTECTED] writes:
From William Chow [EMAIL PROTECTED]
Time to RTFM, there, Corey.
Bruce That's RTM on this list, please.
What, You don't think our manuals are Fine? ;-)
manoj
--
void
I cna dig the whole $user/.xinitrc but everythin was fine last week . .
the machine was up and running for about a month also I only ran X as root
as a test
On Wed, 26 Feb 1997, Corey Allert wrote:
also Xfree86 doesn't run properly .. . it will as root but as any other
user X starts as if
also Xfree86 doesn't run properly .. . it will as root but as any other
user X starts as if no window manager is set . . and typing startx -exec
fvwm2 will bring up the correct gui but there is no command prompt in the
xterm . . . freaky eh??
Corey A.
[EMAIL PROTECTED]
This is a Repost
Hi all:
here is my problem, a machine at my school is running Debian 1.2 (upgraded
from 1.1) the current kernel is 2.0.6, libc is 5.4.20, the problem is any
attempts to send mail from pine results in a segmentation fault. I've
noticed this since I've attempted to install
On Wed, 26 Feb 1997, Corey Allert wrote:
also Xfree86 doesn't run properly .. . it will as root but as any other
user X starts as if no window manager is set . . and typing startx -exec
fvwm2 will bring up the correct gui but there is no command prompt in the
xterm . . . freaky eh??
Time
From: William Chow [EMAIL PROTECTED]
Time to RTFM, there, Corey.
That's RTM on this list, please.
Bruce
--
Bruce Perens K6BP [EMAIL PROTECTED] 510-215-3502
Finger [EMAIL PROTECTED] for PGP public key.
PGP fingerprint = 88 6A 15 D0 65 D4 A3 A6 1F 89 6A 76 95 24 87 B3
--
TO
Gee, what's wrong with a suggestion to Read The Fine Manuals???
Oh, it's read the _fine_ manual, is it? Everything I know is wrong!
One would hope that we could answer questions on this list in a polite
and respectful manner, especially since there's absolutely no way that
we could ever expect
Hi all:
here is my problem, a machine at my school is running Debian 1.2 (upgraded
from 1.1) the current kernel is 2.0.6, libc is 5.4.20, the problem is any
attempts to send mail from pine results in a segmentation fault. I've
noticed this since I've attempted to install Majordomo(ugh!) ok I'm
produces segmentation faults
Hi all:
here is my problem, a machine at my school is running Debian 1.2 (upgraded
from 1.1) the current kernel is 2.0.6, libc is 5.4.20, the problem is any
attempts to send mail from pine results in a segmentation fault. I've
noticed this since I've attempted to install
Hi there,
I have Debian1.2 running kernel 2.0.27. The tar package version is
1.11.8-5.
I can create multipy floppy archive using 'tar cvMf /dev/fd0' but
NOT retrieving it using 'tar xvMf /dev/fd0'.
I always get 'Segmentation faults and then core dumped' when I tried
the latter ??!!.
I think
82 matches
Mail list logo
