On Sun, Jun 1, 2008 at 2:05 AM, Fernando Toledo <[EMAIL PROTECTED]> wrote: > El Vie 30 May 2008, Johannes Berg escribió: >> On Fri, 2008-05-30 at 16:06 +0200, Michael Buesch wrote: >> > On Friday 30 May 2008 14:31:53 Johannes Berg wrote: >> > > Since a while ago I've had trouble resuming when b43 was connected to >> > > an AP while suspended. >> > > >> > > I did a test today where this was the only difference, but I failed to >> > > see whether ssb or b43 were causing the problem. >> > > >> > > Does anyone have a machine with b43 in it that can suspend and supports >> > > the RTC-trace feature so we can narrow it down? Even reproducing might >> > > help to make sure it's not just something weird with my powerbook. >> > >> > Resume is pretty broken since some time for me. >> > It sometimes works fine and sometimes just hangs with a black screen. >> > I have no idea what's going on. >> >> Odd. Resume itself works just fine here, except when b43 is up. But then >> again, you might not notice that this is the problem because by default, >> nothing gets printed on the resume console and then it will indeed hang >> with a black screen. >> >> johannes > > my dmesg > when suspende/resume the b43 crash > <snip> > ata4: SATA link down (SStatus 0 SControl 0) > ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300) > ata1.00: ACPI cmd ef/10:03:00:00:00:a0 succeeded > ata1.00: ACPI cmd ef/10:03:00:00:00:a0 succeeded > ata1.00: configured for UDMA/100 > sd 0:0:0:0: [sda] 117231408 512-byte hardware sectors (60022 MB) > sd 0:0:0:0: [sda] Write Protect is off > sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00 > sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support > DPO or FUA > b43-phy0 debug: Resuming... > b43-phy0 debug: Device resumed. > Restarting tasks ... done. > ieee1394: Host added: ID:BUS[0-00:1023] GUID[00023f9929d1320c] > input: b43-phy0 as /devices/virtual/input/input7 > b43-phy0 ERROR: Microcode not responding > b43-phy0 ERROR: You must go to > http://linuxwireless.org/en/users/Drivers/b43#devicefirmware and download the > correct firmware (version 4). > input: b43-phy0 as /devices/virtual/input/input8 > b43-phy0 ERROR: Microcode not responding > b43-phy0 ERROR: You must go to > http://linuxwireless.org/en/users/Drivers/b43#devicefirmware and download the > correct firmware (version 4). > input: b43-phy0 as /devices/virtual/input/input9 > b43-phy0 ERROR: Microcode not responding > b43-phy0 ERROR: You must go to > http://linuxwireless.org/en/users/Drivers/b43#devicefirmware and download the > correct firmware (version 4). > phy0: Removed STA 00:1b:11:3b:b5:95 > BUG: unable to handle kernel paging request at virtual address f8b1f1aa > printing eip: f8b1f1aa *pde = 37c0f067 *pte = 00000000 > Oops: 0000 [#1] PREEMPT SMP > Modules linked in: i915 drm binfmt_misc rfkill_input vboxdrv lp ipv6 > acpi_cpufreq cpufreq_userspace cpufreq_stats cpufreq_powersave > cpufreq_ondemand freq_table cpufreq_conservative fuse intelfb i2c_algo_bit > i2c_core coretemp hwmon snd_seq_dummy snd_seq_oss snd_seq_midi snd_rawmidi > snd_seq_midi_event snd_seq snd_seq_device arc4 ecb blkcipher cryptomgr > crypto_algapi firmware_class rfkill mac80211 cfg80211 firewire_ohci > firewire_core snd_hda_intel crc32 crc_itu_t snd_pcm_oss snd_mixer_oss > led_class fan rng_core input_polldev ide_cd joydev snd_pcm ehci_hcd cdrom > parport_pc parport ohci1394 uhci_hcd snd_timer thermal rtc ssb iTCO_wdt evdev > ieee1394 mii psmouse yenta_socket rsrc_nonstatic pcmcia_core snd usbcore > container button processor battery ac soundcore snd_page_alloc unix > > Pid: 6057, comm: ipolldevd Not tainted (2.6.24.4fer #11) > EIP: 0060:[<f8b1f1aa>] EFLAGS: 00010247 CPU: 1 > EIP is at 0xf8b1f1aa > EAX: e7a42e40 EBX: e7a42e40 ECX: f7c5eaf0 EDX: e7b1bf48 > ESI: e7a42e54 EDI: e7a42e54 EBP: f8a0809d ESP: f631df80 > DS: 007b ES: 007b FS: 00d8 GS: 0000 SS: 0068 > Process ipolldevd (pid: 6057, ti=f631c000 task=f7cbb6f0 task.ti=f631c000) > Stack: f8a080a9 e7a42e58 e7b1bf40 c0133fc3 001e3247 00000003 00000000 00000000 > e7b1bf48 e7b1bf40 c0134852 e7b1bf50 00000000 c013490e 00000000 f7cbb6f0 > c013729c f631dfc4 f631dfc4 e7b1bf40 c0134852 00000000 c01371cd c0137195 > Call Trace: > [<f8a080a9>] input_polled_device_work+0xc/0x24 [input_polldev] > [<c0133fc3>] run_workqueue+0x77/0x104 > [<c0134852>] worker_thread+0x0/0xca > [<c013490e>] worker_thread+0xbc/0xca > [<c013729c>] autoremove_wake_function+0x0/0x33 > [<c0134852>] worker_thread+0x0/0xca > [<c01371cd>] kthread+0x38/0x5f > [<c0137195>] kthread+0x0/0x5f > [<c0107c67>] kernel_thread_helper+0x7/0x10 > ======================= > Code: Bad EIP value. > EIP: [<f8b1f1aa>] 0xf8b1f1aa SS:ESP 0068:f631df80 > ---[ end trace 46891e208bca1bfe ]--- > b43-phy1: Broadcom 4311 WLAN found > b43-phy1 debug: Found PHY: Analog 0, Type 0, Revision 0 > b43-phy1 ERROR: FOUND UNSUPPORTED RADIO (Manuf 0x0, Version 0x0, Revision 0) > b43: probe of ssb0:0 failed with error -95
Looks like we are losing track of the microcode. The driver thinks it's loaded, but in fact it isn't. Maybe we should reupload the microcode on resume. _______________________________________________ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
