Re: PowerPC 85xx board are caused die by Commit: 864b9e6fd76489aab422bac62162f57c52e06ed8(powerpc: Use lwarx/ldarx hint in bit locks)

2010-03-11 Thread Andrew Liu
Just validated it, this fix can make fsl_p2020ds work again.

Andrew

On Thu, Mar 11, 2010 at 1:39 PM, Kumar Gala wrote:

>
> On Mar 10, 2010, at 11:20 PM, Kumar Gala wrote:
>
> >
> > On Mar 10, 2010, at 9:20 PM, Andrew Liu wrote:
> >
> >> Hi Guys:
> >> I have done several experiments on  fsl_8548cds and fsl_p2020rdb,
> pinpointed the commit: 864b9e6fd76489aab422bac62162f57c52e06ed8(powerpc: Use
> lwarx/ldarx hint in bit locks)  cause the bootup stalledd.
> >>
> >> "
> >> Filename 'fsl_8548cds/uImage'.
> >> Load address: 0x100
> >> Loading:
> #
> >> ###
> >> done
> >> Bytes transferred = 1526546 (174b12 hex)
> >> Speed: 100, full duplex
> >> Using eTSEC0 device
> >> Filename 'sliu/fsl_8548cds/mpc8548cds.dtb'.
> >> Load address: 0xc0
> >> Loading: #
> >> done
> >> Bytes transferred = 9993 (2709 hex)
> >> ## Booting image at 0100 ...
> >>   Image Name:   Linux-2.6.34-rc1-5-g522dba7
> >>   Image Type:   PowerPC Linux Kernel Image (gzip compressed)
> >>   Data Size:1526482 Bytes =  1.5 MB
> >>   Load Address: 
> >>   Entry Point:  
> >>   Verifying Checksum ... OK
> >>   Uncompressing Kernel Image ... OK
> >>   Booting using the fdt at 0xc0
> >>   Loading Device Tree to 007fb000, end 007fd708 ... OK
> >> "
> >>
> >> I guess all 85xx or booke board has this issue.
> >
> > that's very odd since __PPC_EH should be ignored on PPC32 and thus 85xx.
>
> Found the issue and posted a fix.
>
> - k
___
Linuxppc-dev mailing list
Linuxppc-dev@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/linuxppc-dev

PowerPC 85xx board are caused die by Commit: 864b9e6fd76489aab422bac62162f57c52e06ed8(powerpc: Use lwarx/ldarx hint in bit locks)

2010-03-10 Thread Andrew Liu
Hi Guys:
I have done several experiments on  fsl_8548cds and fsl_p2020rdb, pinpointed
the commit: 864b9e6fd76489aab422bac62162f57c52e06ed8(powerpc: Use
lwarx/ldarx hint in bit locks)  cause the bootup stalledd.

"
Filename 'fsl_8548cds/uImage'.
Load address: 0x100
Loading: #
 ###
done
Bytes transferred = 1526546 (174b12 hex)
Speed: 100, full duplex
Using eTSEC0 device
Filename 'sliu/fsl_8548cds/mpc8548cds.dtb'.
Load address: 0xc0
Loading: #
done
Bytes transferred = 9993 (2709 hex)
## Booting image at 0100 ...
   Image Name:   Linux-2.6.34-rc1-5-g522dba7
   Image Type:   PowerPC Linux Kernel Image (gzip compressed)
   Data Size:1526482 Bytes =  1.5 MB
   Load Address: 
   Entry Point:  
   Verifying Checksum ... OK
   Uncompressing Kernel Image ... OK
   Booting using the fdt at 0xc0
   Loading Device Tree to 007fb000, end 007fd708 ... OK
"

I guess all 85xx or booke board has this issue.

Thanks
Andrew
___
Linuxppc-dev mailing list
Linuxppc-dev@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/linuxppc-dev

Re: [PATCH] [POWERPC] Uniformly use memstart_addr variable as the start address of physical memory in powerpc branch

2008-05-20 Thread Andrew Liu


Kumar Gala wrote:


On May 20, 2008, at 8:38 PM, Andrew Liu wrote:


[POWERPC]: Uniformly use memstart_addr as the start address of RAM

