Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
[Solved] X si blocca occupando la CPU
View unanswered posts
View posts from last 24 hours
View posts from last 7 days

Goto page Previous  1, 2, 3  Next  
Reply to topic    Gentoo Forums Forum Index Forum italiano (Italian)
View previous topic :: View next topic  
Author Message
Peach
Advocate
Advocate


Joined: 08 Mar 2003
Posts: 3686
Location: London, UK

PostPosted: Sat Aug 18, 2007 10:19 am    Post subject: Reply with quote

allora proviamo così, potresti postare l'output di:
Code:
# grep -e WW -e EE /var/log/Xorg.0.log

_________________
Gentoo user since 2004.
"It's all fun and games, until someone loses an eye" - mom
Back to top
View user's profile Send private message
Kernel78
Moderator
Moderator


Joined: 24 Jun 2005
Posts: 3652

PostPosted: Sat Aug 18, 2007 10:51 am    Post subject: Reply with quote

Non te la prendere ma in questo periodo ho notato che spacco sempre il capello in 4 (e a volte spacco anche altro ...)
Sarebbe più corretto
Code:
grep -E '^\((WW|EE)\)' /var/log/Xorg.0.log

_________________
Le tre grandi virtù di un programmatore: pigrizia, impazienza e arroganza. (Larry Wall).
Prima di postare un file togli i commenti con
Code:
grep -vE '(^[[:space:]]*($|(#|!|;|//)))'
Back to top
View user's profile Send private message
Luc484
Veteran
Veteran


Joined: 26 Mar 2005
Posts: 1035
Location: Italy

PostPosted: Sat Aug 18, 2007 10:58 am    Post subject: Reply with quote

Questo è l'output, solo che non c'è modo di sapere a quando risalgono le righe, o sbaglio?

Code:
(WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
(EE) Failed to load /usr/lib/xorg/modules//vnc.so
(EE) Failed to load module "vnc" (loader failed, 7)
(WW) RADEON(0): Failed to detect secondary monitor, MergedFB/Clone mode disabled
(WW) RADEON(0): DRI init changed memory map, adjusting ...
(WW) RADEON(0):   MC_FB_LOCATION  was: 0xdbffd800 is: 0xdbffd800
(WW) RADEON(0):   MC_AGP_LOCATION was: 0xffffffc0 is: 0xd07fd000
(WW) RADEON(0): Option "InternalAGPGART" is not used
(WW) AIGLX: 3D driver claims to not support visual 0x23
(WW) AIGLX: 3D driver claims to not support visual 0x24
(WW) AIGLX: 3D driver claims to not support visual 0x25
(WW) AIGLX: 3D driver claims to not support visual 0x26
(WW) AIGLX: 3D driver claims to not support visual 0x27
(WW) AIGLX: 3D driver claims to not support visual 0x28
(WW) AIGLX: 3D driver claims to not support visual 0x29
(WW) AIGLX: 3D driver claims to not support visual 0x2a
(WW) AIGLX: 3D driver claims to not support visual 0x2b
(WW) AIGLX: 3D driver claims to not support visual 0x2c
(WW) AIGLX: 3D driver claims to not support visual 0x2d
(WW) AIGLX: 3D driver claims to not support visual 0x2e
(WW) AIGLX: 3D driver claims to not support visual 0x2f
(WW) AIGLX: 3D driver claims to not support visual 0x30
(WW) AIGLX: 3D driver claims to not support visual 0x31
(WW) AIGLX: 3D driver claims to not support visual 0x32
Back to top
View user's profile Send private message
cloc3
Advocate
Advocate


Joined: 13 Jan 2004
Posts: 4656
Location: http://www.gentoo-users.org/user/cloc3/

PostPosted: Sat Aug 18, 2007 11:17 am    Post subject: Reply with quote

Luc484 wrote:
Questo è l'output, solo che non c'è modo di sapere a quando risalgono le righe, o sbaglio?

Xorg.0.log si rigenera ad ogni riavvio di X. normalmente, e salvo impostazione diversa, viene conservata un'unica copia di cache relativa alla sessione precedente. quindi quell'output è relativo alla sessione attuale che stai utilizzando, probabilemente si riproduce ad ogni avvio ed è quindi una buona base per le indagini.

a prima vista (non uso schede ati) direi che iltuo file /etc/X11/xorg.conf è mal definito. come minimo puoi togliere il load al driver vnc e forse devi definire meglio le caratteristiche del tuo schermo.
_________________
vu vu vu
gentù
mi piaci tu
Back to top
View user's profile Send private message
Luc484
Veteran
Veteran


Joined: 26 Mar 2005
Posts: 1035
Location: Italy

PostPosted: Sat Aug 18, 2007 12:44 pm    Post subject: Reply with quote

Si beh, vnc è ancora un problema aperto :) sembra che abbia deciso di non funzionare, ma amen, sistemerò quando avrò tempo. Il monitor mi pareva ok, mi pareva che le impostazioni siano corrette. Ho sbagliato qualcosa? Comunque nulla che possa essere legato al problema in questione o si?
Grazie a tutti per il vostro tempo.
Back to top
View user's profile Send private message
exebeje
n00b
n00b


Joined: 18 Aug 2004
Posts: 38

PostPosted: Sun Aug 19, 2007 8:10 pm    Post subject: Reply with quote

Quote:
(WW) RADEON(0): Option "InternalAGPGART" is not used


po esse il supporto ad agp nel kernel?
_________________
"just because you're paranoid it don't mean they're not after you"
Back to top
View user's profile Send private message
Luc484
Veteran
Veteran


Joined: 26 Mar 2005
Posts: 1035
Location: Italy

PostPosted: Sun Aug 19, 2007 10:03 pm    Post subject: Reply with quote

Ma quel messaggio non significa che non viene utilizzato? Quindi non è attivo? Dici che dovrei provare a toglierlo dal kernel?
Back to top
View user's profile Send private message
GuN_jAcK
l33t
l33t


Joined: 23 Mar 2005
Posts: 823
Location: Prague, Czech Republic

PostPosted: Sun Aug 19, 2007 11:15 pm    Post subject: Reply with quote

