[Bug 1662891] Re: kernel NULL pointer dereference

2017-02-13 Thread Henrik Schmidt
Due to long running research projects on this computer I can not test
the upstream kernel in the near future.

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

Title:
  kernel NULL pointer dereference

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

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


[Bug 1662891] [NEW] kernel NULL pointer dereference

2017-02-08 Thread Henrik Schmidt
Public bug reported:

BUG: unable to handle kernel NULL pointer dereference at
0008

On login to the computer with ssh I can no longer call htop (blank
screen) or ps -elf (freeze after displaying the result).

The computer was upgraded from 1TB ECC RAM to 1.5 TB ECC RAM a few days
before the event.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-59-generic 4.4.0-59.80
ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
Uname: Linux 4.4.0-59-generic x86_64
AlsaDevices:
 total 0
 crw-rw+ 1 root audio 116,  1 Jan 30 11:22 seq
 crw-rw+ 1 root audio 116, 33 Jan 30 11:22 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
Date: Wed Feb  8 14:14:36 2017
HibernationDevice: RESUME=UUID=b80a8df2-0260-4eeb-ab4a-68bb246e5f6e
InstallationDate: Installed on 2016-05-02 (282 days ago)
InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.3)
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
JournalErrors:
 Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
   Users in the 'systemd-journal' group can see all messages. Pass -q to
   turn off this notice.
 No journal files were opened due to insufficient permissions.
MachineType: Supermicro SYS-6028U-TRT+
PciMultimedia:
 
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.utf8
 SHELL=/bin/bash
ProcFB: 0 astdrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-59-generic 
root=UUID=26de5dd5-eed8-4ccb-ad03-c832b4760c7f ro
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-59-generic N/A
 linux-backports-modules-4.4.0-59-generic  N/A
 linux-firmware1.157.6
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
WifiSyslog:
 
dmi.bios.date: 12/17/2015
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2.0
dmi.board.asset.tag: Default string
dmi.board.name: X10DRU-i+
dmi.board.vendor: Supermicro
dmi.board.version: 1.01
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 1
dmi.chassis.vendor: Supermicro
dmi.chassis.version: 0123456789
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2.0:bd12/17/2015:svnSupermicro:pnSYS-6028U-TRT+:pvr0123456789:rvnSupermicro:rnX10DRU-i+:rvr1.01:cvnSupermicro:ct1:cvr0123456789:
dmi.product.name: SYS-6028U-TRT+
dmi.product.version: 0123456789
dmi.sys.vendor: Supermicro

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug xenial

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

Title:
  kernel NULL pointer dereference

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

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


[Bug 1367296] Re: Software RAID1 gets stuck on data check

2014-09-10 Thread Henrik Schmidt
Unable to test upstream kernel as we need the system running for some days 
which it still does.
Will a reboot in this state leave me with a broken system ?

** Tags added: kernel-unable-to-test-upstream

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

Title:
  Software RAID1 gets stuck on data check

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

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


[Bug 1367296] [NEW] Software RAID1 gets stuck on data check

2014-09-09 Thread Henrik Schmidt
Public bug reported:

Description:Ubuntu 14.04.1 LTS
Release:14.04

cat /proc/mdstat shows that md1 (swap) got stuck at 0% during the
nightly data check of the RAID.

In hope of stopping the sync I called

/usr/share/mdadm/checkarray -x -a

This was a bad idea as this command got stuck too and cat /proc/mdstat
was useless afterwards as it did not show anything nor finish.

No idea what to do as I fear a reboot will leave me with a damaged
system.

dmesg showed this multiple times :

[4367634.910108] INFO: task md1_resync:16812 blocked for more than 120 seconds.
[4367634.954575]   Not tainted 3.13.0-32-generic #57-Ubuntu
[4367634.978601] echo 0  /proc/sys/kernel/hung_task_timeout_secs disables 
this message.
[4367635.028209] md1_resync  D 885fbf354440 0 16812  2 
0x
[4367635.028225]  8820386cbbf8 0002 880dd3ce17f0 
8820386cbfd8
[4367635.028230]  00014440 00014440 880dd3ce17f0 
8825e4566d00
[4367635.028232]  885f75ea84f8 8820386cbc70 885f75ea84e0 
885f75ea8480
[4367635.028235] Call Trace:
[4367635.028248]  [817200d9] schedule+0x29/0x70
[4367635.028265]  [a0047437] sync_request+0x227/0xb30 [raid1]
[4367635.028270]  [810aaf00] ? prepare_to_wait_event+0x100/0x100
[4367635.028274]  [815a8d33] md_do_sync+0x9a3/0xdd0
[4367635.028277]  [815a58d8] md_thread+0x118/0x130
[4367635.028279]  [815a57c0] ? mddev_unlock+0xe0/0xe0
[4367635.028282]  [8108b3d2] kthread+0xd2/0xf0
[4367635.028284]  [8108b300] ? kthread_create_on_node+0x1d0/0x1d0
[4367635.028288]  [8172c5bc] ret_from_fork+0x7c/0xb0
[4367635.028290]  [8108b300] ? kthread_create_on_node+0x1d0/0x1d0

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-32-generic 3.13.0-32.57
ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
Uname: Linux 3.13.0-32-generic x86_64
AlsaDevices:
 total 0
 crw-rw 1 root audio 116,  1 Sep  3 12:31 seq
 crw-rw 1 root audio 116, 33 Sep  3 12:31 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.14.1-0ubuntu3.3
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
CRDA: Error: [Errno 2] No such file or directory: 'iw'
Date: Tue Sep  9 15:12:19 2014
HibernationDevice: RESUME=UUID=86aad4c3-b114-4aaa-9cb7-c47ddd1c4c75
InstallationDate: Installed on 2014-07-07 (64 days ago)
InstallationMedia: Ubuntu-Server 14.04 LTS Trusty Tahr - Release amd64 
(20140416.2)
MachineType: Supermicro X9DRi-LN4+/X9DR3-LN4+
PciMultimedia:
 
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic 
root=UUID=223f3450-172e-43e3-b99f-205c21f39868 ro nomdmonddf nomdmonisw
RelatedPackageVersions:
 linux-restricted-modules-3.13.0-32-generic N/A
 linux-backports-modules-3.13.0-32-generic  N/A
 linux-firmware 1.127.5
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
WifiSyslog:
 
