Re: Debian AMD64 freeze ! (Update)
Am Sonntag, 29. Oktober 2006 23:03 schrieb Cédric Boutillier: > It might be a problem with the bcm43xx driver. Indeed, I experienced > several lockups with debian ppc on my ibook. The last message was > exactly the same as yours, where bcm43xx restarts the controller. > > > Oct 29 10:28:08 protheus2 kernel: bcm43xx: Radio turned off > > Oct 29 10:28:08 protheus2 kernel: bcm43xx: Radio turned off > > Oct 29 10:28:08 protheus2 kernel: bcm43xx: Controller restarted Might be, but could also be, that it is because some other things crash, like memorymapping or whatever. And if this would be so, everyone without that card would have no prolems. Best regards Hans -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Debian AMD64 freeze ! (Update)
It might be a problem with the bcm43xx driver. Indeed, I experienced several lockups with debian ppc on my ibook. The last message was exactly the same as yours, where bcm43xx restarts the controller. Oct 29 10:28:08 protheus2 kernel: bcm43xx: Radio turned off Oct 29 10:28:08 protheus2 kernel: bcm43xx: Radio turned off Oct 29 10:28:08 protheus2 kernel: bcm43xx: Controller restarted -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Debian AMD64 freeze !
I'll have to try the beta drivers again as the last time, the one in debian experimental didn't have the SMBus disabled which was causing a freeze at boot [at least for me]. -Pascal On 10/29/06, pietia .moo <[EMAIL PROTECTED]> wrote: Freezes stoped on my notebook with Amd 64 Turion x2 few days ago when i have changed nvidia drivers to newst 'nvidia beta drivers' from nvzone. Try it! it's much better. There is no freezes! OT: Maybe you know - will Debian Etch (in December) has new drivers in kernel for newes realtek ethernet cards ? -- Homepage (http://organact.mine.nu) Debian GNU/Linux (http://www.debian.org) École de technologie supérieure (http://www.etsmtl.ca)
Re: Debian AMD64 freeze !
On Sun, Oct 29, 2006 at 10:17:57AM +0100, Hans-J. Ullrich wrote: > Am Samstag, 28. Oktober 2006 21:04 schrieb Jack Malmostoso: > > On Sat, 28 Oct 2006 21:00:14 +0200, Hans-J. Ullrich wrote: > > > And last but not least, another hint: The machines do freeze everytime, > > > whenever no one worked on it, so, when there were no keyboard or other > > > input. > > > > Could you try opening your sshd server and try to connect to the frozen > > machine when that happens? It would rule out kernel problems and it would > > concentrate the problem on X. Do you use proprietary drivers? That might > > I checked before: No ssh possible. The whole machine froze. > > I use proprietryry drivers (Nvidia and fglrx), but this seems not to be the > reason (as other users confirmed). > > Additionally: The machine also froze, when I had switched to console (CTRL > +ALT + 2 for example). I suppose, thats makes no difference, as X is still > running, does it ? have you tried alt+sysreq ? Or even just the num lock key - does the light change ? > > (Most important case for me: It is a real bug, not only behaviour on my > machine) > > be another issue: try using only Xorg drivers. > > > > -- > > Best Regards, Jack > > Linux user #264449 > > Powered by Debian PPC > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > > signature.asc Description: Digital signature
Re: Debian AMD64 freeze !
Am Samstag, 28. Oktober 2006 21:04 schrieb Jack Malmostoso: > On Sat, 28 Oct 2006 21:00:14 +0200, Hans-J. Ullrich wrote: > > And last but not least, another hint: The machines do freeze everytime, > > whenever no one worked on it, so, when there were no keyboard or other > > input. > > Could you try opening your sshd server and try to connect to the frozen > machine when that happens? It would rule out kernel problems and it would > concentrate the problem on X. Do you use proprietary drivers? That might I checked before: No ssh possible. The whole machine froze. I use proprietryry drivers (Nvidia and fglrx), but this seems not to be the reason (as other users confirmed). Additionally: The machine also froze, when I had switched to console (CTRL +ALT + 2 for example). I suppose, thats makes no difference, as X is still running, does it ? (Most important case for me: It is a real bug, not only behaviour on my machine) > be another issue: try using only Xorg drivers. > > -- > Best Regards, Jack > Linux user #264449 > Powered by Debian PPC -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Debian AMD64 freeze !
Freezes stoped on my notebook with Amd 64 Turion x2 few days ago when i have changed nvidia drivers to newst 'nvidia beta drivers' from nvzone. Try it! it's much better. There is no freezes! OT: Maybe you know - will Debian Etch (in December) has new drivers in kernel for newes realtek ethernet cards ?
Re: Debian AMD64 freeze ! (Update)
Am Sonntag, 29. Oktober 2006 10:17 schrieb Hans-J. Ullrich: > Am Samstag, 28. Oktober 2006 21:04 schrieb Jack Malmostoso: > > On Sat, 28 Oct 2006 21:00:14 +0200, Hans-J. Ullrich wrote: > > > And last but not least, another hint: The machines do freeze everytime, > > > whenever no one worked on it, so, when there were no keyboard or other > > > input. > > > > Could you try opening your sshd server and try to connect to the frozen > > machine when that happens? It would rule out kernel problems and it would > > concentrate the problem on X. Do you use proprietary drivers? That might > > I checked before: No ssh possible. The whole machine froze. > > I use proprietryry drivers (Nvidia and fglrx), but this seems not to be the > reason (as other users confirmed). > > Additionally: The machine also froze, when I had switched to console (CTRL > +ALT + 2 for example). I suppose, thats makes no difference, as X is still > running, does it ? > > (Most important case for me: It is a real bug, not only behaviour on my > machine) > > > be another issue: try using only Xorg drivers. > > > > -- > > Best Regards, Jack > > Linux user #264449 > > Powered by Debian PPC My machine just froze again ! I checked all, and again: No ssh possible, eben no ping-reply. Here is the last entry from /var/log/kern.log just before the crash and my next reboot (I had to hard reset). You can also see, how I start my machine. Further on you can see, an APIC-error (I never tried starting with the option "noapic") And you see the dbus-error. snip --- Oct 29 09:37:24 protheus2 kernel: dbus-launch[2893]: segfault at rip 2b79c927c590 rsp 7fffe1bbf6f8 error 4 Oct 29 09:37:53 protheus2 kernel: NET: Registered protocol family 4 Oct 29 09:37:53 protheus2 kernel: NET: Registered protocol family 3 Oct 29 09:37:53 protheus2 kernel: NET: Registered protocol family 5 Oct 29 09:37:57 protheus2 kernel: APIC error on CPU0: 00(40) Oct 29 09:37:59 protheus2 kernel: psmouse.c: TouchPad at isa0060/serio4/input0 - driver resynched. Oct 29 09:58:00 protheus2 kernel: APIC error on CPU0: 40(40) Oct 29 10:07:38 protheus2 kernel: Losing some ticks... checking if CPU frequency changed. Oct 29 10:28:08 protheus2 kernel: NETDEV WATCHDOG: eth0: transmit timed out Oct 29 10:28:08 protheus2 kernel: bcm43xx: Controller RESET (TX timeout) ... Oct 29 10:28:08 protheus2 kernel: ACPI: PCI interrupt for device :06:05.0 disabled Oct 29 10:28:08 protheus2 kernel: PCI: Enabling device :06:05.0 ( -> 0002) Oct 29 10:28:08 protheus2 kernel: ACPI: PCI Interrupt :06:05.0[A] -> GSI 21 (level, low) -> IRQ 169 Oct 29 10:28:08 protheus2 kernel: bcm43xx: Chip ID 0x4318, rev 0x2 Oct 29 10:28:08 protheus2 kernel: bcm43xx: Number of cores: 4 Oct 29 10:28:08 protheus2 kernel: bcm43xx: Core 0: ID 0x800, rev 0xd, vendor 0x4243, enabled Oct 29 10:28:08 protheus2 kernel: bcm43xx: Core 1: ID 0x812, rev 0x9, vendor 0x4243, enabled Oct 29 10:28:08 protheus2 kernel: bcm43xx: Core 2: ID 0x804, rev 0xc, vendor 0x4243, enabled Oct 29 10:28:08 protheus2 kernel: bcm43xx: Core 3: ID 0x80d, rev 0x7, vendor 0x4243, enabled Oct 29 10:28:08 protheus2 kernel: bcm43xx: PHY connected Oct 29 10:28:08 protheus2 kernel: bcm43xx: Detected PHY: Version: 3, Type 2, Revision 7 Oct 29 10:28:08 protheus2 kernel: bcm43xx: Detected Radio: ID: 8205017f (Manuf: 17f Ver: 2050 Rev: 8) Oct 29 10:28:08 protheus2 kernel: bcm43xx: Radio turned off Oct 29 10:28:08 protheus2 kernel: bcm43xx: Radio turned off Oct 29 10:28:08 protheus2 kernel: bcm43xx: Controller restarted Oct 29 10:34:06 protheus2 kernel: klogd 1.4.1#20, log source = /proc/kmsg started. Oct 29 10:34:06 protheus2 kernel: Bootdata ok (command line is root=/dev/hda6 ro vga=791 splash=silent) Oct 29 10:34:06 protheus2 kernel: Linux version 2.6.18-1-amd64 (2.6.18-1-amd64-10.00.Custom) ([EMAIL PROTECTED]) (gcc version 4.1.2 20061020 (prerelease) (Debian 4.1.1-17)) #5 SMP Mon Oct 23 20:54:28 CEST 2006 Oct 29 10:34:06 protheus2 kernel: BIOS-provided physical RAM map: Oct 29 10:34:06 protheus2 kernel: BIOS-e820: - 0009b800 (usable) Oct 29 10:34:06 protheus2 kernel: BIOS-e820: 0009b800 - 000a (reserved) Oct 29 10:34:06 protheus2 kernel: BIOS-e820: 000d - 0010 (reserved) Oct 29 10:34:06 protheus2 kernel: BIOS-e820: 0010 - 3fea (usable) Oct 29 10:34:06 protheus2 kernel: BIOS-e820: 3fea - 3feae000 (ACPI data) Oct 29 10:34:06 protheus2 kernel: BIOS-e820: 3feae000 - 3ff0 (ACPI NVS) Oct 29 10:34:06 protheus2 kernel: BIOS-e820: 3ff0 - 4000 (reserved) Oct 29 10:34:06 protheus2 kernel: BIOS-e820: fec0 - fec1 (reserved) Oct 29 10:34:06 protheus2 kernel: BIOS-e820: fee0 - fee01000 (reserved) Oct 29 10:34:06 protheus2 kernel: BIOS-e820: fff8 - 0001 (reserved) Oct 29 10
Re: Debian AMD64 freeze !
On Sat, Oct 28, 2006 at 05:28:20PM -0400, Pascal Giard wrote: > On 10/28/06, Alexander Samad <[EMAIL PROTECTED]> wrote: > >On Sat, Oct 28, 2006 at 04:37:12PM -0400, Pascal Giard wrote: > >> I also experienced those freezes. > >> I noticed it started when upgrading from nvidia's proprietary driver > >> 8774 to 8776. > [...] > >Bugger just upgraded to 8776-1, been up for 2 days no freezes yet > > > > hmmm... once I built the kernel module and installed it, it took about > 2hrs before i got the first freeze... so it seems you won't have that > problem. > > perhaps the problem only shows up in correlation with > linux-image-2.6.18-1-amd64_2.6.18-3 ? [EMAIL PROTECTED]:~$ dpkg -l 'linux-image-2.6.*' | grep ^ii ii linux-image-2.6.15-1-amd64-k8-smp 2.6.15-7 Linux kernel 2.6.15 image on AMD64 K8 SMP ma ii linux-image-2.6.16-1-amd64-k8-smp 2.6.16-12 Linux kernel 2.6.16 image on AMD64 K8 SMP ma ii linux-image-2.6.17-1-amd64-k8-smp 2.6.17-4 Linux kernel 2.6.17 image on AMD64 K8 SMP ma ii linux-image-2.6.18-1-amd642.6.18-3 Linux 2.6.18 image on AMD64 > > btw, i filled a bugreport about my freezes...[1] > > -Pascal > [1] http://bugs.debian.org/395818 > -- > Homepage (http://organact.mine.nu) > Debian GNU/Linux (http://www.debian.org) > École de technologie supérieure (http://www.etsmtl.ca) > > signature.asc Description: Digital signature
Re: Debian AMD64 freeze !
On Sat, Oct 28, 2006 at 04:37:12PM -0400, Pascal Giard wrote: > I also experienced those freezes. > I noticed it started when upgrading from nvidia's proprietary driver > 8774 to 8776. > > I've switched to "nv" 3 days ago and the problem went away. > > Anyone else observed that? I've tried nv, and even the framebuffer. No difference. Mind you, that was a while ago. I'll have to try again. > > -Pascal > > On 10/28/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > >On Sat, Oct 28, 2006 at 08:33:41PM +0200, Hans-J. Ullrich wrote: > >> Dear maintainers, > >> > >> somebody wrote about Debian AMD64 complete freeze. Yes, I can confirm > >this > >> behaviour ! > > > >Was it me? Details at > >http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=379480 > > > >> > >> This is what I watched: > >> > >> During normal working, everything froze: mouse, keyboard, window, > >everything. > >> Even, when I watched a movie, this happened twice. This behaviour is > >similar > >> to BUG#379480. > > > >If it seems to be the same problem, it could help if details were > >sent to [EMAIL PROTECTED] > > > >I've found the keyboard still works to a limited extent. If I have a > >text tntry window open at the moment of freeze, it continues to accept > >input. If it's an open shell window. I can even execute commands. > >But if anything happens to terminate input (such as hitting return on a > >URL entry window in a browser) the freeze becomes complete. > > > >I'm not sure whether it is still possible to ssh in from another system > >when it freezes. IN any case when it was possible, it was too slow to > >be usable (keypress echo in excess of 15 seconds, protocol delays enough > >to time out during initial connection) > > > >-- hendrik > > > >> > >> But what is more important: This behaviour is on my 32-bit-machine, too ! > > > >Fails on my AMD64 in 32-bit mode, too. > > > >> > >> And both machines do have differnent hardware: > >> > >> 32-bit computer with AMD Athlon XP and Nvidia-Card, the > >> 64-bit computer with AMD64 Turion and ATI-Card ! > > > >My workaround has been to use Ubuntu dapper drake. But all the other > >systems on my network use Debian, so it's an anomaly. > > > >> > >> But both use kernel 2.6.18 ! On 32-bit the Debian-original-kernel, on > >64-Bit a > >> selfcompiled out of the Debian-sources. > >> > >> O.k., I tested RAM on both = o.k. > >> I checked the logs, and I discovered this: > >> > >> Oct 28 19:45:29 protheus2 kernel: dbus-launch[2857]: segfault at > >> rip 2ba3403ed590 rsp 7fff6aa4d188 error 4 > >> > >> Maybe this is the reason, although these messages appear on kernel > >2.6.17, > >> too. On 2.6.17 everything went fine. > > > >Fails on evry kernel I've used. > > > >> > >> So, as both machines behave the same, I suppose a kernel problem. > >> > >> And last but not least, another hint: The machines do freeze everytime, > >> whenever no one worked on it, so, when there were no keyboard or other > >input. > > > >I don't recall ever getting a freeze when no one was using the machine > >(except as a file server). > > > >> > >> I hope, my little desription will help to find the bug. > >> > >> Best regards > >> > >> Hans > >> > >> P.S. This mail is related to i386, too. > >> > >> > >> > >> > >> > >> -- > >> 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] > > > > > > > -- > Homepage (http://organact.mine.nu) > Debian GNU/Linux (http://www.debian.org) > ?cole de technologie sup?rieure (http://www.etsmtl.ca) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Debian AMD64 freeze !
On 10/28/06, Alexander Samad <[EMAIL PROTECTED]> wrote: On Sat, Oct 28, 2006 at 04:37:12PM -0400, Pascal Giard wrote: > I also experienced those freezes. > I noticed it started when upgrading from nvidia's proprietary driver > 8774 to 8776. [...] Bugger just upgraded to 8776-1, been up for 2 days no freezes yet hmmm... once I built the kernel module and installed it, it took about 2hrs before i got the first freeze... so it seems you won't have that problem. perhaps the problem only shows up in correlation with linux-image-2.6.18-1-amd64_2.6.18-3 ? btw, i filled a bugreport about my freezes...[1] -Pascal [1] http://bugs.debian.org/395818 -- Homepage (http://organact.mine.nu) Debian GNU/Linux (http://www.debian.org) École de technologie supérieure (http://www.etsmtl.ca)
Re: Debian AMD64 freeze !
On Sat, Oct 28, 2006 at 04:37:12PM -0400, Pascal Giard wrote: > I also experienced those freezes. > I noticed it started when upgrading from nvidia's proprietary driver > 8774 to 8776. > > I've switched to "nv" 3 days ago and the problem went away. > > Anyone else observed that? Bugger just upgraded to 8776-1, been up for 2 days no freezes yet > > -Pascal > > On 10/28/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > >On Sat, Oct 28, 2006 at 08:33:41PM +0200, Hans-J. Ullrich wrote: > >> Dear maintainers, > >> > >> somebody wrote about Debian AMD64 complete freeze. Yes, I can confirm > >this > >> behaviour ! > > > >Was it me? Details at > >http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=379480 > > > >> > >> This is what I watched: > >> > >> During normal working, everything froze: mouse, keyboard, window, > >everything. > >> Even, when I watched a movie, this happened twice. This behaviour is > >similar > >> to BUG#379480. > > > >If it seems to be the same problem, it could help if details were > >sent to [EMAIL PROTECTED] > > > >I've found the keyboard still works to a limited extent. If I have a > >text tntry window open at the moment of freeze, it continues to accept > >input. If it's an open shell window. I can even execute commands. > >But if anything happens to terminate input (such as hitting return on a > >URL entry window in a browser) the freeze becomes complete. > > > >I'm not sure whether it is still possible to ssh in from another system > >when it freezes. IN any case when it was possible, it was too slow to > >be usable (keypress echo in excess of 15 seconds, protocol delays enough > >to time out during initial connection) > > > >-- hendrik > > > >> > >> But what is more important: This behaviour is on my 32-bit-machine, too ! > > > >Fails on my AMD64 in 32-bit mode, too. > > > >> > >> And both machines do have differnent hardware: > >> > >> 32-bit computer with AMD Athlon XP and Nvidia-Card, the > >> 64-bit computer with AMD64 Turion and ATI-Card ! > > > >My workaround has been to use Ubuntu dapper drake. But all the other > >systems on my network use Debian, so it's an anomaly. > > > >> > >> But both use kernel 2.6.18 ! On 32-bit the Debian-original-kernel, on > >64-Bit a > >> selfcompiled out of the Debian-sources. > >> > >> O.k., I tested RAM on both = o.k. > >> I checked the logs, and I discovered this: > >> > >> Oct 28 19:45:29 protheus2 kernel: dbus-launch[2857]: segfault at > >> rip 2ba3403ed590 rsp 7fff6aa4d188 error 4 > >> > >> Maybe this is the reason, although these messages appear on kernel > >2.6.17, > >> too. On 2.6.17 everything went fine. > > > >Fails on evry kernel I've used. > > > >> > >> So, as both machines behave the same, I suppose a kernel problem. > >> > >> And last but not least, another hint: The machines do freeze everytime, > >> whenever no one worked on it, so, when there were no keyboard or other > >input. > > > >I don't recall ever getting a freeze when no one was using the machine > >(except as a file server). > > > >> > >> I hope, my little desription will help to find the bug. > >> > >> Best regards > >> > >> Hans > >> > >> P.S. This mail is related to i386, too. > >> > >> > >> > >> > >> > >> -- > >> 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] > > > > > > > -- > Homepage (http://organact.mine.nu) > Debian GNU/Linux (http://www.debian.org) > École de technologie supérieure (http://www.etsmtl.ca) > > signature.asc Description: Digital signature
Re: Debian AMD64 freeze !
I also experienced those freezes. I noticed it started when upgrading from nvidia's proprietary driver 8774 to 8776. I've switched to "nv" 3 days ago and the problem went away. Anyone else observed that? -Pascal On 10/28/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: On Sat, Oct 28, 2006 at 08:33:41PM +0200, Hans-J. Ullrich wrote: > Dear maintainers, > > somebody wrote about Debian AMD64 complete freeze. Yes, I can confirm this > behaviour ! Was it me? Details at http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=379480 > > This is what I watched: > > During normal working, everything froze: mouse, keyboard, window, everything. > Even, when I watched a movie, this happened twice. This behaviour is similar > to BUG#379480. If it seems to be the same problem, it could help if details were sent to [EMAIL PROTECTED] I've found the keyboard still works to a limited extent. If I have a text tntry window open at the moment of freeze, it continues to accept input. If it's an open shell window. I can even execute commands. But if anything happens to terminate input (such as hitting return on a URL entry window in a browser) the freeze becomes complete. I'm not sure whether it is still possible to ssh in from another system when it freezes. IN any case when it was possible, it was too slow to be usable (keypress echo in excess of 15 seconds, protocol delays enough to time out during initial connection) -- hendrik > > But what is more important: This behaviour is on my 32-bit-machine, too ! Fails on my AMD64 in 32-bit mode, too. > > And both machines do have differnent hardware: > > 32-bit computer with AMD Athlon XP and Nvidia-Card, the > 64-bit computer with AMD64 Turion and ATI-Card ! My workaround has been to use Ubuntu dapper drake. But all the other systems on my network use Debian, so it's an anomaly. > > But both use kernel 2.6.18 ! On 32-bit the Debian-original-kernel, on 64-Bit a > selfcompiled out of the Debian-sources. > > O.k., I tested RAM on both = o.k. > I checked the logs, and I discovered this: > > Oct 28 19:45:29 protheus2 kernel: dbus-launch[2857]: segfault at > rip 2ba3403ed590 rsp 7fff6aa4d188 error 4 > > Maybe this is the reason, although these messages appear on kernel 2.6.17, > too. On 2.6.17 everything went fine. Fails on evry kernel I've used. > > So, as both machines behave the same, I suppose a kernel problem. > > And last but not least, another hint: The machines do freeze everytime, > whenever no one worked on it, so, when there were no keyboard or other input. I don't recall ever getting a freeze when no one was using the machine (except as a file server). > > I hope, my little desription will help to find the bug. > > Best regards > > Hans > > P.S. This mail is related to i386, too. > > > > > > -- > 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] -- Homepage (http://organact.mine.nu) Debian GNU/Linux (http://www.debian.org) École de technologie supérieure (http://www.etsmtl.ca)
Re: Debian AMD64 freeze !
On Sat, Oct 28, 2006 at 08:33:41PM +0200, Hans-J. Ullrich wrote: > Dear maintainers, > > somebody wrote about Debian AMD64 complete freeze. Yes, I can confirm this > behaviour ! Was it me? Details at http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=379480 > > This is what I watched: > > During normal working, everything froze: mouse, keyboard, window, everything. > Even, when I watched a movie, this happened twice. This behaviour is similar > to BUG#379480. If it seems to be the same problem, it could help if details were sent to [EMAIL PROTECTED] I've found the keyboard still works to a limited extent. If I have a text tntry window open at the moment of freeze, it continues to accept input. If it's an open shell window. I can even execute commands. But if anything happens to terminate input (such as hitting return on a URL entry window in a browser) the freeze becomes complete. I'm not sure whether it is still possible to ssh in from another system when it freezes. IN any case when it was possible, it was too slow to be usable (keypress echo in excess of 15 seconds, protocol delays enough to time out during initial connection) -- hendrik > > But what is more important: This behaviour is on my 32-bit-machine, too ! Fails on my AMD64 in 32-bit mode, too. > > And both machines do have differnent hardware: > > 32-bit computer with AMD Athlon XP and Nvidia-Card, the > 64-bit computer with AMD64 Turion and ATI-Card ! My workaround has been to use Ubuntu dapper drake. But all the other systems on my network use Debian, so it's an anomaly. > > But both use kernel 2.6.18 ! On 32-bit the Debian-original-kernel, on 64-Bit > a > selfcompiled out of the Debian-sources. > > O.k., I tested RAM on both = o.k. > I checked the logs, and I discovered this: > > Oct 28 19:45:29 protheus2 kernel: dbus-launch[2857]: segfault at > rip 2ba3403ed590 rsp 7fff6aa4d188 error 4 > > Maybe this is the reason, although these messages appear on kernel 2.6.17, > too. On 2.6.17 everything went fine. Fails on evry kernel I've used. > > So, as both machines behave the same, I suppose a kernel problem. > > And last but not least, another hint: The machines do freeze everytime, > whenever no one worked on it, so, when there were no keyboard or other input. I don't recall ever getting a freeze when no one was using the machine (except as a file server). > > I hope, my little desription will help to find the bug. > > Best regards > > Hans > > P.S. This mail is related to i386, too. > > > > > > -- > 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: Debian AMD64 freeze !
On Saturday 28 October 2006 11:33, Hans-J. Ullrich wrote: > Dear maintainers, > > somebody wrote about Debian AMD64 complete freeze. Yes, I can confirm this > behaviour ! > > This is what I watched: > > During normal working, everything froze: mouse, keyboard, window, > everything. Even, when I watched a movie, this happened twice. This > behaviour is similar to BUG#379480. > > But what is more important: This behaviour is on my 32-bit-machine, too ! > > And both machines do have differnent hardware: > > 32-bit computer with AMD Athlon XP and Nvidia-Card, the > 64-bit computer with AMD64 Turion and ATI-Card ! > > But both use kernel 2.6.18 ! On 32-bit the Debian-original-kernel, on > 64-Bit a selfcompiled out of the Debian-sources. > > O.k., I tested RAM on both = o.k. > I checked the logs, and I discovered this: > > Oct 28 19:45:29 protheus2 kernel: dbus-launch[2857]: segfault at > rip 2ba3403ed590 rsp 7fff6aa4d188 error 4 > > Maybe this is the reason, although these messages appear on kernel 2.6.17, > too. On 2.6.17 everything went fine. > > So, as both machines behave the same, I suppose a kernel problem. > > And last but not least, another hint: The machines do freeze everytime, > whenever no one worked on it, so, when there were no keyboard or other > input. > > I hope, my little desription will help to find the bug. > > Best regards > > Hans > > P.S. This mail is related to i386, too. I've had this same behaviour recently as well; seems to happen with the X sleep function (amdx2 m2pv-vm)... (I also tried to login with ssh. pings but connection is refused) I thought it was an upgrade to xorg 7.1. that did it. I've downgraded to 7.0 and it hasn't happened now for about 2 days. Chris W. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Debian AMD64 freeze !
On Sat, 28 Oct 2006 21:00:14 +0200, Hans-J. Ullrich wrote: > And last but not least, another hint: The machines do freeze everytime, > whenever no one worked on it, so, when there were no keyboard or other input. Could you try opening your sshd server and try to connect to the frozen machine when that happens? It would rule out kernel problems and it would concentrate the problem on X. Do you use proprietary drivers? That might be another issue: try using only Xorg drivers. -- Best Regards, Jack Linux user #264449 Powered by Debian PPC -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Debian AMD64 freeze !
Dear maintainers, somebody wrote about Debian AMD64 complete freeze. Yes, I can confirm this behaviour ! This is what I watched: During normal working, everything froze: mouse, keyboard, window, everything. Even, when I watched a movie, this happened twice. This behaviour is similar to BUG#379480. But what is more important: This behaviour is on my 32-bit-machine, too ! And both machines do have differnent hardware: 32-bit computer with AMD Athlon XP and Nvidia-Card, the 64-bit computer with AMD64 Turion and ATI-Card ! But both use kernel 2.6.18 ! On 32-bit the Debian-original-kernel, on 64-Bit a selfcompiled out of the Debian-sources. O.k., I tested RAM on both = o.k. I checked the logs, and I discovered this: Oct 28 19:45:29 protheus2 kernel: dbus-launch[2857]: segfault at rip 2ba3403ed590 rsp 7fff6aa4d188 error 4 Maybe this is the reason, although these messages appear on kernel 2.6.17, too. On 2.6.17 everything went fine. So, as both machines behave the same, I suppose a kernel problem. And last but not least, another hint: The machines do freeze everytime, whenever no one worked on it, so, when there were no keyboard or other input. I hope, my little desription will help to find the bug. Best regards Hans P.S. This mail is related to i386, too. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