segnalo lo stesso problema... quando ho fatto update dalle ferie mi si presenta lo stesso identico problema.. ora provo a fare un paio di test e vi faccio sapere dettagliatamente...
_________________
Rispondi in maniera intelligente anche a chi ti tratta stupidamente.
Back to top
View user's profile Send private message
exebeje
n00b
n00b


Joined: 18 Aug 2004
Posts: 38

PostPosted: Mon Aug 20, 2007 2:22 pm    Post subject: Reply with quote

Luc484, no dicevo semmai il contario, ma è solo un WW e non un EE, dunque se l'hai già abilitato nel kernel è probabilmente dovuto a qualche EE precedente! :roll:
_________________
"just because you're paranoid it don't mean they're not after you"
Back to top
View user's profile Send private message
GuN_jAcK
l33t
l33t


Joined: 23 Mar 2005
Posts: 823
Location: Prague, Czech Republic

PostPosted: Mon Aug 20, 2007 4:04 pm    Post subject: Reply with quote

a me succede ogni volta che non uso a lungo il pc.. tanto per capirci quando va in standby e spenge il monitor... una volta che si torna si inchioda... ho provato ora a reinstallare i driver video e rifare la conf.... aspetto ora che rivada in standby...
_________________
Rispondi in maniera intelligente anche a chi ti tratta stupidamente.
Back to top
View user's profile Send private message
Luc484
Veteran
Veteran


Joined: 26 Mar 2005
Posts: 1035
Location: Italy

PostPosted: Mon Aug 20, 2007 4:08 pm    Post subject: Reply with quote

Ah. Questo è interessante. Se fosse così sarebbe riproducibile. Effettivamente non ricordo di aver mai notato che mi si bloccasse mentre lo usavo. Almeno a memoria. Potrebbe essere proprio come dici tu. Adesso provo anche io.
Back to top
View user's profile Send private message
GuN_jAcK
l33t
l33t


Joined: 23 Mar 2005
Posts: 823
Location: Prague, Czech Republic

PostPosted: Mon Aug 20, 2007 4:42 pm    Post subject: Reply with quote

ho reinstallato sia nvidia drivers che il settings.. ho unloadato i moduli e ricaricati, riavviato il sistema e sembra ora che vada tutto a posto... staremo a vedere... anhe perchè come errore è bello fastidioso! :x
_________________
Rispondi in maniera intelligente anche a chi ti tratta stupidamente.
Back to top
View user's profile Send private message
GuN_jAcK
l33t
l33t


Joined: 23 Mar 2005
Posts: 823
Location: Prague, Czech Republic

PostPosted: Mon Aug 20, 2007 6:01 pm    Post subject: Reply with quote

ancora tutto ok... sembra che ho risolto.. la prova del 9 sarà se resiste tutta la notte acceso sta brutta bestia brutta... ^_^
_________________
Rispondi in maniera intelligente anche a chi ti tratta stupidamente.
Back to top
View user's profile Send private message
Luc484
Veteran
Veteran


Joined: 26 Mar 2005
Posts: 1035
Location: Italy

PostPosted: Tue Aug 21, 2007 12:16 am    Post subject: Reply with quote

Oh oh... cosa strana. Ho avuto il problema proprio ora. Però stranamente X è impazzito e poi guarito nel giro di qualche minuto. Di solito va avanti indefinitamente. ll sistema lo stavo usando, anche se era partito lo screen saver qualche minuto prima.
Mentre faceva il problema mi sono collegato via sshed ho preso un bel dmesg come mi era stato chiesto:

Code:
cluca luca # dmesg
Linux version 2.6.18-gentoo-r3 (root@cluca) (gcc version 4.1.1 (Gentoo 4.1.1-r1)) #2 Wed Dec 6 09:31:41 CET 2006
BIOS-provided physical RAM map:
 BIOS-e820: 0000000000000000 - 00000000000a0000 (usable)
 BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
 BIOS-e820: 0000000000100000 - 000000002fff0000 (usable)
 BIOS-e820: 000000002fff0000 - 000000002fff3000 (ACPI NVS)
 BIOS-e820: 000000002fff3000 - 0000000030000000 (ACPI data)
 BIOS-e820: 00000000fec00000 - 00000000fec01000 (reserved)
 BIOS-e820: 00000000fee00000 - 00000000fee01000 (reserved)
 BIOS-e820: 00000000ffff0000 - 0000000100000000 (reserved)
767MB LOWMEM available.
On node 0 totalpages: 196592
  DMA zone: 4096 pages, LIFO batch:0
  Normal zone: 192496 pages, LIFO batch:31
DMI 2.3 present.
Allocating PCI resources starting at 40000000 (gap: 30000000:cec00000)
Detected 2086.594 MHz processor.
Built 1 zonelists.  Total pages: 196592
Kernel command line: root=/dev/hda1 nodevfs udev devfs=nomount
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Initializing CPU#0
PID hash table entries: 4096 (order: 12, 16384 bytes)
Speakup v-2.00 CVS: Tue Aug 1 11:16:55 EDT 2006 : initialized
Console: colour VGA+ 80x25
Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
Memory: 775540k/786368k available (2246k kernel code, 10292k reserved, 714k data, 144k init, 0k highmem)
Checking if this processor honours the WP bit even in supervisor mode... Ok.
Calibrating delay using timer specific routine.. 4176.77 BogoMIPS (lpj=8353549)
Mount-cache hash table entries: 512
CPU: After generic identify, caps: 0383fbff c1c3fbff 00000000 00000000 00000000 00000000 00000000
CPU: After vendor identify, caps: 0383fbff c1c3fbff 00000000 00000000 00000000 00000000 00000000
CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
CPU: L2 Cache: 512K (64 bytes/line)
CPU: After all inits, caps: 0383fbff c1c3fbff 00000000 00000420 00000000 00000000 00000000
Intel machine check architecture supported.
Intel machine check reporting enabled on CPU#0.
CPU: AMD Athlon(tm) XP 2800+ stepping 00
Checking 'hlt' instruction... OK.
NET: Registered protocol family 16
PCI: PCI BIOS revision 2.10 entry at 0xf9d60, last bus=1
PCI: Using configuration type 1
Setting up standard PCI resources
Linux Plug and Play Support v0.97 (c) Adam Belay
SCSI subsystem initialized
usbcore: registered new driver usbfs
usbcore: registered new driver hub
PCI: Probing PCI hardware
PCI: Probing PCI hardware (bus 00)
PCI quirk: region 4000-407f claimed by vt8235 PM
PCI quirk: region 5000-500f claimed by vt8235 SMB
Boot video device is 0000:01:00.0
PCI: Using IRQ router default [1106/3189] at 0000:00:00.0
Bluetooth: Core ver 2.10
NET: Registered protocol family 31
Bluetooth: HCI device and connection manager initialized
Bluetooth: HCI socket layer initialized
PCI: Bridge: 0000:00:01.0
  IO window: c000-cfff
  MEM window: e0000000-e1ffffff
  PREFETCH window: d8000000-dfffffff
