On Do, 27 Sep 2007, Rafael J. Wysocki wrote:
> Does it happen with 2.6.22?
Hard to say. It didn't happen as long as I used -22, but it didn't
happen for a long time (since I run -rc6), and it is not reproducible.
What I did at this time is a:
tar -cjf foo.tar.bz2
On Thursday, 27 September 2007 12:31, Norbert Preining wrote:
> Hi all!
>
> (Please Cc)
>
> kernel 2.6.23-rc6
> Debian/sid
Does it happen with 2.6.22?
> kernel ooops:
>
> BUG: unable to handle kernel paging request at virtual address 104b
> printing eip:
> c0195bd3
> *pde =
>
On Thursday, 27 September 2007 12:31, Norbert Preining wrote:
Hi all!
(Please Cc)
kernel 2.6.23-rc6
Debian/sid
Does it happen with 2.6.22?
kernel ooops:
BUG: unable to handle kernel paging request at virtual address 104b
printing eip:
c0195bd3
*pde =
Oops:
On Do, 27 Sep 2007, Rafael J. Wysocki wrote:
Does it happen with 2.6.22?
Hard to say. It didn't happen as long as I used -22, but it didn't
happen for a long time (since I run -rc6), and it is not reproducible.
What I did at this time is a:
tar -cjf foo.tar.bz2
On Thursday, 27 September 2007 15:13, Norbert Preining wrote:
On Do, 27 Sep 2007, Rafael J. Wysocki wrote:
Does it happen with 2.6.22?
Hard to say. It didn't happen as long as I used -22, but it didn't
happen for a long time (since I run -rc6), and it is not reproducible.
What I did at
Hi,
Could you please sent the objdump of the ext4_discard_reservation
function? It doesn't match what I see here.
Thanks,
Mingming
On Thu, 2007-09-27 at 12:31 +0200, [EMAIL PROTECTED]
wrote:
Hi all!
(Please Cc)
kernel 2.6.23-rc6
Debian/sid
kernel ooops:
BUG: unable to handle kernel
Hello together,
I've found an easier way to demonstrate the bug
and filed a report at bugzilla.kernel.org:
http://bugzilla.kernel.org/show_bug.cgi?id=8928
Hope there will be a quick resolution for this issue
as the boxes crashing serve 800 users and more.
Best regards,
Thomas
-
To unsubscribe
Hello together,
I've found an easier way to demonstrate the bug
and filed a report at bugzilla.kernel.org:
http://bugzilla.kernel.org/show_bug.cgi?id=8928
Hope there will be a quick resolution for this issue
as the boxes crashing serve 800 users and more.
Best regards,
Thomas
-
To unsubscribe
On Wed, Aug 22, 2007 at 17:09:04 +0200, Thomas Jarosch wrote:
> Hello,
>
> > > kernel BUG at arch/i386/mm/highmem.c:38
> > >
> > > Try this.
>
> I just tried kernel 2.6.22.4 and 2.6.23-rc3. Using 2.6.23-rc3 vanilla,
> the box survives only 3 seconds with ipt_CRASH. Here's the backtrace,
> it's
Hello,
> > kernel BUG at arch/i386/mm/highmem.c:38
> >
> > Try this.
I just tried kernel 2.6.22.4 and 2.6.23-rc3. Using 2.6.23-rc3 vanilla,
the box survives only 3 seconds with ipt_CRASH. Here's the backtrace,
it's only slightly different:
[ cut here ]
kernel BUG at
Hello,
kernel BUG at arch/i386/mm/highmem.c:38
Try this.
I just tried kernel 2.6.22.4 and 2.6.23-rc3. Using 2.6.23-rc3 vanilla,
the box survives only 3 seconds with ipt_CRASH. Here's the backtrace,
it's only slightly different:
[ cut here ]
kernel BUG at
On Wed, Aug 22, 2007 at 17:09:04 +0200, Thomas Jarosch wrote:
Hello,
kernel BUG at arch/i386/mm/highmem.c:38
Try this.
I just tried kernel 2.6.22.4 and 2.6.23-rc3. Using 2.6.23-rc3 vanilla,
the box survives only 3 seconds with ipt_CRASH. Here's the backtrace,
it's only slightly
On Monday, 20. August 2007, Alexey Dobriyan wrote:
> kernel BUG at arch/i386/mm/highmem.c:38
>
> Try this.
>
> commit b8c1c5da1520977cb55a358f20fc09567d40cad9
> tree c762e6ad77297beed0978337ce2f5b0c50add739
> parent 01e457cfcd5b6b6f18d0bb8cec0c5d43df56557e
> author Andrew Morton <[EMAIL
On Monday, 20. August 2007, Alexey Dobriyan wrote:
kernel BUG at arch/i386/mm/highmem.c:38
Try this.
commit b8c1c5da1520977cb55a358f20fc09567d40cad9
tree c762e6ad77297beed0978337ce2f5b0c50add739
parent 01e457cfcd5b6b6f18d0bb8cec0c5d43df56557e
author Andrew Morton [EMAIL PROTECTED]
On Mon, Aug 20, 2007 at 06:08:08PM +0200, Thomas Jarosch wrote:
> I'm currently debugging a kernel oops with kernel 2.6.21.7 that occurs
> from time to time with our netfilter accounting module ipt_ACCOUNT
> (http://www.intra2net.com/de/produkte/opensource/ipt_account/).
kernel BUG at
On Mon, Aug 20, 2007 at 06:08:08PM +0200, Thomas Jarosch wrote:
I'm currently debugging a kernel oops with kernel 2.6.21.7 that occurs
from time to time with our netfilter accounting module ipt_ACCOUNT
(http://www.intra2net.com/de/produkte/opensource/ipt_account/).
kernel BUG at
(this one looks like it should go to netdev as well - added to Cc)
On 10/08/07, Sinisa Segvic <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I've just got a kernel oops.
>
> http://lxr.linux.no/source/Documentation/oops-tracing.txt
> seems to suggest that oops reports are welcome at this address.
>
>
(this one looks like it should go to netdev as well - added to Cc)
On 10/08/07, Sinisa Segvic [EMAIL PROTECTED] wrote:
Hi,
I've just got a kernel oops.
http://lxr.linux.no/source/Documentation/oops-tracing.txt
seems to suggest that oops reports are welcome at this address.
Cheers,
Michal Piotrowski wrote:
You need to upgrade the kernel "yum upgrade kernel.i686"
If the problem still appears, fill bug report in RedHat bugzilla
https://bugzilla.redhat.com/bugzilla/index.cgi
I am seeing this problem in the FC5 2.6.20-1-2316 kernel, and I have not
seen a new kernel show up
Michal Piotrowski wrote:
You need to upgrade the kernel yum upgrade kernel.i686
If the problem still appears, fill bug report in RedHat bugzilla
https://bugzilla.redhat.com/bugzilla/index.cgi
I am seeing this problem in the FC5 2.6.20-1-2316 kernel, and I have not
seen a new kernel show up in
Am Dienstag, 22. Mai 2007 13:18 schrieben Sie:
> Am Dienstag, 22. Mai 2007 00:54 schrieben Sie:
> > On Tue, 22 May 2007 00:28:57 +0200
> >
> > "Uwe Bugla" <[EMAIL PROTECTED]> wrote:
> > > kernel 2.6.21.1 makes my machine Oops about 20 seconds after KDE 3,5 is
> > > brought up showing its graphical
Am Dienstag, 22. Mai 2007 13:18 schrieben Sie:
Am Dienstag, 22. Mai 2007 00:54 schrieben Sie:
On Tue, 22 May 2007 00:28:57 +0200
Uwe Bugla [EMAIL PROTECTED] wrote:
kernel 2.6.21.1 makes my machine Oops about 20 seconds after KDE 3,5 is
brought up showing its graphical login (kdm):
On Tue, May 22, 2007 at 12:28:57AM +0200, Uwe Bugla wrote:
> Hello everybody,
>
> kernel 2.6.21.1 makes my machine Oops about 20 seconds after KDE 3,5 is
> brought up showing its graphical login (kdm):
>
> lspci -v, based on a "sane" kernel 2.6.22-rc2 or 2.6.20.11 (with both of
> them
Uwe Bugla schrieb:
Hello everybody,
kernel 2.6.21.1 makes my machine Oops about 20 seconds after KDE 3,5 is brought
up showing its graphical login (kdm):
lspci -v, based on a "sane" kernel 2.6.22-rc2 or 2.6.20.11 (with both of them
the Oops does not happen at all) looks like this:
00:00.0
On 5/21/07, Uwe Bugla <[EMAIL PROTECTED]> wrote:
kernel 2.6.21.1 makes my machine Oops about 20 seconds after KDE 3,5 is brought
up showing its graphical login (kdm):
Please include the output out of the actual oops message. It has all
sorts of information that will help track this down.
The
On Tue, 22 May 2007 00:28:57 +0200
"Uwe Bugla" <[EMAIL PROTECTED]> wrote:
> kernel 2.6.21.1 makes my machine Oops about 20 seconds after KDE 3,5 is
> brought up showing its graphical login (kdm):
We're completely blind unless we can see that oops info. If it reached
/var/log/messages then
On 5/21/07, Uwe Bugla [EMAIL PROTECTED] wrote:
kernel 2.6.21.1 makes my machine Oops about 20 seconds after KDE 3,5 is brought
up showing its graphical login (kdm):
Please include the output out of the actual oops message. It has all
sorts of information that will help track this down.
The
On Tue, 22 May 2007 00:28:57 +0200
Uwe Bugla [EMAIL PROTECTED] wrote:
kernel 2.6.21.1 makes my machine Oops about 20 seconds after KDE 3,5 is
brought up showing its graphical login (kdm):
We're completely blind unless we can see that oops info. If it reached
/var/log/messages then please
Uwe Bugla schrieb:
Hello everybody,
kernel 2.6.21.1 makes my machine Oops about 20 seconds after KDE 3,5 is brought
up showing its graphical login (kdm):
lspci -v, based on a sane kernel 2.6.22-rc2 or 2.6.20.11 (with both of them
the Oops does not happen at all) looks like this:
00:00.0
On Tue, May 22, 2007 at 12:28:57AM +0200, Uwe Bugla wrote:
Hello everybody,
kernel 2.6.21.1 makes my machine Oops about 20 seconds after KDE 3,5 is
brought up showing its graphical login (kdm):
lspci -v, based on a sane kernel 2.6.22-rc2 or 2.6.20.11 (with both of
them the Oops
On Mon, 14 May 2007 09:16:11 +0200
Gabor Burjan <[EMAIL PROTECTED]> wrote:
> On Sat, May 12, 2007 at 05:05:51PM +0200, Patrick McHardy wrote:
> > Gabor Burjan wrote:
> > > EIP is at destroy_conntrack+0x52/0x127 [nf_conntrack]
> > >
> > >>>nmblookup
> > >>>cat /proc/net/ip_conntrack
> > >>>
> >
On Sat, May 12, 2007 at 05:05:51PM +0200, Patrick McHardy wrote:
> Gabor Burjan wrote:
> > EIP is at destroy_conntrack+0x52/0x127 [nf_conntrack]
> >
> >>>nmblookup
> >>>cat /proc/net/ip_conntrack
> >>>
> >>>sleep 3
> >>>
> >>>rmmod nf_conntrack_netbios_ns
>
> Thanks for the report and good
On Sat, May 12, 2007 at 05:05:51PM +0200, Patrick McHardy wrote:
Gabor Burjan wrote:
EIP is at destroy_conntrack+0x52/0x127 [nf_conntrack]
nmblookup existing_netbios_name
cat /proc/net/ip_conntrack
sleep 3
rmmod nf_conntrack_netbios_ns
Thanks for the report and good testcase, the
On Mon, 14 May 2007 09:16:11 +0200
Gabor Burjan [EMAIL PROTECTED] wrote:
On Sat, May 12, 2007 at 05:05:51PM +0200, Patrick McHardy wrote:
Gabor Burjan wrote:
EIP is at destroy_conntrack+0x52/0x127 [nf_conntrack]
nmblookup existing_netbios_name
cat /proc/net/ip_conntrack
sleep 3
Gabor Burjan wrote:
> EIP is at destroy_conntrack+0x52/0x127 [nf_conntrack]
>
>>>nmblookup
>>>cat /proc/net/ip_conntrack
>>>
>>>sleep 3
>>>
>>>rmmod nf_conntrack_netbios_ns
Thanks for the report and good testcase, the crash can only happen with
a sleep of >= 3s after the last nmblookup packet
Gabor Burjan wrote:
EIP is at destroy_conntrack+0x52/0x127 [nf_conntrack]
nmblookup existing_netbios_name
cat /proc/net/ip_conntrack
sleep 3
rmmod nf_conntrack_netbios_ns
Thanks for the report and good testcase, the crash can only happen with
a sleep of = 3s after the last nmblookup packet
Hi,
On Thu, May 10, 2007 at 03:34:11AM -0700, Andrew Morton wrote:
>
> (add netdev to cc)
>
> On Thu, 10 May 2007 11:06:03 +0200 Gabor Burjan <[EMAIL PROTECTED]> wrote:
>
> > Hi,
> >
> > [1.] One line summary of the problem:
> >
> > Kernel oops after unloading nf_conntrack_netbios_ns module
(add netdev to cc)
On Thu, 10 May 2007 11:06:03 +0200 Gabor Burjan <[EMAIL PROTECTED]> wrote:
> Hi,
>
> [1.] One line summary of the problem:
>
> Kernel oops after unloading nf_conntrack_netbios_ns module
>
> [2.] Full description of the problem/report:
>
> After I remove the netbios-ns
(add netdev to cc)
On Thu, 10 May 2007 11:06:03 +0200 Gabor Burjan [EMAIL PROTECTED] wrote:
Hi,
[1.] One line summary of the problem:
Kernel oops after unloading nf_conntrack_netbios_ns module
[2.] Full description of the problem/report:
After I remove the netbios-ns conntrack
Hi,
On Thu, May 10, 2007 at 03:34:11AM -0700, Andrew Morton wrote:
(add netdev to cc)
On Thu, 10 May 2007 11:06:03 +0200 Gabor Burjan [EMAIL PROTECTED] wrote:
Hi,
[1.] One line summary of the problem:
Kernel oops after unloading nf_conntrack_netbios_ns module
[2.] Full
On Tue, 08 May 2007 17:54:40 -0400
Chuck Ebbert <[EMAIL PROTECTED]> wrote:
> Chuck Ebbert wrote:
> > In 2.6.21.1 when dock driver initialization fails it does a kfree()
> > of dock_station. (Below, this is due to some error installing a
> > notify handler.) Later when a bay is discovered it calls
Chuck Ebbert wrote:
> In 2.6.21.1 when dock driver initialization fails it does a kfree()
> of dock_station. (Below, this is due to some error installing a
> notify handler.) Later when a bay is discovered it calls
> is_dock_device() which attempts to lock the (nonexistent)
> dock_station. Reason
Chuck Ebbert wrote:
In 2.6.21.1 when dock driver initialization fails it does a kfree()
of dock_station. (Below, this is due to some error installing a
notify handler.) Later when a bay is discovered it calls
is_dock_device() which attempts to lock the (nonexistent)
dock_station. Reason is
On Tue, 08 May 2007 17:54:40 -0400
Chuck Ebbert [EMAIL PROTECTED] wrote:
Chuck Ebbert wrote:
In 2.6.21.1 when dock driver initialization fails it does a kfree()
of dock_station. (Below, this is due to some error installing a
notify handler.) Later when a bay is discovered it calls
Alexander,
Rather than try to hunt down the oops via the interrupt code I'll try to
fix the original problem, which is cooked_ioctl incorrectly determines
the length of the track when an audio CD also contains a data track. I
have noticed this bug for a long time (over a year) but only
Alexander,
Rather than try to hunt down the oops via the interrupt code I'll try to
fix the original problem, which is cooked_ioctl incorrectly determines
the length of the track when an audio CD also contains a data track. I
have noticed this bug for a long time (over a year) but only
Thanks.
On 5/3/07, Michal Piotrowski <[EMAIL PROTECTED]> wrote:
Hi Gary,
On 03/05/07, Gary Martin <[EMAIL PROTECTED]> wrote:
> I have a system running Fedora Core 6 on a Dell PE4400 that crashed
> and became unresponsive, I captured the following kernel oops in
> /var/log/messages:
>
> Apr 30
Hi Gary,
On 03/05/07, Gary Martin <[EMAIL PROTECTED]> wrote:
I have a system running Fedora Core 6 on a Dell PE4400 that crashed
and became unresponsive, I captured the following kernel oops in
/var/log/messages:
Apr 30 08:52:11 hostname kernel: list_del corruption. prev->next
should be
Hi Gary,
> I have a system running Fedora Core 6 on a Dell PE4400 that crashed
> and became unresponsive, I captured the following kernel oops in
> /var/log/messages:
>
> Apr 30 08:52:11 hostname kernel: list_del corruption. prev->next
> should be d5507478, but was 008f
> Apr 30 08:52:11
Hi Gary,
I have a system running Fedora Core 6 on a Dell PE4400 that crashed
and became unresponsive, I captured the following kernel oops in
/var/log/messages:
Apr 30 08:52:11 hostname kernel: list_del corruption. prev-next
should be d5507478, but was 008f
Apr 30 08:52:11 hostname
Hi Gary,
On 03/05/07, Gary Martin [EMAIL PROTECTED] wrote:
I have a system running Fedora Core 6 on a Dell PE4400 that crashed
and became unresponsive, I captured the following kernel oops in
/var/log/messages:
Apr 30 08:52:11 hostname kernel: list_del corruption. prev-next
should be d5507478,
Thanks.
On 5/3/07, Michal Piotrowski [EMAIL PROTECTED] wrote:
Hi Gary,
On 03/05/07, Gary Martin [EMAIL PROTECTED] wrote:
I have a system running Fedora Core 6 on a Dell PE4400 that crashed
and became unresponsive, I captured the following kernel oops in
/var/log/messages:
Apr 30 08:52:11
Ross Alexander wrote:
[warning: all of the below is just generic bug triage, I have no idea what
is really wrong]
Call Trace:
run_timer_softirq+0x156/0x1ac
__do_softirq+0x50/0xbb
call_softirq+0x1c/02x8
do_softieq+0x2f/x097
irq_exit+0x3d/0x4f
smp_apic_timer_interrupt+0x46/0x58
Hello,
I have repeated the cdda2wav run without the nvidia module and I get a
very similar kernel oops. I have to hand copy the oops so it could well
contain errors. If somebody can tell me exactly what information they
require it would be helpful.I have run this a number of times and
Hello,
I have repeated the cdda2wav run without the nvidia module and I get a
very similar kernel oops. I have to hand copy the oops so it could well
contain errors. If somebody can tell me exactly what information they
require it would be helpful.I have run this a number of times and
Ross Alexander wrote:
[warning: all of the below is just generic bug triage, I have no idea what
is really wrong]
Call Trace:
run_timer_softirq+0x156/0x1ac
__do_softirq+0x50/0xbb
call_softirq+0x1c/02x8
do_softieq+0x2f/x097
irq_exit+0x3d/0x4f
smp_apic_timer_interrupt+0x46/0x58
Ross Alexander wrote:
Modules linked in: nvidia(P)
Tainted:P
With this, nobody will even look at your report. Please retry without
proprietary modules.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info
Ross Alexander wrote:
Modules linked in: nvidia(P)
Tainted:P
With this, nobody will even look at your report. Please retry without
proprietary modules.
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at
On Sat, 2007-04-07 at 19:47 -0700, Randy Dunlap wrote:
> On Sat, 07 Apr 2007 19:21:01 -0500 Larry Finger wrote:
>
> > With the following line in /etc/modprobe.conf.local:
> >
> > options bcm43xx fwpostfix = ".fw3" locale=8
> >
> > the kernel oops below is generated. I realize that the line
On Sat, 2007-04-07 at 19:47 -0700, Randy Dunlap wrote:
On Sat, 07 Apr 2007 19:21:01 -0500 Larry Finger wrote:
With the following line in /etc/modprobe.conf.local:
options bcm43xx fwpostfix = .fw3 locale=8
the kernel oops below is generated. I realize that the line should have no
Randy Dunlap wrote:
On Sat, 07 Apr 2007 19:21:01 -0500 Larry Finger wrote:
With the following line in /etc/modprobe.conf.local:
options bcm43xx fwpostfix = ".fw3" locale=8
the kernel oops below is generated. I realize that the line should have no whitespace around the
"=", but I do not feel
On Sat, 07 Apr 2007 19:21:01 -0500 Larry Finger wrote:
> With the following line in /etc/modprobe.conf.local:
>
> options bcm43xx fwpostfix = ".fw3" locale=8
>
> the kernel oops below is generated. I realize that the line should have no
> whitespace around the
> "=", but I do not feel that an
On Sat, 07 Apr 2007 19:21:01 -0500 Larry Finger wrote:
With the following line in /etc/modprobe.conf.local:
options bcm43xx fwpostfix = .fw3 locale=8
the kernel oops below is generated. I realize that the line should have no
whitespace around the
=, but I do not feel that an oops is
Randy Dunlap wrote:
On Sat, 07 Apr 2007 19:21:01 -0500 Larry Finger wrote:
With the following line in /etc/modprobe.conf.local:
options bcm43xx fwpostfix = .fw3 locale=8
the kernel oops below is generated. I realize that the line should have no whitespace around the
=, but I do not feel
Hello Adrian,
reverting d9a7ecacac5f8274d2afce09aadcf37bdb42b93a does help.
thanks !
On Mon, 2007-03-19 at 17:34 +0100, Adrian Bunk wrote:
> On Mon, Mar 19, 2007 at 05:27:58PM +0200, Zilvinas Valinskas wrote:
> > Hello,
> >
> > Before 2.6.21-rc4 (vanilla) serial was oopsing if I pull
Hello Adrian,
reverting d9a7ecacac5f8274d2afce09aadcf37bdb42b93a does help.
thanks !
On Mon, 2007-03-19 at 17:34 +0100, Adrian Bunk wrote:
On Mon, Mar 19, 2007 at 05:27:58PM +0200, Zilvinas Valinskas wrote:
Hello,
Before 2.6.21-rc4 (vanilla) serial was oopsing if I pull usb-serial
On Mon, Mar 19, 2007 at 05:27:58PM +0200, Zilvinas Valinskas wrote:
> Hello,
>
> Before 2.6.21-rc4 (vanilla) serial was oopsing if I pull usb-serial
> cable while minicom was running. Now it doesn't matter if minicom is
> running or minicom closed, pulling serial cable results in such oops.
>...
On Mon, Mar 19, 2007 at 05:27:58PM +0200, Zilvinas Valinskas wrote:
Hello,
Before 2.6.21-rc4 (vanilla) serial was oopsing if I pull usb-serial
cable while minicom was running. Now it doesn't matter if minicom is
running or minicom closed, pulling serial cable results in such oops.
...
Does
On Thu, 2007-03-01 at 16:08 -0800, Bill Irwin wrote:
>> Looks like I should grab these testcases for the sake of due diligence
>> (not to say I intend to alter maintenance style from primarily review,
>> approval, and bugfixing, not that I've been doing as much of any of those
>> as I should). To
On Thu, 2007-03-01 at 16:08 -0800, Bill Irwin wrote:
> On Wed, Feb 28, 2007 at 02:13:29PM -0600, Adam Litke wrote:
> > Hey. While testing 2.6.21-rc2 with libhugetlbfs, the shm-fork test case
> > causes the kernel to oops. To reproduce: Execute 'make check' in the
> > latest libhugetlbfs source
On Thu, 2007-03-01 at 16:08 -0800, Bill Irwin wrote:
On Wed, Feb 28, 2007 at 02:13:29PM -0600, Adam Litke wrote:
Hey. While testing 2.6.21-rc2 with libhugetlbfs, the shm-fork test case
causes the kernel to oops. To reproduce: Execute 'make check' in the
latest libhugetlbfs source on a
On Thu, 2007-03-01 at 16:08 -0800, Bill Irwin wrote:
Looks like I should grab these testcases for the sake of due diligence
(not to say I intend to alter maintenance style from primarily review,
approval, and bugfixing, not that I've been doing as much of any of those
as I should). To which
On Wed, Feb 28, 2007 at 02:13:29PM -0600, Adam Litke wrote:
> Hey. While testing 2.6.21-rc2 with libhugetlbfs, the shm-fork test case
> causes the kernel to oops. To reproduce: Execute 'make check' in the
> latest libhugetlbfs source on a 2.6.21-rc2 kernel with 100 huge pages
> allocated.
On Wed, Feb 28, 2007 at 02:13:29PM -0600, Adam Litke wrote:
Hey. While testing 2.6.21-rc2 with libhugetlbfs, the shm-fork test case
causes the kernel to oops. To reproduce: Execute 'make check' in the
latest libhugetlbfs source on a 2.6.21-rc2 kernel with 100 huge pages
allocated. Using
Adam Litke <[EMAIL PROTECTED]> writes:
> Hey. While testing 2.6.21-rc2 with libhugetlbfs, the shm-fork test case
> causes the kernel to oops. To reproduce: Execute 'make check' in the
> latest libhugetlbfs source on a 2.6.21-rc2 kernel with 100 huge pages
> allocated. Using fewer huge pages
Adam Litke [EMAIL PROTECTED] writes:
Hey. While testing 2.6.21-rc2 with libhugetlbfs, the shm-fork test case
causes the kernel to oops. To reproduce: Execute 'make check' in the
latest libhugetlbfs source on a 2.6.21-rc2 kernel with 100 huge pages
allocated. Using fewer huge pages will
>
> Update: I think that you can ignore this error. I am getting
> segmentation faults when I attempt to rebuild the kernel. This is
> exactly the same problem I had with slackware 10.1 with the 2.6.10
> kernel. So I think it is a hardware issue. Memtest86 didn't show any
> errors after 35 passes,
Update: I think that you can ignore this error. I am getting
segmentation faults when I attempt to rebuild the kernel. This is
exactly the same problem I had with slackware 10.1 with the 2.6.10
kernel. So I think it is a hardware issue. Memtest86 didn't show any
errors after 35 passes, so I'll
Update: I think that you can ignore this error. I am getting
segmentation faults when I attempt to rebuild the kernel. This is
exactly the same problem I had with slackware 10.1 with the 2.6.10
kernel. So I think it is a hardware issue. Memtest86 didn't show any
errors after 35 passes, so I'll
Update: I think that you can ignore this error. I am getting
segmentation faults when I attempt to rebuild the kernel. This is
exactly the same problem I had with slackware 10.1 with the 2.6.10
kernel. So I think it is a hardware issue. Memtest86 didn't show any
errors after 35 passes, so
Here is the full dmesg log of the crash:
iret exception: [#1]
SMP
Modules linked in: ppdev lp button ac battery ipv6 dm_snapshot
dm_mirror dm_mod loop tsdev rtc psmouse parport_pc parport floppy
serio_raw pcspkr i2c_nforce2 snd_intel8x0 snd_ac97_codec snd_
ac97_bus snd_pcm snd_timer snd
Here is the full dmesg log of the crash:
iret exception: [#1]
SMP
Modules linked in: ppdev lp button ac battery ipv6 dm_snapshot
dm_mirror dm_mod loop tsdev rtc psmouse parport_pc parport floppy
serio_raw pcspkr i2c_nforce2 snd_intel8x0 snd_ac97_codec snd_
ac97_bus snd_pcm snd_timer snd
> Modules linked in: nvidia(P) snd_pcm_oss snd_mixer_oss
> CPU:1
> EIP:0060:[]Tainted: P VLI
does this happen only Linux code in the kernel? (eg without binary
drivers)
Greetings,
Arjan van de Ven
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
Modules linked in: nvidia(P) snd_pcm_oss snd_mixer_oss
CPU:1
EIP:0060:[c014dda9]Tainted: P VLI
does this happen only Linux code in the kernel? (eg without binary
drivers)
Greetings,
Arjan van de Ven
-
To unsubscribe from this list: send the line unsubscribe linux-kernel
No, it doesn't.
Is that something that should help? Now that the error has occurred
once, it occurred again within 24 hours.
Thanks,
Kristina
On 8/18/05, Nathan Scott <[EMAIL PROTECTED]> wrote:
> On Thu, Aug 18, 2005 at 06:49:05PM +, kristina clair wrote:
> > I've just come across this
No, it doesn't.
Is that something that should help? Now that the error has occurred
once, it occurred again within 24 hours.
Thanks,
Kristina
On 8/18/05, Nathan Scott [EMAIL PROTECTED] wrote:
On Thu, Aug 18, 2005 at 06:49:05PM +, kristina clair wrote:
I've just come across this oops.
On Thu, Aug 18, 2005 at 06:49:05PM +, kristina clair wrote:
> I've just come across this oops. We're running gentoo with a 2.6.11
> kernel, xfs + nfs + lvm (+hardware raid).
Check whether your kernel has this fix included:
I've just come across this oops. We're running gentoo with a 2.6.11
kernel, xfs + nfs + lvm (+hardware raid).
nfsd was not responding, and the load was at 27. the machine was
responsive, other than nfsd. everything had been responsive for at
least 9 months previous to this.
It seems like from
I've just come across this oops. We're running gentoo with a 2.6.11
kernel, xfs + nfs + lvm (+hardware raid).
nfsd was not responding, and the load was at 27. the machine was
responsive, other than nfsd. everything had been responsive for at
least 9 months previous to this.
It seems like from
On Thu, Aug 18, 2005 at 06:49:05PM +, kristina clair wrote:
I've just come across this oops. We're running gentoo with a 2.6.11
kernel, xfs + nfs + lvm (+hardware raid).
Check whether your kernel has this fix included:
Francois Pepin <[EMAIL PROTECTED]> writes:
> Hi,
>
> I am getting pseudo-random kernel oops on my Opteron box (Tyan Thunder
> K8W) with 4Gb RAM. I am running RedHad FC3 with kernel
> 2.6.11-1.35_FC3smp.
>
> It runs well with default BIOS settings, but only 3.5Gb RAM are visible.
> Using the
Francois Pepin [EMAIL PROTECTED] writes:
Hi,
I am getting pseudo-random kernel oops on my Opteron box (Tyan Thunder
K8W) with 4Gb RAM. I am running RedHad FC3 with kernel
2.6.11-1.35_FC3smp.
It runs well with default BIOS settings, but only 3.5Gb RAM are visible.
Using the Software
Hello,
just some basic questions :
- did your configuration change before the oopses started ? (eg: new
matches, etc...)
- did the traffic change recently (protocols, data rate) ? eg: new
applications on the network, etc...
- is it possible that it's being targetted by an attack
Hello,
just some basic questions :
- did your configuration change before the oopses started ? (eg: new
matches, etc...)
- did the traffic change recently (protocols, data rate) ? eg: new
applications on the network, etc...
- is it possible that it's being targetted by an attack
ael J. Wysocki" <[EMAIL PROTECTED]>
To: "Jon Schindler" <[EMAIL PROTECTED]>
CC: linux-kernel@vger.kernel.org
Subject: Re: Kernel Oops with dual core athlon 64 (quick question)
Date: Thu, 7 Jul 2005 21:04:25 +0200
Hi,
On Thursday, 7 of July 2005 18:41, Jon Schindle
Hi,
On Thursday, 7 of July 2005 18:41, Jon Schindler wrote:
> Hi Rafael,
> I looked at the patch and noticed that it's changing a file inside
> linux-2.6.12-rc6/arch/i386/kernel/cpu/cpufreq/powernow-k8.c
> So, basically, it's modifying the powernow driver in the i386 arch
> directory, but
Cc:
Sent: Thursday, July 07, 2005 4:29 AM
Subject: Re: Kernel Oops with dual core athlon 64
Hi,
On Thursday, 7 of July 2005 07:58, Jon Schindler wrote:
The dmesg is below. After I get this Oops, I am unable to use my (PS/2)
keyboard, and had to ssh to my machine in order to save a copy of dmes
Thanks, I'll recompile tonight and let you know if I still experience any
issues.
Jon
- Original Message -
From: "Rafael J. Wysocki" <[EMAIL PROTECTED]>
To: "Jon Schindler" <[EMAIL PROTECTED]>
Cc:
Sent: Thursday, July 07, 2005 4:29 AM
Subject: Re: Kern
Hi,
On Thursday, 7 of July 2005 07:58, Jon Schindler wrote:
> The dmesg is below. After I get this Oops, I am unable to use my (PS/2)
> keyboard, and had to ssh to my machine in order to save a copy of dmesg
> before rebooting the machine. I've seen a couple of other users of dual
> core
Hi,
On Thursday, 7 of July 2005 07:58, Jon Schindler wrote:
The dmesg is below. After I get this Oops, I am unable to use my (PS/2)
keyboard, and had to ssh to my machine in order to save a copy of dmesg
before rebooting the machine. I've seen a couple of other users of dual
core
201 - 300 of 402 matches
Mail list logo