The variable: memstart_addr whose initial value is got from dts file
is used as the start address of physical memory in PowerPC ARCH,
although it is used in functions: mapin_ram(pgtable_32.c) and
cam_mapin_ram(fsl_booke_mmu.c), however, in function: mmu_mapin_ram
(ppc_mmu_32.c), use 0 as the start address of physical memory, so
it is necessary to unify them: in mmu_mapin_ram, use memstart_addr
as the start address of physical memory, instead of 0.

Signed-off-by: Andrew Liu <[EMAIL PROTECTED]>
---


Do you have a case where this is non-zero for ppc_mmu_32?  I left these 
alone because I wasn't aware of one (or if its reasonable).




No.
I submitted this patch just because in ppc branch, PPC_MEMSTART is used as 
the start address of physical memory uniformly, however, in powerpc branch, 
use memstart_addr and 0, although, almost for all boards which are in powerpc,

they are equal, from the aspect of code consistency, I think it is necessary to
unify them.

You know we can't make sure in future the start address of all incoming 
boards' RAM is 0, especially, in AMP system, different cpu uses the different RAM area, 
definitely, the start address of some is not 0.


BRs,
Andrew



- k



___
Linuxppc-dev mailing list
Linuxppc-dev@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-dev


[PATCH] [POWERPC] Uniformly use memstart_addr variable as the start address of physical memory in powerpc branch

2008-05-20 Thread Andrew Liu

[POWERPC]: Uniformly use memstart_addr as the start address of RAM

The variable: memstart_addr whose initial value is got from dts file
is used as the start address of physical memory in PowerPC ARCH,
although it is used in functions: mapin_ram(pgtable_32.c) and
cam_mapin_ram(fsl_booke_mmu.c), however, in function: mmu_mapin_ram
(ppc_mmu_32.c), use 0 as the start address of physical memory, so
it is necessary to unify them: in mmu_mapin_ram, use memstart_addr
as the start address of physical memory, instead of 0.

Signed-off-by: Andrew Liu <[EMAIL PROTECTED]>
---

b/arch/powerpc/mm/ppc_mmu_32.c |4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)


diff --git a/arch/powerpc/mm/ppc_mmu_32.c b/arch/powerpc/mm/ppc_mmu_32.c
index cef9f15..f133c6e 100644
--- a/arch/powerpc/mm/ppc_mmu_32.c
+++ b/arch/powerpc/mm/ppc_mmu_32.c
@@ -98,7 +98,7 @@ unsigned long __init mmu_mapin_ram(void)
break;
}

-   setbat(2, KERNELBASE, 0, bl, _PAGE_RAM);
+   setbat(2, KERNELBASE, memstart_addr, bl, _PAGE_RAM);
done = (unsigned long)bat_addrs[2].limit - KERNELBASE + 1;
if ((done < tot) && !bat_addrs[3].limit) {
/* use BAT3 to cover a bit more */
@@ -106,7 +106,7 @@ unsigned long __init mmu_mapin_ram(void)
for (bl = 128<<10; bl < max_size; bl <<= 1)
if (bl * 2 > tot)
break;
-   setbat(3, KERNELBASE+done, done, bl, _PAGE_RAM);
+   setbat(3, KERNELBASE+done, memstart_addr+done, bl, _PAGE_RAM);
done = (unsigned long)bat_addrs[3].limit - KERNELBASE + 1;
}

___
Linuxppc-dev mailing list
Linuxppc-dev@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-dev


[PATCH] Fix a potential issue in mpc52xx uart driver

2008-04-29 Thread Andrew Liu

mpc52xx_uart_int and __uart_put_char both try to acquire the
port->lock. Therefore the function sequence of:

mpc52xx_uart_int--> ...-->flush_to_ldisc-->...-->__uart_put_char

can potentially trigger a deadlock. To avoid this deadlock a fix
similar to that found in the 8250.c serial driver is applied. The
deadlock is avoided by releasing the lock before pushing a buffer
and reacquiring it when completed.

Signed-off-by: Andrew Liu <[EMAIL PROTECTED]>

diff --git a/drivers/serial/mpc52xx_uart.c b/drivers/serial/mpc52xx_uart.c
index d93b357..5f95e53 100644
--- a/drivers/serial/mpc52xx_uart.c
+++ b/drivers/serial/mpc52xx_uart.c
@@ -783,7 +783,9 @@ mpc52xx_uart_int_rx_chars(struct uart_port *port)
}
}

+   spin_unlock(&port->lock);
tty_flip_buffer_push(tty);
+   spin_lock(&port->lock);

return psc_ops->raw_rx_rdy(port);
 }
___
Linuxppc-dev mailing list
Linuxppc-dev@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-dev


Re: AMCC yosemite 440ep PCI slot doesn't work.

2007-09-24 Thread Andrew Liu
Currently, ppc44x use ppc branch, not powerpc, especially for AMCC
yosemite 440ep.

Through adding printk in function ppc4xx_pic_init which is in
arch/ppc/syslib/ppc4xx_pic.c, whether setting  IRQ_LEVEL has no effect
on it.



BRs,
Andrew


Valentine Barshak wrote:
> Stefan Roese wrote:
>> On Monday 24 September 2007, Andrew Liu wrote:
>>> By default, it is IRQ_SENSE_LEVEL | IRQ_POLARITY_NEGATIVE
>>
>> And that should be correct for PCI interrupts.
>>
>>>  I change it to IRQ_SENSE_EDGE | IRQ_POLARITY_NEGATIVE  or
>>> IRQ_SENSE_EDGE | IRQ_POLARITY_POSITIVE.
>>> It  displays:
>>> eth2: link up, 100Mbps, full-duplex, lpa 0x45E1
>>> eth2: no IPv6 routers present
>>> NETDEV WATCHDOG: eth2: transmit timed out
>>> eth2: Transmit timeout, status 0c 0005 c07f media 10.
>>> eth2: Tx queue start entry 4  dirty entry 0.
>>> eth2:  Tx descriptor 0 is 0008a05a. (queue head)
>>> eth2:  Tx descriptor 1 is 0008a04e.
>>> eth2:  Tx descriptor 2 is 0008a046.
>>> eth2:  Tx descriptor 3 is 0008a05a.
>>> eth2: link up, 100Mbps, full-duplex, lpa 0x45E1
>>>
>>> and
>>> [EMAIL PROTECTED]:/root> ifconfig  eth2
>>> eth2  Link encap:Ethernet  HWaddr 00:0E:2E:7E:F5:E6
>>>   inet addr:128.224.149.13  Bcast:128.224.255.255 
>>> Mask:255.255.0.0
>>>   inet6 addr: fe80::20e:2eff:fe7e:f5e6/64 Scope:Link
>>>   UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>>>   RX packets:0 errors:0 dropped:0 overruns:0 frame:0
>>>   TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
>>>   collisions:0 txqueuelen:1000
>>>   RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
>>>   Interrupt:25 Base address:0x6f00
>>>
>>>
>>> and
>>> [EMAIL PROTECTED]:/root> cat /proc/interrupts
>>>CPU0
>>>   2:  0  UIC0 Edge  IBM IIC
>>>   7:  0  UIC0 Edge  IBM IIC
>>>  10:  11961  UIC0 Edge  MAL TX EOB
>>>  11:  18471  UIC0 Edge  MAL RX EOB
>>>  25:  0  UIC0 Edge  eth2
>>>  32:  0  UIC1 Edge  MAL SERR
>>>  33:  0  UIC1 Edge  MAL TX DE
>>>  34:  0  UIC1 Edge  MAL RX DE
>>>  40: 32  UIC1 Edge  ohci_hcd:usb1
>>>  60:  0  UIC1 Edge  EMAC
>>> BAD:  0
>>>
>>>
>>> Can PCI slot use level trigger?
>>>
>>> give me some advice.
>
> This could be caused by misseting the IRQ_lEVEL flag in desc->status.
> There have been a commit 4dc7b4b0405fd7320940849b6e31ea8ea68fd0df that
> fixes the problem.
> Thanks,
> Valentine.
>
>>
>> Hmmm. Did you try an earlier Linux version too? For example 2.6.22 or
>> even earlier? Please give it a try and let us know if the same
>> problem occurs.
>>
>> Best regards,
>> Stefan
>>
>> =
>> DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
>> HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
>> Phone: +49-8142-66989-0 Fax: +49-8142-66989-80  Email: [EMAIL PROTECTED]
>> =
>
>
___
Linuxppc-dev mailing list
Linuxppc-dev@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-dev


Re: AMCC yosemite 440ep PCI slot doesn't work.

2007-09-24 Thread Andrew Liu
I have tested it on linux-2.6.19 which is from AMCC website ,  linux 
2.6.21.7 which is from linux mainline and  linux-2.6.23.rc7 which is
from git://www.denx.de/git/linux-2.6-denx.git
Have the same problem.
 I don't understand, why after enabling this PCI interrupts.  in so
short time, produce 100,000 interrupt request (25: 10  UIC0
Level eth2).


BRs,
Andrew.

Stefan Roese wrote:
> On Monday 24 September 2007, Andrew Liu wrote:
>   
>> By default, it is IRQ_SENSE_LEVEL | IRQ_POLARITY_NEGATIVE
>> 
>
> And that should be correct for PCI interrupts.
>
>   
>>  I change it to IRQ_SENSE_EDGE | IRQ_POLARITY_NEGATIVE  or
>> IRQ_SENSE_EDGE | IRQ_POLARITY_POSITIVE.
>> It  displays:
>> eth2: link up, 100Mbps, full-duplex, lpa 0x45E1
>> eth2: no IPv6 routers present
>> NETDEV WATCHDOG: eth2: transmit timed out
>> eth2: Transmit timeout, status 0c 0005 c07f media 10.
>> eth2: Tx queue start entry 4  dirty entry 0.
>> eth2:  Tx descriptor 0 is 0008a05a. (queue head)
>> eth2:  Tx descriptor 1 is 0008a04e.
>> eth2:  Tx descriptor 2 is 0008a046.
>> eth2:  Tx descriptor 3 is 0008a05a.
>> eth2: link up, 100Mbps, full-duplex, lpa 0x45E1
>>
>> and
>> [EMAIL PROTECTED]:/root> ifconfig  eth2
>> eth2  Link encap:Ethernet  HWaddr 00:0E:2E:7E:F5:E6
>>   inet addr:128.224.149.13  Bcast:128.224.255.255  Mask:255.255.0.0
>>   inet6 addr: fe80::20e:2eff:fe7e:f5e6/64 Scope:Link
>>   UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>>   RX packets:0 errors:0 dropped:0 overruns:0 frame:0
>>   TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
>>   collisions:0 txqueuelen:1000
>>   RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
>>   Interrupt:25 Base address:0x6f00
>>
>>
>> and
>> [EMAIL PROTECTED]:/root> cat /proc/interrupts
>>CPU0
>>   2:  0  UIC0 Edge  IBM IIC
>>   7:  0  UIC0 Edge  IBM IIC
>>  10:  11961  UIC0 Edge  MAL TX EOB
>>  11:  18471  UIC0 Edge  MAL RX EOB
>>  25:  0  UIC0 Edge  eth2
>>  32:  0  UIC1 Edge  MAL SERR
>>  33:  0  UIC1 Edge  MAL TX DE
>>  34:  0  UIC1 Edge  MAL RX DE
>>  40: 32  UIC1 Edge  ohci_hcd:usb1
>>  60:  0  UIC1 Edge  EMAC
>> BAD:  0
>>
>>
>> Can PCI slot use level trigger?
>>
>> give me some advice.
>> 
>
> Hmmm. Did you try an earlier Linux version too? For example 2.6.22 or even 
> earlier? Please give it a try and let us know if the same problem occurs.
>
> Best regards,
> Stefan
>
> =
> DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
> HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
> Phone: +49-8142-66989-0 Fax: +49-8142-66989-80  Email: [EMAIL PROTECTED]
> =
>
>   
___
Linuxppc-dev mailing list
Linuxppc-dev@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-dev


Re: AMCC yosemite 440ep PCI slot doesn't work.

2007-09-24 Thread Andrew Liu
By default, it is IRQ_SENSE_LEVEL | IRQ_POLARITY_NEGATIVE
 
 I change it to IRQ_SENSE_EDGE | IRQ_POLARITY_NEGATIVE  or
IRQ_SENSE_EDGE | IRQ_POLARITY_POSITIVE.
It  displays:
eth2: link up, 100Mbps, full-duplex, lpa 0x45E1
eth2: no IPv6 routers present
NETDEV WATCHDOG: eth2: transmit timed out
eth2: Transmit timeout, status 0c 0005 c07f media 10.
eth2: Tx queue start entry 4  dirty entry 0.
eth2:  Tx descriptor 0 is 0008a05a. (queue head)
eth2:  Tx descriptor 1 is 0008a04e.
eth2:  Tx descriptor 2 is 0008a046.
eth2:  Tx descriptor 3 is 0008a05a.
eth2: link up, 100Mbps, full-duplex, lpa 0x45E1

and
[EMAIL PROTECTED]:/root> ifconfig  eth2
eth2  Link encap:Ethernet  HWaddr 00:0E:2E:7E:F5:E6 
  inet addr:128.224.149.13  Bcast:128.224.255.255  Mask:255.255.0.0
  inet6 addr: fe80::20e:2eff:fe7e:f5e6/64 Scope:Link
  UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
  RX packets:0 errors:0 dropped:0 overruns:0 frame:0
  TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:1000
  RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
  Interrupt:25 Base address:0x6f00


and
[EMAIL PROTECTED]:/root> cat /proc/interrupts
   CPU0  
  2:  0  UIC0 Edge  IBM IIC
  7:  0  UIC0 Edge  IBM IIC
 10:  11961  UIC0 Edge  MAL TX EOB
 11:  18471  UIC0 Edge  MAL RX EOB
 25:  0  UIC0 Edge  eth2
 32:  0  UIC1 Edge  MAL SERR
 33:  0  UIC1 Edge  MAL TX DE
 34:  0  UIC1 Edge  MAL RX DE
 40: 32  UIC1 Edge  ohci_hcd:usb1
 60:  0  UIC1 Edge  EMAC
BAD:  0


Can PCI slot use level trigger?

give me some advice.

Thanks.

Valentine Barshak wrote:
> Andrew Liu wrote:
>> Hello All,
>>
>> when insert a  RealTek RTL8139 network card into PCI slot,
>> After system boot up,
>>
>> [EMAIL PROTECTED]:/root> ifconfig eth2 192.168.17.12
>> irq 25: nobody cared (try booting with the "irqpoll" option)
>> Call Trace:
>> [cf135af0] [c0008820] show_stack+0x48/0x190 (unreliable)
>> [cf135b20] [c003c414] __report_bad_irq+0x34/0xac
>> [cf135b40] [c003c714] note_interrupt+0x288/0x2c8
>> [cf135b70] [c003b818] __do_IRQ+0x104/0x110
>> [cf135b90] [c0006900] do_IRQ+0xbc/0xc0
>> [cf135ba0] [c00020c0] ret_from_except+0x0/0x18
>> [cf135c60] [0019] 0x19
>> [cf135c90] [c000668c] do_softirq+0x54/0x58
>> [cf135ca0] [c001df40] irq_exit+0x48/0x58
>> [cf135cb0] [c00068b4] do_IRQ+0x70/0xc0
>> [cf135cc0] [c00020c0] ret_from_except+0x0/0x18
>> [cf135d80] [c003c2b4] setup_irq+0x1ac/0x200
>> [cf135da0] [c003c3cc] request_irq+0xc4/0xd8
>> [cf135dd0] [c0122328] rtl8139_open+0x38/0x210
>> [cf135df0] [c0187500] dev_open+0x7c/0xcc
>> [cf135e10] [c0187420] dev_change_flags+0x16c/0x1d0
>> [cf135e30] [c01cbff0] devinet_ioctl+0x604/0x720
>> [cf135ea0] [c01cc1f8] inet_ioctl+0x98/0xbc
>> [cf135eb0] [c0179328] sock_ioctl+0x60/0x260
>> [cf135ed0] [c006c360] do_ioctl+0x38/0x84
>> [cf135ee0] [c006c438] vfs_ioctl+0x8c/0x40c
>> [cf135f10] [c006c7f8] sys_ioctl+0x40/0x74
>> [cf135f40] [c0001a84] ret_from_syscall+0x0/0x3c
>> handlers:
>> [] (rtl8139_interrupt+0x0/0x52c)
>> Disabling IRQ #25
>> [EMAIL PROTECTED]:/root>
>> Message from [EMAIL PROTECTED] at Thu Jan  1 00:02:13 1970 ...
>> localhost kernel: Disabling IRQ #25
>>
>> [EMAIL PROTECTED]:/root>
>>
>>
>>  The system boot up information as follows:
>> [EMAIL PROTECTED]:/root> dmesg
>> Linux version 2.6.23-rc6-gea60adb5 ([EMAIL PROTECTED]) (gcc
>> version 4.0.0 (DENX ELDK 4.1 4.0.0)) #3 Fri Sep 21 18:37:59 CST 2007
>> AMCC PowerPC 440EP Yosemite Platform
>> Entering add_active_range(0, 0, 65536) 0 entries of 256 used
>> Zone PFN ranges:
>>   DMA 0 ->65536
>>   Normal  65536 ->65536
>> Movable zone start PFN for each node
>> early_node_map[1] active PFN ranges
>> 0:0 ->65536
>> On node 0 totalpages: 65536
>>   DMA zone: 512 pages used for memmap
>>   DMA zone: 0 pages reserved
>>   DMA zone: 65024 pages, LIFO batch:15
>>   Normal zone: 0 pages used for memmap
>>   Movable zone: 0 pages used for memmap
>> Built 1 zonelists in Zone order.  Total pages: 65024
>> Kernel command line: root=/dev/nfs rw
>> nfsroot=128.224.149.6:/tftpboot/sliu/rootfs
>> ip=128.224.149.11::128.224.149.1:255.255.255.0:yosemite:eth0:off
>> console=ttyS0,9600
>> PID hash table entries: 1024 (order: 10, 4096 bytes)
>> console [ttyS0] enabled
>> Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
>> Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
>> Memory: 