PCI: Setting latency timer of device 0000:00:01.0 to 64
NET: Registered protocol family 2
IP route cache hash table entries: 32768 (order: 5, 131072 bytes)
TCP established hash table entries: 131072 (order: 7, 524288 bytes)
TCP bind hash table entries: 65536 (order: 6, 262144 bytes)
TCP: Hash tables configured (established 131072 bind 65536)
TCP reno registered
Machine check exception polling timer started.
Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
SGI XFS with large block numbers, no debug enabled
Initializing Cryptographic API
io scheduler noop registered
io scheduler anticipatory registered (default)
io scheduler deadline registered
io scheduler cfq registered
Real Time Clock Driver v1.12ac
Non-volatile memory driver v1.2
initialized device: /dev/synth, node ( MAJOR 10, MINOR 25 )
Linux agpgart interface v0.101 (c) Dave Jones
agpgart: Detected VIA KT400/KT400A/KT600 chipset
agpgart: AGP aperture is 128M @ 0xd0000000
vesafb: ATI Technologies Inc., R100, 01.00 (OEM: ATI RADEON VE)
vesafb: VBE version: 2.0
vesafb: protected mode interface info at c000:5490
vesafb: pmi: set display start = c00c5524, set palette = c00c5570
vesafb: pmi: ports = c010 c016 c054 c038 c03c c05c c000 c004 c0b0 c0b2 c0b4
vesafb: no monitor limits have been set
vesafb: scrolling: redraw
vesafb: VBE state buffer size cannot be determined (eax: 0x0)
Console: switching to colour frame buffer device 80x30
vesafb: framebuffer at 0xd8000000, mapped to 0xf0880000, using 10240k, total 65536k
fb0: VESA VGA frame buffer device
Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing disabled
serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
serial8250: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
PNP: No PS/2 controller found. Probing ports directly.
serio: i8042 AUX port at 0x60,0x64 irq 12
serio: i8042 KBD port at 0x60,0x64 irq 1
mice: PS/2 mouse device common for all mice
Floppy drive(s): fd0 is 1.44M
FDC 0 is a post-1991 82077
RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
loop: loaded (max 8 devices)
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
VP_IDE: IDE controller at PCI slot 0000:00:11.1
PCI: VIA IRQ fixup for 0000:00:11.1, from 255 to 0
VP_IDE: chipset revision 6
VP_IDE: not 100% native mode: will probe irqs later
VP_IDE: VIA vt8235 (rev 00) IDE UDMA133 controller on pci0000:00:11.1
    ide0: BM-DMA at 0xe400-0xe407, BIOS settings: hda:DMA, hdb:DMA
    ide1: BM-DMA at 0xe408-0xe40f, BIOS settings: hdc:DMA, hdd:DMA
Probing IDE interface ide0...
input: AT Translated Set 2 keyboard as /class/input/input0
hda: Maxtor 6Y080L0, ATA DISK drive
hdb: WDC WD1600JB-00GVA0, ATA DISK drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
Probing IDE interface ide1...
hdc: ASUS CD-S500/A, ATAPI CD/DVD-ROM drive
hdd: HL-DT-ST GCE-8320B, ATAPI CD/DVD-ROM drive
ide1 at 0x170-0x177,0x376 on irq 15
hda: max request size: 128KiB
hda: 160086528 sectors (81964 MB) w/2048KiB Cache, CHS=65535/16/63, UDMA(133)
hda: cache flushes supported
 hda: hda1 hda2 hda3 hda4
hdb: max request size: 512KiB
hdb: 312581808 sectors (160041 MB) w/8192KiB Cache, CHS=19457/255/63, UDMA(100)
hdb: cache flushes supported
 hdb: hdb1 hdb2
hdc: ATAPI 50X CD-ROM drive, 128kB Cache, UDMA(33)
Uniform CD-ROM driver Revision: 3.20
hdd: ATAPI 40X CD-ROM CD-R/RW drive, 8192kB Cache, DMA
ide-floppy driver 0.99.newide
st: Version 20050830, fixed bufsize 32768, s/g segs 256
ehci_hcd 0000:00:10.3: EHCI Host Controller
ehci_hcd 0000:00:10.3: new USB bus registered, assigned bus number 1
ehci_hcd 0000:00:10.3: irq 10, io mem 0xe2001000
ehci_hcd 0000:00:10.3: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 6 ports detected
ohci_hcd: 2005 April 22 USB 1.1 'Open' Host Controller (OHCI) Driver (PCI)
USB Universal Host Controller Interface driver v3.0
uhci_hcd 0000:00:10.0: UHCI Host Controller
uhci_hcd 0000:00:10.0: new USB bus registered, assigned bus number 2
uhci_hcd 0000:00:10.0: irq 12, io base 0x0000d800
usb usb2: configuration #1 chosen from 1 choice
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 2 ports detected
uhci_hcd 0000:00:10.1: UHCI Host Controller
uhci_hcd 0000:00:10.1: new USB bus registered, assigned bus number 3
uhci_hcd 0000:00:10.1: irq 11, io base 0x0000dc00
usb usb3: configuration #1 chosen from 1 choice
hub 3-0:1.0: USB hub found
hub 3-0:1.0: 2 ports detected
uhci_hcd 0000:00:10.2: UHCI Host Controller
uhci_hcd 0000:00:10.2: new USB bus registered, assigned bus number 4
uhci_hcd 0000:00:10.2: irq 11, io base 0x0000e000
usb usb4: configuration #1 chosen from 1 choice
hub 4-0:1.0: USB hub found
hub 4-0:1.0: 2 ports detected
usb 2-1: new low speed USB device using uhci_hcd and address 2
usb 2-1: configuration #1 chosen from 1 choice
usbcore: registered new driver usblp
drivers/usb/class/usblp.c: v0.13: USB Printer Device Class driver
Initializing USB Mass Storage driver...
usbcore: registered new driver usb-storage
USB Mass Storage support registered.
input: Logitech USB-PS/2 Optical Mouse as /class/input/input1
input: USB HID v1.10 Mouse [Logitech USB-PS/2 Optical Mouse] on usb-0000:00:10.0-1
usbcore: registered new driver usbhid
drivers/usb/input/hid-core.c: v2.6:USB HID core driver
Bluetooth: HCI UART driver ver 2.2
Bluetooth: HCI H4 protocol initialized
Bluetooth: HCI BCSP protocol initialized
Advanced Linux Sound Architecture Driver Version 1.0.12rc1 (Thu Jun 22 13:55:50 2006 UTC).
ALSA device list:
  No soundcards found.