dmi.bios.date: 05/27/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 3.0b
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: X9DRi-LN4+/X9DR3-LN4+
dmi.board.vendor: Supermicro
dmi.board.version: REV:1.20A
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 17
dmi.chassis.vendor: Supermicro
dmi.chassis.version: 0123456789
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3.0b:bd05/27/2014:svnSupermicro:pnX9DRi-LN4+/X9DR3-LN4+:pvr0123456789:rvnSupermicro:rnX9DRi-LN4+/X9DR3-LN4+:rvrREV1.20A:cvnSupermicro:ct17:cvr0123456789:
dmi.product.name: X9DRi-LN4+/X9DR3-LN4+
dmi.product.version: 0123456789
dmi.sys.vendor: Supermicro

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug trusty

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

Title:
  Software RAID1 gets stuck on data check

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

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


[Bug 114482] Re: [feisty] At boot-up I'm connected to an untrusted wireless network and Network Manager doesn't tell me about it

2008-04-06 Thread Henrik Schmidt
I cannot reproduce the bug in Hardy, so it would seem fixed :)

-- 
[feisty] At boot-up I'm connected to an untrusted wireless network and Network 
Manager doesn't tell me about it
https://bugs.launchpad.net/bugs/114482
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.

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


[Bug 114482] Re: [feisty] At boot-up I'm connected to an untrusted wireless network and Network Manager doesn't tell me about it

2007-05-14 Thread Henrik Schmidt
OK, I still feel it is a security issue, but of course it depends on how
many people are affected by it. In the meantime I have been able to
reproduce the issue with the server being (accidentally) spoofed. The
reason it's hard to test this is, that I don't have my own wireless
network, and I can't affect when other people connect to the wireless
network or if they're close enough for me to talk to them.

Prerequisites to reproduce (rather hardware and setup intensive, I'm
afraid):

- A laptop with wired and wireless network, preferably similar hardware
to the Dell Latitude D505, with a newly installed Feisty. If you in fact
use the D505, you need to install the bcm43xx driver to get the wireless
working.

sudo apt-get install bcm43xx-fwcutter
sudo /usr/share/bcm43xx-fwcutter/install_bcm43xx_firmware.sh

- A wireless router with a DHCP server set up similar to your wired DHCP
server (same local IP range etc.). The router should not have any
security set up.

Steps to reproduce:

1. Bootup your laptop wired. Verify that n-m tells your that you're on the 
wired network.
2. Try to ping the remote network (ping -Ieth1 192.168.1.1)
3. If you can ping the remote network try to physically disconnect your laptop 
from the wired network. Verify tha nm-applet tells you you've been disconnected.
4. Now do a traceroute (or use a browser to connect to for example google.com). 
Verify that you're going through the wireless router.
5. Reconnect your wired network. Verify that n-m tells you that you're 
connected to the wired network.
6. Repeat step 4. Sometimes you should still be connected to the wireless 
network and go through the wireless router.

I'm always able to do this. If you're not, it must be some issue with my
specific hardware.

If you can't do the above, you're done. Otherwise, here's the
preriquisites for the server spoofing issue

- A server at some address not specified by your wired DHCP server (like 
192.168.1.2)
- Another PC with the same IP as the internal server (192.168.1.2) connected to 
the wireless. 

7. After step 6 has been completed, try to ping to 192.168.1.2. Lookup
the MAC address in the arp table (arp -a 192.168.1.2). If the MAC
address is the remote 1921.168.1.2, you've succesfully spoofed the
internal server.

-- 
[feisty] At boot-up I'm connected to an untrusted wireless network and Network 
Manager doesn't tell me about it
https://bugs.launchpad.net/bugs/114482
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.

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