Bug 128745 - [zyd] zyd theoretically supported usb device makes kernel panic
Summary: [zyd] zyd theoretically supported usb device makes kernel panic
Status: Open
Alias: None
Product: Base System
Classification: Unclassified
Component: usb (show other bugs)
Version: 7.1-PRERELEASE
Hardware: Any Any
: Normal Affects Only Me
Assignee: freebsd-usb (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-11-10 06:20 UTC by aGaTHoS
Modified: 2017-12-31 22:27 UTC (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description aGaTHoS 2008-11-10 06:20:01 UTC
Usb zyd device with vendor and product id's: 0x0ace, 0x1215, causes kernel panic inmediately when plugged.

How-To-Repeat: 1. plug zyd device with vendor and product id's 0x0ace, 0x1215
2. wait 2 or 3 seconds :)

[root@ares ~]# kgdb /usr/obj/usr/src/sys/ARES/kernel.debug /var/crash/vmcore.1 
GNU gdb 6.1.1 [FreeBSD]
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "amd64-marcel-freebsd"...

Unread portion of the kernel message buffer:
zyd0: zyd_read sleep timeout
ehci_check_intr: sqtdstart=NULL


Fatal trap 12: page fault while in kernel mode
cpuid = 1; apic id = 01
fault virtual address   = 0x38
fault code              = supervisor read data, page not present
instruction pointer     = 0x8:0xffffffff802273df
stack pointer           = 0x10:0xffffffffacd82be0
frame pointer           = 0x10:0xffffffffacdb1f80
code segment            = base rx0, limit 0xfffff, type 0x1b
                        = DPL 0, pres 1, long 1, def32 0, gran 1
processor eflags        = interrupt enabled, resume, IOPL = 0
current process         = 28 (usbtask-hc)
trap number             = 12
panic: page fault
cpuid = 1
Uptime: 18m29s
ehci_check_intr: sqtdstart=NULL
ehci_check_intr: sqtdstart=NULL
ehci_check_intr: sqtdstart=NULL
ehci_check_intr: sqtdstart=NULL
ehci_check_intr: sqtdstart=NULL
ehci_check_intr: sqtdstart=NULL
Physical memory: 2037 MB
Dumping 165 MB: 150 134 118 102 86 70 54 38 22 6

Reading symbols from /boot/kernel/zfs.ko...Reading symbols from /boot/kernel/zfs.ko.symbols...done.
done.
Loaded symbols for /boot/kernel/zfs.ko
Reading symbols from /boot/kernel/opensolaris.ko...Reading symbols from /boot/kernel/opensolaris.ko.
symbols...done.
done.
Loaded symbols for /boot/kernel/opensolaris.ko
Reading symbols from /boot/kernel/if_zyd.ko...Reading symbols from /boot/kernel/if_zyd.ko.symbols...
done.
done.
Loaded symbols for /boot/kernel/if_zyd.ko
Reading symbols from /boot/kernel/wlan_amrr.ko...Reading symbols from /boot/kernel/wlan_amrr.ko.symb
ols...done.
done.
Loaded symbols for /boot/kernel/wlan_amrr.ko
Reading symbols from /boot/kernel/wlan.ko...Reading symbols from /boot/kernel/wlan.ko.symbols...done
Comment 1 Weongyo Jeong freebsd_committer 2008-11-11 01:36:06 UTC
Responsible Changed
From-To: freebsd-usb->weongyo

Promised to him I'll look at this PR.
Comment 2 Weongyo Jeong freebsd_committer 2008-12-09 01:39:30 UTC
State Changed
From-To: open->feedback

I've requested to him testing on Linux or Windows because his H/W looks 
abnormal.  So waiting his response.
Comment 3 Mark Linimon freebsd_committer freebsd_triage 2013-07-03 01:50:32 UTC
State Changed
From-To: feedback->feedback

commit bit has been taken in for safekeeping. 


Comment 4 Mark Linimon freebsd_committer freebsd_triage 2013-07-03 01:50:32 UTC
Responsible Changed
From-To: weongyo->freebsd-usb
Comment 5 Eitan Adler freebsd_committer freebsd_triage 2017-12-31 08:00:26 UTC
For bugs matching the following criteria:

Status: In Progress Changed: (is less than) 2014-06-01

Reset to default assignee and clear in-progress tags.

Mail being skipped