TCP bic registered
NET: Registered protocol family 1
NET: Registered protocol family 17
Using IPI Shortcut mode
Time: tsc clocksource has been installed.
kjournald starting.  Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
VFS: Mounted root (ext3 filesystem) readonly.
Freeing unused kernel memory: 144k freed
8139too Fast Ethernet driver 0.9.27
eth0: RealTek RTL8139 at 0xf0820000, 00:20:ed:65:88:68, IRQ 11
eth0:  Identified 8139 chip type 'RTL-8100B/8139D'
PCI: Setting latency timer of device 0000:00:11.5 to 64
udev: renamed network interface eth0 to eth1
ne2k-pci.c:v1.03 9/22/2003 D. Becker/P. Gortmaker
  http://www.scyld.com/network/ne2k-pci.html
eth0: RealTek RTL-8029 found at 0xd400, IRQ 10, 00:40:33:53:DC:88.
EXT3 FS on hda1, internal journal
kjournald starting.  Commit interval 5 seconds
EXT3 FS on hda4, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS on hdb1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS on hdb2, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
Adding 500464k swap on /dev/hda3.  Priority:-1 extents:1 across:500464k
Bluetooth: L2CAP ver 2.8
Bluetooth: L2CAP socket layer initialized
Bluetooth: RFCOMM socket layer initialized
Bluetooth: RFCOMM TTY layer initialized
Bluetooth: RFCOMM ver 1.8
it87: Found IT8705F chip at 0x290, revision 2
it87-isa 9191-0290: Detected broken BIOS defaults, disabling PWM interface
eth1: link up, 100Mbps, full-duplex, lpa 0x45E1
CSLIP: code copyright 1989 Regents of the University of California
PPP generic driver version 2.4.2
NET: Registered protocol family 24
ip_tables: (C) 2000-2006 Netfilter Core Team
ip_conntrack version 2.4 (6143 buckets, 49144 max) - 208 bytes per conntrack
[drm] Initialized drm 1.0.1 20051102
PCI: Unable to reserve mem region #1:8000000@d8000000 for device 0000:01:00.0
[drm] Initialized radeon 1.25.0 20060524 on minor 0:
[drm] Used old pci detect: framebuffer loaded
mtrr: 0xd8000000,0x8000000 overlaps existing 0xd8000000,0x4000000
mtrr: 0xd8000000,0x8000000 overlaps existing 0xd8000000,0x4000000
mtrr: 0xd8000000,0x8000000 overlaps existing 0xd8000000,0x4000000
agpgart: Found an AGP 2.0 compliant device at 0000:00:00.0.
agpgart: Putting AGP V2 device at 0000:00:00.0 into 1x mode
agpgart: Putting AGP V2 device at 0000:01:00.0 into 1x mode
[drm] Setting GART location based on new memory map
[drm] writeback test succeeded in 1 usecs
spurious 8259A interrupt: IRQ7.
usb 1-6: new high speed USB device using ehci_hcd and address 3
usb 1-6: configuration #1 chosen from 1 choice
scsi0 : SCSI emulation for USB Mass Storage devices
usb-storage: device found at 3
usb-storage: waiting for device to settle before scanning
  Vendor: Toshiba   Model: USB 2.0 Ext. HDD  Rev: 1.21
  Type:   Direct-Access                      ANSI SCSI revision: 00
SCSI device sda: 488397168 512-byte hdwr sectors (250059 MB)
sda: Write Protect is off
sda: Mode Sense: 0b 00 00 08
sda: assuming drive cache: write through
SCSI device sda: 488397168 512-byte hdwr sectors (250059 MB)
sda: Write Protect is off
sda: Mode Sense: 0b 00 00 08
sda: assuming drive cache: write through
 sda: sda1
sd 0:0:0:0: Attached scsi disk sda
sd 0:0:0:0: Attached scsi generic sg0 type 0
usb-storage: device scan complete
kjournald starting.  Commit interval 5 seconds
EXT3-fs warning: maximal mount count reached, running e2fsck is recommended
EXT3 FS on sda1, internal journal
EXT3-fs: recovery complete.
EXT3-fs: mounted filesystem with ordered data mode.


Superkaramba era aperto, però come ho detto il problema è durato per minuti, non so se fosse proprio lo stesso problema.
Back to top
View user's profile Send private message
GuN_jAcK
l33t
l33t


Joined: 23 Mar 2005
Posts: 823
Location: Prague, Czech Republic

PostPosted: Tue Aug 21, 2007 11:26 am    Post subject: Reply with quote

no il problema da me persiste... ora provo a chiudere superkaramba e stiamo a vedere.... :\
_________________
Rispondi in maniera intelligente anche a chi ti tratta stupidamente.
Back to top
View user's profile Send private message
GuN_jAcK
l33t
l33t


Joined: 23 Mar 2005
Posts: 823
Location: Prague, Czech Republic

PostPosted: Tue Aug 21, 2007 7:03 pm    Post subject: Reply with quote

credo che abbia risolto chiudendo superkaramba.... può essere qualche plugin che gli dava fastidio... mmmm...

Luc484 che plugin usavi con superakaramba..?
_________________
Rispondi in maniera intelligente anche a chi ti tratta stupidamente.
Back to top
View user's profile Send private message
Luc484
Veteran
Veteran


Joined: 26 Mar 2005
Posts: 1035
Location: Italy

PostPosted: Tue Aug 21, 2007 7:16 pm    Post subject: Reply with quote

Li uso da un sacco di tempo, sono liquid weather e T Desktop Enhancements.
Back to top
View user's profile Send private message
GuN_jAcK
l33t
l33t


Joined: 23 Mar 2005
Posts: 823
Location: Prague, Czech Republic

PostPosted: Tue Aug 21, 2007 7:47 pm    Post subject: Reply with quote

io li uso da anni anche io ^_^ e l'unica cosa in comune che abbiamo e liquid weather... può essere per colpa sua? prova a disabilitarlo e vedi se continua a darti il problema :)
_________________
Rispondi in maniera intelligente anche a chi ti tratta stupidamente.
Back to top
View user's profile Send private message
Luc484
Veteran
Veteran


Joined: 26 Mar 2005
Posts: 1035
Location: Italy

PostPosted: Tue Aug 21, 2007 9:47 pm    Post subject: Reply with quote

Si, a questo punto può essere che l'abbiamo trovato. Comunque prima pensavo di fare come dicevo prima. Provo a vedere appena si blocca e provo a killare superkaramba. Se effettivamente si sistema X, allora so per certo che è quello. Vediamo perché sono ancora in attesa che si blocchi per bene come al solito, così poi faccio la prova.
Back to top
View user's profile Send private message
GuN_jAcK
l33t
l33t


Joined: 23 Mar 2005
Posts: 823
Location: Prague, Czech Republic

PostPosted: Wed Aug 22, 2007 10:08 am    Post subject: Reply with quote

no ho provato.. se lo killi karamba una volta che si freeza X non lo sblocchi più.. anzi a me ha chiodato poi TUTTO il sistema.. -.- direi alquanto imbarazzante...
_________________
Rispondi in maniera intelligente anche a chi ti tratta stupidamente.
Back to top
View user's profile Send private message
Luc484
Veteran
Veteran


Joined: 26 Mar 2005
Posts: 1035
Location: Italy

PostPosted: Wed Aug 22, 2007 10:41 am    Post subject: Reply with quote

Ma di solito ti si bloccava tutto o solo X? Cioè, io ho sempre killato solamente X senza problemi per il resto del sistema. Allora probabilmente il problema non è lo stesso di cui parlava to.alex, perché lui diceva che riusciva a killare solamente superkaramba ed X tornava subito a posto.
Allora a questo punto faccio così: controllo che il problema si ripresenti, perché ho fatto qualche piccola modifica e voglio confermare che non abbiano influenze, poi killo X e riprovo senza superkaramba, così vedo. Il problema è che noto che a te si presenta più di frequente. Io sono ancora qui in attesa che X impazzisca.
Back to top
View user's profile Send private message
GuN_jAcK
l33t
l33t


Joined: 23 Mar 2005
Posts: 823
Location: Prague, Czech Republic

PostPosted: Wed Aug 22, 2007 3:59 pm    Post subject: Reply with quote

se killavo X il sistema era a posto... ma se killavo prima superkaramba mi chiodava proprio tutto il sistema.. io da quando ho tolto superkaramba non ho riscontrato problemi.. ora non so se era colpa di qualche plugin o di karamba stesso...
_________________
Rispondi in maniera intelligente anche a chi ti tratta stupidamente.
Back to top
View user's profile Send private message
Luc484
Veteran
Veteran


Joined: 26 Mar 2005
Posts: 1035
Location: Italy

PostPosted: Fri Aug 24, 2007 7:30 am    Post subject: Reply with quote

Bene, è appena successo. X è impazzito del tutto. Questo il dmesg che ho adesso mentre X sta occupando la CPU:

Code:
 drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
Probing IDE interface ide1...
hdc: ASUS CD-S500/A, ATAPI CD/DVD-ROM drive
hdd: HL-DT-ST GCE-8320B, ATAPI CD/DVD-ROM drive
ide1 at 0x170-0x177,0x376 on irq 15
hda: max request size: 128KiB
hda: 160086528 sectors (81964 MB) w/2048KiB Cache, CHS=65535/16/63, UDMA(133)
hda: cache flushes supported
 hda: hda1 hda2 hda3 hda4
hdb: max request size: 512KiB
hdb: 312581808 sectors (160041 MB) w/8192KiB Cache, CHS=19457/255/63, UDMA(100)
hdb: cache flushes supported
 hdb: hdb1 hdb2
