[Bug 1821564] Re: b44 Ethernet driver null pointer during initialization

2021-10-27 Thread Boris Gjenero
No, "pcie_aspm=off" does not help.

I also tried uninstalling broadcom-sta-dkms. It blacklists the b44
module via /etc/modprobe.d/broadcom-sta-dkms.conf and also
https://wiki.debian.org/wl says that b44 is incompatible with wl. This
did not help either.

My laptop seems fine with just having the b44 module loaded. Lockups
only happen when I plug in the Ethernet cable and start using it. The
lockup seems total, with even Magic SysRq from the laptop's own keyboard
doing absolutely nothing.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1821564

Title:
  b44 Ethernet driver null pointer during initialization

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821564/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1821564] Re: b44 Ethernet driver null pointer during initialization

2021-10-20 Thread Kai-Heng Feng
Does kernel parameter "pcie_aspm=off" help?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1821564

Title:
  b44 Ethernet driver null pointer during initialization

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821564/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1821564] Re: b44 Ethernet driver null pointer during initialization

2021-10-03 Thread Boris Gjenero
In Ubuntu 21.10 with 5.13.0-16-generic kernel, I don't get any dmesg
errors after I "modprobe b44" and Ethernet works initially at reasonable
speed, but the whole system freezes totally after a few minutes. I
suppose this means the b44 driver still doesn't work properly, because I
don't get such freezes when using WiFi. Though I don't know for sure,
because I don't have any error messages.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1821564

Title:
  b44 Ethernet driver null pointer during initialization

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821564/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1821564] Re: b44 Ethernet driver null pointer during initialization

2020-07-03 Thread Kai-Heng Feng
Please test latest mainline kernel:
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.8-rc3/

If mainline kernel doesn't solve the issue please do a kernel bisection.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1821564

Title:
  b44 Ethernet driver null pointer during initialization

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821564/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1821564] Re: b44 Ethernet driver null pointer during initialization

2020-06-09 Thread Boris Gjenero
I don't see a null pointer message but the b44 driver is still broken in
5.4.0-33-generic on my Dell Inspiron 6400:

