MPC8560 Gianfar driver hangs after soft reboot

MPC8560 Gianfar driver hangs after soft reboot

[Bill Farrow]

Hi,
The Gianfar driver is hanging during boot-up after a soft reboot.  It
works fine when the board is power cycled.

Any hints on where to look further on this issue?



Here are the details (cut and pasted from my colleague's email):

1. Load the kernel from the Flash and the rootfs from a NFS server.
2. Issue the "reboot" command.  This runs the Busybox reboot producing
the following output:

  The system is going down NOW!
  Sending SIGTERM to all processes
  Sending SIGKILL to all processes
  Requesting system reboot

3. After rebooting, the system starts up Linux and it hangs after:

  eth0: Gianfar Ethernet Controller Version 1.2, 00:40:42:01:00:00
  eth0: Running with NAPI enabled
  eth0: 256/256 RX/TX BD ring size


When stepped through, the kernel endlessly loops in the function:
  gfar_probe(struct platform_device *pdev)

  File: gianfar.c
  Line 233: while (!(gfar_read(&priv->regs->ievent) & (IEVENT_GRSC |
IEVENT_GTSC)))
		cpu_relax();

The soft reset procedure in the MPC8560RM.pdf was followed by separating
out the GTS and GRS completion polling with a delay between these.  The
kernel seems to get stuck at waiting for the GTS to complete.

Tried not doing this "Graceful" stop procedure by commenting out the
relevant driver code.  In this case the Kernel seems to continue on and
gets stuck at mounting the rootfs from NFS, indicating that the network
cannot be accessed.

Also tried soft rebooting without the network cable and the kernel boots
without hanging, but the network does not work when the re-connected.
The PHY seems to be working because when we plug the cable back in it
detects the link and writes this console message:

  [ 1557.465085] PHY: 0:01 - Link is Up - 100/Full

Note that there are two Ethernet controllers on the board (eth0 and
eth1).  Only eth1 is connected to the network.

Background info:
Kernel version 2.6.20.4 PPC
Uboot version 1.2.0
Busybox version 1.5.0
ELDK: 4.1
JTAG: BDI-2000
Board : Microsys PM856 - with MPC8560 processor.


Bill
--
Bill Farrow
Phone : +61 3 9538-3386 <http://www.optiscan.com>

Re: MPC8560 Gianfar driver hangs after soft reboot

[Clemens Koller]

Hi, Bill!

Bill Farrow schrieb:
> The Gianfar driver is hanging during boot-up after a soft reboot.  It
> works fine when the board is power cycled.
> 
> Any hints on where to look further on this issue?

I have had some rare issues with PHY initialization on the PM854
with the u-boot-1.2.0 not being able to download something
via TFTP. There is an entry somewhere in the U-Boot wiki (I think)
that the TQM8540 board can have some issues... well the boards
are quite similar.
Pushing the reset button (Never needed to power that off) solves
the issue.

> 3. After rebooting, the system starts up Linux and it hangs after:
> 
>   eth0: Gianfar Ethernet Controller Version 1.2, 00:40:42:01:00:00
>   eth0: Running with NAPI enabled
>   eth0: 256/256 RX/TX BD ring size

The Kernels I 've tried (2.6.13 up to 2.6.21-rc5 and some latest gits)
never stopped there...
I would just try another kernel. Checkout the code in the latest
git.

> Also tried soft rebooting without the network cable and the kernel boots
> without hanging, but the network does not work when the re-connected.
> The PHY seems to be working because when we plug the cable back in it
> detects the link and writes this console message:
> 
>   [ 1557.465085] PHY: 0:01 - Link is Up - 100/Full
> 
> Note that there are two Ethernet controllers on the board (eth0 and
> eth1).  Only eth1 is connected to the network.

What PHY's do you have on these ports?
(MV88E1111 over here)

> Background info:
> Kernel version 2.6.20.4 PPC
> Uboot version 1.2.0
> Busybox version 1.5.0
> ELDK: 4.1
> JTAG: BDI-2000
> Board : Microsys PM856 - with MPC8560 processor.

Looks good. I am using the PM854.

Well, some other thing: I had some instabilities on my prototyping
hardware in the beginnging, but I guess due to EMI and the sloppy setup.
After I got all the stuff nailed down onto some aluminum-plate, the
boards is working _very_ stable (24/7).

Greets,
-- 
Clemens Koller
__________________________________
R&D Imaging Devices
Anagramm GmbH
Rupert-Mayer-Straße 45/1
Linhof Werksgelände
D-81379 München
Tel.089-741518-50
Fax 089-741518-19
http://www.anagramm-technology.com

RE: MPC8560 Gianfar driver hangs after soft reboot

[Bill Farrow]

On 25 May 2007 Clemens Koller wrote:
> Hi, Bill!
>=20
> Bill Farrow schrieb:
> > The Gianfar driver is hanging during boot-up after a soft
> reboot.  It works fine when the board is power cycled.
> >=20
> > Any hints on where to look further on this issue?
>=20
> I have had some rare issues with PHY initialization on the
> PM854 with the u-boot-1.2.0 not being able to download something via=20
> TFTP. There is an entry somewhere in the U-Boot wiki (I think) that=20
> the TQM8540 board can have some issues...
> well the boards are quite similar.
> Pushing the reset button (Never needed to power that off) solves the=20
> issue.

We have found a work around for this problem: If the network interfaces
are disabled before doing a soft reboot then everything works properly.
We are using the ramdisk from the ELDK 4.1 and are no rc scripts for
busybox to call to shutdown the network interfaces before rebooting.  We
will just add our own script to do this when rebooting.

> > 3. After rebooting, the system starts up Linux and it hangs after:
> >=20
> >   eth0: Gianfar Ethernet Controller Version 1.2, 00:40:42:01:00:00
> >   eth0: Running with NAPI enabled
> >   eth0: 256/256 RX/TX BD ring size
>=20
> The Kernels I 've tried (2.6.13 up to 2.6.21-rc5 and some latest gits)

> never stopped there...
> I would just try another kernel. Checkout the code in the latest git.

Agreed. I did look at some future kernel versions to see what changes
had been made to the gianfar source code, but your right, we should try
some out on the actual hardware.

> > Also tried soft rebooting without the network cable and the kernel=20
> > boots without hanging, but the network does not work when
> the re-connected.
> > The PHY seems to be working because when we plug the cable
> back in it
> > detects the link and writes this console message:
> >=20
> >   [ 1557.465085] PHY: 0:01 - Link is Up - 100/Full
> >=20
> > Note that there are two Ethernet controllers on the board (eth0 and=20
> > eth1).  Only eth1 is connected to the network.
>=20
> What PHY's do you have on these ports?
> (MV88E1111 over here)

Same ones as you: Marvell 88E1111 Gigabit NetPhy

> > Background info:
> > Kernel version 2.6.20.4 PPC
> > Uboot version 1.2.0
> > Busybox version 1.5.0
> > ELDK: 4.1
> > JTAG: BDI-2000
> > Board : Microsys PM856 - with MPC8560 processor.
>=20
> Looks good. I am using the PM854.
>=20
> Well, some other thing: I had some instabilities on my prototyping=20
> hardware in the beginnging, but I guess due to EMI and the sloppy=20
> setup.
> After I got all the stuff nailed down onto some aluminum-plate, the=20
> boards is working _very_ stable (24/7).

We are using the Microsys carrier board with the PM856 module and has
been quite stable.

Bill

Re: MPC8560 Gianfar driver hangs after soft reboot

[Clemens Koller]

Hello, Bill!

Bill Farrow schrieb:
> On 25 May 2007 Clemens Koller wrote:
>> Bill Farrow schrieb:
>>> The Gianfar driver is hanging during boot-up after a soft
>> reboot.  It works fine when the board is power cycled.
>>> Any hints on where to look further on this issue?
>> I have had some rare issues with PHY initialization on the
>> PM854 with the u-boot-1.2.0 not being able to download something via 
>> TFTP. There is an entry somewhere in the U-Boot wiki (I think) that 
>> the TQM8540 board can have some issues...
>> well the boards are quite similar.
>> Pushing the reset button (Never needed to power that off) solves the 
>> issue.
> 
> We have found a work around for this problem: If the network interfaces
> are disabled before doing a soft reboot then everything works properly.
> We are using the ramdisk from the ELDK 4.1 and are no rc scripts for
> busybox to call to shutdown the network interfaces before rebooting.  We
> will just add our own script to do this when rebooting.

Something like:

          /sbin/ip route del default
          /sbin/ip link set eth0 down
          /sbin/ip addr del 192.168.1.200/24 dev eth0
(or something similar using the ifconfig <foo>)

Or how do you define to "shutdown the network interfaces"?

I guess I am lucky that I always had rc scripts running on my system.
(native distribution on harddisk, based on http://crux.nu )

> Agreed. I did look at some future kernel versions to see what changes
> had been made to the gianfar source code, but your right, we should try
> some out on the actual hardware.

Yup, there were lots of changes, also in the PHY/MII interface.

> We are using the Microsys carrier board with the PM856 module and has
> been quite stable.

Same over here. It's good stuff!

Best greets,
-- 
Clemens Koller
__________________________________
R&D Imaging Devices
Anagramm GmbH
Rupert-Mayer-Straße 45/1
Linhof Werksgelände
D-81379 München
Tel.089-741518-50
Fax 089-741518-19
http://www.anagramm-technology.com