hdc: ATAPI 50X CD-ROM drive, 128kB Cache, UDMA(33)
Uniform CD-ROM driver Revision: 3.20
hdd: ATAPI 40X CD-ROM CD-R/RW drive, 8192kB Cache, DMA
ide-floppy driver 0.99.newide
st: Version 20050830, fixed bufsize 32768, s/g segs 256
ehci_hcd 0000:00:10.3: EHCI Host Controller
ehci_hcd 0000:00:10.3: new USB bus registered, assigned bus number 1
ehci_hcd 0000:00:10.3: irq 10, io mem 0xe2001000
ehci_hcd 0000:00:10.3: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 6 ports detected
ohci_hcd: 2005 April 22 USB 1.1 'Open' Host Controller (OHCI) Driver (PCI)
USB Universal Host Controller Interface driver v3.0
uhci_hcd 0000:00:10.0: UHCI Host Controller
uhci_hcd 0000:00:10.0: new USB bus registered, assigned bus number 2
uhci_hcd 0000:00:10.0: irq 12, io base 0x0000d800
usb usb2: configuration #1 chosen from 1 choice
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 2 ports detected
uhci_hcd 0000:00:10.1: UHCI Host Controller
uhci_hcd 0000:00:10.1: new USB bus registered, assigned bus number 3
uhci_hcd 0000:00:10.1: irq 11, io base 0x0000dc00
usb usb3: configuration #1 chosen from 1 choice
hub 3-0:1.0: USB hub found
hub 3-0:1.0: 2 ports detected
uhci_hcd 0000:00:10.2: UHCI Host Controller
uhci_hcd 0000:00:10.2: new USB bus registered, assigned bus number 4
uhci_hcd 0000:00:10.2: irq 11, io base 0x0000e000
usb usb4: configuration #1 chosen from 1 choice
hub 4-0:1.0: USB hub found
hub 4-0:1.0: 2 ports detected
usb 2-1: new low speed USB device using uhci_hcd and address 2
usb 2-1: configuration #1 chosen from 1 choice
usbcore: registered new driver usblp
drivers/usb/class/usblp.c: v0.13: USB Printer Device Class driver
Initializing USB Mass Storage driver...
usbcore: registered new driver usb-storage
USB Mass Storage support registered.
input: Logitech USB-PS/2 Optical Mouse as /class/input/input1
input: USB HID v1.10 Mouse [Logitech USB-PS/2 Optical Mouse] on usb-0000:00:10.0-1
usbcore: registered new driver usbhid
drivers/usb/input/hid-core.c: v2.6:USB HID core driver
Bluetooth: HCI UART driver ver 2.2
Bluetooth: HCI H4 protocol initialized
Bluetooth: HCI BCSP protocol initialized
Advanced Linux Sound Architecture Driver Version 1.0.12rc1 (Thu Jun 22 13:55:50 2006 UTC).
ALSA device list:
  No soundcards found.
TCP bic registered
NET: Registered protocol family 1
NET: Registered protocol family 17
Using IPI Shortcut mode
Time: tsc clocksource has been installed.
kjournald starting.  Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
VFS: Mounted root (ext3 filesystem) readonly.
Freeing unused kernel memory: 144k freed
8139too Fast Ethernet driver 0.9.27
eth0: RealTek RTL8139 at 0xf0820000, 00:20:ed:65:88:68, IRQ 11
eth0:  Identified 8139 chip type 'RTL-8100B/8139D'
PCI: Setting latency timer of device 0000:00:11.5 to 64
udev: renamed network interface eth0 to eth1
ne2k-pci.c:v1.03 9/22/2003 D. Becker/P. Gortmaker
  http://www.scyld.com/network/ne2k-pci.html
eth0: RealTek RTL-8029 found at 0xd400, IRQ 10, 00:40:33:53:DC:88.
EXT3 FS on hda1, internal journal
kjournald starting.  Commit interval 5 seconds
EXT3 FS on hda4, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS on hdb1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS on hdb2, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
Adding 500464k swap on /dev/hda3.  Priority:-1 extents:1 across:500464k
Bluetooth: L2CAP ver 2.8
Bluetooth: L2CAP socket layer initialized
Bluetooth: RFCOMM socket layer initialized
Bluetooth: RFCOMM TTY layer initialized
Bluetooth: RFCOMM ver 1.8
it87: Found IT8705F chip at 0x290, revision 2
it87-isa 9191-0290: Detected broken BIOS defaults, disabling PWM interface
eth1: link up, 100Mbps, full-duplex, lpa 0x45E1
CSLIP: code copyright 1989 Regents of the University of California
PPP generic driver version 2.4.2
NET: Registered protocol family 24
ip_tables: (C) 2000-2006 Netfilter Core Team
ip_conntrack version 2.4 (6143 buckets, 49144 max) - 208 bytes per conntrack
[drm] Initialized drm 1.0.1 20051102
PCI: Unable to reserve mem region #1:8000000@d8000000 for device 0000:01:00.0
[drm] Initialized radeon 1.25.0 20060524 on minor 0:
[drm] Used old pci detect: framebuffer loaded
mtrr: 0xd8000000,0x8000000 overlaps existing 0xd8000000,0x4000000
mtrr: 0xd8000000,0x8000000 overlaps existing 0xd8000000,0x4000000
mtrr: 0xd8000000,0x8000000 overlaps existing 0xd8000000,0x4000000
agpgart: Found an AGP 2.0 compliant device at 0000:00:00.0.
agpgart: Putting AGP V2 device at 0000:00:00.0 into 1x mode
agpgart: Putting AGP V2 device at 0000:01:00.0 into 1x mode
[drm] Setting GART location based on new memory map
[drm] writeback test succeeded in 1 usecs
spurious 8259A interrupt: IRQ7.
usb 1-6: new high speed USB device using ehci_hcd and address 3
usb 1-6: configuration #1 chosen from 1 choice
scsi0 : SCSI emulation for USB Mass Storage devices
usb-storage: device found at 3
usb-storage: waiting for device to settle before scanning
  Vendor: Toshiba   Model: USB 2.0 Ext. HDD  Rev: 1.21
  Type:   Direct-Access                      ANSI SCSI revision: 00
SCSI device sda: 488397168 512-byte hdwr sectors (250059 MB)
sda: Write Protect is off
sda: Mode Sense: 0b 00 00 08
sda: assuming drive cache: write through
SCSI device sda: 488397168 512-byte hdwr sectors (250059 MB)
sda: Write Protect is off
sda: Mode Sense: 0b 00 00 08
sda: assuming drive cache: write through
 sda: sda1