[ 3148.539194] ssb: Found chip with id 0x4401, rev 0x02 and package 0x00
[ 3148.599317] b44 :03:00.0: Sonics Silicon Backplane found on PCI device 
:03:00.0
[ 3148.599414] b44: Broadcom 44xx/47xx 10/100 PCI ethernet driver version 2.0
[ 3148.627839] b44 ssb1:0 eth0: Broadcom 44xx/47xx 10/100 PCI ethernet driver 
00:15:c5:b3:8a:ba
[ 3148.684246] swiotlb_tbl_map_single: 14 callbacks suppressed
[ 3148.684251] b44 :03:00.0: swiotlb buffer is full (sz: 1566 bytes), total 
0 (slots), used 0 (slots)
[ 3148.684261] [ cut here ]
[ 3148.684267] WARNING: CPU: 0 PID: 36638 at kernel/dma/direct.c:35 
report_addr+0x37/0x60
[ 3148.684268] Modules linked in: b44 mii iptable_filter bpfilter ccm b43 
dell_laptop dell_smm_hwmon snd_hda_codec_hdmi cordic kvm snd_hda_codec_idt 
snd_hda_codec_generic bcma ledtrig_audio radeon dell_wmi snd_hda_intel 
snd_intel_dspcfg dell_smbios dcdbas input_leds joydev mac80211 snd_hda_codec 
r852 sparse_keymap wmi_bmof serio_raw dell_wmi_descriptor ttm sm_common 
snd_hda_core nand snd_hwdep drm_kms_helper nand_ecc snd_pcm cfg80211 bch 
i2c_algo_bit snd_timer fb_sys_fops r592 nandcore mtd memstick syscopyarea 
sysfillrect snd libarc4 sysimgblt soundcore mac_hid sch_fq_codel coretemp 
parport_pc ppdev lp parport drm ip_tables x_tables autofs4 ssb_hcd gpio_ich 
pata_acpi i2c_i801 psmouse lpc_ich firewire_ohci sdhci_pci cqhci firewire_core 
sdhci crc_itu_t ssb wmi video
[ 3148.684314] CPU: 0 PID: 36638 Comm: NetworkManager Not tainted 
5.4.0-33-generic #37-Ubuntu
[ 3148.684315] Hardware name: Dell Inc. MM061   
/0XD720, BIOS A17 06/13/2007
[ 3148.684318] RIP: 0010:report_addr+0x37/0x60
[ 3148.684320] Code: 48 8b 87 28 02 00 00 48 89 75 f8 48 85 c0 74 2a 4c 8b 00 
b8 fe ff ff ff 49 39 c0 76 11 80 3d db c3 71 01 00 0f 84 7d 07 00 00 <0f> 0b c9 
c3 48 83 bf 38 02 00 00 00 74 f2 eb e3 80 3d bf c3 71 01
[ 3148.684321] RSP: 0018:9ae68055b450 EFLAGS: 00010246
[ 3148.684323] RAX: fffe RBX:  RCX: 
[ 3148.684324] RDX: 061e RSI: 6b440a80 RDI: 8cb34b4db0b0
[ 3148.684325] RBP: 9ae68055b458 R08: 3fff R09: 0004
[ 3148.684327] R10:  R11: 0001 R12: 8cb2f8b0c000
[ 3148.684328] R13: 061e R14: 8cb2f45cef00 R15: 8cb2f96ac8c0
[ 3148.684330] FS:  7f02e05ca240() GS:8cb34c60() 
knlGS:
[ 3148.684331] CS:  0010 DS:  ES:  CR0: 80050033
[ 3148.684333] CR2: 7f5935e43f28 CR3: c6128000 CR4: 06f0
[ 3148.684334] Call Trace:
[ 3148.684340]  dma_direct_map_page+0xdc/0xf0
[ 3148.684347]  b44_alloc_rx_skb+0x1bb/0x4a0 [b44]
[ 3148.684348]  ? dma_direct_alloc_pages+0x93/0x130
[ 3148.684351]  b44_init_rings+0xb8/0x190 [b44]
[ 3148.684354]  b44_open+0xfc/0x470 [b44]
[ 3148.684357]  __dev_open+0xd4/0x170
[ 3148.684359]  __dev_change_flags+0x191/0x1f0
[ 3148.684361]  dev_change_flags+0x26/0x60
[ 3148.684364]  do_setlink+0x82e/0x980
[ 3148.684368]  ? cpumask_next+0x1b/0x20
[ 3148.684371]  ? __snmp6_fill_stats64.isra.0+0xe7/0x110
[ 3148.684375]  ? __nla_validate_parse+0x42/0x140
[ 3148.684377]  __rtnl_newlink+0x580/0x970
[ 3148.684380]  ? __nla_put+0x20/0x30
[ 3148.684383]  ? __kmalloc_node_track_caller+0x205/0x320
[ 3148.684385]  ? pskb_expand_head+0x75/0x2d0
[ 3148.684387]  ? __kmalloc_reserve.isra.0+0x31/0x90
[ 3148.684391]  ? security_sock_rcv_skb+0x2f/0x50
[ 3148.684393]  ? sk_filter_trim_cap+0x48/0x220
[ 3148.684395]  ? skb_queue_tail+0x43/0x50
[ 3148.684397]  ? __netlink_sendskb+0x42/0x50
[ 3148.684401]  ? security_capable+0x3d/0x60
[ 3148.684404]  ? _cond_resched+0x19/0x30
[ 3148.684406]  ? kmem_cache_alloc_trace+0x16c/0x240
[ 3148.684408]  rtnl_newlink+0x49/0x70
[ 3148.684410]  rtnetlink_rcv_msg+0x2c0/0x380
[ 3148.684413]  ? vsnprintf+0x35d/0x4e0
[ 3148.684414]  ? rtnl_calcit.isra.0+0x100/0x100
[ 3148.684416]  netlink_rcv_skb+0x50/0x120
[ 3148.684418]  rtnetlink_rcv+0x15/0x20
[ 3148.684420]  netlink_unicast+0x187/0x220
[ 3148.684422]  netlink_sendmsg+0x222/0x3e0
[ 3148.684425]  sock_sendmsg+0x65/0x70
[ 3148.684426]  sys_sendmsg+0x212/0x280
[ 3148.684429]  ___sys_sendmsg+0x88/0xd0
[ 3148.684431]  ? rtnl_unlock+0xe/0x10
[ 3148.684433]  ? addrconf_sysctl_forward+0x111/0x280
[ 3148.684436]  ? get_max_files+0x20/0x20
[ 3148.684439]  ? __fget_light+0x57/0x70
[ 3148.684441]  __sys_sendmsg+0x5c/0xa0
[ 3148.68]  __x64_sys_sendmsg+0x1f/0x30
[ 3148.684447]  do_syscall_64+0x57/0x190
[ 3148.684450]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
[ 3148.684452] RIP: 0033:0x7f02e1a3b12d
[ 3148.684454] Code: 28 89 54 24 1c 48 89 74 24 10 89 7c 24 08 e8 ca ee ff ff 
8b 54 24 1c 48 8b 74 24 10 41 89 c0 8b 7c 24 08 b8 2e 00 00 00 0f 05 <48> 3d 00 
f0 ff ff 77 2f 44 89 c7 48 89 44 24 08 e8 fe ee ff ff 48
[ 3148.684455] RSP: 002b:7fffaac61a40 EFLAGS: 

