LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
* help regarding my kernel compilation for powerpc 405-xilinxml300
From: shivani kirubanandan @ 2006-02-28  7:13 UTC (permalink / raw)
  To: linuxppc-embedded

hello,
intially the compiler was
unable to find xiic_l.h file ...so i went to
arch/ppc/boot/simple/embed_config.c

and gave the entire path for the file to be
#include<home/shivani/downloads/linux-2.4.26/drivers/i2c/xilinx_iic/xiic_l.h>

after which this error has occured,am not sure where
the path ent wrong i again tried changing the path for
this file (xbasic_types.h) but the error persists
help me out plz.


xiic_l.h:64:85:
home/shivani/downloads/linux-2.4.26/drivers/i2c/xilinx_iic/xbasic_types.h:
No such file or directory
make[3]: *** [i2c-algo-xilinx.o] Error 1
make[3]: Leaving directory
`/home/shivani/downloads/linux-2.4.26/drivers/i2c/xilinx_iic'
make[2]: *** [_subdir_xilinx_iic] Error 2
make[2]: Leaving directory
`/home/shivani/downloads/linux-2.4.26/drivers/i2c'
make[1]: *** [_subdir_i2c] Error 2
make[1]: Leaving directory
`/home/shivani/downloads/linux-2.4.26/drivers'
make: *** [_dir_drivers] Error 2


thanks in advance 

shivani


__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 

^ permalink raw reply

* Help: How to search for previous topics
From: Krishnan @ 2006-02-28  6:34 UTC (permalink / raw)
  To: linuxppc-embedded

Hello,

Could anyone please tell me how previous topics could be searched so that I
don't
need to trouble anyone for repetitive content?

I only know of one way today, go through each list and try to do a Ctrl+F
which is quite
painful.

Cheers,
Kris

^ permalink raw reply

* Re: copying /sys causes fans to spin up
From: Benjamin Herrenschmidt @ 2006-02-27 21:53 UTC (permalink / raw)
  To: Olaf Hering; +Cc: linuxppc-dev
In-Reply-To: <20060227215023.GA21932@suse.de>

On Mon, 2006-02-27 at 22:50 +0100, Olaf Hering wrote:
>  On Tue, Feb 28, Benjamin Herrenschmidt wrote:
> 
> > 
> > > windfarm: failed to attach ds1775 hd-temp to i2c
> > > windfarm: failed to attach MAX6690 sensor
> > > 
> > > 
> > > Maybe thats harmless, but I have seen it on a few different G5.
> > 
> > Hrm... the windfarm sensors are useless on those old G5s that use
> > therm_pm72... though I wouldn't have expected them to cause harm.
> 
> Its compiled into the kernel, too much trouble if they are not loaded by
> accident.

Yeah, I should add a test for supported machines... 

Ben.

^ permalink raw reply

* Re: copying /sys causes fans to spin up
From: Olaf Hering @ 2006-02-27 21:50 UTC (permalink / raw)
  To: Benjamin Herrenschmidt; +Cc: linuxppc-dev
In-Reply-To: <1141076553.4809.18.camel@localhost.localdomain>

 On Tue, Feb 28, Benjamin Herrenschmidt wrote:

> 
> > windfarm: failed to attach ds1775 hd-temp to i2c
> > windfarm: failed to attach MAX6690 sensor
> > 
> > 
> > Maybe thats harmless, but I have seen it on a few different G5.
> 
> Hrm... the windfarm sensors are useless on those old G5s that use
> therm_pm72... though I wouldn't have expected them to cause harm.

Its compiled into the kernel, too much trouble if they are not loaded by
accident.

^ permalink raw reply

* Re: copying /sys causes fans to spin up
From: Benjamin Herrenschmidt @ 2006-02-27 21:42 UTC (permalink / raw)
  To: Olaf Hering; +Cc: linuxppc-dev
In-Reply-To: <20060227213612.GB21832@suse.de>


> windfarm: failed to attach ds1775 hd-temp to i2c
> windfarm: failed to attach MAX6690 sensor
> 
> 
> Maybe thats harmless, but I have seen it on a few different G5.

Hrm... the windfarm sensors are useless on those old G5s that use
therm_pm72... though I wouldn't have expected them to cause harm.

Might be useful for now to make them not load on PowerMac7,2 7,3 and
RackMac3,1 tho...

Ben.

^ permalink raw reply

* Re: copying /sys causes fans to spin up
From: Olaf Hering @ 2006-02-27 21:36 UTC (permalink / raw)
  To: Benjamin Herrenschmidt; +Cc: linuxppc-dev
In-Reply-To: <20060227213435.GA21832@suse.de>

 On Mon, Feb 27, Olaf Hering wrote:

>  On Tue, Feb 28, Benjamin Herrenschmidt wrote:
> 
> > On Mon, 2006-02-27 at 17:09 +0100, Olaf Hering wrote:
> > > Ben, 
> > > 
> > > 
> > > some tool copies /sys, and while doing it, the fans start to spin up on
> > > my G5. Any idea how to fix it, other than not reading from /sys? Have to
> > > find the exact file.
> > 
> > Interesting... it's causing the i2c bus to go nuts... It would be useful
> > to find out what file indeed...
> 
> For Olof it was /sys/devices/platform/windfarm.0/hd-temp, but I cant
> test it right now.

my dmesg has:

windfarm: failed to attach ds1775 hd-temp to i2c
windfarm: failed to attach MAX6690 sensor


Maybe thats harmless, but I have seen it on a few different G5.

^ permalink raw reply

* Re: copying /sys causes fans to spin up
From: Olof Johansson @ 2006-02-27 21:35 UTC (permalink / raw)
  To: Olof Johansson; +Cc: Olaf Hering, linuxppc-dev
In-Reply-To: <20060227213319.GC4685@pb15.lixom.net>

On Mon, Feb 27, 2006 at 01:33:19PM -0800, Olof Johansson wrote:

> For me it's /sys/devices/system/windfarm.0/hd-temp

-EBADCRACK

/sys/devices/platform/windfarm.0/hd-temp, I mean. And it's enough to cat
the file for it to happen.

^ permalink raw reply

* Re: copying /sys causes fans to spin up
From: Olaf Hering @ 2006-02-27 21:34 UTC (permalink / raw)
  To: Benjamin Herrenschmidt; +Cc: linuxppc-dev
In-Reply-To: <1141075795.4809.15.camel@localhost.localdomain>

 On Tue, Feb 28, Benjamin Herrenschmidt wrote:

> On Mon, 2006-02-27 at 17:09 +0100, Olaf Hering wrote:
> > Ben, 
> > 
> > 
> > some tool copies /sys, and while doing it, the fans start to spin up on
> > my G5. Any idea how to fix it, other than not reading from /sys? Have to
> > find the exact file.
> 
> Interesting... it's causing the i2c bus to go nuts... It would be useful
> to find out what file indeed...

For Olof it was /sys/devices/platform/windfarm.0/hd-temp, but I cant
test it right now.

^ permalink raw reply

* Re: copying /sys causes fans to spin up
From: Olof Johansson @ 2006-02-27 21:33 UTC (permalink / raw)
  To: Benjamin Herrenschmidt; +Cc: linuxppc-dev, Olaf Hering
In-Reply-To: <1141075795.4809.15.camel@localhost.localdomain>

On Tue, Feb 28, 2006 at 08:29:55AM +1100, Benjamin Herrenschmidt wrote:
> On Mon, 2006-02-27 at 17:09 +0100, Olaf Hering wrote:
> > Ben, 
> > 
> > 
> > some tool copies /sys, and while doing it, the fans start to spin up on
> > my G5. Any idea how to fix it, other than not reading from /sys? Have to
> > find the exact file.
> 
> Interesting... it's causing the i2c bus to go nuts... It would be useful
> to find out what file indeed...

For me it's /sys/devices/system/windfarm.0/hd-temp

It also seems that the windfarm module misdetects my system. From dmesg:

PowerMac G5 Thermal control driver 1.2b2
Detected fan controls:
  0: PWM fan, id 1, location: BACKSIDE,SYS CTRLR FAN
  1: RPM fan, id 2, location: DRIVE BAY
  2: PWM fan, id 2, location: SLOT,PCI FAN
  3: RPM fan, id 3, location: CPU A INTAKE
  4: RPM fan, id 4, location: CPU A EXHAUST
  5: RPM fan, id 5, location: CPU B INTAKE
  6: RPM fan, id 6, location: CPU B EXHAUST
  7: RPM fan, id 1, location: CPU A PUMP
  8: RPM fan, id 0, location: CPU B PUMP
....
PowerMac i2c bus pmu 2 registered
PowerMac i2c bus pmu 1 registered
PowerMac i2c bus mac-io 0 registered
PowerMac i2c bus u3 1 registered
Liquid cooling pumps detected, using new algorithm !
windfarm: failed to attach ds1775 hd-temp to i2c

And it for sure is not a liquid cooled model, the 2.0's never were.
(PM7,3)

I think this is a 2.6.16-rc2 with the cpufreq patches, but I seems to
have lost the source tree to verify for sure.


-Olof

^ permalink raw reply

* Re: copying /sys causes fans to spin up
From: Benjamin Herrenschmidt @ 2006-02-27 21:29 UTC (permalink / raw)
  To: Olaf Hering; +Cc: linuxppc-dev
In-Reply-To: <20060227160911.GA17569@suse.de>

On Mon, 2006-02-27 at 17:09 +0100, Olaf Hering wrote:
> Ben, 
> 
> 
> some tool copies /sys, and while doing it, the fans start to spin up on
> my G5. Any idea how to fix it, other than not reading from /sys? Have to
> find the exact file.

Interesting... it's causing the i2c bus to go nuts... It would be useful
to find out what file indeed...

Ben.

^ permalink raw reply

* Re: fix NULL pointer in handle_eeh_events
From: Linas Vepstas @ 2006-02-27 17:27 UTC (permalink / raw)
  To: Olaf Hering; +Cc: linuxppc-dev
In-Reply-To: <20060227145259.GA15955@suse.de>

On Mon, Feb 27, 2006 at 03:52:59PM +0100, Olaf Hering was heard to remark:
> 
> This patch fixes a crash in handle_eeh_events,

Dohh.

Acked-by: Linas Vepstas <linas@austin.ibm.com>

> but ethtool -t still doesnt work right.

I'll look at this.

--linas

^ permalink raw reply

* Re: fix NULL pointer in handle_eeh_events
From: Olaf Hering @ 2006-02-27 17:31 UTC (permalink / raw)
  To: Linas Vepstas; +Cc: linuxppc-dev
In-Reply-To: <20060227172703.GL26339@austin.ibm.com>

 On Mon, Feb 27, Linas Vepstas wrote:

> > but ethtool -t still doesnt work right.
> 
> I'll look at this.

Reverting e100.c back to 2.6.15 status fixes it, but maybe it just does
not cover the error paths in EEH.

^ permalink raw reply

* Re: copying /sys causes fans to spin up
From: Olaf Hering @ 2006-02-27 16:43 UTC (permalink / raw)
  To: Benjamin Herrenschmidt, linuxppc-dev
In-Reply-To: <20060227160911.GA17569@suse.de>

 On Mon, Feb 27, Olaf Hering wrote:

> Ben, 
> 
> 
> some tool copies /sys, and while doing it, the fans start to spin up on
> my G5. Any idea how to fix it, other than not reading from /sys? Have to
> find the exact file.

Just 'cp -a --parents /sys /dev/shm/' will trigger this, but fans dont
spin up:

KW: wrong state. Got KW_I2C_IRQ_ADDR, state: state_stop (isr: 06)
KW: wrong state. Got KW_I2C_IRQ_ADDR, state: state_stop (isr: 06)
KW: wrong state. Got KW_I2C_IRQ_STOP, state: state_addr (isr: 04)
low_i2c: Keywest got an out of state interrupt, ignoring
low_i2c: Keywest got an out of state interrupt, ignoring
low_i2c: Keywest got an out of state interrupt, ignoring

^ permalink raw reply

* Re: [PATCH] powerpc: Fix mem= cmdline handling on arch/powerpc for !MULTIPLATFORM
From: Kumar Gala @ 2006-02-27 16:12 UTC (permalink / raw)
  To: Dave Hansen; +Cc: linuxppc-dev, Linus Torvalds, linux-kernel
In-Reply-To: <1140986335.8697.139.camel@localhost.localdomain>


On Feb 26, 2006, at 2:38 PM, Dave Hansen wrote:

> On Fri, 2006-02-24 at 10:54 -0600, Kumar Gala wrote:
>> +       if (strstr(cmd_line, "mem=")) {
>> +               char *p, *q;
>> +               unsigned long maxmem = 0;
>> +
>> +               for (q = cmd_line; (p = strstr(q, "mem=")) != 0; ) {
>> +                       q = p + 4;
>> +                       if (p > cmd_line && p[-1] != ' ')
>> +                               continue;
>> +                       maxmem = simple_strtoul(q, &q, 0);
>> +                       if (*q == 'k' || *q == 'K') {
>> +                               maxmem <<= 10;
>> +                               ++q;
>> +                       } else if (*q == 'm' || *q == 'M') {
>> +                               maxmem <<= 20;
>> +                               ++q;
>> +                       } else if (*q == 'g' || *q == 'G') {
>> +                               maxmem <<= 30;
>> +                               ++q;
>> +                       }
>> +               }
>> +               memory_limit = maxmem;
>> +       }
>
> You may want to check out lib/cmdline.c's memparse() function.  I  
> think
> it does this for you.

Yeah, found it after I sent the patch.  Since Linus applied this  
version, I'll provide Paul a version that changes this code to use  
memparse for post 2.6.16.

- kumar

^ permalink raw reply

* copying /sys causes fans to spin up
From: Olaf Hering @ 2006-02-27 16:09 UTC (permalink / raw)
  To: Benjamin Herrenschmidt, linuxppc-dev

Ben, 


some tool copies /sys, and while doing it, the fans start to spin up on
my G5. Any idea how to fix it, other than not reading from /sys? Have to
find the exact file.



Page orders: linear mapping = 24, others = 12
Found initrd at 0xc000000001100000:0xc0000000013e8000
Found U3 memory controller & host bridge @ 0xf8000000 revision: 0x32
Mapped at 0xd000080080000000
Found a K2 mac-io controller, rev: 32, mapped at 0xd000080080041000
PowerMac motherboard: PowerMac G5
Using native/NAP idle loop
DART: table not allocated, using direct DMA
Starting Linux PPC64 #1 SMP Mon Feb 20 15:56:05 UTC 2006
-----------------------------------------------------
ppc64_pft_size                = 0x0
ppc64_interrupt_controller    = 0x1
platform                      = 0x400
physicalMemorySize            = 0x10000000
ppc64_caches.dcache_line_size = 0x80
ppc64_caches.icache_line_size = 0x80
htab_address                  = 0xc00000000f800000
htab_hash_mask                = 0x7fff
-----------------------------------------------------
[boot]0100 MM Init
[boot]0100 MM Init Done
Linux version 2.6.16-rc4-3-ppc64 (geeko@buildhost) (gcc version 4.1.0 20060218 (prerelease) (SUSE Linux)) #1 SMP Mon Feb 20 15:56:05 UTC 2006
[boot]0012 Setup Arch
Top of RAM: 0x10000000, Total RAM: 0x10000000
Memory hole size: 0MB
Found U3-AGP PCI host bridge.  Firmware bus number: 240->255
Can't get bus-range for /ht@0,f2000000, assume bus 0
Found U3-HT PCI host bridge.  Firmware bus number: 0->239
PCI Host 0, io start: 400000; io end: bfffff
PCI Host 1, io start: 0; io end: 3fffff
via-pmu: Server Mode is disabled
PMU driver v2 initialized for Core99, firmware: 0c
nvram: Checking bank 0...
nvram: gen0=445, gen1=444
nvram: Active bank is: 0
nvram: OF partition at 0x410
nvram: XP partition at 0x1020
nvram: NR partition at 0x1120
On node 0 totalpages: 65536
  DMA zone: 65536 pages, LIFO batch:15
  DMA32 zone: 0 pages, LIFO batch:0
  Normal zone: 0 pages, LIFO batch:0
  HighMem zone: 0 pages, LIFO batch:0
[boot]0015 Setup Done
Built 1 zonelists
Kernel command line: quiet sysrq=1 root=/dev/disk/by-path/pci-0001:05:0c.0-scsi-0:0:0:0-part11 root=/dev/sda11 
mpic: Setting up MPIC " MPIC 1   " version 1.2 at 80040000, max 4 CPUs
mpic: ISU size: 120, shift: 7, mask: 7f
mpic: Initializing for 120 sources
mpic: Setting up MPIC " MPIC 2   " version 1.2 at f8040000, max 4 CPUs
mpic: ISU size: 120, shift: 7, mask: 7f
mpic: Initializing for 120 sources
PID hash table entries: 2048 (order: 11, 65536 bytes)
time_init: decrementer frequency = 33.333333 MHz
time_init: processor frequency   = 1600.000000 MHz
Console: colour dummy device 80x25
Dentry cache hash table entries: 65536 (order: 7, 524288 bytes)
Inode-cache hash table entries: 32768 (order: 6, 262144 bytes)
freeing bootmem node 0
Memory: 242736k/262144k available (4336k kernel code, 19408k reserved, 1952k data, 851k bss, 256k init)
Calibrating delay loop... 66.56 BogoMIPS (lpj=332800)
Security Framework v1.0.0 initialized
Mount-cache hash table entries: 256
checking if image is initramfs... it is
Freeing initrd memory: 2976k freed
PowerMac SMP probe found 1 cpus
Brought up 1 CPUs
migration_cost=0
NET: Registered protocol family 16
KeyWest i2c @0xf8001003 irq 170 /u3@0,f8000000/i2c@f8001000
 channel 0 bus <multibus>
 channel 1 bus <multibus>
KeyWest i2c @0x80018000 irq 26 /ht@0,f2000000/pci@3/mac-io@7/i2c@18000
 channel 0 bus <multibus>
PMU i2c /ht@0,f2000000/pci@3/mac-io@7/via-pmu@16000/pmu-i2c
 channel 1 bus <multibus>
 channel 2 bus <multibus>
Installing base platform functions...
Installing MMIO functions for macio /ht@0,f2000000/pci@3/mac-io@7
Installing GPIO functions for macio /ht@0,f2000000/pci@3/mac-io@7
Calling initial GPIO functions for macio /ht@0,f2000000/pci@3/mac-io@7
Do write 0x82 to GPIO /ht@0,f2000000/pci@3/mac-io@7/gpio@50/line-input-detect@c (d00008008004105c)
Do write 0x80 to GPIO /ht@0,f2000000/pci@3/mac-io@7/gpio@50/line-output-detect@16 (d000080080041066)
Do write 0x82 to GPIO /ht@0,f2000000/pci@3/mac-io@7/gpio@50/headphone-detect@17 (d000080080041067)
Installing functions for UniN /u3@0,f8000000
All base functions installed
PCI: Probing PCI hardware
Can't get ranges for PCI-PCI bridge /ht@0,f2000000/pci@2
mapping IO f0000000 -> d000080000400000, size: 800000
mapping IO f4000000 -> d000080000000000, size: 400000
PCI: Probing PCI hardware done
Registering pmac pic with sysfs...
usbcore: registered new driver usbfs
usbcore: registered new driver hub
TC classifier action (bugs to netdev@vger.kernel.org cc hadi@cyberus.ca)
IBM eBus Device Driver
nvram_init: Could not find nvram partition for nvram buffered error logging.
Registering G5 CPU frequency driver
Frequency method: i2c/pfunc, Voltage method: i2c/pfunc
Low: 1301 Mhz, High: 1600 Mhz, Cur: 1600 MHz
audit: initializing netlink socket (disabled)
audit(1141055721.759:1): initialized
Total HugeTLB memory allocated, 0
VFS: Disk quotas dquot_6.5.1
Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
Initializing Cryptographic API
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered (default)
nvidiafb: PCI id - 10de0321
nvidiafb: Actual id - 10de0321
nvidiafb: nVidia device/chipset 10DE0321
nvidiafb: CRTC0 analog not found
nvidiafb: CRTC1 analog not found
nvidiafb: EDID found from BUS2
nvidiafb: CRTC 1 is currently programmed for DFP
nvidiafb: Using DFP on CRTC 1
Panel size is 1680 x 1050
nvidiafb: Flat panel dithering disabled
Console: switching to colour frame buffer device 210x65
nvidiafb: PCI nVidia NV32 framebuffer (64MB @ 0xA8000000)
vio_register_driver: driver hvc_console registering
HVSI: registered 0 devices
Generic RTC Driver v1.07
pmac_zilog: 0.6 (Benjamin Herrenschmidt <benh@kernel.crashing.org>)
ttyS0 at MMIO 0x80013020 (irq = 22) is a Z85c30 ESCC - Serial port
ttyS1 at MMIO 0x80013000 (irq = 23) is a Z85c30 ESCC - Serial port
RAMDISK driver initialized: 16 RAM disks of 123456K size 1024 blocksize
MacIO PCI driver attached to K2 chipset
input: Macintosh mouse button emulation as /class/input/input0
PowerMac G5 Thermal control driver 1.2b2
adb: starting probe task...
adb: finished probe task...
Detected fan controls:
  0: PWM fan, id 1, location: BACKSIDE,SYS CTRLR FAN
  1: RPM fan, id 2, location: DRIVE BAY
  2: PWM fan, id 2, location: SLOT,PCI FAN
  3: RPM fan, id 3, location: CPU A INTAKE
  4: RPM fan, id 4, location: CPU A EXHAUST
  5: RPM fan, id 5, location: CPU B INTAKE
  6: RPM fan, id 6, location: CPU B EXHAUST
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
PCI: Enabling device: (0001:03:0d.0), cmd 16
ide0: Found Apple K2 ATA-6 controller, bus ID 3, irq 39
Probing IDE interface ide0...
hda: PIONEER DVD-RW DVR-106D, ATAPI CD/DVD-ROM drive
hda: Enabling Ultra DMA 2
ide0 at 0xd0000800872eb000-0xd0000800872eb007,0xd0000800872eb160 on irq 39
PCI: Enabling device: (0001:02:0b.2), cmd 6
ehci_hcd 0001:02:0b.2: EHCI Host Controller
ehci_hcd 0001:02:0b.2: new USB bus registered, assigned bus number 1
ehci_hcd 0001:02:0b.2: irq 63, io mem 0x80100000
ehci_hcd 0001:02:0b.2: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
usb usb1: new device found, idVendor=0000, idProduct=0000
usb usb1: new device strings: Mfr=3, Product=2, SerialNumber=1
usb usb1: Product: EHCI Host Controller
usb usb1: Manufacturer: Linux 2.6.16-rc4-3-ppc64 ehci_hcd
usb usb1: SerialNumber: 0001:02:0b.2
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 5 ports detected
ohci_hcd: 2005 April 22 USB 1.1 'Open' Host Controller (OHCI) Driver (PCI)
PCI: Enabling device: (0001:01:08.0), cmd 2
ohci_hcd 0001:01:08.0: OHCI Host Controller
ohci_hcd 0001:01:08.0: new USB bus registered, assigned bus number 2
ohci_hcd 0001:01:08.0: irq 27, io mem 0x80081000
usb usb2: new device found, idVendor=0000, idProduct=0000
usb usb2: new device strings: Mfr=3, Product=2, SerialNumber=1
usb usb2: Product: OHCI Host Controller
usb usb2: Manufacturer: Linux 2.6.16-rc4-3-ppc64 ohci_hcd
usb usb2: SerialNumber: 0001:01:08.0
usb usb2: configuration #1 chosen from 1 choice
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 2 ports detected
PCI: Enabling device: (0001:01:09.0), cmd 2
ohci_hcd 0001:01:09.0: OHCI Host Controller
ohci_hcd 0001:01:09.0: new USB bus registered, assigned bus number 3
ohci_hcd 0001:01:09.0: irq 28, io mem 0x80080000
usb usb3: new device found, idVendor=0000, idProduct=0000
usb usb3: new device strings: Mfr=3, Product=2, SerialNumber=1
usb usb3: Product: OHCI Host Controller
usb usb3: Manufacturer: Linux 2.6.16-rc4-3-ppc64 ohci_hcd
usb usb3: SerialNumber: 0001:01:09.0
usb usb3: configuration #1 chosen from 1 choice
hub 3-0:1.0: USB hub found
hub 3-0:1.0: 2 ports detected
PCI: Enabling device: (0001:02:0b.0), cmd 2
ohci_hcd 0001:02:0b.0: OHCI Host Controller
ohci_hcd 0001:02:0b.0: new USB bus registered, assigned bus number 4
ohci_hcd 0001:02:0b.0: irq 63, io mem 0x80102000
usb usb4: new device found, idVendor=0000, idProduct=0000
usb usb4: new device strings: Mfr=3, Product=2, SerialNumber=1
usb usb4: Product: OHCI Host Controller
usb usb4: Manufacturer: Linux 2.6.16-rc4-3-ppc64 ohci_hcd
usb usb4: SerialNumber: 0001:02:0b.0
usb usb4: configuration #1 chosen from 1 choice
hub 4-0:1.0: USB hub found
hub 4-0:1.0: 3 ports detected
PCI: Enabling device: (0001:02:0b.1), cmd 2
ohci_hcd 0001:02:0b.1: OHCI Host Controller
ohci_hcd 0001:02:0b.1: new USB bus registered, assigned bus number 5
ohci_hcd 0001:02:0b.1: irq 63, io mem 0x80101000
usb usb5: new device found, idVendor=0000, idProduct=0000
usb usb5: new device strings: Mfr=3, Product=2, SerialNumber=1
usb usb5: Product: OHCI Host Controller
usb usb5: Manufacturer: Linux 2.6.16-rc4-3-ppc64 ohci_hcd
usb usb5: SerialNumber: 0001:02:0b.1
usb usb5: configuration #1 chosen from 1 choice
hub 5-0:1.0: USB hub found
hub 5-0:1.0: 2 ports detected
usb 4-2: new full speed USB device using ohci_hcd and address 2
usb 4-2: new device found, idVendor=05ac, idProduct=1003
usb 4-2: new device strings: Mfr=1, Product=2, SerialNumber=0
usb 4-2: Product: Hub in Apple Extended USB Keyboard
usb 4-2: Manufacturer: Mitsumi Electric
usb 4-2: configuration #1 chosen from 1 choice
hub 4-2:1.0: USB hub found
hub 4-2:1.0: 3 ports detected
usb 5-2: new full speed USB device using ohci_hcd and address 2
usb 5-2: new device found, idVendor=06cd, idProduct=0110
usb 5-2: new device strings: Mfr=1, Product=2, SerialNumber=0
usb 5-2: Product: Keyspan USB Serial Adapter
usb 5-2: Manufacturer: Keyspan, a division of InnoSys Inc.
usb 5-2: configuration #1 chosen from 2 choices
usb 4-2.1: new low speed USB device using ohci_hcd and address 3
usb 4-2.1: new device found, idVendor=05ac, idProduct=0307
usb 4-2.1: new device strings: Mfr=1, Product=2, SerialNumber=0
usb 4-2.1: Product: Apple Optical USB Mouse
usb 4-2.1: Manufacturer: Logitech
usb 4-2.1: configuration #1 chosen from 1 choice
usb 4-2.3: new full speed USB device using ohci_hcd and address 4
usb 4-2.3: new device found, idVendor=05ac, idProduct=020c
usb 4-2.3: new device strings: Mfr=1, Product=3, SerialNumber=0
usb 4-2.3: Product: Apple Extended USB Keyboard
usb 4-2.3: Manufacturer: Mitsumi Electric
usb 4-2.3: configuration #1 chosen from 1 choice
usbcore: registered new driver hiddev
input: Logitech Apple Optical USB Mouse as /class/input/input1
input: USB HID v1.10 Mouse [Logitech Apple Optical USB Mouse] on usb-0001:02:0b.0-2.1
input: Mitsumi Electric Apple Extended USB Keyboard as /class/input/input2
input: USB HID v1.10 Keyboard [Mitsumi Electric Apple Extended USB Keyboard] on usb-0001:02:0b.0-2.3
input: Mitsumi Electric Apple Extended USB Keyboard as /class/input/input3
input: USB HID v1.10 Device [Mitsumi Electric Apple Extended USB Keyboard] on usb-0001:02:0b.0-2.3
usbcore: registered new driver usbhid
drivers/usb/input/hid-core.c: v2.6:USB HID core driver
mice: PS/2 mouse device common for all mice
PowerMac i2c bus pmu 2 registered
PowerMac i2c bus pmu 1 registered
PowerMac i2c bus mac-io 0 registered
found max6690, loc=BACKSIDE reg=98
found max6690, loc=MLB MAX6690 AMB reg=9c
PowerMac i2c bus u3 1 registered
windfarm: failed to attach ds1775 hd-temp to i2c
found max6690, loc=BACKSIDE reg=98
windfarm: failed to attach MAX6690 sensor
found max6690, loc=MLB MAX6690 AMB reg=9c
PowerMac i2c bus u3 0 registered
md: md driver 0.90.3 MAX_MD_DEVS=256, MD_SB_DISKS=27
md: bitmap version 4.39
oprofile: using ppc64/970 performance monitoring.
NET: Registered protocol family 2
IP route cache hash table entries: 4096 (order: 3, 32768 bytes)
TCP established hash table entries: 16384 (order: 7, 524288 bytes)
TCP bind hash table entries: 16384 (order: 7, 524288 bytes)
TCP: Hash tables configured (established 16384 bind 16384)
TCP reno registered
NET: Registered protocol family 1
NET: Registered protocol family 17
NET: Registered protocol family 15
Freeing unused kernel memory: 256k freed
SCSI subsystem initialized
libata version 1.20 loaded.
sata_svw 0001:05:0c.0: version 1.07
ata1: SATA max UDMA/133 cmd 0xD0000800872F2000 ctl 0xD0000800872F2020 bmdma 0xD0000800872F2030 irq 0
ata2: SATA max UDMA/133 cmd 0xD0000800872F2100 ctl 0xD0000800872F2120 bmdma 0xD0000800872F2130 irq 0
ata3: SATA max UDMA/133 cmd 0xD0000800872F2200 ctl 0xD0000800872F2220 bmdma 0xD0000800872F2230 irq 0
ata4: SATA max UDMA/133 cmd 0xD0000800872F2300 ctl 0xD0000800872F2320 bmdma 0xD0000800872F2330 irq 0
ata1: SATA link up 1.5 Gbps (SStatus 113)
ata1: dev 0 cfg 49:2f00 82:346b 83:7d01 84:4003 85:3469 86:3c01 87:4003 88:007f
ata1: dev 0 ATA-6, max UDMA/133, 156301488 sectors: LBA48
ata1: dev 0 configured for UDMA/133
scsi0 : sata_svw
ata2: SATA link up 1.5 Gbps (SStatus 113)
ata2: dev 0 cfg 49:2f00 82:7c6b 83:7b09 84:4003 85:7c69 86:3a01 87:4003 88:007f
ata2: dev 0 ATA-7, max UDMA/133, 156312576 sectors: LBA
ata2: dev 0 configured for UDMA/133
scsi1 : sata_svw
ata3: SATA link down (SStatus 4)
scsi2 : sata_svw
ata4: SATA link down (SStatus 4)
scsi3 : sata_svw
  Vendor: ATA       Model: ST380013AS        Rev: 3.05
  Type:   Direct-Access                      ANSI SCSI revision: 05
SCSI device sda: 156301488 512-byte hdwr sectors (80026 MB)
sda: Write Protect is off
sda: Mode Sense: 00 3a 00 00
SCSI device sda: drive cache: write back
SCSI device sda: 156301488 512-byte hdwr sectors (80026 MB)
sda: Write Protect is off
sda: Mode Sense: 00 3a 00 00
SCSI device sda: drive cache: write back
 sda: [mac] sda1 sda2 sda3 sda4 sda5 sda6 sda7 sda8 sda9 sda10 sda11
sd 0:0:0:0: Attached scsi disk sda
  Vendor: ATA       Model: Maxtor 6Y080M0    Rev: YAR5
  Type:   Direct-Access                      ANSI SCSI revision: 05
sd 0:0:0:0: Attached scsi generic sg0 type 0
SCSI device sdb: 156312576 512-byte hdwr sectors (80032 MB)
sdb: Write Protect is off
sdb: Mode Sense: 00 3a 00 00
SCSI device sdb: drive cache: write back
SCSI device sdb: 156312576 512-byte hdwr sectors (80032 MB)
sdb: Write Protect is off
sdb: Mode Sense: 00 3a 00 00
SCSI device sdb: drive cache: write back
 sdb: [mac] sdb1 sdb2 sdb3 sdb4 sdb5 sdb6 sdb7 sdb8
sd 1:0:0:0: Attached scsi disk sdb
sd 1:0:0:0: Attached scsi generic sg1 type 0
Adding 1048568k swap on /dev/sda3.  Priority:-1 extents:1 across:1048568k
Adding 1023992k swap on /dev/sdb3.  Priority:-2 extents:1 across:1023992k
input: PowerMac Beep as /class/input/input4
hda: ATAPI 32X DVD-ROM DVD-R CD-R/RW drive, 2000kB Cache, UDMA(33)
Uniform CD-ROM driver Revision: 3.20
Linux agpgart interface v0.101 (c) Dave Jones
agpgart: Detected Apple U3 chipset
agpgart: configuring for size idx: 64
agpgart: AGP aperture is 256M @ 0x0
ieee1394: Initialized config rom entry `ip1394'
PCI: Enabling device: (0001:03:0e.0), cmd 2
ohci1394: fw-host0: Unexpected PCI resource length of 1000!
ohci1394: fw-host0: OHCI-1394 1.0 (PCI): IRQ=[40]  MMIO=[80200000-802007ff]  Max Packet=[4096]  IR/IT contexts=[8/8]
tg3.c:v3.49 (Feb 2, 2006)
PCI: Enabling device: (0001:06:03.0), cmd 6
spidernet: module not supported by Novell, setting U taint flag.
eth0: Tigon3 [partno(3C996B-T) rev 0105 PHY(5701)] (PCI:33MHz:64-bit) 10/100/1000BaseT Ethernet 00:04:76:f3:c2:4f
eth0: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[0] Split[0] WireSpeed[1] TSOcap[0] 
eth0: dma_rwctrl[76ff2d0f]
sungem.c:v0.98 8/24/03 David S. Miller (davem@redhat.com)
PHY ID: 2062e0, addr: 1
eth1: Sun GEM (PCI) 10/100/1000BaseT Ethernet 00:0a:95:a6:5d:66 
eth1: Found BCM5421-K2 PHY
ieee1394: Node added: ID:BUS[0-00:1023]  GUID[0010b92100519fad]
ieee1394: Host added: ID:BUS[0-01:1023]  GUID[000a95fffea65d66]
usbcore: registered new driver usbserial
drivers/usb/serial/usb-serial.c: USB Serial support registered for generic
usbcore: registered new driver usbserial_generic
drivers/usb/serial/usb-serial.c: USB Serial Driver core
drivers/usb/serial/usb-serial.c: USB Serial support registered for Keyspan - (without firmware)
drivers/usb/serial/usb-serial.c: USB Serial support registered for Keyspan 1 port adapter
drivers/usb/serial/usb-serial.c: USB Serial support registered for Keyspan 2 port adapter
drivers/usb/serial/usb-serial.c: USB Serial support registered for Keyspan 4 port adapter
keyspan 5-2:1.0: Keyspan 2 port adapter converter detected
usb 5-2: Keyspan 2 port adapter converter now attached to ttyUSB0
usb 5-2: Keyspan 2 port adapter converter now attached to ttyUSB1
usbcore: registered new driver keyspan
drivers/usb/serial/keyspan.c: v1.1.4:Keyspan USB to Serial Converter Driver
eth0 renamed to ethxx0
eth1 renamed to eth0
eth0: Link is up at 100 Mbps, full-duplex.
ethxx0 renamed to eth1
ieee1394: sbp2: Driver forced to serialize I/O (serialize_io=1)
ieee1394: sbp2: Try serialize_io=0 for better performance
scsi4 : SBP-2 IEEE-1394
ieee1394: sbp2: Logged into SBP-2 device
ieee1394: Node 0-00:1023: Max speed [S400] - Max payload [2048]
  Vendor: Maxtor    Model: OneTouch II       Rev: 023g
  Type:   Direct-Access                      ANSI SCSI revision: 04