sd 0:0:0:0: Attached scsi disk sda
sd 0:0:0:0: Attached scsi generic sg0 type 0
usb-storage: device scan complete
kjournald starting.  Commit interval 5 seconds
EXT3-fs warning: maximal mount count reached, running e2fsck is recommended
EXT3 FS on sda1, internal journal
EXT3-fs: recovery complete.
EXT3-fs: mounted filesystem with ordered data mode.
usb 1-6: USB disconnect, address 3
scsi 0:0:0:0: rejecting I/O to dead device
EXT3-fs error (device sda1): ext3_find_entry: reading directory #2064390 offset 0
Aborting journal on device sda1.
scsi 0:0:0:0: rejecting I/O to dead device
Buffer I/O error on device sda1, logical block 1560
lost page write due to I/O error on sda1
scsi 0:0:0:0: rejecting I/O to dead device
Buffer I/O error on device sda1, logical block 0
lost page write due to I/O error on sda1
scsi 0:0:0:0: rejecting I/O to dead device
EXT3-fs error (device sda1): ext3_find_entry: reading directory #2064390 offset 0
scsi 0:0:0:0: rejecting I/O to dead device
Buffer I/O error on device sda1, logical block 0
lost page write due to I/O error on sda1
scsi 0:0:0:0: rejecting I/O to dead device
EXT3-fs error (device sda1): ext3_find_entry: reading directory #2064390 offset 0
scsi 0:0:0:0: rejecting I/O to dead device
Buffer I/O error on device sda1, logical block 0
lost page write due to I/O error on sda1
scsi 0:0:0:0: rejecting I/O to dead device
EXT3-fs error (device sda1): ext3_find_entry: reading directory #2064390 offset 0
scsi 0:0:0:0: rejecting I/O to dead device
Buffer I/O error on device sda1, logical block 0
lost page write due to I/O error on sda1
scsi 0:0:0:0: rejecting I/O to dead device
EXT3-fs error (device sda1): ext3_find_entry: reading directory #2064390 offset 0
scsi 0:0:0:0: rejecting I/O to dead device
Buffer I/O error on device sda1, logical block 0
lost page write due to I/O error on sda1
scsi 0:0:0:0: rejecting I/O to dead device
EXT3-fs error (device sda1): ext3_find_entry: reading directory #2064390 offset 0
scsi 0:0:0:0: rejecting I/O to dead device
Buffer I/O error on device sda1, logical block 0
lost page write due to I/O error on sda1
scsi 0:0:0:0: rejecting I/O to dead device
ext3_abort called.
EXT3-fs error (device sda1): ext3_journal_start_sb: Detected aborted journal
Remounting filesystem read-only
scsi 0:0:0:0: rejecting I/O to dead device
scsi 0:0:0:0: rejecting I/O to dead device
EXT3-fs error (device sda1): ext3_find_entry: reading directory #2064386 offset 0
scsi 0:0:0:0: rejecting I/O to dead device
EXT3-fs error (device sda1): ext3_find_entry: reading directory #2064386 offset 0
scsi 0:0:0:0: rejecting I/O to dead device
EXT3-fs error (device sda1): ext3_find_entry: reading directory #2064386 offset 0
scsi 0:0:0:0: rejecting I/O to dead device
scsi 0:0:0:0: rejecting I/O to dead device
EXT3-fs error (device sda1): ext3_find_entry: reading directory #2 offset 0
scsi 0:0:0:0: rejecting I/O to dead device
EXT3-fs error (device sda1): ext3_find_entry: reading directory #2 offset 0
scsi 0:0:0:0: rejecting I/O to dead device
EXT3-fs error (device sda1): ext3_find_entry: reading directory #2 offset 0
scsi 0:0:0:0: rejecting I/O to dead device
EXT3-fs error (device sda1): ext3_find_entry: reading directory #2 offset 0
scsi 0:0:0:0: rejecting I/O to dead device
EXT3-fs error (device sda1): ext3_find_entry: reading directory #2 offset 0
scsi 0:0:0:0: rejecting I/O to dead device
EXT3-fs error (device sda1): ext3_find_entry: reading directory #2 offset 0
scsi 0:0:0:0: rejecting I/O to dead device
EXT3-fs error (device sda1): ext3_find_entry: reading directory #2 offset 0
scsi 0:0:0:0: rejecting I/O to dead device
EXT3-fs error (device sda1): ext3_find_entry: reading directory #2 offset 0
scsi 0:0:0:0: rejecting I/O to dead device
EXT3-fs error (device sda1): ext3_find_entry: reading directory #2 offset 0
scsi 0:0:0:0: rejecting I/O to dead device
scsi 0:0:0:0: rejecting I/O to dead device
EXT3-fs error (device sda1): ext3_find_entry: reading directory #2 offset 0
scsi 0:0:0:0: rejecting I/O to dead device
EXT3-fs error (device sda1): ext3_find_entry: reading directory #2 offset 0
scsi 0:0:0:0: rejecting I/O to dead device
EXT3-fs error (device sda1): ext3_find_entry: reading directory #2 offset 0
scsi 0:0:0:0: rejecting I/O to dead device
EXT3-fs error (device sda1): ext3_find_entry: reading directory #2 offset 0
scsi 0:0:0:0: rejecting I/O to dead device
MCE: The hardware reports a non fatal, correctable incident occurred on CPU 0.
Bank 2: 940040000000017a
scsi 0:0:0:0: rejecting I/O to dead device
EXT3-fs error (device sda1): ext3_find_entry: reading directory #2 offset 0
usb 1-6: new high speed USB device using ehci_hcd and address 4
usb 1-6: configuration #1 chosen from 1 choice
scsi1 : SCSI emulation for USB Mass Storage devices
usb-storage: device found at 4
usb-storage: waiting for device to settle before scanning
scsi 0:0:0:0: rejecting I/O to dead device
  Vendor: Toshiba   Model: USB 2.0 Ext. HDD  Rev: 1.21
  Type:   Direct-Access                      ANSI SCSI revision: 00
SCSI device sdb: 488397168 512-byte hdwr sectors (250059 MB)
sdb: Write Protect is off
sdb: Mode Sense: 0b 00 00 08
sdb: assuming drive cache: write through
SCSI device sdb: 488397168 512-byte hdwr sectors (250059 MB)
sdb: Write Protect is off
sdb: Mode Sense: 0b 00 00 08
sdb: assuming drive cache: write through
 sdb: sdb1
sd 1:0:0:0: Attached scsi disk sdb
sd 1:0:0:0: Attached scsi generic sg0 type 0
usb-storage: device scan complete
scsi 0:0:0:0: rejecting I/O to dead device
scsi 0:0:0:0: rejecting I/O to dead device
scsi 0:0:0:0: rejecting I/O to dead device
Buffer I/O error on device sda1, logical block 1560
lost page write due to I/O error on sda1
usb 1-6: USB disconnect, address 4
usb 1-6: new high speed USB device using ehci_hcd and address 5
usb 1-6: configuration #1 chosen from 1 choice
scsi2 : SCSI emulation for USB Mass Storage devices
usb-storage: device found at 5
usb-storage: waiting for device to settle before scanning
  Vendor: Toshiba   Model: USB 2.0 Ext. HDD  Rev: 1.21
  Type:   Direct-Access                      ANSI SCSI revision: 00
