Re: [Fwd: Re: long-term regression - Parallel Port broken?]
On Sunday 29 July 2007 09:59:18 pm [EMAIL PROTECTED] wrote: > On Sun, 29 Jul 2007, Bjorn Helgaas wrote: > > >>> > >>> Could you try the attached patch and collect the dmesg log and contents > >>> of /proc/interrupts? > >> > >> done, see the files > >> 2.6.22-rc4.interrupts > >> 2.6.22-rc4.dmesg.test > >> at http://lang.hm/linux > > > > Thanks, but you booted with "pnpacpi=off", so we didn't learn anything. > > The port works with "pnpacpi=off" even without the patch. Somebody > > else tried my "disable/init/activate" patch with terrible results, so > > that approach will need more work. > > Ok, the new versions are there now. I assume the port still didn't work. My current theory is that there's something wrong with parport DMA. > > This seems an awful lot like this bug report: > > http://bugzilla.kernel.org/show_bug.cgi?id=5832 > > > > Can you take a look at 5832, and maybe we can combine your problem > > with that one if you agree they look the same? > > yes, it definantly looks like the same thing. OK, I added you to the cc: list of 5832. Bjorn - To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [Fwd: Re: long-term regression - Parallel Port broken?]
On Sun, 29 Jul 2007, Bjorn Helgaas wrote: Could you try the attached patch and collect the dmesg log and contents of /proc/interrupts? done, see the files 2.6.22-rc4.interrupts 2.6.22-rc4.dmesg.test at http://lang.hm/linux Thanks, but you booted with "pnpacpi=off", so we didn't learn anything. The port works with "pnpacpi=off" even without the patch. Somebody else tried my "disable/init/activate" patch with terrible results, so that approach will need more work. Ok, the new versions are there now. This seems an awful lot like this bug report: http://bugzilla.kernel.org/show_bug.cgi?id=5832 Can you take a look at 5832, and maybe we can combine your problem with that one if you agree they look the same? yes, it definantly looks like the same thing. David Lang Bjorn - To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [Fwd: Re: long-term regression - Parallel Port broken?]
On Sun, 29 Jul 2007, Bjorn Helgaas wrote: of /proc/interrupts? done, see the files 2.6.22-rc4.interrupts 2.6.22-rc4.dmesg.test at http://lang.hm/linux Thanks, but you booted with "pnpacpi=off", so we didn't learn anything. The port works with "pnpacpi=off" even without the patch. Somebody else tried my "disable/init/activate" patch with terrible results, so that approach will need more work. I did?? I thought I had changed that. Ok, I'll try again. David Lang This seems an awful lot like this bug report: http://bugzilla.kernel.org/show_bug.cgi?id=5832 Can you take a look at 5832, and maybe we can combine your problem with that one if you agree they look the same? Bjorn - To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [Fwd: Re: long-term regression - Parallel Port broken?]
On Sunday 29 July 2007 07:22:41 pm [EMAIL PROTECTED] wrote: > On Tue, 24 Jul 2007, Bjorn Helgaas wrote: > > > On Saturday 21 July 2007 08:09:11 pm [EMAIL PROTECTED] wrote: > >> On Fri, 6 Jul 2007, Bjorn Helgaas wrote: > >>> Ultimately, you should have CONFIG_ACPI=y and CONFIG_PNPACPI=y, and you > >>> should not have to boot with "noisapnp" or "pnpacpi=off". My guess is > >>> that you only need "pnpacpi=off" to work around the current problem. > >> > >> these two options are enabled and pnpacpi=off does solve the problem. > >> ... > >> there's now a dmesg.pnpacpi_off which works, and you are correct that the > >> dmesg that's there is the non working one. > > > > Thanks. Here's what I glean from that. With no arguments, it doesn't work: > > > >parport_pc 00:0a: reported by Plug and Play ACPI > >parport0: PC-style at 0x378 (0x778), irq 7, dma 3 > > [PCSPP,TRISTATE,COMPAT,ECP,DMA] > >parport0: Printer, Brother HL-5040 series > >lp0: using parport0 (interrupt-driven). > > > > With pnpacpi=off, it works: > > > >parport0: PC-style at 0x378 (0x778) [PCSPP,TRISTATE] > >parport0: irq 7 detected > >parport0: Printer, Brother HL-5040 series > >lp0: using parport0 (polling). > > > > With pnpacpi=off, or a kernel without PNPACPI, we just probe at 0x378 > > and use the port in polling mode, and it works. > > > > PNPACPI claims the device supports interrupts, so we try to use it in > > interrupt mode, and it doesn't work. It's possible that ACPI is lying > > to us, and the interrupt really doesn't work. Or maybe the interrupt > > *does* work, but the BIOS left it half-configured. > > > > Could you try the attached patch and collect the dmesg log and contents > > of /proc/interrupts? > > done, see the files > 2.6.22-rc4.interrupts > 2.6.22-rc4.dmesg.test > at http://lang.hm/linux Thanks, but you booted with "pnpacpi=off", so we didn't learn anything. The port works with "pnpacpi=off" even without the patch. Somebody else tried my "disable/init/activate" patch with terrible results, so that approach will need more work. This seems an awful lot like this bug report: http://bugzilla.kernel.org/show_bug.cgi?id=5832 Can you take a look at 5832, and maybe we can combine your problem with that one if you agree they look the same? Bjorn - To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [Fwd: Re: long-term regression - Parallel Port broken?]
On Tue, 24 Jul 2007, Bjorn Helgaas wrote:
On Saturday 21 July 2007 08:09:11 pm [EMAIL PROTECTED] wrote:
On Fri, 6 Jul 2007, Bjorn Helgaas wrote:
Ultimately, you should have CONFIG_ACPI=y and CONFIG_PNPACPI=y, and you
should not have to boot with "noisapnp" or "pnpacpi=off". My guess is
that you only need "pnpacpi=off" to work around the current problem.
these two options are enabled and pnpacpi=off does solve the problem.
...
there's now a dmesg.pnpacpi_off which works, and you are correct that the
dmesg that's there is the non working one.
Thanks. Here's what I glean from that. With no arguments, it doesn't work:
parport_pc 00:0a: reported by Plug and Play ACPI
parport0: PC-style at 0x378 (0x778), irq 7, dma 3
[PCSPP,TRISTATE,COMPAT,ECP,DMA]
parport0: Printer, Brother HL-5040 series
lp0: using parport0 (interrupt-driven).
With pnpacpi=off, it works:
parport0: PC-style at 0x378 (0x778) [PCSPP,TRISTATE]
parport0: irq 7 detected
parport0: Printer, Brother HL-5040 series
lp0: using parport0 (polling).
With pnpacpi=off, or a kernel without PNPACPI, we just probe at 0x378
and use the port in polling mode, and it works.
PNPACPI claims the device supports interrupts, so we try to use it in
interrupt mode, and it doesn't work. It's possible that ACPI is lying
to us, and the interrupt really doesn't work. Or maybe the interrupt
*does* work, but the BIOS left it half-configured.
Could you try the attached patch and collect the dmesg log and contents
of /proc/interrupts?
done, see the files
2.6.22-rc4.interrupts
2.6.22-rc4.dmesg.test
at http://lang.hm/linux
David Lang
Thanks,
Bjorn
Index: w/drivers/pnp/pnpacpi/core.c
===
--- w.orig/drivers/pnp/pnpacpi/core.c 2007-07-24 15:05:25.0 -0600
+++ w/drivers/pnp/pnpacpi/core.c2007-07-24 15:29:50.0 -0600
@@ -216,6 +216,13 @@
pnp_add_device(dev);
num ++;
+ if (dev->active) {
+ printk("%s: configuring %s (%s)\n", __FUNCTION__, dev->dev.bus_id,
dev_id->id);
+ pnp_disable_dev(dev);
+ pnp_init_resource_table(&dev->res);
+ pnp_activate_dev(dev);
+ }
+
return AE_OK;
err1:
kfree(dev_id);
-
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [Fwd: Re: long-term regression - Parallel Port broken?]
On Saturday 21 July 2007 08:09:11 pm [EMAIL PROTECTED] wrote:
> On Fri, 6 Jul 2007, Bjorn Helgaas wrote:
> > Ultimately, you should have CONFIG_ACPI=y and CONFIG_PNPACPI=y, and you
> > should not have to boot with "noisapnp" or "pnpacpi=off". My guess is
> > that you only need "pnpacpi=off" to work around the current problem.
>
> these two options are enabled and pnpacpi=off does solve the problem.
> ...
> there's now a dmesg.pnpacpi_off which works, and you are correct that the
> dmesg that's there is the non working one.
Thanks. Here's what I glean from that. With no arguments, it doesn't work:
parport_pc 00:0a: reported by Plug and Play ACPI
parport0: PC-style at 0x378 (0x778), irq 7, dma 3
[PCSPP,TRISTATE,COMPAT,ECP,DMA]
parport0: Printer, Brother HL-5040 series
lp0: using parport0 (interrupt-driven).
With pnpacpi=off, it works:
parport0: PC-style at 0x378 (0x778) [PCSPP,TRISTATE]
parport0: irq 7 detected
parport0: Printer, Brother HL-5040 series
lp0: using parport0 (polling).
With pnpacpi=off, or a kernel without PNPACPI, we just probe at 0x378
and use the port in polling mode, and it works.
PNPACPI claims the device supports interrupts, so we try to use it in
interrupt mode, and it doesn't work. It's possible that ACPI is lying
to us, and the interrupt really doesn't work. Or maybe the interrupt
*does* work, but the BIOS left it half-configured.
Could you try the attached patch and collect the dmesg log and contents
of /proc/interrupts?
Thanks,
Bjorn
Index: w/drivers/pnp/pnpacpi/core.c
===
--- w.orig/drivers/pnp/pnpacpi/core.c 2007-07-24 15:05:25.0 -0600
+++ w/drivers/pnp/pnpacpi/core.c2007-07-24 15:29:50.0 -0600
@@ -216,6 +216,13 @@
pnp_add_device(dev);
num ++;
+ if (dev->active) {
+ printk("%s: configuring %s (%s)\n", __FUNCTION__,
dev->dev.bus_id, dev_id->id);
+ pnp_disable_dev(dev);
+ pnp_init_resource_table(&dev->res);
+ pnp_activate_dev(dev);
+ }
+
return AE_OK;
err1:
kfree(dev_id);
-
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [Fwd: Re: long-term regression - Parallel Port broken?]
On Sun, 22 Jul 2007, Thomas Renninger wrote:
On Sat, 2007-07-21 at 19:04 -0700, [EMAIL PROTECTED] wrote:
On Thu, 28 Jun 2007, Thomas Renninger wrote:
Hi David,
Could this problem have to do with this one:
https://bugzilla.novell.com/show_bug.cgi?id=180390
Tell me if you have problems accessing the bug, it should be public.
Unfortunately the ongoing of the bug stopped a bit for various reasons.
it's requireing a login, and I'm not particularly eager to play 20 guesses
to find a userid that's not already in use.
Yes, but posting on a bugzilla server needs an account...
true, but haivng to go through all that before I can even read details on
the bug is annoying (and haven't you read the other rants by people about
bugzilla, this is one of the reasons ;-)
The first comments pointed in the wrong direction, it's getting
interesting when Vojtech joined the conversation and things pointed to
acpi, possibly acpipnp.
First a collection of acpidump outputs of affected machines would be
great, hopefully other reporters start helping again...
how do I generate an acpidump?
It's included in acpica sources:
http://developer.intel.com/technology/iapc/acpi/downloads.htm
You probably don't want to compile this..., don't know what distribution
you are using, the binary should already be provided ("acpidump"), maybe
you need to install a package including it...
then simply run:
acpidump >/tmp/acpidump
and post the output file using plaintext as mime type.
the file is at lang.hm/linux/acpidump.2.6.22-rc4.nopnpacpi_y
David Lang
Thomas
David Lang
If it is the same bug, it's interesting that 2.6.18-rc3 worked for you
(vanilla or gentoo?). Because SLE[DS]10 is 2.6.16 based, we could have
backported the bug and that might help finding it?
Thanks,
Thomas
PS: I stripped the CC list, things seem to point to acpi...
PSS: Has there already been a bug at bugzilla.kernel.org opened where
dmesg, acpidump and other info can be reviewed? If not this should be
done.
On Wed, 2007-06-27 at 09:19 -0700, Randy Dunlap wrote:
[adding [EMAIL PROTECTED]
On Wed, 27 Jun 2007 00:38:17 -0700 (PDT) [EMAIL PROTECTED] wrote:
On Tue, 26 Jun 2007, Randy Dunlap wrote:
On Mon, 25 Jun 2007 15:56:17 -0700 (PDT) [EMAIL PROTECTED] wrote:
due to the size the files are posted at http://linux.lang.hm/linux
let me know what else I can send to help.
David Lang
I suggest that you test 2.6.22-rcN using one or both of these
boot options:
noisapnp
pnpacpi=off
Somewhere between 2.6.18 and 2.6.22-development, the ACPI config
symbol also starting enabling (selecting) PNP. That's one of many
differences
with the 2.6.22-rc4 kernel that I was useing earlier, adding these two
options clears up the problem. Thanks.
should I test the two individually? or just plan on useing both from now
on?
Yes, please test them individually. I expect that just one of them
will suffice, but I don't know which one.
I normally disable PnP (both ISA and PCI), should I leave it enabled with
the newer kernels and this motherboard?
ACPI recently began enabling (selecting) PNP for you...
How do you normally disable PCI PNP?
What kind of hardware is this? Please show us lspci output.
I would also disable CONFIG_USB_USS720, at least for testing.
for ease of testing (I got time to reboot the box around midnight) I used
the same config as before, so this is still on.
David Lang
On Mon, 25 Jun 2007, Randy Dunlap wrote:
Date: Mon, 25 Jun 2007 15:40:28 -0700
From: Randy Dunlap <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Cc: Andrew Morton <[EMAIL PROTECTED]>, [EMAIL PROTECTED],
[EMAIL PROTECTED]
Subject: Re: long-term regression
[EMAIL PROTECTED] wrote:
On Thu, 21 Jun 2007, Randy Dunlap wrote:
Date: Thu, 21 Jun 2007 08:36:59 -0700
From: Randy Dunlap <[EMAIL PROTECTED]>
To: Andrew Morton <[EMAIL PROTECTED]>
Cc: [EMAIL PROTECTED], [EMAIL PROTECTED],
[EMAIL PROTECTED]
Subject: Re: long-term regression
On Thu, 21 Jun 2007 05:28:07 -0700 Andrew Morton wrote:
On Sun, 17 Jun 2007 10:57:55 -0700 (PDT) [EMAIL PROTECTED] wrote:
I haven't had time to bisect this, but I'm having a problem on a
AMD64
gentoo system where the printer doesn't work with recent kernels.
2.6.18-rc3 worked
2.6.21.1 doesn't
2.6.22-rc4 doesn't
unfortunantly the system is gooted on 2.6.18 at the moment and I'm
out of
town so my ability to test is limited I can provide the 2.6.22-rc4
(attached) and 2.6.18-rc3 configs.
dmesg appears to show the port being detected, but writes to the
port
under newer kernels appear to complete, but no data gets to the
printer.
any suggestions other then doing the large bisect?
That would be good, thanks. Please be sure to cc linux-usb-devel on
the results.
OK, I'm curious about how someone deduced that this is a problem
with a USB printer vs. parallel port p
Re: [Fwd: Re: long-term regression - Parallel Port broken?]
On Sat, 2007-07-21 at 19:04 -0700, [EMAIL PROTECTED] wrote:
> On Thu, 28 Jun 2007, Thomas Renninger wrote:
>
> > Hi David,
> >
> > Could this problem have to do with this one:
> > https://bugzilla.novell.com/show_bug.cgi?id=180390
> > Tell me if you have problems accessing the bug, it should be public.
> > Unfortunately the ongoing of the bug stopped a bit for various reasons.
>
> it's requireing a login, and I'm not particularly eager to play 20 guesses
> to find a userid that's not already in use.
Yes, but posting on a bugzilla server needs an account...
> > The first comments pointed in the wrong direction, it's getting
> > interesting when Vojtech joined the conversation and things pointed to
> > acpi, possibly acpipnp.
> >
> > First a collection of acpidump outputs of affected machines would be
> > great, hopefully other reporters start helping again...
>
> how do I generate an acpidump?
It's included in acpica sources:
http://developer.intel.com/technology/iapc/acpi/downloads.htm
You probably don't want to compile this..., don't know what distribution
you are using, the binary should already be provided ("acpidump"), maybe
you need to install a package including it...
then simply run:
>acpidump >/tmp/acpidump
and post the output file using plaintext as mime type.
Thomas
> David Lang
>
> > If it is the same bug, it's interesting that 2.6.18-rc3 worked for you
> > (vanilla or gentoo?). Because SLE[DS]10 is 2.6.16 based, we could have
> > backported the bug and that might help finding it?
> >
> > Thanks,
> >
> > Thomas
> >
> > PS: I stripped the CC list, things seem to point to acpi...
> >
> > PSS: Has there already been a bug at bugzilla.kernel.org opened where
> > dmesg, acpidump and other info can be reviewed? If not this should be
> > done.
> >
> > On Wed, 2007-06-27 at 09:19 -0700, Randy Dunlap wrote:
> >> [adding [EMAIL PROTECTED]
> >>
> >> On Wed, 27 Jun 2007 00:38:17 -0700 (PDT) [EMAIL PROTECTED] wrote:
> >>
> >>> On Tue, 26 Jun 2007, Randy Dunlap wrote:
> >>>
> >>>> On Mon, 25 Jun 2007 15:56:17 -0700 (PDT) [EMAIL PROTECTED] wrote:
> >>>>
> >>>>> due to the size the files are posted at http://linux.lang.hm/linux
> >>>>>
> >>>>> let me know what else I can send to help.
> >>>>>
> >>>>> David Lang
> >>>>
> >>>>
> >>>> I suggest that you test 2.6.22-rcN using one or both of these
> >>>> boot options:
> >>>>
> >>>> noisapnp
> >>>> pnpacpi=off
> >>>>
> >>>> Somewhere between 2.6.18 and 2.6.22-development, the ACPI config
> >>>> symbol also starting enabling (selecting) PNP. That's one of many
> >>>> differences
> >>>
> >>> with the 2.6.22-rc4 kernel that I was useing earlier, adding these two
> >>> options clears up the problem. Thanks.
> >>>
> >>> should I test the two individually? or just plan on useing both from now
> >>> on?
> >>
> >> Yes, please test them individually. I expect that just one of them
> >> will suffice, but I don't know which one.
> >>
> >>> I normally disable PnP (both ISA and PCI), should I leave it enabled with
> >>> the newer kernels and this motherboard?
> >>
> >> ACPI recently began enabling (selecting) PNP for you...
> >>
> >> How do you normally disable PCI PNP?
> >>
> >> What kind of hardware is this? Please show us lspci output.
> >>
> >>>> I would also disable CONFIG_USB_USS720, at least for testing.
> >>>
> >>> for ease of testing (I got time to reboot the box around midnight) I used
> >>> the same config as before, so this is still on.
> >>>
> >>> David Lang
> >>>
> >>>>
> >>>>> On Mon, 25 Jun 2007, Randy Dunlap wrote:
> >>>>>
> >>>>>> Date: Mon, 25 Jun 2007 15:40:28 -0700
> >>>>>> From: Randy Dunlap <[EMAIL PROTECTED]>
> >>>>>> To: [EMAIL PROTECTED]
> >>>>>> Cc: Andrew Morton <[EMAIL PROTECTED]>, [EMAIL PROTECTED],
> >>>>>> [EMAIL PROTECTED]
> >>>>>> Subject: Re: long-term regression
> >>>>>>
> >>>>>> [EMAIL PROTECTED] wrote:
> >>>>>
Re: [Fwd: Re: long-term regression - Parallel Port broken?]
On Thu, 28 Jun 2007, Thomas Renninger wrote: Hi David, Could this problem have to do with this one: https://bugzilla.novell.com/show_bug.cgi?id=180390 Tell me if you have problems accessing the bug, it should be public. Unfortunately the ongoing of the bug stopped a bit for various reasons. it's requireing a login, and I'm not particularly eager to play 20 guesses to find a userid that's not already in use. The first comments pointed in the wrong direction, it's getting interesting when Vojtech joined the conversation and things pointed to acpi, possibly acpipnp. First a collection of acpidump outputs of affected machines would be great, hopefully other reporters start helping again... how do I generate an acpidump? David Lang If it is the same bug, it's interesting that 2.6.18-rc3 worked for you (vanilla or gentoo?). Because SLE[DS]10 is 2.6.16 based, we could have backported the bug and that might help finding it? Thanks, Thomas PS: I stripped the CC list, things seem to point to acpi... PSS: Has there already been a bug at bugzilla.kernel.org opened where dmesg, acpidump and other info can be reviewed? If not this should be done. On Wed, 2007-06-27 at 09:19 -0700, Randy Dunlap wrote: [adding [EMAIL PROTECTED] On Wed, 27 Jun 2007 00:38:17 -0700 (PDT) [EMAIL PROTECTED] wrote: On Tue, 26 Jun 2007, Randy Dunlap wrote: On Mon, 25 Jun 2007 15:56:17 -0700 (PDT) [EMAIL PROTECTED] wrote: due to the size the files are posted at http://linux.lang.hm/linux let me know what else I can send to help. David Lang I suggest that you test 2.6.22-rcN using one or both of these boot options: noisapnp pnpacpi=off Somewhere between 2.6.18 and 2.6.22-development, the ACPI config symbol also starting enabling (selecting) PNP. That's one of many differences with the 2.6.22-rc4 kernel that I was useing earlier, adding these two options clears up the problem. Thanks. should I test the two individually? or just plan on useing both from now on? Yes, please test them individually. I expect that just one of them will suffice, but I don't know which one. I normally disable PnP (both ISA and PCI), should I leave it enabled with the newer kernels and this motherboard? ACPI recently began enabling (selecting) PNP for you... How do you normally disable PCI PNP? What kind of hardware is this? Please show us lspci output. I would also disable CONFIG_USB_USS720, at least for testing. for ease of testing (I got time to reboot the box around midnight) I used the same config as before, so this is still on. David Lang On Mon, 25 Jun 2007, Randy Dunlap wrote: Date: Mon, 25 Jun 2007 15:40:28 -0700 From: Randy Dunlap <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Cc: Andrew Morton <[EMAIL PROTECTED]>, [EMAIL PROTECTED], [EMAIL PROTECTED] Subject: Re: long-term regression [EMAIL PROTECTED] wrote: On Thu, 21 Jun 2007, Randy Dunlap wrote: Date: Thu, 21 Jun 2007 08:36:59 -0700 From: Randy Dunlap <[EMAIL PROTECTED]> To: Andrew Morton <[EMAIL PROTECTED]> Cc: [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED] Subject: Re: long-term regression On Thu, 21 Jun 2007 05:28:07 -0700 Andrew Morton wrote: On Sun, 17 Jun 2007 10:57:55 -0700 (PDT) [EMAIL PROTECTED] wrote: I haven't had time to bisect this, but I'm having a problem on a AMD64 gentoo system where the printer doesn't work with recent kernels. 2.6.18-rc3 worked 2.6.21.1 doesn't 2.6.22-rc4 doesn't unfortunantly the system is gooted on 2.6.18 at the moment and I'm out of town so my ability to test is limited I can provide the 2.6.22-rc4 (attached) and 2.6.18-rc3 configs. dmesg appears to show the port being detected, but writes to the port under newer kernels appear to complete, but no data gets to the printer. any suggestions other then doing the large bisect? That would be good, thanks. Please be sure to cc linux-usb-devel on the results. OK, I'm curious about how someone deduced that this is a problem with a USB printer vs. parallel port printer since the config file has: CONFIG_PRINTER=y CONFIG_USB_PRINTER=y The kernel boot log should probably be posted also. here is the dmesg from 2.6.22-rc4 and kern.log showing 2.6.22.-rc4 and 2.6.180rc3 the printer not working is the parallel port. This email didn't show up on lkml or linux-usb-devel due to size limits (it was 900+ KB). David, please send your working 2.6.18 config file. Can you post the kernel log files on the web somewhere? --- - To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [Fwd: Re: long-term regression - Parallel Port broken?]
On Fri, 6 Jul 2007, Bjorn Helgaas wrote: should I test the two individually? or just plan on useing both from now on? I normally disable PnP (both ISA and PCI), should I leave it enabled with the newer kernels and this motherboard? Ultimately, you should have CONFIG_ACPI=y and CONFIG_PNPACPI=y, and you should not have to boot with "noisapnp" or "pnpacpi=off". My guess is that you only need "pnpacpi=off" to work around the current problem. these two options are enabled and pnpacpi=off does solve the problem.x At http://linux.lang.hm/linux, I see dmesg logs (with tons of kobject debug that's useless to me) from 2.6.22-rc4. It would be useful to have the log from 2.6.22-rc4 with "pnpacpi=off" (which I expect to work), so we could compare it with the "2.6.22-rc4.dmesg" log, which I assume a non-working one. there's now a dmesg.pnpacpi_off which works, and you are correct that the dmesg that's there is the non working one. Linux PNPACPI currently doesn't manage resources quite the same way Windows does, and that might account for this problem. You might try this: - boot without "pnpacpi=off" (leave PNPACPI enabled) - before loading the parport_pc driver, do this: # echo "disable" > /sys/devices/pnp0/00:0a/resources # echo "enable" > /sys/devices/pnp0/00:0a/resources - load the parport_pc driver the parport driver is built-in (and the kernel doesn't include module support), is there a way to accomplish the test without switching this to a module? David Lang That should cause PNPACPI to run _PRS and _SRS. Many BIOSes report that devices are enabled, but don't actually enable them until _SRS is called. Bjorn - To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: long-term regression
ble) [disabled] [size=64K]
Capabilities: [50] Power Management version 2
Capabilities: [58] Express Endpoint IRQ 0
David Lang
I would also disable CONFIG_USB_USS720, at least for testing.
for ease of testing (I got time to reboot the box around midnight) I used
the same config as before, so this is still on.
David Lang
On Mon, 25 Jun 2007, Randy Dunlap wrote:
Date: Mon, 25 Jun 2007 15:40:28 -0700
From: Randy Dunlap <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Cc: Andrew Morton <[EMAIL PROTECTED]>, [EMAIL PROTECTED],
[EMAIL PROTECTED]
Subject: Re: long-term regression
[EMAIL PROTECTED] wrote:
On Thu, 21 Jun 2007, Randy Dunlap wrote:
Date: Thu, 21 Jun 2007 08:36:59 -0700
From: Randy Dunlap <[EMAIL PROTECTED]>
To: Andrew Morton <[EMAIL PROTECTED]>
Cc: [EMAIL PROTECTED], [EMAIL PROTECTED],
[EMAIL PROTECTED]
Subject: Re: long-term regression
On Thu, 21 Jun 2007 05:28:07 -0700 Andrew Morton wrote:
On Sun, 17 Jun 2007 10:57:55 -0700 (PDT) [EMAIL PROTECTED] wrote:
I haven't had time to bisect this, but I'm having a problem on a
AMD64
gentoo system where the printer doesn't work with recent kernels.
2.6.18-rc3 worked
2.6.21.1 doesn't
2.6.22-rc4 doesn't
unfortunantly the system is gooted on 2.6.18 at the moment and I'm
out of
town so my ability to test is limited I can provide the 2.6.22-rc4
(attached) and 2.6.18-rc3 configs.
dmesg appears to show the port being detected, but writes to the
port
under newer kernels appear to complete, but no data gets to the
printer.
any suggestions other then doing the large bisect?
That would be good, thanks. Please be sure to cc linux-usb-devel on
the results.
OK, I'm curious about how someone deduced that this is a problem
with a USB printer vs. parallel port printer since the config file has:
CONFIG_PRINTER=y
CONFIG_USB_PRINTER=y
The kernel boot log should probably be posted also.
here is the dmesg from 2.6.22-rc4 and kern.log showing 2.6.22.-rc4 and
2.6.180rc3
the printer not working is the parallel port.
This email didn't show up on lkml or linux-usb-devel due to size limits (it
was 900+ KB).
David, please send your working 2.6.18 config file.
Can you post the kernel log files on the web somewhere?
---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
-
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [Fwd: Re: long-term regression - Parallel Port broken?]
On Friday 06 July 2007 03:20:36 pm Bjorn Helgaas wrote: > On Friday 06 July 2007 10:38:50 am Bjorn Helgaas wrote: > > > should I test the two individually? or just plan on useing both from now > > > on? > > > I normally disable PnP (both ISA and PCI), should I leave it enabled with > > > the newer kernels and this motherboard? > > > > Ultimately, you should have CONFIG_ACPI=y and CONFIG_PNPACPI=y, and you > > should not have to boot with "noisapnp" or "pnpacpi=off". My guess is > > that you only need "pnpacpi=off" to work around the current problem. > > > > At http://linux.lang.hm/linux, I see dmesg logs (with tons of > > kobject debug that's useless to me) from 2.6.22-rc4. It would > > be useful to have the log from 2.6.22-rc4 with "pnpacpi=off" > > (which I expect to work), so we could compare it with the > > "2.6.22-rc4.dmesg" log, which I assume a non-working one. > > > > Linux PNPACPI currently doesn't manage resources quite the same way > > Windows does, and that might account for this problem. You might > > try this: > > > > - boot without "pnpacpi=off" (leave PNPACPI enabled) > > - before loading the parport_pc driver, do this: > > # echo "disable" > /sys/devices/pnp0/00:0a/resources > > # echo "enable" > /sys/devices/pnp0/00:0a/resources > > Sorry, I meant: > > # echo "disable" > /sys/devices/pnp0/00:0a/resources > # echo "clear" > /sys/devices/pnp0/00:0a/resources > # echo "enable" > /sys/devices/pnp0/00:0a/resources Ping! David, do you still care about this issue? - To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [Fwd: Re: long-term regression - Parallel Port broken?]
On Friday 06 July 2007 10:38:50 am Bjorn Helgaas wrote: > > should I test the two individually? or just plan on useing both from now > > on? > > I normally disable PnP (both ISA and PCI), should I leave it enabled with > > the newer kernels and this motherboard? > > Ultimately, you should have CONFIG_ACPI=y and CONFIG_PNPACPI=y, and you > should not have to boot with "noisapnp" or "pnpacpi=off". My guess is > that you only need "pnpacpi=off" to work around the current problem. > > At http://linux.lang.hm/linux, I see dmesg logs (with tons of > kobject debug that's useless to me) from 2.6.22-rc4. It would > be useful to have the log from 2.6.22-rc4 with "pnpacpi=off" > (which I expect to work), so we could compare it with the > "2.6.22-rc4.dmesg" log, which I assume a non-working one. > > Linux PNPACPI currently doesn't manage resources quite the same way > Windows does, and that might account for this problem. You might > try this: > > - boot without "pnpacpi=off" (leave PNPACPI enabled) > - before loading the parport_pc driver, do this: > # echo "disable" > /sys/devices/pnp0/00:0a/resources > # echo "enable" > /sys/devices/pnp0/00:0a/resources Sorry, I meant: # echo "disable" > /sys/devices/pnp0/00:0a/resources # echo "clear" > /sys/devices/pnp0/00:0a/resources # echo "enable" > /sys/devices/pnp0/00:0a/resources - To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [Fwd: Re: long-term regression - Parallel Port broken?]
> should I test the two individually? or just plan on useing both from now > on? > I normally disable PnP (both ISA and PCI), should I leave it enabled with > the newer kernels and this motherboard? Ultimately, you should have CONFIG_ACPI=y and CONFIG_PNPACPI=y, and you should not have to boot with "noisapnp" or "pnpacpi=off". My guess is that you only need "pnpacpi=off" to work around the current problem. At http://linux.lang.hm/linux, I see dmesg logs (with tons of kobject debug that's useless to me) from 2.6.22-rc4. It would be useful to have the log from 2.6.22-rc4 with "pnpacpi=off" (which I expect to work), so we could compare it with the "2.6.22-rc4.dmesg" log, which I assume a non-working one. Linux PNPACPI currently doesn't manage resources quite the same way Windows does, and that might account for this problem. You might try this: - boot without "pnpacpi=off" (leave PNPACPI enabled) - before loading the parport_pc driver, do this: # echo "disable" > /sys/devices/pnp0/00:0a/resources # echo "enable" > /sys/devices/pnp0/00:0a/resources - load the parport_pc driver That should cause PNPACPI to run _PRS and _SRS. Many BIOSes report that devices are enabled, but don't actually enable them until _SRS is called. Bjorn - To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
[Fwd: Re: long-term regression - Parallel Port broken?]
Hi David, Could this problem have to do with this one: https://bugzilla.novell.com/show_bug.cgi?id=180390 Tell me if you have problems accessing the bug, it should be public. Unfortunately the ongoing of the bug stopped a bit for various reasons. The first comments pointed in the wrong direction, it's getting interesting when Vojtech joined the conversation and things pointed to acpi, possibly acpipnp. First a collection of acpidump outputs of affected machines would be great, hopefully other reporters start helping again... If it is the same bug, it's interesting that 2.6.18-rc3 worked for you (vanilla or gentoo?). Because SLE[DS]10 is 2.6.16 based, we could have backported the bug and that might help finding it? Thanks, Thomas PS: I stripped the CC list, things seem to point to acpi... PSS: Has there already been a bug at bugzilla.kernel.org opened where dmesg, acpidump and other info can be reviewed? If not this should be done. On Wed, 2007-06-27 at 09:19 -0700, Randy Dunlap wrote: > [adding [EMAIL PROTECTED] > > On Wed, 27 Jun 2007 00:38:17 -0700 (PDT) [EMAIL PROTECTED] wrote: > > > On Tue, 26 Jun 2007, Randy Dunlap wrote: > > > > > On Mon, 25 Jun 2007 15:56:17 -0700 (PDT) [EMAIL PROTECTED] wrote: > > > > > >> due to the size the files are posted at http://linux.lang.hm/linux > > >> > > >> let me know what else I can send to help. > > >> > > >> David Lang > > > > > > > > > I suggest that you test 2.6.22-rcN using one or both of these > > > boot options: > > > > > > noisapnp > > > pnpacpi=off > > > > > > Somewhere between 2.6.18 and 2.6.22-development, the ACPI config > > > symbol also starting enabling (selecting) PNP. That's one of many > > > differences > > > > with the 2.6.22-rc4 kernel that I was useing earlier, adding these two > > options clears up the problem. Thanks. > > > > should I test the two individually? or just plan on useing both from now > > on? > > Yes, please test them individually. I expect that just one of them > will suffice, but I don't know which one. > > > I normally disable PnP (both ISA and PCI), should I leave it enabled with > > the newer kernels and this motherboard? > > ACPI recently began enabling (selecting) PNP for you... > > How do you normally disable PCI PNP? > > What kind of hardware is this? Please show us lspci output. > > > > I would also disable CONFIG_USB_USS720, at least for testing. > > > > for ease of testing (I got time to reboot the box around midnight) I used > > the same config as before, so this is still on. > > > > David Lang > > > > > > > >> On Mon, 25 Jun 2007, Randy Dunlap wrote: > > >> > > >>> Date: Mon, 25 Jun 2007 15:40:28 -0700 > > >>> From: Randy Dunlap <[EMAIL PROTECTED]> > > >>> To: [EMAIL PROTECTED] > > >>> Cc: Andrew Morton <[EMAIL PROTECTED]>, [EMAIL PROTECTED], > > >>> [EMAIL PROTECTED] > > >>> Subject: Re: long-term regression > > >>> > > >>> [EMAIL PROTECTED] wrote: > > >>>> On Thu, 21 Jun 2007, Randy Dunlap wrote: > > >>>> > > >>>>> Date: Thu, 21 Jun 2007 08:36:59 -0700 > > >>>>> From: Randy Dunlap <[EMAIL PROTECTED]> > > >>>>> To: Andrew Morton <[EMAIL PROTECTED]> > > >>>>> Cc: [EMAIL PROTECTED], [EMAIL PROTECTED], > > >>>>> [EMAIL PROTECTED] > > >>>>> Subject: Re: long-term regression > > >>>>> > > >>>>> On Thu, 21 Jun 2007 05:28:07 -0700 Andrew Morton wrote: > > >>>>> > > >>>>>>> On Sun, 17 Jun 2007 10:57:55 -0700 (PDT) [EMAIL PROTECTED] wrote: > > >>>>>>> I haven't had time to bisect this, but I'm having a problem on a > > >>>>>>> AMD64 > > >>>>>>> gentoo system where the printer doesn't work with recent kernels. > > >>>>>>> > > >>>>>>> 2.6.18-rc3 worked > > >>>>>>> 2.6.21.1 doesn't > > >>>>>>> 2.6.22-rc4 doesn't > > >>>>>>> > > >>>>>>> unfortunantly the system is gooted on 2.6.18 at the moment and I'm > > >>>>>>> out of > > >>>>>>> town so my ability to test is l
Re: long-term regression
[adding [EMAIL PROTECTED] On Wed, 27 Jun 2007 00:38:17 -0700 (PDT) [EMAIL PROTECTED] wrote: > On Tue, 26 Jun 2007, Randy Dunlap wrote: > > > On Mon, 25 Jun 2007 15:56:17 -0700 (PDT) [EMAIL PROTECTED] wrote: > > > >> due to the size the files are posted at http://linux.lang.hm/linux > >> > >> let me know what else I can send to help. > >> > >> David Lang > > > > > > I suggest that you test 2.6.22-rcN using one or both of these > > boot options: > > > > noisapnp > > pnpacpi=off > > > > Somewhere between 2.6.18 and 2.6.22-development, the ACPI config > > symbol also starting enabling (selecting) PNP. That's one of many > > differences > > with the 2.6.22-rc4 kernel that I was useing earlier, adding these two > options clears up the problem. Thanks. > > should I test the two individually? or just plan on useing both from now > on? Yes, please test them individually. I expect that just one of them will suffice, but I don't know which one. > I normally disable PnP (both ISA and PCI), should I leave it enabled with > the newer kernels and this motherboard? ACPI recently began enabling (selecting) PNP for you... How do you normally disable PCI PNP? What kind of hardware is this? Please show us lspci output. > > I would also disable CONFIG_USB_USS720, at least for testing. > > for ease of testing (I got time to reboot the box around midnight) I used > the same config as before, so this is still on. > > David Lang > > > > >> On Mon, 25 Jun 2007, Randy Dunlap wrote: > >> > >>> Date: Mon, 25 Jun 2007 15:40:28 -0700 > >>> From: Randy Dunlap <[EMAIL PROTECTED]> > >>> To: [EMAIL PROTECTED] > >>> Cc: Andrew Morton <[EMAIL PROTECTED]>, [EMAIL PROTECTED], > >>> [EMAIL PROTECTED] > >>> Subject: Re: long-term regression > >>> > >>> [EMAIL PROTECTED] wrote: > >>>> On Thu, 21 Jun 2007, Randy Dunlap wrote: > >>>> > >>>>> Date: Thu, 21 Jun 2007 08:36:59 -0700 > >>>>> From: Randy Dunlap <[EMAIL PROTECTED]> > >>>>> To: Andrew Morton <[EMAIL PROTECTED]> > >>>>> Cc: [EMAIL PROTECTED], [EMAIL PROTECTED], > >>>>> [EMAIL PROTECTED] > >>>>> Subject: Re: long-term regression > >>>>> > >>>>> On Thu, 21 Jun 2007 05:28:07 -0700 Andrew Morton wrote: > >>>>> > >>>>>>> On Sun, 17 Jun 2007 10:57:55 -0700 (PDT) [EMAIL PROTECTED] wrote: > >>>>>>> I haven't had time to bisect this, but I'm having a problem on a > >>>>>>> AMD64 > >>>>>>> gentoo system where the printer doesn't work with recent kernels. > >>>>>>> > >>>>>>> 2.6.18-rc3 worked > >>>>>>> 2.6.21.1 doesn't > >>>>>>> 2.6.22-rc4 doesn't > >>>>>>> > >>>>>>> unfortunantly the system is gooted on 2.6.18 at the moment and I'm > >>>>>>> out of > >>>>>>> town so my ability to test is limited I can provide the 2.6.22-rc4 > >>>>>>> (attached) and 2.6.18-rc3 configs. > >>>>>>> > >>>>>>> dmesg appears to show the port being detected, but writes to the > >>>>>>> port > >>>>>>> under newer kernels appear to complete, but no data gets to the > >>>>>>> printer. > >>>>>>> > >>>>>>> any suggestions other then doing the large bisect? > >>>>>> > >>>>>> That would be good, thanks. Please be sure to cc linux-usb-devel on > >>>>>> the results. > >>>>> > >>>>> OK, I'm curious about how someone deduced that this is a problem > >>>>> with a USB printer vs. parallel port printer since the config file has: > >>>>> > >>>>> CONFIG_PRINTER=y > >>>>> CONFIG_USB_PRINTER=y > >>>>> > >>>>> The kernel boot log should probably be posted also. > >>>> > >>>> here is the dmesg from 2.6.22-rc4 and kern.log showing 2.6.22.-rc4 and > >>>> 2.6.180rc3 > >>>> > >>>> the printer not working is the parallel port. > >>> > >>> This email didn't show up on lkml or linux-usb-devel due to size limits > >>> (it > >>> was 900+ KB). > >>> > >>> David, please send your working 2.6.18 config file. > >>> > >>> Can you post the kernel log files on the web somewhere? --- ~Randy *** Remember to use Documentation/SubmitChecklist when testing your code *** - To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
