DaemonForums  

Go Back   DaemonForums > OpenBSD > OpenBSD General

OpenBSD General Other questions regarding OpenBSD which do not fit in any of the categories below.

Reply
 
Thread Tools Display Modes
  #1   (View Single Post)  
Old 25th April 2011
shep shep is offline
ISO Quartermaster
 
Join Date: May 2008
Location: Dry and Dusty
Posts: 546
Thanked 9 Times in 9 Posts
Default Is Bug Reporting Broken in OpenBSD?

I have put a fair amount of effort trying to report a pciide bug with the Via sata controller (emulates ide) to the OpenBSD developers without much luck. When I look at the nabble mailing list there are 3 pages of bug reports intermixed with a significant quantity of spam. It is reminiscent of the old bsdforums.

The messages that have more than 1 post are "bumps" by the original poster. Can't find one that a developer has responded to. The developers seem to shift their focus at times ie openports.se showed a flurry of activity but has been quiet as of late. Given that 4.9 is being mailed from the CD replicators, the release push should be over and to me it seems a good time to begin addressing issues for 5.0

I like the simplicity of OpenBSD but development is becoming more of a developers Cathedral than an Opensource Bazaar. That will have consequences. Anyway my 2 cents.
Reply With Quote
  #2   (View Single Post)  
Old 25th April 2011
jggimi's Avatar
jggimi jggimi is offline
More noise than signal
 
Join Date: May 2008
Location: USA
Posts: 3,432
Thanked 214 Times in 189 Posts
Default

Shep, if you use sendbug(1) to report your bug, a structured problem report is sent to gnats@, which is the problem reporting database tracking tool program, and that will assign a PR number if it receives a formatted report. The bugs@ mailing list is sent a copy, and followup discussions may inadvertently occur there, but it is not used for reporting bugs directly.

If you just post to bugs@, your report will not be assigned a number, and will likely get lost in the noise.

That said, having a PR number is not a guarantee of immediate attention.

----

Edited to add: I've just looked at bugs@ and see what I think are your two posts there, on March 8 and again on April 19. They did not go through sendbug, so may not be seen by the appropriate developer(s).

Last edited by jggimi; 25th April 2011 at 04:46 PM.
Reply With Quote
  #3   (View Single Post)  
Old 25th April 2011
shep shep is offline
ISO Quartermaster
 
Join Date: May 2008
Location: Dry and Dusty
Posts: 546
Thanked 9 Times in 9 Posts
Default

Jiggimi;
The problem occurs during installation and the system goes tu before I can generate a dmesg (no null modem cable) or activate sendbug. I'll research sendbug to see if I can utilize it on a working system and paste the relevant info into sendbug. Looked at your link, I'll use the sendbug -D option so the report does not get littered with information not pertinent to the problem.

Thanks

Last edited by shep; 25th April 2011 at 06:31 PM. Reason: sendbug -D
Reply With Quote
  #4   (View Single Post)  
Old 26th April 2011
BSDfan666 BSDfan666 is offline
Real Name: N/A, this is the interweb.
Helpful companion
 
Join Date: Apr 2008
Location: Ontario, Canada
Posts: 2,223
Thanked 193 Times in 184 Posts
Default

They have no obligation to fix bugs, so, you'll have to do your best to provide as much information as you can.. verbose/debug pcidump/lspci output for the device, links to datasheets/specifications if they exist and you can find them.

Indeed, you can use sendbug(1) on another system to assemble and send your bug report.. if the system doesn't have mail configured properly, you'll need to provide another address for them to respond.

It is technically possible to send mail to gnats@ manually, but it should be in the format produced by sendbug.. and you need to be sure your mailer won't mangle lines or anything, no need for a subject on the message as the server will generate one itself.
Reply With Quote
  #5   (View Single Post)  
Old 26th April 2011
BSDfan666 BSDfan666 is offline
Real Name: N/A, this is the interweb.
Helpful companion
 
Join Date: Apr 2008
Location: Ontario, Canada
Posts: 2,223
Thanked 193 Times in 184 Posts
Default

Just found what I believe to be your message on the lists, have you considered building a kernel with debug messages enabled?

It may give some additional information to the developers, and if you can boot using a USB device there is no need to through the process of building a RAMDISK kernel.

option WDCDEBUG

Alternative, you can disable pciide in the UKC and the kernel will attempt to use the legacy ISA wdc(4) driver, it will be somewhat slower.

Good luck, just curious.. but does the BIOS/chipset not allow AHCI mode? that would avoid the pciide(4) driver usually.
Reply With Quote
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
openbsd 4.5 macppc radeon drive still broken gosha OpenBSD Installation and Upgrading 13 28th June 2009 03:14 PM
openbsd 4.3 e2fsprogs seems to be broken gosha OpenBSD Packages and Ports 0 27th June 2009 03:18 AM
netinet/in.h in OpenBSD 4.4 i386 broken? SunSpyda OpenBSD General 4 3rd June 2009 01:51 PM
Bug reporting jones OpenBSD General 4 3rd July 2008 02:51 PM


All times are GMT. The time now is 03:22 PM.


Powered by vBulletin® Version 3.8.4
Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content copyright © 2007-2010, the authors
Daemon image copyright ©1988, Marshall Kirk McKusick