[Bug 1821564] Re: b44 Ethernet driver null pointer during initialization

2020-06-08 Thread Kai-Heng Feng
Please test latest 20.04 kernel.

** Changed in: linux (Ubuntu)
   Status: Confirmed => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1821564

Title:
  b44 Ethernet driver null pointer during initialization

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821564/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1821564] Re: b44 Ethernet driver null pointer during initialization

2020-04-10 Thread Boris Gjenero
iommu=soft does not help, and I don't understand why it would help
theoretically when the Core 2 Duo T7400 CPU doesn't have a hardware
IOMMU. The problem seems to be that the 64 MB buffer is allocated beyond
1 GB.

One theoretical good workaround would be to boot up with only 1 GB and
then enable the rest of memory. But I'm not sure how to do that.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1821564

Title:
  b44 Ethernet driver null pointer during initialization

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821564/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1821564] Re: b44 Ethernet driver null pointer during initialization

2020-04-07 Thread Nelson Hennemann F
@Boris Gjenero, try using the kernel parameter "iommu=soft" instead of
limiting the memory to 1GB. It will force the use of a 64MB swiotlb
bounce buffer to workaround this issue. Tested with Focal Fossa Beta ISO
(Kernel 5.4.0-21-generic) on my Optiplex 320 with 2GB of RAM.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1821564

Title:
  b44 Ethernet driver null pointer during initialization

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821564/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1821564] Re: b44 Ethernet driver null pointer during initialization

2020-04-05 Thread Boris Gjenero
This problem still exists in Ubuntu Focal Fossa (development branch)
20.04 with linux-image-5.4.0-21-generic. It also exists in linux-image-
unsigned-5.6.2-050602-generic_5.6.2-050602.202004020822_amd64.deb

With linux-image-5.4.0-21-generic I didn't get any error messages after
"insmod b44" in recovery mode. Also I normally booted linux-
image-5.4.0-21-generic with mem=1G (limiting available memory to 1 GB)
twice and also didn't get error messages after "sudo insmod b44". These
symptoms are consistent with the hypothesis that swiotlb bounce buffers
normally get allocated above 1 GB, causing a problem for b44 because the
device can't do DMA above 1 GB and the driver can't handle this
situation. That's the same problem discussed in this thread from 2011
https://groups.google.com/forum/#!topic/linux.kernel/GEx80ZCue1o

Obviously limiting memory to 1 GB has an unacceptable performance
penalty, but it's nice to have at least one way to get working Ethernet.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1821564

Title:
  b44 Ethernet driver null pointer during initialization

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821564/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1821564] Re: b44 Ethernet driver null pointer during initialization

2020-01-02 Thread Boris Gjenero
I don't normally use Ethernet on my laptop, and for some reason the b44
module for Ethernet doesn't get loaded normally. So I didn't notice
this. But I'm getting the same problem reported in
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821564/comments/8
in Ubuntu 19.10 with linux-image-5.3.0-24-generic on my Inspiron 6400.
This Debian bug report has some ideas about a cause:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939697

** Bug watch added: Debian Bug tracker #939697
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939697

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1821564

Title:
  b44 Ethernet driver null pointer during initialization

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821564/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1821564] Re: b44 Ethernet driver null pointer during initialization

2019-05-26 Thread Nelson Hennemann F
@Hans P Möller, i've tested with kernel 5.1.0-050100rc3-generic and the
b44 module loaded and worked fine, but it created some others warnings
in the dmesg:

