On Tue, 13 Apr 2021, Mike Rapoport wrote:
>
> I think I've found the reason. trim_snb_memory() reserved the entire first
> megabyte very early leaving no room for real mode trampoline allocation.
> Since this reservation is needed only to make sure integrated gfx does not
> access some memory, it
On 4/13/21 11:23 AM, Mike Rapoport wrote:
> On Tue, Apr 13, 2021 at 10:34:25AM -0700, Randy Dunlap wrote:
>> On 4/13/21 9:58 AM, Mike Rapoport wrote:
>>
>> Mike,
>> That works.
>>
>> Please send the next test.
>
> I think I've found the reason. trim_snb_memory() reserved the entire first
> megaby
On Tue, Apr 13, 2021 at 10:34:25AM -0700, Randy Dunlap wrote:
> On 4/13/21 9:58 AM, Mike Rapoport wrote:
> > On Mon, Apr 12, 2021 at 11:21:48PM -0700, Randy Dunlap wrote:
> >> On 4/12/21 11:06 PM, Mike Rapoport wrote:
> >>> Hi Randy,
> >>>
> >>> On Mon, Apr 12, 2021 at 01:53:34PM -0700, Randy Dunla
On 4/13/21 9:58 AM, Mike Rapoport wrote:
> On Mon, Apr 12, 2021 at 11:21:48PM -0700, Randy Dunlap wrote:
>> On 4/12/21 11:06 PM, Mike Rapoport wrote:
>>> Hi Randy,
>>>
>>> On Mon, Apr 12, 2021 at 01:53:34PM -0700, Randy Dunlap wrote:
On 4/12/21 10:01 AM, Mike Rapoport wrote:
> On Mon, Apr
On Mon, Apr 12, 2021 at 11:21:48PM -0700, Randy Dunlap wrote:
> On 4/12/21 11:06 PM, Mike Rapoport wrote:
> > Hi Randy,
> >
> > On Mon, Apr 12, 2021 at 01:53:34PM -0700, Randy Dunlap wrote:
> >> On 4/12/21 10:01 AM, Mike Rapoport wrote:
> >>> On Mon, Apr 12, 2021 at 08:49:49AM -0700, Randy Dunlap
On 4/12/21 11:06 PM, Mike Rapoport wrote:
> Hi Randy,
>
> On Mon, Apr 12, 2021 at 01:53:34PM -0700, Randy Dunlap wrote:
>> On 4/12/21 10:01 AM, Mike Rapoport wrote:
>>> On Mon, Apr 12, 2021 at 08:49:49AM -0700, Randy Dunlap wrote:
>>>
>>> I thought about adding some prints to see what's causing
Hi Randy,
On Mon, Apr 12, 2021 at 01:53:34PM -0700, Randy Dunlap wrote:
> On 4/12/21 10:01 AM, Mike Rapoport wrote:
> > On Mon, Apr 12, 2021 at 08:49:49AM -0700, Randy Dunlap wrote:
> >
> > I thought about adding some prints to see what's causing the hang, the
> > reservations or their absence.
On 4/12/21 10:01 AM, Mike Rapoport wrote:
> On Mon, Apr 12, 2021 at 08:49:49AM -0700, Randy Dunlap wrote:
>> On 4/11/21 11:14 PM, Mike Rapoport wrote:
>>> Hi Randy,
>>>
>>> On Sun, Apr 11, 2021 at 07:41:37PM -0700, Randy Dunlap wrote:
On 4/9/21 4:51 AM, Stephen Rothwell wrote:
> Hi all,
>>
On Mon, Apr 12, 2021 at 08:49:49AM -0700, Randy Dunlap wrote:
> On 4/11/21 11:14 PM, Mike Rapoport wrote:
> > Hi Randy,
> >
> > On Sun, Apr 11, 2021 at 07:41:37PM -0700, Randy Dunlap wrote:
> >> On 4/9/21 4:51 AM, Stephen Rothwell wrote:
> >>> Hi all,
> >>>
> >>> Changes since 20210408:
> >>>
> >>
On 4/11/21 11:14 PM, Mike Rapoport wrote:
> Hi Randy,
>
> On Sun, Apr 11, 2021 at 07:41:37PM -0700, Randy Dunlap wrote:
>> On 4/9/21 4:51 AM, Stephen Rothwell wrote:
>>> Hi all,
>>>
>>> Changes since 20210408:
>>>
>>
>> Hi,
>>
>> I cannot boot linux-next 20210408 nor 20210409 on an antique
>> x86_
Hi Randy,
On Sun, Apr 11, 2021 at 07:41:37PM -0700, Randy Dunlap wrote:
> On 4/9/21 4:51 AM, Stephen Rothwell wrote:
> > Hi all,
> >
> > Changes since 20210408:
> >
>
> Hi,
>
> I cannot boot linux-next 20210408 nor 20210409 on an antique
> x86_64 laptop (Toshiba Portege).
>
> After many faile
On 4/9/21 4:51 AM, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20210408:
>
Hi,
I cannot boot linux-next 20210408 nor 20210409 on an antique
x86_64 laptop (Toshiba Portege).
After many failed tests, I finally resorted to git bisect,
which led me to:
git bisect start
# good: [e49d033bdd
On 4/9/21 4:51 AM, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20210408:
>
> New trees: iio, iio-fixes
>
on ia64: (not X86)
(from a 01.org kernel config file)
../drivers/iommu/intel/pasid.c: In function 'pasid_enable_wpe':
../drivers/iommu/intel/pasid.c:554:22: error: implicit declar
Hi all,
Changes since 20210408:
New trees: iio, iio-fixes
The arm-soc tree gained a build failure so I reverted some commits.
The bluetooth tree lost its build failure.
The drm tree gained a conflict against the drm-misc-fixes tree and also a
bad merge for which I applied a merge fix patch.
T
; Cc: Linux Kernel Mailing List ; Naga
> Sureshkumar Relli
> ; Michal Simek ; linux-spi s...@vger.kernel.org>
> Subject: Re: linux-next: Tree for Apr 9 (spi/spi-zynq-qspi.c)
>
> On 4/9/19 1:00 AM, Stephen Rothwell wrote:
> > Hi all,
> >
> > Changes since 20190
On Tue, 2019-04-09 at 11:25 -0700, Guenter Roeck wrote:
> On Tue, Apr 09, 2019 at 06:00:42PM +1000, Stephen Rothwell wrote:
> > Hi all,
> >
> > Changes since 20190408:
> >
> > The mac80211-next tree gained a conflict against the mac80211 tree.
> >
> > The drm tree still had its build failure for
On Tue, Apr 09, 2019 at 06:00:42PM +1000, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20190408:
>
> The mac80211-next tree gained a conflict against the mac80211 tree.
>
> The drm tree still had its build failure for which I disabled a driver.
>
> The drm-misc tree gained conflicts agai
On 4/9/19 1:00 AM, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20190408:
>
on x86_64:
# CONFIG_MODULES is not set
In file included from ../include/linux/kernel.h:11:0,
from ../arch/x86/platform/efi/efi_64.c:21:
../arch/x86/platform/efi/efi_64.c: In function ‘efi_sync_lo
Hi all,
Changes since 20190408:
The mac80211-next tree gained a conflict against the mac80211 tree.
The drm tree still had its build failure for which I disabled a driver.
The drm-misc tree gained conflicts against the drm tree and also a build
failure for which I marked a driver as BROKEN.
Th
Hi all,
Please do not add any v4.18 destined stuff to your linux-next included
trees until after v4.17-rc1 has been released.
Changes since 20180406:
The vfs tree lost its build failure.
The parisc-hd tree still had its build failure for which I applied a patch.
The nvdimm tree gained a build
Hi all,
Changes since 20150408:
The arm-soc tree still had its build failure for which I reverted a commit.
The regulator tree gained a build failure for which I applied a merge
fix patch.
The vhost tree gained a conflict against the usb tree.
Non-merge commits (relative to Linus' tree): 9398
Hi,
On 09/04/14 18:01, Randy Dunlap wrote:
> On 04/09/2014 12:22 AM, Stephen Rothwell wrote:
>> > Hi all,
>> >
>> > Please do not add material intended for v3.16 to your linux-next included
>> > branches until after v3.15-rc1 is released.
>> >
>> > This tree still fails (more than usual) the pow
Hi all,
Please do not add material intended for v3.16 to your linux-next included
branches until after v3.15-rc1 is released.
This tree still fails (more than usual) the powerpc allyesconfig build.
Changes since 20140408:
Dropped trees: akpm-current, akpm (too complex conflicts)
The powerpc tr
On Monday, April 22, 2013 08:44:30 AM Viresh Kumar wrote:
> On 22 April 2013 05:00, Rafael J. Wysocki wrote:
> > Applied to linux-pm.git/linux-next, although please check the result,
> > because
> > the patchwork version of the patch wasn't quite applicable and I fixed it up
> > manually.
>
> Ye
On 22 April 2013 05:00, Rafael J. Wysocki wrote:
> Applied to linux-pm.git/linux-next, although please check the result, because
> the patchwork version of the patch wasn't quite applicable and I fixed it up
> manually.
Yes it looks fine and that's why i have attached the patch with my
email earl
On Monday, April 15, 2013 10:52:28 PM Viresh Kumar wrote:
> On 15 April 2013 21:37, Dirk Brandewie wrote:
> > If the intel_pstate driver is being used __cpufreq_governor() should NOT be
> > called intel_pstate does not implement the target() callback.
> >
> > Nathan's commit 5800043b2 changed the
On Wednesday, April 17, 2013 04:04:46 PM Sedat Dilek wrote:
> On Mon, Apr 15, 2013 at 7:22 PM, Viresh Kumar wrote:
> > On 15 April 2013 21:37, Dirk Brandewie wrote:
> >> If the intel_pstate driver is being used __cpufreq_governor() should NOT be
> >> called intel_pstate does not implement the tar
On Mon, Apr 15, 2013 at 7:22 PM, Viresh Kumar wrote:
> On 15 April 2013 21:37, Dirk Brandewie wrote:
>> If the intel_pstate driver is being used __cpufreq_governor() should NOT be
>> called intel_pstate does not implement the target() callback.
>>
>> Nathan's commit 5800043b2 changed the fence ar
On Mon, Apr 15, 2013 at 7:57 PM, Sedat Dilek wrote:
> On Mon, Apr 15, 2013 at 7:51 PM, Sedat Dilek wrote:
>> On Mon, Apr 15, 2013 at 7:22 PM, Viresh Kumar
>> wrote:
>>> On 15 April 2013 21:37, Dirk Brandewie wrote:
If the intel_pstate driver is being used __cpufreq_governor() should NOT b
On 04/15/2013 12:42 PM, Dirk Brandewie wrote:
On 04/15/2013 10:27 AM, Nathan Zimmer wrote:
On 04/15/2013 11:07 AM, Dirk Brandewie wrote:
On 04/13/2013 02:55 AM, Sedat Dilek wrote:
On Sat, Apr 13, 2013 at 12:51 AM, Rafael J. Wysocki
wrote:
On Friday, April 12, 2013 11:08:37 PM Sedat Dilek wro
On 04/15/2013 10:51 AM, Sedat Dilek wrote:
On Mon, Apr 15, 2013 at 7:22 PM, Viresh Kumar wrote:
On 15 April 2013 21:37, Dirk Brandewie wrote:
If the intel_pstate driver is being used __cpufreq_governor() should NOT be
called intel_pstate does not implement the target() callback.
Nathan's com
On Mon, Apr 15, 2013 at 7:51 PM, Sedat Dilek wrote:
> On Mon, Apr 15, 2013 at 7:22 PM, Viresh Kumar wrote:
>> On 15 April 2013 21:37, Dirk Brandewie wrote:
>>> If the intel_pstate driver is being used __cpufreq_governor() should NOT be
>>> called intel_pstate does not implement the target() call
On 04/15/2013 10:27 AM, Nathan Zimmer wrote:
On 04/15/2013 11:07 AM, Dirk Brandewie wrote:
On 04/13/2013 02:55 AM, Sedat Dilek wrote:
On Sat, Apr 13, 2013 at 12:51 AM, Rafael J. Wysocki wrote:
On Friday, April 12, 2013 11:08:37 PM Sedat Dilek wrote:
On Fri, Apr 12, 2013 at 6:27 PM, Sedat Dil
On 04/15/2013 11:07 AM, Dirk Brandewie wrote:
On 04/13/2013 02:55 AM, Sedat Dilek wrote:
On Sat, Apr 13, 2013 at 12:51 AM, Rafael J. Wysocki wrote:
On Friday, April 12, 2013 11:08:37 PM Sedat Dilek wrote:
On Fri, Apr 12, 2013 at 6:27 PM, Sedat Dilek
wrote:
On Fri, Apr 12, 2013 at 5:45 PM, Se
On 15 April 2013 21:37, Dirk Brandewie wrote:
> If the intel_pstate driver is being used __cpufreq_governor() should NOT be
> called intel_pstate does not implement the target() callback.
>
> Nathan's commit 5800043b2 changed the fence around the call to
> __cpufreq_governor() in __cpufreq_remove_
On Mon, Apr 15, 2013 at 6:07 PM, Dirk Brandewie
wrote:
> On 04/13/2013 02:55 AM, Sedat Dilek wrote:
>>
>> On Sat, Apr 13, 2013 at 12:51 AM, Rafael J. Wysocki wrote:
>>>
>>> On Friday, April 12, 2013 11:08:37 PM Sedat Dilek wrote:
On Fri, Apr 12, 2013 at 6:27 PM, Sedat Dilek
wrote:
On 04/13/2013 02:55 AM, Sedat Dilek wrote:
On Sat, Apr 13, 2013 at 12:51 AM, Rafael J. Wysocki wrote:
On Friday, April 12, 2013 11:08:37 PM Sedat Dilek wrote:
On Fri, Apr 12, 2013 at 6:27 PM, Sedat Dilek wrote:
On Fri, Apr 12, 2013 at 5:45 PM, Sedat Dilek wrote:
On Fri, Apr 12, 2013 at 4:2
On Sat, Apr 13, 2013 at 12:51 AM, Rafael J. Wysocki wrote:
> On Friday, April 12, 2013 11:08:37 PM Sedat Dilek wrote:
>> On Fri, Apr 12, 2013 at 6:27 PM, Sedat Dilek wrote:
>> > On Fri, Apr 12, 2013 at 5:45 PM, Sedat Dilek wrote:
>> >> On Fri, Apr 12, 2013 at 4:24 PM, Sedat Dilek
>> >> wrote:
On Friday, April 12, 2013 11:08:37 PM Sedat Dilek wrote:
> On Fri, Apr 12, 2013 at 6:27 PM, Sedat Dilek wrote:
> > On Fri, Apr 12, 2013 at 5:45 PM, Sedat Dilek wrote:
> >> On Fri, Apr 12, 2013 at 4:24 PM, Sedat Dilek wrote:
> >>> On Fri, Apr 12, 2013 at 10:23 AM, Viresh Kumar
> >>> wrote:
> >>
On Fri, Apr 12, 2013 at 10:23 AM, Viresh Kumar wrote:
> On 10 April 2013 11:44, Sedat Dilek wrote:
>> I found this "[RFC PATCH] kbuild: Build linux-tools package with 'make
>> deb-pkg'" from February 2012.
>> Can't say what happened to it...
>
> Sedat,
>
> Sorry for being late. I am down with Fev
On 10 April 2013 11:44, Sedat Dilek wrote:
> I found this "[RFC PATCH] kbuild: Build linux-tools package with 'make
> deb-pkg'" from February 2012.
> Can't say what happened to it...
Sedat,
Sorry for being late. I am down with Fever and throat infection since few days.
Still struggling with it..
On Wed, Apr 10, 2013 at 7:53 AM, Sedat Dilek wrote:
> On Wed, Apr 10, 2013 at 7:41 AM, Sedat Dilek wrote:
>> On Tue, Apr 9, 2013 at 6:51 PM, Viresh Kumar wrote:
>>> On 9 April 2013 21:38, Sedat Dilek wrote:
With x=3 the system gets in an unuseable state.
root# echo 0 > /sys/
On Wed, Apr 10, 2013 at 7:41 AM, Sedat Dilek wrote:
> On Tue, Apr 9, 2013 at 6:51 PM, Viresh Kumar wrote:
>> On 9 April 2013 21:38, Sedat Dilek wrote:
>>> With x=3 the system gets in an unuseable state.
>>>
>>> root# echo 0 > /sys/devices/system/cpu/cpu3/online
>>>
>>> I could not write my
On Tue, Apr 9, 2013 at 6:51 PM, Viresh Kumar wrote:
> On 9 April 2013 21:38, Sedat Dilek wrote:
>> With x=3 the system gets in an unuseable state.
>>
>> root# echo 0 > /sys/devices/system/cpu/cpu3/online
>>
>> I could not write my reply and had to do a hard/cold reboot.
>> The dmesg log I sa
On Tue, Apr 9, 2013 at 8:39 PM, Sedat Dilek wrote:
> On Tue, Apr 9, 2013 at 8:29 PM, Sedat Dilek wrote:
>> On Tue, Apr 9, 2013 at 8:26 PM, Sedat Dilek wrote:
>>> On Tue, Apr 9, 2013 at 6:51 PM, Viresh Kumar
>>> wrote:
On 9 April 2013 21:38, Sedat Dilek wrote:
> With x=3 the system ge
On Tue, Apr 9, 2013 at 11:30 AM, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20130408:
>
> The vfs tree still had its build failure so I used the version from
> next-20130405.
>
With the attached patch including a follow-up I was able to boot
today's Linux-Next.
I have reverted "Revert "
On Tue, Apr 9, 2013 at 6:51 PM, Viresh Kumar wrote:
> On 9 April 2013 21:38, Sedat Dilek wrote:
>> With x=3 the system gets in an unuseable state.
>>
>> root# echo 0 > /sys/devices/system/cpu/cpu3/online
>>
>> I could not write my reply and had to do a hard/cold reboot.
>> The dmesg log I sa
On 9 April 2013 21:38, Sedat Dilek wrote:
> With x=3 the system gets in an unuseable state.
>
> root# echo 0 > /sys/devices/system/cpu/cpu3/online
>
> I could not write my reply and had to do a hard/cold reboot.
> The dmesg log I saw looked similiar to my digicam-shot.
Few things i need from
On Tue, Apr 9, 2013 at 4:56 PM, Viresh Kumar wrote:
> On 9 April 2013 19:34, Sedat Dilek wrote:
>> I have seen it on reboots.
>> How to online/offline from sysfs?
>
> offline a cpu "x" with:
>
> echo 0 > /sys/devices/system/cpu/cpux/online
>
> and online with echo 1 > to same location.
With x=3
On Tue, Apr 9, 2013 at 5:11 PM, Sedat Dilek wrote:
> On Tue, Apr 9, 2013 at 4:32 PM, Sedat Dilek wrote:
>> On Tue, Apr 9, 2013 at 4:23 PM, Stephen Rothwell
>> wrote:
>>> Hi Sedat,
>>>
>>> On Tue, 9 Apr 2013 16:11:50 +0200 Sedat Dilek wrote:
[ CC Al Viro ]
>>>
>>> You forgot to do tha
On Tue, Apr 9, 2013 at 4:32 PM, Sedat Dilek wrote:
> On Tue, Apr 9, 2013 at 4:23 PM, Stephen Rothwell
> wrote:
>> Hi Sedat,
>>
>> On Tue, 9 Apr 2013 16:11:50 +0200 Sedat Dilek wrote:
>>>
>>> [ CC Al Viro ]
>>
>> You forgot to do that ...
>>
>>> Is there a "magic" git-command to revert all commi
On Tue, Apr 9, 2013 at 4:56 PM, Viresh Kumar wrote:
> On 9 April 2013 19:34, Sedat Dilek wrote:
>> I have seen it on reboots.
>> How to online/offline from sysfs?
>
> offline a cpu "x" with:
>
> echo 0 > /sys/devices/system/cpu/cpux/online
>
> and online with echo 1 > to same location.
Eh, yeah
On 9 April 2013 19:33, Rafael J. Wysocki wrote:
> On Tuesday, April 09, 2013 02:47:39 PM Sedat Dilek wrote:
>> On reboot I see hanging cpufreq with the help of kdb/kgdb?
>> See screenshot.
>>
>> I have also a screenshot with next-20130326, so this issue seems not to be
>> new.
>
> This is during
On 9 April 2013 19:34, Sedat Dilek wrote:
> I have seen it on reboots.
> How to online/offline from sysfs?
offline a cpu "x" with:
echo 0 > /sys/devices/system/cpu/cpux/online
and online with echo 1 > to same location.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" i
On Tue, Apr 9, 2013 at 4:23 PM, Stephen Rothwell wrote:
> Hi Sedat,
>
> On Tue, 9 Apr 2013 16:11:50 +0200 Sedat Dilek wrote:
>>
>> [ CC Al Viro ]
>
> You forgot to do that ...
>
>> Is there a "magic" git-command to revert all commits coming from your
>> latest vfs-merge (commit c1c04d3667608a630a
Hi Sedat,
On Tue, 9 Apr 2013 16:11:50 +0200 Sedat Dilek wrote:
>
> [ CC Al Viro ]
You forgot to do that ...
> Is there a "magic" git-command to revert all commits coming from your
> latest vfs-merge (commit c1c04d3667608a630ae0821995b465a523e83fb1)?
>
> 2013-04-09 11:36 Stephen Rothwell │ M─
On Tue, Apr 9, 2013 at 3:59 PM, Stephen Rothwell wrote:
> Hi Sedat,
>
> On Tue, 9 Apr 2013 12:56:46 +0200 Sedat Dilek wrote:
>>
>> This version hangs... I started in rescue-mode and see that udev,
>> premount and init scripts are run.
>> Currently, I have no glue why when what...
>> Lemme see if
On Tue, Apr 9, 2013 at 4:03 PM, Rafael J. Wysocki wrote:
> On Tuesday, April 09, 2013 02:47:39 PM Sedat Dilek wrote:
>> On Tue, Apr 9, 2013 at 11:30 AM, Stephen Rothwell
>> wrote:
>> > Hi all,
>> >
>> > Changes since 20130408:
>> >
>> > The vfs tree still had its build failure so I used the vers
On Tue, Apr 9, 2013 at 3:59 PM, Stephen Rothwell wrote:
> Hi Sedat,
>
> On Tue, 9 Apr 2013 12:56:46 +0200 Sedat Dilek wrote:
>>
>> This version hangs... I started in rescue-mode and see that udev,
>> premount and init scripts are run.
>> Currently, I have no glue why when what...
>> Lemme see if
Hi Sedat,
On Tue, 9 Apr 2013 12:56:46 +0200 Sedat Dilek wrote:
>
> This version hangs... I started in rescue-mode and see that udev,
> premount and init scripts are run.
> Currently, I have no glue why when what...
> Lemme see if I get k(g)bd started.
>
> Unfortunately, there was a "quiet" boot-
On Tuesday, April 09, 2013 02:47:39 PM Sedat Dilek wrote:
> On Tue, Apr 9, 2013 at 11:30 AM, Stephen Rothwell
> wrote:
> > Hi all,
> >
> > Changes since 20130408:
> >
> > The vfs tree still had its build failure so I used the version from
> > next-20130405.
> >
> > The wireless-next tree lost its
On Tue, Apr 9, 2013 at 2:37 PM, Sedat Dilek wrote:
> On Tue, Apr 9, 2013 at 12:56 PM, Sedat Dilek wrote:
>> Hi,
>>
>> I still did not get the original posting...
>>
>> This version hangs... I started in rescue-mode and see that udev,
>> premount and init scripts are run.
>
> ... udevd
> /scr
On Tue, Apr 9, 2013 at 12:56 PM, Sedat Dilek wrote:
> Hi,
>
> I still did not get the original posting...
>
> This version hangs... I started in rescue-mode and see that udev,
> premount and init scripts are run.
... udevd
/scripts/init-premount ... done
/scripts/pre-premount ... done
/scrip
Hi all,
Changes since 20130408:
The vfs tree still had its build failure so I used the version from
next-20130405.
The wireless-next tree lost its build failure.
The mfd tree still had its build failure so I used the version from
next-20130405.
The ftrace tree gained a conflict against Linus'
64 matches
Mail list logo
