Skip to contentSkip to conversation

2.6.22-rc4: known regressions v3

PATCH Michal Piotrowski 6 participants 23 messages Jun 13, 2007 – Jun 17, 2007 1 message not in the archive

Subsystems (2)
lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): [email protected]

#1 lore raw

Hi all,

Here is a list of some known regressions in 2.6.22-rc4.

Feel free to add new regressions/remove fixed etc.
http://kernelnewbies.org/known_regressions

Networking

Subject : commit 9093bbb2d96d0184f037cea9b4e952a44ebe7c32 broke the bonding driver
References : http://lkml.org/lkml/2007/6/13/65
Submitter : Dan Aloni <[email protected]>

Status : Unknown

Sparc64

Subject : 2.6.22-rc broke X on Ultra5
References : http://lkml.org/lkml/2007/5/22/78
Submitter : Mikael Pettersson <[email protected]>

Status : problem is being debugged

Suspend

Subject : hibernate(?) fails totally - regression
References : http://lkml.org/lkml/2007/6/1/401
Submitter : David Greaves <[email protected]>

             commit 9666f4009c22f6520ac3fb8a19c9e32ab973e828

Status : problem is being debugged

TTY

Subject : OOPS (NULL pointer dereference) in v2.6.22-rc3
References : http://lkml.org/lkml/2007/6/1/389
http://bugzilla.kernel.org/show_bug.cgi?id„73
http://bugzilla.kernel.org/show_bug.cgi?id…74
Submitter : Alex Riesen <[email protected]>
Status : problem is being debugged

x86-64

Subject : x86-64 2.6.22-rc2 random segfaults
References : http://lkml.org/lkml/2007/5/24/275
Submitter : Ioan Ionita <[email protected]>
Status : Unknown

Regards,
Michal

Signature · 2 lines
LOG
http://www.stardust.webpages.pl/log/
#2 lore raw
Quoted 8 lines · Michal Piotrowski

TTY

Subject : OOPS (NULL pointer dereference) in v2.6.22-rc3
References : http://lkml.org/lkml/2007/6/1/389

            http://bugzilla.kernel.org/show_bug.cgi?id=8473
            http://bugzilla.kernel.org/show_bug.cgi?id=8574

Submitter : Alex Riesen <[email protected]>
Status : problem is being debugged

Patch available at: http://lkml.org/lkml/2007/6/8/490

Björn
-
To unsubscribe from this list: send the line "unsubscribe sparclinux" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html

#3 lore raw
Quoted 11 lines · Björn Steinbrink
Quoted 8 lines · Michal Piotrowski

TTY

Subject : OOPS (NULL pointer dereference) in v2.6.22-rc3
References : http://lkml.org/lkml/2007/6/1/389
http://bugzilla.kernel.org/show_bug.cgi?id„73
http://bugzilla.kernel.org/show_bug.cgi?id…74
Submitter : Alex Riesen <[email protected]>
Status : problem is being debugged

Patch available at: http://lkml.org/lkml/2007/6/8/490

Thanks for letting me know.

Regards,
Michal

Signature · 2 lines
LOG
http://www.stardust.webpages.pl/log/
#4 lore raw
In reply to Björn Steinbrink
Quoted 11 lines · Björn Steinbrink
Quoted 8 lines · Michal Piotrowski

TTY

Subject : OOPS (NULL pointer dereference) in v2.6.22-rc3
References : http://lkml.org/lkml/2007/6/1/389

            http://bugzilla.kernel.org/show_bug.cgi?id=8473
            http://bugzilla.kernel.org/show_bug.cgi?id=8574

Submitter : Alex Riesen <[email protected]>
Status : problem is being debugged

Patch available at: http://lkml.org/lkml/2007/6/8/490

Thanks for letting me know.

Regards,
Michal

Signature · 2 lines
LOG
http://www.stardust.webpages.pl/log/
#6 lore raw
In reply to Michal Piotrowski

Hi all,

The random seg faults on x86_64 is interesting as I have been getting random illegal instruction faults on sparc (sun4c) with 2.6.22-rc3. I have not yet tried to track it down. All I know at present is that it is not a problem on 2.6.20.9.

Regards
Mark Fortescue.

Quoted 72 lines · Michal Piotrowski

Hi all,

Here is a list of some known regressions in 2.6.22-rc4.

Feel free to add new regressions/remove fixed etc.
http://kernelnewbies.org/known_regressions

Networking

Subject : commit 9093bbb2d96d0184f037cea9b4e952a44ebe7c32 broke the bonding driver
References : http://lkml.org/lkml/2007/6/13/65
Submitter : Dan Aloni <[email protected]>

