Thank you, new bug is 252856.
--
skge driver broken: invalid call to spin_unlock causes system crash
https://bugs.launchpad.net/bugs/65631
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
eh... i'm not sure if this is the same bug or related but i am getting an error
with the skge.c file that locks up my computer. the strange thing is that it
doesn't always happen, it seems only to lock-up on random.
I've attached the part of the dmesg log that has the problem
** Attachment
It would be best to open a new bug. The issues in this bug have been
addressed, so new problems shouldn't be confused with it. (Especially
since it is considered to be closed.)
--
skge driver broken: invalid call to spin_unlock causes system crash
https://bugs.launchpad.net/bugs/65631
You
This should now be fixed in USN-578-1 (Dapper kernel 2.6.15-51.66).
** Changed in: linux-source-2.6.15 (Ubuntu)
Status: Fix Committed = Fix Released
--
skge driver broken: invalid call to spin_unlock causes system crash
https://bugs.launchpad.net/bugs/65631
You received this bug
The latest Dapper kernel, 2.6.15-51-686, will still easily crash due to
skge. Please see attached log.
** Attachment added: skge.log
http://launchpadlibrarian.net/11562782/skge.log
--
skge driver broken: invalid call to spin_unlock causes system crash
https://bugs.launchpad.net/bugs/65631
Hm, I'm not sure how, but the ubuntu-security team wasn't subscribed to
this bug (yet it was flagged as security). The fix for this should be
available in the next kernel update for Dapper. Thanks for tracking
down the cause and building a patch. :)
--
skge driver broken: invalid call to
** Changed in: linux-source-2.6.15 (Ubuntu)
Importance: Undecided = Medium
Assignee: Ubuntu Kernel Team (ubuntu-kernel-team) = Kees Cook (keescook)
Status: Confirmed = Fix Committed
--
skge driver broken: invalid call to spin_unlock causes system crash
** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2006-7229
--
skge driver broken: invalid call to spin_unlock causes system crash
https://bugs.launchpad.net/bugs/65631
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
** This bug has been flagged as a security issue
--
skge driver broken: invalid call to spin_unlock causes system crash
https://bugs.launchpad.net/bugs/65631
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing
** Attachment removed: Gutsy: Remove hw_lock spinlock in skge
http://launchpadlibrarian.net/10318744/01_skge.patch
--
skge driver broken: invalid call to spin_unlock causes system crash
https://bugs.launchpad.net/bugs/65631
You received this bug notification because you are a member of
Can anyone confirm the fault still happens when using Gutsy (2.6.22) ?
I've attached a patch for Gutsy to testing.
Although the drivers/net/skge.c and drivers/net/skge.h source has
changed somewhat they still use
drivers/net/skge.h::struct skge_hw {
void __iomem *regs;
I have been using Gutsy for about two weeks now on one of the machines
that were affected by this bug under Dapper (This is a fresh, parallel
installation, no dist-upgrade). I haven't experienced any problems so
far, so it seems that this bug does not exist in Gutsy. My kernel
version is
** Changed in: linux-source-2.6.15 (Ubuntu)
Assignee: (unassigned) = Ubuntu Kernel Team (ubuntu-kernel-team)
--
skge driver broken: invalid call to spin_unlock causes system crash
https://bugs.launchpad.net/bugs/65631
You received this bug notification because you are a member of Ubuntu
This bug still seems to exist in Dapper kernel 2.6.15-29. It's been
almost a year since the bug was reported and the 3-line fix attached.
--
skge driver broken: invalid call to spin_unlock causes system crash
https://bugs.launchpad.net/bugs/65631
You received this bug notification because you
I can confirm that this bug exists in Dapper since version 2.6.15-26.47.
The changelog states that skge was then updated to version in 2.6.17, to
obtain fixes and D-Link DGE-530T support.
I was able to reproduce the bug on two identical computers (ASUS A8V
Deluxe Mainboard, with a Marvell
I can confirm this bug still exists in Dapper kernel 2.6.15-28.
We have three almost identical computers at the office, each having an
Asus P4P800-SE motherboard and running Dapper. All three computers are
connected to a gigabit switch. All three have had stability issues with
networking
** Changed in: linux-source-2.6.15 (Ubuntu)
Status: Unconfirmed = Confirmed
--
skge driver broken: invalid call to spin_unlock causes system crash
https://bugs.launchpad.net/bugs/65631
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for
As there seems to be no activity on this bug yet, I did a binary search
in the bcollins/ubuntu-edgy git tree to find the problematic commit that
introduced the problem. (I use the http interface on git.kernel.org to
do this.)
The situation is quite confusing. There are two files named skge.c in
Included hw spin-lock patch for skge.c and skge.h (based on 2.6.15-27.48
sources). Fix seems to correct the problems in our setup.
** Attachment added: Patch for skge driver version 1.5 (skge.c, skge.h)
http://librarian.launchpad.net/4797263/patch.txt
--
skge driver broken: invalid call to
I just verified that this defect in the skge driver is also present in
the current git tree (URL given below) for edgy. It would be fine if it
could be fixed in time, as releasing edgy with this bug would prevent
installation of edgy on affected machines (without special workarounds),
as accessing
20 matches
Mail list logo