SCSI device sdc: 586114704 512-byte hdwr sectors (300091 MB)
sdc: Write Protect is off
sdc: Mode Sense: 00 32 00 00
sdc: cache data unavailable
sdc: assuming drive cache: write through
SCSI device sdc: 586114704 512-byte hdwr sectors (300091 MB)
sdc: Write Protect is off
sdc: Mode Sense: 00 32 00 00
sdc: cache data unavailable
sdc: assuming drive cache: write through
 sdc: [mac] sdc1 sdc2 sdc3 sdc4 sdc5 sdc6 sdc7 sdc8
sd 4:0:1:0: Attached scsi disk sdc
sd 4:0:1:0: Attached scsi generic sg2 type 0
device-mapper: 4.5.0-ioctl (2005-10-04) initialised: dm-devel@redhat.com
dm-netlink version 0.0.2 loaded
loop: loaded (max 8 devices)
AppArmor: AppArmor (version 2.0-19.43r6152) initialized
audit(1141052147.508:2): AppArmor (version 2.0-19.43r6152) initialized

eth0: Link is up at 100 Mbps, full-duplex.
eth0: Pause is enabled (rxfifo: 10240 off: 7168 on: 5632)
NET: Registered protocol family 10
lo: Disabled Privacy Extensions
IPv6 over IPv4 tunneling driver
st: Version 20050830, fixed bufsize 32768, s/g segs 256
Warning: /proc/ide/hd?/settings interface is obsolete, and will be removed soon!
KW: wrong state. Got KW_I2C_IRQ_ADDR, state: state_stop (isr: 06)
KW: wrong state. Got KW_I2C_IRQ_ADDR, state: state_stop (isr: 06)
KW: wrong state. Got KW_I2C_IRQ_ADDR, state: state_stop (isr: 06)
KW: wrong state. Got KW_I2C_IRQ_STOP, state: state_write (isr: 04)
KW: wrong state. Got KW_I2C_IRQ_ADDR, state: state_stop (isr: 06)
KW: wrong state. Got KW_I2C_IRQ_ADDR, state: state_stop (isr: 06)
KW: wrong state. Got KW_I2C_IRQ_STOP, state: state_write (isr: 04)
KW: wrong state. Got KW_I2C_IRQ_ADDR, state: state_stop (isr: 06)
KW: wrong state. Got KW_I2C_IRQ_ADDR, state: state_stop (isr: 06)
KW: wrong state. Got KW_I2C_IRQ_STOP, state: state_write (isr: 04)
KW: wrong state. Got KW_I2C_IRQ_ADDR, state: state_stop (isr: 06)
KW: wrong state. Got KW_I2C_IRQ_ADDR, state: state_stop (isr: 06)
KW: wrong state. Got KW_I2C_IRQ_STOP, state: state_write (isr: 04)
KW: wrong state. Got KW_I2C_IRQ_ADDR, state: state_stop (isr: 06)
KW: wrong state. Got KW_I2C_IRQ_ADDR, state: state_stop (isr: 06)
KW: wrong state. Got KW_I2C_IRQ_STOP, state: state_write (isr: 04)
KW: wrong state. Got KW_I2C_IRQ_ADDR, state: state_stop (isr: 06)
KW: wrong state. Got KW_I2C_IRQ_STOP, state: state_write (isr: 04)
KW: wrong state. Got KW_I2C_IRQ_ADDR, state: state_stop (isr: 06)
KW: wrong state. Got KW_I2C_IRQ_STOP, state: state_write (isr: 04)
KW: wrong state. Got KW_I2C_IRQ_ADDR, state: state_stop (isr: 06)
KW: wrong state. Got KW_I2C_IRQ_ADDR, state: state_stop (isr: 06)
KW: wrong state. Got KW_I2C_IRQ_STOP, state: state_write (isr: 04)
KW: wrong state. Got KW_I2C_IRQ_ADDR, state: state_stop (isr: 06)
KW: wrong state. Got KW_I2C_IRQ_ADDR, state: state_stop (isr: 06)
KW: wrong state. Got KW_I2C_IRQ_STOP, state: state_write (isr: 04)
KW: wrong state. Got KW_I2C_IRQ_ADDR, state: state_stop (isr: 06)
KW: wrong state. Got KW_I2C_IRQ_ADDR, state: state_stop (isr: 06)
KW: wrong state. Got KW_I2C_IRQ_STOP, state: state_write (isr: 04)
KW: wrong state. Got KW_I2C_IRQ_ADDR, state: state_stop (isr: 06)
KW: wrong state. Got KW_I2C_IRQ_STOP, state: state_addr (isr: 04)
low_i2c: Keywest got an out of state interrupt, ignoring
low_i2c: Keywest got an out of state interrupt, ignoring
low_i2c: Keywest got an out of state interrupt, ignoring
KW: wrong state. Got KW_I2C_IRQ_ADDR, state: state_stop (isr: 06)
KW: wrong state. Got KW_I2C_IRQ_STOP, state: state_write (isr: 04)
KW: wrong state. Got KW_I2C_IRQ_ADDR, state: state_stop (isr: 06)
KW: wrong state. Got KW_I2C_IRQ_ADDR, state: state_stop (isr: 06)
KW: wrong state. Got KW_I2C_IRQ_STOP, state: state_write (isr: 04)
KW: wrong state. Got KW_I2C_IRQ_ADDR, state: state_stop (isr: 06)
KW: wrong state. Got KW_I2C_IRQ_ADDR, state: state_stop (isr: 06)
KW: wrong state. Got KW_I2C_IRQ_STOP, state: state_write (isr: 04)
KW: wrong state. Got KW_I2C_IRQ_ADDR, state: state_stop (isr: 06)
KW: wrong state. Got KW_I2C_IRQ_ADDR, state: state_stop (isr: 06)
KW: wrong state. Got KW_I2C_IRQ_STOP, state: state_write (isr: 04)
KW: wrong state. Got KW_I2C_IRQ_ADDR, state: state_stop (isr: 06)
KW: wrong state. Got KW_I2C_IRQ_ADDR, state: state_stop (isr: 06)
KW: wrong state. Got KW_I2C_IRQ_STOP, state: state_write (isr: 04)
KW: wrong state. Got KW_I2C_IRQ_ADDR, state: state_stop (isr: 06)
KW: wrong state. Got KW_I2C_IRQ_ADDR, state: state_stop (isr: 06)
KW: wrong state. Got KW_I2C_IRQ_STOP, state: state_write (isr: 04)
KW: wrong state. Got KW_I2C_IRQ_ADDR, state: state_stop (isr: 06)
KW: wrong state. Got KW_I2C_IRQ_ADDR, state: state_stop (isr: 06)
KW: wrong state. Got KW_I2C_IRQ_STOP, state: state_write (isr: 04)
KW: wrong state. Got KW_I2C_IRQ_ADDR, state: state_stop (isr: 06)
KW: wrong state. Got KW_I2C_IRQ_ADDR, state: state_stop (isr: 06)
KW: wrong state. Got KW_I2C_IRQ_STOP, state: state_write (isr: 04)
KW: wrong state. Got KW_I2C_IRQ_ADDR, state: state_stop (isr: 06)
KW: wrong state. Got KW_I2C_IRQ_ADDR, state: state_stop (isr: 06)
KW: wrong state. Got KW_I2C_IRQ_STOP, state: state_write (isr: 04)
KW: wrong state. Got KW_I2C_IRQ_ADDR, state: state_stop (isr: 06)
KW: wrong state. Got KW_I2C_IRQ_ADDR, state: state_stop (isr: 06)
KW: wrong state. Got KW_I2C_IRQ_STOP, state: state_write (isr: 04)
KW: wrong state. Got KW_I2C_IRQ_ADDR, state: state_stop (isr: 06)
KW: wrong state. Got KW_I2C_IRQ_ADDR, state: state_stop (isr: 06)
KW: wrong state. Got KW_I2C_IRQ_STOP, state: state_write (isr: 04)
KW: wrong state. Got KW_I2C_IRQ_ADDR, state: state_stop (isr: 06)
KW: wrong state. Got KW_I2C_IRQ_ADDR, state: state_stop (isr: 06)
KW: wrong state. Got KW_I2C_IRQ_STOP, state: state_write (isr: 04)
KW: wrong state. Got KW_I2C_IRQ_ADDR, state: state_stop (isr: 06)
KW: wrong state. Got KW_I2C_IRQ_ADDR, state: state_stop (isr: 06)
KW: wrong state. Got KW_I2C_IRQ_STOP, state: state_write (isr: 04)
KW: wrong state. Got KW_I2C_IRQ_ADDR, state: state_stop (isr: 06)
KW: wrong state. Got KW_I2C_IRQ_ADDR, state: state_stop (isr: 06)
KW: wrong state. Got KW_I2C_IRQ_STOP, state: state_write (isr: 04)
KW: wrong state. Got KW_I2C_IRQ_ADDR, state: state_stop (isr: 06)
KW: wrong state. Got KW_I2C_IRQ_ADDR, state: state_stop (isr: 06)
KW: wrong state. Got KW_I2C_IRQ_STOP, state: state_write (isr: 04)
KW: wrong state. Got KW_I2C_IRQ_ADDR, state: state_stop (isr: 06)
KW: wrong state. Got KW_I2C_IRQ_ADDR, state: state_stop (isr: 06)
KW: wrong state. Got KW_I2C_IRQ_STOP, state: state_write (isr: 04)
KW: wrong state. Got KW_I2C_IRQ_ADDR, state: state_stop (isr: 06)
KW: wrong state. Got KW_I2C_IRQ_ADDR, state: state_stop (isr: 06)
KW: wrong state. Got KW_I2C_IRQ_STOP, state: state_write (isr: 04)
KW: wrong state. Got KW_I2C_IRQ_ADDR, state: state_stop (isr: 06)
KW: wrong state. Got KW_I2C_IRQ_ADDR, state: state_stop (isr: 06)
KW: wrong state. Got KW_I2C_IRQ_STOP, state: state_write (isr: 04)
KW: wrong state. Got KW_I2C_IRQ_ADDR, state: state_stop (isr: 06)
KW: wrong state. Got KW_I2C_IRQ_ADDR, state: state_stop (isr: 06)
KW: wrong state. Got KW_I2C_IRQ_STOP, state: state_write (isr: 04)
KW: wrong state. Got KW_I2C_IRQ_ADDR, state: state_stop (isr: 06)
KW: wrong state. Got KW_I2C_IRQ_ADDR, state: state_stop (isr: 06)
KW: wrong state. Got KW_I2C_IRQ_STOP, state: state_write (isr: 04)
KW: wrong state. Got KW_I2C_IRQ_ADDR, state: state_stop (isr: 06)
KW: wrong state. Got KW_I2C_IRQ_ADDR, state: state_stop (isr: 06)
KW: wrong state. Got KW_I2C_IRQ_STOP, state: state_write (isr: 04)
KW: wrong state. Got KW_I2C_IRQ_ADDR, state: state_stop (isr: 06)
KW: wrong state. Got KW_I2C_IRQ_ADDR, state: state_stop (isr: 06)
KW: wrong state. Got KW_I2C_IRQ_STOP, state: state_write (isr: 04)
KW: wrong state. Got KW_I2C_IRQ_ADDR, state: state_stop (isr: 06)
KW: wrong state. Got KW_I2C_IRQ_ADDR, state: state_stop (isr: 06)
KW: wrong state. Got KW_I2C_IRQ_STOP, state: state_write (isr: 04)
KW: wrong state. Got KW_I2C_IRQ_ADDR, state: state_stop (isr: 06)
KW: wrong state. Got KW_I2C_IRQ_ADDR, state: state_stop (isr: 06)
KW: wrong state. Got KW_I2C_IRQ_STOP, state: state_write (isr: 04)
KW: wrong state. Got KW_I2C_IRQ_ADDR, state: state_stop (isr: 06)
KW: wrong state. Got KW_I2C_IRQ_ADDR, state: state_stop (isr: 06)
KW: wrong state. Got KW_I2C_IRQ_STOP, state: state_write (isr: 04)
KW: wrong state. Got KW_I2C_IRQ_ADDR, state: state_stop (isr: 06)
KW: wrong state. Got KW_I2C_IRQ_ADDR, state: state_stop (isr: 06)
Failure writing address to FCU: -5<7>KW: wrong state. Got KW_I2C_IRQ_STOP, state: state_write (isr: 04)
Error -6 reading backside fan !
Error -6 reading backside fan !
Error -6 reading backside fan !
Error -6 reading backside fan !
Error -6 reading backside fan !
Error -6 reading backside fan !
Error -6 reading backside fan !
Error -6 reading backside fan !
Error -6 reading backside fan !
Error -6 reading backside fan !
Error -6 reading backside fan !
Error -6 reading backside fan !
Error -6 reading backside fan !
Error -6 reading backside fan !
Error -6 reading backside fan !
Error -6 reading backside fan !

