On Mon, Nov 29, 2010 at 09:27:55PM +0100, Frans van Berckel wrote: > On Mon, 2010-11-29 at 17:05 +0000, Richard Mortimer wrote: > > Both devices have local-mac-address properties in the device tree. That > > suggests that there is something wrong with the logic in driver itself. > > <snip> > > > I had a quick look at the 2.3.36 driver on kernel.org > > > > http://git.kernel.org/?p=linux/kernel/git/stable/linux-2.6.36.y.git;a=history;f=drivers/net/cassini.c;h=28c88eeec757361fb2fa3db11a63b57c97b892fb;hb=HEAD > > > > and a cursory look at that shows code for parsing local-mac-address > > (circa line 3290). I haven't looked very deeply but it seems like the > > driver is failing to read the VPD rom and falling back onto a random > > address. > > > > There doesn't seem to be anything obvious in the recent history that > > suggests where this might have been fixed. > > > > Next step would likely be to try a 2.6.36 kernel to see whether it > > already has a fix etc. > > Thanks for looking into it Richard, but the stable 2.6.36.1 does not boot at > all, with a serial console on Sparc64. But that's outside the scoop of the > cassini driver stuff we are looking for. > > Booting Linux... > PERCPU: Embedded 6 pages/cpu @fffff80004400000 s18240 r8192 d22720 u1048576 > pcpu-alloc: s18240 r8192 d22720 u1048576 alloc=1*4194304 > pcpu-alloc: [0] 0 1 2 3 > Built 1 zonelists in Zone order, mobility grouping on. Total pages: 842577 > Kernel command line: root=/dev/md0 ro > PID hash table entries: 4096 (order: 2, 32768 bytes) > Dentry cache hash table entries: 1048576 (order: 10, 8388608 bytes) > Inode-cache hash table entries: 524288 (order: 9, 4194304 bytes) > Memory: 8292000k available (5088k kernel code, 1800k data, 272k init) > [fffff80000000000,000000323feb6000] > SLUB: Genslabs=14, HWalign=32, Order=0-3, MinObjects=0, CPUs=4, Nodes=1 > Hierarchical RCU implementation. > CONFIG_RCU_FANOUT set to non-default value of 32 > RCU-based detection of stalled CPUs is disabled. > Verbose stalled-CPUs detection is disabled. > NR_IRQS:255 > clocksource: mult[c8000000] shift[25] > clockevent: mult[28f5c28] shift[32] > Console: colour dummy device 80x25 > console [tty0] enabled, bootconsole disabled
Can you try doing a cold boot, i.e. powering the machine down completely before booting it into the new kernel? I've seen the same symptoms when rebooting, but it works for me as expected if I power-cycle the machine before booting. Best regards, -- Jurij Smakov [email protected] Key: http://www.wooyd.org/pgpkey/ KeyID: C99E03CC -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: http://lists.debian.org/[email protected]
