lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Fri, 21 Aug 2009 20:03:26 +0900
From:	Mike McCormack <mikem@...g3k.org>
To:	Rene Mayrhofer <rene.mayrhofer@...raltar.at>
Cc:	Stephen Hemminger <shemminger@...ux-foundation.org>,
	netdev@...r.kernel.org, Richard Leitner <leitner@...s.at>
Subject: Re: Kernel oops on setting sky2 interfaces down

2009/8/21 Rene Mayrhofer <rene.mayrhofer@...raltar.at>:

> I've also tried the net-next-2.6 version of sky2.[ch] as of yesterday without
> Mike's "bandaid" patches. With that version (the last one in branch
> gibraltar-3.0 at https://www.gibraltar.at/git/linux-2.6-gibraltar.git), I
> managed to successfully do a networking restart (with "light" traffic on one
> interface), leaving the interfaces functional after the restart. This worked
> even twice in a row, so mabye we are onto something here. This is certainly an
> improvement over the version with Mike's last patch (from yesterday) applied,
> which left the interfaces broken after a restart (and with the quoted errors
> on a rmmod/modprobe sky2).
>
> However, after doing a ping -f on one of the (GBit) interfaces to another host
> on the same switch for a few seconds and then executing networking restart,
> the result was an immediate reboot of the box without any oops being printed
> to the (serial) console beforehand.

How about trying to remove the skge module, then running tests on the
sky2 interfaces only?  This way you might be able isolate the
remaining problems to sky2 or skge...?

thanks,

Mike
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