----- End forwarded message -----

^ permalink raw reply

* fix NULL pointer in handle_eeh_events
From: Olaf Hering @ 2006-02-27 14:52 UTC (permalink / raw)
  To: Linas Vepstas, linuxppc-dev


This patch fixes a crash in handle_eeh_events,
but ethtool -t still doesnt work right.

...
pepino:~ # cpu 0x3: Vector: 300 (Data Access) at [c00000005192bbe0]
    pc: c00000000004a380: .handle_eeh_events+0xe0/0x23c
    lr: c00000000004a374: .handle_eeh_events+0xd4/0x23c
    sp: c00000005192be60
   msr: 9000000000009032
   dar: 268
 dsisr: 40000000
  current = 0xc0000001fe7bf1a0
  paca    = 0xc00000000048b280
    pid   = 16322, comm = eehd
enter ? for help
[c00000005192bf00] c00000000004a808 .eeh_event_handler+0xcc/0x130
[c00000005192bf90] c000000000025e00 .kernel_thread+0x4c/0x68

...

(none):/# /usr/sbin/ethtool -i eth0
driver: e100
version: 3.5.10-k2-NAPI
firmware-version: N/A
bus-info: 0000:21:01.0
(none):/# /usr/sbin/ethtool -t eth0
Call Trace:
[C00000000F8DEFF0] [C00000000000F270] .show_stack+0x74/0x1b4 (unreliable)
[C00000000F8DF0A0] [C000000000049D04] .eeh_dn_check_failure+0x290/0x2d8
[C00000000F8DF150] [C000000000049E58] .eeh_check_failure+0x10c/0x138
[C00000000F8DF1E0] [C0000000002DFDB0] .e100_hw_reset+0x70/0xf4
[C00000000F8DF270] [C0000000002E1BBC] .e100_hw_init+0x2c/0x260
[C00000000F8DF310] [C0000000002E2464] .e100_loopback_test+0x8c/0x220
[C00000000F8DF3C0] [C0000000002E28DC] .e100_diag_test+0xdc/0x16c
[C00000000F8DF490] [C000000000420BE0] .dev_ethtool+0xf24/0x14f8
[C00000000F8DF8F0] [C00000000041F4A8] .dev_ioctl+0x5cc/0x740
[C00000000F8DFA20] [C00000000040FEFC] .sock_ioctl+0x3d0/0x404
[C00000000F8DFAC0] [C0000000000D513C] .do_ioctl+0x68/0x108
[C00000000F8DFB50] [C0000000000D56B0] .vfs_ioctl+0x4d4/0x510
[C00000000F8DFC10] [C0000000000D5740] .sys_ioctl+0x54/0x94
[C00000000F8DFCC0] [C0000000000FB6EC] .ethtool_ioctl+0x11c/0x150
[C00000000F8DFD60] [C0000000000F7E40] .compat_sys_ioctl+0x338/0x3bc
[C00000000F8DFE30] [C00000000000871C] syscall_exit+0x0/0x40
EEH: Detected PCI bus error on device 0000:21:01.0
EEH: This PCI device has failed 1 times since last reboot: <NULL> -

