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

Re: doppio processore... come controllo?

Il giorno Mon, 10 Jun 2002 14:14:12 +0200
Giuseppe Sacco <eppesuigoccas@iol.it> ha scritto:
> GS 
> GS Prova a darci le prime 20-30 righe di dmesg.

ora sto ricompilando il kernel dopo aver escluso lo sharing degli irq tra i processori e disabilitato il workaround del bug dei primi processor 601.... che non sia quello!! :(

qui sotto parte del dmesg


Memory BAT mapping: BAT2=64Mb, BAT3=32Mb, residual: 16Mb
Warning, memory limited to 96 Mb, use CONFIG_HIGHMEM to reach 96 Mb
Total memory = 96MB; using 512kB for hash table (at c0380000)
Linux version 2.4.18 (root@debian-ppc) (gcc version 3.1.1 20020606 (Debian prerelease)) #2 SMP Sun Jun 9 23:30:44 CEST 2002
Found a Grand Central mac-io controller, rev: 2, mapped at 0xfdcff000
PowerMac motherboard: PowerMac 8500/8600
Cache coherency enabled for bandit/PSX at 00000000
Found Bandit PCI host bridge at 0xf2000000. Firmware bus number: 0->0
Found Chaos PCI host bridge at 0xf0000000. Firmware bus number: 1->1
On node 0 totalpages: 24576
zone(0): 24576 pages.
zone(1): 0 pages.
zone(2): 0 pages.
Kernel command line: root=/dev/sda8 keyboard_sends_linux_keycodes=1 video=ofonlySystem has 32 possible interrupts
GMT Delta read from XPRAM: 60 minutes, DST: off
via_calibrate_decr: ticks per jiffy = 125002 (750016 ticks)
Console: colour dummy device 80x25
Calibrating delay loop... 398.95 BogoMIPS
Memory: 92764k available (1988k kernel code, 1072k data, 292k init, 0k highmem)
Dentry-cache hash table entries: 16384 (order: 5, 131072 bytes)
Inode-cache hash table entries: 8192 (order: 4, 65536 bytes)
Mount-cache hash table entries: 2048 (order: 2, 16384 bytes)
Buffer-cache hash table entries: 4096 (order: 2, 16384 bytes)
Page-cache hash table entries: 32768 (order: 5, 131072 bytes)
POSIX conformance testing by UNIFIX
Entering SMP Mode...
Processor 1 is stuck.
Waiting on wait_init_idle (map = 0x0)
All processors have done init_idle
PCI: Probing PCI hardware
PCI:00:10.0: Resource 0: f3000000-f301ffff (f=200)
PCI:00:0e.0: Resource 0: 00000400-000004ff (f=101)
PCI:00:0e.0: Resource 1: 80800000-808000ff (f=200)
PCI:00:0f.0: Resource 0: 80801000-80801fff (f=200)
PCI:01:0b.0: Resource 1: 90000000-9000ffff (f=200)
PCI:01:0b.0: Resource 2: 94000000-97ffffff (f=200)
PCI:01:0d.0: Resource 0: 90000000-900003ff (f=200)
PCI: Cannot allocate resource region 0 of device 01:0d.0
PCI:  parent is c0363068: 90000000-9fffffff (f=200)
Macintosh CUDA driver v0.5 for Unified ADB.
Linux NET4.0 for Linux 2.4
Based upon Swansea University Computer Society NET3.039
Initializing RT netlink socket
Thermal assist unit not available
Starting kswapd
Journalled Block Device driver loaded
devfs: v1.10 (20020120) Richard Gooch (rgooch@atnf.csiro.au)
devfs: boot_options: 0x0
i2c-core.o: i2c core module
MacOS display is /chaos/control
Using unsupported 832x624 control at 94c00210, depth=32, pitch=3360
Console: switching to colour frame buffer device 104x39
fb0: Open Firmware frame buffer device on /chaos/control
input0: Macintosh mouse button emulation
pty: 256 Unix98 ptys configured
block: 128 slots per queue, batch=32
RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
Uniform Multi-Platform E-IDE driver Revision: 6.31
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
ide-floppy driver 0.97.sv
fd0: SWIM3 floppy controller 
loop: loaded (max 8 devices)
eth0: MACE at 00:05:02:ac:d5:71, chip revision 25.64
PPP generic driver version 2.4.1
PPP Deflate Compression module registered
ide-floppy driver 0.97.sv
SCSI subsystem driver Revision: 1.00
scsi0 : SCSI host adapter emulation for IDE ATAPI devices
scsi1 : MESH
mesh: target 2 synchronous at 5.0 MB/s
  Vendor: QUANTUM   Model: FIREBALL ST4.3S   Rev: 0F0C
  Type:   Direct-Access                      ANSI SCSI revision: 02

Massimo Biffi  LocTeam Barcelona - Spain
Debian/Sid on PowerBook Apple G3 
Home: www.maximumdebian.org

To UNSUBSCRIBE, email to debian-italian-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

Reply to: