The following changes since commit 4dd3c2e5a4225e3df85afc6033e62ce8b09f0ed2:
Merge tag 'nfsd-4.15' of git://linux-nfs.org/~bfields/linux (2017-11-18
11:22:04 -0800)
are available in the git repository at:
git://www.linux-watchdog.org/linux-watchdog.git
for you to fetch changes up to
Hi Linus,
Please pull the watchdog fixes for the v4.16 release cycle.
This series contains:
* f71808e_wdt: Fix magic close handling
* sbsa: 32-bit read fix for WCV
* hpwdt: Remove legacy NMI sourcing
The output from git request-pull:
text and module licence match
watchdog: add SPDX identifiers for watchdog subsystem
Milton Miller (2):
watchdog: aspeed: Fix translation of reset mode to ctrl register
watchdog: aspeed: Allow configuring for alternate boot
Wim Van Sebroeck (4):
Merge branch 'v4.16-f
: rave-sp: add NVMEM dependency
Matteo Croce (1):
watchdog: i6300esb: fix build failure
Radu Rendec (1):
watchdog: xen_wdt: fix potential build failure
Wim Van Sebroeck (1):
watchdog: sp5100_tco.c: fix potential build failure
drivers/watchdog/Kconfig | 4
1 file changed
Hi Linus,
Please pull the watchdog fixes for the v4.16 release cycle.
This series contains:
* f71808e_wdt: Fix magic close handling
* sbsa: 32-bit read fix for WCV
* hpwdt: Remove legacy NMI sourcing
The output from git request-pull:
text and module licence match
watchdog: add SPDX identifiers for watchdog subsystem
Milton Miller (2):
watchdog: aspeed: Fix translation of reset mode to ctrl register
watchdog: aspeed: Allow configuring for alternate boot
Wim Van Sebroeck (4):
Merge branch 'v4.16-f
: rave-sp: add NVMEM dependency
Matteo Croce (1):
watchdog: i6300esb: fix build failure
Radu Rendec (1):
watchdog: xen_wdt: fix potential build failure
Wim Van Sebroeck (1):
watchdog: sp5100_tco.c: fix potential build failure
drivers/watchdog/Kconfig | 4
1 file changed
The following changes since commit 4dd3c2e5a4225e3df85afc6033e62ce8b09f0ed2:
Merge tag 'nfsd-4.15' of git://linux-nfs.org/~bfields/linux (2017-11-18
11:22:04 -0800)
are available in the git repository at:
git://www.linux-watchdog.org/linux-watchdog.git
for you to fetch changes up to
On Sat, Sep 03, 2005 at 02:42:36AM -0400, Daniel Phillips wrote:
On Friday 02 September 2005 20:16, Mark Fasheh wrote:
As far as userspace dlm apis go, dlmfs already abstracts away a large part
of the dlm interaction...
Dumb question, why can't you use sysfs for this instead of rolling
On Fri, Sep 02, 2005 at 11:17:08PM +0200, Andi Kleen wrote:
Andrew Morton [EMAIL PROTECTED] writes:
Again, that's not a technical reason. It's _a_ reason, sure. But what are
the technical reasons for merging gfs[2], ocfs2, both or neither?
clusterfilesystems are very common, there are
On 18-5-2015 12:45, Jes Sorensen wrote:
Wim de With nauxu...@wimdewith.com writes:
This is a patch that fixes the function declarations in
visorbus/visorchipset.c by removing newlines after the function return
type
This patch doesn't fix things, it makes things worse!
If you want to post
This is a patch that fixes the function declarations in
visorbus/visorchipset.c by removing newlines after the function return
type
Signed-off-by: Wim de With nauxu...@wimdewith.com
---
drivers/staging/unisys/visorbus/visorchipset.c | 225 ++---
1 file changed, 85 insertions
This patch fixes most of the lines over 80 characters long in
dgnc_sysfs.c. I couldn't find a way to break line 202-207 in a sensible
way. If there is a way, let me know.
Signed-off-by: Wim de With nauxu...@wimdewith.com
---
drivers/staging/dgnc/dgnc_sysfs.c | 110
/file.c:2483:36:expected void const
[noderef] *
drivers/staging/lustre/lustre/llite/file.c:2483:36:got void *
It simply casts pointers to __user pointers in most cases, and changes a
few pointers to __user pointers.
Signed-off-by: Wim de With <nauxu...@wimdewith.com>
---
drivers/s
This fixes the sparse warnings about dereferencing a userspace pointer.
Once I updated the sparse annotations, I noticed a bug in
gdm_wimax_ioctl() where we pass a user space pointer to gdm_update_fsm()
which dereferences it. I fixed this.
Signed-off-by: Wim de With <nauxu...@wimdewith.
On 10-12-2015 10:37, Dan Carpenter wrote:
> On Thu, Dec 10, 2015 at 10:11:12AM +0100, Wim de With wrote:
>> @@ -482,8 +483,16 @@ static int gdm_wimax_ioctl(struct net_device *dev,
>> struct ifreq *ifr, int cmd)
>> /* NOTE: gdm_update
this, and am not sure what to do about it.
Signed-off-by: Wim de With <nauxu...@wimdewith.com>
---
drivers/staging/gdm72xx/gdm_wimax.c | 17 +
drivers/staging/gdm72xx/wm_ioctl.h | 7 ++-
2 files changed, 19 insertions(+), 5 deletions(-)
diff --git a/drivers/staging/gdm72xx/gdm_w
On Thu, Dec 10, 2015 at 02:44:45PM +, One Thousand Gnomes wrote:
> (except that you mean sizeof(struct fsm_s) and it doesn't compile at the
> moment!
Oops, sloppy mistake.
> data_s can just be modified to be __user. All uses of it follow that
> rule.
What do you mean? The data still needs
This fixes the sparse warnings about dereferencing a userspace pointer.
Once I updated the sparse annotations, I noticed a bug in
gdm_wimax_ioctl() where we pass a user space pointer to gdm_update_fsm()
which dereferences it. I fixed this.
Signed-off-by: Wim de With <nauxu...@wimdewith.
ere in the kernel.
Could someone please explain and repair the magic that is happening here?
Thanks in advance, Wim Osterholt.
- w...@djo.tudelft.nl -
gt;
> int main(int argc, char *argv[])
> {
> if (open("foo", 3) == -1)
> perror("foo");
> return 0;
> }
No errors get printed for kernel 4.4 to 4.7 .
Regards, Wim.
- w...@djo.tudelft.nl -
rst 'wrong' kernel would be best)
git revert 09954bad448(that did something, which I assume te be good)
copied the .config file from 4.5 I had lying around and ran make.
Surprising or not, the thusly compiled kernel ran fine and I could handle
floppies like before!
(open(/dev/fd0,O_ACCMODE) succeeds.)
Regards, Wim.
- w...@djo.tudelft.nl -
r some such.
Problem is that fdutils is probably unmaintained for ten years or so.
Regards, Wim.
- w...@djo.tudelft.nl -
> PIRQ_PENALTY_PCI_USING;
> +
>
>
>
> > Bjorn
I tried this on kernel 4.7.0-rc4, but that didn't help. It still tried to
grab irq7.
Regards, Wim.
- w...@djo.tudelft.nl -
unction and then send
> the output?
>
> pr_info("%s:%d irq = %d penalty = %d\n", __func__, __LINE__, irq,
> penalty);
>
This produced some 60 lines extra. Too much to include here.
The entire dmesg file is here:
http://webserver.djo.tudelft.nl/d
+ACPI
http://webserver.djo.tudelft.nl/dmesg473+ACPI
http://webserver.djo.tudelft.nl/dmesg473noACPI
(with excuses for the silly hostname which is out of our control)
Regards, Wim.
- w...@djo.tudelft.nl -
On Wed, Jun 22, 2016 at 11:54:39PM -0400, ok...@codeaurora.org wrote:
> On 2016-06-21 18:13, Wim Osterholt wrote:
> >>
> >>pr_info("%s:%d irq = %d penalty = %d\n", __func__, __LINE__, irq,
> >>penalty);
> >>
> >
> >
On my first message I stated:
It looks to me that the code in floppy.c is quite old; no changes here.
So the bug is elsewhere in the kernel.
That was because the changelog at the beginning of floppy.c ended in 2003.
Wouln't it be wise to keep these items updated?
Groeten, Wim.
- w
On Wed, Jun 15, 2016 at 04:13:53PM +0200, Jiri Kosina wrote:
>
> Wim, could you please test whether the patch below, applied on top of
> vanilla kernel (i.e. drop the revert), everything you are using still
> works as expected?
>
Applied on kernel-4.7-rc3 it looks like it's w
p, Dell Inspiron 4100.
The same problem arises at a Dell Inspiron 510m.
I've not seen it on a workstation Dell XW4300.
Groeten, Wim.
- w...@djo.tudelft.nl -
ISA_IRQS)
> - penalty += acpi_isa_irq_penalty[irq];
> + return acpi_isa_irq_penalty[irq];
>
> /*
> * Penalize IRQ used by ACPI SCI. If ACPI SCI pin attributes conflict
Regards, Wim.
- w...@djo.tudelft.nl -
On Sat, Jun 25, 2016 at 04:51:03AM -0400, ok...@codeaurora.org wrote:
> On 2016-06-24 21:39, Wim Osterholt wrote:
>
> Please apply the patches on top of clean 4.7-rc4 tree and apply them in
> order with
>
> git am 0001...
> git am 0002...
It doesn't work that way.
Beginn
ed setfdprm userspace for ioctl-only open().
>
> Reintroduce back the original behavior wrt !(FMODE_READ|FMODE_WRITE)
> modes, while still keeping the original O_NDELAY bug fixed.
>
> Cc: sta...@vger.kernel.org # v4.5+
> Reported-by: Wim Osterholt <w...@djo.tudelft.nl>
&g
t; you something to test before posting the official version.
The 510m just finished compiling and now it works fine too.
Thanks.
Regards, Wim.
- w...@djo.tudelft.nl -
t is quite similar to the one from kernel-4.6 .
Tested-by: Wim Osterholt. <w...@djo.tudelft.nl>
, but it says
null pointer dereference at 0246
...
failed while handling devices/pci:00/:00:1d.3/usb7/7-1/7-1:1d etc.
...
udevd .. is taking too long..
Could someone please explain and repair the magic that is happening here?
Thanks in advance, Wim Osterholt.
- w...@djo.tudelft.nl -
0:00:1d.3/usb7/7-1/7-1:1.0'
Sep 6 19:15:44 localhost shutdown[13136]: shutting down for system reboot
Regards, Wim.
for anything the last 20 years or so.
I don't have the device at hand here, so new logs will be available
tomorrow.
Regards, Wim.
SS:ESP 0068:dc741ce8
[ 46.391243] CR2: 0246
[ 46.802809] ---[ end trace 3cd7f784cc67fa66 ]---
[ 46.811156] udevd[884]: worker [1868] terminated by signal 9 (Killed)
[ 46.811164] udevd[884]: worker [1868] failed while handling
'/devices/pci:00/:00:1d.2/usb4/4-1/4-1:1.1'
Regards, Wim.
y
difference, except for that it says 'a reboot is necessairy' en then it
freezes. Still no symbols.
Google didn't tell me anything useful, nor did you.
This took me days already.
I told you all you need: plug in a modem that needs cdc_acm.
Wim.
- w...@djo.tudelft.nl -
On Thu, Sep 08, 2016 at 03:05:15PM +0200, Oliver Neukum wrote:
>
> your stack trace is broken. Did you fail to install the System.map file?
>
> Regards
> Oliver
A laptop, more broken than the rest, does not output anything after
inserting. Later on it crashes. No system.map
_pci ohci_hcd uhci_hcd wmi floppy parport_pc soundcore
ehci_pci parport acpi_cpufreq ehci_hcd button processor
[ 551.177957] CPU: 0 PID: 725 Comm: kworker/0:2 Tainted: G O
4.8.0-rc8 #1
Regards, Wim.
On Wed, Sep 28, 2016 at 07:38:41PM -0400, Sinan Kaya wrote:
>
> Can you try these patches on your machines please?
I applied the included patches on vanilla 4.8-rc8 and my machine booted
fine. (I saw a remark about SCSI interrupts, but I have no SCSI.)
Regards, Wim.
RelDate4 04052004
wCountryCode 0x4803
Device Status: 0x
(Bus Powered)
Regards Wim.
On Wed, Sep 21, 2016 at 02:21:17PM +0200, Oliver Neukum wrote:
> On Tue, 2016-09-20 at 17:45 +0200, Wim Osterholt wrote:
>
> Anyway, which of its configurations is used?
> Please look up the bConfigurationValue for your device
> in sysfs.
And what might that be?
'locate sysfs
ads 'Conexant' and
bConfigurationValue which reads '1'
Regards, Wim.
and provide the full output of dmesg after that.
That is not possible under a 4.8 kernel.
'Fixing recursive fault but reboot is needed!' and frozen it is.
Regards, Wim.
e done in a safe 4.7.4 or a crashable 4.8.
(if I get that far to retrieve dmesg to a file).
Anyway, echo "module cdc_acm +mpf" > /sys/kernel/debug/dynamic_debug/control
results in 'No such file or directory' because there is no 'dynamic_debug'.
The kernel option DYNAMIC_DEBUG was not set.
A new kernel is compiling now..
Groeten, Wim.
trl_msg - rq 0x20,
val 0x0, len 0x7, result 7
4.8-rc7 is compiling now..
Regards, Wim.
249
[ 3745.49] ---[ end trace e6bc96526d51607e ]---
[ 3745.006322] udevd[945]: worker [24530] terminated by signal 9 (Killed)
[ 3745.008927] udevd[945]: worker [24530] failed while handling
'/devices/pci:00/:00:1d.3/usb6/6-1/6-1:1.0'
Regards, Wim.
thread_data+0xf/0x13 SS:ESP 0068:dec31f44
[ 410.763961] CR2: ffec
[ 410.763964] ---[ end trace 6872abde65b2c9e2 ]---
[ 410.763965] Fixing recursive fault but reboot is needed!
Regards, Wim.
if (quirks & NO_CAP_LINE)
1348acm->ctrl_caps &= ~USB_CDC_CAP_LINE;
1349acm->ctrlsize = ctrlsize;
1350acm->readsize = readsize;
(gdb) quit
A new kernel is compiling now.
Regards, Wim.
On Tue, Oct 18, 2016 at 02:18:43PM +0200, Oliver Neukum wrote:
> On Mon, 2016-10-17 at 17:20 +0200, Wim Osterholt wrote:
> > On Mon, Oct 17, 2016 at 04:10:45PM +0200, Oliver Neukum wrote:
> > > Hi,
> > >
> > > I got one of those devices. However, I don't
e = usb_endpoint_maxp(epctrl);
1329WARN_ON(!epread);
1330readsize = usb_endpoint_maxp(epread) *
1331(quirks == SINGLE_RX_URB ? 1 : 2);
1332acm->combined_interfaces = combined_interfaces;
1333WARN_ON(!epwrite);
1334acm->writesize = usb_endpoint_maxp(epwrite) * 20;
1335acm->control = control_interface;
1336acm->data = data_interface;
(gdb)
quit
Regards, Wim.
on other machines with (slightly) different configs all seem to
confirm that the problems are gone when CONFIG_SMP is set.
Regards, Wim.
On Mon, Nov 21, 2016 at 04:58:25PM +0100, Wim Osterholt wrote:
>
> I didn't find traces of kernel-4.9-rc5 being ran on any of my laptops, so I
> can't have seen a crash on rc5. It seems rc5 and rc6 is safe now.
Neither 4.8.10, nor 4.8.9 show the bug.
It must be a bug ousid
80 84 02 00 00 5d <8b> 40
ec c3 55 89 e5 52 3e 8d 74 26 00 b9 04 00 00 00 8b 90 84
[ 161.398316] EIP: [] kthread_data+0xf/0x13 SS:ESP 0068:df4dbf44
[ 161.398318] CR2: ffffffec
[ 161.398320] ---[ end trace da016e6d3520a332 ]---
[ 161.398321] Fixing recursive fault but reboot is needed!
Regards, Wim.
it could crash.
The oops does normally not immediately lead to a crash. Only with debugging
on it will halt immediately and the log will tell you that a reboot will
be necessairy.
Wim.
f what you mean here.
> would you? What's the output of
>
> cat /sys/bus/usb/drivers/cdc_acm/new_id
Just empty.
Wim.
On Wed, Nov 16, 2016 at 04:07:57PM +0100, Wim Osterholt wrote:
> A bit of patience please. Yesterday I hadn't the modem at hand.
Whell, I lost track of what happens where with which config file..
Confusion about the bug not appearing an too many configs with SMP set
where I'm sure the machin
On Thu, Nov 17, 2016 at 02:57:33AM +0100, Wim Osterholt wrote:
> Now a retry of 4.9-rc5. I take the config of 4.8.8 and accept
> the default for the new options.
> SMP set. No call trace appears.
> For completeness I should also try with SMP unset. That is for tomorrow
> then.
On Wed, Nov 16, 2016 at 01:34:30PM +0100, Oliver Neukum wrote:
>
> This is very odd. We need to know where it crashes. Please try the
> insane debug patch I posted.
A bit of patience please. Yesterday I hadn't the modem at hand.
Groeten, Wim.
On Thu, Nov 17, 2016 at 10:14:34AM +0100, Wim Osterholt wrote:
> > For completeness I should also try with SMP unset. That is for tomorrow
> > then.
>
> With CONFIG_SMP unset nothing goes wrong here either.
> It looks like it has been fixed in 4.9-rc5, but I should also d
On Mon, Nov 21, 2016 at 02:19:32PM +0100, Oliver Neukum wrote:
> On Thu, 2016-11-17 at 17:11 +0100, Wim Osterholt wrote:
>
> > Nov 17 15:07:51 localhost kernel: Check point 10
> > Nov 17 15:07:51 localhost kernel: BUG: unable to handle kernel NULL pointer
> > dereferenc
at shutdown
time). It's not even an oops but a warning. In the end it happens to just
work.
Regards, Wim.
Many options are inherited by 'make oldconfig' from version to version,
without me knowing what it all means. So maybe it's just a weird combination
of options then?
Regards, Wim.
On Sat, Jan 07, 2017 at 05:11:38PM +0100, Wim Osterholt wrote:
> On Thu, Dec 29, 2016 at 05:53:58PM +0100, Wim Osterholt wrote:
>
> L.S.,
> >
> > after appearance of kernel-4.10-rc1 two days ago...
>
> A quickly following release of 4.10-rc2 made sure that lir
On Thu, Dec 29, 2016 at 05:53:58PM +0100, Wim Osterholt wrote:
L.S.,
>
> after appearance of kernel-4.10-rc1 two days ago I was pleasantly surprised
> to find a question about lirc_serial in 'make oldconfig':
>
> Homebrew Serial Port Receiver (IR_SERIAL) [N/m/?] (NEW) m
>
in the kernel source.)
Regards, Wim.
Tom, you used the wrong GPL license header. Please fix that to be v2 not v3.
The
+# SPDX-License-Identifier: GPL-2.0
is correct but the adi-test.c one is not.
On 04/20/2018 10:34 AM, Tom Hromatka wrote:
Add a selftest for the sparc64 privileged ADI driver. These
tests verify the read(),
On Sat, Sep 03, 2005 at 02:42:36AM -0400, Daniel Phillips wrote:
> On Friday 02 September 2005 20:16, Mark Fasheh wrote:
> > As far as userspace dlm apis go, dlmfs already abstracts away a large part
> > of the dlm interaction...
>
> Dumb question, why can't you use sysfs for this instead of
On Fri, Sep 02, 2005 at 11:17:08PM +0200, Andi Kleen wrote:
> Andrew Morton <[EMAIL PROTECTED]> writes:
>
> >
> > Again, that's not a technical reason. It's _a_ reason, sure. But what are
> > the technical reasons for merging gfs[2], ocfs2, both or neither?
clusterfilesystems are very common,
Tom, you used the wrong GPL license header. Please fix that to be v2 not v3.
The
+# SPDX-License-Identifier: GPL-2.0
is correct but the adi-test.c one is not.
On 04/20/2018 10:34 AM, Tom Hromatka wrote:
Add a selftest for the sparc64 privileged ADI driver. These
tests verify the read(),
Hello Julius,
I agree with you. Using an existing standard is better than inventing a new one
in this case. I think using the coreboot logging is a good idea as there is
indeed a lot of support already available and it is lightweight and simple.
Best Regards,
Wim Vervoorn
Eltan B.V
This patch fixes most of the lines over 80 characters long in
dgnc_sysfs.c. I couldn't find a way to break line 202-207 in a sensible
way. If there is a way, let me know.
Signed-off-by: Wim de With
---
drivers/staging/dgnc/dgnc_sysfs.c | 110 +-
1 file
This is a patch that fixes the function declarations in
visorbus/visorchipset.c by removing newlines after the function return
type
Signed-off-by: Wim de With
---
drivers/staging/unisys/visorbus/visorchipset.c | 225 ++---
1 file changed, 85 insertions(+), 140 deletions
On 18-5-2015 12:45, Jes Sorensen wrote:
> Wim de With writes:
>> This is a patch that fixes the function declarations in
>> visorbus/visorchipset.c by removing newlines after the function return
>> type
>
> This patch doesn't fix things, it makes things worse!
>
80 84 02 00 00 5d <8b> 40
ec c3 55 89 e5 52 3e 8d 74 26 00 b9 04 00 00 00 8b 90 84
[ 161.398316] EIP: [] kthread_data+0xf/0x13 SS:ESP 0068:df4dbf44
[ 161.398318] CR2: ffffffec
[ 161.398320] ---[ end trace da016e6d3520a332 ]---
[ 161.398321] Fixing recursive fault but reboot is needed!
Regards, Wim.
it could crash.
The oops does normally not immediately lead to a crash. Only with debugging
on it will halt immediately and the log will tell you that a reboot will
be necessairy.
Wim.
f what you mean here.
> would you? What's the output of
>
> cat /sys/bus/usb/drivers/cdc_acm/new_id
Just empty.
Wim.
On Wed, Sep 21, 2016 at 02:21:17PM +0200, Oliver Neukum wrote:
> On Tue, 2016-09-20 at 17:45 +0200, Wim Osterholt wrote:
>
> Anyway, which of its configurations is used?
> Please look up the bConfigurationValue for your device
> in sysfs.
And what might that be?
'locate sysfs
ads 'Conexant' and
bConfigurationValue which reads '1'
Regards, Wim.
e done in a safe 4.7.4 or a crashable 4.8.
(if I get that far to retrieve dmesg to a file).
Anyway, echo "module cdc_acm +mpf" > /sys/kernel/debug/dynamic_debug/control
results in 'No such file or directory' because there is no 'dynamic_debug'.
The kernel option DYNAMIC_DEBUG was not set.
A new kernel is compiling now..
Groeten, Wim.
trl_msg - rq 0x20,
val 0x0, len 0x7, result 7
4.8-rc7 is compiling now..
Regards, Wim.
and provide the full output of dmesg after that.
That is not possible under a 4.8 kernel.
'Fixing recursive fault but reboot is needed!' and frozen it is.
Regards, Wim.
On Thu, Dec 29, 2016 at 05:53:58PM +0100, Wim Osterholt wrote:
L.S.,
>
> after appearance of kernel-4.10-rc1 two days ago I was pleasantly surprised
> to find a question about lirc_serial in 'make oldconfig':
>
> Homebrew Serial Port Receiver (IR_SERIAL) [N/m/?] (NEW) m
>
Many options are inherited by 'make oldconfig' from version to version,
without me knowing what it all means. So maybe it's just a weird combination
of options then?
Regards, Wim.
, but it says
null pointer dereference at 0246
...
failed while handling devices/pci:00/:00:1d.3/usb7/7-1/7-1:1d etc.
...
udevd .. is taking too long..
Could someone please explain and repair the magic that is happening here?
Thanks in advance, Wim Osterholt.
- w...@djo.tudelft.nl -
0:00:1d.3/usb7/7-1/7-1:1.0'
Sep 6 19:15:44 localhost shutdown[13136]: shutting down for system reboot
Regards, Wim.
for anything the last 20 years or so.
I don't have the device at hand here, so new logs will be available
tomorrow.
Regards, Wim.
SS:ESP 0068:dc741ce8
[ 46.391243] CR2: 0246
[ 46.802809] ---[ end trace 3cd7f784cc67fa66 ]---
[ 46.811156] udevd[884]: worker [1868] terminated by signal 9 (Killed)
[ 46.811164] udevd[884]: worker [1868] failed while handling
'/devices/pci:00/:00:1d.2/usb4/4-1/4-1:1.1'
Regards, Wim.
y
difference, except for that it says 'a reboot is necessairy' en then it
freezes. Still no symbols.
Google didn't tell me anything useful, nor did you.
This took me days already.
I told you all you need: plug in a modem that needs cdc_acm.
Wim.
- w...@djo.tudelft.nl -
RelDate4 04052004
wCountryCode 0x4803
Device Status: 0x
(Bus Powered)
Regards Wim.
On Wed, Nov 16, 2016 at 01:34:30PM +0100, Oliver Neukum wrote:
>
> This is very odd. We need to know where it crashes. Please try the
> insane debug patch I posted.
A bit of patience please. Yesterday I hadn't the modem at hand.
Groeten, Wim.
On Wed, Nov 16, 2016 at 04:07:57PM +0100, Wim Osterholt wrote:
> A bit of patience please. Yesterday I hadn't the modem at hand.
Whell, I lost track of what happens where with which config file..
Confusion about the bug not appearing an too many configs with SMP set
where I'm sure the machin
On Thu, Nov 17, 2016 at 02:57:33AM +0100, Wim Osterholt wrote:
> Now a retry of 4.9-rc5. I take the config of 4.8.8 and accept
> the default for the new options.
> SMP set. No call trace appears.
> For completeness I should also try with SMP unset. That is for tomorrow
> then.
On Thu, Nov 17, 2016 at 10:14:34AM +0100, Wim Osterholt wrote:
> > For completeness I should also try with SMP unset. That is for tomorrow
> > then.
>
> With CONFIG_SMP unset nothing goes wrong here either.
> It looks like it has been fixed in 4.9-rc5, but I should also d
On Mon, Nov 21, 2016 at 02:19:32PM +0100, Oliver Neukum wrote:
> On Thu, 2016-11-17 at 17:11 +0100, Wim Osterholt wrote:
>
> > Nov 17 15:07:51 localhost kernel: Check point 10
> > Nov 17 15:07:51 localhost kernel: BUG: unable to handle kernel NULL pointer
> > dereferenc
On Mon, Nov 21, 2016 at 04:58:25PM +0100, Wim Osterholt wrote:
>
> I didn't find traces of kernel-4.9-rc5 being ran on any of my laptops, so I
> can't have seen a crash on rc5. It seems rc5 and rc6 is safe now.
Neither 4.8.10, nor 4.8.9 show the bug.
It must be a bug ousid
on other machines with (slightly) different configs all seem to
confirm that the problems are gone when CONFIG_SMP is set.
Regards, Wim.
1 - 100 of 937 matches
Mail list logo
