* Re: Linux v2.6.16-rc5
2006-02-27 5:27 Linux v2.6.16-rc5 Linus Torvalds
@ 2006-02-27 5:51 ` Jeff Garzik
2006-02-27 6:21 ` Randy.Dunlap
` (2 more replies)
2006-02-27 6:13 ` 2.6.16-rc5: known regressions Adrian Bunk
` (9 subsequent siblings)
10 siblings, 3 replies; 62+ messages in thread
From: Jeff Garzik @ 2006-02-27 5:51 UTC (permalink / raw)
To: Linus Torvalds; +Cc: Linux Kernel Mailing List
Linus Torvalds wrote:
> The tar-ball is being uploaded right now, and everything else should
> already be pushed out. Mirroring might take a while, of course.
>
> There's not much to say about this: people have been pretty good, and it's
> just a random collection of fixes in various random areas. The shortlog is
> actually pretty short, and it really describes the updates better than
> anything else.
>
> Have I missed anything? Holler. And please keep reminding about any
> regressions since 2.6.15.
Yep, you missed the data corruption fix (libata) and oops fix (netdev)
that I sent at 5pm EST today...
And we may have to turn off FUA (barriers) before 2.6.16 goes out.
Jeff
^ permalink raw reply [flat|nested] 62+ messages in thread* Re: Linux v2.6.16-rc5
2006-02-27 5:51 ` Jeff Garzik
@ 2006-02-27 6:21 ` Randy.Dunlap
2006-02-27 6:52 ` Jeff Garzik
2006-02-27 8:13 ` Paul Rolland
2006-02-27 18:04 ` Francois Romieu
2 siblings, 1 reply; 62+ messages in thread
From: Randy.Dunlap @ 2006-02-27 6:21 UTC (permalink / raw)
To: Jeff Garzik; +Cc: torvalds, linux-kernel
On Mon, 27 Feb 2006 00:51:07 -0500 Jeff Garzik wrote:
> Linus Torvalds wrote:
> > The tar-ball is being uploaded right now, and everything else should
> > already be pushed out. Mirroring might take a while, of course.
> >
> > There's not much to say about this: people have been pretty good, and it's
> > just a random collection of fixes in various random areas. The shortlog is
> > actually pretty short, and it really describes the updates better than
> > anything else.
> >
> > Have I missed anything? Holler. And please keep reminding about any
> > regressions since 2.6.15.
>
> Yep, you missed the data corruption fix (libata) and oops fix (netdev)
> that I sent at 5pm EST today...
>
> And we may have to turn off FUA (barriers) before 2.6.16 goes out.
Jeff, were you planning to make atapi_enabled=1 be the default
for 2.6.16 ?
---
~Randy
^ permalink raw reply [flat|nested] 62+ messages in thread
* Re: Linux v2.6.16-rc5
2006-02-27 6:21 ` Randy.Dunlap
@ 2006-02-27 6:52 ` Jeff Garzik
0 siblings, 0 replies; 62+ messages in thread
From: Jeff Garzik @ 2006-02-27 6:52 UTC (permalink / raw)
To: Randy.Dunlap; +Cc: torvalds, linux-kernel
Randy.Dunlap wrote:
> On Mon, 27 Feb 2006 00:51:07 -0500 Jeff Garzik wrote:
>
>
>>Linus Torvalds wrote:
>>
>>>The tar-ball is being uploaded right now, and everything else should
>>>already be pushed out. Mirroring might take a while, of course.
>>>
>>>There's not much to say about this: people have been pretty good, and it's
>>>just a random collection of fixes in various random areas. The shortlog is
>>>actually pretty short, and it really describes the updates better than
>>>anything else.
>>>
>>>Have I missed anything? Holler. And please keep reminding about any
>>>regressions since 2.6.15.
>>
>>Yep, you missed the data corruption fix (libata) and oops fix (netdev)
>>that I sent at 5pm EST today...
>>
>>And we may have to turn off FUA (barriers) before 2.6.16 goes out.
>
>
> Jeff, were you planning to make atapi_enabled=1 be the default
> for 2.6.16 ?
It's far too late for that now.
Jeff
^ permalink raw reply [flat|nested] 62+ messages in thread
* Re: Linux v2.6.16-rc5
2006-02-27 5:51 ` Jeff Garzik
2006-02-27 6:21 ` Randy.Dunlap
@ 2006-02-27 8:13 ` Paul Rolland
2006-02-27 18:04 ` Francois Romieu
2 siblings, 0 replies; 62+ messages in thread
From: Paul Rolland @ 2006-02-27 8:13 UTC (permalink / raw)
To: 'Jeff Garzik', 'Linus Torvalds'
Cc: 'Linux Kernel Mailing List'
Missing also the fix I sent for e1000 MII interface.
Paul
Paul Rolland, rol(at)as2917.net
ex-AS2917 Network administrator and Peering Coordinator
--
Please no HTML, I'm not a browser - Pas d'HTML, je ne suis pas un navigateur
"Some people dream of success... while others wake up and work hard at it"
"I worry about my child and the Internet all the time, even though she's too
young to have logged on yet. Here's what I worry about. I worry that 10 or 15
years from now, she will come to me and say 'Daddy, where were you when they
took freedom of the press away from the Internet?'"
--Mike Godwin, Electronic Frontier Foundation
> -----Original Message-----
> From: linux-kernel-owner@vger.kernel.org
> [mailto:linux-kernel-owner@vger.kernel.org] On Behalf Of Jeff Garzik
> Sent: Monday, February 27, 2006 6:51 AM
> To: Linus Torvalds
> Cc: Linux Kernel Mailing List
> Subject: Re: Linux v2.6.16-rc5
>
> Linus Torvalds wrote:
> > The tar-ball is being uploaded right now, and everything
> else should
> > already be pushed out. Mirroring might take a while, of course.
> >
> > There's not much to say about this: people have been pretty
> good, and it's
> > just a random collection of fixes in various random areas.
> The shortlog is
> > actually pretty short, and it really describes the updates
> better than
> > anything else.
> >
> > Have I missed anything? Holler. And please keep reminding about any
> > regressions since 2.6.15.
>
> Yep, you missed the data corruption fix (libata) and oops fix
> (netdev)
> that I sent at 5pm EST today...
>
> And we may have to turn off FUA (barriers) before 2.6.16 goes out.
>
> Jeff
>
>
>
> -
> To unsubscribe from this list: send the line "unsubscribe
> linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
>
^ permalink raw reply [flat|nested] 62+ messages in thread
* Re: Linux v2.6.16-rc5
2006-02-27 5:51 ` Jeff Garzik
2006-02-27 6:21 ` Randy.Dunlap
2006-02-27 8:13 ` Paul Rolland
@ 2006-02-27 18:04 ` Francois Romieu
2006-02-27 18:38 ` Jeff Garzik
2 siblings, 1 reply; 62+ messages in thread
From: Francois Romieu @ 2006-02-27 18:04 UTC (permalink / raw)
To: Jeff Garzik; +Cc: Linus Torvalds, Linux Kernel Mailing List
Jeff Garzik <jgarzik@pobox.com> :
[...]
> Yep, you missed the data corruption fix (libata) and oops fix (netdev)
> that I sent at 5pm EST today...
Expect a fix for a via-velocity bug when mtu > 1500 and a fix for
suspend/resume with the 8139cp driver later today.
--
Ueimor
^ permalink raw reply [flat|nested] 62+ messages in thread
* Re: Linux v2.6.16-rc5
2006-02-27 18:04 ` Francois Romieu
@ 2006-02-27 18:38 ` Jeff Garzik
2006-02-27 22:24 ` Pull request for 'for-jeff' branch Francois Romieu
0 siblings, 1 reply; 62+ messages in thread
From: Jeff Garzik @ 2006-02-27 18:38 UTC (permalink / raw)
To: Francois Romieu; +Cc: Linus Torvalds, Linux Kernel Mailing List
Francois Romieu wrote:
> Jeff Garzik <jgarzik@pobox.com> :
> [...]
>
>>Yep, you missed the data corruption fix (libata) and oops fix (netdev)
>>that I sent at 5pm EST today...
>
>
> Expect a fix for a via-velocity bug when mtu > 1500 and a fix for
> suspend/resume with the 8139cp driver later today.
Cool, I'll send those with the e1000 fix that needs to go.
Jeff
^ permalink raw reply [flat|nested] 62+ messages in thread
* Pull request for 'for-jeff' branch
2006-02-27 18:38 ` Jeff Garzik
@ 2006-02-27 22:24 ` Francois Romieu
0 siblings, 0 replies; 62+ messages in thread
From: Francois Romieu @ 2006-02-27 22:24 UTC (permalink / raw)
To: Jeff Garzik; +Cc: linux-kernel, netdev, Pierre Ossman, John Zielinski
Please pull from branch 'for-jeff' to get the changes below:
git://electric-eye.fr.zoreil.com/home/romieu/linux-2.6.git
Shortlog
--------
$ git rev-list --pretty master..HEAD | git shortlog
Francois Romieu:
via-velocity: fix memory corruption when changing the mtu
8139cp: fix broken suspend/resume
Patch
-----
diff --git a/drivers/net/8139cp.c b/drivers/net/8139cp.c
index f822cd3..dd41049 100644
--- a/drivers/net/8139cp.c
+++ b/drivers/net/8139cp.c
@@ -1118,13 +1118,18 @@ err_out:
return -ENOMEM;
}
+static void cp_init_rings_index (struct cp_private *cp)
+{
+ cp->rx_tail = 0;
+ cp->tx_head = cp->tx_tail = 0;
+}
+
static int cp_init_rings (struct cp_private *cp)
{
memset(cp->tx_ring, 0, sizeof(struct cp_desc) * CP_TX_RING_SIZE);
cp->tx_ring[CP_TX_RING_SIZE - 1].opts1 = cpu_to_le32(RingEnd);
- cp->rx_tail = 0;
- cp->tx_head = cp->tx_tail = 0;
+ cp_init_rings_index(cp);
return cp_refill_rx (cp);
}
@@ -1886,30 +1891,30 @@ static int cp_suspend (struct pci_dev *p
spin_unlock_irqrestore (&cp->lock, flags);
- if (cp->pdev && cp->wol_enabled) {
- pci_save_state (cp->pdev);
- cp_set_d3_state (cp);
- }
+ pci_save_state(pdev);
+ pci_enable_wake(pdev, pci_choose_state(pdev, state), cp->wol_enabled);
+ pci_set_power_state(pdev, pci_choose_state(pdev, state));
return 0;
}
static int cp_resume (struct pci_dev *pdev)
{
- struct net_device *dev;
- struct cp_private *cp;
+ struct net_device *dev = pci_get_drvdata (pdev);
+ struct cp_private *cp = netdev_priv(dev);
unsigned long flags;
- dev = pci_get_drvdata (pdev);
- cp = netdev_priv(dev);
+ if (!netif_running(dev))
+ return 0;
netif_device_attach (dev);
-
- if (cp->pdev && cp->wol_enabled) {
- pci_set_power_state (cp->pdev, PCI_D0);
- pci_restore_state (cp->pdev);
- }
-
+
+ pci_set_power_state(pdev, PCI_D0);
+ pci_restore_state(pdev);
+ pci_enable_wake(pdev, PCI_D0, 0);
+
+ /* FIXME: sh*t may happen if the Rx ring buffer is depleted */
+ cp_init_rings_index (cp);
cp_init_hw (cp);
netif_start_queue (dev);
diff --git a/drivers/net/via-velocity.c b/drivers/net/via-velocity.c
index c2d5907..ed1f837 100644
--- a/drivers/net/via-velocity.c
+++ b/drivers/net/via-velocity.c
@@ -1106,6 +1106,9 @@ static void velocity_free_rd_ring(struct
for (i = 0; i < vptr->options.numrx; i++) {
struct velocity_rd_info *rd_info = &(vptr->rd_info[i]);
+ struct rx_desc *rd = vptr->rd_ring + i;
+
+ memset(rd, 0, sizeof(*rd));
if (!rd_info->skb)
continue;
^ permalink raw reply related [flat|nested] 62+ messages in thread
* 2.6.16-rc5: known regressions
2006-02-27 5:27 Linux v2.6.16-rc5 Linus Torvalds
2006-02-27 5:51 ` Jeff Garzik
@ 2006-02-27 6:13 ` Adrian Bunk
2006-02-27 6:26 ` Ryan Phillips
` (4 more replies)
2006-02-27 7:28 ` Linux v2.6.16-rc5 Dave Jones
` (8 subsequent siblings)
10 siblings, 5 replies; 62+ messages in thread
From: Adrian Bunk @ 2006-02-27 6:13 UTC (permalink / raw)
To: Linus Torvalds, Andrew Morton
Cc: Linux Kernel Mailing List, Tom Seeley, Dave Jones, Jiri Slaby,
michael, mchehab, v4l-dvb-maintainer, video4linux-list,
Brian Marete, Ryan Phillips, gregkh, linux-usb-devel,
Sanjoy Mahajan, Luming Yu, len.brown, linux-acpi, Mark Lord,
Randy Dunlap, jgarzik, linux-ide, Duncan, Pavlik Vojtech,
linux-input, Meelis Roos
This email lists some known regressions in 2.6.16-rc5 compared to 2.6.15.
If you find your name in the Cc header, you are either submitter of one
of the bugs, maintainer of an affectected subsystem or driver, a patch
of you was declared guilty for a breakage or I'm considering you in any
other way possibly involved with one or more of these issues.
Due to the huge amount of recipients, this email has a Reply-To set.
Please add the appropriate people to the Cc when replying regarding one
of these issues.
Subject : usb_submit_urb(ctrl) failed on 2.6.16-rc4-git10 kernel
References : http://bugzilla.kernel.org/show_bug.cgi?id=6134
Submitter : Ryan Phillips <rphillips@gentoo.org>
Status : unknown
Subject : Oops in Kernel 2.6.16-rc4 on Modprobe of saa7134.ko
References : http://lkml.org/lkml/2006/2/20/122
Submitter : Brian Marete <bgmarete@gmail.com>
Status : unknown
Subject : saa7146: no devices created in /dev/dvb
References : https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=181063
http://lkml.org/lkml/2006/2/18/204
Submitter : Tom Seeley <redhat@tomseeley.co.uk>
Dave Jones <davej@redhat.com>
Handled-By : Jiri Slaby <jirislaby@gmail.com>
Status : unknown
Subject : S3 sleep hangs the second time - 600X
References : http://bugzilla.kernel.org/show_bug.cgi?id=5989
Submitter : Sanjoy Mahajan <sanjoy@mrao.cam.ac.uk>
Handled-By : Luming Yu <luming.yu@intel.com>
Status : is being debugged,
we might want to change the default back for 2.6.16:
http://lkml.org/lkml/2006/2/25/101
Subject : 2.6.16-rc[34]: resume-from-RAM unreliable (SATA)
References : http://lkml.org/lkml/2006/2/20/159
Submitter : Mark Lord <lkml@rtr.ca>
Handled-By : Randy Dunlap <rdunlap@xenotime.net>
Status : one of Randy's patches seems to fix it
Subject : total ps2 keyboard lockup from boot
References : http://bugzilla.kernel.org/show_bug.cgi?id=6130
Submitter : Duncan <1i5t5.duncan@cox.net>
Handled-By : Dmitry Torokhov <dmitry.torokhov@gmail.com>
Pavlik Vojtech <vojtech@suse.cz>
Status : discussion and debugging in the bug logs
Subject : psmouse starts losing sync in 2.6.16-rc2
References : http://lkml.org/lkml/2006/2/5/50
Submitter : Meelis Roos <mroos@linux.ee>
Handled-By : Dmitry Torokhov <dmitry.torokhov@gmail.com>
Status : Dmitry: Working on various manifestations of this one.
At worst we will have to disable resync by default
before 2.6.16 final is out and continue in 2.6.17 cycle.
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
^ permalink raw reply [flat|nested] 62+ messages in thread* Re: 2.6.16-rc5: known regressions
2006-02-27 6:13 ` 2.6.16-rc5: known regressions Adrian Bunk
@ 2006-02-27 6:26 ` Ryan Phillips
2006-02-27 6:39 ` Vojtech Pavlik
2006-02-27 6:54 ` 2.6.16-rc5: known regressions Jeff Garzik
` (3 subsequent siblings)
4 siblings, 1 reply; 62+ messages in thread
From: Ryan Phillips @ 2006-02-27 6:26 UTC (permalink / raw)
To: linux-kernel
Cc: Linus Torvalds, Andrew Morton, Tom Seeley, Dave Jones,
Jiri Slaby, michael, mchehab, v4l-dvb-maintainer,
video4linux-list, Brian Marete, Ryan Phillips, gregkh,
linux-usb-devel, Sanjoy Mahajan, Luming Yu, len.brown,
linux-acpi, Mark Lord, Randy Dunlap, jgarzik, linux-ide, Duncan,
Pavlik Vojtech, linux-input, Meelis Roos
Adrian Bunk wrote:
> This email lists some known regressions in 2.6.16-rc5 compared to 2.6.15.
>
> If you find your name in the Cc header, you are either submitter of one
> of the bugs, maintainer of an affectected subsystem or driver, a patch
> of you was declared guilty for a breakage or I'm considering you in any
> other way possibly involved with one or more of these issues.
>
> Due to the huge amount of recipients, this email has a Reply-To set.
> Please add the appropriate people to the Cc when replying regarding one
> of these issues.
>
>
> Subject : usb_submit_urb(ctrl) failed on 2.6.16-rc4-git10 kernel
> References : http://bugzilla.kernel.org/show_bug.cgi?id=6134
> Submitter : Ryan Phillips <rphillips@gentoo.org>
> Status : unknown
>
>
*snipped
> Subject : total ps2 keyboard lockup from boot
> References : http://bugzilla.kernel.org/show_bug.cgi?id=6130
> Submitter : Duncan <1i5t5.duncan@cox.net>
> Handled-By : Dmitry Torokhov <dmitry.torokhov@gmail.com>
> Pavlik Vojtech <vojtech@suse.cz>
> Status : discussion and debugging in the bug logs
>
>
*snipped
It appears that Duncan's "total ps2 keyboard lockup from boot" is the
same, or similar problem as mine.
2.6.15.1 kernel is working for me though.
-Ryan
^ permalink raw reply [flat|nested] 62+ messages in thread* Re: 2.6.16-rc5: known regressions
2006-02-27 6:26 ` Ryan Phillips
@ 2006-02-27 6:39 ` Vojtech Pavlik
2006-02-27 9:14 ` 2.6.16-rc5: known regressions (ps2 mouse/keyboard issues) Duncan
0 siblings, 1 reply; 62+ messages in thread
From: Vojtech Pavlik @ 2006-02-27 6:39 UTC (permalink / raw)
To: Ryan Phillips
Cc: linux-kernel, Linus Torvalds, Andrew Morton, Tom Seeley,
Dave Jones, Jiri Slaby, michael, mchehab, v4l-dvb-maintainer,
video4linux-list, Brian Marete, Ryan Phillips, gregkh,
linux-usb-devel, Sanjoy Mahajan, Luming Yu, len.brown,
linux-acpi, Mark Lord, Randy Dunlap, jgarzik, linux-ide, Duncan,
linux-input, Meelis Roos
On Sun, Feb 26, 2006 at 10:26:41PM -0800, Ryan Phillips wrote:
> Adrian Bunk wrote:
> > This email lists some known regressions in 2.6.16-rc5 compared to 2.6.15.
> >
> > If you find your name in the Cc header, you are either submitter of one
> > of the bugs, maintainer of an affectected subsystem or driver, a patch
> > of you was declared guilty for a breakage or I'm considering you in any
> > other way possibly involved with one or more of these issues.
> >
> > Due to the huge amount of recipients, this email has a Reply-To set.
> > Please add the appropriate people to the Cc when replying regarding one
> > of these issues.
> >
> >
> > Subject : usb_submit_urb(ctrl) failed on 2.6.16-rc4-git10 kernel
> > References : http://bugzilla.kernel.org/show_bug.cgi?id=6134
> > Submitter : Ryan Phillips <rphillips@gentoo.org>
> > Status : unknown
> >
> >
> *snipped
> > Subject : total ps2 keyboard lockup from boot
> > References : http://bugzilla.kernel.org/show_bug.cgi?id=6130
> > Submitter : Duncan <1i5t5.duncan@cox.net>
> > Handled-By : Dmitry Torokhov <dmitry.torokhov@gmail.com>
> > Pavlik Vojtech <vojtech@suse.cz>
> > Status : discussion and debugging in the bug logs
> >
> >
> *snipped
>
> It appears that Duncan's "total ps2 keyboard lockup from boot" is the
> same, or similar problem as mine.
> 2.6.15.1 kernel is working for me though.
Except one of the keyboards is USB and the other PS/2. Both are
Microsoft wireless, though.
--
Vojtech Pavlik
Director SuSE Labs
^ permalink raw reply [flat|nested] 62+ messages in thread
* Re: 2.6.16-rc5: known regressions (ps2 mouse/keyboard issues)
2006-02-27 6:39 ` Vojtech Pavlik
@ 2006-02-27 9:14 ` Duncan
0 siblings, 0 replies; 62+ messages in thread
From: Duncan @ 2006-02-27 9:14 UTC (permalink / raw)
To: Vojtech Pavlik
Cc: Ryan Phillips, linux-kernel, Linus Torvalds, Andrew Morton,
Tom Seeley, Dave Jones, Jiri Slaby, michael, mchehab,
v4l-dvb-maintainer, video4linux-list, Brian Marete,
Ryan Phillips, gregkh, linux-usb-devel, Sanjoy Mahajan,
Luming Yu, len.brown, linux-acpi, Mark Lord, Randy Dunlap,
jgarzik, linux-ide, linux-input, Meelis Roos
On Sunday 26 February 2006 23:39, Vojtech Pavlik wrote:
> On Sun, Feb 26, 2006 at 10:26:41PM -0800, Ryan Phillips wrote:
> > Adrian Bunk wrote:
> > > This email lists some known regressions in 2.6.16-rc5 compared to
> > > 2.6.15.
[snip]
> > > Subject : usb_submit_urb(ctrl) failed on 2.6.16-rc4-git10 kernel
> > > References : http://bugzilla.kernel.org/show_bug.cgi?id=6134
> > > Submitter : Ryan Phillips <rphillips@gentoo.org>
> > > Status : unknown
[snip]
> > > Subject : total ps2 keyboard lockup from boot
> > > References : http://bugzilla.kernel.org/show_bug.cgi?id=6130
> > > Submitter : Duncan <1i5t5.duncan@cox.net>
> > > Handled-By : Dmitry Torokhov <dmitry.torokhov@gmail.com>
> > > Pavlik Vojtech <vojtech@suse.cz>
> > > Status : discussion and debugging in the bug logs
> >
> > It appears that Duncan's "total ps2 keyboard lockup from boot" is the
> > same, or similar problem as mine.
> > 2.6.15.1 kernel is working for me though.
>
> Except one of the keyboards is USB and the other PS/2. Both are
> Microsoft wireless, though.
As Ryan observes in his bug, the keyboard and mouse were both plugged into the
ps2 ports. Same keyboard, both amd64, both with both the mouse and keyboard
plugged into the ps2 ports, both with a dead keyboard before rc1. As he says,
evidence suggests it is indeed the same bug. Also, we're both on Gentoo, but
that could simply be due to the fact that Gentoo folks are probably more
likely to be running rc or even git kernels than most, due to the type of
distribution it is and GregKH's recently adding mainline git snapshots to the
package tree to encourage quicker testing.
One discrepancy so far: Ryan mentions git10, implying it failed for him, while
git10 works here but git11 fails. My guess is that the USB error he
originally keyed in on, that turned out to be happening with working kernels
too, sent him down the wrong path, and git10 will end up working for him.
Either that or the root issue is something that changed in git10, and then
again in git11, killing his one day and mine the next, due to the mobo
differences or something.
--
Duncan - Plain text mail please, HTML mail filtered as spam
"They that can give up essential liberty to obtain a little
temporary safety, deserve neither liberty nor safety."
Benjamin Franklin
^ permalink raw reply [flat|nested] 62+ messages in thread
* Re: 2.6.16-rc5: known regressions
2006-02-27 6:13 ` 2.6.16-rc5: known regressions Adrian Bunk
2006-02-27 6:26 ` Ryan Phillips
@ 2006-02-27 6:54 ` Jeff Garzik
2006-02-27 7:08 ` Adrian Bunk
2006-02-27 13:36 ` Mark Lord
` (2 subsequent siblings)
4 siblings, 1 reply; 62+ messages in thread
From: Jeff Garzik @ 2006-02-27 6:54 UTC (permalink / raw)
To: linux-kernel
Cc: Linus Torvalds, Andrew Morton, Tom Seeley, Dave Jones,
Jiri Slaby, michael, mchehab, v4l-dvb-maintainer,
video4linux-list, Brian Marete, Ryan Phillips, gregkh,
linux-usb-devel, Sanjoy Mahajan, Luming Yu, len.brown,
linux-acpi, Mark Lord, Randy Dunlap, linux-ide, Duncan,
Pavlik Vojtech, linux-input, Meelis Roos
Adrian Bunk wrote:
> Subject : 2.6.16-rc[34]: resume-from-RAM unreliable (SATA)
> References : http://lkml.org/lkml/2006/2/20/159
> Submitter : Mark Lord <lkml@rtr.ca>
> Handled-By : Randy Dunlap <rdunlap@xenotime.net>
> Status : one of Randy's patches seems to fix it
This is not a regression, libata suspend/resume has always been crappy.
It's under active development (by Randy, among others) to fix this.
Jeff
^ permalink raw reply [flat|nested] 62+ messages in thread* Re: 2.6.16-rc5: known regressions
2006-02-27 6:54 ` 2.6.16-rc5: known regressions Jeff Garzik
@ 2006-02-27 7:08 ` Adrian Bunk
2006-02-28 9:40 ` Jens Axboe
0 siblings, 1 reply; 62+ messages in thread
From: Adrian Bunk @ 2006-02-27 7:08 UTC (permalink / raw)
To: Jeff Garzik
Cc: linux-kernel, Linus Torvalds, Andrew Morton, Mark Lord,
Randy Dunlap, linux-ide
On Mon, Feb 27, 2006 at 01:54:17AM -0500, Jeff Garzik wrote:
> Adrian Bunk wrote:
> >Subject : 2.6.16-rc[34]: resume-from-RAM unreliable (SATA)
> >References : http://lkml.org/lkml/2006/2/20/159
> >Submitter : Mark Lord <lkml@rtr.ca>
> >Handled-By : Randy Dunlap <rdunlap@xenotime.net>
> >Status : one of Randy's patches seems to fix it
>
>
> This is not a regression, libata suspend/resume has always been crappy.
> It's under active development (by Randy, among others) to fix this.
It might have always been crappy, but it is a regression since
according to the submitter it is working with 2.6.15.
> Jeff
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
^ permalink raw reply [flat|nested] 62+ messages in thread* Re: 2.6.16-rc5: known regressions
2006-02-27 7:08 ` Adrian Bunk
@ 2006-02-28 9:40 ` Jens Axboe
2006-03-01 0:17 ` Randy.Dunlap
0 siblings, 1 reply; 62+ messages in thread
From: Jens Axboe @ 2006-02-28 9:40 UTC (permalink / raw)
To: Adrian Bunk
Cc: Jeff Garzik, linux-kernel, Linus Torvalds, Andrew Morton,
Mark Lord, Randy Dunlap, linux-ide
On Mon, Feb 27 2006, Adrian Bunk wrote:
> On Mon, Feb 27, 2006 at 01:54:17AM -0500, Jeff Garzik wrote:
> > Adrian Bunk wrote:
> > >Subject : 2.6.16-rc[34]: resume-from-RAM unreliable (SATA)
> > >References : http://lkml.org/lkml/2006/2/20/159
> > >Submitter : Mark Lord <lkml@rtr.ca>
> > >Handled-By : Randy Dunlap <rdunlap@xenotime.net>
> > >Status : one of Randy's patches seems to fix it
> >
> >
> > This is not a regression, libata suspend/resume has always been crappy.
> > It's under active development (by Randy, among others) to fix this.
>
> It might have always been crappy, but it is a regression since
> according to the submitter it is working with 2.6.15.
It might have worked under lucky circumstances with an idle disk and a
goat sacrifice, so I agree with Jeff that this is definitely not a
regression. To my knowledge, Mark always used my libata suspend patch on
earlier kernels so it's not even an apples-apples comparison.
So please scratch that entry.
--
Jens Axboe
^ permalink raw reply [flat|nested] 62+ messages in thread
* Re: 2.6.16-rc5: known regressions
2006-02-28 9:40 ` Jens Axboe
@ 2006-03-01 0:17 ` Randy.Dunlap
2006-03-04 13:18 ` Adrian Bunk
0 siblings, 1 reply; 62+ messages in thread
From: Randy.Dunlap @ 2006-03-01 0:17 UTC (permalink / raw)
To: Jens Axboe; +Cc: bunk, jgarzik, linux-kernel, torvalds, akpm, lkml, linux-ide
On Tue, 28 Feb 2006 10:40:53 +0100 Jens Axboe wrote:
> On Mon, Feb 27 2006, Adrian Bunk wrote:
> > On Mon, Feb 27, 2006 at 01:54:17AM -0500, Jeff Garzik wrote:
> > > Adrian Bunk wrote:
> > > >Subject : 2.6.16-rc[34]: resume-from-RAM unreliable (SATA)
> > > >References : http://lkml.org/lkml/2006/2/20/159
> > > >Submitter : Mark Lord <lkml@rtr.ca>
> > > >Handled-By : Randy Dunlap <rdunlap@xenotime.net>
> > > >Status : one of Randy's patches seems to fix it
> > >
> > >
> > > This is not a regression, libata suspend/resume has always been crappy.
> > > It's under active development (by Randy, among others) to fix this.
> >
> > It might have always been crappy, but it is a regression since
> > according to the submitter it is working with 2.6.15.
>
> It might have worked under lucky circumstances with an idle disk and a
> goat sacrifice, so I agree with Jeff that this is definitely not a
> regression. To my knowledge, Mark always used my libata suspend patch on
> earlier kernels so it's not even an apples-apples comparison.
>
> So please scratch that entry.
I'll third that request/comment.
---
~Randy
^ permalink raw reply [flat|nested] 62+ messages in thread
* Re: 2.6.16-rc5: known regressions
2006-03-01 0:17 ` Randy.Dunlap
@ 2006-03-04 13:18 ` Adrian Bunk
0 siblings, 0 replies; 62+ messages in thread
From: Adrian Bunk @ 2006-03-04 13:18 UTC (permalink / raw)
To: Randy.Dunlap
Cc: Jens Axboe, jgarzik, linux-kernel, torvalds, akpm, lkml, linux-ide
On Tue, Feb 28, 2006 at 04:17:25PM -0800, Randy.Dunlap wrote:
> On Tue, 28 Feb 2006 10:40:53 +0100 Jens Axboe wrote:
>
> > On Mon, Feb 27 2006, Adrian Bunk wrote:
> > > On Mon, Feb 27, 2006 at 01:54:17AM -0500, Jeff Garzik wrote:
> > > > Adrian Bunk wrote:
> > > > >Subject : 2.6.16-rc[34]: resume-from-RAM unreliable (SATA)
> > > > >References : http://lkml.org/lkml/2006/2/20/159
> > > > >Submitter : Mark Lord <lkml@rtr.ca>
> > > > >Handled-By : Randy Dunlap <rdunlap@xenotime.net>
> > > > >Status : one of Randy's patches seems to fix it
> > > >
> > > >
> > > > This is not a regression, libata suspend/resume has always been crappy.
> > > > It's under active development (by Randy, among others) to fix this.
> > >
> > > It might have always been crappy, but it is a regression since
> > > according to the submitter it is working with 2.6.15.
> >
> > It might have worked under lucky circumstances with an idle disk and a
> > goat sacrifice, so I agree with Jeff that this is definitely not a
> > regression. To my knowledge, Mark always used my libata suspend patch on
> > earlier kernels so it's not even an apples-apples comparison.
> >
> > So please scratch that entry.
>
> I'll third that request/comment.
OK, done.
> ~Randy
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
^ permalink raw reply [flat|nested] 62+ messages in thread
* Re: 2.6.16-rc5: known regressions
2006-02-27 6:13 ` 2.6.16-rc5: known regressions Adrian Bunk
2006-02-27 6:26 ` Ryan Phillips
2006-02-27 6:54 ` 2.6.16-rc5: known regressions Jeff Garzik
@ 2006-02-27 13:36 ` Mark Lord
2006-02-27 14:09 ` Pavel Machek
2006-03-02 14:00 ` [v4l-dvb-maintainer] " Mauro Carvalho Chehab
4 siblings, 0 replies; 62+ messages in thread
From: Mark Lord @ 2006-02-27 13:36 UTC (permalink / raw)
To: linux-kernel
Cc: Linus Torvalds, Andrew Morton, Tom Seeley, Dave Jones,
Jiri Slaby, michael, mchehab, v4l-dvb-maintainer,
video4linux-list, Brian Marete, Ryan Phillips, gregkh,
linux-usb-devel, Sanjoy Mahajan, Luming Yu, len.brown,
linux-acpi, Randy Dunlap, jgarzik, linux-ide, Duncan,
Pavlik Vojtech, linux-input, Meelis Roos
Adrian Bunk wrote:
>
> Subject : 2.6.16-rc[34]: resume-from-RAM unreliable (SATA)
> References : http://lkml.org/lkml/2006/2/20/159
> Submitter : Mark Lord <lkml@rtr.ca>
> Handled-By : Randy Dunlap <rdunlap@xenotime.net>
> Status : one of Randy's patches seems to fix it
I'm not certain about this. It may also have been broken in 2.6.15,
but it (resume) did work fine with 2.6.14. I've been using Randy's
patches with both 2.6.15 (since -rc?), and 2.6.16-rc.
Cheers
^ permalink raw reply [flat|nested] 62+ messages in thread
* Re: 2.6.16-rc5: known regressions
2006-02-27 6:13 ` 2.6.16-rc5: known regressions Adrian Bunk
` (2 preceding siblings ...)
2006-02-27 13:36 ` Mark Lord
@ 2006-02-27 14:09 ` Pavel Machek
2006-03-02 14:00 ` [v4l-dvb-maintainer] " Mauro Carvalho Chehab
4 siblings, 0 replies; 62+ messages in thread
From: Pavel Machek @ 2006-02-27 14:09 UTC (permalink / raw)
To: linux-kernel
Cc: Linus Torvalds, Andrew Morton, Tom Seeley, Dave Jones,
Jiri Slaby, michael, mchehab, v4l-dvb-maintainer,
video4linux-list, Brian Marete, Ryan Phillips, gregkh,
linux-usb-devel, Sanjoy Mahajan, Luming Yu, len.brown,
linux-acpi, Mark Lord, Randy Dunlap, jgarzik, linux-ide, Duncan,
Pavlik Vojtech, linux-input, Meelis Roos
On Mon 27-02-06 07:13:54, Adrian Bunk wrote:
>
> Subject : S3 sleep hangs the second time - 600X
> References : http://bugzilla.kernel.org/show_bug.cgi?id=5989
> Submitter : Sanjoy Mahajan <sanjoy@mrao.cam.ac.uk>
> Handled-By : Luming Yu <luming.yu@intel.com>
> Status : is being debugged,
> we might want to change the default back for 2.6.16:
> http://lkml.org/lkml/2006/2/25/101
Luming's call, but ec_intr apparently fixed some machines, too.s
> Subject : 2.6.16-rc[34]: resume-from-RAM unreliable (SATA)
> References : http://lkml.org/lkml/2006/2/20/159
> Submitter : Mark Lord <lkml@rtr.ca>
> Handled-By : Randy Dunlap <rdunlap@xenotime.net>
> Status : one of Randy's patches seems to fix it
Is this really regression?
--
Thanks, Sharp!
^ permalink raw reply [flat|nested] 62+ messages in thread* Re: [v4l-dvb-maintainer] 2.6.16-rc5: known regressions
2006-02-27 6:13 ` 2.6.16-rc5: known regressions Adrian Bunk
` (3 preceding siblings ...)
2006-02-27 14:09 ` Pavel Machek
@ 2006-03-02 14:00 ` Mauro Carvalho Chehab
2006-03-04 13:27 ` Adrian Bunk
[not found] ` <6dd519ae0603080313o4e7b8a61h5002125c33a0e008@mail.gmail.com>
4 siblings, 2 replies; 62+ messages in thread
From: Mauro Carvalho Chehab @ 2006-03-02 14:00 UTC (permalink / raw)
To: linux-kernel
Cc: Linus Torvalds, Andrew Morton, video4linux-list, Jiri Slaby,
Ryan Phillips, linux-ide, Randy Dunlap, linux-input,
linux-usb-devel, Meelis Roos, Luming Yu, linux-acpi,
Pavlik Vojtech, Sanjoy Mahajan, jgarzik, len.brown, Brian Marete,
Dave Jones, v4l-dvb-maintainer, Duncan, Tom Seeley, michael,
gregkh, Mark Lord
> Subject : Oops in Kernel 2.6.16-rc4 on Modprobe of saa7134.ko
> References : http://lkml.org/lkml/2006/2/20/122
> Submitter : Brian Marete <bgmarete@gmail.com>
> Status : unknown
This is not a regression, since the user is not configuring saa7134 with
the right card.
Cheers,
Mauro.
^ permalink raw reply [flat|nested] 62+ messages in thread* Re: [v4l-dvb-maintainer] 2.6.16-rc5: known regressions
2006-03-02 14:00 ` [v4l-dvb-maintainer] " Mauro Carvalho Chehab
@ 2006-03-04 13:27 ` Adrian Bunk
2006-03-04 13:39 ` Mauro Carvalho Chehab
[not found] ` <6dd519ae0603080313o4e7b8a61h5002125c33a0e008@mail.gmail.com>
1 sibling, 1 reply; 62+ messages in thread
From: Adrian Bunk @ 2006-03-04 13:27 UTC (permalink / raw)
To: Mauro Carvalho Chehab
Cc: linux-kernel, Linus Torvalds, Andrew Morton, video4linux-list,
Brian Marete, v4l-dvb-maintainer
On Thu, Mar 02, 2006 at 11:00:11AM -0300, Mauro Carvalho Chehab wrote:
>
> > Subject : Oops in Kernel 2.6.16-rc4 on Modprobe of saa7134.ko
> > References : http://lkml.org/lkml/2006/2/20/122
> > Submitter : Brian Marete <bgmarete@gmail.com>
> > Status : unknown
>
> This is not a regression, since the user is not configuring saa7134 with
> the right card.
Thanks for this information.
The Oops is still a problem that should IMHO be fixed, but I removed
this issue from my regressions list.
> Cheers,
> Mauro.
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
^ permalink raw reply [flat|nested] 62+ messages in thread[parent not found: <6dd519ae0603080313o4e7b8a61h5002125c33a0e008@mail.gmail.com>]
* Re: [v4l-dvb-maintainer] 2.6.16-rc5: known regressions
[not found] ` <6dd519ae0603080313o4e7b8a61h5002125c33a0e008@mail.gmail.com>
@ 2006-03-08 20:29 ` Mauro Carvalho Chehab
2006-03-08 22:52 ` Hartmut Hackmann
0 siblings, 1 reply; 62+ messages in thread
From: Mauro Carvalho Chehab @ 2006-03-08 20:29 UTC (permalink / raw)
To: Brian Marete
Cc: video4linux-list, v4l-dvb-maintainer, linux-kernel, Adrian Bunk
Wow! Lots of people being c/c here! Since all pertinent guys are at
lkml, I've just removed all those spam, keeping copied just the lists,
and Adrian, who warned me about it.
Em Qua, 2006-03-08 às 14:13 +0300, Brian Marete escreveu:
> What you say is quite correct.
>
> However, my card is not known by the driver, and `card=3' has been working
> for me all the while, with no problems at all. In any case, removing
> `disable_ir=1' from the insmod options hides the problem for me. By the way,
> that option was there since in an an earlier -rc, loading the driver without
> it would cause an oops.
The option disable_ir is, in fact, a workaround. If this is not needed
anymore, this is a progress ;) Anyway, having an OOPS is really bad. We
should go further to avoid oops on it.
IR on some saa7134 cards are really a trouble. Sometimes, it just
generates lots of weird events, since you are gathering a generic io
port (GPIO) from hardware to generate keypressing. Using the wrong port
may generate troubles at the system, by sending wrong events to input.
With a wrong card, if somebody fixed the IR, it may broke for your
board.
>
> If there are any hints about how I might discover the correct parameters for
> my card to be added to `saa7134-cards.c' I would love to hear them.
> I am tired of the FM radio not working anyway. Next time, I will make sure to
> avoid the cheap, brand less cards made in God Knows Where :)
El Cheapo boards are difficult to support. Most of they don't offer an
unique PCI ID. Others are just OEM cards. The same card is selled on
several different markets with different brand names (sometimes with
different GPIO ports and/or tuners).
For you to include it at kernel, you need to discover gpio ports used on
it. There are some wiki pages at http://linuxtv.org explaining the
process of identifying it using dscaler for m$. Dscaler is a freeware,
and have a small app, called regspy, that enables reading what windoze
is programming at some devices. For more details, please look at:
http://linuxtv.org/v4lwiki/index.php/GPIO_pins
>
> Thanks,
> Brian Marete.
>
> On 3/2/06, Mauro Carvalho Chehab <mchehab@infradead.org> wrote:
> >
> >
> > > Subject : Oops in Kernel 2.6.16-rc4 on Modprobe of saa7134.ko
> > > References : http://lkml.org/lkml/2006/2/20/122
> > > Submitter : Brian Marete <bgmarete@gmail.com>
> > > Status : unknown
> >
> > This is not a regression, since the user is not configuring saa7134 with
> > the right card.
> >
> > Cheers,
> > Mauro.
> >
> >
>
>
> --
> B. Gitonga Marete
> Tel: +254-722-151-590
> _______________________________________________
> v4l-dvb-maintainer mailing list
> v4l-dvb-maintainer@linuxtv.org
> http://www.linuxtv.org/cgi-bin/mailman/listinfo/v4l-dvb-maintainer
Cheers,
Mauro.
^ permalink raw reply [flat|nested] 62+ messages in thread* Re: [v4l-dvb-maintainer] 2.6.16-rc5: known regressions
2006-03-08 20:29 ` Mauro Carvalho Chehab
@ 2006-03-08 22:52 ` Hartmut Hackmann
0 siblings, 0 replies; 62+ messages in thread
From: Hartmut Hackmann @ 2006-03-08 22:52 UTC (permalink / raw)
To: Linux and Kernel Video
Cc: Brian Marete, Adrian Bunk, v4l-dvb-maintainer, linux-kernel
Hi, Brian
Mauro Carvalho Chehab wrote:
> Wow! Lots of people being c/c here! Since all pertinent guys are at
> lkml, I've just removed all those spam, keeping copied just the lists,
> and Adrian, who warned me about it.
>
> Em Qua, 2006-03-08 às 14:13 +0300, Brian Marete escreveu:
>
>>What you say is quite correct.
>>
>>However, my card is not known by the driver, and `card=3' has been working
>>for me all the while, with no problems at all. In any case, removing
>>`disable_ir=1' from the insmod options hides the problem for me. By the way,
>>that option was there since in an an earlier -rc, loading the driver without
>>it would cause an oops.
>
> The option disable_ir is, in fact, a workaround. If this is not needed
> anymore, this is a progress ;) Anyway, having an OOPS is really bad. We
> should go further to avoid oops on it.
>
> IR on some saa7134 cards are really a trouble. Sometimes, it just
> generates lots of weird events, since you are gathering a generic io
> port (GPIO) from hardware to generate keypressing. Using the wrong port
> may generate troubles at the system, by sending wrong events to input.
> With a wrong card, if somebody fixed the IR, it may broke for your
> board.
<snip>
I tried to reproduce your problem but i didn't succeed yet. I also think
that the IR support could be the problem. Card 3 defines a GPIO based
remote support. As Mauro mentioned above, this is - at least - dangerous
if you force this card type but you don't have a remote control or just a
different one. This type of remote can use a GPIO port of the SAA713x to
generate interrupts. If this pin is floating on your card, the driver can
just be flooded with IRQs. We should have a look whether we can prevent this
in the IRQ handler.
Best regards
Hartmut
^ permalink raw reply [flat|nested] 62+ messages in thread
* Re: Linux v2.6.16-rc5
2006-02-27 5:27 Linux v2.6.16-rc5 Linus Torvalds
2006-02-27 5:51 ` Jeff Garzik
2006-02-27 6:13 ` 2.6.16-rc5: known regressions Adrian Bunk
@ 2006-02-27 7:28 ` Dave Jones
2006-02-27 11:20 ` Jens Axboe
2006-02-27 7:42 ` Dave Jones
` (7 subsequent siblings)
10 siblings, 1 reply; 62+ messages in thread
From: Dave Jones @ 2006-02-27 7:28 UTC (permalink / raw)
To: Linus Torvalds; +Cc: Linux Kernel Mailing List
On Sun, Feb 26, 2006 at 09:27:28PM -0800, Linus Torvalds wrote:
> Have I missed anything? Holler. And please keep reminding about any
> regressions since 2.6.15.
We seem to have a nasty bio slab leak.
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=183017
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=182970
Two seperate reports, both using raid1, sata_via and firewire
Curiously, they're both on x86-64 too.
Will keep an eye open for other reports of this as they come in.
(The kernels they mention in those reports are fairly recent.
2.6.15-1.1977_FC5 is ctually based on 2.6.16rc4-git6)
Dave
^ permalink raw reply [flat|nested] 62+ messages in thread* Re: Linux v2.6.16-rc5
2006-02-27 7:28 ` Linux v2.6.16-rc5 Dave Jones
@ 2006-02-27 11:20 ` Jens Axboe
2006-02-27 22:42 ` Neil Brown
0 siblings, 1 reply; 62+ messages in thread
From: Jens Axboe @ 2006-02-27 11:20 UTC (permalink / raw)
To: Dave Jones, Linus Torvalds, Linux Kernel Mailing List; +Cc: neilb
On Mon, Feb 27 2006, Dave Jones wrote:
> On Sun, Feb 26, 2006 at 09:27:28PM -0800, Linus Torvalds wrote:
>
> > Have I missed anything? Holler. And please keep reminding about any
> > regressions since 2.6.15.
>
> We seem to have a nasty bio slab leak.
> https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=183017
> https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=182970
>
> Two seperate reports, both using raid1, sata_via and firewire
> Curiously, they're both on x86-64 too.
>
> Will keep an eye open for other reports of this as they come in.
>
> (The kernels they mention in those reports are fairly recent.
> 2.6.15-1.1977_FC5 is ctually based on 2.6.16rc4-git6)
This smells very much like a raid1 bio leak, I thought Neil had
diagnosed and fixed that already though - Neil?
--
Jens Axboe
^ permalink raw reply [flat|nested] 62+ messages in thread
* Re: Linux v2.6.16-rc5
2006-02-27 11:20 ` Jens Axboe
@ 2006-02-27 22:42 ` Neil Brown
0 siblings, 0 replies; 62+ messages in thread
From: Neil Brown @ 2006-02-27 22:42 UTC (permalink / raw)
To: Jens Axboe; +Cc: Dave Jones, Linus Torvalds, Linux Kernel Mailing List
On Monday February 27, axboe@suse.de wrote:
> On Mon, Feb 27 2006, Dave Jones wrote:
> > On Sun, Feb 26, 2006 at 09:27:28PM -0800, Linus Torvalds wrote:
> >
> > > Have I missed anything? Holler. And please keep reminding about any
> > > regressions since 2.6.15.
> >
> > We seem to have a nasty bio slab leak.
> > https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=183017
> > https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=182970
> >
> > Two seperate reports, both using raid1, sata_via and firewire
> > Curiously, they're both on x86-64 too.
> >
> > Will keep an eye open for other reports of this as they come in.
> >
> > (The kernels they mention in those reports are fairly recent.
> > 2.6.15-1.1977_FC5 is ctually based on 2.6.16rc4-git6)
>
> This smells very much like a raid1 bio leak, I thought Neil had
> diagnosed and fixed that already though - Neil?
It certainly does smell like a raid1 bio leak, and we have had those
before, but I've looked over the relevant code several time and cannot
find one. And my test machine doesn't show a leak.
There are some different code paths depending on whether the
underlying devices support BIO_RW_BARRIER or not, so my testing isn't
conclusive - I think my devices do support BIO_RW_BARRIER so it could
just happen where BIO_RW_BARRIER isn't supported .... but the code
still looks good.
There are new code paths to handle auto-correcting read errors, and
they probably haven't been exercises as much as I would like (some,
but not lots and lots) so maybe there is an issue there, but nobody is
reporting disk errors along with the bio leak, and given the size of
the leak, it would need to be lots of errors.
I think we need to narrow down where the problem was introduced. The
current:
2.6.14.7 works,
2.6.16-rc4 doesn't
is too broad.
NeilBrown
^ permalink raw reply [flat|nested] 62+ messages in thread
* Re: Linux v2.6.16-rc5
2006-02-27 5:27 Linux v2.6.16-rc5 Linus Torvalds
` (2 preceding siblings ...)
2006-02-27 7:28 ` Linux v2.6.16-rc5 Dave Jones
@ 2006-02-27 7:42 ` Dave Jones
2006-02-27 9:28 ` Nick Piggin
2006-02-27 19:52 ` Rene Herman
` (6 subsequent siblings)
10 siblings, 1 reply; 62+ messages in thread
From: Dave Jones @ 2006-02-27 7:42 UTC (permalink / raw)
To: Linus Torvalds; +Cc: Linux Kernel Mailing List
On Sun, Feb 26, 2006 at 09:27:28PM -0800, Linus Torvalds wrote:
>
> The tar-ball is being uploaded right now, and everything else should
> already be pushed out. Mirroring might take a while, of course.
>
> There's not much to say about this: people have been pretty good, and it's
> just a random collection of fixes in various random areas. The shortlog is
> actually pretty short, and it really describes the updates better than
> anything else.
>
> Have I missed anything? Holler. And please keep reminding about any
> regressions since 2.6.15.
Those brave Fedora-rawhide testers have also hit an assortment of slab
related errors recently, manifesting in various ways including our old
friend the negative page_mapcount.
(From a 2.6.16rc4-git6 based kernel ...)
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=182593
Unable to handle kernel paging request at virtual address 6363665f
printing eip:
00800000
*pde = 6b6b6b6b
Oops: 0000 [#1]
SMP
last sysfs file: /block/hda/hda1/size
Modules linked in: ppdev autofs4 sunrpc ip_conntrack_netbios_ns ipt_REJECT
xt_state ip_conntrack nfnetlink xt_tcpudp iptable_filter ip_tables x_tables
video button battery ac ipv6 lp parport_pc parport floppy nvram sg sd_mod
usb_storage scsi_mod ehci_hcd uhci_hcd natsemi snd_intel8x0 snd_ac97_codec
snd_ac97_bus snd_seq_dummy snd_seq_oss snd_seq_midi_event snd_seq snd_seq_device
snd_pcm_oss snd_mixer_oss snd_pcm snd_timer snd hw_random i2c_i801 soundcore
i2c_core snd_page_alloc dm_snapshot dm_zero dm_mirror dm_mod ext3 jbd
CPU: 1
EIP: 0060:[<00800000>] Not tainted VLI
EFLAGS: 00210292 (2.6.15-1.1975_FC5smp #1)
EIP is at 0x800000
eax: 00000000 ebx: f7db2200 ecx: f0a6df5c edx: 00000010
esi: f7db2030 edi: f14e5004 ebp: 00000000 esp: f0a6dfa8
ds: 007b es: 007b ss: 0068
Process gnome-settings- (pid: 2565, threadinfo=f0a6d000 task=f1e23290)
Stack: <0>00000001 00000003 bff1f7f4 08966978 c0103d39 00000003 0000541b bff1f7f4
bff1f7f4 08966978 bff1f7a8 ffffffda c010007b 0000007b 00000036 001a5402
00000073 00200216 bff1f784 0000007b 00000000 00000000
Call Trace:
[<c0103d39>] syscall_call+0x7/0xb <0>Code: Bad EIP value.
kernel: slab error in cache_free_debugcheck(): cache `size-32': double free, or memory outside object was overwritten
kernel: [<c015fbc4>] cache_free_debugcheck+0xce/0x1b9 [<c0160b79>] free_block+0x141/0x17d
kernel: [<c0161619>] kmem_cache_free+0x2a/0x5c [<c0160b79>] free_block+0x141/0x17d
kernel: [<c0160c24>] drain_array_locked+0x6f/0x90 [<c0160cb9>] cache_reap+0x74/0x29c
kernel: [<c0131108>] run_workqueue+0x7f/0xba [<c0160c45>] cache_reap+0x0/0x29c
kernel: [<c01318f5>] worker_thread+0x0/0x117 [<c01319db>] worker_thread+0xe6/0x117
kernel: [<c011d6ab>] default_wake_function+0x0/0xc [<c0134149>] kthread+0x9d/0xc9
kernel: [<c01340ac>] kthread+0x0/0xc9 [<c0102005>]kernel_thread_helper+0x5/0xb
kernel: ee9979ac: redzone 1: 0x160fc2a5, redzone 2: 0x170fc2a5.
kernel: Eeek! page_mapcount(page) went negative! (-1)
kernel: page->flags = c001006c
kernel: page->count = 1
kernel: page->mapping = f68f1c00
kernel: ------------[ cut here ]------------
kernel: kernel BUG at mm/rmap.c:555!
There's a bunch more reports of slab related problems, but they're mostly against
kernels from a few weeks back, I'm trying to weed through them and get them
retested on current builds.
Dave
^ permalink raw reply [flat|nested] 62+ messages in thread* Re: Linux v2.6.16-rc5
2006-02-27 7:42 ` Dave Jones
@ 2006-02-27 9:28 ` Nick Piggin
0 siblings, 0 replies; 62+ messages in thread
From: Nick Piggin @ 2006-02-27 9:28 UTC (permalink / raw)
To: Dave Jones; +Cc: Linus Torvalds, Linux Kernel Mailing List
Dave Jones wrote:
> Those brave Fedora-rawhide testers have also hit an assortment of slab
> related errors recently, manifesting in various ways including our old
> friend the negative page_mapcount.
>
> (From a 2.6.16rc4-git6 based kernel ...)
> https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=182593
>
From that report, the page flags indicate that the page is regular
old pagecache. I'd be very surprised if there is a mapcount bug here.
It looks like something is scribbling in memory, which I would
suspect first.
However if you do see new mm/rmap bugs, do keep posting them so we
can see if there is a pattern.
--
SUSE Labs, Novell Inc.
Send instant messages to your online friends http://au.messenger.yahoo.com
^ permalink raw reply [flat|nested] 62+ messages in thread
* Re: Linux v2.6.16-rc5
2006-02-27 5:27 Linux v2.6.16-rc5 Linus Torvalds
` (3 preceding siblings ...)
2006-02-27 7:42 ` Dave Jones
@ 2006-02-27 19:52 ` Rene Herman
2006-02-27 22:51 ` Andrew Morton
2006-02-28 9:38 ` Linux v2.6.16-rc5 - regression Peter Hagervall
` (5 subsequent siblings)
10 siblings, 1 reply; 62+ messages in thread
From: Rene Herman @ 2006-02-27 19:52 UTC (permalink / raw)
To: Linus Torvalds; +Cc: Linux Kernel Mailing List, Andrew Morton, Adam Belay
Linus Torvalds wrote:
> Have I missed anything? Holler. And please keep reminding about any
> regressions since 2.6.15.
This one isn't in: http://lkml.org/lkml/2006/2/21/7
Andrew did pick it up -- pnp-bus-type-fix.patch, named as being in the
2.6.16 queue in his 2.6.16-rc4-mm2 announce:
http://lkml.org/lkml/2006/2/24/66
so it's probably okay. The other two patches from that same thread
already made it into -rc5 though, so thought I'd ping anyway. It does
really want to make 2.6.16. Many ISA-PnP drivers are quite severely
broken without (it's also a regression against 2.6.15).
Rene.
^ permalink raw reply [flat|nested] 62+ messages in thread* Re: Linux v2.6.16-rc5
2006-02-27 19:52 ` Rene Herman
@ 2006-02-27 22:51 ` Andrew Morton
2006-02-27 23:32 ` Rene Herman
0 siblings, 1 reply; 62+ messages in thread
From: Andrew Morton @ 2006-02-27 22:51 UTC (permalink / raw)
To: Rene Herman; +Cc: torvalds, linux-kernel, ambx1
Rene Herman <rene.herman@keyaccess.nl> wrote:
>
> Linus Torvalds wrote:
>
> > Have I missed anything? Holler. And please keep reminding about any
> > regressions since 2.6.15.
>
> This one isn't in: http://lkml.org/lkml/2006/2/21/7
>
> Andrew did pick it up -- pnp-bus-type-fix.patch, named as being in the
> 2.6.16 queue in his 2.6.16-rc4-mm2 announce:
>
> http://lkml.org/lkml/2006/2/24/66
>
> so it's probably okay. The other two patches from that same thread
> already made it into -rc5 though, so thought I'd ping anyway. It does
> really want to make 2.6.16. Many ISA-PnP drivers are quite severely
> broken without (it's also a regression against 2.6.15).
>
Problem is, that patch was just a "here, try this" thing which Adam slung
onto the mailing list - I have no idea whether it was compete or final or
whether he wants it in 2.6.16 or what. No indication of what problem it's
fixing, nor how, now what risk there is of breaking something else. It's
just a lonely little diff at present.
^ permalink raw reply [flat|nested] 62+ messages in thread
* Re: Linux v2.6.16-rc5
2006-02-27 22:51 ` Andrew Morton
@ 2006-02-27 23:32 ` Rene Herman
2006-02-28 1:05 ` Rene Herman
0 siblings, 1 reply; 62+ messages in thread
From: Rene Herman @ 2006-02-27 23:32 UTC (permalink / raw)
To: Andrew Morton; +Cc: torvalds, linux-kernel, ambx1
Andrew Morton wrote:
> Rene Herman <rene.herman@keyaccess.nl> wrote:
>> This one isn't in: http://lkml.org/lkml/2006/2/21/7
>>
>> Andrew did pick it up -- pnp-bus-type-fix.patch, named as being in the
>> 2.6.16 queue in his 2.6.16-rc4-mm2 announce:
>>
>> http://lkml.org/lkml/2006/2/24/66
>>
>> so it's probably okay. The other two patches from that same thread
>> already made it into -rc5 though, so thought I'd ping anyway. It does
>> really want to make 2.6.16. Many ISA-PnP drivers are quite severely
>> broken without (it's also a regression against 2.6.15).
>>
>
> Problem is, that patch was just a "here, try this" thing which Adam slung
> onto the mailing list - I have no idea whether it was compete or final or
> whether he wants it in 2.6.16 or what.
Adam? But something will need to go in. At the moment an entire bus
subsystem appears to be broken.
> No indication of what problem it's fixing, nor how, now what risk
> there is of breaking something else. It's just a lonely little diff
> at present.
The problem it fixed for me was that the CS4236 ALSA driver's private
PnP remove method was not being called at modprobe -r, which meant that
the card wasn't being freed at all, resulting in memory leaks, the
inability to reload the driver, and oopses, during modprobe -r and reboot.
All ALSA ISA card drivers, not just CS4236, use the same interface to
PnP (the pnp_card_driver struct) meaning they would all appear to be
broken in that exact same way as well. Or rather, _any_ ISA-PnP driver
using that pnp_card_driver interface (there's also drivers using the
pnp_driver interface -- those appear to be okay). CS4236 isn't doing
anything special...
The problem seems to be caused by the "bustype" driver model changes in
2.6.16, the same ones that made the sensors drivers complain about
private methods versus bustype methods which was fixed in -rc2. Adam
said that in fact not so much the teardown was broken, but the setup,
and the patch replaces a subsystem probe method with a bustype method.
As to the risk of it breaking anything else... I doubt it. Given that
the old method did not work _at all_ it seems this is simply the way to
do this.
Adam ofcourse is the PnP expert though...
Rene.
^ permalink raw reply [flat|nested] 62+ messages in thread
* Re: Linux v2.6.16-rc5
2006-02-27 23:32 ` Rene Herman
@ 2006-02-28 1:05 ` Rene Herman
2006-02-28 1:12 ` Andrew Morton
0 siblings, 1 reply; 62+ messages in thread
From: Rene Herman @ 2006-02-28 1:05 UTC (permalink / raw)
To: Andrew Morton; +Cc: torvalds, linux-kernel, ambx1
Rene Herman wrote:
> All ALSA ISA card drivers, not just CS4236, use the same interface to
> PnP (the pnp_card_driver struct) meaning they would all appear to be
> broken in that exact same way as well. Or rather, _any_ ISA-PnP driver
> using that pnp_card_driver interface (there's also drivers using the
> pnp_driver interface -- those appear to be okay). CS4236 isn't doing
> anything special...
If it helps any, I can at least confirm that it's nothing ALSA or CS4236
specific. This is a minimal, skeleton, pnp_card driver:
=== foo.c
#include <linux/kernel.h>
#include <linux/module.h>
#include <linux/pnp.h>
MODULE_LICENSE("GPL");
static struct pnp_card_device_id foo_pnp_card_device_id_table[] = {
{ .id = "CSCa836", .devs = { { "CSCa800" } } },
/* --- */
{ .id = "" }
};
MODULE_DEVICE_TABLE(pnp_card, foo_pnp_card_device_id_table);
static int foo_pnp_probe(struct pnp_card_link *pcard,
const struct pnp_card_device_id *pid)
{
struct pnp_dev *pdev;
printk(KERN_INFO "%s\n", __FUNCTION__);
pdev = pnp_request_card_device(pcard, pid->devs[0].id, NULL);
if (!pdev || pnp_activate_dev(pdev) < 0)
return -ENODEV;
// allocate, enable.
return 0;
}
static void foo_pnp_remove(struct pnp_card_link *pcard)
{
printk(KERN_INFO "%s\n", __FUNCTION__);
// disable, deallocate.
}
static struct pnp_card_driver foo_pnp_card_driver = {
.name = "foo",
.id_table = foo_pnp_card_device_id_table,
.flags = PNP_DRIVER_RES_DISABLE,
.probe = foo_pnp_probe,
.remove = foo_pnp_remove
};
int __init foo_init(void)
{
return pnp_register_card_driver(&foo_pnp_card_driver);
}
void __exit foo_exit(void)
{
pnp_unregister_card_driver(&foo_pnp_card_driver);
}
module_init(foo_init);
module_exit(foo_exit);
===
compile with
=== Makefile
ifneq ($(KERNELRELEASE),)
obj-m := foo.o
else
default:
$(MAKE) -C /lib/modules/$(shell uname -r)/build M=$(shell pwd)
clean:
$(MAKE) -C /lib/modules/$(shell uname -r)/build M=$(shell pwd)
clean
endif
===
This ofcourse needs ISA-PnP support in the kernel, and actually loading
it requires replacing the PnP IDs with IDs actually present (these are
from my CS4236 soundcard).
With 2.6.15.4 and with 2.6.16-rc with Adam's fix applied, an "insmod
foo.ko && rmmod foo" shows the following in dmesg (this needs the PnP
debug messages selectable in menuconfig):
pnp: the driver 'foo' has been registered
foo_pnp_probe
pnp: match found with the PnP device '01:01.00' and the driver 'foo'
pnp: Device 01:01.00 activated.
foo_pnp_remove
pnp: Device 01:01.00 disabled.
pnp: the driver 'foo' has been unregistered
which is as it should be. On 2.6.16-rc without Adam's fix, both the
"pnp: match found with" and the "foo_pnp_remove" lines are missing:
pnp: the driver 'foo' has been registered
foo_pnp_probe
pnp: Device 01:01.00 activated.
pnp: Device 01:01.00 disabled.
pnp: the driver 'foo' has been unregistered
Of course, with this skeleton driver that's not much of a problem, but
in real drivers it certainly is; in pnp_remove you'd deactivate and
deallocate anything that was allocated and activated in/through the
pnp_probe method -- all things associated with this instance of the
card, normally.
I can also confirm that a driver using the "pnp_driver" interface isn't
affected by the bug. Same skeleton-type driver:
=== bar.c
#include <linux/kernel.h>
#include <linux/module.h>
#include <linux/pnp.h>
MODULE_LICENSE("GPL");
static struct pnp_device_id bar_pnp_device_id_table[] = {
{ .id = "CSCa800" },
/* --- */
{ .id = "" }
};
MODULE_DEVICE_TABLE(pnp, bar_pnp_device_id_table);
static int bar_pnp_probe(struct pnp_dev *pdev,
const struct pnp_device_id *pid)
{
printk(KERN_INFO "%s\n", __FUNCTION__);
if (pnp_activate_dev(pdev) < 0)
return -ENODEV;
// allocate, enable.
return 0;
}
static void bar_pnp_remove(struct pnp_dev *pdev)
{
printk(KERN_INFO "%s\n", __FUNCTION__);
// disable, deallocate.
}
static struct pnp_driver bar_pnp_driver = {
.name = "bar",
.id_table = bar_pnp_device_id_table,
.flags = PNP_DRIVER_RES_DISABLE,
.probe = bar_pnp_probe,
.remove = bar_pnp_remove
};
int __init bar_init(void)
{
return pnp_register_driver(&bar_pnp_driver);
}
void __exit bar_exit(void)
{
pnp_unregister_driver(&bar_pnp_driver);
}
module_init(bar_init);
module_exit(bar_exit);
===
2.6.15.4, 2.6.16-rc with or without Adam's fix:
pnp: the driver 'bar' has been registered
pnp: match found with the PnP device '01:01.00' and the driver 'bar'
bar_pnp_probe
pnp: Device 01:01.00 activated.
bar_pnp_remove
pnp: Device 01:01.00 disabled.
pnp: the driver 'bar' has been unregistered
So that's all fine. As said though, all ALSA drivers for one are using
the card_driver interface, and are therefore all broken currently.
Rene.
^ permalink raw reply [flat|nested] 62+ messages in thread* Re: Linux v2.6.16-rc5
2006-02-28 1:05 ` Rene Herman
@ 2006-02-28 1:12 ` Andrew Morton
0 siblings, 0 replies; 62+ messages in thread
From: Andrew Morton @ 2006-02-28 1:12 UTC (permalink / raw)
To: Rene Herman; +Cc: torvalds, linux-kernel, ambx1
Rene Herman <rene.herman@keyaccess.nl> wrote:
>
> On 2.6.16-rc without Adam's fix, both the
> "pnp: match found with" and the "foo_pnp_remove" lines are missing:
Useful, thanks. Hopefully we'll hear from Adam in the next day or two
(he's intermittent lately). If not, I guess we'll need to jam the patch in
anwyay.
In which case we might as well jam it in now, so we get more testing.
^ permalink raw reply [flat|nested] 62+ messages in thread
* Re: Linux v2.6.16-rc5 - regression
2006-02-27 5:27 Linux v2.6.16-rc5 Linus Torvalds
` (4 preceding siblings ...)
2006-02-27 19:52 ` Rene Herman
@ 2006-02-28 9:38 ` Peter Hagervall
2006-02-28 10:03 ` Andrew Morton
2006-02-28 12:43 ` Linux v2.6.16-rc5 Christoph Hellwig
` (4 subsequent siblings)
10 siblings, 1 reply; 62+ messages in thread
From: Peter Hagervall @ 2006-02-28 9:38 UTC (permalink / raw)
To: Linus Torvalds; +Cc: Linux Kernel Mailing List, akpm, garloff
In -rc5 the printk timing numbers do not reset to [ 0.000000] upon
boot. This worked in -rc4 and so I started bisecting and git came up
with:
commit 9827b781f20828e5ceb911b879f268f78fe90815
Author: Kurt Garloff <garloff@suse.de>
Date: Mon Feb 20 18:27:51 2006 -0800
[PATCH] OOM kill: children accounting
I can't see why that would break the timing information, but I'll just
assume that git was right, and tell you guys.
My system is:
Linux sap 2.6.16-rc4 #1 PREEMPT Mon Feb 20 13:34:18 CET 2006 i686
Intel(R) Pentium(R) 4 CPU 2.00GHz GenuineIntel GNU/Linux
Let me know if more information is needed.
Peter Hagervall
--
Peter Hagervall......................email: hager@cs.umu.se
Department of Computing Science........tel: +46(0)90 786 7018
University of Umeå, SE-901 87 Umeå.....fax: +46(0)90 786 6126
^ permalink raw reply [flat|nested] 62+ messages in thread* Re: Linux v2.6.16-rc5 - regression
2006-02-28 9:38 ` Linux v2.6.16-rc5 - regression Peter Hagervall
@ 2006-02-28 10:03 ` Andrew Morton
2006-02-28 11:41 ` Peter Hagervall
0 siblings, 1 reply; 62+ messages in thread
From: Andrew Morton @ 2006-02-28 10:03 UTC (permalink / raw)
To: Peter Hagervall; +Cc: torvalds, linux-kernel, garloff
Peter Hagervall <hager@cs.umu.se> wrote:
>
> In -rc5 the printk timing numbers do not reset to [ 0.000000] upon
> boot.
What numbers are you getting now?
> This worked in -rc4 and so I started bisecting and git came up
> with:
>
> commit 9827b781f20828e5ceb911b879f268f78fe90815
> Author: Kurt Garloff <garloff@suse.de>
> Date: Mon Feb 20 18:27:51 2006 -0800
>
> [PATCH] OOM kill: children accounting
>
> I can't see why that would break the timing information, but I'll just
> assume that git was right, and tell you guys.
Well yes, it'll be something else - perhaps some TSC change or something.
We'd need to know what architecture you're using...
Anwyay, these numbers aren't supposed to measure anything absolute like
uptime - they're purely for relative timing. It would be nice to get them
increasing monotonically from zero, but we wouldn't bust a gut to achieve
that - it's just a debugging thing.
^ permalink raw reply [flat|nested] 62+ messages in thread
* Re: Linux v2.6.16-rc5 - regression
2006-02-28 10:03 ` Andrew Morton
@ 2006-02-28 11:41 ` Peter Hagervall
2006-02-28 11:49 ` Peter Hagervall
0 siblings, 1 reply; 62+ messages in thread
From: Peter Hagervall @ 2006-02-28 11:41 UTC (permalink / raw)
To: Andrew Morton; +Cc: torvalds, linux-kernel, garloff
On Tue, Feb 28, 2006 at 02:03:36AM -0800, Andrew Morton wrote:
> Peter Hagervall <hager@cs.umu.se> wrote:
> >
> > In -rc5 the printk timing numbers do not reset to [ 0.000000] upon
> > boot.
>
> What numbers are you getting now?
>
[4294667.296000] and upwards.
> > This worked in -rc4 and so I started bisecting and git came up
> > with:
> >
> > commit 9827b781f20828e5ceb911b879f268f78fe90815
> > Author: Kurt Garloff <garloff@suse.de>
> > Date: Mon Feb 20 18:27:51 2006 -0800
> >
> > [PATCH] OOM kill: children accounting
> >
> > I can't see why that would break the timing information, but I'll just
> > assume that git was right, and tell you guys.
>
> Well yes, it'll be something else - perhaps some TSC change or something.
> We'd need to know what architecture you're using...
sap ~ $ cat /proc/cpuinfo
processor : 0
vendor_id : GenuineIntel
cpu family : 15
model : 2
model name : Intel(R) Pentium(R) 4 CPU 2.00GHz
stepping : 4
cpu MHz : 1994.176
cache size : 512 KB
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 2
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge
mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm
bogomips : 3992.49
>
> Anwyay, these numbers aren't supposed to measure anything absolute like
> uptime - they're purely for relative timing. It would be nice to get them
> increasing monotonically from zero, but we wouldn't bust a gut to achieve
> that - it's just a debugging thing.
Yeah, it's not a showstopper or anything, just thought I'd pipe up.
Peter Hagervall
--
Peter Hagervall......................email: hager@cs.umu.se
Department of Computing Science........tel: +46(0)90 786 7018
University of Umeå, SE-901 87 Umeå.....fax: +46(0)90 786 6126
^ permalink raw reply [flat|nested] 62+ messages in thread
* Re: Linux v2.6.16-rc5 - regression
2006-02-28 11:41 ` Peter Hagervall
@ 2006-02-28 11:49 ` Peter Hagervall
0 siblings, 0 replies; 62+ messages in thread
From: Peter Hagervall @ 2006-02-28 11:49 UTC (permalink / raw)
To: Andrew Morton; +Cc: torvalds, linux-kernel, garloff
> On Tue, Feb 28, 2006 at 02:03:36AM -0800, Andrew Morton wrote:
> >
> > Well yes, it'll be something else - perhaps some TSC change or something.
Looking closer I see that CONFIG_X86_PM_TIMER defaults to y in
2.6.16-rc5, whereas I have had it unset in earlier kernels.
This changed silently when I ran 'make oldconfig', and is most likely
the source of this "problem".
Peter Hagervall
--
Peter Hagervall......................email: hager@cs.umu.se
Department of Computing Science........tel: +46(0)90 786 7018
University of Umeå, SE-901 87 Umeå.....fax: +46(0)90 786 6126
^ permalink raw reply [flat|nested] 62+ messages in thread
* Re: Linux v2.6.16-rc5
2006-02-27 5:27 Linux v2.6.16-rc5 Linus Torvalds
` (5 preceding siblings ...)
2006-02-28 9:38 ` Linux v2.6.16-rc5 - regression Peter Hagervall
@ 2006-02-28 12:43 ` Christoph Hellwig
2006-03-03 16:00 ` Mark Rosenstand
` (3 subsequent siblings)
10 siblings, 0 replies; 62+ messages in thread
From: Christoph Hellwig @ 2006-02-28 12:43 UTC (permalink / raw)
To: Linus Torvalds; +Cc: Linux Kernel Mailing List, jejb, linux-scsi
On Sun, Feb 26, 2006 at 09:27:28PM -0800, Linus Torvalds wrote:
>
> The tar-ball is being uploaded right now, and everything else should
> already be pushed out. Mirroring might take a while, of course.
>
> There's not much to say about this: people have been pretty good, and it's
> just a random collection of fixes in various random areas. The shortlog is
> actually pretty short, and it really describes the updates better than
> anything else.
>
> Have I missed anything? Holler. And please keep reminding about any
> regressions since 2.6.15.
We still have a regression from 2.6.15 in the megaraid_sas driver.
We started sending down all requests as scatter/gather lists after 2.6.15,
and the (broken) way megaraid_sas tried to hide the physical disks ceased
to work. Now the driver shows all physical disks which confuses installers
to no end and could trick people to write to it which would corrupt controller
internal state badly.
To fix this properly the scsi midlayer needs to handle the ->slave_configure
return value. The patch for that is pretty trivially, but could in theory
cause problems if an existing driver returns something bogus from
->slave_configure. Both the core patch and the actual megaraid_sas fix
are in James' scsi-rc-fixes tree, so if you pull that once more we should
be done with this.
^ permalink raw reply [flat|nested] 62+ messages in thread* Re: Linux v2.6.16-rc5
2006-02-27 5:27 Linux v2.6.16-rc5 Linus Torvalds
` (6 preceding siblings ...)
2006-02-28 12:43 ` Linux v2.6.16-rc5 Christoph Hellwig
@ 2006-03-03 16:00 ` Mark Rosenstand
2006-03-03 23:01 ` 2.6.16-rc regression: m68k CONFIG_RMW_INSNS=n compile broken Adrian Bunk
` (2 subsequent siblings)
10 siblings, 0 replies; 62+ messages in thread
From: Mark Rosenstand @ 2006-03-03 16:00 UTC (permalink / raw)
To: Linux Kernel Mailing List
On Monday 27 February 2006 06:27, Linus Torvalds wrote:
> The tar-ball is being uploaded right now, and everything else should
> already be pushed out. Mirroring might take a while, of course.
It would be nice if the -rc announcements could make it to
linux-kernel-announce as well, like -mm.
^ permalink raw reply [flat|nested] 62+ messages in thread* 2.6.16-rc regression: m68k CONFIG_RMW_INSNS=n compile broken
2006-02-27 5:27 Linux v2.6.16-rc5 Linus Torvalds
` (7 preceding siblings ...)
2006-03-03 16:00 ` Mark Rosenstand
@ 2006-03-03 23:01 ` Adrian Bunk
2006-03-03 23:22 ` Linus Torvalds
2006-03-05 14:09 ` Linux v2.6.16-rc5 Olaf Hering
2006-03-05 22:03 ` Mathieu Chouquet-Stringer
10 siblings, 1 reply; 62+ messages in thread
From: Adrian Bunk @ 2006-03-03 23:01 UTC (permalink / raw)
To: Linus Torvalds, Andrew Morton, .geert, zippel, linux-m68k
Cc: Linux Kernel Mailing List
The m68k defconfig does no longer compile in 2.6.16-rc:
<-- snip -->
...
CC fs/file_table.o
fs/file_table.c: In function `fget':
fs/file_table.c:170: warning: implicit declaration of function `cmpxchg'
...
LD .tmp_vmlinux1
fs/built-in.o(.text+0x275a): In function `fget':
: undefined reference to `cmpxchg'
fs/built-in.o(.text+0x27da): In function `fget_light':
: undefined reference to `cmpxchg'
make: *** [.tmp_vmlinux1] Error 1
<-- snip -->
It seems the problem is that in the CONFIG_RMW_INSNS=n case, there's no
cmpxchg #define in include/asm-m68k/system.h required for the
atomic_add_unless #define in include/asm-m68k/atomic.h.
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
^ permalink raw reply [flat|nested] 62+ messages in thread* Re: 2.6.16-rc regression: m68k CONFIG_RMW_INSNS=n compile broken
2006-03-03 23:01 ` 2.6.16-rc regression: m68k CONFIG_RMW_INSNS=n compile broken Adrian Bunk
@ 2006-03-03 23:22 ` Linus Torvalds
2006-03-03 23:43 ` Adrian Bunk
2006-03-03 23:59 ` Andrew Morton
0 siblings, 2 replies; 62+ messages in thread
From: Linus Torvalds @ 2006-03-03 23:22 UTC (permalink / raw)
To: Adrian Bunk
Cc: Andrew Morton, .geert, zippel, linux-m68k,
Linux Kernel Mailing List, Nick Piggin
On Sat, 4 Mar 2006, Adrian Bunk wrote:
>
> It seems the problem is that in the CONFIG_RMW_INSNS=n case, there's no
> cmpxchg #define in include/asm-m68k/system.h required for the
> atomic_add_unless #define in include/asm-m68k/atomic.h.
Hmm. It seems like it never has been there.. Do you know what brought this
on? Was it Nick's RCU changes from "rcuref_dec_and_test()" to
"atomic_dec_and_test()" and friends?
Judging by your error messages, I _think_ it's the "atomic_inc_not_zero()"
that gets expanded to a cmpxchg() that simply doesn't exist on m68k and
never has.
I guess we've never depended on cmpxchg before. Or am I missing something?
Linus
^ permalink raw reply [flat|nested] 62+ messages in thread
* Re: 2.6.16-rc regression: m68k CONFIG_RMW_INSNS=n compile broken
2006-03-03 23:22 ` Linus Torvalds
@ 2006-03-03 23:43 ` Adrian Bunk
2006-03-03 23:59 ` Andrew Morton
1 sibling, 0 replies; 62+ messages in thread
From: Adrian Bunk @ 2006-03-03 23:43 UTC (permalink / raw)
To: Linus Torvalds
Cc: Andrew Morton, geert, zippel, linux-m68k,
Linux Kernel Mailing List, Nick Piggin
On Fri, Mar 03, 2006 at 03:22:42PM -0800, Linus Torvalds wrote:
>
>
> On Sat, 4 Mar 2006, Adrian Bunk wrote:
> >
> > It seems the problem is that in the CONFIG_RMW_INSNS=n case, there's no
> > cmpxchg #define in include/asm-m68k/system.h required for the
> > atomic_add_unless #define in include/asm-m68k/atomic.h.
>
> Hmm. It seems like it never has been there.. Do you know what brought this
> on? Was it Nick's RCU changes from "rcuref_dec_and_test()" to
> "atomic_dec_and_test()" and friends?
It was Nick's commit 8426e1f6af0fd7f44d040af7263750c5a52f3cc3 that added
atomic_inc_not_zero(), and Nick's patch that changed fs/file_table.c
from rcuref_dec_and_test() to atomic_dec_and_test() exposed this
problem.
> Judging by your error messages, I _think_ it's the "atomic_inc_not_zero()"
> that gets expanded to a cmpxchg() that simply doesn't exist on m68k and
> never has.
Exactly, that's what I wanted to say in my report.
> I guess we've never depended on cmpxchg before. Or am I missing something?
It seems this is the case.
And as far as I can see, m68k is the only architecture where cmpxchg
isn't always available.
> Linus
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
^ permalink raw reply [flat|nested] 62+ messages in thread* Re: 2.6.16-rc regression: m68k CONFIG_RMW_INSNS=n compile broken
2006-03-03 23:22 ` Linus Torvalds
2006-03-03 23:43 ` Adrian Bunk
@ 2006-03-03 23:59 ` Andrew Morton
2006-03-04 14:01 ` Roman Zippel
1 sibling, 1 reply; 62+ messages in thread
From: Andrew Morton @ 2006-03-03 23:59 UTC (permalink / raw)
To: Linus Torvalds; +Cc: bunk, .geert, zippel, linux-m68k, linux-kernel, nickpiggin
Linus Torvalds <torvalds@osdl.org> wrote:
>
>
>
> On Sat, 4 Mar 2006, Adrian Bunk wrote:
> >
> > It seems the problem is that in the CONFIG_RMW_INSNS=n case, there's no
> > cmpxchg #define in include/asm-m68k/system.h required for the
> > atomic_add_unless #define in include/asm-m68k/atomic.h.
>
> Hmm. It seems like it never has been there.. Do you know what brought this
> on? Was it Nick's RCU changes from "rcuref_dec_and_test()" to
> "atomic_dec_and_test()" and friends?
>
> Judging by your error messages, I _think_ it's the "atomic_inc_not_zero()"
> that gets expanded to a cmpxchg() that simply doesn't exist on m68k and
> never has.
>
> I guess we've never depended on cmpxchg before. Or am I missing something?
>
Yes, we now require cmpxchg of all architectures.
It's pretty simple to fix - just use local_irq_save(). We can steal the code
from include/asm-m68knommu/system.h.
^ permalink raw reply [flat|nested] 62+ messages in thread
* Re: 2.6.16-rc regression: m68k CONFIG_RMW_INSNS=n compile broken
2006-03-03 23:59 ` Andrew Morton
@ 2006-03-04 14:01 ` Roman Zippel
2006-03-04 14:12 ` Nick Piggin
0 siblings, 1 reply; 62+ messages in thread
From: Roman Zippel @ 2006-03-04 14:01 UTC (permalink / raw)
To: Andrew Morton
Cc: Linus Torvalds, bunk, .geert, linux-m68k, linux-kernel, nickpiggin
Hi,
On Fri, 3 Mar 2006, Andrew Morton wrote:
> Yes, we now require cmpxchg of all architectures.
Actually I'd prefer if we used atomic_cmpxchg() instead.
The cmpxchg() emulation was never added for a good reason - to keep code
from assuming it can be used it for userspace synchronisation. Using an
atomic_t here would probably get at least some attention.
bye, Roman
^ permalink raw reply [flat|nested] 62+ messages in thread
* Re: 2.6.16-rc regression: m68k CONFIG_RMW_INSNS=n compile broken
2006-03-04 14:01 ` Roman Zippel
@ 2006-03-04 14:12 ` Nick Piggin
2006-03-04 20:28 ` Andrew Morton
0 siblings, 1 reply; 62+ messages in thread
From: Nick Piggin @ 2006-03-04 14:12 UTC (permalink / raw)
To: Roman Zippel
Cc: Andrew Morton, Linus Torvalds, bunk, Geert Uytterhoeven,
linux-m68k, linux-kernel
Roman Zippel wrote:
> Hi,
>
> On Fri, 3 Mar 2006, Andrew Morton wrote:
>
>
>>Yes, we now require cmpxchg of all architectures.
>
>
> Actually I'd prefer if we used atomic_cmpxchg() instead.
> The cmpxchg() emulation was never added for a good reason - to keep code
> from assuming it can be used it for userspace synchronisation. Using an
> atomic_t here would probably get at least some attention.
>
Yes, I guess that's what Andrew meant. The reason we can require
atomic_cmpxchg of all architectures is because it is only guaranteed
to work on atomic_t.
Glad to hear it won't be a problem for you though.
--
SUSE Labs, Novell Inc.
Send instant messages to your online friends http://au.messenger.yahoo.com
^ permalink raw reply [flat|nested] 62+ messages in thread
* Re: 2.6.16-rc regression: m68k CONFIG_RMW_INSNS=n compile broken
2006-03-04 14:12 ` Nick Piggin
@ 2006-03-04 20:28 ` Andrew Morton
2006-03-08 11:24 ` [2.6 patch] m68k: fix cmpxchg compile errors if CONFIG_RMW_INSNS=n Adrian Bunk
0 siblings, 1 reply; 62+ messages in thread
From: Andrew Morton @ 2006-03-04 20:28 UTC (permalink / raw)
To: Nick Piggin; +Cc: zippel, torvalds, bunk, geert, linux-m68k, linux-kernel
Nick Piggin <nickpiggin@yahoo.com.au> wrote:
>
> Roman Zippel wrote:
> > Hi,
> >
> > On Fri, 3 Mar 2006, Andrew Morton wrote:
> >
> >
> >>Yes, we now require cmpxchg of all architectures.
> >
> >
> > Actually I'd prefer if we used atomic_cmpxchg() instead.
> > The cmpxchg() emulation was never added for a good reason - to keep code
> > from assuming it can be used it for userspace synchronisation. Using an
> > atomic_t here would probably get at least some attention.
> >
>
> Yes, I guess that's what Andrew meant. The reason we can require
> atomic_cmpxchg of all architectures is because it is only guaranteed
> to work on atomic_t.
>
> Glad to hear it won't be a problem for you though.
>
Could someone with an m68k compiler please send the patch?
^ permalink raw reply [flat|nested] 62+ messages in thread
* [2.6 patch] m68k: fix cmpxchg compile errors if CONFIG_RMW_INSNS=n
2006-03-04 20:28 ` Andrew Morton
@ 2006-03-08 11:24 ` Adrian Bunk
0 siblings, 0 replies; 62+ messages in thread
From: Adrian Bunk @ 2006-03-08 11:24 UTC (permalink / raw)
To: Andrew Morton
Cc: Nick Piggin, zippel, torvalds, geert, linux-m68k, linux-kernel
On Sat, Mar 04, 2006 at 12:28:48PM -0800, Andrew Morton wrote:
> Nick Piggin <nickpiggin@yahoo.com.au> wrote:
> >
> > Roman Zippel wrote:
> > > Hi,
> > >
> > > On Fri, 3 Mar 2006, Andrew Morton wrote:
> > >
> > >
> > >>Yes, we now require cmpxchg of all architectures.
> > >
> > >
> > > Actually I'd prefer if we used atomic_cmpxchg() instead.
> > > The cmpxchg() emulation was never added for a good reason - to keep code
> > > from assuming it can be used it for userspace synchronisation. Using an
> > > atomic_t here would probably get at least some attention.
> > >
> >
> > Yes, I guess that's what Andrew meant. The reason we can require
> > atomic_cmpxchg of all architectures is because it is only guaranteed
> > to work on atomic_t.
> >
> > Glad to hear it won't be a problem for you though.
> >
>
> Could someone with an m68k compiler please send the patch?
It's below.
cu
Adrian
<-- snip -->
This patch provides a cmpxchg() if CONFIG_RMW_INSNS=n (code stolen from
m68knommu).
Signed-off-by: Adrian Bunk <bunk@stusta.de>
---
include/asm-m68k/system.h | 15 +++++++++++++++
1 file changed, 15 insertions(+)
--- linux-2.6.16-rc5-mm3-m68k/include/asm-m68k/system.h.old 2006-03-08 12:10:48.000000000 +0100
+++ linux-2.6.16-rc5-mm3-m68k/include/asm-m68k/system.h 2006-03-08 12:17:47.000000000 +0100
@@ -192,6 +192,21 @@
#define cmpxchg(ptr,o,n)\
((__typeof__(*(ptr)))__cmpxchg((ptr),(unsigned long)(o),\
(unsigned long)(n),sizeof(*(ptr))))
+
+#else
+
+static inline unsigned long cmpxchg(volatile int *p, int old, int new)
+{
+ unsigned long flags;
+ int prev;
+
+ local_irq_save(flags);
+ if ((prev = *p) == old)
+ *p = new;
+ local_irq_restore(flags);
+ return(prev);
+}
+
#endif
#define arch_align_stack(x) (x)
^ permalink raw reply [flat|nested] 62+ messages in thread
* Re: Linux v2.6.16-rc5
2006-02-27 5:27 Linux v2.6.16-rc5 Linus Torvalds
` (8 preceding siblings ...)
2006-03-03 23:01 ` 2.6.16-rc regression: m68k CONFIG_RMW_INSNS=n compile broken Adrian Bunk
@ 2006-03-05 14:09 ` Olaf Hering
2006-03-05 18:59 ` Olaf Hering
2006-03-05 22:03 ` Mathieu Chouquet-Stringer
10 siblings, 1 reply; 62+ messages in thread
From: Olaf Hering @ 2006-03-05 14:09 UTC (permalink / raw)
To: Linus Torvalds, linuxppc-dev; +Cc: Linux Kernel Mailing List
On Sun, Feb 26, Linus Torvalds wrote:
> Have I missed anything? Holler. And please keep reminding about any
> regressions since 2.6.15.
I see random memory corruption on an early G3 ibook.
Testcase is an openSuSE 10.1 installation. 2.6.15 works ok modulo 2 bugs
to get it booted at all, and the usual udev breakage.
plain 2.6.16-rc5-git7 locks up after a few packages, no ping.
Our SuSE kernel does not lockup, but ext2 shows access beyond end of
device after > 200 packages, or the rpmdb gets corrupt, or both. With reiserfs
it gets past 100 packages, then reiserfs complains about fs corruption.
plain -rc2 shows the same reiserfs corruption.
plain -rc1 dies after a few packages, it jumps to 0x0 in softirq.
I'm trying to compile the git snapshots now, which is a real challenge..
^ permalink raw reply [flat|nested] 62+ messages in thread* Re: Linux v2.6.16-rc5
2006-03-05 14:09 ` Linux v2.6.16-rc5 Olaf Hering
@ 2006-03-05 18:59 ` Olaf Hering
2006-03-05 20:02 ` Linus Torvalds
0 siblings, 1 reply; 62+ messages in thread
From: Olaf Hering @ 2006-03-05 18:59 UTC (permalink / raw)
To: Linus Torvalds, linuxppc-dev; +Cc: Linux Kernel Mailing List
On Sun, Mar 05, Olaf Hering wrote:
> On Sun, Feb 26, Linus Torvalds wrote:
>
> > Have I missed anything? Holler. And please keep reminding about any
> > regressions since 2.6.15.
>
> I see random memory corruption on an early G3 ibook.
> Testcase is an openSuSE 10.1 installation. 2.6.15 works ok modulo 2 bugs
> to get it booted at all, and the usual udev breakage.
>
> plain 2.6.16-rc5-git7 locks up after a few packages, no ping.
> Our SuSE kernel does not lockup, but ext2 shows access beyond end of
> device after > 200 packages, or the rpmdb gets corrupt, or both. With reiserfs
> it gets past 100 packages, then reiserfs complains about fs corruption.
> plain -rc2 shows the same reiserfs corruption.
> plain -rc1 dies after a few packages, it jumps to 0x0 in softirq.
-git5 works, -git7 showed reiserfs corruption. -git6 died, jumped from
__do_softirq to 0x0, will try once again.
git5->6 has the mutex changes, but also lots of powerpc changes. Lets
see if I can narrow it down further.
The ibook has 160mb, installation is done via modular nfs
(ro,v3,rsize=32768,wsize=32768,hard,nolock,proto=tcp,addr=1.1.1.3)
I havent seen this on a B&W G3 with 256mb, nor on other ppc32 systems.
^ permalink raw reply [flat|nested] 62+ messages in thread
* Re: Linux v2.6.16-rc5
2006-03-05 18:59 ` Olaf Hering
@ 2006-03-05 20:02 ` Linus Torvalds
2006-03-05 20:42 ` Olaf Hering
0 siblings, 1 reply; 62+ messages in thread
From: Linus Torvalds @ 2006-03-05 20:02 UTC (permalink / raw)
To: Olaf Hering; +Cc: linuxppc-dev, Linux Kernel Mailing List
On Sun, 5 Mar 2006, Olaf Hering wrote:
> On Sun, Mar 05, Olaf Hering wrote:
> >
> > plain 2.6.16-rc5-git7 locks up after a few packages, no ping.
> > Our SuSE kernel does not lockup, but ext2 shows access beyond end of
> > device after > 200 packages, or the rpmdb gets corrupt, or both. With reiserfs
> > it gets past 100 packages, then reiserfs complains about fs corruption.
> > plain -rc2 shows the same reiserfs corruption.
> > plain -rc1 dies after a few packages, it jumps to 0x0 in softirq.
>
> -git5 works, -git7 showed reiserfs corruption. -git6 died, jumped from
> __do_softirq to 0x0, will try once again.
Since there are several git users in the ppc camp, one thing that always
helps is that when you test a -git snapshot, you also say what the "git
ID" was.
I'm assuming that when you say "-git5 works", you mean 2.6.15-git5.
In this case:
2.6.15-git5: 5367f2d67c7d0bf1faae90e6e7b4e2ac3c9b5e0f
2.6.15-git6: 977127174a7dff52d17faeeb4c4949a54221881f
2.6.15-git7: 05f6ece6f37f987e9de643f6f76e8fb5d5b9e014
> git5->6 has the mutex changes, but also lots of powerpc changes. Lets
> see if I can narrow it down further.
If you can try out git, the best way to proceed is
git bisect start
git bisect good 5367f2d67c7d0bf1faae90e6e7b4e2ac3c9b5e0f
git bisect bad 977127174a7dff52d17faeeb4c4949a54221881f
which should help narrow it down pretty efficiently (I'm marking -git6 as
bad, on the logic that the bug being chased is "corruption _or_ jumping to
address 0". It's much harder if you want to chase down just one bug, when
the other bug might stand in your way).
And yes, that range contains not just powerpc updates, but also PCI layer,
mutex changes, crypto and V4L/DVB. Doing just three or four bisection
trials would help narrow it down a lot (now it's 448 commits - doing three
bisctions should narrow it down into less than 60 commits and likely which
subsystem, while doing another bisection or two would get us into a few
tens of commits).
"git bisect" really is very powerful and easy to use.
Linus
^ permalink raw reply [flat|nested] 62+ messages in thread
* Re: Linux v2.6.16-rc5
2006-03-05 20:02 ` Linus Torvalds
@ 2006-03-05 20:42 ` Olaf Hering
2006-03-05 21:50 ` Paul Mackerras
0 siblings, 1 reply; 62+ messages in thread
From: Olaf Hering @ 2006-03-05 20:42 UTC (permalink / raw)
To: Linus Torvalds; +Cc: linuxppc-dev, Linux Kernel Mailing List
[-- Attachment #1: Type: text/plain, Size: 1858 bytes --]
On Sun, Mar 05, Linus Torvalds wrote:
> "git bisect" really is very powerful and easy to use.
Indeed. The one "between" gi5 and git6
(93b47684f60cf25e8cefe19a21d94aa0257fdf36) is fails also. There are no
mutex changes left, so I suspect some ppc bug.
With this changeset, my first attempt ran into this deadlock, the second
attempt lead to the reiserfs corruption.
See attached 93b47684f60cf25e8cefe19a21d94aa0257fdf36.log
I'm now at 03929c76f3e5af919fb762e9882a9c286d361e7d, which fails as
well. dmesg shows this:
Adding 295332k swap on /dev/hda10. Priority:-1 extents:1 across:295332k
ReiserFS: warning: is_leaf: wrong item type for item *3.5*[-1 -1 0xffffffff DIRECT], item_len 65535, item_location 65535, free_space(entry_count) 65535
ReiserFS: hda11: warning: vs-5150: search_by_key: invalid format found in block 0. Fsck?
ReiserFS: hda11: warning: vs-13070: reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [2 4652 0x0 SD]
ReiserFS: warning: is_leaf: wrong item type for item *3.5*[-1 -1 0xffffffff DIRECT], item_len 65535, item_location 65535, free_space(entry_count) 65535
ReiserFS: hda11: warning: vs-5150: search_by_key: invalid format found in block 0. Fsck?
ReiserFS: hda11: warning: vs-13070: reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [2 4652 0x0 SD]
ReiserFS: warning: is_leaf: wrong item type for item *3.5*[-1 -1 0xffffffff DIRECT], item_len 65535, item_location 65535, free_space(entry_count) 65535
ReiserFS: hda11: warning: vs-5150: search_by_key: invalid format found in block 0. Fsck?
ReiserFS: hda11: warning: vs-13070: reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [2 4652 0x0 SD]
There are only powerpc related changes left.
Its a bit time comsuming until I get to the point of where it fails,
lets see how far I get this evening.
[-- Attachment #2: 93b47684f60cf25e8cefe19a21d94aa0257fdf36.log --]
[-- Type: text/x-log, Size: 24139 bytes --]
inst-sys:~ # dmesg
device-mapper: 4.5.0-ioctl (2005-10-04) initialised: dm-devel@redhat.com
md: Autodetecting RAID arrays.
md: autorun ...
md: ... autorun DONE.
md: raid0 personality registered for level 0
md: raid1 personality registered for level 1
raid5: measuring checksumming speed
8regs : 351.000 MB/sec
8regs_prefetch: 296.000 MB/sec
32regs : 325.000 MB/sec
32regs_prefetch: 285.000 MB/sec
raid5: using function: 8regs (351.000 MB/sec)
md: raid5 personality registered for level 5
md: raid4 personality registered for level 4
raid6: int32x1 58 MB/s
raid6: int32x2 88 MB/s
raid6: int32x4 110 MB/s
raid6: int32x8 105 MB/s
raid6: using algorithm int32x4 (110 MB/s)
md: raid6 personality registered for level 6
md: multipath personality registered for level -4
hdc: packet command error: status=0x51 { DriveReady SeekComplete Error }
hdc: packet command error: error=0x54 { AbortedCommand LastFailedSense=0x05 }
ide: failed opcode was: unknown
cdrom: open failed.
ReiserFS: hda11: found reiserfs format "3.6" with standard journal
ReiserFS: hda11: using ordered data mode
ReiserFS: hda11: journal params: device hda11, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30
ReiserFS: hda11: checking transaction log (hda11)
ReiserFS: hda11: Using r5 hash to sort names
ReiserFS: hda11: warning: Created .reiserfs_priv on hda11 - reserved for xattr storage.
Adding 295332k swap on /dev/hda10. Priority:-1 extents:1 across:295332k
SysRq : Show State
sibling
task PC pid father child younger older
init S 0FEC24B4 0 1 0 2 (NOTLB)
Call Trace:
[C2D29D90] [C2D29E40] 0xc2d29e40 (unreliable)
[C2D29E50] [C000C318] __switch_to+0x5c/0x74
[C2D29E70] [C02D3B28] schedule+0x680/0x734
[C2D29EB0] [C00332D0] do_wait+0xc88/0xe94
[C2D29F40] [C001052C] ret_from_syscall+0x0/0x40
--- Exception: c01 at 0xfec24b4
LR = 0xfe5ed00
ksoftirqd/0 S 00000000 0 2 1 3 (L-TLB)
Call Trace:
[C2D2BE90] [EA6713EA] 0xea6713ea (unreliable)
[C2D2BF50] [C000C318] __switch_to+0x5c/0x74
[C2D2BF70] [C02D3B28] schedule+0x680/0x734
[C2D2BFB0] [C0035D74] ksoftirqd+0x4c/0xa8
[C2D2BFC0] [C0048900] kthread+0xd4/0x110
[C2D2BFF0] [C00117C4] kernel_thread+0x44/0x60
watchdog/0 S 00000000 0 3 1 4 2 (L-TLB)
Call Trace:
[C2D2DE30] [7C00F54F] 0x7c00f54f (unreliable)
[C2D2DEF0] [C000C318] __switch_to+0x5c/0x74
[C2D2DF10] [C02D3B28] schedule+0x680/0x734
[C2D2DF50] [C02D4618] schedule_timeout+0x98/0xc8
[C2D2DF90] [C003B374] msleep_interruptible+0x38/0x6c
[C2D2DFA0] [C0058068] watchdog+0x44/0x84
[C2D2DFC0] [C0048900] kthread+0xd4/0x110
[C2D2DFF0] [C00117C4] kernel_thread+0x44/0x60
events/0 S 00000000 0 4 1 5 3 (L-TLB)
Call Trace:
[C2787E20] [00000001] 0x1 (unreliable)
[C2787EE0] [C000C318] __switch_to+0x5c/0x74
[C2787F00] [C02D3B28] schedule+0x680/0x734
[C2787F40] [C0043A1C] worker_thread+0xdc/0x224
[C2787FC0] [C0048900] kthread+0xd4/0x110
[C2787FF0] [C00117C4] kernel_thread+0x44/0x60
khelper S 00000000 0 5 1 6 4 (L-TLB)
Call Trace:
[C2CE1E20] [C0043940] worker_thread+0x0/0x224 (unreliable)
[C2CE1EE0] [C000C318] __switch_to+0x5c/0x74
[C2CE1F00] [C02D3B28] schedule+0x680/0x734
[C2CE1F40] [C0043A1C] worker_thread+0xdc/0x224
[C2CE1FC0] [C0048900] kthread+0xd4/0x110
[C2CE1FF0] [C00117C4] kernel_thread+0x44/0x60
kthread S 00000000 0 6 1 24 73 5 (L-TLB)
Call Trace:
[C2789E20] [0000000A] 0xa (unreliable)
[C2789EE0] [C000C318] __switch_to+0x5c/0x74
[C2789F00] [C02D3B28] schedule+0x680/0x734
[C2789F40] [C0043A1C] worker_thread+0xdc/0x224
[C2789FC0] [C0048900] kthread+0xd4/0x110
[C2789FF0] [C00117C4] kernel_thread+0x44/0x60
kblockd/0 S 00000000 0 24 6 28 (L-TLB)
Call Trace:
[C9B41E20] [C04798C0] ide_hwifs+0x0/0x41c0 (unreliable)
[C9B41EE0] [C000C318] __switch_to+0x5c/0x74
[C9B41F00] [C02D3B28] schedule+0x680/0x734
[C9B41F40] [C0043A1C] worker_thread+0xdc/0x224
[C9B41FC0] [C0048900] kthread+0xd4/0x110
[C9B41FF0] [C00117C4] kernel_thread+0x44/0x60
khubd S 00000000 0 28 6 71 24 (L-TLB)
Call Trace:
[C9B4FE10] [C0224D98] urb_destroy+0x10/0x20 (unreliable)
[C9B4FED0] [C000C318] __switch_to+0x5c/0x74
[C9B4FEF0] [C02D3B28] schedule+0x680/0x734
[C9B4FF30] [C022223C] hub_thread+0xb78/0xc08
[C9B4FFC0] [C0048900] kthread+0xd4/0x110
[C9B4FFF0] [C00117C4] kernel_thread+0x44/0x60
pdflush S 00000000 0 71 6 72 28 (L-TLB)
Call Trace:
[C9B6BE60] [C003ABD8] process_timeout+0x0/0x20 (unreliable)
[C9B6BF20] [C000C318] __switch_to+0x5c/0x74
[C9B6BF40] [C02D3B28] schedule+0x680/0x734
[C9B6BF80] [C0060E58] pdflush+0xc0/0x218
[C9B6BFC0] [C0048900] kthread+0xd4/0x110
[C9B6BFF0] [C00117C4] kernel_thread+0x44/0x60
pdflush D 00000000 0 72 6 74 71 (L-TLB)
Call Trace:
[C9B65BF0] [000003FA] 0x3fa (unreliable)
[C9B65CB0] [C000C318] __switch_to+0x5c/0x74
[C9B65CD0] [C02D3B28] schedule+0x680/0x734
[C9B65D10] [C02D326C] __down+0x64/0xd0
[C9B65D70] [C00F896C] flush_commit_list+0x17c/0x7c4
[C9B65DB0] [C00F8900] flush_commit_list+0x110/0x7c4
[C9B65DF0] [C00FC9C4] do_journal_end+0xe74/0xec0
[C9B65E50] [C00FCA98] journal_end_sync+0x88/0x9c
[C9B65E70] [C00E5FBC] reiserfs_sync_fs+0x4c/0x88
[C9B65EB0] [C00E600C] reiserfs_write_super+0x14/0x24
[C9B65EC0] [C0089394] sync_supers+0x104/0x1c4
[C9B65EE0] [C00602D8] wb_kupdate+0x54/0x16c
[C9B65F80] [C0060EBC] pdflush+0x124/0x218
[C9B65FC0] [C0048900] kthread+0xd4/0x110
[C9B65FF0] [C00117C4] kernel_thread+0x44/0x60
aio/0 S 00000000 0 74 6 283 72 (L-TLB)
Call Trace:
[C9B49E20] [C060C000] 0xc060c000 (unreliable)
[C9B49EE0] [C000C318] __switch_to+0x5c/0x74
[C9B49F00] [C02D3B28] schedule+0x680/0x734
[C9B49F40] [C0043A1C] worker_thread+0xdc/0x224
[C9B49FC0] [C0048900] kthread+0xd4/0x110
[C9B49FF0] [C00117C4] kernel_thread+0x44/0x60
kswapd0 S 00000000 0 73 1 383 6 (L-TLB)
Call Trace:
[C9B67E60] [C02D507C] _spin_unlock_irqrestore+0x18/0x30 (unreliable)
[C9B67F20] [C000C318] __switch_to+0x5c/0x74
[C9B67F40] [C02D3B28] schedule+0x680/0x734
[C9B67F80] [C0064604] kswapd+0xc8/0xec
[C9B67FF0] [C00117C4] kernel_thread+0x44/0x60
cqueue/0 S 00000000 0 283 6 284 74 (L-TLB)
Call Trace:
[C9BEDE20] [C060C000] 0xc060c000 (unreliable)
[C9BEDEE0] [C000C318] __switch_to+0x5c/0x74
[C9BEDF00] [C02D3B28] schedule+0x680/0x734
[C9BEDF40] [C0043A1C] worker_thread+0xdc/0x224
[C9BEDFC0] [C0048900] kthread+0xd4/0x110
[C9BEDFF0] [C00117C4] kernel_thread+0x44/0x60
kseriod S 00000000 0 284 6 1064 283 (L-TLB)
Call Trace:
[C9BF7E40] [C00CB664] sysfs_new_dirent+0x2c/0x94 (unreliable)
[C9BF7F00] [C000C318] __switch_to+0x5c/0x74
[C9BF7F20] [C02D3B28] schedule+0x680/0x734
[C9BF7F60] [C01E791C] serio_thread+0x2e8/0x33c
[C9BF7FC0] [C0048900] kthread+0xd4/0x110
[C9BF7FF0] [C00117C4] kernel_thread+0x44/0x60
udevd S 0FF626D4 0 383 1 947 73 (NOTLB)
Call Trace:
[C2D69CE0] [0000000A] 0xa (unreliable)
[C2D69DA0] [C000C318] __switch_to+0x5c/0x74
[C2D69DC0] [C02D3B28] schedule+0x680/0x734
[C2D69E00] [C02D45AC] schedule_timeout+0x2c/0xc8
[C2D69E40] [C0097E68] do_select+0x328/0x384
[C2D69EC0] [C00981C0] sys_select+0x2fc/0x4dc
[C2D69F10] [C0004D98] ppc_select+0xfc/0x118
[C2D69F40] [C001052C] ret_from_syscall+0x0/0x40
--- Exception: c01 at 0xff626d4
LR = 0x1000317c
bash S 0FE372A8 0 947 1 1061 383 (NOTLB)
Call Trace:
[C9E1FCD0] [08D4B305] 0x8d4b305 (unreliable)
[C9E1FD90] [C000C318] __switch_to+0x5c/0x74
[C9E1FDB0] [C02D3B28] schedule+0x680/0x734
[C9E1FDF0] [C02D45AC] schedule_timeout+0x2c/0xc8
[C9E1FE30] [C01D63E0] read_chan+0x368/0x814
[C9E1FEC0] [C01D2674] tty_read+0x8c/0xdc
[C9E1FEF0] [C008002C] vfs_read+0xec/0x1c4
[C9E1FF10] [C00804CC] sys_read+0x4c/0x94
[C9E1FF40] [C001052C] ret_from_syscall+0x0/0x40
--- Exception: c01 at 0xfe372a8
LR = 0xffc96e4
dhcpcd S 07F33CF0 0 1061 1 1063 947 (NOTLB)
Call Trace:
[C258FDB0] [C00A236C] mntput_no_expire+0x2c/0xc4 (unreliable)
[C258FE70] [C000C318] __switch_to+0x5c/0x74
[C258FE90] [C02D3B28] schedule+0x680/0x734
[C258FED0] [C02D4618] schedule_timeout+0x98/0xc8
[C258FF10] [C003B5DC] sys_nanosleep+0x128/0x260
[C258FF40] [C001052C] ret_from_syscall+0x0/0x40
--- Exception: c01 at 0x7f33cf0
LR = 0x7f33aa4
portmap S 07F111E0 0 1063 1 1065 1061 (NOTLB)
Call Trace:
[C2595D90] [C025C698] move_addr_to_kernel+0x90/0xc4 (unreliable)
[C2595E50] [C000C318] __switch_to+0x5c/0x74
[C2595E70] [C02D3B28] schedule+0x680/0x734
[C2595EB0] [C02D45AC] schedule_timeout+0x2c/0xc8
[C2595EF0] [C0098614] sys_poll+0x274/0x360
[C2595F40] [C001052C] ret_from_syscall+0x0/0x40
--- Exception: c01 at 0x7f111e0
LR = 0x7f1119c
rpciod/0 S 00000000 0 1064 6 3348 284 (L-TLB)
Call Trace:
[C258BE20] [C02D507C] _spin_unlock_irqrestore+0x18/0x30 (unreliable)
[C258BEE0] [C000C318] __switch_to+0x5c/0x74
[C258BF00] [C02D3B28] schedule+0x680/0x734
[C258BF40] [C0043A1C] worker_thread+0xdc/0x224
[C258BFC0] [C0048900] kthread+0xd4/0x110
[C258BFF0] [C00117C4] kernel_thread+0x44/0x60
lockd S 00000000 0 1065 1 1066 1063 (L-TLB)
Call Trace:
[C2591E00] [C007AA64] cache_free_debugcheck+0x214/0x22c (unreliable)
[C2591EC0] [C000C318] __switch_to+0x5c/0x74
[C2591EE0] [C02D3B28] schedule+0x680/0x734
[C2591F20] [C02D45AC] schedule_timeout+0x2c/0xc8
[C2591F60] [CB18F0D4] svc_recv+0x300/0x530 [sunrpc]
[C2591FD0] [CB152924] lockd+0x168/0x280 [lockd]
[C2591FF0] [C00117C4] kernel_thread+0x44/0x60
loop0 S 00000000 0 1066 1 1084 1065 (L-TLB)
Call Trace:
[C2DADE10] [C2DADE60] 0xc2dade60 (unreliable)
[C2DADED0] [C000C318] __switch_to+0x5c/0x74
[C2DADEF0] [C02D3B28] schedule+0x680/0x734
[C2DADF30] [C02D3370] __down_interruptible+0x98/0x10c
[C2DADF90] [CB104630] loop_thread+0xac/0x468 [loop]
[C2DADFF0] [C00117C4] kernel_thread+0x44/0x60
bash R running 0 1084 1 1087 1066 (NOTLB)
bash S 0FE372A8 0 1087 1 1090 1084 (NOTLB)
Call Trace:
[C887BCD0] [08BA8785] 0x8ba8785 (unreliable)
[C887BD90] [C000C318] __switch_to+0x5c/0x74
[C887BDB0] [C02D3B28] schedule+0x680/0x734
[C887BDF0] [C02D45AC] schedule_timeout+0x2c/0xc8
[C887BE30] [C01D63E0] read_chan+0x368/0x814
[C887BEC0] [C01D2674] tty_read+0x8c/0xdc
[C887BEF0] [C008002C] vfs_read+0xec/0x1c4
[C887BF10] [C00804CC] sys_read+0x4c/0x94
[C887BF40] [C001052C] ret_from_syscall+0x0/0x40
--- Exception: c01 at 0xfe372a8
LR = 0xffc96e4
bash S 0FE372A8 0 1090 1 1093 1087 (NOTLB)
Call Trace:
[C88D1CD0] [08B8F785] 0x8b8f785 (unreliable)
[C88D1D90] [C000C318] __switch_to+0x5c/0x74
[C88D1DB0] [C02D3B28] schedule+0x680/0x734
[C88D1DF0] [C02D45AC] schedule_timeout+0x2c/0xc8
[C88D1E30] [C01D63E0] read_chan+0x368/0x814
[C88D1EC0] [C01D2674] tty_read+0x8c/0xdc
[C88D1EF0] [C008002C] vfs_read+0xec/0x1c4
[C88D1F10] [C00804CC] sys_read+0x4c/0x94
[C88D1F40] [C001052C] ret_from_syscall+0x0/0x40
--- Exception: c01 at 0xfe372a8
LR = 0xffc96e4
inst_setup S 0FE114B4 0 1093 1 1209 1096 1090 (NOTLB)
Call Trace:
[C8921D90] [C006A390] __handle_mm_fault+0x1214/0x12cc (unreliable)
[C8921E50] [C000C318] __switch_to+0x5c/0x74
[C8921E70] [C02D3B28] schedule+0x680/0x734
[C8921EB0] [C00332D0] do_wait+0xc88/0xe94
[C8921F40] [C001052C] ret_from_syscall+0x0/0x40
--- Exception: c01 at 0xfe114b4
LR = 0x100324e8
showconsole X 0FEFE178 0 1096 1 1107 1093 (L-TLB)
Call Trace:
[C8B73DD0] [C005EED8] __free_pages+0x74/0x194 (unreliable)
[C8B73E90] [C000C318] __switch_to+0x5c/0x74
[C8B73EB0] [C02D3B28] schedule+0x680/0x734
[C8B73EF0] [C0034010] do_exit+0xa8c/0xb18
[C8B73F20] [C0034138] sys_exit_group+0x0/0x8
[C8B73F40] [C001052C] ret_from_syscall+0x0/0x40
--- Exception: c01 at 0xfefe178
LR = 0xfefe148
dbus-daemon S 0FC711E0 0 1107 1 1109 1096 (NOTLB)
Call Trace:
[C80E7D90] [C025ACD8] sock_writev+0x90/0xc0 (unreliable)
[C80E7E50] [C000C318] __switch_to+0x5c/0x74
[C80E7E70] [C02D3B28] schedule+0x680/0x734
[C80E7EB0] [C02D45AC] schedule_timeout+0x2c/0xc8
[C80E7EF0] [C0098614] sys_poll+0x274/0x360
[C80E7F40] [C001052C] ret_from_syscall+0x0/0x40
--- Exception: c01 at 0xfc711e0
LR = 0xfc7119c
hald S 0FC611E0 0 1109 1 1125 1162 1107 (NOTLB)
Call Trace:
[C83FBD90] [C015FE70] _atomic_dec_and_lock+0x44/0x60 (unreliable)
[C83FBE50] [C000C318] __switch_to+0x5c/0x74
[C83FBE70] [C02D3B28] schedule+0x680/0x734
[C83FBEB0] [C02D4618] schedule_timeout+0x98/0xc8
[C83FBEF0] [C0098614] sys_poll+0x274/0x360
[C83FBF40] [C001052C] ret_from_syscall+0x0/0x40
--- Exception: c01 at 0xfc611e0
LR = 0xfc6119c
hald-addon-st S 0FE76CF0 0 1125 1109 (NOTLB)
Call Trace:
[C7EFBDB0] [C035D7B8] xtime_lock+0x4/0x14 (unreliable)
[C7EFBE70] [C000C318] __switch_to+0x5c/0x74
[C7EFBE90] [C02D3B28] schedule+0x680/0x734
[C7EFBED0] [C02D4618] schedule_timeout+0x98/0xc8
[C7EFBF10] [C003B5DC] sys_nanosleep+0x128/0x260
[C7EFBF40] [C001052C] ret_from_syscall+0x0/0x40
--- Exception: c01 at 0xfe76cf0
LR = 0xfe76aa4
syslogd.bin S 07F626D4 0 1162 1 1167 1109 (NOTLB)
Call Trace:
[C63CFCE0] [C02CD768] unix_dgram_recvmsg+0x218/0x264 (unreliable)
[C63CFDA0] [C000C318] __switch_to+0x5c/0x74
[C63CFDC0] [C02D3B28] schedule+0x680/0x734
[C63CFE00] [C02D45AC] schedule_timeout+0x2c/0xc8
[C63CFE40] [C0097E68] do_select+0x328/0x384
[C63CFEC0] [C00981C0] sys_select+0x2fc/0x4dc
[C63CFF10] [C0004D98] ppc_select+0xfc/0x118
[C63CFF40] [C001052C] ret_from_syscall+0x0/0x40
--- Exception: c01 at 0x7f626d4
LR = 0x8007490
klogd R running 0 1167 1 1199 1162 (NOTLB)
sshd S 07A9C6D4 0 1199 1 1893 2167 1167 (NOTLB)
Call Trace:
[C5DBDCE0] [C002B43C] __wake_up_common+0x40/0x94 (unreliable)
[C5DBDDA0] [C000C318] __switch_to+0x5c/0x74
[C5DBDDC0] [C02D3B28] schedule+0x680/0x734
[C5DBDE00] [C02D45AC] schedule_timeout+0x2c/0xc8
[C5DBDE40] [C0097E68] do_select+0x328/0x384
[C5DBDEC0] [C00981C0] sys_select+0x2fc/0x4dc
[C5DBDF10] [C0004D98] ppc_select+0xfc/0x118
[C5DBDF40] [C001052C] ret_from_syscall+0x0/0x40
--- Exception: c01 at 0x7a9c6d4
LR = 0x800ff28
yast S 0FE114B4 0 1209 1093 2279 (NOTLB)
Call Trace:
[C5B11D90] [C006A390] __handle_mm_fault+0x1214/0x12cc (unreliable)
[C5B11E50] [C000C318] __switch_to+0x5c/0x74
[C5B11E70] [C02D3B28] schedule+0x680/0x734
[C5B11EB0] [C00332D0] do_wait+0xc88/0xe94
[C5B11F40] [C001052C] ret_from_syscall+0x0/0x40
--- Exception: c01 at 0xfe114b4
LR = 0x100324e8
sshd S 07A9C6D4 0 1893 1199 2055 (NOTLB)
Call Trace:
[C5E93CE0] [C0010C5C] ret_from_except+0x0/0x1c (unreliable)
--- Exception: c5e93da0 at __switch_to+0x5c/0x74
LR = 0xc5e93da0
[C5E93DA0] [C000C318] __switch_to+0x5c/0x74 (unreliable)
[C5E93DC0] [C02D3B28] schedule+0x680/0x734
[C5E93E00] [C02D45AC] schedule_timeout+0x2c/0xc8
[C5E93E40] [C0097E68] do_select+0x328/0x384
[C5E93EC0] [C00981C0] sys_select+0x2fc/0x4dc
[C5E93F10] [C0004D98] ppc_select+0xfc/0x118
[C5E93F40] [C001052C] ret_from_syscall+0x0/0x40
--- Exception: c01 at 0x7a9c6d4
LR = 0x801675c
bash S 0FE114B4 0 2055 1893 2113 (NOTLB)
Call Trace:
[C5F2FD90] [C002BCC4] __wake_up+0x4c/0x60 (unreliable)
[C5F2FE50] [C000C318] __switch_to+0x5c/0x74
[C5F2FE70] [C02D3B28] schedule+0x680/0x734
[C5F2FEB0] [C00332D0] do_wait+0xc88/0xe94
[C5F2FF40] [C001052C] ret_from_syscall+0x0/0x40
--- Exception: c01 at 0xfe114b4
LR = 0x100324e8
tail S 0FF33CF0 0 2113 2055 (NOTLB)
Call Trace:
[C5535DB0] [C00A236C] mntput_no_expire+0x2c/0xc4 (unreliable)
[C5535E70] [C000C318] __switch_to+0x5c/0x74
[C5535E90] [C02D3B28] schedule+0x680/0x734
[C5535ED0] [C02D4618] schedule_timeout+0x98/0xc8
[C5535F10] [C003B5DC] sys_nanosleep+0x128/0x260
[C5535F40] [C001052C] ret_from_syscall+0x0/0x40
--- Exception: c01 at 0xff33cf0
LR = 0x10005e4c
gzip X 0FF34178 0 2167 1 2865 1199 (L-TLB)
Call Trace:
[C5593DD0] [00000001] 0x1 (unreliable)
[C5593E90] [C000C318] __switch_to+0x5c/0x74
[C5593EB0] [C02D3B28] schedule+0x680/0x734
[C5593EF0] [C0034010] do_exit+0xa8c/0xb18
[C5593F20] [C0034138] sys_exit_group+0x0/0x8
[C5593F40] [C001052C] ret_from_syscall+0x0/0x40
--- Exception: c01 at 0xff34178
LR = 0xff34148
YaST2.call S 0FE114B4 0 2279 1209 2844 (NOTLB)
Call Trace:
[C5507D90] [C006A390] __handle_mm_fault+0x1214/0x12cc (unreliable)
[C5507E50] [C000C318] __switch_to+0x5c/0x74
[C5507E70] [C02D3B28] schedule+0x680/0x734
[C5507EB0] [C00332D0] do_wait+0xc88/0xe94
[C5507F40] [C001052C] ret_from_syscall+0x0/0x40
--- Exception: c01 at 0xfe114b4
LR = 0x100324e8
y2base S 0F3242E4 0 2844 2279 3387 2845 (NOTLB)
Call Trace:
[C4A81D00] [00009032] 0x9032 (unreliable)
[C4A81DC0] [C000C318] __switch_to+0x5c/0x74
[C4A81DE0] [C02D3B28] schedule+0x680/0x734
[C4A81E20] [C008F9B4] pipe_wait+0x88/0xdc
[C4A81E80] [C0090294] pipe_readv+0x2b8/0x360
[C4A81ED0] [C009035C] pipe_read+0x20/0x30
[C4A81EF0] [C008002C] vfs_read+0xec/0x1c4
[C4A81F10] [C00804CC] sys_read+0x4c/0x94
[C4A81F40] [C001052C] ret_from_syscall+0x0/0x40
--- Exception: c01 at 0xf3242e4
LR = 0xf3242cc
y2base S 0F32D720 0 2845 2279 2844 (NOTLB)
Call Trace:
[C7F7FCE0] [5A2CF071] 0x5a2cf071 (unreliable)
[C7F7FDA0] [C000C318] __switch_to+0x5c/0x74
[C7F7FDC0] [C02D3B28] schedule+0x680/0x734
[C7F7FE00] [C02D4618] schedule_timeout+0x98/0xc8
[C7F7FE40] [C0097E68] do_select+0x328/0x384
[C7F7FEC0] [C00981C0] sys_select+0x2fc/0x4dc
[C7F7FF10] [C0004D98] ppc_select+0xfc/0x118
[C7F7FF40] [C001052C] ret_from_syscall+0x0/0x40
--- Exception: c01 at 0xf32d720
LR = 0xf32d700
gzip X 0FF34178 0 2865 1 2893 2167 (L-TLB)
Call Trace:
[C76DFDD0] [00000001] 0x1 (unreliable)
[C76DFE90] [C000C318] __switch_to+0x5c/0x74
[C76DFEB0] [C02D3B28] schedule+0x680/0x734
[C76DFEF0] [C0034010] do_exit+0xa8c/0xb18
[C76DFF20] [C0034138] sys_exit_group+0x0/0x8
[C76DFF40] [C001052C] ret_from_syscall+0x0/0x40
--- Exception: c01 at 0xff34178
LR = 0xff34148
gzip X 0FF34178 0 2893 1 2913 2865 (L-TLB)
Call Trace:
[C726FDD0] [00000001] 0x1 (unreliable)
[C726FE90] [C000C318] __switch_to+0x5c/0x74
[C726FEB0] [C02D3B28] schedule+0x680/0x734
[C726FEF0] [C0034010] do_exit+0xa8c/0xb18
[C726FF20] [C0034138] sys_exit_group+0x0/0x8
[C726FF40] [C001052C] ret_from_syscall+0x0/0x40
--- Exception: c01 at 0xff34178
LR = 0xff34148
gzip X 0FF34178 0 2913 1 3120 2893 (L-TLB)
Call Trace:
[C7327DD0] [C7327E80] 0xc7327e80 (unreliable)
[C7327E90] [C000C318] __switch_to+0x5c/0x74
[C7327EB0] [C02D3B28] schedule+0x680/0x734
[C7327EF0] [C0034010] do_exit+0xa8c/0xb18
[C7327F20] [C0034138] sys_exit_group+0x0/0x8
[C7327F40] [C001052C] ret_from_syscall+0x0/0x40
--- Exception: c01 at 0xff34178
LR = 0xff34148
gzip X 0FF34178 0 3120 1 3241 2913 (L-TLB)
Call Trace:
[C443FDD0] [C005EED8] __free_pages+0x74/0x194 (unreliable)
[C443FE90] [C000C318] __switch_to+0x5c/0x74
[C443FEB0] [C02D3B28] schedule+0x680/0x734
[C443FEF0] [C0034010] do_exit+0xa8c/0xb18
[C443FF20] [C0034138] sys_exit_group+0x0/0x8
[C443FF40] [C001052C] ret_from_syscall+0x0/0x40
--- Exception: c01 at 0xff34178
LR = 0xff34148
gzip X 0FF34178 0 3241 1 3120 (L-TLB)
Call Trace:
[C870FDD0] [C005EED8] __free_pages+0x74/0x194 (unreliable)
[C870FE90] [C000C318] __switch_to+0x5c/0x74
[C870FEB0] [C02D3B28] schedule+0x680/0x734
[C870FEF0] [C0034010] do_exit+0xa8c/0xb18
[C870FF20] [C0034138] sys_exit_group+0x0/0x8
[C870FF40] [C001052C] ret_from_syscall+0x0/0x40
--- Exception: c01 at 0xff34178
LR = 0xff34148
reiserfs/0 D 00000000 0 3348 6 1064 (L-TLB)
Call Trace:
[C71A3D20] [C01525D8] submit_bio+0xe0/0xf4 (unreliable)
[C71A3DE0] [C000C318] __switch_to+0x5c/0x74
[C71A3E00] [C02D3B28] schedule+0x680/0x734
[C71A3E40] [C02D326C] __down+0x64/0xd0
[C71A3EA0] [C00F896C] flush_commit_list+0x17c/0x7c4
[C71A3EE0] [C00F8900] flush_commit_list+0x110/0x7c4
[C71A3F20] [C00FD8A8] flush_async_commits+0x3c/0xa0
[C71A3F40] [C0043AD8] worker_thread+0x198/0x224
[C71A3FC0] [C0048900] kthread+0xd4/0x110
[C71A3FF0] [C00117C4] kernel_thread+0x44/0x60
rpm D 0FAA793C 0 3387 2844 (NOTLB)
Call Trace:
[C5BC1B40] [C280C7DC] 0xc280c7dc (unreliable)
[C5BC1C00] [C000C318] __switch_to+0x5c/0x74
[C5BC1C20] [C02D3B28] schedule+0x680/0x734
[C5BC1C60] [C02D3CF8] io_schedule+0x30/0x60
[C5BC1C80] [C0082CBC] sync_buffer+0x50/0x64
[C5BC1C90] [C02D4958] __wait_on_bit+0x60/0xb0
[C5BC1CB0] [C02D4A24] out_of_line_wait_on_bit+0x7c/0x90
[C5BC1D20] [C0082B84] __wait_on_buffer+0x2c/0x3c
[C5BC1D30] [C00F86A0] write_ordered_buffers+0x248/0x2a4
[C5BC1DE0] [C00F8A20] flush_commit_list+0x230/0x7c4
[C5BC1E20] [C00FC9C4] do_journal_end+0xe74/0xec0
[C5BC1E80] [C00FCA98] journal_end_sync+0x88/0x9c
[C5BC1EA0] [C00FD54C] reiserfs_commit_for_inode+0x140/0x1c8
[C5BC1F00] [C00DD2B8] reiserfs_sync_file+0x44/0x90
[C5BC1F20] [C008269C] do_fsync+0xb0/0x128
[C5BC1F40] [C001052C] ret_from_syscall+0x0/0x40
--- Exception: c01 at 0xfaa793c
LR = 0xfee6110
inst-sys:~ # dmesg |o
device-mapper: 4.5.0-ioctl (2005-10-04) initialised: dm-devel@redhat.com
md: Autodetecting RAID arrays.
md: autorun ...
md: ... autorun DONE.
md: raid0 personality registered for level 0
md: raid1 personality registered for level 1
raid5: measuring checksumming speed
8regs : 351.000 MB/sec
8regs_prefetch: 296.000 MB/sec
32regs : 325.000 MB/sec
32regs_prefetch: 285.000 MB/sec
raid5: using function: 8regs (351.000 MB/sec)
md: raid5 personality registered for level 5
md: raid4 personality registered for level 4
raid6: int32x1 58 MB/s
raid6: int32x2 88 MB/s
raid6: int32x4 110 MB/s
raid6: int32x8 105 MB/s
raid6: using algorithm int32x4 (110 MB/s)
md: raid6 personality registered for level 6
md: multipath personality registered for level -4
hdc: packet command error: status=0x51 { DriveReady SeekComplete Error }
hdc: packet command error: error=0x54 { AbortedCommand LastFailedSense=0x05 }
ide: failed opcode was: unknown
cdrom: open failed.
ReiserFS: hda11: found reiserfs format "3.6" with standard journal
ReiserFS: hda11: using ordered data mode
ReiserFS: hda11: journal params: device hda11, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30
ReiserFS: hda11: checking transaction log (hda11)
ReiserFS: hda11: Using r5 hash to sort names
ReiserFS: hda11: warning: Created .reiserfs_priv on hda11 - reserved for xattr storage.
Adding 295332k swap on /dev/hda10. Priority:-1 extents:1 across:295332k
SysRq : Show State
sibling
task PC pid father child younger older
init S 0FEC24B4 0 1 0 2 (NOTLB)
Call Trace:
[C2D29D90] [C2D29E40] 0xc2d29e40 (unreliable)
[C2D29E50] [C000C318] __switch_to+0x5c/0x74
[C2D29E70] [C02D3B28] schedule+0x680/0x734
[C2D29EB0] [C00332D0] do_wait+0xc88/0xe94
[C2D29F40] [C001052C] ret_from_syscall+0x0/0x40
--- Exception: c01 at 0xfec24b4
LR = 0xfe5ed00
ksoftirqd/0 S 00000000 0 2 1 3 (L-TLB)
Call Trace:
[C2D2BE90] [EA6713EA] 0xea6713ea (unreliable)
[C2D2BF50] [C000C318] __switch_to+0x5c/0x74
[C2D2BF70] [C02D3B28] schedule+0x680/0x734
[C2D2BFB0] [C0035D74] ksoftirqd+0x4c/0xa8
[C2D2BFC0] [C0048900] kthread+0xd4/0x110
[C2D2BFF0] [C00117C4] kernel_thread+0x44/0x60
watchdog/0 S 00000000 0 3 1 4 2 (L-TLB)
inst-sys:~ # ( ps faxwwwwwwww ; dmesg) > 93b47684f60cf25e8cefe19a21d94aa0257fdf36.log
inst-sys:~ # scp 93b47684f60cf25e8cefe19a21d94aa0257fdf36.log olaf@1.1.1.3:
^ permalink raw reply [flat|nested] 62+ messages in thread* Re: Linux v2.6.16-rc5
2006-03-05 20:42 ` Olaf Hering
@ 2006-03-05 21:50 ` Paul Mackerras
2006-03-05 22:22 ` Olaf Hering
2006-03-06 16:48 ` Olaf Hering
0 siblings, 2 replies; 62+ messages in thread
From: Paul Mackerras @ 2006-03-05 21:50 UTC (permalink / raw)
To: Olaf Hering; +Cc: Linus Torvalds, linuxppc-dev, Linux Kernel Mailing List
Olaf Hering writes:
> I'm now at 03929c76f3e5af919fb762e9882a9c286d361e7d, which fails as
> well. dmesg shows this:
The range from git5 to there includes David Woodhouse's syscall
entry/exit revamp (401d1f029bebb7153ca704997772113dc36d9527) and the
follow-ons which fix it for 32-bit:
9687c587596b54a77f08620595f5686ea35eed97
623703f620453c798b6fa3eb79ad8ea27bfd302a
There are also commits from Ben H that change the way we parse
addresses from the OF device tree. If you can bisect a bit further
that would be good, although you may strike problems between the 401d
and 6237 commits I mentioned above.
It would be interesting to take 401d and then apply 9687 and 6237
directly on top of it and try that, and if it fails, then try
1cd8e506209223ed10da805d99be55e268f4023c (the parent of 401d).
Paul.
^ permalink raw reply [flat|nested] 62+ messages in thread
* Re: Linux v2.6.16-rc5
2006-03-05 21:50 ` Paul Mackerras
@ 2006-03-05 22:22 ` Olaf Hering
2006-03-05 22:44 ` Olaf Hering
2006-03-06 16:48 ` Olaf Hering
1 sibling, 1 reply; 62+ messages in thread
From: Olaf Hering @ 2006-03-05 22:22 UTC (permalink / raw)
To: Paul Mackerras; +Cc: Linus Torvalds, linuxppc-dev, Linux Kernel Mailing List
On Mon, Mar 06, Paul Mackeras wrote:
> Olaf Hering writes:
>
> > I'm now at 03929c76f3e5af919fb762e9882a9c286d361e7d, which fails as
> > well. dmesg shows this:
>
> The range from git5 to there includes David Woodhouse's syscall
> entry/exit revamp (401d1f029bebb7153ca704997772113dc36d9527) and the
> follow-ons which fix it for 32-bit:
>
> 9687c587596b54a77f08620595f5686ea35eed97
> 623703f620453c798b6fa3eb79ad8ea27bfd302a
>
> There are also commits from Ben H that change the way we parse
> addresses from the OF device tree. If you can bisect a bit further
> that would be good, although you may strike problems between the 401d
> and 6237 commits I mentioned above.
I will check this tomorrow.
quick update:
d4e4b3520c4df46cf1d15a56379a6fa57e267b7d, locks up, tried two times
404849bbd2bfd62e05b36f4753f6e1af6050a824 + 3 buildfixes:
31df1678d7732b94178a6e457ed6666e4431212f
8dacaedf04467e32c50148751a96150e73323cdc
d2dd482bc17c3bc240045f80a7c4b4d5cea5e29c
This one has the syscall changes, but not the two fixes you mentioned.
It gets far, but at the point where it locks up with the d4eb, it
crashes in run_timer_softirq, branched to 0x1f4. Maybe its the result of
the missing fixes. Will continue tomorrow.
^ permalink raw reply [flat|nested] 62+ messages in thread
* Re: Linux v2.6.16-rc5
2006-03-05 22:22 ` Olaf Hering
@ 2006-03-05 22:44 ` Olaf Hering
2006-03-06 7:48 ` Olaf Hering
0 siblings, 1 reply; 62+ messages in thread
From: Olaf Hering @ 2006-03-05 22:44 UTC (permalink / raw)
To: Paul Mackerras; +Cc: Linus Torvalds, linuxppc-dev, Linux Kernel Mailing List
On Sun, Mar 05, Olaf Hering wrote:
> 404849bbd2bfd62e05b36f4753f6e1af6050a824 + 3 buildfixes:
>
> 31df1678d7732b94178a6e457ed6666e4431212f
> 8dacaedf04467e32c50148751a96150e73323cdc
> d2dd482bc17c3bc240045f80a7c4b4d5cea5e29c
>
>
> This one has the syscall changes, but not the two fixes you mentioned.
> It gets far, but at the point where it locks up with the d4eb, it
> crashes in run_timer_softirq, branched to 0x1f4. Maybe its the result of
> the missing fixes. Will continue tomorrow.
Another try with that version, now I see the corruption before the
package where it locked up before (glibc-locale, rather large).
Will backout the syscall change and try again with 404849bbd2bfd62e05b36f4753f6e1af6050a824.
ReiserFS: warning: vs-500: unknown uniqueness 1634738234
ReiserFS: warning: vs-500: unknown uniqueness 1634738234
ReiserFS: warning: vs-500: unknown uniqueness 1634738234
ReiserFS: warning: vs-500: unknown uniqueness 1634738234
ReiserFS: warning: vs-500: unknown uniqueness 1634738234
ReiserFS: warning: vs-500: unknown uniqueness 1634738234, item_len 25965, item_location 25972, free_space(entry_count) 24946
ReiserFS: hda11: warning: vs-5150: search_by_key: invalid format found in block 0. Fsck?
ReiserFS: hda11: warning: zam-7001: io error in reiserfs_find_entry
ReiserFS: warning: vs-500: unknown uniqueness 1634738234
ReiserFS: warning: vs-500: unknown uniqueness 1634738234
ReiserFS: warning: vs-500: unknown uniqueness 1634738234
ReiserFS: warning: vs-500: unknown uniqueness 1634738234
ReiserFS: warning: vs-500: unknown uniqueness 1634738234
ReiserFS: warning: vs-500: unknown uniqueness 1634738234, item_len 25965, item_location 25972, free_space(entry_count) 24946
ReiserFS: hda11: warning: vs-5150: search_by_key: invalid format found in block 0. Fsck?
ReiserFS: hda11: warning: zam-7001: io error in reiserfs_find_entry
ReiserFS: warning: vs-500: unknown uniqueness 1634738234
ReiserFS: warning: vs-500: unknown uniqueness 1634738234
ReiserFS: warning: vs-500: unknown uniqueness 1634738234
ReiserFS: warning: vs-500: unknown uniqueness 1634738234
ReiserFS: warning: vs-500: unknown uniqueness 1634738234
ReiserFS: warning: vs-500: unknown uniqueness 1634738234, item_len 25965, item_location 25972, free_space(entry_count) 24946
ReiserFS: hda11: warning: vs-5150: search_by_key: invalid format found in block 0. Fsck?
ReiserFS: hda11: warning: zam-7001: io error in reiserfs_find_entry
ReiserFS: warning: vs-500: unknown uniqueness 1634738234
ReiserFS: warning: vs-500: unknown uniqueness 1634738234
ReiserFS: warning: vs-500: unknown uniqueness 1634738234
ReiserFS: warning: vs-500: unknown uniqueness 1634738234
ReiserFS: warning: vs-500: unknown uniqueness 1634738234
ReiserFS: warning: vs-500: unknown uniqueness 1634738234, item_len 25965, item_location 25972, free_space(entry_count) 24946
ReiserFS: hda11: warning: vs-5150: search_by_key: invalid format found in block 0. Fsck?
ReiserFS: hda11: warning: zam-7001: io error in reiserfs_find_entry
ReiserFS: warning: vs-500: unknown uniqueness 1634738234
ReiserFS: warning: vs-500: unknown uniqueness 1634738234
ReiserFS: warning: vs-500: unknown uniqueness 1634738234
ReiserFS: warning: vs-500: unknown uniqueness 1634738234
ReiserFS: warning: vs-500: unknown uniqueness 1634738234
ReiserFS: warning: vs-500: unknown uniqueness 1634738234, item_len 25965, item_location 25972, free_space(entry_count) 24946
ReiserFS: hda11: warning: vs-5150: search_by_key: invalid format found in block 0. Fsck?
ReiserFS: hda11: warning: zam-7001: io error in reiserfs_find_entry
ReiserFS: warning: vs-500: unknown uniqueness 1634738234
ReiserFS: warning: vs-500: unknown uniqueness 1634738234
ReiserFS: warning: vs-500: unknown uniqueness 1634738234
ReiserFS: warning: vs-500: unknown uniqueness 1634738234
ReiserFS: warning: vs-500: unknown uniqueness 1634738234
ReiserFS: warning: vs-500: unknown uniqueness 1634738234, item_len 25965, item_location 25972, free_space(entry_count) 24946
ReiserFS: hda11: warning: vs-5150: search_by_key: invalid format found in block 0. Fsck?
ReiserFS: hda11: warning: zam-7001: io error in reiserfs_find_entry
ReiserFS: warning: vs-500: unknown uniqueness 1634738234
ReiserFS: warning: vs-500: unknown uniqueness 1634738234
ReiserFS: warning: vs-500: unknown uniqueness 1634738234
ReiserFS: warning: vs-500: unknown uniqueness 1634738234
ReiserFS: warning: vs-500: unknown uniqueness 1634738234
ReiserFS: warning: vs-500: unknown uniqueness 1634738234, item_len 25965, item_location 25972, free_space(entry_count) 24946
ReiserFS: hda11: warning: vs-5150: search_by_key: invalid format found in block 0. Fsck?
ReiserFS: hda11: warning: zam-7001: io error in reiserfs_find_entry
ReiserFS: warning: vs-500: unknown uniqueness 1634738234
ReiserFS: warning: vs-500: unknown uniqueness 1634738234
ReiserFS: warning: vs-500: unknown uniqueness 1634738234
ReiserFS: warning: vs-500: unknown uniqueness 1634738234
ReiserFS: warning: vs-500: unknown uniqueness 1634738234
ReiserFS: warning: vs-500: unknown uniqueness 1634738234, item_len 25965, item_location 25972, free_space(entry_count) 24946
ReiserFS: hda11: warning: vs-5150: search_by_key: invalid format found in block 0. Fsck?
ReiserFS: hda11: warning: zam-7001: io error in reiserfs_find_entry
ReiserFS: warning: vs-500: unknown uniqueness 1634738234
ReiserFS: warning: vs-500: unknown uniqueness 1634738234
ReiserFS: warning: vs-500: unknown uniqueness 1634738234
ReiserFS: warning: vs-500: unknown uniqueness 1634738234
ReiserFS: warning: vs-500: unknown uniqueness 1634738234
ReiserFS: warning: vs-500: unknown uniqueness 1634738234, item_len 25965, item_location 25972, free_space(entry_count) 24946
ReiserFS: hda11: warning: vs-5150: search_by_key: invalid format found in block 0. Fsck?
ReiserFS: hda11: warning: zam-7001: io error in reiserfs_find_entry
ReiserFS: warning: vs-500: unknown uniqueness 1634738234
ReiserFS: warning: vs-500: unknown uniqueness 1634738234
ReiserFS: warning: vs-500: unknown uniqueness 1634738234
ReiserFS: warning: vs-500: unknown uniqueness 1634738234
ReiserFS: warning: vs-500: unknown uniqueness 1634738234
ReiserFS: warning: vs-500: unknown uniqueness 1634738234, item_len 25965, item_location 25972, free_space(entry_count) 24946
ReiserFS: hda11: warning: vs-5150: search_by_key: invalid format found in block 0. Fsck?
ReiserFS: hda11: warning: zam-7001: io error in reiserfs_find_entry
^ permalink raw reply [flat|nested] 62+ messages in thread
* Re: Linux v2.6.16-rc5
2006-03-05 22:44 ` Olaf Hering
@ 2006-03-06 7:48 ` Olaf Hering
0 siblings, 0 replies; 62+ messages in thread
From: Olaf Hering @ 2006-03-06 7:48 UTC (permalink / raw)
To: Paul Mackerras; +Cc: linuxppc-dev, Linus Torvalds, Linux Kernel Mailing List
On Sun, Mar 05, Olaf Hering wrote:
> On Sun, Mar 05, Olaf Hering wrote:
>
> > 404849bbd2bfd62e05b36f4753f6e1af6050a824 + 3 buildfixes:
> >
> > 31df1678d7732b94178a6e457ed6666e4431212f
> > 8dacaedf04467e32c50148751a96150e73323cdc
> > d2dd482bc17c3bc240045f80a7c4b4d5cea5e29c
> >
> >
> > This one has the syscall changes, but not the two fixes you mentioned.
> > It gets far, but at the point where it locks up with the d4eb, it
> > crashes in run_timer_softirq, branched to 0x1f4. Maybe its the result of
> > the missing fixes. Will continue tomorrow.
>
> Another try with that version, now I see the corruption before the
> package where it locked up before (glibc-locale, rather large).
> Will backout the syscall change and try again with 404849bbd2bfd62e05b36f4753f6e1af6050a824.
Its not the syscall change at least. Looking further.
^ permalink raw reply [flat|nested] 62+ messages in thread
* Re: Linux v2.6.16-rc5
2006-03-05 21:50 ` Paul Mackerras
2006-03-05 22:22 ` Olaf Hering
@ 2006-03-06 16:48 ` Olaf Hering
2006-03-06 22:20 ` Olaf Hering
1 sibling, 1 reply; 62+ messages in thread
From: Olaf Hering @ 2006-03-06 16:48 UTC (permalink / raw)
To: Paul Mackerras; +Cc: Linus Torvalds, linuxppc-dev, Linux Kernel Mailing List
On Mon, Mar 06, Paul Mackeras wrote:
> There are also commits from Ben H that change the way we parse
> addresses from the OF device tree. If you can bisect a bit further
> that would be good, although you may strike problems between the 401d
> and 6237 commits I mentioned above.
What I have right now is this, which got me in a non-compiling state.
I will pick the udbg stuff and apply the relevant changes to -git5.
==> .git/HEAD <==
463ce0e103f419f51b1769111e73fe8bb305d0ec
==> .git/refs/bisect/bad <==
51d3082fe6e55aecfa17113dbe98077c749f724c
==> .git/refs/bisect/good-5367f2d67c7d0bf1faae90e6e7b4e2ac3c9b5e0f <==
5367f2d67c7d0bf1faae90e6e7b4e2ac3c9b5e0f
==> .git/refs/bisect/good-d1405b869850982f05c7ec0d3f137ca27588192f <==
d1405b869850982f05c7ec0d3f137ca27588192f
==> .git/BISECT_LOG <==
git-bisect start
# good: [5367f2d67c7d0bf1faae90e6e7b4e2ac3c9b5e0f] Merge branch 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/roland/infiniband
git-bisect good 5367f2d67c7d0bf1faae90e6e7b4e2ac3c9b5e0f
# bad: [977127174a7dff52d17faeeb4c4949a54221881f] Merge master.kernel.org:/pub/scm/linux/kernel/git/gregkh/pci-2.6
git-bisect bad 977127174a7dff52d17faeeb4c4949a54221881f
# bad: [93b47684f60cf25e8cefe19a21d94aa0257fdf36] drivers/*rest*: Replace pci_module_init() with pci_register_driver()
git-bisect bad 93b47684f60cf25e8cefe19a21d94aa0257fdf36
# bad: [03929c76f3e5af919fb762e9882a9c286d361e7d] ppc32: cpm_uart: fix xchar sending
git-bisect bad 03929c76f3e5af919fb762e9882a9c286d361e7d
# bad: [d4e4b3520c4df46cf1d15a56379a6fa57e267b7d] powerpc: fix for "Update OF address parsers"
git-bisect bad d4e4b3520c4df46cf1d15a56379a6fa57e267b7d
# bad: [404849bbd2bfd62e05b36f4753f6e1af6050a824] powerpc: Remove some unneeded fields from the paca
git-bisect bad 404849bbd2bfd62e05b36f4753f6e1af6050a824
# good: [d1405b869850982f05c7ec0d3f137ca27588192f] powerpc: Add OF address parsing code (#2)
git-bisect good d1405b869850982f05c7ec0d3f137ca27588192f
# bad: [e199500c6280aadf98c185db99fd24ab61ebe0c7] powerpc: partly merge iseries do_IRQ
git-bisect bad e199500c6280aadf98c185db99fd24ab61ebe0c7
# bad: [2c5bd01f8f5d7c655d9d1aa60b696d980947e3be] powerpc: convert macio_asic to use prom_parse
git-bisect bad 2c5bd01f8f5d7c655d9d1aa60b696d980947e3be
# bad: [51d3082fe6e55aecfa17113dbe98077c749f724c] powerpc: Unify udbg (#2)
git-bisect bad 51d3082fe6e55aecfa17113dbe98077c749f724c
^ permalink raw reply [flat|nested] 62+ messages in thread
* Re: Linux v2.6.16-rc5
2006-03-06 16:48 ` Olaf Hering
@ 2006-03-06 22:20 ` Olaf Hering
2006-03-06 23:02 ` Olaf Hering
0 siblings, 1 reply; 62+ messages in thread
From: Olaf Hering @ 2006-03-06 22:20 UTC (permalink / raw)
To: Paul Mackerras; +Cc: Linus Torvalds, linuxppc-dev, Linux Kernel Mailing List
[-- Attachment #1: Type: text/plain, Size: 2353 bytes --]
On Mon, Mar 06, Olaf Hering wrote:
> On Mon, Mar 06, Paul Mackeras wrote:
>
> > There are also commits from Ben H that change the way we parse
> > addresses from the OF device tree. If you can bisect a bit further
> > that would be good, although you may strike problems between the 401d
> > and 6237 commits I mentioned above.
>
> What I have right now is this, which got me in a non-compiling state.
> I will pick the udbg stuff and apply the relevant changes to -git5.
Here is the working vs. non-working thing.
So its the udbg patch. My used .config is attached, use yes '' | make oldconfig
to get it in shape.
--- ../series.conf.good.463ce0e103f419f51b1769111e73fe8bb305d0ec 2006-03-06 22:47:03.040936341 +0100
+++ series.conf 2006-03-06 22:48:50.611294236 +0100
@@ -25,21 +25,28 @@
patches.suse/suse-ppc-legacy-io.patch
patches.arch/0022-powerpc-incorrect-rmo_top-handling-in-prom_init.txt
+ # buildfix
+ patches.suse/9100b205fdc70b300894954ebebbf2709c5ed525.patch
+
#kexec32
patches.suse/3d1229d6ae92ed1994f4411b8493327ef8f4b76f.patch
- # udbg2
+ # address parsing code2
patches.suse/d1405b869850982f05c7ec0d3f137ca27588192f.patch
#serial port2
patches.suse/463ce0e103f419f51b1769111e73fe8bb305d0ec.patch
- # buildfix
- patches.suse/9100b205fdc70b300894954ebebbf2709c5ed525.patch
+
+ #Subject: [PATCH] powerpc: Unify udbg (#2)
+ patches.suse/51d3082fe6e55aecfa17113dbe98077c749f724c.patch
+ #Subject: [PATCH] powerpc: serial port discovery: cope with broken firmware
+ patches.suse/31df1678d7732b94178a6e457ed6666e4431212f.patch
+ #Subject: [PATCH] powerpc: More serial probe fixes (#2)
+ patches.suse/8dacaedf04467e32c50148751a96150e73323cdc.patch
+
#- patches.suse/ac448afbcdcc218fd8d177960466ecc4a523722f.patch
#- patches.suse/36874579dbf4cafa31486d4207c6807efbbf1378.patch
#- patches.suse/575e321606c5673efabf28c0fa075e198980c44e.patch
# patches.suse/3b212db9217d02e623eaa12f41c9b5f8c6a99535.patch
-# patches.suse/31df1678d7732b94178a6e457ed6666e4431212f.patch
-# patches.suse/8dacaedf04467e32c50148751a96150e73323cdc.patch
#- patches.suse/d2dd482bc17c3bc240045f80a7c4b4d5cea5e29c.patch
#+rev patches.suse/bcb05504edf0e27a648aa1059cbb71e8746758a1.patch
[-- Attachment #2: default --]
[-- Type: text/plain, Size: 46720 bytes --]
#
# Automatically generated make config: don't edit
#
# CONFIG_PPC64 is not set
CONFIG_PPC32=y
CONFIG_PPC_MERGE=y
CONFIG_MMU=y
CONFIG_GENERIC_HARDIRQS=y
CONFIG_RWSEM_XCHGADD_ALGORITHM=y
CONFIG_GENERIC_CALIBRATE_DELAY=y
CONFIG_PPC=y
CONFIG_EARLY_PRINTK=y
CONFIG_GENERIC_NVRAM=y
CONFIG_SCHED_NO_NO_OMIT_FRAME_POINTER=y
CONFIG_ARCH_MAY_HAVE_PC_FDC=y
CONFIG_PPC_OF=y
CONFIG_PPC_UDBG_16550=y
# CONFIG_GENERIC_TBSYNC is not set
# CONFIG_DEFAULT_UIMAGE is not set
#
# Processor support
#
CONFIG_CLASSIC32=y
# CONFIG_PPC_52xx is not set
# CONFIG_PPC_82xx is not set
# CONFIG_PPC_83xx is not set
# CONFIG_40x is not set
# CONFIG_44x is not set
# CONFIG_8xx is not set
# CONFIG_E200 is not set
# CONFIG_E500 is not set
CONFIG_6xx=y
CONFIG_PPC_FPU=y
CONFIG_ALTIVEC=y
CONFIG_PPC_STD_MMU=y
CONFIG_PPC_STD_MMU_32=y
# CONFIG_SMP is not set
#
# Code maturity level options
#
CONFIG_EXPERIMENTAL=y
CONFIG_BROKEN_ON_SMP=y
CONFIG_INIT_ENV_ARG_LIMIT=32
#
# General setup
#
CONFIG_LOCALVERSION="-default"
# CONFIG_LOCALVERSION_AUTO is not set
CONFIG_SUSE_KERNEL=y
CONFIG_SWAP=y
CONFIG_SYSVIPC=y
CONFIG_POSIX_MQUEUE=y
CONFIG_BSD_PROCESS_ACCT=y
CONFIG_BSD_PROCESS_ACCT_V3=y
CONFIG_TASK_DELAY_ACCT=y
CONFIG_SYSCTL=y
CONFIG_AUDIT=y
CONFIG_AUDITSYSCALL=y
CONFIG_IKCONFIG=y
CONFIG_IKCONFIG_PROC=y
CONFIG_INITRAMFS_SOURCE=""
CONFIG_CC_OPTIMIZE_FOR_SIZE=y
# CONFIG_EMBEDDED is not set
CONFIG_KALLSYMS=y
CONFIG_KALLSYMS_ALL=y
# CONFIG_KALLSYMS_EXTRA_PASS is not set
CONFIG_HOTPLUG=y
CONFIG_PRINTK=y
CONFIG_BUG=y
CONFIG_ELF_CORE=y
CONFIG_BASE_FULL=y
CONFIG_FUTEX=y
CONFIG_EPOLL=y
CONFIG_SHMEM=y
CONFIG_CC_ALIGN_FUNCTIONS=0
CONFIG_CC_ALIGN_LABELS=0
CONFIG_CC_ALIGN_LOOPS=0
CONFIG_CC_ALIGN_JUMPS=0
CONFIG_SLAB=y
# CONFIG_TINY_SHMEM is not set
CONFIG_BASE_SMALL=0
# CONFIG_SLOB is not set
#
# Loadable module support
#
CONFIG_MODULES=y
CONFIG_MODULE_UNLOAD=y
# CONFIG_MODULE_FORCE_UNLOAD is not set
CONFIG_OBSOLETE_MODPARM=y
CONFIG_MODVERSIONS=y
CONFIG_MODULE_SRCVERSION_ALL=y
CONFIG_KMOD=y
#
# Block layer
#
CONFIG_LBD=y
#
# IO Schedulers
#
CONFIG_IOSCHED_NOOP=y
CONFIG_IOSCHED_AS=y
CONFIG_IOSCHED_DEADLINE=y
CONFIG_IOSCHED_CFQ=y
# CONFIG_DEFAULT_AS is not set
# CONFIG_DEFAULT_DEADLINE is not set
CONFIG_DEFAULT_CFQ=y
# CONFIG_DEFAULT_NOOP is not set
CONFIG_DEFAULT_IOSCHED="cfq"
#
# Platform support
#
CONFIG_PPC_MULTIPLATFORM=y
# CONFIG_PPC_ISERIES is not set
# CONFIG_EMBEDDED6xx is not set
# CONFIG_APUS is not set
CONFIG_PPC_CHRP=y
CONFIG_PPC_PMAC=y
CONFIG_MPIC=y
CONFIG_PPC_RTAS=y
# CONFIG_RTAS_ERROR_LOGGING is not set
CONFIG_RTAS_PROC=y
# CONFIG_MMIO_NVRAM is not set
CONFIG_PPC_MPC106=y
CONFIG_CPU_FREQ=y
CONFIG_CPU_FREQ_TABLE=y
# CONFIG_CPU_FREQ_DEBUG is not set
CONFIG_CPU_FREQ_STAT=m
CONFIG_CPU_FREQ_STAT_DETAILS=y
CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE=y
# CONFIG_CPU_FREQ_DEFAULT_GOV_USERSPACE is not set
CONFIG_CPU_FREQ_GOV_PERFORMANCE=y
CONFIG_CPU_FREQ_GOV_POWERSAVE=m
CONFIG_CPU_FREQ_GOV_USERSPACE=m
CONFIG_CPU_FREQ_GOV_ONDEMAND=m
CONFIG_CPU_FREQ_GOV_CONSERVATIVE=m
CONFIG_CPU_FREQ_PMAC=y
CONFIG_PPC601_SYNC_FIX=y
CONFIG_TAU=y
# CONFIG_TAU_INT is not set
# CONFIG_TAU_AVERAGE is not set
# CONFIG_WANT_EARLY_SERIAL is not set
#
# Kernel options
#
CONFIG_HIGHMEM=y
# CONFIG_HZ_100 is not set
CONFIG_HZ_250=y
# CONFIG_HZ_1000 is not set
CONFIG_HZ=250
# CONFIG_PREEMPT_NONE is not set
CONFIG_PREEMPT_VOLUNTARY=y
# CONFIG_PREEMPT is not set
CONFIG_BINFMT_ELF=y
CONFIG_BINFMT_MISC=m
# CONFIG_KEXEC is not set
CONFIG_ARCH_FLATMEM_ENABLE=y
CONFIG_SELECT_MEMORY_MODEL=y
CONFIG_FLATMEM_MANUAL=y
# CONFIG_DISCONTIGMEM_MANUAL is not set
# CONFIG_SPARSEMEM_MANUAL is not set
CONFIG_FLATMEM=y
CONFIG_FLAT_NODE_MEM_MAP=y
# CONFIG_SPARSEMEM_STATIC is not set
CONFIG_SPLIT_PTLOCK_CPUS=4
CONFIG_PROC_DEVICETREE=y
# CONFIG_CMDLINE_BOOL is not set
CONFIG_PM=y
CONFIG_PM_LEGACY=y
# CONFIG_PM_DEBUG is not set
CONFIG_SOFTWARE_SUSPEND=y
CONFIG_PM_STD_PARTITION=""
CONFIG_SECCOMP=y
CONFIG_ISA_DMA_API=y
#
# Bus options
#
# CONFIG_ISA is not set
CONFIG_GENERIC_ISA_DMA=y
CONFIG_PPC_I8259=y
CONFIG_PPC_INDIRECT_PCI=y
CONFIG_PCI=y
CONFIG_PCI_DOMAINS=y
# CONFIG_PCI_LEGACY_PROC is not set
# CONFIG_PCI_DEBUG is not set
#
# PCCARD (PCMCIA/CardBus) support
#
CONFIG_PCCARD=m
# CONFIG_PCMCIA_DEBUG is not set
CONFIG_PCMCIA=m
CONFIG_PCMCIA_LOAD_CIS=y
CONFIG_PCMCIA_IOCTL=y
CONFIG_CARDBUS=y
#
# PC-card bridges
#
CONFIG_YENTA=m
CONFIG_YENTA_O2=y
CONFIG_YENTA_RICOH=y
CONFIG_YENTA_TI=y
CONFIG_YENTA_ENE_TUNE=y
CONFIG_YENTA_TOSHIBA=y
# CONFIG_PD6729 is not set
CONFIG_I82092=m
CONFIG_PCCARD_NONSTATIC=m
#
# PCI Hotplug Support
#
# CONFIG_HOTPLUG_PCI is not set
#
# Advanced setup
#
# CONFIG_ADVANCED_OPTIONS is not set
#
# Default settings for advanced configuration options are used
#
CONFIG_HIGHMEM_START=0xfe000000
CONFIG_LOWMEM_SIZE=0x30000000
CONFIG_KERNEL_START=0xc0000000
CONFIG_TASK_SIZE=0x80000000
CONFIG_BOOT_LOAD=0x00800000
#
# Networking
#
CONFIG_NET=y
#
# Networking options
#
# CONFIG_NETDEBUG is not set
CONFIG_PACKET=y
CONFIG_PACKET_MMAP=y
CONFIG_UNIX=y
CONFIG_XFRM=y
CONFIG_XFRM_USER=m
CONFIG_NET_KEY=m
CONFIG_INET=y
CONFIG_IP_MULTICAST=y
CONFIG_IP_ADVANCED_ROUTER=y
CONFIG_ASK_IP_FIB_HASH=y
# CONFIG_IP_FIB_TRIE is not set
CONFIG_IP_FIB_HASH=y
CONFIG_IP_MULTIPLE_TABLES=y
CONFIG_IP_ROUTE_FWMARK=y
CONFIG_IP_ROUTE_MULTIPATH=y
# CONFIG_IP_ROUTE_MULTIPATH_CACHED is not set
# CONFIG_IP_ROUTE_VERBOSE is not set
# CONFIG_IP_PNP is not set
CONFIG_NET_IPIP=m
CONFIG_NET_IPGRE=m
CONFIG_NET_IPGRE_BROADCAST=y
CONFIG_IP_MROUTE=y
CONFIG_IP_PIMSM_V1=y
CONFIG_IP_PIMSM_V2=y
# CONFIG_ARPD is not set
CONFIG_SYN_COOKIES=y
CONFIG_INET_AH=m
CONFIG_INET_ESP=m
CONFIG_INET_IPCOMP=m
CONFIG_INET_TUNNEL=m
CONFIG_INET_DIAG=m
CONFIG_INET_TCP_DIAG=m
CONFIG_TCP_CONG_ADVANCED=y
#
# TCP congestion control
#
CONFIG_TCP_CONG_BIC=m
CONFIG_TCP_CONG_CUBIC=m
CONFIG_TCP_CONG_WESTWOOD=m
CONFIG_TCP_CONG_HTCP=m
CONFIG_TCP_CONG_HSTCP=m
CONFIG_TCP_CONG_HYBLA=m
CONFIG_TCP_CONG_VEGAS=m
CONFIG_TCP_CONG_SCALABLE=m
#
# IP: Virtual Server Configuration
#
# CONFIG_IP_VS is not set
CONFIG_IPV6=m
CONFIG_IPV6_PRIVACY=y
CONFIG_INET6_AH=m
CONFIG_INET6_ESP=m
CONFIG_INET6_IPCOMP=m
CONFIG_INET6_TUNNEL=m
CONFIG_IPV6_TUNNEL=m
CONFIG_NETFILTER=y
# CONFIG_NETFILTER_DEBUG is not set
CONFIG_BRIDGE_NETFILTER=y
#
# Core Netfilter Configuration
#
CONFIG_NETFILTER_NETLINK=m
CONFIG_NETFILTER_NETLINK_QUEUE=m
CONFIG_NETFILTER_NETLINK_LOG=m
CONFIG_NETFILTER_XTABLES=m
CONFIG_NETFILTER_XT_TARGET_CLASSIFY=m
CONFIG_NETFILTER_XT_TARGET_CONNMARK=m
CONFIG_NETFILTER_XT_TARGET_MARK=m
CONFIG_NETFILTER_XT_TARGET_NFQUEUE=m
CONFIG_NETFILTER_XT_TARGET_NOTRACK=m
CONFIG_NETFILTER_XT_MATCH_COMMENT=m
CONFIG_NETFILTER_XT_MATCH_CONNMARK=m
CONFIG_NETFILTER_XT_MATCH_CONNTRACK=m
CONFIG_NETFILTER_XT_MATCH_DCCP=m
CONFIG_NETFILTER_XT_MATCH_HELPER=m
CONFIG_NETFILTER_XT_MATCH_LENGTH=m
CONFIG_NETFILTER_XT_MATCH_LIMIT=m
CONFIG_NETFILTER_XT_MATCH_MAC=m
CONFIG_NETFILTER_XT_MATCH_MARK=m
CONFIG_NETFILTER_XT_MATCH_PHYSDEV=m
CONFIG_NETFILTER_XT_MATCH_PKTTYPE=m
CONFIG_NETFILTER_XT_MATCH_REALM=m
CONFIG_NETFILTER_XT_MATCH_SCTP=m
CONFIG_NETFILTER_XT_MATCH_STATE=m
CONFIG_NETFILTER_XT_MATCH_STRING=m
CONFIG_NETFILTER_XT_MATCH_TCPMSS=m
#
# IP: Netfilter Configuration
#
CONFIG_IP_NF_CONNTRACK=m
# CONFIG_IP_NF_CT_ACCT is not set
CONFIG_IP_NF_CONNTRACK_MARK=y
CONFIG_IP_NF_CONNTRACK_EVENTS=y
CONFIG_IP_NF_CONNTRACK_NETLINK=m
CONFIG_IP_NF_CT_PROTO_SCTP=m
CONFIG_IP_NF_FTP=m
CONFIG_IP_NF_IRC=m
CONFIG_IP_NF_NETBIOS_NS=m
CONFIG_IP_NF_TFTP=m
CONFIG_IP_NF_AMANDA=m
CONFIG_IP_NF_PPTP=m
CONFIG_IP_NF_QUEUE=m
CONFIG_IP_NF_IPTABLES=m
CONFIG_IP_NF_MATCH_IPRANGE=m
CONFIG_IP_NF_MATCH_MULTIPORT=m
CONFIG_IP_NF_MATCH_TOS=m
CONFIG_IP_NF_MATCH_RECENT=m
CONFIG_IP_NF_MATCH_ECN=m
CONFIG_IP_NF_MATCH_DSCP=m
CONFIG_IP_NF_MATCH_AH_ESP=m
CONFIG_IP_NF_MATCH_TTL=m
CONFIG_IP_NF_MATCH_OWNER=m
CONFIG_IP_NF_MATCH_ADDRTYPE=m
CONFIG_IP_NF_MATCH_HASHLIMIT=m
CONFIG_IP_NF_MATCH_POLICY=m
CONFIG_IP_NF_MATCH_IPV4OPTIONS=m
CONFIG_IP_NF_FILTER=m
CONFIG_IP_NF_TARGET_REJECT=m
CONFIG_IP_NF_TARGET_LOG=m
CONFIG_IP_NF_TARGET_ULOG=m
CONFIG_IP_NF_TARGET_TCPMSS=m
CONFIG_IP_NF_NAT=m
CONFIG_IP_NF_NAT_NEEDED=y
CONFIG_IP_NF_TARGET_MASQUERADE=m
CONFIG_IP_NF_TARGET_REDIRECT=m
CONFIG_IP_NF_TARGET_NETMAP=m
CONFIG_IP_NF_TARGET_SAME=m
CONFIG_IP_NF_NAT_SNMP_BASIC=m
CONFIG_IP_NF_NAT_IRC=m
CONFIG_IP_NF_NAT_FTP=m
CONFIG_IP_NF_NAT_TFTP=m
CONFIG_IP_NF_NAT_AMANDA=m
CONFIG_IP_NF_NAT_PPTP=m
CONFIG_IP_NF_MANGLE=m
CONFIG_IP_NF_TARGET_TOS=m
CONFIG_IP_NF_TARGET_ECN=m
CONFIG_IP_NF_TARGET_DSCP=m
CONFIG_IP_NF_TARGET_TTL=m
CONFIG_IP_NF_TARGET_CLUSTERIP=m
CONFIG_IP_NF_RAW=m
CONFIG_IP_NF_ARPTABLES=m
CONFIG_IP_NF_ARPFILTER=m
CONFIG_IP_NF_ARP_MANGLE=m
#
# IPv6: Netfilter Configuration (EXPERIMENTAL)
#
CONFIG_IP6_NF_QUEUE=m
CONFIG_IP6_NF_IPTABLES=m
CONFIG_IP6_NF_MATCH_RT=m
CONFIG_IP6_NF_MATCH_OPTS=m
CONFIG_IP6_NF_MATCH_FRAG=m
CONFIG_IP6_NF_MATCH_HL=m
CONFIG_IP6_NF_MATCH_MULTIPORT=m
CONFIG_IP6_NF_MATCH_OWNER=m
CONFIG_IP6_NF_MATCH_IPV6HEADER=m
CONFIG_IP6_NF_MATCH_AHESP=m
CONFIG_IP6_NF_MATCH_EUI64=m
CONFIG_IP6_NF_MATCH_POLICY=m
CONFIG_IP6_NF_FILTER=m
CONFIG_IP6_NF_TARGET_LOG=m
CONFIG_IP6_NF_TARGET_REJECT=m
CONFIG_IP6_NF_MANGLE=m
CONFIG_IP6_NF_TARGET_HL=m
CONFIG_IP6_NF_RAW=m
#
# DECnet: Netfilter Configuration
#
CONFIG_DECNET_NF_GRABULATOR=m
#
# Bridge: Netfilter Configuration
#
CONFIG_BRIDGE_NF_EBTABLES=m
CONFIG_BRIDGE_EBT_BROUTE=m
CONFIG_BRIDGE_EBT_T_FILTER=m
CONFIG_BRIDGE_EBT_T_NAT=m
CONFIG_BRIDGE_EBT_802_3=m
CONFIG_BRIDGE_EBT_AMONG=m
CONFIG_BRIDGE_EBT_ARP=m
CONFIG_BRIDGE_EBT_IP=m
CONFIG_BRIDGE_EBT_LIMIT=m
CONFIG_BRIDGE_EBT_MARK=m
CONFIG_BRIDGE_EBT_PKTTYPE=m
CONFIG_BRIDGE_EBT_STP=m
CONFIG_BRIDGE_EBT_VLAN=m
CONFIG_BRIDGE_EBT_ARPREPLY=m
CONFIG_BRIDGE_EBT_DNAT=m
CONFIG_BRIDGE_EBT_MARK_T=m
CONFIG_BRIDGE_EBT_REDIRECT=m
CONFIG_BRIDGE_EBT_SNAT=m
CONFIG_BRIDGE_EBT_LOG=m
CONFIG_BRIDGE_EBT_ULOG=m
#
# DCCP Configuration (EXPERIMENTAL)
#
CONFIG_IP_DCCP=m
CONFIG_INET_DCCP_DIAG=m
#
# DCCP CCIDs Configuration (EXPERIMENTAL)
#
CONFIG_IP_DCCP_CCID3=m
CONFIG_IP_DCCP_TFRC_LIB=m
#
# DCCP Kernel Hacking
#
# CONFIG_IP_DCCP_DEBUG is not set
# CONFIG_IP_DCCP_UNLOAD_HACK is not set
#
# SCTP Configuration (EXPERIMENTAL)
#
CONFIG_IP_SCTP=m
# CONFIG_SCTP_DBG_MSG is not set
# CONFIG_SCTP_DBG_OBJCNT is not set
# CONFIG_SCTP_HMAC_NONE is not set
# CONFIG_SCTP_HMAC_SHA1 is not set
CONFIG_SCTP_HMAC_MD5=y
#
# TIPC Configuration (EXPERIMENTAL)
#
# CONFIG_TIPC is not set
# CONFIG_ATM is not set
CONFIG_BRIDGE=m
CONFIG_VLAN_8021Q=m
CONFIG_DECNET=m
# CONFIG_DECNET_ROUTER is not set
CONFIG_LLC=y
CONFIG_LLC2=m
CONFIG_IPX=m
CONFIG_IPX_INTERN=y
CONFIG_ATALK=m
CONFIG_DEV_APPLETALK=y
CONFIG_IPDDP=m
CONFIG_IPDDP_ENCAP=y
CONFIG_IPDDP_DECAP=y
CONFIG_X25=m
CONFIG_LAPB=m
# CONFIG_NET_DIVERT is not set
# CONFIG_ECONET is not set
# CONFIG_WAN_ROUTER is not set
#
# QoS and/or fair queueing
#
CONFIG_NET_SCHED=y
CONFIG_NET_SCH_CLK_JIFFIES=y
# CONFIG_NET_SCH_CLK_GETTIMEOFDAY is not set
# CONFIG_NET_SCH_CLK_CPU is not set
#
# Queueing/Scheduling
#
CONFIG_NET_SCH_CBQ=m
CONFIG_NET_SCH_HTB=m
CONFIG_NET_SCH_HFSC=m
CONFIG_NET_SCH_PRIO=m
CONFIG_NET_SCH_RED=m
CONFIG_NET_SCH_SFQ=m
CONFIG_NET_SCH_TEQL=m
CONFIG_NET_SCH_TBF=m
CONFIG_NET_SCH_GRED=m
CONFIG_NET_SCH_DSMARK=m
CONFIG_NET_SCH_NETEM=m
CONFIG_NET_SCH_INGRESS=m
#
# Classification
#
CONFIG_NET_CLS=y
CONFIG_NET_CLS_BASIC=m
CONFIG_NET_CLS_TCINDEX=m
CONFIG_NET_CLS_ROUTE4=m
CONFIG_NET_CLS_ROUTE=y
CONFIG_NET_CLS_FW=m
CONFIG_NET_CLS_U32=m
CONFIG_CLS_U32_PERF=y
CONFIG_CLS_U32_MARK=y
CONFIG_NET_CLS_RSVP=m
CONFIG_NET_CLS_RSVP6=m
CONFIG_NET_EMATCH=y
CONFIG_NET_EMATCH_STACK=32
CONFIG_NET_EMATCH_CMP=m
CONFIG_NET_EMATCH_NBYTE=m
CONFIG_NET_EMATCH_U32=m
CONFIG_NET_EMATCH_META=m
CONFIG_NET_EMATCH_TEXT=m
CONFIG_NET_CLS_ACT=y
CONFIG_NET_ACT_POLICE=m
CONFIG_NET_ACT_GACT=m
CONFIG_GACT_PROB=y
CONFIG_NET_ACT_MIRRED=m
CONFIG_NET_ACT_IPT=m
CONFIG_NET_ACT_PEDIT=m
CONFIG_NET_ACT_SIMP=m
CONFIG_NET_CLS_IND=y
CONFIG_NET_ESTIMATOR=y
#
# Network testing
#
CONFIG_NET_PKTGEN=m
# CONFIG_HAMRADIO is not set
CONFIG_IRDA=m
#
# IrDA protocols
#
CONFIG_IRLAN=m
CONFIG_IRNET=m
CONFIG_IRCOMM=m
CONFIG_IRDA_ULTRA=y
#
# IrDA options
#
CONFIG_IRDA_CACHE_LAST_LSAP=y
CONFIG_IRDA_FAST_RR=y
# CONFIG_IRDA_DEBUG is not set
#
# Infrared-port device drivers
#
#
# SIR device drivers
#
CONFIG_IRTTY_SIR=m
#
# Dongle support
#
CONFIG_DONGLE=y
CONFIG_ESI_DONGLE=m
CONFIG_ACTISYS_DONGLE=m
CONFIG_TEKRAM_DONGLE=m
CONFIG_LITELINK_DONGLE=m
CONFIG_MA600_DONGLE=m
CONFIG_GIRBIL_DONGLE=m
CONFIG_MCP2120_DONGLE=m
CONFIG_OLD_BELKIN_DONGLE=m
CONFIG_ACT200L_DONGLE=m
#
# Old SIR device drivers
#
CONFIG_IRPORT_SIR=m
#
# Old Serial dongle support
#
# CONFIG_DONGLE_OLD is not set
#
# FIR device drivers
#
CONFIG_USB_IRDA=m
CONFIG_SIGMATEL_FIR=m
CONFIG_NSC_FIR=m
CONFIG_WINBOND_FIR=m
CONFIG_TOSHIBA_FIR=m
CONFIG_SMC_IRCC_FIR=m
CONFIG_ALI_FIR=m
CONFIG_VLSI_FIR=m
CONFIG_VIA_FIR=m
CONFIG_BT=m
CONFIG_BT_L2CAP=m
CONFIG_BT_SCO=m
CONFIG_BT_RFCOMM=m
CONFIG_BT_RFCOMM_TTY=y
CONFIG_BT_BNEP=m
CONFIG_BT_BNEP_MC_FILTER=y
CONFIG_BT_BNEP_PROTO_FILTER=y
CONFIG_BT_HIDP=m
#
# Bluetooth device drivers
#
CONFIG_BT_HCIUSB=m
CONFIG_BT_HCIUSB_SCO=y
CONFIG_BT_HCIUART=m
CONFIG_BT_HCIUART_H4=y
CONFIG_BT_HCIUART_BCSP=y
CONFIG_BT_HCIBCM203X=m
CONFIG_BT_HCIBPA10X=m
CONFIG_BT_HCIBFUSB=m
CONFIG_BT_HCIDTL1=m
CONFIG_BT_HCIBT3C=m
CONFIG_BT_HCIBLUECARD=m
CONFIG_BT_HCIBTUART=m
CONFIG_BT_HCIVHCI=m
CONFIG_IEEE80211=m
# CONFIG_IEEE80211_DEBUG is not set
CONFIG_IEEE80211_CRYPT_WEP=m
CONFIG_IEEE80211_CRYPT_CCMP=m
CONFIG_IEEE80211_CRYPT_TKIP=m
#
# Device Drivers
#
#
# Generic Driver Options
#
CONFIG_STANDALONE=y
CONFIG_PREVENT_FIRMWARE_BUILD=y
CONFIG_FW_LOADER=m
# CONFIG_DEBUG_DRIVER is not set
#
# Connector - unified userspace <-> kernelspace linker
#
CONFIG_CONNECTOR=y
CONFIG_PROC_EVENTS=y
#
# Memory Technology Devices (MTD)
#
# CONFIG_MTD is not set
#
# Parallel port support
#
CONFIG_PARPORT=m
CONFIG_PARPORT_PC=m
CONFIG_PARPORT_SERIAL=m
CONFIG_PARPORT_PC_FIFO=y
# CONFIG_PARPORT_PC_SUPERIO is not set
# CONFIG_PARPORT_PC_PCMCIA is not set
CONFIG_PARPORT_NOT_PC=y
# CONFIG_PARPORT_GSC is not set
CONFIG_PARPORT_1284=y
#
# Plug and Play support
#
#
# Block devices
#
CONFIG_BLK_DEV_FD=m
CONFIG_MAC_FLOPPY=m
# CONFIG_PARIDE is not set
# CONFIG_BLK_CPQ_DA is not set
# CONFIG_BLK_CPQ_CISS_DA is not set
# CONFIG_BLK_DEV_DAC960 is not set
# CONFIG_BLK_DEV_UMEM is not set
# CONFIG_BLK_DEV_COW_COMMON is not set
CONFIG_BLK_DEV_LOOP=m
CONFIG_BLK_DEV_CRYPTOLOOP=m
CONFIG_BLK_DEV_NBD=m
# CONFIG_BLK_DEV_SX8 is not set
# CONFIG_BLK_DEV_UB is not set
CONFIG_BLK_DEV_RAM=y
CONFIG_BLK_DEV_RAM_COUNT=16
CONFIG_BLK_DEV_RAM_SIZE=123456
CONFIG_BLK_DEV_INITRD=y
CONFIG_CDROM_PKTCDVD=m
CONFIG_CDROM_PKTCDVD_BUFFERS=8
CONFIG_CDROM_PKTCDVD_WCACHE=y
CONFIG_CIPHER_TWOFISH=m
CONFIG_ATA_OVER_ETH=m
#
# ATA/ATAPI/MFM/RLL support
#
CONFIG_IDE=y
CONFIG_BLK_DEV_IDE=y
#
# Please see Documentation/ide.txt for help/info on IDE drives
#
# CONFIG_BLK_DEV_IDE_SATA is not set
CONFIG_BLK_DEV_IDEDISK=y
CONFIG_IDEDISK_MULTI_MODE=y
# CONFIG_BLK_DEV_IDECS is not set
CONFIG_BLK_DEV_IDECD=m
# CONFIG_BLK_DEV_IDETAPE is not set
CONFIG_BLK_DEV_IDEFLOPPY=m
CONFIG_BLK_DEV_IDESCSI=m
CONFIG_IDE_TASK_IOCTL=y
#
# IDE chipset support/bugfixes
#
CONFIG_IDE_GENERIC=y
CONFIG_BLK_DEV_IDEPCI=y
CONFIG_IDEPCI_SHARE_IRQ=y
CONFIG_BLK_DEV_OFFBOARD=y
CONFIG_BLK_DEV_GENERIC=y
# CONFIG_BLK_DEV_OPTI621 is not set
# CONFIG_BLK_DEV_SL82C105 is not set
CONFIG_BLK_DEV_IDEDMA_PCI=y
# CONFIG_BLK_DEV_IDEDMA_FORCED is not set
CONFIG_IDEDMA_PCI_AUTO=y
# CONFIG_IDEDMA_ONLYDISK is not set
CONFIG_BLK_DEV_AEC62XX=m
# CONFIG_BLK_DEV_ALI15X3 is not set
# CONFIG_BLK_DEV_AMD74XX is not set
CONFIG_BLK_DEV_CMD64X=y
# CONFIG_BLK_DEV_TRIFLEX is not set
# CONFIG_BLK_DEV_CY82C693 is not set
# CONFIG_BLK_DEV_CS5520 is not set
# CONFIG_BLK_DEV_CS5530 is not set
# CONFIG_BLK_DEV_HPT34X is not set
# CONFIG_BLK_DEV_HPT366 is not set
# CONFIG_BLK_DEV_SC1200 is not set
# CONFIG_BLK_DEV_PIIX is not set
# CONFIG_BLK_DEV_IT821X is not set
# CONFIG_BLK_DEV_NS87415 is not set
CONFIG_BLK_DEV_PDC202XX_OLD=m
CONFIG_PDC202XX_BURST=y
CONFIG_BLK_DEV_PDC202XX_NEW=m
# CONFIG_BLK_DEV_SVWKS is not set
# CONFIG_BLK_DEV_SIIMAGE is not set
# CONFIG_BLK_DEV_SLC90E66 is not set
# CONFIG_BLK_DEV_TRM290 is not set
CONFIG_BLK_DEV_VIA82CXXX=m
CONFIG_BLK_DEV_IDE_PMAC=y
CONFIG_BLK_DEV_IDE_PMAC_ATA100FIRST=y
CONFIG_BLK_DEV_IDEDMA_PMAC=y
# CONFIG_BLK_DEV_IDE_PMAC_BLINK is not set
# CONFIG_IDE_ARM is not set
CONFIG_BLK_DEV_IDEDMA=y
# CONFIG_IDEDMA_IVB is not set
CONFIG_IDEDMA_AUTO=y
# CONFIG_BLK_DEV_HD is not set
#
# SCSI device support
#
CONFIG_RAID_ATTRS=m
CONFIG_SCSI=m
# CONFIG_SCSI_PROC_FS is not set
#
# SCSI support type (disk, tape, CD-ROM)
#
CONFIG_BLK_DEV_SD=m
CONFIG_CHR_DEV_ST=m
CONFIG_CHR_DEV_OSST=m
CONFIG_BLK_DEV_SR=m
CONFIG_BLK_DEV_SR_VENDOR=y
CONFIG_CHR_DEV_SG=m
CONFIG_CHR_DEV_SCH=m
#
# Some SCSI devices (e.g. CD jukebox) support multiple LUNs
#
CONFIG_SCSI_MULTI_LUN=y
CONFIG_SCSI_CONSTANTS=y
CONFIG_SCSI_LOGGING=y
#
# SCSI Transport Attributes
#
CONFIG_SCSI_SPI_ATTRS=m
CONFIG_SCSI_FC_ATTRS=m
CONFIG_SCSI_ISCSI_ATTRS=m
CONFIG_SCSI_SAS_ATTRS=m
CONFIG_ISCSI_TARGET=m
#
# SCSI low-level drivers
#
CONFIG_ISCSI_TCP=m
# CONFIG_BLK_DEV_3W_XXXX_RAID is not set
# CONFIG_SCSI_3W_9XXX is not set
# CONFIG_SCSI_ACARD is not set
# CONFIG_SCSI_AACRAID is not set
CONFIG_SCSI_AIC7XXX=m
CONFIG_AIC7XXX_CMDS_PER_DEVICE=32
CONFIG_AIC7XXX_RESET_DELAY_MS=5000
# CONFIG_AIC7XXX_DEBUG_ENABLE is not set
CONFIG_AIC7XXX_DEBUG_MASK=0
CONFIG_AIC7XXX_REG_PRETTY_PRINT=y
# CONFIG_SCSI_AIC7XXX_OLD is not set
CONFIG_SCSI_AIC79XX=m
CONFIG_AIC79XX_CMDS_PER_DEVICE=32
CONFIG_AIC79XX_RESET_DELAY_MS=15000
# CONFIG_AIC79XX_ENABLE_RD_STRM is not set
# CONFIG_AIC79XX_DEBUG_ENABLE is not set
CONFIG_AIC79XX_DEBUG_MASK=0
CONFIG_AIC79XX_REG_PRETTY_PRINT=y
# CONFIG_SCSI_DPT_I2O is not set
# CONFIG_MEGARAID_NEWGEN is not set
# CONFIG_MEGARAID_LEGACY is not set
# CONFIG_MEGARAID_SAS is not set
# CONFIG_SCSI_SATA is not set
# CONFIG_SCSI_BUSLOGIC is not set
# CONFIG_SCSI_DMX3191D is not set
# CONFIG_SCSI_EATA is not set
# CONFIG_SCSI_FUTURE_DOMAIN is not set
# CONFIG_SCSI_GDTH is not set
# CONFIG_SCSI_IPS is not set
CONFIG_SCSI_INITIO=m
# CONFIG_SCSI_INIA100 is not set
CONFIG_SCSI_PPA=m
CONFIG_SCSI_IMM=m
# CONFIG_SCSI_IZIP_EPP16 is not set
# CONFIG_SCSI_IZIP_SLOW_CTR is not set
CONFIG_SCSI_SYM53C8XX_2=m
CONFIG_SCSI_SYM53C8XX_DMA_ADDRESSING_MODE=0
CONFIG_SCSI_SYM53C8XX_DEFAULT_TAGS=16
CONFIG_SCSI_SYM53C8XX_MAX_TAGS=64
# CONFIG_SCSI_SYM53C8XX_IOMAPPED is not set
CONFIG_SCSI_IPR=m
CONFIG_SCSI_IPR_TRACE=y
CONFIG_SCSI_IPR_DUMP=y
# CONFIG_SCSI_QLOGIC_FC is not set
# CONFIG_SCSI_QLOGIC_1280 is not set
CONFIG_SCSI_QLA_FC=m
# CONFIG_SCSI_QLA2XXX_EMBEDDED_FIRMWARE is not set
CONFIG_SCSI_QLA4XXX=m
CONFIG_SCSI_LPFC=m
# CONFIG_SCSI_DC395x is not set
# CONFIG_SCSI_DC390T is not set
# CONFIG_SCSI_NSP32 is not set
CONFIG_SCSI_DEBUG=m
CONFIG_SCSI_MESH=m
CONFIG_SCSI_MESH_SYNC_RATE=5
CONFIG_SCSI_MESH_RESET_DELAY_MS=4000
CONFIG_SCSI_MAC53C94=m
#
# PCMCIA SCSI adapter support
#
# CONFIG_PCMCIA_AHA152X is not set
# CONFIG_PCMCIA_FDOMAIN is not set
# CONFIG_PCMCIA_NINJA_SCSI is not set
# CONFIG_PCMCIA_QLOGIC is not set
# CONFIG_PCMCIA_SYM53C500 is not set
#
# Multi-device support (RAID and LVM)
#
CONFIG_MD=y
CONFIG_BLK_DEV_MD=y
CONFIG_MD_LINEAR=m
CONFIG_MD_RAID0=m
CONFIG_MD_RAID1=m
CONFIG_MD_RAID10=m
CONFIG_MD_RAID5=m
CONFIG_MD_RAID6=m
CONFIG_MD_MULTIPATH=m
CONFIG_MD_FAULTY=m
CONFIG_BLK_DEV_DM=m
CONFIG_DM_CRYPT=m
CONFIG_DM_SNAPSHOT=m
CONFIG_DM_MIRROR=m
CONFIG_DM_ZERO=m
CONFIG_DM_MULTIPATH=m
CONFIG_DM_MULTIPATH_EMC=m
CONFIG_DM_NL_EVT=y
#
# Fusion MPT device support
#
# CONFIG_FUSION is not set
# CONFIG_FUSION_SPI is not set
# CONFIG_FUSION_FC is not set
# CONFIG_FUSION_SAS is not set
#
# IEEE 1394 (FireWire) support
#
CONFIG_IEEE1394=m
#
# Subsystem Options
#
# CONFIG_IEEE1394_VERBOSEDEBUG is not set
# CONFIG_IEEE1394_OUI_DB is not set
CONFIG_IEEE1394_EXTRA_CONFIG_ROMS=y
CONFIG_IEEE1394_CONFIG_ROM_IP1394=y
CONFIG_IEEE1394_EXPORT_FULL_API=y
#
# Device Drivers
#
# CONFIG_IEEE1394_PCILYNX is not set
CONFIG_IEEE1394_OHCI1394=m
#
# Protocol Drivers
#
CONFIG_IEEE1394_VIDEO1394=m
CONFIG_IEEE1394_SBP2=m
# CONFIG_IEEE1394_SBP2_PHYS_DMA is not set
CONFIG_IEEE1394_ETH1394=m
CONFIG_IEEE1394_DV1394=m
CONFIG_IEEE1394_RAWIO=m
#
# I2O device support
#
# CONFIG_I2O is not set
#
# Macintosh device drivers
#
CONFIG_ADB=y
CONFIG_ADB_CUDA=y
CONFIG_ADB_PMU=y
CONFIG_PMAC_APM_EMU=y
CONFIG_PMAC_MEDIABAY=y
CONFIG_PMAC_BACKLIGHT=y
CONFIG_ADB_MACIO=y
CONFIG_INPUT_ADBHID=y
CONFIG_MAC_EMUMOUSEBTN=y
CONFIG_THERM_WINDTUNNEL=y
CONFIG_THERM_ADT746X=y
CONFIG_WINDFARM=y
# CONFIG_ANSLCD is not set
CONFIG_MACONLINUX=m
#
# Network device support
#
CONFIG_NETDEVICES=y
CONFIG_IFB=m
CONFIG_DUMMY=m
CONFIG_BONDING=m
CONFIG_EQUALIZER=m
CONFIG_TUN=m
#
# ARCnet devices
#
# CONFIG_ARCNET is not set
#
# PHY device support
#
CONFIG_PHYLIB=m
#
# MII PHY device drivers
#
CONFIG_MARVELL_PHY=m
CONFIG_DAVICOM_PHY=m
CONFIG_QSEMI_PHY=m
CONFIG_LXT_PHY=m
CONFIG_CICADA_PHY=m
#
# Ethernet (10 or 100Mbit)
#
CONFIG_NET_ETHERNET=y
CONFIG_MII=m
CONFIG_MACE=m
# CONFIG_MACE_AAUI_PORT is not set
CONFIG_BMAC=m
CONFIG_HAPPYMEAL=m
CONFIG_SUNGEM=m
CONFIG_CASSINI=m
CONFIG_NET_VENDOR_3COM=y
CONFIG_VORTEX=m
CONFIG_TYPHOON=m
#
# Tulip family network device support
#
CONFIG_NET_TULIP=y
CONFIG_DE2104X=m
CONFIG_TULIP=m
CONFIG_TULIP_MWI=y
CONFIG_TULIP_MMIO=y
CONFIG_TULIP_NAPI=y
# CONFIG_TULIP_NAPI_HW_MITIGATION is not set
CONFIG_DE4X5=m
CONFIG_WINBOND_840=m
CONFIG_DM9102=m
CONFIG_ULI526X=m
CONFIG_PCMCIA_XIRCOM=m
CONFIG_PCMCIA_XIRTULIP=m
# CONFIG_HP100 is not set
CONFIG_NET_PCI=y
CONFIG_PCNET32=m
# CONFIG_AMD8111_ETH is not set
CONFIG_ADAPTEC_STARFIRE=m
CONFIG_ADAPTEC_STARFIRE_NAPI=y
# CONFIG_B44 is not set
# CONFIG_FORCEDETH is not set
# CONFIG_DGRS is not set
# CONFIG_EEPRO100 is not set
CONFIG_E100=m
CONFIG_FEALNX=m
CONFIG_NATSEMI=m
CONFIG_NE2K_PCI=m
CONFIG_8139CP=m
CONFIG_8139TOO=m
# CONFIG_8139TOO_PIO is not set
# CONFIG_8139TOO_TUNE_TWISTER is not set
# CONFIG_8139TOO_8129 is not set
# CONFIG_8139_OLD_RX_RESET is not set
# CONFIG_SIS900 is not set
CONFIG_EPIC100=m
CONFIG_SUNDANCE=m
# CONFIG_SUNDANCE_MMIO is not set
CONFIG_TLAN=m
CONFIG_VIA_RHINE=m
# CONFIG_VIA_RHINE_MMIO is not set
# CONFIG_NET_POCKET is not set
#
# Ethernet (1000 Mbit)
#
CONFIG_ACENIC=m
CONFIG_ACENIC_OMIT_TIGON_I=y
# CONFIG_DL2K is not set
CONFIG_E1000=m
CONFIG_E1000_NAPI=y
# CONFIG_E1000_DISABLE_PACKET_SPLIT is not set
# CONFIG_NS83820 is not set
# CONFIG_HAMACHI is not set
# CONFIG_YELLOWFIN is not set
CONFIG_R8169=m
CONFIG_R8169_NAPI=y
CONFIG_R8169_VLAN=y
CONFIG_SIS190=m
# CONFIG_SKGE is not set
CONFIG_SKY2=m
# CONFIG_SK98LIN is not set
# CONFIG_VIA_VELOCITY is not set
CONFIG_TIGON3=m
# CONFIG_BNX2 is not set
# CONFIG_MV643XX_ETH is not set
CONFIG_MV643XX_ETH_0=y
CONFIG_MV643XX_ETH_1=y
CONFIG_MV643XX_ETH_2=y
#
# Ethernet (10000 Mbit)
#
CONFIG_CHELSIO_T1=m
CONFIG_IXGB=m
CONFIG_IXGB_NAPI=y
CONFIG_S2IO=m
CONFIG_S2IO_NAPI=y
#
# Token Ring devices
#
CONFIG_TR=y
CONFIG_IBMOL=m
CONFIG_IBMLS=m
# CONFIG_3C359 is not set
# CONFIG_TMS380TR is not set
#
# Wireless LAN (non-hamradio)
#
CONFIG_NET_RADIO=y
#
# Obsolete Wireless cards support (pre-802.11)
#
# CONFIG_STRIP is not set
CONFIG_PCMCIA_WAVELAN=m
CONFIG_PCMCIA_NETWAVE=m
#
# Wireless 802.11 Frequency Hopping cards support
#
CONFIG_PCMCIA_RAYCS=m
#
# Wireless 802.11b ISA/PCI cards support
#
CONFIG_IPW2100=m
CONFIG_IPW2100_MONITOR=y
# CONFIG_IPW2100_DEBUG is not set
CONFIG_IPW2200=m
# CONFIG_IPW2200_DEBUG is not set
CONFIG_AIRO=m
CONFIG_HERMES=m
CONFIG_APPLE_AIRPORT=m
CONFIG_PLX_HERMES=m
CONFIG_TMD_HERMES=m
CONFIG_NORTEL_HERMES=m
CONFIG_PCI_HERMES=m
CONFIG_ATMEL=m
CONFIG_PCI_ATMEL=m
#
# Wireless 802.11b Pcmcia/Cardbus cards support
#
CONFIG_PCMCIA_HERMES=m
CONFIG_PCMCIA_SPECTRUM=m
CONFIG_AIRO_CS=m
CONFIG_PCMCIA_ATMEL=m
CONFIG_PCMCIA_WL3501=m
#
# Prism GT/Duette 802.11(a/b/g) PCI/Cardbus support
#
CONFIG_PRISM54=m
CONFIG_HOSTAP=m
CONFIG_HOSTAP_FIRMWARE=y
CONFIG_HOSTAP_FIRMWARE_NVRAM=y
CONFIG_HOSTAP_PLX=m
CONFIG_HOSTAP_PCI=m
CONFIG_HOSTAP_CS=m
CONFIG_NET_WIRELESS=y
#
# PCMCIA network device support
#
CONFIG_NET_PCMCIA=y
CONFIG_PCMCIA_3C589=m
CONFIG_PCMCIA_3C574=m
CONFIG_PCMCIA_FMVJ18X=m
CONFIG_PCMCIA_PCNET=m
CONFIG_PCMCIA_NMCLAN=m
CONFIG_PCMCIA_SMC91C92=m
CONFIG_PCMCIA_XIRC2PS=m
CONFIG_PCMCIA_AXNET=m
CONFIG_PCMCIA_IBMTR=m
#
# Wan interfaces
#
# CONFIG_WAN is not set
# CONFIG_FDDI is not set
# CONFIG_HIPPI is not set
# CONFIG_PLIP is not set
CONFIG_PPP=m
CONFIG_PPP_MULTILINK=y
CONFIG_PPP_FILTER=y
CONFIG_PPP_ASYNC=m
CONFIG_PPP_SYNC_TTY=m
CONFIG_PPP_DEFLATE=m
CONFIG_PPP_BSDCOMP=m
CONFIG_PPP_MPPE=m
CONFIG_PPPOE=m
CONFIG_SLIP=m
CONFIG_SLIP_COMPRESSED=y
CONFIG_SLIP_SMART=y
CONFIG_SLIP_MODE_SLIP6=y
# CONFIG_NET_FC is not set
CONFIG_SHAPER=m
CONFIG_NETCONSOLE=m
CONFIG_NETPOLL=y
CONFIG_NETPOLL_RX=y
CONFIG_NETPOLL_TRAP=y
CONFIG_NET_POLL_CONTROLLER=y
#
# ISDN subsystem
#
# CONFIG_ISDN is not set
#
# Telephony Support
#
# CONFIG_PHONE is not set
#
# Input device support
#
CONFIG_INPUT=y
#
# Userland interfaces
#
CONFIG_INPUT_MOUSEDEV=y
# CONFIG_INPUT_MOUSEDEV_PSAUX is not set
CONFIG_INPUT_MOUSEDEV_SCREEN_X=1024
CONFIG_INPUT_MOUSEDEV_SCREEN_Y=768
CONFIG_INPUT_JOYDEV=m
CONFIG_INPUT_TSDEV=m
CONFIG_INPUT_TSDEV_SCREEN_X=240
CONFIG_INPUT_TSDEV_SCREEN_Y=320
CONFIG_INPUT_EVDEV=y
CONFIG_INPUT_EVBUG=m
#
# Input Device Drivers
#
CONFIG_INPUT_KEYBOARD=y
CONFIG_KEYBOARD_ATKBD=y
# CONFIG_KEYBOARD_SUNKBD is not set
# CONFIG_KEYBOARD_LKKBD is not set
# CONFIG_KEYBOARD_XTKBD is not set
# CONFIG_KEYBOARD_NEWTON is not set
CONFIG_INPUT_MOUSE=y
CONFIG_MOUSE_PS2=y
CONFIG_MOUSE_SERIAL=m
# CONFIG_MOUSE_VSXXXAA is not set
CONFIG_INPUT_JOYSTICK=y
# CONFIG_JOYSTICK_ANALOG is not set
# CONFIG_JOYSTICK_A3D is not set
# CONFIG_JOYSTICK_ADI is not set
# CONFIG_JOYSTICK_COBRA is not set
# CONFIG_JOYSTICK_GF2K is not set
# CONFIG_JOYSTICK_GRIP is not set
# CONFIG_JOYSTICK_GRIP_MP is not set
# CONFIG_JOYSTICK_GUILLEMOT is not set
# CONFIG_JOYSTICK_INTERACT is not set
# CONFIG_JOYSTICK_SIDEWINDER is not set
# CONFIG_JOYSTICK_TMDC is not set
CONFIG_JOYSTICK_IFORCE=m
CONFIG_JOYSTICK_IFORCE_USB=y
# CONFIG_JOYSTICK_IFORCE_232 is not set
# CONFIG_JOYSTICK_WARRIOR is not set
# CONFIG_JOYSTICK_MAGELLAN is not set
# CONFIG_JOYSTICK_SPACEORB is not set
# CONFIG_JOYSTICK_SPACEBALL is not set
# CONFIG_JOYSTICK_STINGER is not set
# CONFIG_JOYSTICK_TWIDJOY is not set
# CONFIG_JOYSTICK_DB9 is not set
# CONFIG_JOYSTICK_GAMECON is not set
# CONFIG_JOYSTICK_TURBOGRAFX is not set
# CONFIG_JOYSTICK_JOYDUMP is not set
CONFIG_INPUT_TOUCHSCREEN=y
CONFIG_TOUCHSCREEN_ADS7846=m
CONFIG_TOUCHSCREEN_GUNZE=m
CONFIG_TOUCHSCREEN_ELO=m
CONFIG_TOUCHSCREEN_MTOUCH=m
CONFIG_TOUCHSCREEN_MK712=m
CONFIG_INPUT_MISC=y
CONFIG_INPUT_PCSPKR=m
CONFIG_INPUT_UINPUT=m
#
# Hardware I/O ports
#
CONFIG_SERIO=y
CONFIG_SERIO_I8042=y
CONFIG_SERIO_SERPORT=m
# CONFIG_SERIO_PARKBD is not set
CONFIG_SERIO_PCIPS2=m
CONFIG_SERIO_LIBPS2=y
CONFIG_SERIO_RAW=m
# CONFIG_GAMEPORT is not set
#
# Character devices
#
CONFIG_VT=y
CONFIG_VT_CONSOLE=y
CONFIG_HW_CONSOLE=y
# CONFIG_SERIAL_NONSTANDARD is not set
#
# Serial drivers
#
CONFIG_SERIAL_8250=y
CONFIG_SERIAL_8250_CONSOLE=y
CONFIG_SERIAL_8250_CS=m
CONFIG_SERIAL_8250_NR_UARTS=4
CONFIG_SERIAL_8250_RUNTIME_UARTS=4
# CONFIG_SERIAL_8250_EXTENDED is not set
#
# Non-8250 serial port support
#
CONFIG_SERIAL_CORE=y
CONFIG_SERIAL_CORE_CONSOLE=y
CONFIG_SERIAL_PMACZILOG=y
CONFIG_SERIAL_PMACZILOG_CONSOLE=y
CONFIG_SERIAL_JSM=m
CONFIG_UNIX98_PTYS=y
CONFIG_LEGACY_PTYS=y
CONFIG_LEGACY_PTY_COUNT=64
CONFIG_PRINTER=m
# CONFIG_LP_CONSOLE is not set
CONFIG_PPDEV=m
# CONFIG_TIPAR is not set
#
# IPMI
#
# CONFIG_IPMI_HANDLER is not set
#
# Watchdog Cards
#
CONFIG_WATCHDOG=y
# CONFIG_WATCHDOG_NOWAYOUT is not set
#
# Watchdog Device Drivers
#
CONFIG_SOFT_WATCHDOG=m
CONFIG_WATCHDOG_RTAS=m
#
# PCI-based Watchdog Cards
#
# CONFIG_PCIPCWATCHDOG is not set
# CONFIG_WDTPCI is not set
#
# USB-based Watchdog Cards
#
CONFIG_USBPCWATCHDOG=m
CONFIG_NVRAM=y
CONFIG_GEN_RTC=y
# CONFIG_GEN_RTC_X is not set
# CONFIG_DTLK is not set
# CONFIG_R3964 is not set
# CONFIG_APPLICOM is not set
#
# Ftape, the floppy tape device driver
#
CONFIG_AGP=m
CONFIG_AGP_UNINORTH=m
CONFIG_DRM=m
# CONFIG_DRM_TDFX is not set
CONFIG_DRM_R128=m
CONFIG_DRM_RADEON=m
# CONFIG_DRM_MGA is not set
# CONFIG_DRM_SIS is not set
# CONFIG_DRM_VIA is not set
# CONFIG_DRM_SAVAGE is not set
#
# PCMCIA character devices
#
CONFIG_SYNCLINK_CS=m
CONFIG_CARDMAN_4000=m
CONFIG_CARDMAN_4040=m
CONFIG_RAW_DRIVER=m
CONFIG_MAX_RAW_DEVS=4096
#
# TPM devices
#
# CONFIG_TCG_TPM is not set
# CONFIG_TELCLOCK is not set
CONFIG_CRASHER=m
#
# I2C support
#
CONFIG_I2C=y
CONFIG_I2C_CHARDEV=m
#
# I2C Algorithms
#
CONFIG_I2C_ALGOBIT=y
# CONFIG_I2C_ALGOPCF is not set
# CONFIG_I2C_ALGOPCA is not set
#
# I2C Hardware Bus support
#
# CONFIG_I2C_ALI1535 is not set
# CONFIG_I2C_ALI1563 is not set
# CONFIG_I2C_ALI15X3 is not set
# CONFIG_I2C_AMD756 is not set
# CONFIG_I2C_AMD8111 is not set
CONFIG_I2C_HYDRA=m
# CONFIG_I2C_I801 is not set
# CONFIG_I2C_I810 is not set
# CONFIG_I2C_PIIX4 is not set
CONFIG_I2C_POWERMAC=y
# CONFIG_I2C_MPC is not set
# CONFIG_I2C_NFORCE2 is not set
# CONFIG_I2C_PARPORT is not set
# CONFIG_I2C_PARPORT_LIGHT is not set
# CONFIG_I2C_PROSAVAGE is not set
# CONFIG_I2C_SAVAGE4 is not set
# CONFIG_SCx200_ACB is not set
# CONFIG_I2C_SIS5595 is not set
# CONFIG_I2C_SIS630 is not set
# CONFIG_I2C_SIS96X is not set
# CONFIG_I2C_STUB is not set
# CONFIG_I2C_VIA is not set
# CONFIG_I2C_VIAPRO is not set
# CONFIG_I2C_VOODOO3 is not set
# CONFIG_I2C_PCA_ISA is not set
#
# Miscellaneous I2C Chip support
#
# CONFIG_SENSORS_DS1337 is not set
# CONFIG_SENSORS_DS1374 is not set
# CONFIG_SENSORS_EEPROM is not set
# CONFIG_SENSORS_PCF8574 is not set
# CONFIG_SENSORS_PCA9539 is not set
# CONFIG_SENSORS_PCF8591 is not set
# CONFIG_SENSORS_RTC8564 is not set
# CONFIG_SENSORS_M41T00 is not set
# CONFIG_SENSORS_MAX6875 is not set
# CONFIG_RTC_X1205_I2C is not set
# CONFIG_I2C_DEBUG_CORE is not set
# CONFIG_I2C_DEBUG_ALGO is not set
# CONFIG_I2C_DEBUG_BUS is not set
# CONFIG_I2C_DEBUG_CHIP is not set
#
# SPI support
#
CONFIG_SPI=y
CONFIG_SPI_DEBUG=y
CONFIG_SPI_MASTER=y
#
# SPI Master Controller Drivers
#
CONFIG_SPI_BITBANG=m
CONFIG_SPI_BUTTERFLY=m
#
# SPI Protocol Masters
#
#
# Dallas's 1-wire bus
#
CONFIG_W1=m
CONFIG_W1_MATROX=m
CONFIG_W1_DS9490=m
CONFIG_W1_DS9490_BRIDGE=m
CONFIG_W1_THERM=m
CONFIG_W1_SMEM=m
CONFIG_W1_DS2433=m
CONFIG_W1_DS2433_CRC=y
#
# Hardware Monitoring support
#
# CONFIG_HWMON is not set
# CONFIG_HWMON_VID is not set
#
# Misc devices
#
#
# Multimedia Capabilities Port drivers
#
#
# Multimedia devices
#
CONFIG_VIDEO_DEV=m
#
# Video For Linux
#
#
# Video Adapters
#
# CONFIG_VIDEO_ADV_DEBUG is not set
CONFIG_VIDEO_BT848=m
CONFIG_VIDEO_SAA6588=m
# CONFIG_VIDEO_BWQCAM is not set
# CONFIG_VIDEO_CQCAM is not set
# CONFIG_VIDEO_W9966 is not set
# CONFIG_VIDEO_CPIA is not set
# CONFIG_VIDEO_SAA5246A is not set
# CONFIG_VIDEO_SAA5249 is not set
# CONFIG_TUNER_3036 is not set
# CONFIG_VIDEO_STRADIS is not set
# CONFIG_VIDEO_ZORAN is not set
# CONFIG_VIDEO_SAA7134 is not set
# CONFIG_VIDEO_MXB is not set
# CONFIG_VIDEO_DPC is not set
# CONFIG_VIDEO_HEXIUM_ORION is not set
# CONFIG_VIDEO_HEXIUM_GEMINI is not set
# CONFIG_VIDEO_CX88 is not set
# CONFIG_VIDEO_EM28XX is not set
# CONFIG_VIDEO_OVCAMCHIP is not set
# CONFIG_VIDEO_AUDIO_DECODER is not set
# CONFIG_VIDEO_DECODER is not set
#
# Radio Adapters
#
# CONFIG_RADIO_GEMTEK_PCI is not set
# CONFIG_RADIO_MAXIRADIO is not set
# CONFIG_RADIO_MAESTRO is not set
#
# Digital Video Broadcasting Devices
#
# CONFIG_DVB is not set
CONFIG_VIDEO_TUNER=m
CONFIG_VIDEO_BUF=m
CONFIG_VIDEO_BTCX=m
CONFIG_VIDEO_IR=m
CONFIG_VIDEO_TVEEPROM=m
#
# Graphics support
#
CONFIG_FB=y
CONFIG_FB_CFB_FILLRECT=y
CONFIG_FB_CFB_COPYAREA=y
CONFIG_FB_CFB_IMAGEBLIT=y
CONFIG_FB_MACMODES=y
CONFIG_FB_MODE_HELPERS=y
CONFIG_FB_TILEBLITTING=y
CONFIG_FB_CIRRUS=m
# CONFIG_FB_PM2 is not set
# CONFIG_FB_CYBER2000 is not set
CONFIG_FB_OF=y
CONFIG_FB_CONTROL=y
CONFIG_FB_PLATINUM=y
CONFIG_FB_VALKYRIE=y
CONFIG_FB_CT65550=y
# CONFIG_FB_ASILIANT is not set
CONFIG_FB_IMSTT=y
# CONFIG_FB_VGA16 is not set
# CONFIG_FB_S1D13XXX is not set
CONFIG_FB_NVIDIA=y
CONFIG_FB_NVIDIA_I2C=y
CONFIG_FB_RIVA=y
CONFIG_FB_RIVA_I2C=y
# CONFIG_FB_RIVA_DEBUG is not set
CONFIG_FB_MATROX=y
CONFIG_FB_MATROX_MILLENIUM=y
CONFIG_FB_MATROX_MYSTIQUE=y
CONFIG_FB_MATROX_G=y
CONFIG_FB_MATROX_I2C=m
CONFIG_FB_MATROX_MAVEN=m
CONFIG_FB_MATROX_MULTIHEAD=y
# CONFIG_FB_RADEON_OLD is not set
CONFIG_FB_RADEON=y
CONFIG_FB_RADEON_I2C=y
# CONFIG_FB_RADEON_DEBUG is not set
CONFIG_FB_ATY128=y
CONFIG_FB_ATY=y
CONFIG_FB_ATY_CT=y
CONFIG_FB_ATY_GENERIC_LCD=y
CONFIG_FB_ATY_GX=y
CONFIG_FB_SAVAGE=m
CONFIG_FB_SAVAGE_I2C=y
CONFIG_FB_SAVAGE_ACCEL=y
# CONFIG_FB_SIS is not set
# CONFIG_FB_NEOMAGIC is not set
# CONFIG_FB_KYRO is not set
# CONFIG_FB_3DFX is not set
# CONFIG_FB_VOODOO1 is not set
# CONFIG_FB_TRIDENT is not set
# CONFIG_FB_VIRTUAL is not set
#
# Console display driver support
#
CONFIG_VGA_CONSOLE=y
CONFIG_DUMMY_CONSOLE=y
CONFIG_FRAMEBUFFER_CONSOLE=y
CONFIG_FRAMEBUFFER_CONSOLE_ROTATION=y
# CONFIG_FONTS is not set
CONFIG_FONT_8x8=y
CONFIG_FONT_8x16=y
#
# Logo configuration
#
CONFIG_LOGO=y
# CONFIG_LOGO_LINUX_MONO is not set
# CONFIG_LOGO_LINUX_VGA16 is not set
CONFIG_LOGO_LINUX_CLUT224=y
CONFIG_BACKLIGHT_LCD_SUPPORT=y
CONFIG_BACKLIGHT_CLASS_DEVICE=m
CONFIG_BACKLIGHT_DEVICE=y
CONFIG_LCD_CLASS_DEVICE=m
CONFIG_LCD_DEVICE=y
#
# Bootsplash configuration
#
#
# Sound
#
CONFIG_SOUND=m
CONFIG_DMASOUND_PMAC=m
CONFIG_DMASOUND=m
#
# Advanced Linux Sound Architecture
#
CONFIG_SND=m
CONFIG_SND_TIMER=m
CONFIG_SND_PCM=m
CONFIG_SND_HWDEP=m
CONFIG_SND_RAWMIDI=m
CONFIG_SND_SEQUENCER=m
CONFIG_SND_SEQ_DUMMY=m
CONFIG_SND_OSSEMUL=y
CONFIG_SND_MIXER_OSS=m
CONFIG_SND_PCM_OSS=m
CONFIG_SND_PCM_OSS_PLUGINS=y
CONFIG_SND_SEQUENCER_OSS=y
CONFIG_SND_DYNAMIC_MINORS=y
CONFIG_SND_SUPPORT_OLD_API=y
CONFIG_SND_VERBOSE_PROCFS=y
CONFIG_SND_VERBOSE_PRINTK=y
CONFIG_SND_DEBUG=y
# CONFIG_SND_DEBUG_DETECT is not set
#
# Generic devices
#
CONFIG_SND_MPU401_UART=m
CONFIG_SND_AC97_CODEC=m
CONFIG_SND_AC97_BUS=m
CONFIG_SND_DUMMY=m
CONFIG_SND_VIRMIDI=m
CONFIG_SND_MTPAV=m
CONFIG_SND_SERIAL_U16550=m
CONFIG_SND_MPU401=m
#
# PCI devices
#
CONFIG_SND_AD1889=m
# CONFIG_SND_ALS4000 is not set
# CONFIG_SND_ALI5451 is not set
# CONFIG_SND_ATIIXP is not set
# CONFIG_SND_ATIIXP_MODEM is not set
# CONFIG_SND_AU8810 is not set
# CONFIG_SND_AU8820 is not set
# CONFIG_SND_AU8830 is not set
# CONFIG_SND_AZT3328 is not set
# CONFIG_SND_BT87X is not set
# CONFIG_SND_CA0106 is not set
# CONFIG_SND_CMIPCI is not set
# CONFIG_SND_CS4281 is not set
CONFIG_SND_CS46XX=m
CONFIG_SND_CS46XX_NEW_DSP=y
CONFIG_SND_EMU10K1=m
# CONFIG_SND_EMU10K1X is not set
# CONFIG_SND_ENS1370 is not set
# CONFIG_SND_ENS1371 is not set
# CONFIG_SND_ES1938 is not set
# CONFIG_SND_ES1968 is not set
# CONFIG_SND_FM801 is not set
# CONFIG_SND_HDA_INTEL is not set
# CONFIG_SND_HDSP is not set
# CONFIG_SND_HDSPM is not set
# CONFIG_SND_ICE1712 is not set
# CONFIG_SND_ICE1724 is not set
# CONFIG_SND_INTEL8X0 is not set
# CONFIG_SND_INTEL8X0M is not set
# CONFIG_SND_KORG1212 is not set
# CONFIG_SND_MAESTRO3 is not set
# CONFIG_SND_MIXART is not set
# CONFIG_SND_NM256 is not set
# CONFIG_SND_PCXHR is not set
# CONFIG_SND_RME32 is not set
# CONFIG_SND_RME96 is not set
# CONFIG_SND_RME9652 is not set
# CONFIG_SND_SONICVIBES is not set
# CONFIG_SND_TRIDENT is not set
CONFIG_SND_VIA82XX=m
CONFIG_SND_VIA82XX_MODEM=m
# CONFIG_SND_VX222 is not set
# CONFIG_SND_YMFPCI is not set
#
# ALSA PowerMac devices
#
CONFIG_SND_POWERMAC=m
# CONFIG_SND_POWERMAC_AUTO_DRC is not set
#
# USB devices
#
CONFIG_SND_USB_AUDIO=m
CONFIG_SND_USB_USX2Y=m
#
# PCMCIA devices
#
#
# Open Sound System
#
# CONFIG_SOUND_PRIME is not set
#
# USB support
#
CONFIG_USB_ARCH_HAS_HCD=y
CONFIG_USB_ARCH_HAS_OHCI=y
CONFIG_USB=y
# CONFIG_USB_DEBUG is not set
#
# Miscellaneous USB options
#
CONFIG_USB_DEVICEFS=y
# CONFIG_USB_BANDWIDTH is not set
# CONFIG_USB_DYNAMIC_MINORS is not set
CONFIG_USB_SUSPEND=y
# CONFIG_USB_OTG is not set
#
# USB Host Controller Drivers
#
CONFIG_USB_EHCI_HCD=m
CONFIG_USB_EHCI_SPLIT_ISO=y
CONFIG_USB_EHCI_ROOT_HUB_TT=y
# CONFIG_USB_ISP116X_HCD is not set
CONFIG_USB_OHCI_HCD=y
# CONFIG_USB_OHCI_BIG_ENDIAN is not set
CONFIG_USB_OHCI_LITTLE_ENDIAN=y
CONFIG_USB_UHCI_HCD=m
# CONFIG_USB_SL811_HCD is not set
#
# USB Device Class drivers
#
# CONFIG_OBSOLETE_OSS_USB_DRIVER is not set
CONFIG_USB_ACM=m
CONFIG_USB_PRINTER=m
#
# NOTE: USB_STORAGE enables SCSI, and 'SCSI disk support'
#
#
# may also be needed; see USB_STORAGE Help for more information
#
CONFIG_USB_STORAGE=m
# CONFIG_USB_STORAGE_DEBUG is not set
CONFIG_USB_STORAGE_DATAFAB=y
CONFIG_USB_STORAGE_FREECOM=y
CONFIG_USB_STORAGE_ISD200=y
CONFIG_USB_STORAGE_DPCM=y
CONFIG_USB_STORAGE_USBAT=y
CONFIG_USB_STORAGE_SDDR09=y
CONFIG_USB_STORAGE_SDDR55=y
CONFIG_USB_STORAGE_JUMPSHOT=y
CONFIG_USB_STORAGE_ALAUDA=y
# CONFIG_USB_LIBUSUAL is not set
#
# USB Input Devices
#
CONFIG_USB_HID=y
CONFIG_USB_HIDINPUT=y
CONFIG_USB_HIDINPUT_POWERBOOK=y
CONFIG_HID_FF=y
CONFIG_HID_PID=y
CONFIG_LOGITECH_FF=y
CONFIG_THRUSTMASTER_FF=y
CONFIG_USB_HIDDEV=y
CONFIG_USB_AIPTEK=m
# CONFIG_USB_WACOM is not set
CONFIG_USB_ACECAD=m
CONFIG_USB_KBTAB=m
CONFIG_USB_POWERMATE=m
CONFIG_USB_MTOUCH=m
CONFIG_USB_ITMTOUCH=m
CONFIG_USB_EGALAX=m
CONFIG_USB_YEALINK=m
CONFIG_USB_XPAD=m
CONFIG_USB_ATI_REMOTE=m
CONFIG_USB_ATI_REMOTE2=m
CONFIG_USB_KEYSPAN_REMOTE=m
CONFIG_USB_APPLETOUCH=m
#
# USB Imaging devices
#
CONFIG_USB_MDC800=m
CONFIG_USB_MICROTEK=m
#
# USB Multimedia devices
#
CONFIG_USB_DABUSB=m
CONFIG_USB_VICAM=m
CONFIG_USB_DSBR=m
CONFIG_USB_ET61X251=m
CONFIG_USB_IBMCAM=m
CONFIG_USB_KONICAWC=m
CONFIG_USB_OV511=m
CONFIG_USB_SE401=m
CONFIG_USB_SN9C102=m
CONFIG_USB_STV680=m
CONFIG_USB_PWC=m
#
# USB Network Adapters
#
CONFIG_USB_CATC=m
CONFIG_USB_KAWETH=m
CONFIG_USB_PEGASUS=m
CONFIG_USB_RTL8150=m
CONFIG_USB_USBNET=m
CONFIG_USB_NET_AX8817X=m
CONFIG_USB_NET_CDCETHER=m
CONFIG_USB_NET_GL620A=m
CONFIG_USB_NET_NET1080=m
CONFIG_USB_NET_PLUSB=m
CONFIG_USB_NET_RNDIS_HOST=m
CONFIG_USB_NET_CDC_SUBSET=m
CONFIG_USB_ALI_M5632=y
CONFIG_USB_AN2720=y
CONFIG_USB_BELKIN=y
CONFIG_USB_ARMLINUX=y
CONFIG_USB_EPSON2888=y
CONFIG_USB_NET_ZAURUS=m
CONFIG_USB_ZD1201=m
# CONFIG_USB_MON is not set
#
# USB port drivers
#
CONFIG_USB_USS720=m
#
# USB Serial Converter support
#
CONFIG_USB_SERIAL=m
CONFIG_USB_SERIAL_GENERIC=y
CONFIG_USB_SERIAL_AIRPRIME=m
CONFIG_USB_SERIAL_ANYDATA=m
CONFIG_USB_SERIAL_BELKIN=m
CONFIG_USB_SERIAL_WHITEHEAT=m
CONFIG_USB_SERIAL_DIGI_ACCELEPORT=m
CONFIG_USB_SERIAL_CP2101=m
CONFIG_USB_SERIAL_CYPRESS_M8=m
CONFIG_USB_SERIAL_EMPEG=m
CONFIG_USB_SERIAL_FTDI_SIO=m
CONFIG_USB_SERIAL_VISOR=m
CONFIG_USB_SERIAL_IPAQ=m
CONFIG_USB_SERIAL_IR=m
CONFIG_USB_SERIAL_EDGEPORT=m
CONFIG_USB_SERIAL_EDGEPORT_TI=m
CONFIG_USB_SERIAL_GARMIN=m
CONFIG_USB_SERIAL_IPW=m
CONFIG_USB_SERIAL_KEYSPAN_PDA=m
CONFIG_USB_SERIAL_KEYSPAN=m
CONFIG_USB_SERIAL_KEYSPAN_MPR=y
CONFIG_USB_SERIAL_KEYSPAN_USA28=y
CONFIG_USB_SERIAL_KEYSPAN_USA28X=y
CONFIG_USB_SERIAL_KEYSPAN_USA28XA=y
CONFIG_USB_SERIAL_KEYSPAN_USA28XB=y
CONFIG_USB_SERIAL_KEYSPAN_USA19=y
CONFIG_USB_SERIAL_KEYSPAN_USA18X=y
CONFIG_USB_SERIAL_KEYSPAN_USA19W=y
CONFIG_USB_SERIAL_KEYSPAN_USA19QW=y
CONFIG_USB_SERIAL_KEYSPAN_USA19QI=y
CONFIG_USB_SERIAL_KEYSPAN_USA49W=y
CONFIG_USB_SERIAL_KEYSPAN_USA49WLC=y
CONFIG_USB_SERIAL_KLSI=m
CONFIG_USB_SERIAL_KOBIL_SCT=m
CONFIG_USB_SERIAL_MCT_U232=m
CONFIG_USB_SERIAL_PL2303=m
CONFIG_USB_SERIAL_HP4X=m
CONFIG_USB_SERIAL_SAFE=m
CONFIG_USB_SERIAL_SAFE_PADDED=y
CONFIG_USB_SERIAL_TI=m
CONFIG_USB_SERIAL_CYBERJACK=m
CONFIG_USB_SERIAL_XIRCOM=m
CONFIG_USB_SERIAL_OPTION=m
CONFIG_USB_SERIAL_OMNINET=m
CONFIG_USB_EZUSB=y
#
# USB Miscellaneous drivers
#
CONFIG_USB_EMI62=m
CONFIG_USB_EMI26=m
CONFIG_USB_AUERSWALD=m
CONFIG_USB_RIO500=m
CONFIG_USB_LEGOTOWER=m
CONFIG_USB_LCD=m
CONFIG_USB_LED=m
CONFIG_USB_CYTHERM=m
CONFIG_USB_PHIDGETKIT=m
CONFIG_USB_PHIDGETSERVO=m
CONFIG_USB_IDMOUSE=m
CONFIG_USB_SISUSBVGA=m
CONFIG_USB_SISUSBVGA_CON=y
CONFIG_USB_LD=m
# CONFIG_USB_TEST is not set
#
# USB DSL modem support
#
#
# USB Gadget Support
#
# CONFIG_USB_GADGET is not set
#
# MMC/SD Card support
#
# CONFIG_MMC is not set
#
# InfiniBand support
#
CONFIG_INFINIBAND=m
CONFIG_INFINIBAND_USER_MAD=m
CONFIG_INFINIBAND_USER_ACCESS=m
CONFIG_INFINIBAND_MTHCA=m
# CONFIG_INFINIBAND_MTHCA_DEBUG is not set
CONFIG_INFINIBAND_IPOIB=m
# CONFIG_INFINIBAND_IPOIB_DEBUG is not set
CONFIG_INFINIBAND_SRP=m
#
# EDAC - error detection and reporting (RAS)
#
#
# DMA Engine support
#
# CONFIG_DMA_ENGINE is not set
#
# DMA Clients
#
#
# DMA Devices
#
#
# File systems
#
CONFIG_EXT2_FS=y
CONFIG_EXT2_FS_XATTR=y
CONFIG_EXT2_FS_POSIX_ACL=y
CONFIG_EXT2_FS_SECURITY=y
# CONFIG_EXT2_FS_XIP is not set
CONFIG_EXT3_FS=y
CONFIG_EXT3_FS_XATTR=y
CONFIG_EXT3_FS_POSIX_ACL=y
CONFIG_EXT3_FS_SECURITY=y
CONFIG_JBD=y
CONFIG_JBD_DEBUG=y
CONFIG_FS_MBCACHE=y
CONFIG_REISERFS_FS=y
# CONFIG_REISERFS_CC_REDUCE_OPTIMZE is not set
# CONFIG_REISERFS_CHECK is not set
CONFIG_REISERFS_PROC_INFO=y
CONFIG_REISERFS_FS_XATTR=y
CONFIG_REISERFS_FS_POSIX_ACL=y
CONFIG_REISERFS_FS_SECURITY=y
CONFIG_JFS_FS=m
CONFIG_JFS_POSIX_ACL=y
CONFIG_JFS_SECURITY=y
# CONFIG_JFS_DEBUG is not set
CONFIG_JFS_STATISTICS=y
CONFIG_FS_POSIX_ACL=y
CONFIG_XFS_FS=m
CONFIG_XFS_EXPORT=y
CONFIG_XFS_QUOTA=m
CONFIG_XFS_DMAPI=m
CONFIG_XFS_SECURITY=y
CONFIG_XFS_POSIX_ACL=y
CONFIG_XFS_RT=y
# CONFIG_XFS_DEBUG is not set
# CONFIG_XFS_TRACE is not set
CONFIG_OCFS2_FS=m
CONFIG_OCFS2_FS_USERSPACE_CLUSTER=m
CONFIG_MINIX_FS=m
CONFIG_ROMFS_FS=m
CONFIG_INOTIFY=y
CONFIG_DMAPI=m
# CONFIG_DMAPI_DEBUG is not set
CONFIG_QUOTA=y
CONFIG_QFMT_V1=m
CONFIG_QFMT_V2=m
CONFIG_QUOTACTL=y
CONFIG_DNOTIFY=y
CONFIG_AUTOFS_FS=m
CONFIG_AUTOFS4_FS=m
CONFIG_FUSE_FS=m
#
# CD-ROM/DVD Filesystems
#
CONFIG_ISO9660_FS=y
CONFIG_JOLIET=y
CONFIG_ZISOFS=y
CONFIG_ZISOFS_FS=y
CONFIG_UDF_FS=m
CONFIG_UDF_NLS=y
#
# DOS/FAT/NT Filesystems
#
CONFIG_FAT_FS=y
CONFIG_MSDOS_FS=m
CONFIG_VFAT_FS=y
CONFIG_FAT_DEFAULT_CODEPAGE=437
CONFIG_FAT_DEFAULT_IOCHARSET="iso8859-1"
CONFIG_NTFS_FS=m
# CONFIG_NTFS_DEBUG is not set
# CONFIG_NTFS_RW is not set
#
# Pseudo filesystems
#
CONFIG_PROC_FS=y
CONFIG_PROC_KCORE=y
CONFIG_SYSFS=y
CONFIG_TMPFS=y
CONFIG_TMPFS_POSIX_ACL=y
# CONFIG_HUGETLB_PAGE is not set
CONFIG_RAMFS=y
CONFIG_RELAYFS_FS=m
CONFIG_CONFIGFS_FS=m
#
# Miscellaneous filesystems
#
# CONFIG_ADFS_FS is not set
CONFIG_AFFS_FS=m
CONFIG_HFS_FS=m
CONFIG_HFSPLUS_FS=m
# CONFIG_BEFS_FS is not set
# CONFIG_BFS_FS is not set
CONFIG_EFS_FS=m
CONFIG_CRAMFS=y
# CONFIG_VXFS_FS is not set
# CONFIG_HPFS_FS is not set
CONFIG_QNX4FS_FS=m
# CONFIG_SYSV_FS is not set
CONFIG_UFS_FS=m
#
# Network File Systems
#
CONFIG_NFS_FS=m
CONFIG_NFS_V3=y
CONFIG_NFS_V3_ACL=y
CONFIG_NFS_V4=y
CONFIG_NFS_DIRECTIO=y
CONFIG_NFSD=m
CONFIG_NFSD_V2_ACL=y
CONFIG_NFSD_V3=y
CONFIG_NFSD_V3_ACL=y
CONFIG_NFSD_V4=y
CONFIG_NFSD_TCP=y
CONFIG_LOCKD=m
CONFIG_LOCKD_V4=y
CONFIG_EXPORTFS=m
CONFIG_NFS_ACL_SUPPORT=m
CONFIG_NFS_COMMON=y
CONFIG_SUNRPC=m
CONFIG_SUNRPC_GSS=m
CONFIG_RPCSEC_GSS_KRB5=m
CONFIG_RPCSEC_GSS_SPKM3=m
CONFIG_SMB_FS=m
CONFIG_SMB_NLS_DEFAULT=y
CONFIG_SMB_NLS_REMOTE="cp850"
CONFIG_CIFS=m
CONFIG_CIFS_STATS=y
# CONFIG_CIFS_STATS2 is not set
CONFIG_CIFS_XATTR=y
CONFIG_CIFS_POSIX=y
# CONFIG_CIFS_EXPERIMENTAL is not set
CONFIG_NCP_FS=m
CONFIG_NCPFS_PACKET_SIGNING=y
CONFIG_NCPFS_IOCTL_LOCKING=y
CONFIG_NCPFS_STRONG=y
CONFIG_NCPFS_NFS_NS=y
CONFIG_NCPFS_OS2_NS=y
CONFIG_NCPFS_SMALLDOS=y
CONFIG_NCPFS_NLS=y
CONFIG_NCPFS_EXTRAS=y
# CONFIG_CODA_FS is not set
CONFIG_AFS_FS=m
CONFIG_RXRPC=m
CONFIG_9P_FS=m
CONFIG_GENERIC_ACL=y
#
# Partition Types
#
CONFIG_PARTITION_ADVANCED=y
# CONFIG_ACORN_PARTITION is not set
CONFIG_OSF_PARTITION=y
CONFIG_AMIGA_PARTITION=y
CONFIG_ATARI_PARTITION=y
CONFIG_MAC_PARTITION=y
CONFIG_MSDOS_PARTITION=y
CONFIG_BSD_DISKLABEL=y
CONFIG_MINIX_SUBPARTITION=y
CONFIG_SOLARIS_X86_PARTITION=y
CONFIG_UNIXWARE_DISKLABEL=y
CONFIG_LDM_PARTITION=y
# CONFIG_LDM_DEBUG is not set
CONFIG_SGI_PARTITION=y
CONFIG_ULTRIX_PARTITION=y
CONFIG_SUN_PARTITION=y
CONFIG_KARMA_PARTITION=y
CONFIG_EFI_PARTITION=y
#
# Native Language Support
#
CONFIG_NLS=y
CONFIG_NLS_DEFAULT="utf8"
CONFIG_NLS_CODEPAGE_437=y
CONFIG_NLS_CODEPAGE_737=m
CONFIG_NLS_CODEPAGE_775=m
CONFIG_NLS_CODEPAGE_850=m
CONFIG_NLS_CODEPAGE_852=m
CONFIG_NLS_CODEPAGE_855=m
CONFIG_NLS_CODEPAGE_857=m
CONFIG_NLS_CODEPAGE_860=m
CONFIG_NLS_CODEPAGE_861=m
CONFIG_NLS_CODEPAGE_862=m
CONFIG_NLS_CODEPAGE_863=m
CONFIG_NLS_CODEPAGE_864=m
CONFIG_NLS_CODEPAGE_865=m
CONFIG_NLS_CODEPAGE_866=m
CONFIG_NLS_CODEPAGE_869=m
CONFIG_NLS_CODEPAGE_936=m
CONFIG_NLS_CODEPAGE_950=m
CONFIG_NLS_CODEPAGE_932=m
CONFIG_NLS_CODEPAGE_949=m
CONFIG_NLS_CODEPAGE_874=m
CONFIG_NLS_ISO8859_8=m
CONFIG_NLS_CODEPAGE_1250=m
CONFIG_NLS_CODEPAGE_1251=m
CONFIG_NLS_ASCII=m
CONFIG_NLS_ISO8859_1=y
CONFIG_NLS_ISO8859_2=m
CONFIG_NLS_ISO8859_3=m
CONFIG_NLS_ISO8859_4=m
CONFIG_NLS_ISO8859_5=m
CONFIG_NLS_ISO8859_6=m
CONFIG_NLS_ISO8859_7=m
CONFIG_NLS_ISO8859_9=m
CONFIG_NLS_ISO8859_13=m
CONFIG_NLS_ISO8859_14=m
CONFIG_NLS_ISO8859_15=m
CONFIG_NLS_KOI8_R=m
CONFIG_NLS_KOI8_U=m
CONFIG_NLS_UTF8=m
#
# Library routines
#
CONFIG_CRC_CCITT=m
CONFIG_CRC16=m
CONFIG_CRC32=y
CONFIG_LIBCRC32C=m
CONFIG_ZLIB_INFLATE=y
CONFIG_ZLIB_DEFLATE=m
CONFIG_TEXTSEARCH=y
CONFIG_TEXTSEARCH_KMP=m
CONFIG_TEXTSEARCH_BM=m
CONFIG_TEXTSEARCH_FSM=m
#
# Instrumentation Support
#
# CONFIG_PROFILING is not set
#
# Kernel hacking
#
# CONFIG_PRINTK_TIME is not set
CONFIG_MAGIC_SYSRQ=y
CONFIG_DEBUG_KERNEL=y
CONFIG_LOG_BUF_SHIFT=18
CONFIG_DETECT_SOFTLOCKUP=y
CONFIG_SCHEDSTATS=y
CONFIG_DEBUG_SLAB=y
# CONFIG_DEBUG_MUTEXES is not set
CONFIG_DEBUG_SPINLOCK=y
CONFIG_DEBUG_SPINLOCK_SLEEP=y
# CONFIG_DEBUG_KOBJECT is not set
# CONFIG_DEBUG_HIGHMEM is not set
# CONFIG_DEBUG_INFO is not set
CONFIG_DEBUG_FS=y
# CONFIG_DEBUG_VM is not set
CONFIG_FORCED_INLINING=y
# CONFIG_RCU_TORTURE_TEST is not set
# CONFIG_LKCD_DUMP is not set
CONFIG_DEBUGGER=y
CONFIG_XMON=y
CONFIG_XMON_DEFAULT=y
# CONFIG_BDI_SWITCH is not set
CONFIG_BOOTX_TEXT=y
# CONFIG_PPC_EARLY_DEBUG_LPAR is not set
# CONFIG_PPC_EARLY_DEBUG_G5 is not set
# CONFIG_PPC_EARLY_DEBUG_RTAS is not set
# CONFIG_PPC_EARLY_DEBUG_MAPLE is not set
# CONFIG_PPC_EARLY_DEBUG_ISERIES is not set
#
# Security options
#
# CONFIG_KEYS is not set
CONFIG_SECURITY=y
CONFIG_SECURITY_NETWORK=y
# CONFIG_SECURITY_NETWORK_XFRM is not set
CONFIG_SECURITY_CAPABILITIES=m
CONFIG_SECURITY_ROOTPLUG=m
CONFIG_SECURITY_SECLVL=m
# CONFIG_SECURITY_SELINUX is not set
CONFIG_SECURITY_APPARMOR=m
#
# Cryptographic options
#
CONFIG_CRYPTO=y
CONFIG_CRYPTO_HMAC=y
CONFIG_CRYPTO_NULL=m
CONFIG_CRYPTO_MD4=m
CONFIG_CRYPTO_MD5=y
CONFIG_CRYPTO_SHA1=m
CONFIG_CRYPTO_SHA256=m
CONFIG_CRYPTO_SHA512=m
CONFIG_CRYPTO_WP512=m
CONFIG_CRYPTO_TGR192=m
CONFIG_CRYPTO_DES=y
CONFIG_CRYPTO_BLOWFISH=m
CONFIG_CRYPTO_TWOFISH=m
CONFIG_CRYPTO_SERPENT=m
CONFIG_CRYPTO_AES=m
CONFIG_CRYPTO_CAST5=m
CONFIG_CRYPTO_CAST6=m
CONFIG_CRYPTO_TEA=m
CONFIG_CRYPTO_ARC4=m
CONFIG_CRYPTO_KHAZAD=m
CONFIG_CRYPTO_ANUBIS=m
CONFIG_CRYPTO_DEFLATE=m
CONFIG_CRYPTO_MICHAEL_MIC=m
CONFIG_CRYPTO_CRC32C=m
CONFIG_CRYPTO_TEST=m
#
# Hardware crypto devices
#
^ permalink raw reply [flat|nested] 62+ messages in thread* Re: Linux v2.6.16-rc5
2006-03-06 22:20 ` Olaf Hering
@ 2006-03-06 23:02 ` Olaf Hering
2006-03-11 21:59 ` Olaf Hering
0 siblings, 1 reply; 62+ messages in thread
From: Olaf Hering @ 2006-03-06 23:02 UTC (permalink / raw)
To: Paul Mackerras; +Cc: Linus Torvalds, linuxppc-dev, Linux Kernel Mailing List
On Mon, Mar 06, Olaf Hering wrote:
> On Mon, Mar 06, Olaf Hering wrote:
>
> > On Mon, Mar 06, Paul Mackeras wrote:
> >
> > > There are also commits from Ben H that change the way we parse
> > > addresses from the OF device tree. If you can bisect a bit further
> > > that would be good, although you may strike problems between the 401d
> > > and 6237 commits I mentioned above.
> >
> > What I have right now is this, which got me in a non-compiling state.
> > I will pick the udbg stuff and apply the relevant changes to -git5.
I tried with CONFIG_BOOTX_TEXT disabled. same result. This is the list
of patches I used on top of 2.6.15:
patches.kernel.org/patch-2.6.15-git5
patches.suse/get_cramfs_inode-revert.patch
patches.suse/suse-ppc-legacy-io.patch
patches.arch/0022-powerpc-incorrect-rmo_top-handling-in-prom_init.txt
patches.suse/9100b205fdc70b300894954ebebbf2709c5ed525.patch
patches.suse/3d1229d6ae92ed1994f4411b8493327ef8f4b76f.patch
patches.suse/d1405b869850982f05c7ec0d3f137ca27588192f.patch
patches.suse/463ce0e103f419f51b1769111e73fe8bb305d0ec.patch
patches.suse/51d3082fe6e55aecfa17113dbe98077c749f724c.patch
patches.suse/31df1678d7732b94178a6e457ed6666e4431212f.patch
patches.suse/8dacaedf04467e32c50148751a96150e73323cdc.patch
patches.suse/52020d2bda9fe447bb50674a2e39e4064b6a10b5.patch
^ permalink raw reply [flat|nested] 62+ messages in thread
* Re: Linux v2.6.16-rc5
2006-03-06 23:02 ` Olaf Hering
@ 2006-03-11 21:59 ` Olaf Hering
0 siblings, 0 replies; 62+ messages in thread
From: Olaf Hering @ 2006-03-11 21:59 UTC (permalink / raw)
To: Paul Mackerras; +Cc: Linus Torvalds, linuxppc-dev, Linux Kernel Mailing List
On Tue, Mar 07, Olaf Hering wrote:
> On Mon, Mar 06, Olaf Hering wrote:
>
> > On Mon, Mar 06, Olaf Hering wrote:
> >
> > > On Mon, Mar 06, Paul Mackeras wrote:
> > >
> > > > There are also commits from Ben H that change the way we parse
> > > > addresses from the OF device tree. If you can bisect a bit further
> > > > that would be good, although you may strike problems between the 401d
> > > > and 6237 commits I mentioned above.
> > >
> > > What I have right now is this, which got me in a non-compiling state.
> > > I will pick the udbg stuff and apply the relevant changes to -git5.
>
> I tried with CONFIG_BOOTX_TEXT disabled. same result. This is the list
> of patches I used on top of 2.6.15:
>
> patches.kernel.org/patch-2.6.15-git5
> patches.suse/get_cramfs_inode-revert.patch
> patches.suse/suse-ppc-legacy-io.patch
> patches.arch/0022-powerpc-incorrect-rmo_top-handling-in-prom_init.txt
> patches.suse/9100b205fdc70b300894954ebebbf2709c5ed525.patch
> patches.suse/3d1229d6ae92ed1994f4411b8493327ef8f4b76f.patch
> patches.suse/d1405b869850982f05c7ec0d3f137ca27588192f.patch
> patches.suse/463ce0e103f419f51b1769111e73fe8bb305d0ec.patch
>
> patches.suse/51d3082fe6e55aecfa17113dbe98077c749f724c.patch
> patches.suse/31df1678d7732b94178a6e457ed6666e4431212f.patch
> patches.suse/8dacaedf04467e32c50148751a96150e73323cdc.patch
> patches.suse/52020d2bda9fe447bb50674a2e39e4064b6a10b5.patch
51d3082fe6e55aecfa17113dbe98077c749f724c enabled powersave_nap
unconditionally. But early G3 cpus can not handle it.
I sent a patch in another thread.
^ permalink raw reply [flat|nested] 62+ messages in thread
* Re: Linux v2.6.16-rc5
2006-02-27 5:27 Linux v2.6.16-rc5 Linus Torvalds
` (9 preceding siblings ...)
2006-03-05 14:09 ` Linux v2.6.16-rc5 Olaf Hering
@ 2006-03-05 22:03 ` Mathieu Chouquet-Stringer
2006-03-06 2:12 ` Linus Torvalds
10 siblings, 1 reply; 62+ messages in thread
From: Mathieu Chouquet-Stringer @ 2006-03-05 22:03 UTC (permalink / raw)
To: Linus Torvalds; +Cc: Linux Kernel Mailing List
torvalds@osdl.org (Linus Torvalds) writes:
> Have I missed anything? Holler. And please keep reminding about any
> regressions since 2.6.15.
As reported yesterday [1], the generic irq framework for alpha introduced
in commit 0595bf3bca9d9932a05b06dd438f40f01d27cd33 kills my box under
fairly heavy disk usage. I got a md raid 0 array stripped accross 3 scsi
disks and any kind of relatively intensive IOs (like md5sum or sha1sum
against iso files) kill the box immediately; either it panics in
kernel/exit.c:do_exit - the first three "unlikely" - or in
arch/alpha/mm/fault.c:do_page_fault "Unable to handle paging reguest at
some address"...
Reverting it makes the box stable again (as it was under vanilla 2.6.15).
Here's the commit detail:
0595bf3bca9d9932a05b06dd438f40f01d27cd33 is first bad commit
diff-tree 0595bf3bca9d9932a05b06dd438f40f01d27cd33 (from eee45269b0f5979c70bc151c6c2f4e5f4f5ababe)
Author: Ivan Kokshaysky <ink@jurassic.park.msu.ru>
Date: Fri Jan 6 00:12:22 2006 -0800
[PATCH] Alpha: convert to generic irq framework (alpha part)
Kconfig tweaks and tons of deletions.
Signed-off-by: Ivan Kokshaysky <ink@jurassic.park.msu.ru>
Cc: Christoph Hellwig <hch@lst.de>
Cc: Richard Henderson <rth@twiddle.net>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
:040000 040000 ac127f16325bb65941bd38208325ab7821877f52 15d7d4d17a7c8cfb8fe53c29ded31ff9cf287534 M arch
:040000 040000 287f73cdf371b2b33cc48f1d876005aab29ff3de 29263093ae33ceccd6346b987870367bc8329f0a M include
[1] Problem on Alpha with "convert to generic irq framework"
Message-Id: <20060304111219.GA10532@localhost>
http://lkml.org/lkml/2006/3/4/31
--
Mathieu Chouquet-Stringer
^ permalink raw reply [flat|nested] 62+ messages in thread* Re: Linux v2.6.16-rc5
2006-03-05 22:03 ` Mathieu Chouquet-Stringer
@ 2006-03-06 2:12 ` Linus Torvalds
0 siblings, 0 replies; 62+ messages in thread
From: Linus Torvalds @ 2006-03-06 2:12 UTC (permalink / raw)
To: Mathieu Chouquet-Stringer
Cc: Linux Kernel Mailing List, Ivan Kokshaysky, Richard Henderson,
Christoph Hellwig
Ivan, rth,
any ideas?
Linus
On Sun, 5 Mar 2006, Mathieu Chouquet-Stringer wrote:
>
> torvalds@osdl.org (Linus Torvalds) writes:
> > Have I missed anything? Holler. And please keep reminding about any
> > regressions since 2.6.15.
>
> As reported yesterday [1], the generic irq framework for alpha introduced
> in commit 0595bf3bca9d9932a05b06dd438f40f01d27cd33 kills my box under
> fairly heavy disk usage. I got a md raid 0 array stripped accross 3 scsi
> disks and any kind of relatively intensive IOs (like md5sum or sha1sum
> against iso files) kill the box immediately; either it panics in
> kernel/exit.c:do_exit - the first three "unlikely" - or in
> arch/alpha/mm/fault.c:do_page_fault "Unable to handle paging reguest at
> some address"...
>
> Reverting it makes the box stable again (as it was under vanilla 2.6.15).
>
> Here's the commit detail:
>
> 0595bf3bca9d9932a05b06dd438f40f01d27cd33 is first bad commit
> diff-tree 0595bf3bca9d9932a05b06dd438f40f01d27cd33 (from eee45269b0f5979c70bc151c6c2f4e5f4f5ababe)
> Author: Ivan Kokshaysky <ink@jurassic.park.msu.ru>
> Date: Fri Jan 6 00:12:22 2006 -0800
>
> [PATCH] Alpha: convert to generic irq framework (alpha part)
>
> Kconfig tweaks and tons of deletions.
>
> Signed-off-by: Ivan Kokshaysky <ink@jurassic.park.msu.ru>
> Cc: Christoph Hellwig <hch@lst.de>
> Cc: Richard Henderson <rth@twiddle.net>
> Signed-off-by: Andrew Morton <akpm@osdl.org>
> Signed-off-by: Linus Torvalds <torvalds@osdl.org>
>
> :040000 040000 ac127f16325bb65941bd38208325ab7821877f52 15d7d4d17a7c8cfb8fe53c29ded31ff9cf287534 M arch
> :040000 040000 287f73cdf371b2b33cc48f1d876005aab29ff3de 29263093ae33ceccd6346b987870367bc8329f0a M include
>
>
> [1] Problem on Alpha with "convert to generic irq framework"
> Message-Id: <20060304111219.GA10532@localhost>
> http://lkml.org/lkml/2006/3/4/31
>
> --
> Mathieu Chouquet-Stringer
>
^ permalink raw reply [flat|nested] 62+ messages in thread