Dear Linda and Larry, Linda... I am sorry half of the things you said are greek to me... iirc some early rc of 3.6 was ok... Larry... before I get dirty with commits in kernel.. I like to get an analytic approach and have the issue confirmed and be sure is not an observer effect. Alin On 21 September 2012 23:14, Larry Finger <Larry.Finger@lwfinger.net> wrote:
On 09/21/2012 04:31 PM, Linda Walsh wrote:
Alin M Elena wrote:
Hi there,
I have stated the kernel in the title but that does not mean I imply is kernel's fault.
on my system using a broadcom wireless device (which worked pretty well in the past) with the current factory (I got it via a zypper dup from a clean 12.2 install) stopped working... the module loads... the connection seems to be up the only thing is I see no networks.
digging into I see grep eth1 /var/log/warn Sep 21 08:54:24 abbaton udevd[285]: seq 1823 '/devices/pci0000:00/0000:00:16.0/0000:03:00.0/net/eth1' killed Sep 21 08:54:25 abbaton NetworkManager[618]: <error> [1348214065.75959] [nm- device-wifi.c:2673] real_update_permanent_hw_address(): (eth1): unable to read permanent MAC address (error 0)
plus the usual complains about not being able to scan... [alin@abbaton:~]: uname -a Linux abbaton.ucd.ie 3.6.0-rc6-1-desktop #1 SMP PREEMPT Mon Sep 17 13:57:42 UTC 2012 (d6432fe) x86_64 x86_64 x86_64 GNU/Linux
I have a broadcom 1Gb ethernet card in my server that effectively goes dead in 3.3.x and works in 3.2.28.
By 'dead', I mean netlink claims it does not see the device.
However, it is seen by "ip" when I list links (but "ip" can't set it up or set an address on it, as I get a message that netlink thinks there is no such device).
In 3.4, my Intel cards stop being able to operate w/jumbo packets.. I run 9k packets internally, but with 3.4.?, 'ip' was no longer able to set the packet length on these cards.
I have yet to find a solution -- I posted the question to the kernel list but got no response.
Maybe broadcom is no longer supported? Seems unlikely, but anything is possible.
I find it a bit odd that I hadn't seen others with problems, but -- what was the last kernel you used before 3.6?
Weird..never seen symptoms like this before...
You should do what many of us do when there is a regression. We download the git tree for mainline and use 'git bisect' to find the bad commit.
Larry
-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org