On Wed, 2013-01-16 at 10:29 +0100, Michel Dänzer wrote: > On Die, 2013-01-15 at 22:33 +0100, Martin Kuball wrote: > > Am Tuesday 15 January 2013 schrieb Michel Dänzer: > > > On Mon, 2013-01-14 at 19:47 +0100, Martin Kuball wrote: > > > > > > > > After spending to much time figuring out what's going on, I have at > > > > least a working system. The error is triggered when laptop-mode is > > > > setting the auto negotiation attribute. So it may be a hardware error > > > > after all. Because if I bring up the network manually (ifup -a) it > > > > works. > > > > > > It might still be a sungem driver bug, or the driver might at least be > > > able to work around the hardware problem. Consider reporting a bug > > > against the kernel, preferably upstream. > > > > Can you tell me how to do this or point me to a howto? > > Actually, it looks like there is already a bug report for this, > including a bisected commit introducing the problem: > > https://bugzilla.kernel.org/show_bug.cgi?id=42992 > > > Ben, any ideas?
Looks like it's accessing the chip as a result of an ioctl while the chip is powered down. I'll have a look. Ben. -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: http://lists.debian.org/1358376244.2782.14.camel@pasglop
