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>] [day] [month] [year] [list]
Message-Id: <200811231908.17856.mb@bu3sch.de>
Date:	Sun, 23 Nov 2008 19:08:17 +0100
From:	Michael Buesch <mb@...sch.de>
To:	Yuval Hager <yuval@...amzon.net>
Cc:	bcm43xx-dev@...ts.berlios.de, LKML <linux-kernel@...r.kernel.org>,
	wireless <linux-wireless@...r.kernel.org>,
	Peter Stuge <peter@...ge.se>,
	Larry Finger <Larry.Finger@...inger.net>
Subject: Re: BCM4312 Fails when xdm is started

On Sunday 23 November 2008 18:55:36 Yuval Hager wrote:
> On Sunday 23 November 2008, you wrote:
> > On Sunday 23 November 2008 16:42:28 Larry Finger wrote:
> > > Michael Buesch wrote:
> > > > On Sunday 23 November 2008 12:49:55 Yuval Hager wrote:
> > > >> [  182.891400] ****** b43: B43_MMIO_MACCTL 0x840A0503
> > > >> [  182.891409] ****** b43: SSB_TMSLOW 0x20150000
> > > >> [  258.299027] irq 10: nobody cared (try booting with the "irqpoll"
> > > >> option)
> > > >
> > > > Does the kernel disable the PCI device, if it ignores the IRQ?
> > >
> > > According to /proc/interrupts that Yuval posted earlier, IRQ 10 is not
> > > used.
> >
> > Can you try booting with kernel parameters "noapic" and "noacpi"
> > and reproduce?
> 
> The dump above was generated with "acpi=off noapic nolapic pci=noacpi" boot 
> parameters (see my last email). The /proc/interrupts output was from an 
> earlier occurence, without any of these parameters.
> Did you mean to reproduce and provide logs as well as the content 
> of /proc/interrupts before and after the failure?

No thanks.
Anyway, I cannot really help you with the issue.
I don't think this is a b43 bug, but either a hardware bug or a bug
in some code that controls the PCI bus.

-- 
Greetings Michael.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