[   44.045886] b44 :02:09.0: swiotlb buffer is full (sz: 1566 bytes)
[   44.045906] WARNING: CPU: 1 PID: 565 at kernel/dma/direct.c:43 
report_addr+0x37/0x60
[   44.045908] Modules linked in: snd_hda_codec_analog snd_hda_codec_generic 
ledtrig_audio snd_hda_intel snd_hda_codec snd_hda_core snd_hwdep r8188eu(C) 
snd_pcm snd_seq_midi snd_seq_midi_event lib80211 radeon cfg80211 snd_rawmidi 
joydev input_leds dcdbas coretemp ttm drm_kms_helper snd_seq drm i2c_algo_bit 
fb_sys_fops syscopyarea sysfillrect serio_raw snd_seq_device sysimgblt 
snd_timer snd soundcore mac_hid sch_fq_codel parport_pc ppdev lp parport 
ip_tables x_tables autofs4 pata_acpi hid_generic usbhid hid psmouse b44 ssb mii 
pata_atiixp i2c_piix4 ahci libahci
[   44.045940] CPU: 1 PID: 565 Comm: NetworkManager Tainted: GWC
5.1.0-050100rc3-generic #201904010618
[   44.045942] Hardware name: Dell Inc. OptiPlex 320
 /0UT237, BIOS 1.1.12  06/17/2009
[   44.045944] RIP: 0010:report_addr+0x37/0x60
[   44.045946] Code: 48 8b 87 30 02 00 00 48 89 75 f8 48 85 c0 74 2a 4c 8b 00 
b8 fe ff ff ff 49 39 c0 76 11 80 3d f7 6b 72 01 00 0f 84 cf 07 00 00 <0f> 0b c9 
c3 48 83 bf 40 02 00 00 00 74 f2 eb e3 80 3d db 6b 72 01
[   44.045947] RSP: 0018:9fb4808af478 EFLAGS: 00010246
[   44.045949] RAX: fffe RBX: 88a93bc1f0b0 RCX: 
[   44.045950] RDX: 061e RSI: 7a2df880 RDI: 88a93bc1f0b0
[   44.045951] RBP: 9fb4808af480 R08: 3fff R09: 0004
[   44.045952] R10:  R11: 0001 R12: 061e
[   44.045953] R13: 88a92cc35500 R14:  R15: 88a93c2898c0
[   44.045955] FS:  7fd85987abc0() GS:88a93fc4() 
knlGS:
[   44.045956] CS:  0010 DS:  ES:  CR0: 80050033
[   44.045957] CR2: 7f0e4401e008 CR3: 33e44000 CR4: 06e0
[   44.045958] Call Trace:
[   44.045964]  dma_direct_map_page+0xdf/0xf0
[   44.045971]  b44_alloc_rx_skb+0x18e/0x3f0 [b44]
[   44.045973]  b44_init_rings+0xbe/0x1b0 [b44]
[   44.045976]  b44_open+0xfc/0x3f0 [b44]
[   44.045980]  __dev_open+0xd4/0x170
[   44.045982]  __dev_change_flags+0x18f/0x200
[   44.045984]  dev_change_flags+0x27/0x60
[   44.045986]  do_setlink+0x32c/0xe30
[   44.045991]  ? __nla_parse+0xf1/0x120
[   44.045995]  ? cpumask_next+0x1b/0x20
[   44.045998]  ? __snmp6_fill_stats64.isra.57+0xf6/0x120
[   44.046000]  ? __nla_parse+0x38/0x120
[   44.046002]  __rtnl_newlink+0x52a/0x8f0
[   44.046004]  ? __nla_put+0x20/0x30
[   44.046007]  ? __kmalloc_node_track_caller+0x1db/0x2b0
[   44.046009]  ? pskb_expand_head+0x70/0x2e0
[   44.046011]  ? __kmalloc_reserve.isra.53+0x31/0x90
[   44.046014]  ? apparmor_inet_conn_request+0x40/0x40
[   44.046017]  ? security_sock_rcv_skb+0x2f/0x50
[   44.046019]  ? sk_filter_trim_cap+0x48/0x210
[   44.046020]  ? skb_queue_tail+0x43/0x50
[   44.046024]  ? __netlink_sendskb+0x53/0x70
[   44.046029]  ? fib6_clean_node+0x40/0x180
[   44.046032]  ? _cond_resched+0x19/0x30
[   44.046034]  ? kmem_cache_alloc_trace+0x150/0x1d0
[   44.046036]  rtnl_newlink+0x48/0x70
[   44.046037]  rtnetlink_rcv_msg+0x213/0x300
[   44.046039]  ? rtnl_calcit.isra.32+0x100/0x100
[   44.046041]  netlink_rcv_skb+0x4f/0x120
[   44.046042]  rtnetlink_rcv+0x15/0x20
[   44.046044]  netlink_unicast+0x19f/0x260
[   44.046046]  netlink_sendmsg+0x20d/0x3c0
[   44.046048]  sock_sendmsg+0x3e/0x50
[   44.046050]  ___sys_sendmsg+0x295/0x2f0
[   44.046053]  ? rtnl_unlock+0xe/0x10
[   44.046055]  ? addrconf_sysctl_forward+0x114/0x280
[   44.046057]  ? security_capable+0x3f/0x60
[   44.046059]  ? dev_forward_change+0x140/0x140
[   44.046062]  ? lockref_put_or_lock+0x60/0x80
[   44.046064]  ? __fget_light+0x59/0x70
[   44.046066]  __sys_sendmsg+0x5c/0xa0
[   44.046068]  __x64_sys_sendmsg+0x1f/0x30
[   44.046071]  do_syscall_64+0x5a/0x110
[   44.046074]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
[   44.046076] RIP: 0033:0x7fd85b000cb7
[   44.046078] Code: 44 00 00 41 54 41 89 d4 55 48 89 f5 53 89 fb 48 83 ec 10 
e8 3b ed ff ff 44 89 e2 48 89 ee 89 df 41 89 c0 b8 2e 00 00 00 0f 05 <48> 3d 00 
f0 ff ff 77 35 44 89 c7 48 89 44 24 08 e8 74 ed ff ff 48
[   44.046079] RSP: 002b:7ffc8d8acb80 EFLAGS: 0293 ORIG_RAX: 
002e
[   44.046081] RAX: ffda RBX: 000a RCX: 7fd85b000cb7
[   44.046082] RDX:  RSI: 7ffc8d8acbd0 RDI: 000a
[   44.046083] RBP: 7ffc8d8acbd0 R08:  R09: 
[   44.046084] R10: 7fd85afe6ca0 R11: 0293 R12: 
[   44.046085] R13:  R14: 7ffc8d8acd88 R15: 7ffc8d8acd7c
[   44.046087] ---[ end trace 470ecf714c2b853b ]---
[   44.046098] b44 :02:09.0: swiotlb buffer is full (sz: 1566 byte

[Bug 1821564] Re: b44 Ethernet driver null pointer during initialization

2019-04-06 Thread Hans P . Möller
@Boris please test kernel 5.1.0-050100rc3-generic (or above) at least
#1822913 was solved with this kernel

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1821564

Title:
  b44 Ethernet driver null pointer during initialization

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821564/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1821564] Re: b44 Ethernet driver null pointer during initialization