modprobe: FATAL: Could not load /lib/modules/2.6.16-rc4-git7/modules.dep: No such file or directory

Cannot get strings: No such device
(none):/#
(none):/# EEH: Unable to configure device bridge (-3) for /pci@400000000110/pci@2,2

(none):/# Call Trace:
[C00000000FA17940] [C00000000000F270] .show_stack+0x74/0x1b4 (unreliable)
[C00000000FA179F0] [C000000000049D04] .eeh_dn_check_failure+0x290/0x2d8
[C00000000FA17AA0] [C00000000001E114] .rtas_read_config+0x120/0x154
[C00000000FA17B40] [C000000000049664] .early_enable_eeh+0x274/0x2bc
[C00000000FA17C00] [C000000000049708] .eeh_add_device_early+0x5c/0x6c
[C00000000FA17C90] [C000000000049748] .eeh_add_device_tree_early+0x30/0x5c
[C00000000FA17D20] [C000000000046568] .pcibios_add_pci_devices+0x8c/0x1f8
[C00000000FA17DD0] [C00000000004A528] .eeh_reset_device+0xe0/0x110
[C00000000FA17E60] [C00000000004A698] .handle_eeh_events+0x140/0x250
[C00000000FA17F00] [C00000000004AC7C] .eeh_event_handler+0xe8/0x140
[C00000000FA17F90] [C000000000025784] .kernel_thread+0x4c/0x68
EEH: Detected PCI bus error on device <NULL>
EEH: This PCI device has failed 1 times since last reboot: <NULL> -
EEH: Unable to configure device bridge (-3) for /pci@400000000110/pci@2,2
Call Trace:
[C00000000FA17940] [C00000000000F270] .show_stack+0x74/0x1b4 (unreliable)
[C00000000FA179F0] [C000000000049D04] .eeh_dn_check_failure+0x290/0x2d8
[C00000000FA17AA0] [C00000000001E114] .rtas_read_config+0x120/0x154
[C00000000FA17B40] [C000000000049664] .early_enable_eeh+0x274/0x2bc
[C00000000FA17C00] [C000000000049708] .eeh_add_device_early+0x5c/0x6c
[C00000000FA17C90] [C000000000049748] .eeh_add_device_tree_early+0x30/0x5c
[C00000000FA17D20] [C000000000046568] .pcibios_add_pci_devices+0x8c/0x1f8
[C00000000FA17DD0] [C00000000004A528] .eeh_reset_device+0xe0/0x110
[C00000000FA17E60] [C00000000004A698] .handle_eeh_events+0x140/0x250
[C00000000FA17F00] [C00000000004AC7C] .eeh_event_handler+0xe8/0x140
[C00000000FA17F90] [C000000000025784] .kernel_thread+0x4c/0x68
EEH: Detected PCI bus error on device <NULL>
EEH: This PCI device has failed 1 times since last reboot: <NULL> -
EEH: Unable to configure device bridge (-3) for /pci@400000000110/pci@2,2
Call Trace:
[C00000000FA17940] [C00000000000F270] .show_stack+0x74/0x1b4 (unreliable)
[C00000000FA179F0] [C000000000049D04] .eeh_dn_check_failure+0x290/0x2d8
[C00000000FA17AA0] [C00000000001E114] .rtas_read_config+0x120/0x154
[C00000000FA17B40] [C000000000049664] .early_enable_eeh+0x274/0x2bc
[C00000000FA17C00] [C000000000049708] .eeh_add_device_early+0x5c/0x6c
[C00000000FA17C90] [C000000000049748] .eeh_add_device_tree_early+0x30/0x5c
[C00000000FA17D20] [C000000000046568] .pcibios_add_pci_devices+0x8c/0x1f8
[C00000000FA17DD0] [C00000000004A528] .eeh_reset_device+0xe0/0x110
[C00000000FA17E60] [C00000000004A698] .handle_eeh_events+0x140/0x250
[C00000000FA17F00] [C00000000004AC7C] .eeh_event_handler+0xe8/0x140
[C00000000FA17F90] [C000000000025784] .kernel_thread+0x4c/0x68
EEH: Detected PCI bus error on device <NULL>
and so on