Status : Unknown

Sparc64

Subject : 2.6.22-rc broke X on Ultra5
References : http://lkml.org/lkml/2007/5/22/78
Submitter : Mikael Pettersson <[email protected]>

Status : problem is being debugged

Suspend

Subject : hibernate(?) fails totally - regression
References : http://lkml.org/lkml/2007/6/1/401
Submitter : David Greaves <[email protected]>

           commit 9666f4009c22f6520ac3fb8a19c9e32ab973e828

Status : problem is being debugged

TTY

Subject : OOPS (NULL pointer dereference) in v2.6.22-rc3
References : http://lkml.org/lkml/2007/6/1/389

           http://bugzilla.kernel.org/show_bug.cgi?id=8473
           http://bugzilla.kernel.org/show_bug.cgi?id=8574

Submitter : Alex Riesen <[email protected]>
Status : problem is being debugged

x86-64

Subject : x86-64 2.6.22-rc2 random segfaults
References : http://lkml.org/lkml/2007/5/24/275
Submitter : Ioan Ionita <[email protected]>
Status : Unknown

Regards,
Michal

Signature · 6 lines
LOG
http://www.stardust.webpages.pl/log/
-
To unsubscribe from this list: send the line "unsubscribe sparclinux" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
#7 lore raw
Quoted 4 lines · Mark Fortescue

The random seg faults on x86_64 is interesting as I have been getting random illegal instruction faults on sparc (sun4c) with 2.6.22-rc3. I have not yet tried to track it down. All I know at present is that it is not a problem on 2.6.20.9.

Very interesting. Any hints as to how to test or how long to wait before the illegal instructions happen?

-- wli

#8 lore raw

Hi All,

They apear as soon as simpleinit starts up. Somtimes I get to a login prompt before seeing any. Other times, commands in the simpleinit rc script fail.

They do apear to be random. If a command failes, you re-run the command and it is OK. Commands seen to fail are basic (depmod, rm cat ..).

The test I did use the same binaries with both the OK and problem kernels so it is not a change to the application code, it is definatly a kernel issue.

Regards
Mark Fortescue.

Quoted 12 lines · William Lee Irwin III
Quoted 4 lines · Mark Fortescue

The random seg faults on x86_64 is interesting as I have been getting random illegal instruction faults on sparc (sun4c) with 2.6.22-rc3. I have not yet tried to track it down. All I know at present is that it is not a problem on 2.6.20.9.

Very interesting. Any hints as to how to test or how long to wait before the illegal instructions happen?

-- wli

#9 lore raw
Quoted 8 lines · Mark Fortescue

They apear as soon as simpleinit starts up. Somtimes I get to a login prompt before seeing any. Other times, commands in the simpleinit rc script fail.
They do apear to be random. If a command failes, you re-run the command and it is OK. Commands seen to fail are basic (depmod, rm cat ..). The test I did use the same binaries with both the OK and problem kernels so it is not a change to the application code, it is definatly a kernel issue.

This sounds like it may be addressed by benh's ptep_set_access_flags() fixes. Those fixes are still in -mm, hopefully to hit mainline by 2.6.22.

-- wli

#10 lore raw

Benh's ptep_set_access_flags() patch needs to be applied in order to get anyware with sun4c for all kernels >= linux-2.6.15. If not applied, you will be lucky to get sash running as your init and even that will have very limitit capabilities before it locks up the processor (power up reset required).

It has been applied to both the kernels I used for testing so this problem is independent of the ptep_set_access_flags patch but that does not mean that it is not a related issue.

I will try to get some testing done over the weekend to narrow down when the random illegal instructions first occour.

If I start with 2.6.21 then if that is OK, then I should be able to narow the issue down without too much trouble. If it is between 2.6.20 and 2.6.21 then it will be a right pig as there are a large number of commits that don't compile for sun4c between these two. What I am hoping is that it occours in the 2.6.22-rc2 as per the x86_64.

I am going to have to put a 'reset' button onto my test system as power up resets are bad news on this old hardware and almost all kernel failures result in a processor lockup. I have even had to make BUG reports 'panic' as thoes that I have during kernel fault location had are terminal to a sun4c (they cause a processor lockup).

Regards
Mark Fortescue.

Quoted 16 lines · William Lee Irwin III
Quoted 8 lines · Mark Fortescue

They apear as soon as simpleinit starts up. Somtimes I get to a login prompt before seeing any. Other times, commands in the simpleinit rc script fail.
They do apear to be random. If a command failes, you re-run the command and it is OK. Commands seen to fail are basic (depmod, rm cat ..). The test I did use the same binaries with both the OK and problem kernels so it is not a change to the application code, it is definatly a kernel issue.