2019-04-05 Thread Boris Gjenero
linux-image-
unsigned-4.20.0-042000-generic_4.20.0-042000.201812232030_amd64.deb is
good but linux-image-
unsigned-5.0.0-05rc1-generic_5.0.0-05rc1.201901062130_amd64.deb
is bad. I'm not sure I'll have time for a git bisect.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1821564

Title:
  b44 Ethernet driver null pointer during initialization

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821564/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1821564] Re: b44 Ethernet driver null pointer during initialization

2019-04-04 Thread Hans P Möller
I just tested Kernel 4.20.17 an it is good. I will do the bisect but I
don't have much time at this moment

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1821564

Title:
  b44 Ethernet driver null pointer during initialization

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821564/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1821564] Re: b44 Ethernet driver null pointer during initialization

2019-04-03 Thread Kai-Heng Feng
Ok, I failed to find where the regression comes from.

Would it be possible for you to do a kernel bisection?

First, find the last good -rc kernel and the first bad -rc kernel from
http://kernel.ubuntu.com/~kernel-ppa/mainline/

Then,
$ sudo apt build-dep linux
$ git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
$ cd linux
$ git bisect start
$ git bisect good $(the good version you found)
$ git bisect bad $(the bad version found)
$ make localmodconfig
$ make -j`nproc` deb-pkg
Install the newly built kernel, then reboot with it.
If the issue still happens,
$ git bisect bad
Otherwise,
$ git bisect good
Repeat to "make -j`nproc` deb-pkg" until you find the commit that causes the 
regression.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1821564

Title:
  b44 Ethernet driver null pointer during initialization

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821564/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1821564] Re: b44 Ethernet driver null pointer during initialization

2019-03-25 Thread Boris Gjenero
Sorry, I mean bug is not present in 4.18.0-16-generic and present in
5.0.0-7-generic

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1821564

Title:
  b44 Ethernet driver null pointer during initialization

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821564/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs