Post new topic   Reply to topic
View previous topic Printable version Log in to check your private messages View next topic
Author Message
finottiOffline
Post subject: can't boot with kernel 3.13  PostPosted: 26.02.2014, 01:48



Joined: 2010-09-12
Posts: 319

Status: Offline
Dear all,

I cannot boot with kernel 3.13. I've tried 3.13-2.slh.3-aptosid-amd64, 3.13-5.slh.1-aptosid-amd64 and a 3.13-4 (which for some reason does not appear when I run kernel-remover). They all freeze, not always in the same place. See the boot screen of my latest attempt (with 3.13-5.slh.1-aptosid-amd64) attached. It always shows "rcu_preempt detected stalls on cpus/tasks", as in the picture, though.

Here is some info about the system:

      Code:

root@debian[/var/log]# infobash -v3
Host/Kernel/OS  "debian" running Linux 3.12-7.slh.2-aptosid-amd64 x86_64 [ aptosid 2010-02 Κῆρες - kde-full - (201009132215) ]
CPU Info        2x Intel Core2 Duo E8400 @ 6144 KB cache flags( sse3 ht nx lm vmx ) clocked at [ 2999.924 MHz ]
Videocard       NVIDIA G86 [GeForce 8500 GT]     [  ]
Network cards   NVIDIA MCP55
                NVIDIA MCP55
Processes 238 | Uptime 12min | Memory 1550.6/7990.7MB | HDD WDC WD1500ADFD-0,WDC WD1001FALS-0,WDC WD20EARX-00P,WDC WD10EALS-00Z Size 4150GB (61%used) | Client Shell | Infobash v3.46


I cannot find any messages in the logs from failed attempts to boot with kernel 3.13. If I can provide any more info, just tell me what I can do.

Best to all,

Luis

EDIT: I tried again without the option "quiet". I've posted a picture of it (and the one attached) in full resolution at http://www.math.utk.edu/~finotti/tmp/



boot2.jpg
 Description:
 Filesize:  168.28 KB
 Viewed:  3908 Time(s)

boot2.jpg


 
 View user's profile Send private message  
Reply with quote Back to top
slhAdministrator
Post subject: RE: can  PostPosted: 26.02.2014, 03:28



Joined: 2010-08-25
Posts: 750

Status: Online!
If you can try to take a photo of the very first Oops message (there seems to be a 2 second delay between the two visible ones, so it might be possible to time it right) as that one would be a lot more reliable (after the first Oops, all bets are off and successive messages might be misleading).

What you can try either way:
      Code:
- add "nouveau.runpm=0" to GRUB_CMDLINE_LINUX in /etc/default/grub
# echo "options nouveau runpm=0" > /etc/modprobe.d/nouveau.conf
# update-initramfs -k 3.13-5.slh.1-aptosid-amd64 -u
# update-grub
# reboot
(of course this expects the most current 3.13 kernel, 3.13-5.slh.1-aptosid-amd64 at this moment, to be installed)
 
 View user's profile Send private message  
Reply with quote Back to top
finottiOffline
Post subject: RE: can  PostPosted: 26.02.2014, 20:35



Joined: 2010-09-12
Posts: 319

Status: Offline
Thanks for the help, slh.

The commands you suggested did not seem to fix it, but it seems that the process did go farther. I took some (very bad -- sorry) pictures of the boot process and put them in the site above (http://www.math.utk.edu/~finotti/tmp/). Please let me know if that is not readable enough, as I can take pictures with a real camera...

The pictures were taken in a range of about 5 minutes (probably less). It seemed to be stuck at the time, but maybe it would go further if I'd waited longer.

Any suggestions would be greatly appreciated.

Best to all,

Luis
 
 View user's profile Send private message  
Reply with quote Back to top
slhAdministrator
Post subject: RE: can  PostPosted: 26.02.2014, 22:24



Joined: 2010-08-25
Posts: 750

Status: Online!
Are you sure that your system still works fine using kernel 3.12?

I'm asking because the (S-)ATA issues in your log already happen before nouveau falls over. As a very first test, I'd suggest to boot into kernel 3.12, run "debsums -as" and then check "dmesg" for ATA errors (and the debsums output for read errors/ problems with the files installed by your packages, the kernel packages in particular).
 
 View user's profile Send private message  
Reply with quote Back to top
finottiOffline
Post subject: RE: can  PostPosted: 27.02.2014, 04:25



Joined: 2010-09-12
Posts: 319

Status: Offline
Thanks again, slh.

The system works "fine". (I'm using it right now.) I am getting some freezes every once in a while, but I thought it was video card related from the only clues in the logs. (See [url="http://www.aptosid.com/index.php?name=PNphpBB2&file=viewtopic&t=2716&highlight="]this thread[/url].)

The ATA errors I've seen before too... They were common, but I changed some sata cables and it seemed to work. I hadn't seen them in a while, but noticed them that time too. I booted 3.13 again and they did not show up. (I took pictures of this boot too, if that would help.)

The debsums command gives:

      Code:

root@debian[/home/finotti]# debsums -as
debsums: changed file /etc/default/dmakms (from dmakms package)
debsums: changed file /usr/share/doc/fuse-utils/changelog.Debian.gz (from fuse-utils package)
debsums: changed file /usr/share/doc/fuse-utils/copyright (from fuse-utils package)
debsums: changed file /var/games/hannah/hiscore.dat (from hannah-data package)
debsums: changed file /etc/default/rcS (from initscripts package)
debsums: changed file /etc/dhcp/dhclient.conf (from isc-dhcp-client package)
debsums: changed file /etc/kde4/kdm/kdmrc (from kdm package)
debsums: changed file /etc/libreoffice/sofficerc (from libreoffice-common package)
debsums: changed file /etc/libreoffice/soffice.sh (from libreoffice-common package)
debsums: changed file /etc/sane.d/dll.conf (from libsane:amd64 package)
debsums: changed file /etc/login.defs (from login package)
debsums: changed file /etc/lvm/lvm.conf (from lvm2 package)
debsums: changed file /etc/minidlna.conf (from minidlna package)
debsums: changed file /etc/minidlna/minidlna.conf (from minidlna package)
debsums: changed file /etc/ssh/ssh_config (from openssh-client package)
debsums: missing file /etc/openvpn/update-resolv-conf (from openvpn package)
debsums: changed file /etc/smartd.conf (from smartmontools package)
debsums: changed file /etc/default/smartmontools (from smartmontools package)


Here is a trimmed dmesg:

      Code:

root@debian[/home/finotti]# dmesg | tail -200
[    1.031550] ata3.00: configured for UDMA/133
[    1.042144] ata5.00: ATAPI: LITE-ON DVDRW LH-20A1S, 9L08, max UDMA/100
[    1.064148] ata5.00: configured for UDMA/100
[    1.064273] firewire_core 0000:05:07.0: created device fw0: GUID 5ad10d8000044b16, S400
[    1.091508] forcedeth 0000:00:11.0: ifname eth0, PHY OUI 0x5043 @ 1, addr 00:04:4b:14:8b:2f
[    1.091511] forcedeth 0000:00:11.0: highdma csum vlan pwrctl mgmt gbit lnktim msi desc-v3
[    1.091765] ACPI: PCI Interrupt Link [AMA1] enabled at IRQ 21
[    1.091773] forcedeth 0000:00:12.0: setting latency timer to 64
[    1.310038] usb 1-7: new high-speed USB device number 4 using ehci-pci
[    1.330022] ata2: SATA link down (SStatus 0 SControl 300)
[    1.330145] scsi 2:0:0:0: Direct-Access     ATA      WDC WD1001FALS-0 05.0 PQ: 0 ANSI: 5
[    1.391024] tsc: Refined TSC clocksource calibration: 2999.992 MHz
[    1.438748] usb 1-7: New USB device found, idVendor=0bb4, idProduct=0c96
[    1.438751] usb 1-7: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[    1.438754] usb 1-7: Product: myTouch 4G
[    1.438757] usb 1-7: Manufacturer: T-Mobile
[    1.438760] usb 1-7: SerialNumber: SH15VRM00126
[    1.443933] usb-storage 1-7:1.0: USB Mass Storage device detected
[    1.443969] scsi8 : usb-storage 1-7:1.0
[    1.444031] usbcore: registered new interface driver usb-storage
[    1.613478] forcedeth 0000:00:12.0: ifname eth1, PHY OUI 0x5043 @ 2, addr 00:04:4b:14:8b:31
[    1.613481] forcedeth 0000:00:12.0: highdma csum vlan pwrctl mgmt gbit lnktim msi desc-v3
[    1.621427] sd 2:0:0:0: [sdb] 1953525168 512-byte logical blocks: (1.00 TB/931 GiB)
[    1.621441] sd 0:0:0:0: [sda] 293046768 512-byte logical blocks: (150 GB/139 GiB)
[    1.621530] sd 2:0:0:0: [sdb] Write Protect is off
[    1.621533] sd 2:0:0:0: [sdb] Mode Sense: 00 3a 00 00
[    1.621545] sd 0:0:0:0: [sda] Write Protect is off
[    1.621548] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
[    1.621566] sd 2:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[    1.621570] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[    1.634291]  sdb: sdb1
[    1.634558] sd 2:0:0:0: [sdb] Attached SCSI disk
[    1.644370]  sda: sda1 sda2 sda3
[    1.644693] sd 0:0:0:0: [sda] Attached SCSI disk
[    1.784031] ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[    1.803388] ata4.00: ATA-8: WDC WD20EARX-00PASB0, 51.0AB51, max UDMA/133
[    1.803391] ata4.00: 3907029168 sectors, multi 16: LBA48 NCQ (depth 31/32)
[    1.806028] usb 2-1: new full-speed USB device number 2 using ohci-pci
[    1.822404] ata4.00: configured for UDMA/133
[    1.822513] scsi 3:0:0:0: Direct-Access     ATA      WDC WD20EARX-00P 51.0 PQ: 0 ANSI: 5
[    1.822645] sd 3:0:0:0: [sdc] 3907029168 512-byte logical blocks: (2.00 TB/1.81 TiB)
[    1.822648] sd 3:0:0:0: [sdc] 4096-byte physical blocks
[    1.822697] sd 3:0:0:0: [sdc] Write Protect is off
[    1.822700] sd 3:0:0:0: [sdc] Mode Sense: 00 3a 00 00
[    1.822722] sd 3:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[    1.824160] scsi 4:0:0:0: CD-ROM            LITE-ON  DVDRW LH-20A1S   9L08 PQ: 0 ANSI: 5
[    1.824919] sd 0:0:0:0: Attached scsi generic sg0 type 0
[    1.824994] sd 2:0:0:0: Attached scsi generic sg1 type 0
[    1.825043] sd 3:0:0:0: Attached scsi generic sg2 type 0
[    1.825075] scsi 4:0:0:0: Attached scsi generic sg3 type 5
[    1.829028] sr0: scsi3-mmc drive: 48x/48x writer dvd-ram cd/rw xa/form2 cdda tray
[    1.829031] cdrom: Uniform CD-ROM driver Revision: 3.20
[    1.829191] sr 4:0:0:0: Attached scsi CD-ROM sr0
[    2.006038] usb 2-1: New USB device found, idVendor=046d, idProduct=c52f
[    2.006042] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[    2.006045] usb 2-1: Product: USB Receiver
[    2.006048] usb 2-1: Manufacturer: Logitech
[    2.013527] hidraw: raw HID events driver (C) Jiri Kosina
[    2.024236] usbcore: registered new interface driver usbhid
[    2.024238] usbhid: USB HID core driver
[    2.025488] input: Logitech USB Receiver as /devices/pci0000:00/0000:00:0b.0/usb2/2-1/2-1:1.0/input/input1
[    2.025548] hid-generic 0003:046D:C52F.0001: input,hidraw0: USB HID v1.11 Mouse [Logitech USB Receiver] on usb-0000:00:0b.0-1/input0
[    2.029136] input: Logitech USB Receiver as /devices/pci0000:00/0000:00:0b.0/usb2/2-1/2-1:1.1/input/input2
[    2.029210] hid-generic 0003:046D:C52F.0002: input,hiddev0,hidraw1: USB HID v1.11 Device [Logitech USB Receiver] on usb-0000:00:0b.0-1/input1
[    2.243879]  sdc: sdc1
[    2.244091] sd 3:0:0:0: [sdc] Attached SCSI disk
[    2.273037] usb 2-2: new full-speed USB device number 3 using ohci-pci
[    2.278032] ata6: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[    2.335286] ata6.00: ATA-8: WDC WD10EALS-00Z8A0, 05.01D05, max UDMA/133
[    2.335289] ata6.00: 1953525168 sectors, multi 16: LBA48 NCQ (depth 31/32)
[    2.341278] ata6.00: configured for UDMA/133
[    2.341386] scsi 5:0:0:0: Direct-Access     ATA      WDC WD10EALS-00Z 05.0 PQ: 0 ANSI: 5
[    2.341518] sd 5:0:0:0: [sdd] 1953525168 512-byte logical blocks: (1.00 TB/931 GiB)
[    2.341568] sd 5:0:0:0: [sdd] Write Protect is off
[    2.341571] sd 5:0:0:0: [sdd] Mode Sense: 00 3a 00 00
[    2.341593] sd 5:0:0:0: [sdd] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[    2.341792] sd 5:0:0:0: Attached scsi generic sg4 type 0
[    2.341942] ata8: port disabled--ignoring
[    2.377351]  sdd: sdd1 sdd2 <sdd5>
[    2.377692] sd 5:0:0:0: [sdd] Attached SCSI disk
[    2.391062] Switched to clocksource tsc
[    2.438056] usb 2-2: device descriptor read/64, error -62
[    2.449142] scsi 8:0:0:0: Direct-Access     T-Mobile myTouch 4G       0100 PQ: 0 ANSI: 2
[    2.449310] sd 8:0:0:0: Attached scsi generic sg5 type 0
[    2.458127] sd 8:0:0:0: [sde] Attached SCSI removable disk
[    2.703035] usb 2-2: device descriptor read/64, error -62
[    2.720489] device-mapper: uevent: version 1.0.3
[    2.720680] device-mapper: ioctl: 4.26.0-ioctl (2013-08-15) initialised: dm-devel@redhat.com
[    2.727596] PM: Starting manual resume from disk
[    2.732753] EXT4-fs (sda2): INFO: recovery required on readonly filesystem
[    2.732756] EXT4-fs (sda2): write access will be enabled during recovery
[    2.948230] EXT4-fs (sda2): recovery complete
[    2.953958] EXT4-fs (sda2): mounted filesystem with ordered data mode. Opts: (null)
[    2.961026] usb 2-2: new full-speed USB device number 4 using ohci-pci
[    3.126025] usb 2-2: device descriptor read/64, error -62
[    3.391021] usb 2-2: device descriptor read/64, error -62
[    3.649017] usb 2-2: new full-speed USB device number 5 using ohci-pci
[    4.054012] usb 2-2: device not accepting address 5, error -62
[    4.211025] usb 2-2: new full-speed USB device number 6 using ohci-pci
[    4.561319] systemd-udevd[427]: starting version 204
[    4.617012] usb 2-2: device not accepting address 6, error -62
[    4.617090] hub 2-0:1.0: unable to enumerate USB device on port 2
[    5.229771] input: Power Button as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input3
[    5.229777] ACPI: Power Button [PWRB]
[    5.229863] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input4
[    5.229865] ACPI: Power Button [PWRF]
[    5.308196] [drm] Initialized drm 1.1.0 20060810
[    5.409643] input: PC Speaker as /devices/platform/pcspkr/input/input5
[    5.586181] i2c i2c-0: nForce2 SMBus adapter at 0xf400
[    5.586199] i2c i2c-1: nForce2 SMBus adapter at 0xf000
[    5.616062] wmi: Mapper loaded
[    5.660759] nv_tco: NV TCO WatchDog Timer Driver v0.01
[    5.660823] nv_tco: Watchdog reboot detected
[    5.660865] nv_tco: initialized (0x1440). heartbeat=30 sec (nowayout=0)
[    5.728269] pcieport 0000:02:00.0: driver skip pci_set_master, fix it!
[    5.728548] ACPI: PCI Interrupt Link [AXV5] enabled at IRQ 16
[    5.728691] [drm] hdmi device  not found 3 0 1
[    5.728753] nouveau  [  DEVICE][0000:03:00.0] BOOT0  : 0x086100a2
[    5.728755] nouveau  [  DEVICE][0000:03:00.0] Chipset: G86 (NV86)
[    5.728757] nouveau  [  DEVICE][0000:03:00.0] Family : NV50
[    5.729342] nouveau  [   VBIOS][0000:03:00.0] checking PRAMIN for image...
[    5.788142] nouveau  [   VBIOS][0000:03:00.0] ... appears to be valid
[    5.788145] nouveau  [   VBIOS][0000:03:00.0] using image from PRAMIN
[    5.788275] nouveau  [   VBIOS][0000:03:00.0] BIT signature found
[    5.788277] nouveau  [   VBIOS][0000:03:00.0] version 60.86.34.00.13
[    5.808405] nouveau  [     PFB][0000:03:00.0] RAM type: DDR2
[    5.808407] nouveau  [     PFB][0000:03:00.0] RAM size: 256 MiB
[    5.808409] nouveau  [     PFB][0000:03:00.0]    ZCOMP: 1292 tags
[    5.829980] nouveau  [  PTHERM][0000:03:00.0] FAN control: PWM
[    5.829989] nouveau  [  PTHERM][0000:03:00.0] fan management: disabled
[    5.829993] nouveau  [  PTHERM][0000:03:00.0] internal sensor: yes
[    5.830015] nouveau  [  PTHERM][0000:03:00.0] temperature (88 C) hit the 'fanboost' threshold
[    5.830027] nouveau  [  PTHERM][0000:03:00.0] fan management: automatic
[    5.830132] [TTM] Zone  kernel: Available graphics memory: 4091254 kiB
[    5.830134] [TTM] Zone   dma32: Available graphics memory: 2097152 kiB
[    5.830135] [TTM] Initializing pool allocator
[    5.830139] [TTM] Initializing DMA pool allocator
[    5.830147] nouveau  [     DRM] VRAM: 256 MiB
[    5.830149] nouveau  [     DRM] GART: 1048576 MiB
[    5.830152] nouveau  [     DRM] TMDS table version 2.0
[    5.830153] nouveau  [     DRM] DCB version 4.0
[    5.830156] nouveau  [     DRM] DCB outp 00: 02000300 00000028
[    5.830158] nouveau  [     DRM] DCB outp 01: 04011310 00010028
[    5.830160] nouveau  [     DRM] DCB outp 02: 02011312 00000030
[    5.830161] nouveau  [     DRM] DCB outp 03: 010223f1 00c0c080
[    5.830163] nouveau  [     DRM] DCB conn 00: 1030
[    5.830165] nouveau  [     DRM] DCB conn 01: 0100
[    5.830167] nouveau  [     DRM] DCB conn 02: 0210
[    5.830169] nouveau  [     DRM] DCB conn 03: 0211
[    5.830170] nouveau  [     DRM] DCB conn 04: 0213
[    5.835709] nouveau W[     DRM] failed to create encoder 0/1/0: -19
[    5.835712] nouveau W[     DRM] TV-1 has no encoders, removing
[    5.835729] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010).
[    5.835731] [drm] No driver support for vblank timestamp query.
[    5.835865] nouveau  [     DRM] 1 available performance level(s)
[    5.835868] nouveau  [     DRM] 0: core 459MHz shader 918MHz memory 400MHz fanspeed 100%
[    5.835871] nouveau  [     DRM] c: core 459MHz shader 918MHz memory 399MHz voltage 1320mV fanspeed 97%
[    6.091634] nouveau  [     DRM] MM: using CRYPT for buffer copies
[    6.139648] nouveau  [     DRM] allocated 1280x1024 fb: 0x60000, bo ffff880243f78c00
[    6.139704] fbcon: nouveaufb (fb0) is primary device
[    6.221306] Console: switching to colour frame buffer device 160x64
[    6.222737] nouveau 0000:03:00.0: fb0: nouveaufb frame buffer device
[    6.222739] nouveau 0000:03:00.0: registered panic notifier
[    6.222742] [drm] Initialized nouveau 1.1.1 20120801 for 0000:03:00.0 on minor 0
[    6.357610] nouveau  [  PTHERM][0000:03:00.0] temperature (86 C) went below the 'fanboost' threshold
[    6.606850] ACPI: PCI Interrupt Link [APC2] enabled at IRQ 17
[    7.845592] Adding 15623176k swap on /dev/sdd5.  Priority:-1 extents:1 across:15623176k FS
[    7.886886] Adding 8193144k swap on /dev/sda3.  Priority:-2 extents:1 across:8193144k FS
[    7.910795] EXT4-fs (sda2): re-mounted. Opts: (null)
[    8.192772] EXT4-fs (sda2): re-mounted. Opts: errors=remount-ro,barrier=0
[    8.649442] fuse init (API version 7.22)
[   10.526752] EXT4-fs (sdd6): mounted filesystem with ordered data mode. Opts: errors=remount-ro
[   10.554173] EXT4-fs (sdb1): mounted filesystem with ordered data mode. Opts: (null)
[   10.577463] EXT4-fs (sdd7): mounted filesystem with ordered data mode. Opts: (null)
[   10.628138] EXT4-fs (sdc1): mounted filesystem with ordered data mode. Opts: (null)
[   11.782017] forcedeth 0000:00:11.0: irq 42 for MSI/MSI-X
[   11.782044] forcedeth 0000:00:11.0 eth0: MSI enabled
[   11.783520] forcedeth 0000:00:12.0: irq 43 for MSI/MSI-X
[   11.783540] forcedeth 0000:00:12.0 eth1: MSI enabled
[   11.783761] forcedeth 0000:00:12.0 eth1: no link during initialization
[   11.784174] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
[   11.954504] NET: Registered protocol family 17
[   15.143207] Bluetooth: Core ver 2.16
[   15.143219] NET: Registered protocol family 31
[   15.143221] Bluetooth: HCI device and connection manager initialized
[   15.143229] Bluetooth: HCI socket layer initialized
[   15.143231] Bluetooth: L2CAP socket layer initialized
[   15.143236] Bluetooth: SCO socket layer initialized
[   15.180981] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[   15.180983] Bluetooth: BNEP filters: protocol multicast
[   15.180989] Bluetooth: BNEP socket layer initialized
[   15.330037] Bluetooth: RFCOMM TTY layer initialized
[   15.330050] Bluetooth: RFCOMM socket layer initialized
[   15.330051] Bluetooth: RFCOMM ver 1.11
[   15.468705] lp: driver loaded but no devices found
[   15.482489] ppdev: user-space parallel port driver
[   17.635518] tun: Universal TUN/TAP device driver, 1.6
[   17.635521] tun: (C) 1999-2004 Max Krasnyansky <maxk>
[  972.349043] lp: driver loaded but no devices found
[  972.592196] st: Version 20101219, fixed bufsize 32768, s/g segs 256


Does anything seem wrong? I thought of installing a debian kernel 3.13 to check, but I did not know if it would mess things up and it wanted to install some other stuff, so I aborted...

      Code:

root@debian[/home/finotti]# apt-get install linux-image-3.13-1-amd64 linux-headers-3.13-1-amd64
Reading package lists... Done
Building dependency tree       
Reading state information... Done
The following extra packages will be installed:
  libuuid-perl linux-base linux-compiler-gcc-4.8-x86 linux-headers-3.13-1-common linux-kbuild-3.13
Suggested packages:
  linux-doc-3.13 debian-kernel-handbook
The following NEW packages will be installed:
  libuuid-perl linux-base linux-compiler-gcc-4.8-x86 linux-headers-3.13-1-amd64
  linux-headers-3.13-1-common linux-image-3.13-1-amd64 linux-kbuild-3.13
0 upgraded, 7 newly installed, 0 to remove and 134 not upgraded.
Need to get 35.4 MB of archives.
After this operation, 164 MB of additional disk space will be used.
Do you want to continue? [Y/n] n
Abort.


Just let me know if there is anything else I can do. (Maybe is time to buy a new computer...)

Thanks,

Luis
 
 View user's profile Send private message  
Reply with quote Back to top
slhAdministrator
Post subject: RE: can  PostPosted: 03.03.2014, 03:34



Joined: 2010-08-25
Posts: 750

Status: Online!
The debsums output appears to be o.k.

The previously mentioned SATA error messages however are scary, in all likelyness they point at hardware problems/ dying disks (or cables). Technically it would be possible that these are a false alarm, if they only happen with 3.13, but not 3.12 - but this is not very likely (and would point and deeper problems with basic chipset support).

So far I can't reproduce any problems with nForce4, nForce 405 or (much) older nVidia graphics using nouveau. The other problem is the amount of different error messages you're experiencing (which pushed out the first complaint we've been looking for so far).
 
 View user's profile Send private message  
Reply with quote Back to top
finottiOffline
Post subject: RE: can  PostPosted: 03.03.2014, 04:15



Joined: 2010-09-12
Posts: 319

Status: Offline
Thanks again, slh. The lock ups (in 3.12) are happening more frequently these days, but I am not seeing the sata errors, which used to show up often.

I'm thinking of just building a new computer...

Thanks for your help,

Luis
 
 View user's profile Send private message  
Reply with quote Back to top
spockOffline
Post subject: Strange lockups  PostPosted: 03.03.2014, 10:02



Joined: 2010-09-11
Posts: 80
Location: Near Milton Keynes, UK
Status: Offline
      finotti wrote:
Thanks again, slh. The lock ups (in 3.12) are happening more frequently these days, but I am not seeing the sata errors, which used to show up often.

I'm thinking of just building a new computer...


I too started getting some very weird lockups a fortnight ago. I'm not suggesting there is a software bug with Debian or aptosid, but I just felt compelled to post my experiences, as the issue has puzzled my 30 years' computing experience, and I thought you may appreciate some moral support Smile

My computer, (which is nearly twice as old as yours!) started randomly crashing - the screen just freezing where it stood or with bizarre graphic corruption. Confused No keys worked, neither CTRL+ALT+F1 nor SysRq Magic REISUB key sequence. Only a hard reset would do anything. The system would then reboot and then crash again some time later.

Naturally my computer engineer self assumed hardware failure, so I checked fans, cleaned out dust, removed and tested RAM (all OK). The lockups got progressively more frequent, happening after only a few minutes of operation. Was this SSD/PSU/CPU/mobo failure? All these would be expected on such an ancient machine. My girlfriend even said that everything must die at some point.

I then did the daftest thing: DU'ed thinking that a new kernel may "help" Embarassed Obviously the machine crashed hard right in the crucial bit of the GRUB update, Rolling Eyes rendering the machine unbootable with just a GRUB prompt... Crying or Very sad Terrified, I Googled and read up on how to actually issue commands to boot the machine, gained some knowledge, Idea and was able to rescue my installation again Surprised

But still the lockups got worse, so I tried a different PSU I had lying around. The computer now started refusing to even boot, behaving like HAL dying in the film 2001 Sad So I resigned myself to the fact that I'd have to buy a new computer ASAP, as this is my business machine that runs my empire.

I spent a few days researching the latest PC gear, then wondering if I could re-use the old case, just thought of trying the original PSU again before I ripped it all out, and... it worked fine Shocked Not only that, it remained operational all day with no lockups Very Happy I tentatively tried running different programs one at a time and gradually trusted it enough to run backups and catch up with myself after a week of downtime. Obviously the spare ancient PSU was not up to running the motherboard. Something seems to have fixed the original fault, be it software (unlikely) or hardware. If I get time to test more to discover the real cause then I will, but this week is hectic.

So if anyone's still reading this, my reason for posting was just to say that sometimes weird stuff happens, and don't rule out Pilot Error (especially in my case). Often just walking away from a problem will yield an unforeseen solution... Smile
 
 View user's profile Send private message Visit poster's website  
Reply with quote Back to top
Display posts from previous:     
Jump to:  
All times are GMT - 12 Hours
Post new topic   Reply to topic
View previous topic Printable version Log in to check your private messages View next topic
Powered by Zafenio