This sounds like it may be addressed by benh's ptep_set_access_flags() fixes. Those fixes are still in -mm, hopefully to hit mainline by 2.6.22.

-- wli

#11 lore raw
Quoted 7 lines · Mark Fortescue

Benh's ptep_set_access_flags() patch needs to be applied in order to get anyware with sun4c for all kernels >= linux-2.6.15. If not applied, you will be lucky to get sash running as your init and even that will have very limitit capabilities before it locks up the processor (power up reset required).
It has been applied to both the kernels I used for testing so this problem is independent of the ptep_set_access_flags patch but that

Quoted 8 lines

does not mean that it is not a related issue.
I will try to get some testing done over the weekend to narrow down when the random illegal instructions first occour.
If I start with 2.6.21 then if that is OK, then I should be able to narow the issue down without too much trouble. If it is between 2.6.20 and 2.6.21 then it will be a right pig as there are a large number of commits that don't compile for sun4c between these two. What I am hoping is that it occours in the 2.6.22-rc2 as per the x86_64.

Sounds like I'll be digging through my hardware stockpiles this weekend to find a functional sun4c box.

-- wli

#12 lore raw
In reply to Mark Fortescue
Quoted 7 lines · Mark Fortescue

Benh's ptep_set_access_flags() patch needs to be applied in order to get anyware with sun4c for all kernels >= linux-2.6.15. If not applied, you will be lucky to get sash running as your init and even that will have very limitit capabilities before it locks up the processor (power up reset required).
It has been applied to both the kernels I used for testing so this problem is independent of the ptep_set_access_flags patch but that

Quoted 8 lines

does not mean that it is not a related issue.
I will try to get some testing done over the weekend to narrow down when the random illegal instructions first occour.
If I start with 2.6.21 then if that is OK, then I should be able to narow the issue down without too much trouble. If it is between 2.6.20 and 2.6.21 then it will be a right pig as there are a large number of commits that don't compile for sun4c between these two. What I am hoping is that it occours in the 2.6.22-rc2 as per the x86_64.

Sounds like I'll be digging through my hardware stockpiles this weekend to find a functional sun4c box.

-- wli

#13 lore raw
In reply to William Lee Irwin III

Benh's ptep_set_access_flags() patch needs to be applied in order to get anyware with sun4c for all kernels >= linux-2.6.15. If not applied, you will be lucky to get sash running as your init and even that will have very limitit capabilities before it locks up the processor (power up reset required).

It has been applied to both the kernels I used for testing so this problem is independent of the ptep_set_access_flags patch but that does not mean that it is not a related issue.

I will try to get some testing done over the weekend to narrow down when the random illegal instructions first occour.

If I start with 2.6.21 then if that is OK, then I should be able to narow the issue down without too much trouble. If it is between 2.6.20 and 2.6.21 then it will be a right pig as there are a large number of commits that don't compile for sun4c between these two. What I am hoping is that it occours in the 2.6.22-rc2 as per the x86_64.

I am going to have to put a 'reset' button onto my test system as power up resets are bad news on this old hardware and almost all kernel failures result in a processor lockup. I have even had to make BUG reports 'panic' as thoes that I have during kernel fault location had are terminal to a sun4c (they cause a processor lockup).

Regards
Mark Fortescue.

Quoted 16 lines · William Lee Irwin III
Quoted 8 lines · Mark Fortescue

They apear as soon as simpleinit starts up. Somtimes I get to a login prompt before seeing any. Other times, commands in the simpleinit rc script fail.
They do apear to be random. If a command failes, you re-run the command and it is OK. Commands seen to fail are basic (depmod, rm cat ..). The test I did use the same binaries with both the OK and problem kernels so it is not a change to the application code, it is definatly a kernel issue.

This sounds like it may be addressed by benh's ptep_set_access_flags() fixes. Those fixes are still in -mm, hopefully to hit mainline by 2.6.22.

-- wli

#14 lore raw
In reply to William Lee Irwin III

Hi all,

I have been investigating the random invalid instruction occourances on sparc32 (sun4c) and identified that the problem was introduced pre-v2.6.22-rc1. v2.6.21 is OK. The first time I have observed the issue so far is after commit b46b8f19c9cd435ecac4d9d12b39d78c137ecd66:
Increase slab redzone to 64bits.

Prior to this commit there apears to be a problem with the memory management (depmod -a causes the system to run out of memory!) that may be masking the issue. As a result of this, I am going to try to find the 'last known good' commit after v2.6.21 to see if this helps narrow down the cause.

Regards
Mark Fortescue.