Signed-off-by: Olaf Hering <olh@suse.de>

 arch/powerpc/platforms/pseries/eeh_driver.c |    2 +-
 1 files changed, 1 insertion(+), 1 deletion(-)

Index: linux-2.6.16-rc5-olh/arch/powerpc/platforms/pseries/eeh_driver.c
===================================================================
--- linux-2.6.16-rc5-olh.orig/arch/powerpc/platforms/pseries/eeh_driver.c
+++ linux-2.6.16-rc5-olh/arch/powerpc/platforms/pseries/eeh_driver.c
@@ -37,7 +37,7 @@
 
 static inline const char * pcid_name (struct pci_dev *pdev)
 {
-	if (pdev->dev.driver)
+	if (pdev && pdev->dev.driver)
 		return pdev->dev.driver->name;
 	return "";
 }

^ permalink raw reply

* RE: Gianfar is slower  than fcc_enet on MPC8541 ???
From: Laurent Lagrange @ 2006-02-27 10:03 UTC (permalink / raw)
  To: 'Andy Fleming'; +Cc: linuxppc-embedded
In-Reply-To: <9A05AF34-3A14-4D64-9EDF-81D7C3C315FE@freescale.com>

Hello Andy,

> The answer there is simple: stupidity!
The word is too hard, just say forgetting  :-)

