Hi there!
I am on a core i7 system bl67 intel board and it all keeps oopsing on
me. On 3.2.33 I get on 3.6.6 I get rcu errors (though rcu stress test
didn't show anything) or traces that include cpuidle / apic.
Does anyone have an idea what that could be? The system is just running
a plain
Hi there!
I am on a core i7 system bl67 intel board and it all keeps oopsing on
me. On 3.2.33 I get on 3.6.6 I get rcu errors (though rcu stress test
didn't show anything) or traces that include cpuidle / apic.
Does anyone have an idea what that could be? The system is just running
a plain
Hi,
since kernel version >= 3.4 wireless became extremely slow (download
rates of about 90k/sec when downloading a new kernel from kernel.org
instead of >1MB/s)https://bbs.archlinux.org/viewtopic.php?pid=1146085
There is a thread on archlinux
https://bbs.archlinux.org/viewtopic.php?pid=1146085
Hi,
since kernel version = 3.4 wireless became extremely slow (download
rates of about 90k/sec when downloading a new kernel from kernel.org
instead of 1MB/s)https://bbs.archlinux.org/viewtopic.php?pid=1146085
There is a thread on archlinux
https://bbs.archlinux.org/viewtopic.php?pid=1146085
Happens on an intel dh67bl - config attached, I would happily report
more details / try out things.
[ cut here ]
kernel BUG at mm/slab.c:3073!
invalid opcode: [#1] PREEMPT SMP
CPU 1
Modules linked in:
Pid: 570, comm: kswapd0 Not tainted 3.4.4 #1
Happens on an intel dh67bl - config attached, I would happily report
more details / try out things.
[ cut here ]
kernel BUG at mm/slab.c:3073!
invalid opcode: [#1] PREEMPT SMP
CPU 1
Modules linked in:
Pid: 570, comm: kswapd0 Not tainted 3.4.4 #1
Hi,
there seems to be some weird interaction between the latest (git
current!) linux kernel and recent chrome/chromium releases (>= 2X.X).
Basically chrome fails to open various web sites like https://github.com
just hanging (waiting). This problem is not there with older kernel
version (e.g.
Hi,
there seems to be some weird interaction between the latest (git
current!) linux kernel and recent chrome/chromium releases (= 2X.X).
Basically chrome fails to open various web sites like https://github.com
just hanging (waiting). This problem is not there with older kernel
version (e.g.
On Sun, 2008-02-24 at 12:18 +0100, Rafael J. Wysocki wrote:
> On Sunday, 24 of February 2008, Soeren Sonnenburg wrote:
> > On Sat, 2008-02-23 at 20:00 +0100, Oliver Pinter wrote:
> > > the pci=nommconf kernel parameter helped it?
> >
> > yes indeed, this swit
On Sun, 2008-02-24 at 12:18 +0100, Rafael J. Wysocki wrote:
On Sunday, 24 of February 2008, Soeren Sonnenburg wrote:
On Sat, 2008-02-23 at 20:00 +0100, Oliver Pinter wrote:
the pci=nommconf kernel parameter helped it?
yes indeed, this switch reliably helps to over come the hang
dle: using governor ladder
note that I've never seen these hangs on 2.6.24* ...
Soeren
> On 2/23/08, Soeren Sonnenburg <[EMAIL PROTECTED]> wrote:
> > Hi,
> >
> > trying out newest git, I see a hang with
> > ACPI: SSDT 7feb9c10, 02ae (r1 APPLE CPU0Ist 3000 intl 200
Hi,
trying out newest git, I see a hang with
ACPI: SSDT 7feb9c10, 02ae (r1 APPLE CPU0Ist 3000 intl 20050309)
ACPI: SSDT 7feb9910, 02c3 (r1 APPLE CPU0Cst 3001 intl 20050309)
...
ACPI: Processor [CPU0] (supports 8 throttling states)
ACPI: SSDT 7feb9f10, 0087 (r1 APPLE CPU1Ist 3000 intl 20050309)
Hi,
trying out newest git, I see a hang with
ACPI: SSDT 7feb9c10, 02ae (r1 APPLE CPU0Ist 3000 intl 20050309)
ACPI: SSDT 7feb9910, 02c3 (r1 APPLE CPU0Cst 3001 intl 20050309)
...
ACPI: Processor [CPU0] (supports 8 throttling states)
ACPI: SSDT 7feb9f10, 0087 (r1 APPLE CPU1Ist 3000 intl 20050309)
: using governor ladder
note that I've never seen these hangs on 2.6.24* ...
Soeren
On 2/23/08, Soeren Sonnenburg [EMAIL PROTECTED] wrote:
Hi,
trying out newest git, I see a hang with
ACPI: SSDT 7feb9c10, 02ae (r1 APPLE CPU0Ist 3000 intl 20050309)
ACPI: SSDT 7feb9910, 02c3 (r1 APPLE
compiling with
make CONFIG_DEBUG_SECTION_MISMATCH=y
I see the following warnings:
CC kernel/stacktrace.o
CC kernel/irq/handle.o
LD mm/built-in.o
WARNING: mm/built-in.o(.meminit.text+0x89e): Section mismatch in reference from
the function free_area_init_core() to the
On Fri, 2008-02-22 at 16:56 +0100, Rafael J. Wysocki wrote:
> On Friday, 22 of February 2008, Soeren Sonnenburg wrote:
> > On Fri, 2008-02-22 at 00:06 +0100, Rafael J. Wysocki wrote:
> > > On Thursday, 21 of February 2008, Soeren Sonnenburg wrote:
> > > > On Thu, 200
On Fri, 2008-02-22 at 16:56 +0100, Rafael J. Wysocki wrote:
On Friday, 22 of February 2008, Soeren Sonnenburg wrote:
On Fri, 2008-02-22 at 00:06 +0100, Rafael J. Wysocki wrote:
On Thursday, 21 of February 2008, Soeren Sonnenburg wrote:
On Thu, 2008-02-21 at 01:31 +0100, Rafael J
compiling with
make CONFIG_DEBUG_SECTION_MISMATCH=y
I see the following warnings:
CC kernel/stacktrace.o
CC kernel/irq/handle.o
LD mm/built-in.o
WARNING: mm/built-in.o(.meminit.text+0x89e): Section mismatch in reference from
the function free_area_init_core() to the
On Fri, 2008-02-22 at 00:06 +0100, Rafael J. Wysocki wrote:
> On Thursday, 21 of February 2008, Soeren Sonnenburg wrote:
> > On Thu, 2008-02-21 at 01:31 +0100, Rafael J. Wysocki wrote:
> > > On Wednesday, 20 of February 2008, Soeren Sonnenburg wrote:
> > > > On
On Thu, 2008-02-21 at 01:31 +0100, Rafael J. Wysocki wrote:
> On Wednesday, 20 of February 2008, Soeren Sonnenburg wrote:
> > On Wed, 2008-02-20 at 00:50 +0100, Rafael J. Wysocki wrote:
> > > On Tuesday, 19 of February 2008, Soeren Sonnenburg wrote:
> > > > On
On Thu, 2008-02-21 at 01:31 +0100, Rafael J. Wysocki wrote:
On Wednesday, 20 of February 2008, Soeren Sonnenburg wrote:
On Wed, 2008-02-20 at 00:50 +0100, Rafael J. Wysocki wrote:
On Tuesday, 19 of February 2008, Soeren Sonnenburg wrote:
On Tue, 2008-02-19 at 22:06 +0100, Rafael J
On Fri, 2008-02-22 at 00:06 +0100, Rafael J. Wysocki wrote:
On Thursday, 21 of February 2008, Soeren Sonnenburg wrote:
On Thu, 2008-02-21 at 01:31 +0100, Rafael J. Wysocki wrote:
On Wednesday, 20 of February 2008, Soeren Sonnenburg wrote:
On Wed, 2008-02-20 at 00:50 +0100, Rafael J
On Wed, 2008-02-20 at 00:50 +0100, Rafael J. Wysocki wrote:
> On Tuesday, 19 of February 2008, Soeren Sonnenburg wrote:
> > On Tue, 2008-02-19 at 22:06 +0100, Rafael J. Wysocki wrote:
> > > On Tuesday, 19 of February 2008, Soeren Sonnenburg wrote:
> > > > Hi,
> &g
On Tue, 2008-02-19 at 22:06 +0100, Rafael J. Wysocki wrote:
> On Tuesday, 19 of February 2008, Soeren Sonnenburg wrote:
> > Hi,
>
> Hi,
>
> > since 2.6.25-rc1 (first version I tried) and still in rc2 (and git), I
> > see a hang on s2ram already when trying
Hi,
since 2.6.25-rc1 (first version I tried) and still in rc2 (and git), I
see a hang on s2ram already when trying to suspend.
This is on a macbookpro 1,1 - which steps should I do next to help
isolating the problem?
Soeren
--
To unsubscribe from this list: send the line "unsubscribe
Hi,
since 2.6.25-rc1 (first version I tried) and still in rc2 (and git), I
see a hang on s2ram already when trying to suspend.
This is on a macbookpro 1,1 - which steps should I do next to help
isolating the problem?
Soeren
--
To unsubscribe from this list: send the line unsubscribe
On Tue, 2008-02-19 at 22:06 +0100, Rafael J. Wysocki wrote:
On Tuesday, 19 of February 2008, Soeren Sonnenburg wrote:
Hi,
Hi,
since 2.6.25-rc1 (first version I tried) and still in rc2 (and git), I
see a hang on s2ram already when trying to suspend.
Does it work with 2.6.24?
yes
On Wed, 2008-02-20 at 00:50 +0100, Rafael J. Wysocki wrote:
On Tuesday, 19 of February 2008, Soeren Sonnenburg wrote:
On Tue, 2008-02-19 at 22:06 +0100, Rafael J. Wysocki wrote:
On Tuesday, 19 of February 2008, Soeren Sonnenburg wrote:
Hi,
Hi,
since 2.6.25-rc1 (first
On Tue, 2008-01-22 at 22:44 -0800, David Miller wrote:
> From: Soeren Sonnenburg <[EMAIL PROTECTED]>
> Date: Wed, 23 Jan 2008 07:42:21 +0100
>
> > Dear all,
> >
> > since some 2.6.24rc version I suddenly experience such messages on
> > console w
On Tue, 2008-01-22 at 22:44 -0800, David Miller wrote:
> From: Soeren Sonnenburg <[EMAIL PROTECTED]>
> Date: Wed, 23 Jan 2008 07:42:21 +0100
>
> > Dear all,
> >
> > since some 2.6.24rc version I suddenly experience such messages on
> > console w
Dear all,
since some 2.6.24rc version I suddenly experience such messages on
console when trying to shutdown a vpn connection:
unregister_netdevice: waiting for tun0 to become free. Usage count = 1
or when removing an usb wlan dongle (although it was ifconfig wlan0
down'd before)
Dear all,
since some 2.6.24rc version I suddenly experience such messages on
console when trying to shutdown a vpn connection:
unregister_netdevice: waiting for tun0 to become free. Usage count = 1
or when removing an usb wlan dongle (although it was ifconfig wlan0
down'd before)
On Tue, 2008-01-22 at 22:44 -0800, David Miller wrote:
From: Soeren Sonnenburg [EMAIL PROTECTED]
Date: Wed, 23 Jan 2008 07:42:21 +0100
Dear all,
since some 2.6.24rc version I suddenly experience such messages on
console when trying to shutdown a vpn connection
On Sat, 2008-01-19 at 22:00 -0600, Eric Sandeen wrote:
> Soeren Sonnenburg wrote:
> > Dear all,
> >
> > I've just got this oops (causing the machine to hang finally)...
> >
> > Any ideas?
> > Soeren
>
> I've seen an awful lot of oopses out there
On Sat, 2008-01-19 at 22:00 -0600, Eric Sandeen wrote:
Soeren Sonnenburg wrote:
Dear all,
I've just got this oops (causing the machine to hang finally)...
Any ideas?
Soeren
I've seen an awful lot of oopses out there on this path,
kswapd-shrink_icache_memory; some get a little
Dear all,
I've just got this oops (causing the machine to hang finally)...
Any ideas?
Soeren
BUG: unable to handle kernel paging request at virtual address 66e88e66
printing eip: c01fac85 *pde =
Oops: 0002 [#1] PREEMPT SMP
Modules linked in: hci_usb hidp rfcomm l2cap bluetooth tun
Dear all,
I've just got this oops (causing the machine to hang finally)...
Any ideas?
Soeren
BUG: unable to handle kernel paging request at virtual address 66e88e66
printing eip: c01fac85 *pde =
Oops: 0002 [#1] PREEMPT SMP
Modules linked in: hci_usb hidp rfcomm l2cap bluetooth tun
On Wed, 2007-12-12 at 17:08 +0100, Marcel Holtmann wrote:
> Hi Oliver,
>
> > > I noticed that on my macbook pro1,1 the bluetooth device is gone after
> > > suspend to ram, i.e.
> >
> > Is this a regression?
> > Does it work if you unload hci_usb before you suspend?
> > If so, please recompile
On Wed, 2007-12-12 at 00:20 -0500, Shane wrote:
> In 2.6.24-rc5+, I hit this problem with videobuf_read_start
> not being exported. Patch attached, only compile tested.
>
> CHK include/linux/version.h
> CHK include/linux/utsrelease.h
> CALLscripts/checksyscalls.sh
> CHK
Dear all,
I noticed that on my macbook pro1,1 the bluetooth device is gone after
suspend to ram, i.e.
/usr/sbin/hciconfig -a
normally lists hci0:Type: USB ...
but after suspend does nothing.
Here it does not help to remove the modules and to reload them. Also the
driver reloads without
Dear all,
I noticed that on my macbook pro1,1 the bluetooth device is gone after
suspend to ram, i.e.
/usr/sbin/hciconfig -a
normally lists hci0:Type: USB ...
but after suspend does nothing.
Here it does not help to remove the modules and to reload them. Also the
driver reloads without
On Wed, 2007-12-12 at 00:20 -0500, Shane wrote:
In 2.6.24-rc5+, I hit this problem with videobuf_read_start
not being exported. Patch attached, only compile tested.
CHK include/linux/version.h
CHK include/linux/utsrelease.h
CALLscripts/checksyscalls.sh
CHK
On Wed, 2007-12-12 at 17:08 +0100, Marcel Holtmann wrote:
Hi Oliver,
I noticed that on my macbook pro1,1 the bluetooth device is gone after
suspend to ram, i.e.
Is this a regression?
Does it work if you unload hci_usb before you suspend?
If so, please recompile with
On Tue, 2007-11-06 at 15:52 +0100, Jiri Kosina wrote:
> On Tue, 6 Nov 2007, Dmitry Torokhov wrote:
>
> > Could you please try sticking a printk in
> > hidinput_disconnect(drivers/hid/hid-input.c) to verify that
> > input_unregister_device is in fact being called?
>
> Also, is 2.6.23 the only
On Tue, 2007-11-06 at 15:52 +0100, Jiri Kosina wrote:
On Tue, 6 Nov 2007, Dmitry Torokhov wrote:
Could you please try sticking a printk in
hidinput_disconnect(drivers/hid/hid-input.c) to verify that
input_unregister_device is in fact being called?
Also, is 2.6.23 the only kernel you
Dear all,
whenever I do a suspend resume cycle the input device's numbers are
increased until I finally run out of evdev devices. Is this a kernel
problem or some userspace program (udev/...) creating new devices all
the time?
here is the dmesg:
Soeren
input: Power Button (FF) as
Dear all,
whenever I do a suspend resume cycle the input device's numbers are
increased until I finally run out of evdev devices. Is this a kernel
problem or some userspace program (udev/...) creating new devices all
the time?
here is the dmesg:
Soeren
input: Power Button (FF) as
On Tue, 2007-10-23 at 17:08 +0900, Tejun Heo wrote:
> Jeff Garzik wrote:
> > Alan Cox wrote:
> >>> 2) Once we identified, over time, the set of drives affected by this
> >>> 3112 quirk (aka drives that didn't fully comply to SATA spec), the
> >>> debugging of corruption cases largely shifted to
On Tue, 2007-10-23 at 17:08 +0900, Tejun Heo wrote:
Jeff Garzik wrote:
Alan Cox wrote:
2) Once we identified, over time, the set of drives affected by this
3112 quirk (aka drives that didn't fully comply to SATA spec), the
debugging of corruption cases largely shifted to the standard
On Mon, 2007-10-22 at 12:59 +0200, Bernd Schubert wrote:
> On Monday 22 October 2007 12:36:32 Soeren Sonnenburg wrote:
> > On Mon, 2007-10-22 at 11:48 +0200, Bernd Schubert wrote:
> > > Hello,
> > >
> > > On Monday 22 October 2007 04
On Mon, 2007-10-22 at 12:59 +0200, Bernd Schubert wrote:
On Monday 22 October 2007 12:36:32 Soeren Sonnenburg wrote:
On Mon, 2007-10-22 at 11:48 +0200, Bernd Schubert wrote:
Hello,
On Monday 22 October 2007 04:12:44 Tejun Heo wrote:
Helo,
[...]
Now when I write large
On Mon, 2007-10-22 at 13:02 +0200, Bernd Schubert wrote:
> On Monday 22 October 2007 12:36:32 Soeren Sonnenburg wrote:
> > > but as much as it fits onto the disk. On reading back this file, the
> > > filesystem will report errors somewhere between 50GB and 230GB (dis
On Mon, 2007-10-22 at 11:48 +0200, Bernd Schubert wrote:
> Hello,
>
> On Monday 22 October 2007 04:12:44 Tejun Heo wrote:
> > Helo,
> > [...]
> > > Now when I write large files of zeros to root(sda) and read the file
> > > back in it contains a few nonzero entries:
> > >
> > > # dd if=/dev/zero
On Mon, 2007-10-22 at 11:48 +0200, Bernd Schubert wrote:
Hello,
On Monday 22 October 2007 04:12:44 Tejun Heo wrote:
Helo,
[...]
Now when I write large files of zeros to root(sdasdb) and read the file
back in it contains a few nonzero entries:
# dd if=/dev/zero of=/foo bs=1M
On Mon, 2007-10-22 at 13:02 +0200, Bernd Schubert wrote:
On Monday 22 October 2007 12:36:32 Soeren Sonnenburg wrote:
but as much as it fits onto the disk. On reading back this file, the
filesystem will report errors somewhere between 50GB and 230GB (disk size
is 250GB).
Wow, I really
On Mon, 2007-10-22 at 11:12 +0900, Tejun Heo wrote:
> Helo,
>
> Soeren Sonnenburg wrote:
> > I finally managed to find a *reproducible* setup and way to trigger
> > random corruptions using a sata sil 3114 controller connected to 4
> > seagate drives
> >
>
On Mon, 2007-10-22 at 11:12 +0900, Tejun Heo wrote:
Helo,
Soeren Sonnenburg wrote:
I finally managed to find a *reproducible* setup and way to trigger
random corruptions using a sata sil 3114 controller connected to 4
seagate drives
port 1: ST3400832AS sda
port 2: ST3400620AS sdb
Dear all,
I finally managed to find a *reproducible* setup and way to trigger
random corruptions using a sata sil 3114 controller connected to 4
seagate drives
port 1: ST3400832AS sda
port 2: ST3400620AS sdb
port 3: ST3750640AS sdc
port 4: ST3750640AS sdd
sda & sdb form md0 via a raid1 setup
Dear all,
I finally managed to find a *reproducible* setup and way to trigger
random corruptions using a sata sil 3114 controller connected to 4
seagate drives
port 1: ST3400832AS sda
port 2: ST3400620AS sdb
port 3: ST3750640AS sdc
port 4: ST3750640AS sdd
sda sdb form md0 via a raid1 setup
On Tue, 2007-10-09 at 15:09 +0200, Tomasz Chmielewski wrote:
> Soeren Sonnenburg wrote:
>
> >> Fixing recursive fault but reboot is needed!
> >
> > Hmmhh, so now I rebooted and again tried to
> >
> > $ make
> >
> > the new kernel which agai
On Tue, 2007-10-09 at 15:09 +0200, Tomasz Chmielewski wrote:
Soeren Sonnenburg wrote:
Fixing recursive fault but reboot is needed!
Hmmhh, so now I rebooted and again tried to
$ make
the new kernel which again triggered this(?) BUG:
I had a similar issue with 2.6.22.9
On Fri, 2007-09-14 at 07:22 +1000, Nick Piggin wrote:
> On Friday 14 September 2007 16:02, Soeren Sonnenburg wrote:
> > On Thu, 2007-09-13 at 09:51 +1000, Nick Piggin wrote:
> > > On Thursday 13 September 2007 19:20, Soeren Sonnenburg wrote:
> > > > Dear all,
On Fri, 2007-09-14 at 07:22 +1000, Nick Piggin wrote:
On Friday 14 September 2007 16:02, Soeren Sonnenburg wrote:
On Thu, 2007-09-13 at 09:51 +1000, Nick Piggin wrote:
On Thursday 13 September 2007 19:20, Soeren Sonnenburg wrote:
Dear all,
I've just seen this in dmesg on a AMD
On Mon, 2007-09-17 at 23:03 +0200, Thomas Gleixner wrote:
> On Mon, 2007-09-17 at 22:51 +0200, Arkadiusz Miskiewicz wrote:
> > > > clockevents: fix resume logic
> > >
> > > Linus pulled a series of patches which are addressing this issue into
> > > his tree yesterday. Can you please retest
On Mon, 2007-09-17 at 23:03 +0200, Thomas Gleixner wrote:
On Mon, 2007-09-17 at 22:51 +0200, Arkadiusz Miskiewicz wrote:
clockevents: fix resume logic
Linus pulled a series of patches which are addressing this issue into
his tree yesterday. Can you please retest against current
On Sun, 2007-09-16 at 18:15 +1000, Nick Piggin wrote:
> On Saturday 15 September 2007 20:22, Soeren Sonnenburg wrote:
> > On Sat, 2007-09-15 at 09:47 +0000, Soeren Sonnenburg wrote:
>
> > > Memtest did not find anything after 16 passes so I finally stopped
> it
> >
On Sun, 2007-09-16 at 18:15 +1000, Nick Piggin wrote:
On Saturday 15 September 2007 20:22, Soeren Sonnenburg wrote:
On Sat, 2007-09-15 at 09:47 +, Soeren Sonnenburg wrote:
Memtest did not find anything after 16 passes so I finally stopped
it
applied your patch and used
On Sat, 2007-09-15 at 09:47 +, Soeren Sonnenburg wrote:
> On Fri, 2007-09-14 at 07:22 +1000, Nick Piggin wrote:
> > On Friday 14 September 2007 16:02, Soeren Sonnenburg wrote:
> > > On Thu, 2007-09-13 at 09:51 +1000, Nick Piggin wrote:
> > > > On Thursday 1
On Fri, 2007-09-14 at 07:22 +1000, Nick Piggin wrote:
> On Friday 14 September 2007 16:02, Soeren Sonnenburg wrote:
> > On Thu, 2007-09-13 at 09:51 +1000, Nick Piggin wrote:
> > > On Thursday 13 September 2007 19:20, Soeren Sonnenburg wrote:
> > > > Dear all,
On Fri, 2007-09-14 at 07:22 +1000, Nick Piggin wrote:
On Friday 14 September 2007 16:02, Soeren Sonnenburg wrote:
On Thu, 2007-09-13 at 09:51 +1000, Nick Piggin wrote:
On Thursday 13 September 2007 19:20, Soeren Sonnenburg wrote:
Dear all,
I've just seen this in dmesg on a AMD K7
On Sat, 2007-09-15 at 09:47 +, Soeren Sonnenburg wrote:
On Fri, 2007-09-14 at 07:22 +1000, Nick Piggin wrote:
On Friday 14 September 2007 16:02, Soeren Sonnenburg wrote:
On Thu, 2007-09-13 at 09:51 +1000, Nick Piggin wrote:
On Thursday 13 September 2007 19:20, Soeren Sonnenburg wrote
On Thu, 2007-09-13 at 09:51 +1000, Nick Piggin wrote:
> On Thursday 13 September 2007 19:20, Soeren Sonnenburg wrote:
> > Dear all,
> >
> > I've just seen this in dmesg on a AMD K7 / kernel 2.6.22.6 machine
> > (config attached).
> >
> > Any ideas / which f
On Thu, 2007-09-13 at 09:51 +1000, Nick Piggin wrote:
On Thursday 13 September 2007 19:20, Soeren Sonnenburg wrote:
Dear all,
I've just seen this in dmesg on a AMD K7 / kernel 2.6.22.6 machine
(config attached).
Any ideas / which further information needed ?
Thanks for the report
Dear all,
I've just seen this in dmesg on a AMD K7 / kernel 2.6.22.6 machine
(config attached).
Any ideas / which further information needed ?
Soeren
[ cut here ]
kernel BUG at fs/locks.c:171!
invalid opcode: [#1]
Modules linked in: ipt_iprange ipt_REDIRECT capi
Dear all,
I've just seen this in dmesg on a AMD K7 / kernel 2.6.22.6 machine
(config attached).
Any ideas / which further information needed ?
Soeren
[ cut here ]
kernel BUG at fs/locks.c:171!
invalid opcode: [#1]
Modules linked in: ipt_iprange ipt_REDIRECT capi
On Wed, 2007-08-29 at 17:27 +0200, Michal Piotrowski wrote:
> Power management
>
> Subject : something broke resume from s2ram on mbp c1d (??? :))
> References : http://lkml.org/lkml/2007/8/28/67
> Last known good : 2.6.23-rc3
> Submitter : Soeren Sonnenburg
On Wed, 2007-08-29 at 17:27 +0200, Michal Piotrowski wrote:
Power management
Subject : something broke resume from s2ram on mbp c1d (??? :))
References : http://lkml.org/lkml/2007/8/28/67
Last known good : 2.6.23-rc3
Submitter : Soeren Sonnenburg [EMAIL PROTECTED
On Tue, 2007-08-28 at 12:33 +0200, Rafael J. Wysocki wrote:
> On Tuesday, 28 August 2007 12:09, Soeren Sonnenburg wrote:
[...]
> > I hope I find time to do a bisect soon...
>
> Is this a regression from 2.6.23-rc3, or from an earlier kernel?
it is a regression from rc3, all kern
On Mon, 2007-08-27 at 18:58 -0700, Linus Torvalds wrote:
> Ok, I lost it, and let two weeks pass between -rc releases. My bad.
>
> As a result, -rc4 is a bit bigger than it would/should have been, but
> hopefully it's all good, and we've fixed most regressions. There's some
> arch updates
On Mon, 2007-08-27 at 18:58 -0700, Linus Torvalds wrote:
Ok, I lost it, and let two weeks pass between -rc releases. My bad.
As a result, -rc4 is a bit bigger than it would/should have been, but
hopefully it's all good, and we've fixed most regressions. There's some
arch updates (MIPS,
On Tue, 2007-08-28 at 12:33 +0200, Rafael J. Wysocki wrote:
On Tuesday, 28 August 2007 12:09, Soeren Sonnenburg wrote:
[...]
I hope I find time to do a bisect soon...
Is this a regression from 2.6.23-rc3, or from an earlier kernel?
it is a regression from rc3, all kernels I tested up to 23
Dear all,
I suddenly got flodded with
Bad pte = e900b50d, process = ???, vm_flags = 100173, vaddr = bfc87ee2
[] vm_normal_page+0x3e/0x53
[] follow_page+0x90/0x147
[] get_user_pages+0x20f/0x261
[] access_process_vm+0x7e/0x163
[] vma_merge+0x171/0x17f
[] proc_pid_cmdline+0x57/0xe7
[]
Dear all,
I suddenly got flodded with
Bad pte = e900b50d, process = ???, vm_flags = 100173, vaddr = bfc87ee2
[c0146ae9] vm_normal_page+0x3e/0x53
[c0146f6a] follow_page+0x90/0x147
[c01483d3] get_user_pages+0x20f/0x261
[c0148e7c] access_process_vm+0x7e/0x163
[c014a8af] vma_merge+0x171/0x17f
On Wed, 2007-07-18 at 15:57 -0700, Andrew Morton wrote:
> On Tue, 17 Jul 2007 09:10:18 +0200
> Soeren Sonnenburg <[EMAIL PROTECTED]> wrote:
>
> > the attached minimally intrusive patch is based on Matthew Garret's
> > patch 'Make appletouch shut up when it has n
On Wed, 2007-07-18 at 15:57 -0700, Andrew Morton wrote:
On Tue, 17 Jul 2007 09:10:18 +0200
Soeren Sonnenburg [EMAIL PROTECTED] wrote:
the attached minimally intrusive patch is based on Matthew Garret's
patch 'Make appletouch shut up when it has nothing to say' patches (e.g.
http
On Tue, 2007-07-17 at 21:48 -0400, Dmitry Torokhov wrote:
> On Tuesday 17 July 2007 14:16, Soeren Sonnenburg wrote:
> > On Tue, 2007-07-17 at 11:01 -0400, Dmitry Torokhov wrote:
> [...]
> > > How many boxes did you try this patch on?
> >
> > Mine plus 1 other.
On Tue, 2007-07-17 at 11:01 -0400, Dmitry Torokhov wrote:
> Hi,
>
> On 7/17/07, Soeren Sonnenburg <[EMAIL PROTECTED]> wrote:
> >
> > err_free_buffer:
> > @@ -656,6 +699,7 @@ static void atp_disconnect(struct usb_interface *iface)
> >
> >usb_
On Tue, 2007-07-17 at 15:03 +0200, Johannes Berg wrote:
> Hi,
>
> Good stuff :)
>
> > + int idlecount; /* number of empty packets */
>
> should probably use tabs here.
fixed.
> > + size = usb_control_msg(udev, usb_sndctrlpipe(udev, 0),
> > +
for BTN_LEFT.
Matthew Garrett did the initial 'Make appletouch shut up when it has
nothing to say' so I am adding him to the signed-off lines (hope that is
the correct way).
Patch follows inline and attached.
Soeren.
Signed-off-by: Soeren Sonnenburg <[EMAIL PROTECTED]>
Signed-off-by: Matthew G
for BTN_LEFT.
Matthew Garrett did the initial 'Make appletouch shut up when it has
nothing to say' so I am adding him to the signed-off lines (hope that is
the correct way).
Patch follows inline and attached.
Soeren.
Signed-off-by: Soeren Sonnenburg [EMAIL PROTECTED]
Signed-off-by: Matthew Garrett
On Tue, 2007-07-17 at 15:03 +0200, Johannes Berg wrote:
Hi,
Good stuff :)
+ int idlecount; /* number of empty packets */
should probably use tabs here.
fixed.
+ size = usb_control_msg(udev, usb_sndctrlpipe(udev, 0),
+
On Tue, 2007-07-17 at 11:01 -0400, Dmitry Torokhov wrote:
Hi,
On 7/17/07, Soeren Sonnenburg [EMAIL PROTECTED] wrote:
err_free_buffer:
@@ -656,6 +699,7 @@ static void atp_disconnect(struct usb_interface *iface)
usb_set_intfdata(iface, NULL);
if (dev
On Tue, 2007-07-17 at 21:48 -0400, Dmitry Torokhov wrote:
On Tuesday 17 July 2007 14:16, Soeren Sonnenburg wrote:
On Tue, 2007-07-17 at 11:01 -0400, Dmitry Torokhov wrote:
[...]
How many boxes did you try this patch on?
Mine plus 1 other. However please note that Matthews patch has
On Thu, 2007-07-05 at 03:01 +0900, Tejun Heo wrote:
> Soeren Sonnenburg wrote:
> > On Tue, 2007-07-03 at 15:40 +0900, Tejun Heo wrote:
> >> Soeren Sonnenburg wrote:
> >>> Dear List,
> >>>
> >>> since the switch to
> >>>
On Tue, 2007-07-03 at 15:40 +0900, Tejun Heo wrote:
> Soeren Sonnenburg wrote:
> > Dear List,
> >
> > since the switch to
> >
> > CONFIG_ATA=y
> > CONFIG_ATA_ACPI=y
> > CONFIG_ATA_PIIX=y,
> >
> > the ATA_PIIX driver manages both, intern
On Tue, 2007-07-03 at 15:40 +0900, Tejun Heo wrote:
Soeren Sonnenburg wrote:
Dear List,
since the switch to
CONFIG_ATA=y
CONFIG_ATA_ACPI=y
CONFIG_ATA_PIIX=y,
the ATA_PIIX driver manages both, internal sata disk aswell as cd/dvd
rom. However I am being flooded
On Thu, 2007-07-05 at 03:01 +0900, Tejun Heo wrote:
Soeren Sonnenburg wrote:
On Tue, 2007-07-03 at 15:40 +0900, Tejun Heo wrote:
Soeren Sonnenburg wrote:
Dear List,
since the switch to
CONFIG_ATA=y
CONFIG_ATA_ACPI=y
CONFIG_ATA_PIIX=y,
the ATA_PIIX driver manages both
On Mon, 2007-06-25 at 20:20 +0200, Rudolf Marek wrote:
> > Hi Rudolf,
> >
> > just one more update:
> >
> > When I put my machine into s2ram and make it resume, one of the coretemp
> > sensors gets lost. Ahh and I am already rmmod coretemp / loading
> > microcode after resume / insmod
On Thu, 2007-06-21 at 22:57 +0200, Rudolf Marek wrote:
> Hello Soeren,
[...]
> Soeren pointed at some T60, T60p BIOS update and luckily, there is a
> easy way
> how to extract the microcode update and even convert it into the .txt
> format as
> microcode update utility
On Thu, 2007-06-21 at 22:57 +0200, Rudolf Marek wrote:
Hello Soeren,
[...]
Soeren pointed at some T60, T60p BIOS update and luckily, there is a
easy way
how to extract the microcode update and even convert it into the .txt
format as
microcode update utility
1 - 100 of 228 matches
Mail list logo