AMCC yosemite 440ep PCI slot doesn't work.

2007-09-21 Thread Andrew Liu
Hello All,

when insert a  RealTek RTL8139 network card into PCI slot,
After system boot up,

[EMAIL PROTECTED]:/root> ifconfig eth2 192.168.17.12
irq 25: nobody cared (try booting with the "irqpoll" option)
Call Trace:
[cf135af0] [c0008820] show_stack+0x48/0x190 (unreliable)
[cf135b20] [c003c414] __report_bad_irq+0x34/0xac
[cf135b40] [c003c714] note_interrupt+0x288/0x2c8
[cf135b70] [c003b818] __do_IRQ+0x104/0x110
[cf135b90] [c0006900] do_IRQ+0xbc/0xc0
[cf135ba0] [c00020c0] ret_from_except+0x0/0x18
[cf135c60] [0019] 0x19
[cf135c90] [c000668c] do_softirq+0x54/0x58
[cf135ca0] [c001df40] irq_exit+0x48/0x58
[cf135cb0] [c00068b4] do_IRQ+0x70/0xc0
[cf135cc0] [c00020c0] ret_from_except+0x0/0x18
[cf135d80] [c003c2b4] setup_irq+0x1ac/0x200
[cf135da0] [c003c3cc] request_irq+0xc4/0xd8
[cf135dd0] [c0122328] rtl8139_open+0x38/0x210
[cf135df0] [c0187500] dev_open+0x7c/0xcc
[cf135e10] [c0187420] dev_change_flags+0x16c/0x1d0
[cf135e30] [c01cbff0] devinet_ioctl+0x604/0x720
[cf135ea0] [c01cc1f8] inet_ioctl+0x98/0xbc
[cf135eb0] [c0179328] sock_ioctl+0x60/0x260
[cf135ed0] [c006c360] do_ioctl+0x38/0x84
[cf135ee0] [c006c438] vfs_ioctl+0x8c/0x40c
[cf135f10] [c006c7f8] sys_ioctl+0x40/0x74
[cf135f40] [c0001a84] ret_from_syscall+0x0/0x3c
handlers:
[] (rtl8139_interrupt+0x0/0x52c)
Disabling IRQ #25
[EMAIL PROTECTED]:/root>
Message from [EMAIL PROTECTED] at Thu Jan  1 00:02:13 1970 ...
localhost kernel: Disabling IRQ #25