Quoted 16 lines · William Lee Irwin III
Quoted 8 lines · Mark Fortescue

They apear as soon as simpleinit starts up. Somtimes I get to a login prompt before seeing any. Other times, commands in the simpleinit rc script fail.
They do apear to be random. If a command failes, you re-run the command and it is OK. Commands seen to fail are basic (depmod, rm cat ..). The test I did use the same binaries with both the OK and problem kernels so it is not a change to the application code, it is definatly a kernel issue.

This sounds like it may be addressed by benh's ptep_set_access_flags() fixes. Those fixes are still in -mm, hopefully to hit mainline by 2.6.22.

-- wli

#15 lore raw
In reply to William Lee Irwin III

Hi all,

I have been investigating the random invalid instruction occourances on sparc32 (sun4c) and identified that the problem was introduced pre-v2.6.22-rc1. v2.6.21 is OK. The first time I have observed the issue so far is after commit b46b8f19c9cd435ecac4d9d12b39d78c137ecd66:
Increase slab redzone to 64bits.

Prior to this commit there apears to be a problem with the memory management (depmod -a causes the system to run out of memory!) that may be masking the issue. As a result of this, I am going to try to find the 'last known good' commit after v2.6.21 to see if this helps narrow down the cause.

Regards
Mark Fortescue.

Quoted 16 lines · William Lee Irwin III
Quoted 8 lines · Mark Fortescue

They apear as soon as simpleinit starts up. Somtimes I get to a login prompt before seeing any. Other times, commands in the simpleinit rc script fail.
They do apear to be random. If a command failes, you re-run the command and it is OK. Commands seen to fail are basic (depmod, rm cat ..). The test I did use the same binaries with both the OK and problem kernels so it is not a change to the application code, it is definatly a kernel issue.

This sounds like it may be addressed by benh's ptep_set_access_flags() fixes. Those fixes are still in -mm, hopefully to hit mainline by 2.6.22.

-- wli

#16 lore raw
In reply to Mark Fortescue
Quoted 8 lines · Mark Fortescue

They apear as soon as simpleinit starts up. Somtimes I get to a login prompt before seeing any. Other times, commands in the simpleinit rc script fail.
They do apear to be random. If a command failes, you re-run the command and it is OK. Commands seen to fail are basic (depmod, rm cat ..). The test I did use the same binaries with both the OK and problem kernels so it is not a change to the application code, it is definatly a kernel issue.

This sounds like it may be addressed by benh's ptep_set_access_flags() fixes. Those fixes are still in -mm, hopefully to hit mainline by 2.6.22.

-- wli

#17 lore raw
In reply to William Lee Irwin III

Hi All,

They apear as soon as simpleinit starts up. Somtimes I get to a login prompt before seeing any. Other times, commands in the simpleinit rc script fail.

They do apear to be random. If a command failes, you re-run the command and it is OK. Commands seen to fail are basic (depmod, rm cat ..).

The test I did use the same binaries with both the OK and problem kernels so it is not a change to the application code, it is definatly a kernel issue.

Regards
Mark Fortescue.

Quoted 12 lines · William Lee Irwin III
Quoted 4 lines · Mark Fortescue

The random seg faults on x86_64 is interesting as I have been getting random illegal instruction faults on sparc (sun4c) with 2.6.22-rc3. I have not yet tried to track it down. All I know at present is that it is not a problem on 2.6.20.9.

Very interesting. Any hints as to how to test or how long to wait before the illegal instructions happen?

-- wli

#18 lore raw
In reply to Mark Fortescue
Quoted 4 lines · Mark Fortescue

The random seg faults on x86_64 is interesting as I have been getting random illegal instruction faults on sparc (sun4c) with 2.6.22-rc3. I have not yet tried to track it down. All I know at present is that it is not a problem on 2.6.20.9.

Very interesting. Any hints as to how to test or how long to wait before the illegal instructions happen?

-- wli

#19 lore raw
In reply to Michal Piotrowski

Hi all,

The random seg faults on x86_64 is interesting as I have been getting random illegal instruction faults on sparc (sun4c) with 2.6.22-rc3. I have not yet tried to track it down. All I know at present is that it is not a problem on 2.6.20.9.

Regards
Mark Fortescue.

Quoted 72 lines · Michal Piotrowski

Hi all,

Here is a list of some known regressions in 2.6.22-rc4.

Feel free to add new regressions/remove fixed etc.
http://kernelnewbies.org/known_regressions

Networking

Subject : commit 9093bbb2d96d0184f037cea9b4e952a44ebe7c32 broke the bonding driver
References : http://lkml.org/lkml/2007/6/13/65
Submitter : Dan Aloni <[email protected]>

