On Mit, 2013-01-02 at 14:40 +0100, Martin Kuball wrote: > Am Wednesday 02 January 2013 schrieb Michel Dänzer: > > On Die, 2013-01-01 at 21:52 +0100, Martin Kuball wrote: > > > Hello, > > > > > > I made some progress. After switching update to sequential boot I saw > > > the following exception: > > > > > > machine check in kernel mode > > > caused by (from SRR1=49030): Transfer error ack signal > > > oops: machine check, sig: 7 [#1] > > > > > > the top entry of the call trace is: > > > gem_ioctl+0x60/0x94 [sungem] > > > > > > But this seems really odd to me. If the error is in the kernel module, > > > why does it still occur after switching back to the old kernel? > > > > Maybe one of the userspace packages you upgraded is now using the broken > > kernel functionality but wasn't before. > > > But sungem ist the ethernet driver, isn't it? And indeed networking is > broken.
Right, so the most likely trigger was the upgrade of anything network related, or maybe some kind of boot/init related package which is now setting networking parameters it wasn't before. But a machine check leaves little doubt that the root cause is a bug in the sungem kernel driver (or a hardware problem). > Running ping gives "network unreachable". > ifconfig simply hangs (and with it the shell/terminal from which it > was started). Given the subject says 'stopped booting', how are you able to test that? :) -- Earthling Michel Dänzer | http://www.amd.com Libre software enthusiast | Debian, X and DRI developer -- To UNSUBSCRIBE, email to debian-powerpc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1357146121.30364.164.camel@thor.local