[EMAIL PROTECTED]:/root>


 The system boot up information as follows:
[EMAIL PROTECTED]:/root> dmesg
Linux version 2.6.23-rc6-gea60adb5 ([EMAIL PROTECTED]) (gcc
version 4.0.0 (DENX ELDK 4.1 4.0.0)) #3 Fri Sep 21 18:37:59 CST 2007
AMCC PowerPC 440EP Yosemite Platform
Entering add_active_range(0, 0, 65536) 0 entries of 256 used
Zone PFN ranges:
  DMA 0 ->65536
  Normal  65536 ->65536
Movable zone start PFN for each node
early_node_map[1] active PFN ranges
0:0 ->65536
On node 0 totalpages: 65536
  DMA zone: 512 pages used for memmap
  DMA zone: 0 pages reserved
  DMA zone: 65024 pages, LIFO batch:15
  Normal zone: 0 pages used for memmap
  Movable zone: 0 pages used for memmap
Built 1 zonelists in Zone order.  Total pages: 65024
Kernel command line: root=/dev/nfs rw
nfsroot=128.224.149.6:/tftpboot/sliu/rootfs
ip=128.224.149.11::128.224.149.1:255.255.255.0:yosemite:eth0:off
console=ttyS0,9600
PID hash table entries: 1024 (order: 10, 4096 bytes)
console [ttyS0] enabled
Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
Memory: 256896k available (2052k kernel code, 716k data, 152k init, 0k
highmem)
Calibrating delay loop... 798.72 BogoMIPS (lpj=1597440)
Mount-cache hash table entries: 512
NET: Registered protocol family 16
PCI: Probing PCI hardware
PCI: Scanning bus :00
PCI: Found :00:0c.0 [10ec/8139] 000200 00
PCI: Calling quirk c000444c for :00:0c.0
PCI: Fixups for bus :00
PCI: Bus scan for :00 returning with max=00
PCI: fixup irq: (:00:0c.0) got 25
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
NET: Registered protocol family 2
IP route cache hash table entries: 2048 (order: 1, 8192 bytes)
TCP established hash table entries: 8192 (order: 4, 65536 bytes)
TCP bind hash table entries: 8192 (order: 3, 32768 bytes)
TCP: Hash tables configured (established 8192 bind 8192)
TCP reno registered
io scheduler noop registered
io scheduler anticipatory registered (default)
io scheduler deadline registered
io scheduler cfq registered
PCI: Calling quirk c00fbab4 for :00:0c.0
PCI: Calling quirk c02ae3b8 for :00:0c.0
Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing enabled
serial8250: ttyS0 at MMIO 0x0 (irq = 0) is a 16550A
serial8250: ttyS1 at MMIO 0x0 (irq = 1) is a 16550A
RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
PPC 4xx OCP EMAC driver, version 3.54
mal0: initialized, 4 TX channels, 2 RX channels
zmii0: bridge in RMII mode
eth0: emac0, MAC 00:10:ec:00:87:42
eth0: found Generic MII PHY (0x01)
eth1: emac1, MAC 00:00:00:00:00:00
eth1: found Generic MII PHY (0x03)
8139too Fast Ethernet driver 0.9.28
eth2: RealTek RTL8139 at 0xd1012f00, 00:0e:2e:7e:f5:e6, IRQ 25
eth2:  Identified 8139 chip type 'RTL-8100B/8139D'
pegasus: v0.6.14 (2006/09/27), Pegasus/Pegasus II USB Ethernet driver
usbcore: registered new interface driver pegasus
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
usbmon: debugfs is not available
ohci_hcd: 2006 August 04 USB 1.1 'Open' Host Controller (OHCI) Driver
ppc-soc-ohci ppc-soc-ohci.0: USB Host Controller
ppc-soc-ohci ppc-soc-ohci.0: new USB bus registered, assigned bus number 1
ppc-soc-ohci ppc-soc-ohci.0: irq 40, io mem 0xef601000
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 2 ports de