On Wed, 15 Nov 2006 15:36:14 -0800 Andrew Morton wrote:
> On Thu, 16 Nov 2006 00:16:26 +0100
> Adrian Bunk <[EMAIL PROTECTED]> wrote:
>
> > Paravirt breaks CONFIG_X86_PAE=y compilation:
> >
> > <-- snip -->
> >
> > ...
> > CC init/main.o
> > In file included from include2/asm/pgtable.h
> Patch with the memset follows.
Added thanks
-Andi
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
On Sunday, 26 November 2006 00:43, Greg KH wrote:
> On Sun, Nov 26, 2006 at 12:15:52AM +0100, Rafael J. Wysocki wrote:
> > On Saturday, 25 November 2006 23:20, Rafael J. Wysocki wrote:
> > > On Wednesday, 22 November 2006 22:44, Andrew Morton wrote:
> > > > On Wed, 22 Nov 2006 22:07:06 +0100
> > >
On Sun, Nov 26, 2006 at 12:15:52AM +0100, Rafael J. Wysocki wrote:
> On Saturday, 25 November 2006 23:20, Rafael J. Wysocki wrote:
> > On Wednesday, 22 November 2006 22:44, Andrew Morton wrote:
> > > On Wed, 22 Nov 2006 22:07:06 +0100
> > > "Rafael J. Wysocki" <[EMAIL PROTECTED]> wrote:
> > >
> >
On Saturday, 25 November 2006 23:20, Rafael J. Wysocki wrote:
> On Wednesday, 22 November 2006 22:44, Andrew Morton wrote:
> > On Wed, 22 Nov 2006 22:07:06 +0100
> > "Rafael J. Wysocki" <[EMAIL PROTECTED]> wrote:
> >
> > > Hi,
> > >
> > > I get similar traces on every resume from disk on SMP syst
On Wednesday, 22 November 2006 22:44, Andrew Morton wrote:
> On Wed, 22 Nov 2006 22:07:06 +0100
> "Rafael J. Wysocki" <[EMAIL PROTECTED]> wrote:
>
> > Hi,
> >
> > I get similar traces on every resume from disk on SMP systems:
> >
> > WARNING at lib/kobject.c:172 kobject_init()
> >
> > Call Trac
Andrew Morton wrote:
> On Sun, 19 Nov 2006 18:13:45 +0100
> Stefan Richter <[EMAIL PROTECTED]> wrote:
>> Looks very much like eth1394's sysfs interface is getting
>> in the way. And since it is entirely handled by the ieee1394 core, it
>> means ieee1394 needs the class_dev to dev treatment. I think
On Sun, 19 Nov 2006 18:13:45 +0100
Stefan Richter <[EMAIL PROTECTED]> wrote:
> Mattia Dongili wrote:
> > the winner is... gregkh-driver-network-device.patch
That was a fair bet - that patch has caused a mountain of grief.
> Interesting. Looks very much like eth1394's sysfs interface is getting
>
Mattia Dongili wrote:
> the winner is... gregkh-driver-network-device.patch
Interesting. Looks very much like eth1394's sysfs interface is getting
in the way. And since it is entirely handled by the ieee1394 core, it
means ieee1394 needs the class_dev to dev treatment. I think it's OK if
we just w
On Sunday 19 November 2006 11:22, Mattia Dongili wrote:
>On Sat, Nov 18, 2006 at 10:45:01PM +0100, Stefan Richter wrote:
>[...]
>
>> broken-out/gregkh-driver-config_sysfs_deprecated-bus.patch
>> broken-out/gregkh-driver-config_sysfs_deprecated-class.patch
>> broken-out/gregkh-driver-config_sysfs_de
On Sat, Nov 18, 2006 at 10:45:01PM +0100, Stefan Richter wrote:
[...]
> broken-out/gregkh-driver-config_sysfs_deprecated-bus.patch
> broken-out/gregkh-driver-config_sysfs_deprecated-class.patch
> broken-out/gregkh-driver-config_sysfs_deprecated-device.patch
> broken-out/gregkh-driver-config_sysfs_d
On Sat, Nov 18, 2006 at 10:45:01PM +0100, Stefan Richter wrote:
[...]
> It seems like one of the patches in -mm overwrites a device's list of
> children with junk.
>
> Mattia, *if* your machine is able to compile and reboot into new
> kernels really quickly, it would be nice if you could biject b
I wrote:
> It seems like one of the patches in -mm overwrites a device's list of
> children with junk.
And this happens only if eth1394 wasn't unloaded (therefore unbound
from FireWire "ud" devices beneath FireWire "ne" devices beneath the
FireWire host devices) before the host devices's children
I added the following patch:
--- linux-2.6.19-rc5-mm2.orig/drivers/ieee1394/nodemgr.c2006-11-18
21:18:05.0 +0100
+++ linux-2.6.19-rc5-mm2/drivers/ieee1394/nodemgr.c 2006-11-18
21:33:44.0 +0100
@@ -798,8 +798,9 @@ static void nodemgr_remove_uds(struct no
static void
> Time for me to let -mm loose on my PC.
Small progress:
- I get the oops already in nodemgr_remove_ne, unlike the original
report where it happened a little later in driver core functions
called by nodemgr_remove_ne.
- I get it only if eth1394 is loaded when I unload ohci1394.
- Like
Greg KH wrote:
> On Fri, Nov 17, 2006 at 04:24:27PM +0100, Stefan Richter wrote:
>> I wrote:
>>> Either the FireWire host's device->klist_children was overwritten before
>>> the call to device_for_each_child
>> or *during* the run of device_for_each_child, which first successfully
>> called nodemgr
On Fri, Nov 17, 2006 at 04:24:27PM +0100, Stefan Richter wrote:
> I wrote:
> > Mattia Dongili wrote:
> http://oioio.altervista.org/linux/2.6.19-rc5-mm2-1-ko
> > and
> > http://oioio.altervista.org/linux/config-2.6.19-rc5-mm2-1
> > | # CONFIG_SYSFS_DEPRECATED is not set
> >
> > | ieee1394: Nod
I wrote:
> Mattia Dongili wrote:
http://oioio.altervista.org/linux/2.6.19-rc5-mm2-1-ko
> and
> http://oioio.altervista.org/linux/config-2.6.19-rc5-mm2-1
> | # CONFIG_SYSFS_DEPRECATED is not set
>
> | ieee1394: Node removed: ID:BUS[0-00:1023] GUID[080046030227e7bb]
> | ieee1394: Node removed:
Mattia Dongili wrote:
>>> http://oioio.altervista.org/linux/2.6.19-rc5-mm2-1-ko
and
http://oioio.altervista.org/linux/config-2.6.19-rc5-mm2-1
| # CONFIG_SYSFS_DEPRECATED is not set
| ieee1394: Node removed: ID:BUS[0-00:1023] GUID[080046030227e7bb]
| ieee1394: Node removed: ID:BUS[20754571-38:0455
On Thu, Nov 16, 2006 at 11:50:48PM +0100, Stefan Richter wrote:
> Mattia Dongili wrote:
> > On Thu, Nov 16, 2006 at 07:29:35PM +0100, Stefan Richter wrote:
> >> Could you also test one or even better both of:
> >> - 2.6.19-rc5 plus
> >> http://me.in-berlin.de/~s5r6/linux1394/updates/2.6.19-rc5/2.6
Mattia Dongili wrote:
> On Thu, Nov 16, 2006 at 07:29:35PM +0100, Stefan Richter wrote:
>> Could you also test one or even better both of:
>> - 2.6.19-rc5 plus
>> http://me.in-berlin.de/~s5r6/linux1394/updates/2.6.19-rc5/2.6.19-rc5_ieee1394_v204_experimental.patch.bz2
>> (these are the same FireWi
On Thu, Nov 16, 2006 at 07:29:35PM +0100, Stefan Richter wrote:
> Mattia Dongili wrote:
> > got the following when removing ohci1394 (also happens in -mm1),
> ...
> > ieee1394: Node removed: ID:BUS[0-00:1023] GUID[080046030227e7bb]
> > ieee1394: Node removed: ID:BUS[20754571-38:0391] GUID[000
Mattia Dongili wrote:
> got the following when removing ohci1394 (also happens in -mm1),
...
> ieee1394: Node removed: ID:BUS[0-00:1023] GUID[080046030227e7bb]
> ieee1394: Node removed: ID:BUS[20754571-38:0391] GUID[f8eb5067]
Hm, there is garbage in this node data. Moreover, your full lo
Hello,
got the following when removing ohci1394 (also happens in -mm1), config
and full dmesg are here:
http://oioio.altervista.org/linux/config-2.6.19-rc5-mm2-1
http://oioio.altervista.org/linux/config-2.6.19-rc5-mm1-4
http://oioio.altervista.org/linux/oops_rmmod_ohci-2.6.19-rc5-mm2
http://oioio.
On Thursday 16 November 2006 03:27, Chris Wright wrote:
> * Zachary Amsden ([EMAIL PROTECTED]) wrote:
> > Well that shouldn't have happened. Must have been some reject that went
> > unnoticed? Try this.
>
> Thanks Zach, added to the pv patchqueue as well.
That was one of the things that got fi
25 matches
Mail list logo