Thanks again
Laurent

> -----Message d'origine-----
> De : Andy Fleming [mailto:afleming@freescale.com]
> Envoye : jeu. 23 fevrier 2006 21:08
> A : Laurent Lagrange
> Cc : linuxppc-embedded@ozlabs.org; vbordug@ru.mvista.com;
> pantelis.antoniou@gmail.com
> Objet : Re: Gianfar is slower than fcc_enet on MPC8541 ???
> 
> 
> 
> On Feb 23, 2006, at 11:28, Laurent Lagrange wrote:
> 
> > Hi everybody,
> >
> > I tried the below Andy's idea. It works fine.
> > It is my TCP clients which now slow the traffic.
> >
> > But I don't know why the default timeouts are so high.
> > If the traffic is high, the timeout does not fire.
> > If the traffic is low, the timeout seems too long (???).
> 
> The answer there is simple: stupidity!  :)  I just didn't carefully  
> test the values for performance when I chose them.  I probably also  
> did the math wrong, because I was more concerned about seeing if it  
> worked at all.  It's also possible it got set that way to see a  
> measurable difference to prove it was working, and then got left as  
> the default.  Rest assured, there was not a deliberate reason.  We  
> submitted a patch once this performance issue was discovered.
> 
> 
> 
> 
> 

