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: install: choose kernel
On Sunday 29 October 2006 12:21, Goswin von Brederlow wrote: > Shouldn't the default be linux-image-2.6-amd64 so the kernel does get > automatically updated to the latest versions? At least with grub there > is little harm in adding more kernels because it doesn't "forget" the > old ones like lilo. It is. pgp9MA2N3jSqi.pgp Description: PGP signature
Re: install: choose kernel
Frans Pop <[EMAIL PROTECTED]> writes: > On Saturday 28 October 2006 22:00, Douglas Tutty wrote: >> I'm at the point of choosing which kernel to install: >> >> linux-image-2.6-amd64-generic >> linux-image-2.6.17-2amd64 >> linux-image-2.6-amd64 > > There is absolutely no difference :-) > > In fact the only "real" kernel image package in that list is: > linux-image-2.6.17-2amd64. > the others are just meta packages that pull in that one. > > When in doubt, go with the default (and don't install in expert mode > unless you really need to). > > Cheers, > FJP Shouldn't the default be linux-image-2.6-amd64 so the kernel does get automatically updated to the latest versions? At least with grub there is little harm in adding more kernels because it doesn't "forget" the old ones like lilo. MfG Goswin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
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