Status : Unknown

Sparc64

Subject : 2.6.22-rc broke X on Ultra5
References : http://lkml.org/lkml/2007/5/22/78
Submitter : Mikael Pettersson <[email protected]>

Status : problem is being debugged

Suspend

Subject : hibernate(?) fails totally - regression
References : http://lkml.org/lkml/2007/6/1/401
Submitter : David Greaves <[email protected]>

           commit 9666f4009c22f6520ac3fb8a19c9e32ab973e828

Status : problem is being debugged

TTY

Subject : OOPS (NULL pointer dereference) in v2.6.22-rc3
References : http://lkml.org/lkml/2007/6/1/389

           http://bugzilla.kernel.org/show_bug.cgi?id=8473
           http://bugzilla.kernel.org/show_bug.cgi?id=8574

Submitter : Alex Riesen <[email protected]>
Status : problem is being debugged

x86-64

Subject : x86-64 2.6.22-rc2 random segfaults
References : http://lkml.org/lkml/2007/5/24/275
Submitter : Ioan Ionita <[email protected]>
Status : Unknown

Regards,
Michal

Signature · 6 lines
LOG
http://www.stardust.webpages.pl/log/
-
To unsubscribe from this list: send the line "unsubscribe sparclinux" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
#20 lore raw
In reply to Michal Piotrowski
Quoted 9 lines · On Wed, 13 Jun 2007 21:57:56 +0200 Michal Piotrowski…

Hi all,

Here is a list of some known regressions in 2.6.22-rc4.

Feel free to add new regressions/remove fixed etc.
http://kernelnewbies.org/known_regressions

Quoted 9 lines

Networking

Subject : commit 9093bbb2d96d0184f037cea9b4e952a44ebe7c32 broke the bonding driver
References : http://lkml.org/lkml/2007/6/13/65
Submitter : Dan Aloni <[email protected]>

Status : Unknown

Patch available (to bonding).

#21 lore raw
In reply to Michal Piotrowski
Quoted 8 lines · Michal Piotrowski

Subject : hibernate(?) fails totally - regression
References : http://lkml.org/lkml/2007/6/1/401
Submitter : David Greaves <[email protected]>

            commit 9666f4009c22f6520ac3fb8a19c9e32ab973e828

Status : problem is being debugged

Ahh. This is fixed (fix by Tejun, confirmed by David), and the fix has been merged. It's commit bc90ba093a, in case anybody cares.

Linus

#22 lore raw
In reply to Michal Piotrowski
Quoted 8 lines · Michal Piotrowski

Subject : hibernate(?) fails totally - regression
References : http://lkml.org/lkml/2007/6/1/401
Submitter : David Greaves <[email protected]>

            commit 9666f4009c22f6520ac3fb8a19c9e32ab973e828

Status : problem is being debugged

Ahh. This is fixed (fix by Tejun, confirmed by David), and the fix has been merged. It's commit bc90ba093a, in case anybody cares.

Linus

#23 lore raw
In reply to a message not in the archive

Hi all,

Here is a list of some known regressions in 2.6.22-rc4.

Feel free to add new regressions/remove fixed etc.
http://kernelnewbies.org/known_regressions

Networking

Subject : commit 9093bbb2d96d0184f037cea9b4e952a44ebe7c32 broke the bonding driver
References : http://lkml.org/lkml/2007/6/13/65
Submitter : Dan Aloni <[email protected]>

Status : Unknown

Sparc64

Subject : 2.6.22-rc broke X on Ultra5
References : http://lkml.org/lkml/2007/5/22/78
Submitter : Mikael Pettersson <[email protected]>

Status : problem is being debugged

Suspend

Subject : hibernate(?) fails totally - regression
References : http://lkml.org/lkml/2007/6/1/401
Submitter : David Greaves <[email protected]>

            commit 9666f4009c22f6520ac3fb8a19c9e32ab973e828

Status : problem is being debugged

TTY

Subject : OOPS (NULL pointer dereference) in v2.6.22-rc3
References : http://lkml.org/lkml/2007/6/1/389

            http://bugzilla.kernel.org/show_bug.cgi?id=8473
            http://bugzilla.kernel.org/show_bug.cgi?id=8574

Submitter : Alex Riesen <[email protected]>
Status : problem is being debugged

x86-64

Subject : x86-64 2.6.22-rc2 random segfaults
References : http://lkml.org/lkml/2007/5/24/275
Submitter : Ioan Ionita <[email protected]>
Status : Unknown

Regards,
Michal

Signature · 2 lines
LOG
http://www.stardust.webpages.pl/log/