^ permalink raw reply

* unsubscribe
From: shrisha.prasad @ 2006-02-27  4:10 UTC (permalink / raw)
  To: Linuxppc-dev

[-- Attachment #1: Type: text/plain, Size: 0 bytes --]



[-- Attachment #2: Type: text/html, Size: 0 bytes --]

^ permalink raw reply

* Re: [PATCH] powerpc: Fix mem= cmdline handling on arch/powerpc for !MULTIPLATFORM
From: Dave Hansen @ 2006-02-26 20:38 UTC (permalink / raw)
  To: Kumar Gala; +Cc: linuxppc-dev, Linus Torvalds, linux-kernel
In-Reply-To: <Pine.LNX.4.44.0602241054090.2981-100000@gate.crashing.org>

On Fri, 2006-02-24 at 10:54 -0600, Kumar Gala wrote:
> +       if (strstr(cmd_line, "mem=")) {
> +               char *p, *q;
> +               unsigned long maxmem = 0;
> +
> +               for (q = cmd_line; (p = strstr(q, "mem=")) != 0; ) {
> +                       q = p + 4;
> +                       if (p > cmd_line && p[-1] != ' ')
> +                               continue;
> +                       maxmem = simple_strtoul(q, &q, 0);
> +                       if (*q == 'k' || *q == 'K') {
> +                               maxmem <<= 10;
> +                               ++q;
> +                       } else if (*q == 'm' || *q == 'M') {
> +                               maxmem <<= 20;
> +                               ++q;
> +                       } else if (*q == 'g' || *q == 'G') {
> +                               maxmem <<= 30;
> +                               ++q;
> +                       }
> +               }
> +               memory_limit = maxmem;
> +       } 

You may want to check out lib/cmdline.c's memparse() function.  I think
it does this for you.

-- Dave

^ permalink raw reply

* Re: [Alsa-devel] Re: [PPC,SOUND] Fix audio gpio state detection
From: Lee Revell @ 2006-02-26 19:19 UTC (permalink / raw)
  To: Olaf Hering; +Cc: linuxppc-dev, alsa-devel, Ben Collins
In-Reply-To: <20060226173908.GA4871@suse.de>

On Sun, 2006-02-26 at 18:39 +0100, Olaf Hering wrote:
> /proc/device-tree/pci@f2000000/mac-io@17/gpio@50:
> linux,device     cfdc7808
> name             "gpio"
> linux,phandle    ff90fcd0
> reg              00000050 00000030
> built-in        
> device_type      "gpio"
> 

Argh, /proc abuse... "historical reasons" presumably?

Lee

^ permalink raw reply

* Re: [Alsa-devel] Re: [PPC,SOUND] Fix audio gpio state detection
From: Olaf Hering @ 2006-02-26 19:26 UTC (permalink / raw)
  To: Lee Revell; +Cc: linuxppc-dev, alsa-devel, Ben Collins
In-Reply-To: <1140981558.24141.112.camel@mindpipe>

 On Sun, Feb 26, Lee Revell wrote:

> Argh, /proc abuse... "historical reasons" presumably?

No, the way it works.

^ permalink raw reply

* Re: [PPC,SOUND] Fix audio gpio state detection
From: Olaf Hering @ 2006-02-26 17:39 UTC (permalink / raw)
  To: Benjamin Herrenschmidt; +Cc: alsa-devel, Ben Collins, linuxppc-dev
In-Reply-To: <1139783738.5247.54.camel@localhost.localdomain>

 On Mon, Feb 13, Benjamin Herrenschmidt wrote:

> On Sat, 2006-02-11 at 17:10 +0100, Andreas Schwab wrote:
> > When booting with line out or headphone plugged, you won't hear anything.
> > The problem is that after reset all channels are muted, but the actual
> > value of the gpio port doesn't exactly match the active_val settings as
> > expected by check_audio_gpio.  For example, the line_mute port is set to
> > 7, but check_audio_gpio would expect 0xd or 0xf, thus its return value
> > indicates that it is not active, even though it is.  AFAICS only looking
> > at the low bit is enough to determine whether the port is active.
> > 
> > Signed-off-by: Andreas Schwab <schwab@suse.de>
> > 
> > Index: linux-2.6.16-rc2/sound/ppc/tumbler.c
> > ===================================================================
> > --- linux-2.6.16-rc2.orig/sound/ppc/tumbler.c	2006-02-03 19:43:50.000000000 +0100
> > +++ linux-2.6.16-rc2/sound/ppc/tumbler.c	2006-02-11 03:46:30.000000000 +0100
> > @@ -207,7 +207,7 @@ static int check_audio_gpio(struct pmac_
> >  
> >  	ret = do_gpio_read(gp);
> >  
> > -	return (ret & 0xd) == (gp->active_val & 0xd);
> > +	return (ret & 0x1) == (gp->active_val & 0x1);
> >  }
> >  
> >  static int read_audio_gpio(struct pmac_gpio *gp)

This (sort of) breaks PowerMac3,4 (69 (PowerMac G4 Silver)). I have to
force it on up to now, but with this patch the internal speaker will not
work with or without my patch to force it on.

I get these values:

check_audio_gpio gp c040fc14 addr 0000006f ret 00000007
check_audio_gpio gp c040fbfc addr 00000070 ret 00000004

With speakers plugged in, both give 0x07

/proc/device-tree/pci@f2000000/mac-io@17/gpio@50:
linux,device     cfdc7808
name             "gpio"
linux,phandle    ff90fcd0
reg              00000050 00000030
built-in        
device_type      "gpio"

/proc/device-tree/pci@f2000000/mac-io@17/gpio@50/extint-gpio16:
name             "extint-gpio16"
linux,phandle    ff910a00
interrupt-parent ff90fa80
interrupts       0000003e 00000000
AAPL,address     80000068
built-in        
one-wire-bus     "speaker-id"
AAPL,driver-name ".DallasDriver"
compatible       "keywest-gpio16"
device_type      "extint-gpio16"

/proc/device-tree/pci@f2000000/mac-io@17/gpio@50/extint-gpio15:
name             "extint-gpio15"
linux,phandle    ff9107f8
interrupt-parent ff90fa80
interrupts       0000003d 00000000
AAPL,address     80000067
built-in        
compatible       "keywest-gpio15"
device_type      "extint-gpio15"

/proc/device-tree/pci@f2000000/mac-io@17/gpio@50/gpio11:
name             "gpio11"
linux,phandle    ff9105f8
AAPL,address     80000075
built-in        
audio-gpio-active-state 00000000
audio-gpio       "audio-hw-reset"
compatible       "keywest-11"
device_type      "gpio11"

/proc/device-tree/pci@f2000000/mac-io@17/gpio@50/gpio6:
name             "gpio6"
linux,phandle    ff910400
AAPL,address     80000070
built-in        
audio-gpio-active-state 00000000
audio-gpio       "amp-mute"
compatible       "keywest-6"
device_type      "gpio6"

/proc/device-tree/pci@f2000000/mac-io@17/gpio@50/gpio5:
name             "gpio5"
linux,phandle    ff910208
AAPL,address     8000006f
built-in        
audio-gpio-active-state 00000000
audio-gpio       "headphone-mute"
compatible       "keywest-5"
device_type      "gpio5"

/proc/device-tree/pci@f2000000/mac-io@17/gpio@50/programmer-switch:
name             "programmer-switch"
linux,phandle    ff910058
interrupt-parent ff90fa80
interrupts       00000037 00000000
built-in        
device_type      "programmer-switch"

/proc/device-tree/pci@f2000000/mac-io@17/gpio@50/extint-gpio1:
name             "extint-gpio1"
linux,phandle    ff90fe38
AAPL,interrupt-priorities 00000001
interrupt-parent ff90fa80
interrupts       0000002f 00000001
built-in        
compatible       "keywest-gpio1"
device_type      "extint-gpio1"

^ permalink raw reply

* Re: [PATCH] ppc32: handle Book E debug exceptions on kernel stack
From: Paul Mackerras @ 2006-02-26  2:42 UTC (permalink / raw)
  To: Dale Farnsworth; +Cc: linuxppc-embedded, David Gibson
In-Reply-To: <20060224185251.GA9084@xyzzy.farnsworth.org>

Dale Farnsworth writes:

> There's a race between a critical exception and the normal exception
> entry path.  If a normal exception occurs in user mode and then a
> critical exception occurs before the normal exception handler has set
> r1 to the kernel stack area, we end up with r1 containing the user sp,
> though the critical exception occurred in kernel mode.

That's a separate problem from what we were discussing, which is why
program_check_exception is entered with interrupts disabled.

> I haven't yet come up with a way to detect this case and reliably use
> the kernel stack on a critical exception.

One way to solve this is to put the kernel stack pointer in some SPRGn
when exiting to usermode, and on critical exceptions, use that SPRGn
for the kernel stack if it is non-zero.  In the exception entry path
(for both normal and critical exceptions) put 0 in it once r1 has been
set up with a valid kernel stack pointer.  This also works if you have
to call firmware such as RTAS which runs in kernel mode but may put
arbitrary values in r1.

Paul.

^ permalink raw reply

* Re: [PATCH] processes stuck forever in __do_get_xsec
From: Benjamin Herrenschmidt @ 2006-02-25 21:09 UTC (permalink / raw)
  To: Olaf Hering; +Cc: linuxppc-dev
In-Reply-To: <20060225102730.GA17550@suse.de>

On Sat, 2006-02-25 at 11:27 +0100, Olaf Hering wrote:
> 64bit processes loop forever in __do_get_xsec, r8 is loaded, but r4 is compared.
> Also, gdb doesnt understand __do_get_xsec and __get_datapage.
> 
> No idea if my change is correct.

Good catch ! I send a better patch for it.

Ben.

^ permalink raw reply

* [PATCH] powerpc: vdso 64bits gettimeofday bug
From: Benjamin Herrenschmidt @ 2006-02-25 21:09 UTC (permalink / raw)
  To: Andrew Morton, Linus Torvalds
  Cc: Greg KH, linuxppc-dev list, Olaf Hering, linuxppc64-dev,
	David Woodhouse

A bug in the assembly code of the vdso can cause gettimeofday() to hang
or to return incorrect results. The wrong register was used to test for
pending updates of the calibration variables and to create a dependency
for subsequent loads. This fixes it.

Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
---

Might be worth applying to the stable series too and/or distro kernels
2.6.15 and later

--- linux-work.orig/arch/powerpc/kernel/vdso64/gettimeofday.S	2006-02-26 08:02:57.000000000 +1100
+++ linux-work/arch/powerpc/kernel/vdso64/gettimeofday.S	2006-02-26 08:04:23.000000000 +1100
@@ -225,9 +225,9 @@
   .cfi_startproc
 	/* check for update count & load values */
 1:	ld	r8,CFG_TB_UPDATE_COUNT(r3)
-	andi.	r0,r4,1			/* pending update ? loop */
+	andi.	r0,r8,1			/* pending update ? loop */
 	bne-	1b
-	xor	r0,r4,r4		/* create dependency */
+	xor	r0,r8,r8		/* create dependency */
 	add	r3,r3,r0
 
 	/* Get TB & offset it */

^ permalink raw reply


This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox