linux-kernel - Re: Oops in ACPI with git latest

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>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 24 Oct 2008 08:47:49 +0200
From:	"Rafael J. Wysocki" <rjw@...k.pl>
To:	James Bottomley <James.Bottomley@...senpartnership.com>
Cc:	linux-acpi@...r.kernel.org,
	"linux-kernel" <linux-kernel@...r.kernel.org>,
	Jesse Barnes <jbarnes@...tuousgeek.org>,
	Len Brown <lenb@...nel.org>, Lin Ming <ming.m.lin@...el.com>
Subject: Re: Oops in ACPI with git latest

On Friday, 24 of October 2008, James Bottomley wrote:
> On Thu, 2008-10-23 at 22:42 +0200, Rafael J. Wysocki wrote:
> > On Thursday, 23 of October 2008, James Bottomley wrote:
> > > ACPI Warning (nseval-0168): Insufficient arguments - method [_OSC] needs 5, found 4 [20080926]
> > > ACPI Warning (nspredef-0252): \_SB_.PCI0._OSC: Parameter count mismatch - ASL declared 5, expected 4 [20080926]
> > > ACPI Error (nspredef-0163): \_SB_.PCI0._OSC: Missing expected return value [20080926]
> > > BUG: unable to handle kernel NULL pointer dereference at 00000000
> > Does this patch help?
> > 
> > ---
> >  drivers/pci/pci-acpi.c |    3 +++
> >  1 file changed, 3 insertions(+)
> > 
> > Index: linux-2.6/drivers/pci/pci-acpi.c
> > ===================================================================
> > --- linux-2.6.orig/drivers/pci/pci-acpi.c
> > +++ linux-2.6/drivers/pci/pci-acpi.c
> > @@ -83,6 +83,9 @@ static acpi_status acpi_run_osc(acpi_han
> >  	if (ACPI_FAILURE(status))
> >  		return status;
> >  
> > +	if (!output.pointer)
> > +		return AE_NULL_OBJECT;
> > +
> >  	out_obj = output.pointer;
> >  	if (out_obj->type != ACPI_TYPE_BUFFER) {
> >  		printk(KERN_DEBUG "Evaluate _OSC returns wrong type\n");
> 
> Yes, that seems to fix it, thanks! ... I suppose the ASL error and
> warnings need investigating too?

Unfortunately, they seem to indicate a BIOS breakage.

According to the spec, _OSC should take 4 arguments, but apparently on your
system it wants 5.

The output of acpidump may be helpful, as Lin Ming already said.

Thanks,
Rafael

--
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/