SCSI device sda: 488397168 512-byte hdwr sectors (250059 MB)
sda: Write Protect is off
sda: Mode Sense: 0b 00 00 08
sda: assuming drive cache: write through
SCSI device sda: 488397168 512-byte hdwr sectors (250059 MB)
sda: Write Protect is off
sda: Mode Sense: 0b 00 00 08
sda: assuming drive cache: write through
 sda: sda1
sd 2:0:0:0: Attached scsi disk sda
sd 2:0:0:0: Attached scsi generic sg0 type 0
usb-storage: device scan complete
kjournald starting.  Commit interval 5 seconds
EXT3-fs warning: maximal mount count reached, running e2fsck is recommended
EXT3 FS on sda1, internal journal
EXT3-fs: recovery complete.
EXT3-fs: mounted filesystem with ordered data mode.
usb 1-6: USB disconnect, address 5
usb 1-6: new high speed USB device using ehci_hcd and address 6
usb 1-6: configuration #1 chosen from 1 choice
scsi3 : SCSI emulation for USB Mass Storage devices
usb-storage: device found at 6
usb-storage: waiting for device to settle before scanning
  Vendor: Toshiba   Model: USB 2.0 Ext. HDD  Rev: 1.21
  Type:   Direct-Access                      ANSI SCSI revision: 00
SCSI device sda: 488397168 512-byte hdwr sectors (250059 MB)
sda: Write Protect is off
sda: Mode Sense: 0b 00 00 08
sda: assuming drive cache: write through
SCSI device sda: 488397168 512-byte hdwr sectors (250059 MB)
sda: Write Protect is off
sda: Mode Sense: 0b 00 00 08
sda: assuming drive cache: write through
 sda: sda1
sd 3:0:0:0: Attached scsi disk sda
sd 3:0:0:0: Attached scsi generic sg0 type 0
usb-storage: device scan complete
kjournald starting.  Commit interval 5 seconds
EXT3-fs warning: maximal mount count reached, running e2fsck is recommended
EXT3 FS on sda1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
usb 1-6: USB disconnect, address 6
usb 1-6: new high speed USB device using ehci_hcd and address 7
usb 1-6: configuration #1 chosen from 1 choice
scsi4 : SCSI emulation for USB Mass Storage devices
usb-storage: device found at 7
usb-storage: waiting for device to settle before scanning
  Vendor: Toshiba   Model: USB 2.0 Ext. HDD  Rev: 1.21
  Type:   Direct-Access                      ANSI SCSI revision: 00
SCSI device sda: 488397168 512-byte hdwr sectors (250059 MB)
sda: Write Protect is off
sda: Mode Sense: 0b 00 00 08
sda: assuming drive cache: write through
SCSI device sda: 488397168 512-byte hdwr sectors (250059 MB)
sda: Write Protect is off
sda: Mode Sense: 0b 00 00 08
sda: assuming drive cache: write through
 sda: sda1
sd 4:0:0:0: Attached scsi disk sda
sd 4:0:0:0: Attached scsi generic sg0 type 0
usb-storage: device scan complete
kjournald starting.  Commit interval 5 seconds
EXT3-fs warning: maximal mount count reached, running e2fsck is recommended
EXT3 FS on sda1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
agpgart: Found an AGP 2.0 compliant device at 0000:00:00.0.
agpgart: Putting AGP V2 device at 0000:00:00.0 into 1x mode
agpgart: Putting AGP V2 device at 0000:01:00.0 into 1x mode
kjournald starting.  Commit interval 5 seconds
EXT3-fs warning: maximal mount count reached, running e2fsck is recommended
EXT3 FS on sda1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
usb 1-6: USB disconnect, address 7


Magari qualcuno ci vede qualche indizio. Ora provo a chiudere superkarmba e vediamo se succede ancora.
Back to top
View user's profile Send private message
randomaze
Bodhisattva
Bodhisattva


Joined: 21 Oct 2003
Posts: 9985

PostPosted: Fri Aug 24, 2007 7:48 am    Post subject: Reply with quote

Luc484 wrote:
Bene, è appena successo. X è impazzito del tutto. Questo il dmesg che ho adesso mentre X sta occupando la CPU:

Code:
kjournald starting.  Commit interval 5 seconds
EXT3-fs warning: maximal mount count reached, running e2fsck is recommended
EXT3 FS on sda1, internal journal
EXT3-fs: recovery complete.
EXT3-fs: mounted filesystem with ordered data mode.
usb 1-6: USB disconnect, address 3
scsi 0:0:0:0: rejecting I/O to dead device
EXT3-fs error (device sda1): ext3_find_entry: reading directory #2064390 offset 0
Aborting journal on device sda1.
scsi 0:0:0:0: rejecting I/O to dead device
Buffer I/O error on device sda1, logical block 1560



Sei sicuro che sia colpa di X? O meglio, sei sicuro che la causa sia X/KDE/altro e non quell'sda1 (disco esterno? chiavetta USB?) che é visibilmente marcio? Fai uso di quei gadget che mostrano l'icona del disco, lo spazio occupato e roba simile?
_________________
Ciao da me!
Back to top
View user's profile Send private message
Luc484
Veteran
Veteran


Joined: 26 Mar 2005
Posts: 1035
Location: Italy

PostPosted: Fri Aug 24, 2007 11:06 am    Post subject: Reply with quote

Beh, in realtà quello non è quasi mai acceso, rimane acceso solo per brevi periodi. Comunque... come marcio?? Funziona perfettamente, non so cosa siano quegli errori. Comunque è un hd da 250GB USB.
In realtà si, avevo uno di quei plugin che mostrano lo spazio libero. Ma non mostrava quell'unità lì.
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Forum italiano (Italian) All times are GMT
Goto page Previous  1, 2, 3  Next
Page 2 of 3

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum