Re: Blade 100 and 2.6.{22,23}
Luigi Gangitano wrote:
Hi sparcers,
since last official debian kernel running on my SunBlade100 is
2.6.21-2, today I investigated what is going wrong in 2.6.22 and
2.6.23. Both kernels hang at boot with and without the video=atyfb:off
parameter.
A -p output of 2.6.23 follows, it seems that while scanning the PCI
bus devices get added multiple times. For the record 0000:00:03.0 is
the PMU and 07.0 is the ISA bridge.
Any ideas?
Hi,
I am running on SunBlade100 with 2.6.23-rc4 that I built from the
upstream sources (not debian) as I found that does not need any boot
parameters. Some earlier versions I think had errors if a firewire
device is plugged in.
jim@sun:~$ uname -a
Linux sun 2.6.23-rc4 #1 Sun Sep 2 09:33:06 EST 2007 sparc64 GNU/Linux
jim
PROMLIB: Sun IEEE Boot Prom 'OBP 4.0.45 2001/02/08 14:33'
PROMLIB: Root node compatible:
Linux version 2.6.23-rc4 (jim@sun) (gcc version 4.1.3 20070812
(prerelease) (De
ARCH: SUN4U
Ethernet address: 00:03:ba:04:a4:ab
OF stdout device is: /pci@1f,0/SUNW,m64B@13
PROM: Built device tree with 54219 bytes of memory.
On node 0 totalpages: 32050
Normal zone: 223 pages used for memmap
Normal zone: 0 pages reserved
Normal zone: 31827 pages, LIFO batch:7
Movable zone: 0 pages used for memmap
Built 1 zonelists in Zone order. Total pages: 31827
Kernel command line: root=/dev/hda2 ro
PID hash table entries: 1024 (order: 10, 8192 bytes)
clocksource: mult[b40001] shift[16]
clockevent: mult[16c16bf] shift[32]
Console: colour dummy device 80x25
console [tty0] enabled
Dentry cache hash table entries: 32768 (order: 5, 262144 bytes)
Inode-cache hash table entries: 16384 (order: 4, 131072 bytes)
Memory: 235776k available (2432k kernel code, 864k data, 144k init)
[fffff80000
Calibrating delay using timer specific routine.. 11.12 BogoMIPS (lpj=22256)
Security Framework v1.0.0 initialized
SELinux: Disabled at boot.
Capability LSM initialized
Mount-cache hash table entries: 512
NET: Registered protocol family 16
PCI: Probing for controllers.
/pci@1f,0: SABRE PCI Bus Module
/pci@1f,0: PCI IO[1fe02000000] MEM[1ff00000000]
PCI: Scanning PBM /pci@1f,0
PCI quirk: region 0800-083f claimed by ali7101 ACPI
PCI quirk: region 0600-061f claimed by ali7101 SMB
isa0: [dma -> (floppy) (parallel)] [power] [serial] [serial]
ebus0: [flashprom] [eeprom] [idprom]
power: Control reg at 1fe02000800
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
/pci@1f,0/ebus@c/eeprom@1,0: Clock regs at 000001fff1000000
NET: Registered protocol family 2
Time: hbtick clocksource has been installed.
IP route cache hash table entries: 2048 (order: 1, 16384 bytes)
TCP established hash table entries: 8192 (order: 4, 131072 bytes)
TCP bind hash table entries: 8192 (order: 3, 65536 bytes)
TCP: Hash tables configured (established 8192 bind 8192)
TCP reno registered
checking if image is initramfs... it is
Freeing initrd memory: 5319k freed
Mini RTC Driver
audit: initializing netlink socket (disabled)
audit(1197843231.440:1): initialized
VFS: Disk quotas dquot_6.5.1
Dquot-cache hash table entries: 1024 (order 0, 8192 bytes)
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered (default)
Activating ISA DMA hang workarounds.
PCI: Enabling device: (0000:00:13.0), cmd 83
atyfb: 3D RAGE XL (Mach64 GR, PCI-33) [0x4752 rev 0x27]
atyfb: 8M SDRAM (1:1), 29.498928 MHz XTAL, 230 MHz PLL, 83 Mhz MCLK, 63
MHz XCL
Console: switching to colour frame buffer device 160x64
atyfb: fb0: ATY Mach64 frame buffer device on PCI
[drm] Initialized drm 1.1.0 20060810
f007263c: ttyS0 at MMIO 0x1fe020003f8 (irq = 9) is a 16550A
f0073d68: ttyS1 at MMIO 0x1fe020002e8 (irq = 9) is a 16550A
RAMDISK driver initialized: 16 RAM disks of 16384K size 1024 blocksize
loop: module loaded
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
mice: PS/2 mouse device common for all mice
usbcore: registered new interface driver usbhid
...
Reply to: