[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Crash kernel 2.6



Eccomi di nuovo :))

per  provarle  tutte (vedi post precedente) avevo anche installato (fatto
installare) il kernel 2.6.12.4 su sarge.
Il  sistema  cosi'  impostato  funziona  per alcuni giorni/ore per poi
impallarsi  improvvisamente  e  completamente  apparentemente  per  un
carico di lavoro eccessivo.

Chi  ha  installato il kernel non si spiega il perche' di questi crash
sulla  mia  macchina  affermando  che  su altre installazioni analoghe
funziona perfettamente... gli unici errori che riscontriamo nei log ve
li incollo qui di seguito, a qualcuno dicono qualcosa ?

Grazie

Aug 26 03:17:54 ns3 kernel: Losing too many ticks!
Aug 26 03:17:54 ns3 kernel: TSC cannot be used as a timesource.
Aug 26 03:17:54 ns3 kernel: Possible reasons for this are:
Aug 26 03:17:54 ns3 kernel:   You're running with Speedstep,
Aug 26 03:17:54 ns3 kernel:   You don't have DMA enabled for your hard disk (see hdparm),
Aug 26 03:17:54 ns3 kernel:   Incorrect TSC synchronization on an SMP system (see dmesg).
Aug 26 03:17:54 ns3 kernel: Falling back to a sane timesource now.
Aug 26 08:50:36 ns3 syslogd 1.4.1#17: restart.

--

Aug 25 18:47:12 ns3 kernel: scsi0 : Adaptec AIC7XXX EISA/VLB/PCI SCSI HBA DRIVER, Rev 6.2.36
Aug 25 18:47:12 ns3 kernel:         <Adaptec 29160B Ultra160 SCSI adapter>
Aug 25 18:47:12 ns3 kernel:         aic7892: Ultra160 Wide Channel A,SCSI Id=7, 32/253 SCBs
Aug 25 18:47:12 ns3 kernel:
Aug 25 18:47:12 ns3 kernel: Red Hat/Adaptec aacraid driver (1.1.2-lk2 Aug 12 2005)
Aug 25 18:47:12 ns3 kernel: ips 0000:01:02.0: Warning ! ! ! ServeRAID Version Mismatch
Aug 25 18:47:12 ns3 kernel: ips 0000:01:02.0: Bios = 6.10.24, Firmware = 6.10.24, Device Driver = 7.10.18
Aug 25 18:47:12 ns3 kernel: ips 0000:01:02.0: These levels should match to avoid possible compatibility problems.
Aug 26 08:50:36 ns3 kernel: scsi0 : IBM PCI ServeRAID 7.10.18  Build 731 <ServeRAID 4Lx>
Aug 26 08:50:36 ns3 kernel: blk: queue f7e17e18, I/O limit 4095Mb (mask 0xffffffff)
Aug 26 08:50:36 ns3 kernel:   Vendor: IBM       Model: SERVERAID Rev: 1.00
Aug 26 08:50:36 ns3 kernel:   Type:   Direct-Access ANSI SCSI revision: 02
Aug 26 08:50:36 ns3 kernel: blk: queue f7e17c18, I/O limit 4095Mb (mask 0xffffffff)
Aug 26 08:50:36 ns3 kernel:   Vendor: IBM       Model: SERVERAID Rev: 1.00
Aug 26 08:50:36 ns3 kernel:   Type:   Processor ANSI SCSI revision: 02
Aug 26 08:50:36 ns3 kernel: blk: queue f7e17a18, I/O limit 4095Mb (mask 0xffffffff)
Aug 26 08:50:36 ns3 kernel: Attached scsi disk sda at scsi0, channel 0, id 0, lun 0
Aug 26 08:50:36 ns3 kernel: SCSI device sda: 71096320 512-byte hdwr sectors (36401 MB)

la  CPU se ricordo bene (un P4) usa la funzionalita' hipertreding e il
kernel  in  fase  di  boot vede 2 CPU...nn so se anche questo potrebbe
essere fonte del problema.

-- 
Fabio

 
 
 --
 Email.it, the professional e-mail, gratis per te: http://www.email.it/f
 
 Sponsor:
 Vuoi risparmiare sino al 70% sugli acquisti? Oliviero non teme confronti!
 Clicca qui: http://adv.email.it/cgi-bin/foclick.cgi?mid=3849&d=5-9



Reply to: