Re: apparent crashes persist.
On Wed, Jul 26, 2006 at 08:59:55AM -0400, Lennart Sorensen wrote: > On Wed, Jul 26, 2006 at 08:04:53AM -0400, [EMAIL PROTECTED] wrote: > > After much further trying (documented to some extent in this thread) I'm > > back to suspecting the software again. I've summarized the state of > > affairs as it's known as of now and filed it as a bug against xorg: > > > > bug #379480: Mouse and partial keyboard freeze on AMD64 > > > > Somehow the pattern of failure seems wrong for a hardware problem -- > > not really random enough, it seems to affect things that (I think) > > are different pieces of hardware (USB mouse and pre-PS2 keyboard), and > > it affects things differently that (I think) are the same piece of > > hardware (i.e. different keyboard keys behave differently after the > > "crash"). > > > > Advice on tracking it down, and experiences others have on ASUS > > A8N-VM-UAYGZ motherboards are still very welcome, of course, but perhaps > > I should move this discussion to the xorg mainling list. > > Are you using ps2 or usb mouse and keyboard? > > Is the bios up to date? > > What is a pre-ps2 keyboard? ps2 keyboards have a small round 6 pin > connector just like ps2 mice. Old AT keyboards had a 5 pin din > connector that was quite a bit larger. Does anyone still use those? > > Is usb legacy support enabled in the bios? (if you don't use a usb > keyboard, try turning it off). > > Which window manager are you running? For a while I saw a lot of > lockups when I tried to run firefox under kde. Use anything other than > kde, and crashes/lockups went away. That was a few months ago though. > Seems better now. New news: I found someone with the sam motherboard, and he has Linux working. No crashes for him. It turns out he is using Ubuntu Dapper. So I burned myself an Ubuntu Dapper Draks live CD, and booted it, and I can do some of the things that crash my Debian installation. So it looks like we do have a software problem. To be more sure, I'll have to install Ubuntu, and set it up to do everything I've got set up on Debian, including my home directory and user files and so forth. I think I still have a 1G partition I can use for everything except /usr and /home, enough room in a volume group to create a new /usr, and I'll pich the same /home. ANyone see disasters coming? I should probably append a note that I get no crashes using the Ubuntu live CD to my bug report agains Debian xorg. This should narrow the possibilities a bit. -- hendrik > > -- > Len Sorensen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: apparent crashes persist.
On Thu, Jul 27, 2006 at 08:28:12AM +1000, Alexander Samad wrote: > On Wed, Jul 26, 2006 at 11:05:02AM -0400, [EMAIL PROTECTED] wrote: > > On Wed, Jul 26, 2006 at 08:59:55AM -0400, Lennart Sorensen wrote: > > > On Wed, Jul 26, 2006 at 08:04:53AM -0400, [EMAIL PROTECTED] wrote: > > > > After much further trying (documented to some extent in this thread) > > > > I'm > > > > back to suspecting the software again. I've summarized the state of > > > > affairs as it's known as of now and filed it as a bug against xorg: > > > > > > > > bug #379480: Mouse and partial keyboard freeze on AMD64 > > > > > > > > Somehow the pattern of failure seems wrong for a hardware problem -- > > > > not really random enough, it seems to affect things that (I think) > > > > are different pieces of hardware (USB mouse and pre-PS2 keyboard), and > > > > it affects things differently that (I think) are the same piece of > > > > hardware (i.e. different keyboard keys behave differently after the > > > > "crash"). > > > > > > > > Advice on tracking it down, and experiences others have on ASUS > > If you have another machine then you could push the kernel messages out > ttyS0 and have the second machine hooked into ttyS0 with minitab and log > all the messages, that way you would capture all the error information ! I did mention in the bug report that if an xterm has keyboard focus at the time of the "crash", it retains it and I can go on executing shell commands. This is how I got the dmesg output in the bug report -- after the "crash". Mouse frozen, ctl-alt-function keys dead, but ordinary ASCII still alive. But this suggestion is good for the times that an xterm isn't active... -- hendrik > > > > > A8N-VM-UAYGZ motherboards are still very welcome, of course, but > > > > perhaps > > > > I should move this discussion to the xorg mainling list. > > > > > > Are you using ps2 or usb mouse and keyboard? > > > > A usb nouse > > > > > > > > Is the bios up to date? > > > > > > What is a pre-ps2 keyboard? ps2 keyboards have a small round 6 pin > > > connector just like ps2 mice. Old AT keyboards had a 5 pin din > > > connector that was quite a bit larger. > > > > A five-pin din connector., with an adapter to plug into the ps2 port on > > the comnputer. > > > > > Does anyone still use those? > > > > Yes. Best keyboard I've ever owned. Except for my Alphasmart which I > > bought about a year ago. > > > > > > > > Is usb legacy support enabled in the bios? (if you don't use a usb > > > keyboard, try turning it off). > > > > > > Which window manager are you running? For a while I saw a lot of > > > lockups when I tried to run firefox under kde. Use anything other than > > > kde, and crashes/lockups went away. That was a few months ago though. > > > Seems better now. > > > > icewm, fvwm. Both had the same problems. Never used kde. The problem > > does seem to be less severe these days than a few months ago, though. > > > > > > > > -- > > > Len Sorensen > > > > > > -- > > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > > > > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: apparent crashes persist.
On Wed, Jul 26, 2006 at 11:05:02AM -0400, [EMAIL PROTECTED] wrote: > On Wed, Jul 26, 2006 at 08:59:55AM -0400, Lennart Sorensen wrote: > > On Wed, Jul 26, 2006 at 08:04:53AM -0400, [EMAIL PROTECTED] wrote: > > > After much further trying (documented to some extent in this thread) I'm > > > back to suspecting the software again. I've summarized the state of > > > affairs as it's known as of now and filed it as a bug against xorg: > > > > > > bug #379480: Mouse and partial keyboard freeze on AMD64 > > > > > > Somehow the pattern of failure seems wrong for a hardware problem -- > > > not really random enough, it seems to affect things that (I think) > > > are different pieces of hardware (USB mouse and pre-PS2 keyboard), and > > > it affects things differently that (I think) are the same piece of > > > hardware (i.e. different keyboard keys behave differently after the > > > "crash"). > > > > > > Advice on tracking it down, and experiences others have on ASUS If you have another machine then you could push the kernel messages out ttyS0 and have the second machine hooked into ttyS0 with minitab and log all the messages, that way you would capture all the error information ! > > > A8N-VM-UAYGZ motherboards are still very welcome, of course, but perhaps > > > I should move this discussion to the xorg mainling list. > > > > Are you using ps2 or usb mouse and keyboard? > > A usb nouse > > > > > Is the bios up to date? > > > > What is a pre-ps2 keyboard? ps2 keyboards have a small round 6 pin > > connector just like ps2 mice. Old AT keyboards had a 5 pin din > > connector that was quite a bit larger. > > A five-pin din connector., with an adapter to plug into the ps2 port on > the comnputer. > > > Does anyone still use those? > > Yes. Best keyboard I've ever owned. Except for my Alphasmart which I > bought about a year ago. > > > > > Is usb legacy support enabled in the bios? (if you don't use a usb > > keyboard, try turning it off). > > > > Which window manager are you running? For a while I saw a lot of > > lockups when I tried to run firefox under kde. Use anything other than > > kde, and crashes/lockups went away. That was a few months ago though. > > Seems better now. > > icewm, fvwm. Both had the same problems. Never used kde. The problem > does seem to be less severe these days than a few months ago, though. > > > > > -- > > Len Sorensen > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > > signature.asc Description: Digital signature
Re: apparent crashes persist.
On Wed, Jul 26, 2006 at 08:59:55AM -0400, Lennart Sorensen wrote: > On Wed, Jul 26, 2006 at 08:04:53AM -0400, [EMAIL PROTECTED] wrote: > > After much further trying (documented to some extent in this thread) I'm > > back to suspecting the software again. I've summarized the state of > > affairs as it's known as of now and filed it as a bug against xorg: > > > > bug #379480: Mouse and partial keyboard freeze on AMD64 > > > > Somehow the pattern of failure seems wrong for a hardware problem -- > > not really random enough, it seems to affect things that (I think) > > are different pieces of hardware (USB mouse and pre-PS2 keyboard), and > > it affects things differently that (I think) are the same piece of > > hardware (i.e. different keyboard keys behave differently after the > > "crash"). > > > > Advice on tracking it down, and experiences others have on ASUS > > A8N-VM-UAYGZ motherboards are still very welcome, of course, but perhaps > > I should move this discussion to the xorg mainling list. > > Are you using ps2 or usb mouse and keyboard? A usb nouse > > Is the bios up to date? > > What is a pre-ps2 keyboard? ps2 keyboards have a small round 6 pin > connector just like ps2 mice. Old AT keyboards had a 5 pin din > connector that was quite a bit larger. A five-pin din connector., with an adapter to plug into the ps2 port on the comnputer. > Does anyone still use those? Yes. Best keyboard I've ever owned. Except for my Alphasmart which I bought about a year ago. > > Is usb legacy support enabled in the bios? (if you don't use a usb > keyboard, try turning it off). > > Which window manager are you running? For a while I saw a lot of > lockups when I tried to run firefox under kde. Use anything other than > kde, and crashes/lockups went away. That was a few months ago though. > Seems better now. icewm, fvwm. Both had the same problems. Never used kde. The problem does seem to be less severe these days than a few months ago, though. > > -- > Len Sorensen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: apparent crashes persist.
On Wed, Jul 26, 2006 at 08:04:53AM -0400, [EMAIL PROTECTED] wrote: > After much further trying (documented to some extent in this thread) I'm > back to suspecting the software again. I've summarized the state of > affairs as it's known as of now and filed it as a bug against xorg: > > bug #379480: Mouse and partial keyboard freeze on AMD64 > > Somehow the pattern of failure seems wrong for a hardware problem -- > not really random enough, it seems to affect things that (I think) > are different pieces of hardware (USB mouse and pre-PS2 keyboard), and > it affects things differently that (I think) are the same piece of > hardware (i.e. different keyboard keys behave differently after the > "crash"). > > Advice on tracking it down, and experiences others have on ASUS > A8N-VM-UAYGZ motherboards are still very welcome, of course, but perhaps > I should move this discussion to the xorg mainling list. Are you using ps2 or usb mouse and keyboard? Is the bios up to date? What is a pre-ps2 keyboard? ps2 keyboards have a small round 6 pin connector just like ps2 mice. Old AT keyboards had a 5 pin din connector that was quite a bit larger. Does anyone still use those? Is usb legacy support enabled in the bios? (if you don't use a usb keyboard, try turning it off). Which window manager are you running? For a while I saw a lot of lockups when I tried to run firefox under kde. Use anything other than kde, and crashes/lockups went away. That was a few months ago though. Seems better now. -- Len Sorensen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: apparent crashes persist.
On Fri, Jun 23, 2006 at 03:22:18PM -0400, [EMAIL PROTECTED] wrote: On Friday 23 June 2006 14:16, [EMAIL PROTECTED] wrote: > It's been a while now, about five months and I still haven't gor my > AMD64 working properly > . > Evidently, something is hogging some critical resource, possibly the CPU > (the usual suspect) but it could also be a networking resource, since > that's what the mouse and ssh seem to have in common > . > When logged in locally using the X server it crashes. I suspect a > measure of software involvement in the crashes, because when I upgraded > the nvidia drivers from 1.0.8756-1 to 1.0.8762-2 and also upgraded the > kernel from 2.6.12 to 2.6.15 the crashes became less frequent. After much further trying (documented to some extent in this thread) I'm back to suspecting the software again. I've summarized the state of affairs as it's known as of now and filed it as a bug against xorg: bug #379480: Mouse and partial keyboard freeze on AMD64 Somehow the pattern of failure seems wrong for a hardware problem -- not really random enough, it seems to affect things that (I think) are different pieces of hardware (USB mouse and pre-PS2 keyboard), and it affects things differently that (I think) are the same piece of hardware (i.e. different keyboard keys behave differently after the "crash"). Advice on tracking it down, and experiences others have on ASUS A8N-VM-UAYGZ motherboards are still very welcome, of course, but perhaps I should move this discussion to the xorg mainling list. -- hendrik -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: apparent crashes persist.
On Thu, Jul 13, 2006 at 07:21:06AM -0400, [EMAIL PROTECTED] wrote: > On Wed, Jul 12, 2006 at 09:43:55PM -0500, Jaime Ochoa Malag?n wrote: > > An importat thing about havig ssh acces is the problem is not wqith > > the machine is with your applications, try vesa X driver... > > > > You could have only a unstable X... > > I'm currently running the vesa X driver. Previously I had the problem > with the nvidia X drivers. > > The problem shows up as dead mouse pointer. Which maked X pretty > useless. But if the system is in a state where it might expect keyboard > input, it continues to react to the keyboard. I can continue to enter a > URL into firefox (though it won't load a new one when I press enter), > and the tab key allows me to change panes in firefox -- tab between ads, > images, and so forth. However, the ctrl-alt-F* keys no longer work. > > In fact, the specificity of the problem suggests that it is probably not > a RAM problem at all. But it doesn't rule out other hardware, such as > maybe the mouse itself, or the USB controller the mouse plugs into. And it doesn't seem to be a problem with 64-bit cleanlines or with leftovers from tortuous upgrades. I installed 32-bit etch on a spare partition, with the same failures. It might be hardware, but probably not RAM. It might be a device-driver for one of the new nvidia chips on the AMD-64 motherboard (the reason why I'm using etch instead of stable). Still no idea how to track this down. -- hendrik -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: apparent crashes persist.
On Thu, Jul 13, 2006 at 07:21:06AM -0400, [EMAIL PROTECTED] wrote: > The problem shows up as dead mouse pointer. Which maked X pretty > useless. But if the system is in a state where it might expect keyboard > input, it continues to react to the keyboard. I can continue to enter a > URL into firefox (though it won't load a new one when I press enter), > and the tab key allows me to change panes in firefox -- tab between ads, > images, and so forth. However, the ctrl-alt-F* keys no longer work. Maybe a workaround: :-) Would there be an X window manager that can do everything without a mouse? Or one that will work with two mice (in case only one mouse dies at a time? -- hendrik -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: apparent crashes persist.
Try a X enviroment running inside a chroot or an installation 32bits... On 7/13/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: On Wed, Jul 12, 2006 at 09:43:55PM -0500, Jaime Ochoa Malag?n wrote: > An importat thing about havig ssh acces is the problem is not wqith > the machine is with your applications, try vesa X driver... > > You could have only a unstable X... I'm currently running the vesa X driver. Previously I had the problem with the nvidia X drivers. The problem shows up as dead mouse pointer. Which maked X pretty useless. But if the system is in a state where it might expect keyboard input, it continues to react to the keyboard. I can continue to enter a URL into firefox (though it won't load a new one when I press enter), and the tab key allows me to change panes in firefox -- tab between ads, images, and so forth. However, the ctrl-alt-F* keys no longer work. In fact, the specificity of the problem suggests that it is probably not a RAM problem at all. But it doesn't rule out other hardware, such as maybe the mouse itself, or the USB controller the mouse plugs into. -- hendrik > > Good luck > > On 7/12/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > >On Sun, Jun 25, 2006 at 02:53:17PM +, Dimitris Lampridis wrote: > >> On Sunday 25 June 2006 12:15, [EMAIL PROTECTED] wrote: > >> > Left it running overnight. 9 full passes through memory, *no* faults > >> > detected. > >> > > >> > >> If you search recent posts on the list, you'll see that I also had > >problems > >> with my memory and they were not discovered by memtest. So, as others > >have > >> suggested too, maybe its better to open your box, remove memories and try > >> them one by one for some time. If the problem persists with every single > >> memory module, then either your memories are OK, or all of them are bad > >(but > >> the latter, being such an extreme case, would have been probably > >detected by > >> memtest...) > > > >Took a while to find just how to reduce the number of memories from 2 to > >1. It turns out to be possible, but against all intuition the single > >memory had to be installed in the second slot, which was named A1. > > > >Got the machine wo work for awhile with only one G memory, then it > >crashed in the usual way. Tried it with the other memory in that slot, > >and it worked for longer, but still got around to crashing today. > > > >It crashes quickly when running Pan, when using mozilla firefox with > >complex web pages, and slowly when using xjig. Other things probably > >crash it too. > > > >It took a while to get to the tests involving Pan and the complex > >web0sites, because just to complicate things the DSL line I use for > >network died and the phone company had to get around to fixing it. > >But they crashed quite quickly when I finally got around to it. > > > >I have an idea that it is network activity (the mouse in X also talks on > >the net internally, I believe) during graphics activity that does it in. > >No definitive evidence for that, but I do seem to be doing both when it > >goes down. > > > >Once again, when it crashes, I can sometimes still manage to use a ssh > >connection to get in from elsewhere. What information should I collect, > >and how should I analyse it? > > > >> > >> What is ur memory configuration by the way? I remember you said 2G, but > >is it > >> 2x1G, 4x512M, something else? and what about the manufacturer? > > > >2x1G. But now I'm running 1x1G. Kingston memory. > > > >memtest86+ never finds a thing wrong. > > > >Could be, of course that it's other hardware. > > -- Engañarse por amor es el engaño más terrible; es una pérdida eterna para la que no hay compensación ni en el tiempo ni en la eternidad. Kierkegaard Jaime Ochoa Malagón Integrated Technology Tel: (55) 52 54 26 10
Re: apparent crashes persist.
[EMAIL PROTECTED] writes: > Once again, when it crashes, I can sometimes still manage to use a ssh > connection to get in from elsewhere. What information should I collect, > and how should I analyse it? Have you tried using completly new ram from a different vendor or different make (e.g. single sided instead of double sided or vice versa)? We had a 256 nodes cluster where we found that the ram was plain incompatible and had to swap 2048 DIMMs to a different vendor to get any stability. Even then we still had a 5% failure rate per DIMM in a week of stress testing. MfG Goswin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: apparent crashes persist.
On Wed, Jul 12, 2006 at 09:43:55PM -0500, Jaime Ochoa Malag?n wrote: > An importat thing about havig ssh acces is the problem is not wqith > the machine is with your applications, try vesa X driver... > > You could have only a unstable X... I'm currently running the vesa X driver. Previously I had the problem with the nvidia X drivers. The problem shows up as dead mouse pointer. Which maked X pretty useless. But if the system is in a state where it might expect keyboard input, it continues to react to the keyboard. I can continue to enter a URL into firefox (though it won't load a new one when I press enter), and the tab key allows me to change panes in firefox -- tab between ads, images, and so forth. However, the ctrl-alt-F* keys no longer work. In fact, the specificity of the problem suggests that it is probably not a RAM problem at all. But it doesn't rule out other hardware, such as maybe the mouse itself, or the USB controller the mouse plugs into. -- hendrik > > Good luck > > On 7/12/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > >On Sun, Jun 25, 2006 at 02:53:17PM +, Dimitris Lampridis wrote: > >> On Sunday 25 June 2006 12:15, [EMAIL PROTECTED] wrote: > >> > Left it running overnight. 9 full passes through memory, *no* faults > >> > detected. > >> > > >> > >> If you search recent posts on the list, you'll see that I also had > >problems > >> with my memory and they were not discovered by memtest. So, as others > >have > >> suggested too, maybe its better to open your box, remove memories and try > >> them one by one for some time. If the problem persists with every single > >> memory module, then either your memories are OK, or all of them are bad > >(but > >> the latter, being such an extreme case, would have been probably > >detected by > >> memtest...) > > > >Took a while to find just how to reduce the number of memories from 2 to > >1. It turns out to be possible, but against all intuition the single > >memory had to be installed in the second slot, which was named A1. > > > >Got the machine wo work for awhile with only one G memory, then it > >crashed in the usual way. Tried it with the other memory in that slot, > >and it worked for longer, but still got around to crashing today. > > > >It crashes quickly when running Pan, when using mozilla firefox with > >complex web pages, and slowly when using xjig. Other things probably > >crash it too. > > > >It took a while to get to the tests involving Pan and the complex > >web0sites, because just to complicate things the DSL line I use for > >network died and the phone company had to get around to fixing it. > >But they crashed quite quickly when I finally got around to it. > > > >I have an idea that it is network activity (the mouse in X also talks on > >the net internally, I believe) during graphics activity that does it in. > >No definitive evidence for that, but I do seem to be doing both when it > >goes down. > > > >Once again, when it crashes, I can sometimes still manage to use a ssh > >connection to get in from elsewhere. What information should I collect, > >and how should I analyse it? > > > >> > >> What is ur memory configuration by the way? I remember you said 2G, but > >is it > >> 2x1G, 4x512M, something else? and what about the manufacturer? > > > >2x1G. But now I'm running 1x1G. Kingston memory. > > > >memtest86+ never finds a thing wrong. > > > >Could be, of course that it's other hardware. > > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: apparent crashes persist.
[EMAIL PROTECTED] wrote: Once again, when it crashes, I can sometimes still manage to use a ssh connection to get in from elsewhere. What information should I collect, and how should I analyse it? Start with 'dmesg'. Look for anything erroneous and/or send the output to the list. You can also check /var/log/messages after rebooting, but problems might not get written there if the kernel is somehow unable to write to the disk. What is ur memory configuration by the way? I remember you said 2G, but is it 2x1G, 4x512M, something else? and what about the manufacturer? 2x1G. But now I'm running 1x1G. Kingston memory. memtest86+ never finds a thing wrong. Could be, of course that it's other hardware. Have you tried stressing your CPU? 1. make sure your CPU isn't running too hot 2. # apt-get install cpuburn 3. $ burnK7 4. keep an eye on your CPU temperature and see if your system crashes soon. -Corey -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: apparent crashes persist.
On Sun, Jun 25, 2006 at 02:53:17PM +, Dimitris Lampridis wrote: > On Sunday 25 June 2006 12:15, [EMAIL PROTECTED] wrote: > > Left it running overnight. 9 full passes through memory, *no* faults > > detected. > > > > If you search recent posts on the list, you'll see that I also had problems > with my memory and they were not discovered by memtest. So, as others have > suggested too, maybe its better to open your box, remove memories and try > them one by one for some time. If the problem persists with every single > memory module, then either your memories are OK, or all of them are bad (but > the latter, being such an extreme case, would have been probably detected by > memtest...) Took a while to find just how to reduce the number of memories from 2 to 1. It turns out to be possible, but against all intuition the single memory had to be installed in the second slot, which was named A1. Got the machine wo work for awhile with only one G memory, then it crashed in the usual way. Tried it with the other memory in that slot, and it worked for longer, but still got around to crashing today. It crashes quickly when running Pan, when using mozilla firefox with complex web pages, and slowly when using xjig. Other things probably crash it too. It took a while to get to the tests involving Pan and the complex web0sites, because just to complicate things the DSL line I use for network died and the phone company had to get around to fixing it. But they crashed quite quickly when I finally got around to it. I have an idea that it is network activity (the mouse in X also talks on the net internally, I believe) during graphics activity that does it in. No definitive evidence for that, but I do seem to be doing both when it goes down. Once again, when it crashes, I can sometimes still manage to use a ssh connection to get in from elsewhere. What information should I collect, and how should I analyse it? > > What is ur memory configuration by the way? I remember you said 2G, but is it > 2x1G, 4x512M, something else? and what about the manufacturer? 2x1G. But now I'm running 1x1G. Kingston memory. memtest86+ never finds a thing wrong. Could be, of course that it's other hardware. -- hendrik > > Dimitris > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: apparent crashes persist.
On Sun, Jun 25, 2006 at 02:53:17PM +, Dimitris Lampridis wrote: > On Sunday 25 June 2006 12:15, [EMAIL PROTECTED] wrote: > > Left it running overnight. 9 full passes through memory, *no* faults > > detected. > > > > If you search recent posts on the list, you'll see that I also had problems > with my memory and they were not discovered by memtest. So, as others have > suggested too, maybe its better to open your box, remove memories and try > them one by one for some time. If the problem persists with every single > memory module, then either your memories are OK, or all of them are bad (but > the latter, being such an extreme case, would have been probably detected by > memtest...) > > What is ur memory configuration by the way? I remember you said 2G, but is it > 2x1G, 4x512M, something else? and what about the manufacturer? It's Kingston memory, 2x1G. I don't know whether the system requires both chips to operate, but when I bought the machine they were first talking about 2x512K, and when I suggested that 2G would be more appropriate, they went to 2x1G. 1x1G was never discussed. I'll have to look for and *find* the motherboard manual to find out just what configurations it accepts, and what switches or BIOS paraneters I'll have to set. Things would be so much easier if the store I bought it at hadn't gone out of business last February, "unable to compete with the big box stores". -- hendrik -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: apparent crashes persist.
On Sunday 25 June 2006 12:15, [EMAIL PROTECTED] wrote: > Left it running overnight. 9 full passes through memory, *no* faults > detected. > If you search recent posts on the list, you'll see that I also had problems with my memory and they were not discovered by memtest. So, as others have suggested too, maybe its better to open your box, remove memories and try them one by one for some time. If the problem persists with every single memory module, then either your memories are OK, or all of them are bad (but the latter, being such an extreme case, would have been probably detected by memtest...) What is ur memory configuration by the way? I remember you said 2G, but is it 2x1G, 4x512M, something else? and what about the manufacturer? Dimitris -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: apparent crashes persist.
Left it running overnight. 9 full passes through memory, *no* faults detected. -- hendrik -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: apparent crashes persist.
On Sat, Jun 24, 2006 at 01:09:30PM +, Dimitris Lampridis wrote: > On Saturday 24 June 2006 10:51, [EMAIL PROTECTED] wrote: > > Don't see a memtest option on grub, though I've installed memtest86+. > > Evidently I have to edit the grub configuration, or use its c or e > > options when booting, but I'm completely clueless on this. > > > > Since you installed the package, the only thing that is left to do is to > edit /boot/grub/menu.lst, in a very simple and intuitive way: > > search for "memtest86+" inside this file, you should find something like: > > ## should update-grub create memtest86 boot option > ## e.g. memtest86=true > ## memtest86=false > # memtest86=true > > make sure its "true" and that it remains commented. That means *no change* at all in the configuration file. > > This will instruct update-grub (which you should run as the next step) to > include memtest86 in the grub loader. > > If everything goes well, you should see the output of the update-grub command > similar to: > > Searching for GRUB installation directory ... found: /boot/grub > Testing for an existing GRUB menu.list file ... found: /boot/grub/menu.lst > Searching for splash image ... none found, skipping ... > Found kernel: /vmlinuz-2.6.15-22062006 > Found kernel: /vmlinuz-2.6.15-1-amd64-generic > Found kernel: /memtest86+.bin > Updating /boot/grub/menu.lst ... done No change at all to the configuration, and yet it worked! And it starts to check memory when it boots. Got through 1 and a half passes without finding anything wrong. Then had to reboot to the real system to get some work done. Will check memory again later. Thanks. -- hendrik > > Good luck, > > Dimitris > > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: apparent crashes persist.
On Saturday 24 June 2006 10:51, [EMAIL PROTECTED] wrote: > Don't see a memtest option on grub, though I've installed memtest86+. > Evidently I have to edit the grub configuration, or use its c or e > options when booting, but I'm completely clueless on this. > Since you installed the package, the only thing that is left to do is to edit /boot/grub/menu.lst, in a very simple and intuitive way: search for "memtest86+" inside this file, you should find something like: ## should update-grub create memtest86 boot option ## e.g. memtest86=true ## memtest86=false # memtest86=true make sure its "true" and that it remains commented. This will instruct update-grub (which you should run as the next step) to include memtest86 in the grub loader. If everything goes well, you should see the output of the update-grub command similar to: Searching for GRUB installation directory ... found: /boot/grub Testing for an existing GRUB menu.list file ... found: /boot/grub/menu.lst Searching for splash image ... none found, skipping ... Found kernel: /vmlinuz-2.6.15-22062006 Found kernel: /vmlinuz-2.6.15-1-amd64-generic Found kernel: /memtest86+.bin Updating /boot/grub/menu.lst ... done Good luck, Dimitris -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: apparent crashes persist.
I had no idea this was going to be this difficult! On Sat, Jun 24, 2006 at 09:05:14AM +0100, Nelson Menezes wrote: > [EMAIL PROTECTED] wrote: > >vesa drivers without nvidia glx: firefox still crashes, only more > >slowly. Look like nvidia's stuff is off the hook. > > I'd definitely try memtest86+. Install, reboot, pick the option from > GRUB and let it run overnight. > > I have a similar setup to yours, and was having random lock-ups, etc. > Turns out I had some dodgy RAM that memtest86+ picked up within 10 > minutes of running. Replaced with a proper brand (GEiL); works a charm now. Don't see a memtest option on grub, though I've installed memtest86+. Evidently I have to edit the grub configuration, or use its c or e options when booting, but I'm completely clueless on this. lilo is currently refusing to work, details have just been posted in a thread on debian-user. Something about trying to read from a nonexistent device. The floppy installation script for memtest86+ fails: - * Creating msdos file system 1440+0 records in 1440+0 records out 1474560 bytes (1.5 MB) copied, 0.002501 seconds, 590 MB/s * Installing GRUB files Copying menu.lst /lib/grub/i386-pc/*: No such file or directory - Could it be that it hasn't been updated for AMD64? There's an /lib/grub/x86-64-pc directory. Should I make the obvious change in teh script? Should I report this as a bug? -- hendrik > > > -- > Nelson Menezes > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact > [EMAIL PROTECTED] > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: apparent crashes persist.
[EMAIL PROTECTED] wrote: vesa drivers without nvidia glx: firefox still crashes, only more slowly. Look like nvidia's stuff is off the hook. I'd definitely try memtest86+. Install, reboot, pick the option from GRUB and let it run overnight. I have a similar setup to yours, and was having random lock-ups, etc. Turns out I had some dodgy RAM that memtest86+ picked up within 10 minutes of running. Replaced with a proper brand (GEiL); works a charm now. -- Nelson Menezes -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: apparent crashes persist.
On Fri, Jun 23, 2006 at 03:36:42PM -0400, [EMAIL PROTECTED] wrote: > On Fri, Jun 23, 2006 at 03:22:18PM -0400, [EMAIL PROTECTED] wrote: > > On Fri, Jun 23, 2006 at 02:07:34PM +0100, A J Stiles wrote: > > > On Friday 23 June 2006 14:16, [EMAIL PROTECTED] wrote: > > > > It's been a while now, about five months and I still haven't gor my > > > > AMD64 working properly > > > > . > > > > Evidently, something is hogging some critical resource, possibly the CPU > > > > (the usual suspect) but it could also be a networking resource, since > > > > that's what the mouse and ssh seem to have in common > > > > . > > > > When logged in locally using the X server it crashes. I suspect a > > > > measure of software involvement in the crashes, because when I upgraded > > > > the nvidia drivers from 1.0.8756-1 to 1.0.8762-2 and also upgraded the > > > > kernel from 2.6.12 to 2.6.15 the crashes became less frequent. > > > > > > First thing to try: get rid of the closed-source nVidia drivers and try > > > using > > > the i-tal "nv" driver instead. See how the system fares then. > > > > With the nv driver, get > > (EE) no devices found > > > > Indeed, the 6100 is not on the list of chips supported by the nv driver. > > > > Next, try vesa? > > With vesa, X comes up and crashes under firefox. > Mind you, the log shows that X loaded nvidia's glx even though it had a > vesa driver. I would guess that this combination is unlikely to work. > Looks like I may have to uninstall the nvidia stuff to keep it from > being used. > > here, aptitude is my friend. vesa drivers without nvidia glx: firefox still crashes, only more slowly. Look like nvidia's stuff is off the hook. -- hendrik -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: apparent crashes persist.
On Fri, Jun 23, 2006 at 03:22:18PM -0400, [EMAIL PROTECTED] wrote: > On Fri, Jun 23, 2006 at 02:07:34PM +0100, A J Stiles wrote: > > On Friday 23 June 2006 14:16, [EMAIL PROTECTED] wrote: > > > It's been a while now, about five months and I still haven't gor my > > > AMD64 working properly > > > . > > > Evidently, something is hogging some critical resource, possibly the CPU > > > (the usual suspect) but it could also be a networking resource, since > > > that's what the mouse and ssh seem to have in common > > > . > > > When logged in locally using the X server it crashes. I suspect a > > > measure of software involvement in the crashes, because when I upgraded > > > the nvidia drivers from 1.0.8756-1 to 1.0.8762-2 and also upgraded the > > > kernel from 2.6.12 to 2.6.15 the crashes became less frequent. > > > > First thing to try: get rid of the closed-source nVidia drivers and try > > using > > the i-tal "nv" driver instead. See how the system fares then. > > With the nv driver, get > (EE) no devices found > > Indeed, the 6100 is not on the list of chips supported by the nv driver. > > Next, try vesa? With vesa, X comes up and crashes under firefox. Mind you, the log shows that X loaded nvidia's glx even though it had a vesa driver. I would guess that this combination is unlikely to work. Looks like I may have to uninstall the nvidia stuff to keep it from being used. here, aptitude is my friend. -- hendrik -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: apparent crashes persist.
On Fri, Jun 23, 2006 at 02:07:34PM +0100, A J Stiles wrote: > On Friday 23 June 2006 14:16, [EMAIL PROTECTED] wrote: > > It's been a while now, about five months and I still haven't gor my > > AMD64 working properly > > . > > Evidently, something is hogging some critical resource, possibly the CPU > > (the usual suspect) but it could also be a networking resource, since > > that's what the mouse and ssh seem to have in common > > . > > When logged in locally using the X server it crashes. I suspect a > > measure of software involvement in the crashes, because when I upgraded > > the nvidia drivers from 1.0.8756-1 to 1.0.8762-2 and also upgraded the > > kernel from 2.6.12 to 2.6.15 the crashes became less frequent. > > First thing to try: get rid of the closed-source nVidia drivers and try > using > the i-tal "nv" driver instead. See how the system fares then. With the nv driver, get (EE) no devices found Indeed, the 6100 is not on the list of chips supported by the nv driver. Next, try vesa? -- hendrik -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: apparent crashes persist.
On Fri, Jun 23, 2006 at 11:29:55AM -0400, [EMAIL PROTECTED] wrote: > Can openGL work with nv? Do I have to carefully uninstall > OpenGL-related packages that just know how to talk with nvidia? You can run opengl with mesa libraries, which do opengl in software. There is no modern card that has free drivers for opengl in hardware. Only a few older cards have such drivers. If you want hardware opengl you are stuck with the nvidia driver, but for just running X in 2D, the nv driver generally works great. For testing a problem, it is often handy to elliminate what you can't get source code for, such as the nvidia driver. Len Sorensen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: apparent crashes persist.
On Friday 23 June 2006 15:25, [EMAIL PROTECTED] wrote: > That's the memtest now packaged in package memtester, formerly > part of sysutils, which tests memory while Linux is running? > Or should I look at memtest86+? Will it run on AMD64? > I've invoked many times memtest86 from Grub without any problem. But since you're having so many problems, so often, you don't really need such a time-consuming tool (I think). Just run your PC with one memory module installed at a time and see if you get correct behavior or not. Its faster, given the frequency of crashes you reported. Try firefox for example since it is causing u so many problems. Chances are that one memory module will show the signs immediately (in my case, there was a faulty mem module and when I used it alone, PC wouldn't even boot correctly, so it was piece of cake) BTW, what memory do you have? is there any chance that you're giving it the wrong voltage from the respective BIOS settings? Good luck, Dimitris PS: I also have Asus A8N (no GPU onboard), running Etch64, with 2.6.15 and nvidia 1.0.8762-2, everything is fine. pgpanzdkabpRn.pgp Description: PGP signature
Re: apparent crashes persist -- memtester
[EMAIL PROTECTED] wrote: On Fri, Jun 23, 2006 at 02:24:58PM +0100, Jo Shields wrote: A J Stiles wrote: On Friday 23 June 2006 14:16, [EMAIL PROTECTED] wrote: It's been a while now, about five months and I still haven't gor my AMD64 working properly . Evidently, something is hogging some critical resource, possibly the CPU (the usual suspect) but it could also be a networking resource, since that's what the mouse and ssh seem to have in common . When logged in locally using the X server it crashes. I suspect a measure of software involvement in the crashes, because when I upgraded the nvidia drivers from 1.0.8756-1 to 1.0.8762-2 and also upgraded the kernel from 2.6.12 to 2.6.15 the crashes became less frequent. First thing to try: get rid of the closed-source nVidia drivers and try using the i-tal "nv" driver instead. See how the system fares then. And run your sticks of RAM, one at a time, through memtest, for a good 24 or so hour run Well, memtest alias memtester, when asked to test all, allocated 3G of memory -- I only have 2G on my machine, and then failed to lock all of them into physical RAM -- small wonder. Then it got killed. Does it have no mechanism for distinguishing whether it's testing RAM or swap space? Before you run it, run "swapoff -a" -Steve -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: apparent crashes persist -- memtester
On Fri, Jun 23, 2006 at 02:24:58PM +0100, Jo Shields wrote: > A J Stiles wrote: > >On Friday 23 June 2006 14:16, [EMAIL PROTECTED] wrote: > > > >>It's been a while now, about five months and I still haven't gor my > >>AMD64 working properly > >>. > >>Evidently, something is hogging some critical resource, possibly the CPU > >>(the usual suspect) but it could also be a networking resource, since > >>that's what the mouse and ssh seem to have in common > >>. > >>When logged in locally using the X server it crashes. I suspect a > >>measure of software involvement in the crashes, because when I upgraded > >>the nvidia drivers from 1.0.8756-1 to 1.0.8762-2 and also upgraded the > >>kernel from 2.6.12 to 2.6.15 the crashes became less frequent. > >> > > > >First thing to try: get rid of the closed-source nVidia drivers and try > >using the i-tal "nv" driver instead. See how the system fares then. > > And run your sticks of RAM, one at a time, through memtest, for a good > 24 or so hour run Well, memtest alias memtester, when asked to test all, allocated 3G of memory -- I only have 2G on my machine, and then failed to lock all of them into physical RAM -- small wonder. Then it got killed. Does it have no mechanism for distinguishing whether it's testing RAM or swap space? -- hendrik > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact > [EMAIL PROTECTED] > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: apparent crashes persist.
On Fri, Jun 23, 2006 at 02:07:34PM +0100, A J Stiles wrote: > > First thing to try: get rid of the closed-source nVidia drivers and try > using > the i-tal "nv" driver instead. See how the system fares then. Can openGL work with nv? Do I have to carefully uninstall OpenGL-related packages that just know how to talk with nvidia? -- hendrik > > -- > AJS > delta echo bravo six four at earthshod dot co dot uk > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: apparent crashes persist.
On Fri, Jun 23, 2006 at 02:24:58PM +0100, Jo Shields wrote: > > And run your sticks of RAM, one at a time, through memtest, for a good > 24 or so hour run That's the memtest now packaged in package memtester, formerly part of sysutils, which tests memory while Linux is running? Or should I look at memtest86+? Will it run on AMD64? -- hendrik > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact > [EMAIL PROTECTED] > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: apparent crashes persist.
A J Stiles wrote: On Friday 23 June 2006 14:16, [EMAIL PROTECTED] wrote: It's been a while now, about five months and I still haven't gor my AMD64 working properly . Evidently, something is hogging some critical resource, possibly the CPU (the usual suspect) but it could also be a networking resource, since that's what the mouse and ssh seem to have in common . When logged in locally using the X server it crashes. I suspect a measure of software involvement in the crashes, because when I upgraded the nvidia drivers from 1.0.8756-1 to 1.0.8762-2 and also upgraded the kernel from 2.6.12 to 2.6.15 the crashes became less frequent. First thing to try: get rid of the closed-source nVidia drivers and try using the i-tal "nv" driver instead. See how the system fares then. And run your sticks of RAM, one at a time, through memtest, for a good 24 or so hour run -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: apparent crashes persist.
On Friday 23 June 2006 14:16, [EMAIL PROTECTED] wrote: > It's been a while now, about five months and I still haven't gor my > AMD64 working properly > . > Evidently, something is hogging some critical resource, possibly the CPU > (the usual suspect) but it could also be a networking resource, since > that's what the mouse and ssh seem to have in common > . > When logged in locally using the X server it crashes. I suspect a > measure of software involvement in the crashes, because when I upgraded > the nvidia drivers from 1.0.8756-1 to 1.0.8762-2 and also upgraded the > kernel from 2.6.12 to 2.6.15 the crashes became less frequent. First thing to try: get rid of the closed-source nVidia drivers and try using the i-tal "nv" driver instead. See how the system fares then. -- AJS delta echo bravo six four at earthshod dot co dot uk -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
