Bug 10636 - Pb dualboot XP/debian with the new b44 and ssb drivers (2.6.25)
Summary: Pb dualboot XP/debian with the new b44 and ssb drivers (2.6.25)
Status: CLOSED PATCH_ALREADY_AVAILABLE
Alias: None
Product: Drivers
Classification: Unclassified
Component: Network (show other bugs)
Hardware: All Linux
: P1 normal
Assignee: Jeff Garzik
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-05-08 13:39 UTC by guillaume
Modified: 2008-05-10 02:06 UTC (History)
2 users (show)

See Also:
Kernel Version: 2.6.25.2
Subsystem:
Regression: ---
Bisected commit-id:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description guillaume 2008-05-08 13:39:56 UTC 
Latest working kernel version:
2.6.24.4

Earliest failing kernel version:
none

Distribution:
debian sid

Hardware Environment:
laptop aopen 1557

Software Environment:
dualboot debian/XP

Problem Description:

Hi,
 
I have debian sid and XP on my laptop. I have just tested 2.6.25. All
work good for me except a strange behaviour with b44 and ssb.
 
When I boot on a old 2.6.24 kernel, I have internet through the b44
interface. I reboot under windows, I have internet.
Now When I boot on the new 2.6.25 kernel, I still have internet under
debian. But when I reboot under windows I can't have internet
anymore...

I have seen that there are lots of change with the ssb driver and the
capability to shut down the interface. Is there a link ?

How to fix this behaviour ? 

Steps to reproduce:
boot under debian with 2.6.25 then reboot under XP...


Best regards,
Guillaume
Comment 1 Diego Calleja 2008-05-08 14:37:34 UTC 
(Cc'ed Michael Buesch, the SSB maintainer)
Comment 2 Michael Buesch 2008-05-09 10:46:01 UTC 
I'd say you should fix your windows driver.
This is certainly not a b44/ssb bug, as your windows driver must be able to recover from _any_ state. No matter in which state we leave the card.
So you should upgrade/downgrade your windows driver.
Comment 3 guillaume 2008-05-10 01:37:14 UTC 
bugme-daemon@bugzilla.kernel.org a
Comment 4 Michael Buesch 2008-05-10 01:51:40 UTC 
So can you close this bug, please?
Note You need to log in before you can comment on or make changes to this bug.